nautilus crashed with SIGSEGV in gconf_client_remove_dir()

Bug #253911 reported by ingo
4
Affects Status Importance Assigned to Milestone
nautilus-actions (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: nautilus

Hardy-amd64

Crash happened after today's (01.08.2008) update including proposed 'gvfs' packages.

I have additionally installed:

1. nautilus-open-terminal
2. nautilus-actions with just 'wipe-selected'

ProblemType: Crash
Architecture: amd64
Date: Fri Aug 1 11:33:44 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.22.3-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: nautilus --no-default-window --sm-client-id default2
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 gconf_client_remove_dir ()
 ?? ()
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in gconf_client_remove_dir()
Uname: Linux 2.6.24-19-generic x86_64
UserGroups: adm admin audio cdrom dip floppy fuse lpadmin plugdev uml-net vboxusers video

Revision history for this message
ingo (ingo-steiner) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in nautilus:
importance: Undecided → Medium
status: New → Invalid
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.