Ubuntu
nautilus package

nautilus crashed with SIGSEGV in gconf_client_remove_dir()

Bug #213028 reported by Broomer68 on 2008-04-06

This bug report is a duplicate of: Bug #182345: nautilus crashed with SIGSEGV in gconf_client_remove_dir(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	nautilus (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: nautilus

don't know what happened. reported after reboot

ProblemType: Crash
Architecture: i386
Date: Sun Apr 6 22:11:28 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.22.1-1ubuntu3
PackageArchitecture: i386
ProcCmdline: nautilus --no-default-window --sm-client-id default2
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
gconf_client_remove_dir () from /usr/lib/libgconf-2.so.4
?? ()
?? ()
?? ()
?? ()
Title: nautilus crashed with SIGSEGV in gconf_client_remove_dir()
Uname: Linux 2.6.24-15-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags:

Revision history for this message

Broomer68 (jbezemer) wrote on 2008-04-06:

Dependencies.txt Edit (5.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (23.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (666 bytes, text/plain; charset="utf-8")
Registers.txt Edit (530 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (298 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (766 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2008-04-08: Symbolic stack trace

Stacktrace.txt (retraced) Edit (479 bytes, text/plain)

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-04-08:

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.