caja crashed with SIGSEGV in g_main_context_dispatch()

Bug #2012421 reported by assa manara
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
caja (Ubuntu)
New
Undecided
Unassigned

Bug Description

bug appeared while I am attempting a fresh install of ubuntu mate 23.04
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu Lunar Lobster (development branch)
Release: 23.04

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: caja 1.26.1-1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.480
CurrentDesktop: MATE
Date: Tue Mar 21 17:40:58 2023
ExecutablePath: /usr/bin/caja
LiveMediaBuild: Ubuntu-MATE 23.04 "Lunar Lobster" - Alpha amd64 (20230321)
ProcCmdline: /usr/bin/caja
ProcEnviron:
 LANG=it_IT.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f1cfdeb37f1: mov (%rbx),%rdi
 PC (0x7f1cfdeb37f1) ok
 source "(%rbx)" (0x8f96bf8f5b311343) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: caja
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libmate-desktop-2.so.17
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_application_run () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: caja crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
separator:

Revision history for this message
assa manara (assamanara) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2012182, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.