Ubuntu
nautilus-actions package

nautilus crashed with SIGSEGV in gconf_client_remove_dir()

Bug #278021 reported by ingo on 2008-10-04

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-actions (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: nautilus

reproducing the procedure as Daniel descibed in bug 182345 here

Hardy amd64

ProblemType: Crash
Architecture: amd64
Date: Sat Oct 4 11:45:23 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: nautilus 1:2.22.3-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: nautilus
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
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 audio cdrom dip fax floppy fuse lpadmin plugdev root scanner tape

Tags:

Revision history for this message

ingo (ingo-steiner) wrote on 2008-10-04:

Dependencies.txt Edit (5.9 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (38.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (695 bytes, text/plain; charset="utf-8")
Registers.txt Edit (1.0 KiB, text/plain; charset="utf-8")
Stacktrace.txt Edit (737 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.6 KiB, text/plain; charset="utf-8")

Revision history for this message

ingo (ingo-steiner) wrote on 2008-10-04:

Things are even worse:

when opening nautilus with 'gksudo' a device gets mounted, which is in /etc/fstab, but with 'noauto option'!

(/dev/sdb1 /media/sdb1 ext2 defaults,noatime,noauto 0 2)

Revision history for this message

Sebastien Bacher (seb128) wrote on 2008-10-04:

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find. Do you really think opening duplicates when you know that's a duplicate is an useful thing?

Changed in nautilus:
importance:	Undecided → Medium
status:	New → Invalid

Revision history for this message

cainmark (cainmark) wrote on 2008-10-08: Re: [Bug 278021] Re: nautilus crashed with SIGSEGV in gconf_client_remove_dir()

It crashes, asks for a report. I have no idea what caused it to crash. It
could be something competely different. There is absolutely no feedback
when I start to send the thing off that it is a duplicate, so how the heck
am I to know that?

On Sat, Oct 4, 2008 at 5:21 AM, Sebastien Bacher <email address hidden> wrote:

> *** This bug is a duplicate of bug 182345 ***
> https://bugs.launchpad.net/bugs/182345
>
> Thanks for the bug report. This particular bug has already been
> reported, but feel free to report any other bugs you find. Do you really
> think opening duplicates when you know that's a duplicate is an useful
> thing?
>
> ** Changed in: nautilus-actions (Ubuntu)
> Sourcepackagename: nautilus => nautilus-actions
> Importance: Undecided => Medium
> Status: New => Invalid
>
> ** This bug has been marked a duplicate of bug 182345
> nautilus crashed with SIGSEGV in gconf_client_remove_dir()
>
> --
> nautilus crashed with SIGSEGV in gconf_client_remove_dir()
> https://bugs.launchpad.net/bugs/278021
> You received this bug notification because you are a direct subscriber
> of the bug (via bug 182345).
>