nautilus crashed with SIGSEGV in gtk_action_get_name()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
That's happening when I click on file:
$ nautilus .
(nautilus:12018): Gtk-WARNING **: Theme parsing error: gtk-widgets.
Initializing nautilus-dropbox 1.6.0
Initializing nautilus-
(nautilus:12018): GLib-GObject-
(nautilus:12018): GLib-GObject-
Nautilus-
Please ask your system administrator to enable user sharing.
(nautilus:12018): Gtk-WARNING **: Refusing to add non-unique action 'NautilusDropbo
Violación de segmento (`core' generado)
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: nautilus 1:3.8.2-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 22 16:23:29 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
InstallationDate: Installed on 2012-09-14 (372 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: nautilus --new-window
ProcEnviron:
LANGUAGE=es
PATH=(custom, no user)
XDG_RUNTIME_
LANG=es_ES.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f9bac5e4cc6 <gtk_action_
PC (0x7f9bac5e4cc6) 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: Upgraded to saucy on 2013-09-21 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers www-data
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.