nautilus crashed with SIGSEGV in gtk_action_get_name()

Bug #1202360 reported by M.C. Botha
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Created a link to the Dropbox folder on Windows NTFS partition in my home directory.
Could be that Dropbox integration with Nautilus causes this.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
Date: Wed Jul 17 21:04:19 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1029x683+348+127'"
InstallationDate: Installed on 2013-07-17 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708)
MarkForUpload: True
ProcCmdline: nautilus --new-window
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb72a0503 <gtk_action_get_name+35>: cmp %eax,(%edx)
 PC (0xb72a0503) ok
 source "%eax" ok
 destination "(%edx)" (0xaaaaaaaa) in non-writable VMA region: 0xaaa48000-0xaab00000 ---p None
SegvReason: writing VMA None
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gtk_action_get_name () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nautilus crashed with SIGSEGV in gtk_action_get_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-07-17T20:36:10.424201

Revision history for this message
M.C. Botha (mcbotha) 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 #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.

information type: Private → Public
tags: removed: need-i386-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.