nautilus crashed with SIGSEGV in gconf_client_remove_dir()

StacktraceTop:gconf_client_remove_dir (client=0x77000009,
nautilus_actions_config_gconf_reader_finalize (object=0x81d2b80)
IA__g_object_unref (_object=0x81d2b80)
nautilus_actions_instance_dispose (obj=0x81d2b68) at nautilus-actions.c:178
IA__g_object_unref (_object=0x81d2b68)

thanks for your report, that's more like a nautilus-actions issue, re assigning. Also known upstream you can track it here: http://bugzilla.gnome.org/show_bug.cgi?id=496332

Occurred while installing lots of software and then using sudo nautilus at the same time

Using Hardy fully updated/upgraded

Same here...

Same here, up-to-date hardy.

Occurred every time when I start nautilus with "gksudo nautilus" do what I need to do, and close it. Then it happends.

i have amd64
Just started a new session and had the crash report to do...Nothing seems to be broken... also.

I confirm it. Here it occurred when upgrading language packs.

Confirmed here as well on up-to-date Hardy Beta...

Occurs every boot on Hardy Beta

Occurs at right after boot and at random on up-to-date hardy beta

confirming. i have the same issue.

Also experiencing.

It just happened to me today after a reboot.
Hardy 8.04
Nautilus 1:2.22.2-0ubuntu6
Linux 2.6.24-17-generic x86_64

happen also here !!! please fix

Still happens after today's (2008-08-01) major 'proposed' GNOME-update on Hardy 8.04.1
Please fix asap.

Just got this on logging in.

Using up-to-date 8.10.

Nautilus ver: 1:2.23.6.1-0ubuntu1

this happens in intrepid as well when your root nautilus

thomas@thomas-laptop:~$ lsb_release -rd ; uname -a ; apt-cache policy linux-headers-2.6.27-2-generic linux-image-2.6.27-2-generic linux linux-source-2.6.27 linux-restricted-modules nautilus
Description: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 GNU/Linux
linux-headers-2.6.27-2-generic:
  Installed: 2.6.27-2.3
  Candidate: 2.6.27-2.3
  Version table:
 *** 2.6.27-2.3 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-image-2.6.27-2-generic:
  Installed: 2.6.27-2.3
  Candidate: 2.6.27-2.3
  Version table:
 *** 2.6.27-2.3 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux:
  Installed: 2.6.27.2.2
  Candidate: 2.6.27.2.2
  Version table:
 *** 2.6.27.2.2 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
linux-source-2.6.27:
  Installed: 2.6.27-2.3
  Candidate: 2.6.27-2.3
  Version table:
 *** 2.6.27-2.3 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-restricted-modules:
  Installed: 2.6.27.2.2
  Candidate: 2.6.27.2.2
  Version table:
 *** 2.6.27.2.2 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
nautilus:
  Installed: 1:2.23.91-0ubuntu1
  Candidate: 1:2.23.91-0ubuntu1
  Version table:
 *** 1:2.23.91-0ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
thomas@thomas-laptop:~$

I am getting this one frequently,

It seems to be related somehow with gvsf-trash crash:

Reported by tdflanders 4 hours ago (Activity log) (undecided) Bug 268825:

gvfsd-trash crashed with SIGSEGV in IA__g_main_context_dispatch()

The wastebin opens for no reason wile I am working in Nautilus. It happened twice today. I can only get it uploaded in minimal size. The full report is 1.6 MB. The other one was 3.2 MB.

thomas@thomas-laptop:/var$ lsb_release -rd ; uname -a ; apt-cache policy linux-headers-generic linux-image-generic linux linux-source-2.6.27 linux-restricted-modules synaptic apport-gtk nautilus gvfs
Description: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.27-3-generic #1 SMP Wed Sep 10 16:02:00 UTC 2008 i686 GNU/Linux
linux-headers-generic:
  Installed: 2.6.27.2.2
  Candidate: 2.6.27.2.2
  Version table:
 *** 2.6.27.2.2 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-image-generic:
  Installed: 2.6.27.2.2
  Candidate: 2.6.27.2.2
  Version table:
 *** 2.6.27.2.2 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux:
  Installed: 2.6.27.2.2
  Candidate: 2.6.27.2.2
  Version table:
 *** 2.6.27.2.2 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
linux-source-2.6.27:
  Installed: 2.6.27-3.4
  Candidate: 2.6.27-3.4
  Version table:
 *** 2.6.27-3.4 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
linux-restricted-modules:
  Installed: 2.6.27.2.2
  Candidate: 2.6.27.2.2
  Version table:
 *** 2.6.27.2.2 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status
synaptic:
  Installed: 0.62.1ubuntu8
  Candidate: 0.62.1ubuntu8
  Version table:
 *** 0.62.1ubuntu8 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
apport-gtk:
  Installed: 0.114
  Candidate: 0.114
  Version table:
 *** 0.114 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
nautilus:
  Installed: 1:2.23.92-0ubuntu1
  Candidate: 1:2.23.92-0ubuntu1
  Version table:
 *** 1:2.23.92-0ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
gvfs:
  Installed: 0.99.7.1-0ubuntu1
  Candidate: 0.99.7.1-0ubuntu1
  Version table:
 *** 0.99.7.1-0ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
thomas@thomas-laptop:/var$

I don't understand that this bug is always assigned to nautilus-actions:

Ubuntu-Hardy uses version 1.4.1-1ubuntu1
The same version in the Debian repository has no open bugs assigned to it, see here:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=nautilus-actions;dist=unstable

So it is either not nautilus-actions, or it is specific to Ubuntu.

Ingo

Fixed in Upstream svn.

Atl + F2 > gksudo nautilus > works fine! > closing nautilus > everthing is fine > crash report

I just repeated Daniel's procedure and got apport pop-up with the information filed as Bug #278021

So, seems the fix is not (yet) applied to Hardy?

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)

