nautilus crashed with SIGSEGV in gtk_action_get_name()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 13.10 Saucy. Fault occured when logging in LXDE after logning out of GNOME
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSign
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelMo
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Sat Jul 13 02:48:29 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.
InstallationDate: Installed on 2013-07-13 (0 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Alpha amd64 (20130712)
MarkForUpload: True
ProcCmdline: nautilus --new-window
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f6f8d0d3d66 <gtk_action_
PC (0x7f6f8d0d3d66) ok
source "%rax" ok
destination "(%rdx)" (0xaaaaaaaaaaaa
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
gtk_action_
?? ()
?? ()
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in gtk_action_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev root 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 #1193522, 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.