nautilus crashed with SIGSEGV in g_slice_alloc()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Since installing 14.04 (fresh install) Nautilus crashes regularly (multiple times a day)and randomly with this error message. There is a symlink to another encrypted hard drive in a directory in my home directory.
Ubuntu 14.04 LTS
nautilus:
Installed: 1:3.10.1-0ubuntu9.2
Candidate: 1:3.10.1-0ubuntu9.2
Version table:
*** 1:3.10.1-0ubuntu9.2 0
500 http://
100 /var/lib/
1:
500 http://
Additional packages: nautilus-actions, -compare, -data, -open-terminal, -sendto, -sendto-empathy, -share, -wipe
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu9.2
ProcVersionSign
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Jul 18 14:00:54 2014
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
b'org.
InstallationDate: Installed on 2014-04-27 (81 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: nautilus --new-window
SegvAnalysis:
Segfault happened at: 0x7fb708d12297 <g_slice_
PC (0x7fb708d12297) ok
source "(%rbx)" (0x37373bff0a0a
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
g_slice_alloc () from /lib/x86_
g_slice_alloc0 () from /lib/x86_
g_type_
?? () from /usr/lib/
g_object_newv () from /usr/lib/
Title: nautilus crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1161468, 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.