nautilus crashed with SIGSEGV in gconf_client_get()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus-open-terminal (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have tried to change the color model. First I opened the dialog of the settings for my desktop (right-click on desktop background) then chose to change the background image, I changed the background image and the theme and then clicked on "all settings" (German: Alle Einstellungen) there I chose colors.
There was still a printer that was not connected and actually it was broken so I threw it away. I wanted to delete it from here and right-clicked on it, then the application crashed.
I am not if this was related to the right-click or if it was just a delayed reaction after some of the previous actions. I successfully changed the background and it stayed that way.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus-
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Sat Oct 8 22:15:20 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: nautilus
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x56c8f99 <gconf_
PC (0x056c8f99) ok
source "%eax" ok
destination "(%edx)" (0x00000008) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nautilus-
StacktraceTop:
gconf_client_get () from /usr/lib/
gconf_
nautilus_
nautilus_
?? ()
Title: nautilus crashed with SIGSEGV in gconf_client_get()
UpgradeStatus: Upgraded to oneiric on 2011-10-08 (0 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare tape video
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #869856, 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.