caja crashed with SIGABRT in std::terminate()

Bug #1912106 reported by Norbert
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
caja (Ubuntu)
Invalid
Undecided
Unassigned
gcc-10 (Ubuntu)
Invalid
Undecided
Unassigned
snapd (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Open Caja, navigate to /snap/snapd/ , make right mouse click on current

ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: caja 1.24.0-1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Sun Jan 17 21:20:48 2021
ExecutablePath: /usr/bin/caja
ExecutableTimestamp: 1581590893
InstallationDate: Installed on 2020-10-23 (86 days ago)
InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcCmdline: /usr/bin/caja
ProcCwd: /home/mate
Signal: 6
SourcePackage: caja
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
 ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
 std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6
 ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
 __cxa_call_unexpected () from /lib/x86_64-linux-gnu/libstdc++.so.6
Title: caja crashed with SIGABRT in std::terminate()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
XsessionErrors:
 mate-session[1254]: WARNING: Unable to find provider '' of required component 'dock'
 (caja:1602): Gtk-WARNING **: 21:20:21.901: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
 (process:1704): ayatana-indicator-sound-WARNING **: 21:20:22.414: volume-control-pulse.vala:745: Unable to connect to dbus server at 'unix:path=/run/user/1000/pulse/dbus-socket': Could not connect: No such file or directory
 (caja:2303): Gtk-WARNING **: 21:20:53.497: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
mtime.conffile..etc.apport.crashdb.conf: 2021-01-17T21:23:17.387490
separator:

Revision history for this message
Norbert (nrbrtx) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /tmp/apport_sandbox_ozd1c05f/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28
 ?? () from /tmp/apport_sandbox_ozd1c05f/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28
 std::terminate() () from /tmp/apport_sandbox_ozd1c05f/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28
 ?? () from /tmp/apport_sandbox_ozd1c05f/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28
 __cxa_call_unexpected () from /tmp/apport_sandbox_ozd1c05f/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in caja (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for libgssapi-krb5-2
no debug symbol package found for libkrb5-3
no debug symbol package found for libk5crypto3
no debug symbol package found for libkrb5support0

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
Norbert (nrbrtx) wrote :

It is manually reported variant of bug 1912096 .

Matthias Klose (doko)
information type: Private → Public
Revision history for this message
Matthias Klose (doko) wrote :

LP: #1912096 talk about a snapd issue

Revision history for this message
Matthias Klose (doko) wrote :

looking at the stacktrace, looks more like an issue with some caja extension.

Changed in gcc-10 (Ubuntu):
status: New → Invalid
Revision history for this message
Norbert (nrbrtx) wrote :

Can you reproduce this bug with newer version of Ubuntu MATE?

tags: removed: groovy
Changed in snapd (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for snapd (Ubuntu) because there has been no activity for 60 days.]

Changed in snapd (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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