I just got this error today latest updates/all updates running latest intrepid

Got this today while logged in via FreeNX, latest updates.

On every login to the gnome-desktop I get the error. There appears another error-messoge-box, telling me, that nautilus can't find the bonobo-activation-server.
So everytime I have to kill bonobo manually and restart nautilus manually.

I got this error today for the first time. Occurred after downloading the latest updates for Ubuntu 8.10

I still get it on a dayly base and can easily predict when apport will pop up and report it:

When after logging in the icon for a nfs-mount on my desktop is displaced in a different position, it only takes minutes until apport reports the crash.

Hardy with all available an proposed fixes.

I am taking this out of 'Fix Committed': upstream has not yet published the fix. The problem has been identified, and it seems it was already fixed in SVN quite a long time ago, but the updated code has not yet been released. I am unsure why it was set upstream as 'RESOLVED/FIXED' *before* the availability of the fixed version.

All: this is still an issue. There is no need to state you still have it.

hum. nautilus-actions is correctly orphaned upstream.

I mean currently (not correctly) orphaned (in other words, unmaintained). Sorry.

if the problem had been fixed for some intermittend time as stated above, does that not mean it is not caused by nautilus-achtins and instead should be assigned to nautilus?

I confirm this bug on Intrepid.

@ingo: no, the issue is indeed in nautilus-actions. It was fixed in upstream SVN, but not yet released. Since the package is currently unmaintained, it may take a while for the fix to be made available. If you follow the upstream bug you will see the original maintainer/developer stating he does not have time to keep on, and asking for somebody else to take over).

If I have time, I will extract the fix for this issue and prepare a debdiff or a patch for us. Otherwise, anyone willing to do this is welcome to work on it. For the record, the fix seems to be in revision 480 in SVN.

unsubscribe

Happened to me after closing Nautilus that had been opened by right-clicking context menu and choosing "Open as administrator". Just a while after the window was closed, the "crash report" showed in. I'm using Hardy fully up-to-date.

Any problem since few weeks with nautilus, but I don't know why!

Good luck ;)

matiuzalem

