caja crashed with SIGABRT in g_assertion_message()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
caja (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Crash right after starting caja
Some other comments from the duplicate bugs:
* "I had just installed caja-actions and then added "noatime" to my fstab to use when mounting the root partition." (LP: #1564580)
* "Copied a file in split pane mode from local hd to usb drive and removed usb drive after copy." (LP: #1569427)
* "I'm just tinkering with an external SMB server. This report is generated automatically, I'm just a user." (LP: #1570363)
* "I think I traced the source of the crash to me pulling the rug from under Caja. As I'm still learning Samba 4, I changed the name of a connected share while the server was still connected and I think that's what caused the drop out."
* "I installed caja-actions yesterday and received this error when starting up. Ubuntu Yakkety Yak (development branch)" (LP: #1598959)
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: caja 1.10.4-1
ProcVersionSign
Uname: Linux 4.2.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: MATE
Date: Mon Oct 12 21:38:26 2015
ExecutablePath: /usr/bin/caja
ProcCmdline: caja
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
XDG_RUNTIME_
Signal: 6
SourcePackage: caja
StacktraceTop:
g_assertion_
g_assertion_
?? ()
?? () from /usr/lib/
g_signal_
Title: caja crashed with SIGABRT in g_assertion_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lp lpadmin netdev plugdev sambashare sudo
information type: | Private → Public |
description: | updated |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.