On 06/11/2008, Volnei <email address hidden> wrote:
>
> Happened to me after closing Nautilus that had been opened by right-
> clicking context menu and choosing "Open as administrator". Just a while
> after the window was closed, the "crash report" showed in. I'm using
> Hardy fully up-to-date.
>
> --
> nautilus crashed with SIGSEGV in gconf_client_remove_dir()
> https://bugs.launchpad.net/bugs/182345
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Thank you for your reply.

I just get a lot of crash reports from nautilus... sometimes up to six in a
row. mostly when closing nautilus.

sincerely,
adrian

On Fri, Nov 7, 2008 at 12:03 AM, matiuzalem <email address hidden> wrote:

> Any problem since few weeks with nautilus, but I don't know why!
>
> Good luck ;)
>
> matiuzalem
>
>
> On 06/11/2008, Volnei <email address hidden> wrote:
> >
> > Happened to me after closing Nautilus that had been opened by right-
> > clicking context menu and choosing "Open as administrator". Just a while
> > after the window was closed, the "crash report" showed in. I'm using
> > Hardy fully up-to-date.
> >
> > --
> > nautilus crashed with SIGSEGV in gconf_client_remove_dir()
> > https://bugs.launchpad.net/bugs/182345
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> nautilus crashed with SIGSEGV in gconf_client_remove_dir()
> https://bugs.launchpad.net/bugs/182345
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Nautilus: Fix Released
> Status in "nautilus-actions" source package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: nautilus
>
> Just started a new session and had the crash report to do...Nothing seems
> to be broken...
>
> ProblemType: Crash
> Architecture: i386
> CrashCounter: 1
> Date: Sat Jan 12 13:35:29 2008
> DistroRelease: Ubuntu 8.04
> ExecutablePath: /usr/bin/nautilus
> NonfreeKernelModules: nvidia
> Package: nautilus 1:2.20.0-2ubuntu3
> PackageArchitecture: i386
> ProcCmdline: nautilus --no-default-window --sm-client-id default2
> ProcCwd: /home/fifi
> ProcEnviron:
> SHELL=/bin/bash
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=fr_FR.UTF-8
> 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 maverick 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008
> i686 GNU/Linux
> UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev
> powerdev sambashare scanner video
>

--
Adrian Immanuel Kieß (adrian at immanuelK.net)

happening to me a lot..
** (nautilus:7115): WARNING **: Unable to add monitor: Operation not supported
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSNautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.

Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.

--- Hash table keys for warning below:
--> file:///usr
--> file:///root
--> file:///usr/share
--> file:///

(nautilus:7115): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 4 elements at quit time (keys above)

(nautilus:7115): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 4 elements at quit time

[ 0.422053] ENABLING IO-APIC IRQs
[ 0.422227] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.461921] CPU0: Intel(R) Pentium(R) 4 CPU 2.60GHz stepping 09
[ 0.464029] Brought up 1 CPUs
[ 0.464029] Total of 1 processors activated (5186.98 BogoMIPS).
[ 0.464029] CPU0 attaching sched-domain:
[ 0.464029] domain 0: span 0 level CPU
[ 0.464029] groups: 0
[ 0.464029] net_namespace: 840 bytes
[ 0.464029] Booting paravirtualized kernel on bare hardware
[ 0.464029] Time: 9:32:35 Date: 12/14/08
[ 0.464029] NET: Registered protocol family 16
[ 0.464029] EISA bus registered
[ 0.464029] ACPI: bus type pci registered
[ 0.464029] PCI: PCI BIOS revision 2.10 entry at 0xfbb30, last bus=2
[ 0.464029] PCI: Using configuration type 1 for base access
[ 0.464029] ACPI: EC: Look up EC in DSDT
[ 0.491429] ACPI: Interpreter enabled
[ 0.491435] ACPI: (supports S0 S1 S3 S4 S5)
[ 0.491458] ACPI: Using IOAPIC for interrupt routing
[ 0.519353] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.519453] PCI: 0000:00:00.0 reg 10 32bit mmio: [e8000000, efffffff]
[ 0.519574] PCI: 0000:00:1d.0 reg 20 io port: [ff80, ff9f]
[ 0.519625] PCI: 0000:00:1d.1 reg 20 io port: [ff60, ff7f]
[ 0.519674] PCI: 0000:00:1d.2 reg 20 io port: [ff40, ff5f]
[ 0.519723] PCI: 0000:00:1d.3 reg 20 io port: [ff20, ff3f]
[ 0.519780] PCI: 0000:00:1d.7 reg 10 32bit mmio: [ffa80800, ffa80bff]
[ 0.519831] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 0.519837] pci 0000:00:1d.7: PME# disabled
[ 0.519910] pci 0000:00:1f.0: HPET at 0xfed00000
[ 0.519916] pci 0000:00:1f.0: quirk: region 0800-087f claimed by ICH4 ACPI/GPIO/TCO
[ 0.519921] pci 0000:00:1f.0: quirk: region 0880-08bf claimed by ICH4 GPIO
[ 0.519940] PCI: 0000:00:1f.1 reg 10 io port: [1f0, 1f7]
[ 0.519947] PCI: 0000:00:1f.1 reg 14 io port: [3f4, 3f7]
[ 0.519954] PCI: 0000:00:1f.1 reg 18 io port: [170, 177]
[ 0.519961] PCI: 0000:00:1f.1 reg 1c io port: [374, 377]
[ 0.519968] PCI: 00...

Hello,

This crash report happens often after closing Nautilus or on a new boot up. I never have any problems running Nautilus, and it never shuts down on me, I just keep getting crash reports periodically.

Later, Ray Parrish

The same happens to me: I can keep using Nautilus normally.
It hasn't happened again since a long ago, so I thing it's solved.

Bye

The same problem to me, i'm using ubuntu hardy 64 with a machine core 2 duo and nvidia card.

Keep the good work ubuntu Team.

Jaunty, restart after an update just now. Got a message that Nautilus crashed. Could open Nautilus normally.

Apport says: nautilus crashed with SIGSEGV in gconf_client_remove_dir()

Once more. At the beginning of a Gnome session, two hours ago also.

I get this crash after logging into jaunty.. every time.

Same for me, crash at start.

In my case (reported as https://bugs.launchpad.net/bugs/336737) this does not occur when Nautilus starts, but when I close a Nautilus which I have started from the command line. Pedro Villavicencio thought it was a duplicate of this bug (which it may very well be), so he closed my bug report.

Upgraded to Jaunty, after reboot I get this message. all is working fine.

Same here... I get this problem on every start... Ubuntu 9.04 beta

All

I got terrible problem when upgrading my Intrepid to Jaunty Beta, freeze in the midle and had to launch dpkg --configure and much more actions, but still, system slowed down after a couple of time, found nautilus was giving error SIGFAULT in dmesg related to libgconf2, spent whole day to find solution, in vain.
I noticed that many time during install, I got this warning: /sbin/ldconfig.real /usr/lib/lnspr4.so is not a symbolic link, something i never had before on Intrepid..
After tracing, I found two different condition as per attached images. Any clue to correct this situation? Reinstalling the package doesn't help, removing it, was very scary!

Taufik Hasan

--- On Sat, 3/28/09, Patrick Coutu <email address hidden> wrote:

From: Patrick Coutu <email address hidden>
Subject: [Bug 182345] Re: nautilus crashed with SIGSEGV in gconf_client_remove_dir()
To: <email address hidden>
Date: Saturday, March 28, 2009, 6:50 PM

Same here... I get this problem on every start... Ubuntu 9.04 beta

--
nautilus crashed with SIGSEGV in gconf_client_remove_dir()
https://bugs.launchpad.net/bugs/182345
You received this bug notification because you are a direct subscriber
of the bug.

I didn't have this error before. What I did most recently:

I moved my /home directory to a new separated partition (ext4) from the terminal (gdm stopped).

Afterwards I mounted the new /home, started gdm, logged into gnome and finally got the crash-report "nautilus crashed with SIGSEGV in gconf_client_remove_dir()".

I will try to reboot wiht the "old" /home in / and with the "new" home on the separated partition to see if it makes any difference.

I also have the issue in Jaunty Beta with a separate /home partition (ext4) and a / partition (ext4).
It doesn't happen all the time though, I don't know yet what causes it.

I tried a lot now and it doesn't make a difference if I have a separeted /home or not. Interesting thing is that for instance my mythfrontend doesn't work either. It quits with a segmention fault as well. https://bugs.launchpad.net/bugs/355220

I just wanted to mention: I did a clean fresh install of 9.04 from the desktop CD and and I did not have any error since then. So it seems to be related to upgrade's only - at least for me. Unfortunate, I am now unable to reproduce...

Hey there Tobias!

Sorry to pass a bad word, but I am having the problem with the fresh
install. I am not sure what caused it, and for me, it just pops up
occasionally.

On Tue, Apr 7, 2009 at 5:21 AM, Tobias Gross <email address hidden> wrote:

> I just wanted to mention: I did a clean fresh install of 9.04 from the
> desktop CD and and I did not have any error since then. So it seems to
> be related to upgrade's only - at least for me. Unfortunate, I am now
> unable to reproduce...
>
> --
> nautilus crashed with SIGSEGV in gconf_client_remove_dir()
> https://bugs.launchpad.net/bugs/182345
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Nautilus: Fix Released
> Status in “nautilus-actions” source package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: nautilus
>
> Just started a new session and had the crash report to do...Nothing seems
> to be broken...
>
> ProblemType: Crash
> Architecture: i386
> CrashCounter: 1
> Date: Sat Jan 12 13:35:29 2008
> DistroRelease: Ubuntu 8.04
> ExecutablePath: /usr/bin/nautilus
> NonfreeKernelModules: nvidia
> Package: nautilus 1:2.20.0-2ubuntu3
> PackageArchitecture: i386
> ProcCmdline: nautilus --no-default-window --sm-client-id default2
> ProcCwd: /home/fifi
> ProcEnviron:
> SHELL=/bin/bash
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=fr_FR.UTF-8
> 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 maverick 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008
> i686 GNU/Linux
> UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev
> powerdev sambashare scanner video
>

This bug was fixed in the package nautilus-actions - 1.4.1+svn521-0ubuntu1

---------------
nautilus-actions (1.4.1+svn521-0ubuntu1) jaunty; urgency=low

  * Take SVN version to fix SIGSEGV crash in
    gconf_client_remove_dir and autilus_actions_config_gconf_reader_finalize
    (LP: #182345, #271114)

 -- Didier Roche <email address hidden> Tue, 07 Apr 2009 17:10:19 +0200

And when will the fix be available in Hardy repository?

Please consider that this bug was reported first for Hardy since 1 year.

Here's how to request a backport:
https://help.ubuntu.com/community/UbuntuBackports#How%20to%20request%20new%20packages

done, see here:
https://bugs.launchpad.net/hardy-backports/+bug/357634

I will give it a shot next week after Jaunty RC.

I think this is more an update that is needed than a backport. So I closed the backport request and add targeted release there.

Hello,

Removing the nautilus-actions package eliminates this crash on start up, so the problem must reside within that package.

Later, Ray Parrish

The package already has been fixed, just those who are using [b]Hardy[/b] still have to wait for the backport - that's [b]Long Term[/b] (Support)

The patch is not trivial enough to be ported to hardy/intrepid.

Hopefully, next LTS is soon.
FYI, it's already fixed in jaunty and karmic.

> Hopefully, next LTS is soon.

It was opened for Hardy, why is it ignored. Hardy is LTS - does that mean 'Long Term Suffering'?
Do we have to open a new bug report to get that fixed?

Happens to me in Ibex when I switch between Compiz and Metacity

Thank you for reporting this bug to Ubuntu. Hardy reached EOL on May 9, 2013.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases