nautilus assert failure: *** glibc detected *** nautilus: double free or corruption

Bug #420841 reported by royden
630
This bug affects 120 people
Affects Status Importance Assigned to Milestone
Brasero
Fix Released
Critical
brasero (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

gksudo nautilus leads to apport crash report.

1) Ubuntu Karmic updated

2) Nautilus 1:2.27.91-0ubuntu1

3) nautilus should run with root privelages

4) crash

ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** nautilus: double free or corruption (fasttop): 0x08499d30 ***
CrashCounter: 1
Date: Sat Aug 29 02:05:52 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: libbrasero-media0 2.27.91-0ubuntu1
ProcCmdline: nautilus
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
Signal: 6
SourcePackage: brasero
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: nautilus assert failure: *** glibc detected *** nautilus: double free or corruption (fasttop): 0x08499d30 ***
Uname: Linux 2.6.31-8-generic i686
UserGroups: dialout uucp

Revision history for this message
royden (ryts) wrote :
visibility: private → public
affects: nautilus (Ubuntu) → brasero (Ubuntu)
Changed in brasero (Ubuntu):
status: New → Confirmed
Revision history for this message
Nelson Álvarez Sáez (alvareznelson) wrote :

I get this message when I try to open Nautilus with root privileges in Karmic:

nelson@nechus:~$ sudo nautilus
** Message: Initializing gksu extension...

** (nautilus:4275): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:4275): WARNING **: No marshaller for signature of signal 'DownloadFinished'
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x01 0x00 0x00 0x00 0x00 0x00
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Fallo de segmentación (core dumped)
nelson@nechus:~$

So I opened the following thread at ubuntuforums:
http://ubuntuforums.org/showthread.php?p=7863897#post7863897

Eventually, I solved this problem thanks to corncob's suggestion to type "sudo su" to change to the root prompt and then typing "nautilus".

Revision history for this message
Daniel Letzeisen (dtl131) wrote :

I restarted my system and ran 'gksudo nautilus'. It ran fine once, but after closing it and trying again, I also get a segfault. Backtrace attached
Also, note that the sudo su, nautilus method also produces a craah.

affects: brasero (Ubuntu) → nautilus (Ubuntu)
Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

This seems to have something to do with libnautilus-brasero-extension.

Possibly related:

Bug #420093
Bug #419565
Bug #419092

Changed in nautilus (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__kernel_vsyscall ()
raise () from /lib/tls/i686/cmov/libc.so.6
abort () from /lib/tls/i686/cmov/libc.so.6
?? () from /lib/tls/i686/cmov/libc.so.6
?? () from /lib/tls/i686/cmov/libc.so.6

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: removed: need-i386-retrace
Revision history for this message
Nelson Álvarez Sáez (alvareznelson) wrote : Re: karmic nautilus fails to run as root

Typing sudo su and then nautilus worked only once. Now I get this output:

nelson@nechus:~$ sudo su
root@nechus:/home/nelson# nautilus

(nautilus:10239): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(nautilus:10239): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
root@nechus:/home/nelson#

Revision history for this message
exploder91 (d-cosner) wrote :

Same issue here. The suggested commands are not working.

Revision history for this message
Karl.Mo (partyboi2) wrote :

I am also having the same problem with Karmic, but the workaround mentioned is not working. Here is the output for sudo su then nautilus.
karl@karl-desktop:~$ sudo su
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

root@karl-desktop:/home/karl# nautilus
Initializing nautilus-gdu extension

** (nautilus:6729): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:6729): WARNING **: No marshaller for signature of signal 'DownloadFinished'
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0x00
Segmentation fault (core dumped)
root@karl-desktop:/home/karl#

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

affects: nautilus (Ubuntu) → brasero (Ubuntu)
Changed in brasero (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

@ Chris:

From Bug #420093:

http://launchpadlibrarian.net/30961326/valgrind.log

valgrind log obtained by running:

G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gksu nautilus

Although, it might just be getting info on gksu, not what we really want to look at... Dropping to to root and running just Nautilus doesn't seem to reproduce the crash though...

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Andrew - thanks, but that only shows a problem in gksu. It doesn't show any issue in nautilus unfortunately.

Revision history for this message
Daniel Letzeisen (dtl131) wrote :

Chris, was there something wrong with my backtrace in comment #3?

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Yes, it's of a completely separate crash.

Revision history for this message
Tuomas Aavikko (taavikko) wrote :

Will this backtrace suffice?

What measures you would recommend on debugging "gksudo nautilus" not working?

Revision history for this message
Erick Brunzell (lbsolost) wrote :

This certainly does seem to be related to brasero. If I downgrade to the Jaunty versions of both brasero and libbrasero-media0 that seems to solve the "nautilus as root" problem (both from cli and using the gui 'nautilus-gksu').

I must say however that it's not even a decent work-around because you must also downgrade to the Jaunty version of rhythmbox and it crashes on Karmic.

Just a heads up as far as having this assigned to brasero, maybe more specifically libbrasero-media0. I haven't tried to parse the differences between versions 2.27.91-0 and 2.26.0-0 (not sure what I'd be looking for anyway).

Revision history for this message
frustphil (frustphil) wrote :

It is.. Try look at this bug https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/422041.. It's the bug I reported but I don't know how to do the valgrind thing.. I tried but it doesn't seem to work...

Revision history for this message
Berkeley Churchill (berkeleychurchill) wrote :

I've got the same problem (I mistakenly reported a duplicate #424714)
I'm guessing it won't shine much light on the situation, but here's what I got:

berkeley@be-just:~$ sudo nautilus
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x01 0x00 0x00 0x00 0x00 0x00
Segmentation fault (core dumped)

berkeley@be-just:~$ sudo su
root@be-just:/home/berkeley# nautilus
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x01 0x00 0x00 0x00 0x00 0x00
Segmentation fault (core dumped)

Other Information:

berkeley@be-just:~$ lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10

berkeley@be-just:~$ apt-cache policy nautilus
nautilus:
  Installed: 1:2.27.91-0ubuntu3
  Candidate: 1:2.27.91-0ubuntu3
  Version table:
 *** 1:2.27.91-0ubuntu3 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

berkeley@be-just:~$ groups
berkeley adm dialout cdrom audio plugdev lpadmin ssh netdev admin sambashare usb

the end of /var/log/syslog:

Sep 4 23:53:43 be-just gnome-session[7752]: WARNING: Could not launch application 'nm-applet.desktop': Unable to start application: Failed to execute child process "nm-applet" (No such file or directory)
Sep 4 23:53:51 be-just kernel: [ 2729.631160] nautilus[8017] general protection ip:7f3b86582e78 sp:7fff81c6e720 error:0 in libc-2.10.1.so[7f3b8650d000+166000]
Sep 4 23:56:48 be-just kernel: [ 2907.164475] nautilus[8253]: segfault at 7fc846647260 ip 00007fc843a25e60 sp 00007fff8280e860 error 4 in libc-2.10.1.so[7fc8439b0000+166000]
Sep 4 23:58:32 be-just kernel: [ 3010.722678] nautilus[8324]: segfault at 66697479 ip 00007f78b35c2336 sp 00007fff657b7b10 error 4 in libc-2.10.1.so[7f78b354a000+166000]

Revision history for this message
cheesypoof (cheesypoof-deactivatedaccount) wrote :

Chris, is this the type of log you need for the bug? By the way, sudonautilus is simply a script that contains "sudo nautilus". My apologies in advance if this is not what you need, as I don't usually participate past describing bugs I have experienced. :-)

Revision history for this message
bapoumba (bapoumba) wrote :

~$ G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gksudo nautilus
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0e 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0x00

** (nautilus:6728): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:6728): WARNING **: No marshaller for signature of signal 'DownloadFinished'
Initializing nautilus-gdu extension

uname -a
Linux phoenix 2.6.31-9-generic #29-Ubuntu SMP Sun Aug 30 17:39:23 UTC 2009 i686 GNU/Linux

Revision history for this message
bapoumba (bapoumba) wrote :

Sorry, forgot:

~$ sudo -s
root@phoenix:~# nautilus
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0e 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0x00

** (nautilus:6789): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:6789): WARNING **: No marshaller for signature of signal 'DownloadFinished'
Initializing nautilus-gdu extension
Segmentation fault (core dumped)

summary: - karmic nautilus fails to run as root
+ nautilus assert failure: *** glibc detected *** nautilus: double free or
+ corruption
Revision history for this message
Pedro Villavicencio (pedro) wrote :

In the meantime I've sent this report at https://bugzilla.gnome.org/show_bug.cgi?id=594914 ; could somebody get a valgrind log and attach it to the report or send it upstream? Thanks in advance.

Revision history for this message
Delan Azabani (azabani) wrote :

AFAIK, it affects nautilus, not brasero.

affects: brasero (Ubuntu) → nautilus (Ubuntu)
Revision history for this message
Delan Azabani (azabani) wrote :

(Changed the affected package listing)

Here's my output, similar to others, when running on a terminal:

Initializing nautilus-dropbox 0.6.1

** (nautilus:8033): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:8033): WARNING **: No marshaller for signature of signal 'DownloadFinished'
Initializing nautilus-gdu extension
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x01 0x00 0x00 0x00 0x00 0x00
Segmentation fault (core dumped)

Revision history for this message
BuM (bumaw) wrote :

sudo dbus-launch nautilus
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension

** (nautilus:10013): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:10013): WARNING **: No marshaller for signature of signal 'DownloadFinished'

** (process:10292): WARNING **: Couldn't change nice value of process.
ICC Profile CS 52474220
nautilus: jp2_dec.c:299: jp2_decode: Assertion `dec->image->cmprof_' failed.
Aborted

Revision history for this message
kylea (kylea) wrote :
Download full text (7.4 KiB)

2.6.31-10-generic #32-Ubuntu SMP Thu Sep 10 23:29:56 UTC 2009 x86_64 GNU/Linux
------------------
Description: Ubuntu karmic (development branch)
Release: 9.10

sudo su

root@kylea-laptop-910:/home/kylea/Desktop# nautilus

/usr/share/themes/exotic/gtk-2.0/gtkrc:89: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/usr/share/themes/exotic/gtk-2.0/gtkrc:90: Murrine configuration option "lightborder_ratio" will be deprecated in future releases. Please use "lightborder_shade" instead.
/usr/share/themes/exotic/gtk-2.0/gtkrc:156: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
Initializing nautilus-open-terminal extension
Initializing nautilus-gdu extension
Initializing nautilus-image-converter extension

** (nautilus:11917): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:11917): WARNING **: No marshaller for signature of signal 'DownloadFinished'
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x01 0x00 0x00 0x00 0x00 0x00
*** glibc detected *** nautilus: double free or corruption (fasttop): 0x00000000019c1630 ***
======= Backtrace: =========
/lib/libc.so.6[0x7fd7f7599d46]
/lib/libc.so.6(cfree+0x6c)[0x7fd7f759e67c]
/usr/lib/libgobject-2.0.so.0(g_object_newv+0x2ad)[0x7fd7f8ffb7cd]
/usr/lib/libgobject-2.0.so.0(g_object_new_valist+0x355)[0x7fd7f8ffc345]
/usr/lib/libgobject-2.0.so.0(g_object_new+0xcc)[0x7fd7f8ffc49c]
/usr/lib/libgstreamer-0.10.so.0[0x7fd7eb591d0c]
/usr/lib/libgstreamer-0.10.so.0(gst_registry_binary_read_cache+0x412)[0x7fd7eb593522]
/usr/lib/libgstreamer-0.10.so.0[0x7fd7eb528563]
/usr/lib/libgstreamer-0.10.so.0[0x7fd7eb52a1f8]
/usr/lib/libglib-2.0.so.0(g_option_context_parse+0x419)[0x7fd7f89296e9]
/usr/lib/libgstreamer-0.10.so.0(gst_init_check+0xed)[0x7fd7eb52993d]
/usr/lib/libbrasero-burn.so.0(brasero_burn_library_start+0x4d)[0x7fd7ec0745dd]
/usr/lib/nautilus/extensions-2.0/libnautilus-brasero-extension.so(nautilus_module_initialize+0x12)[0x7fd7ec2d43e2]
nautilus[0x4f2b86]
/usr/lib/libgobject-2.0.so.0(g_type_module_use+0x74)[0x7fd7f9018574]
nautilus[0x4f2c98]
nautilus[0x4338e3]
nautilus[0x443502]
/lib/libc.so.6(__libc_start_main+0xfd)[0x7fd7f7542abd]
nautilus[0x430149]
======= Memory map: ========
00400000-005ae000 r-xp 00000000 08:01 269494 /usr/bin/nautilus
007ae000-007b1000 r--p 001ae000 08:01 269494 /usr/bin/nautilus
007b1000-007b7000 rw-p 001b1000 08:01 269494 /usr/bin/nautilus
007b7000-007b8000 rw-p 00000000 00:00 0
018e2000-019ca000 rw-p 00000000 00:00 0 [heap]
7fd7e4000000-7fd7e4021000 rw-p 00000000 00:00 0
7fd7e4021000-7fd7e8000000 ---p 00000000 00:00 0
7fd7ea08e000-7fd7ea08f000 ---p 00000000 00:00 0
7fd7ea08f000-7fd7ea88f000 rw-p 00000000 00:00 0
7fd7ea88f000-7fd7ea890000 ---p 00000000 00:00 0
7fd7ea890000-7fd7eb090000 rw-p 00000000 00:00 0
7fd7eb090000-7fd7eb0dc000 r-xp 00000000 08:01 330428 /usr/lib/libgmime-2.4.so.2.4.6
7fd7eb0dc000-7fd7eb2dc000 ---p 0004c000 08:01 3304...

Read more...

affects: nautilus (Ubuntu) → brasero (Ubuntu)
Revision history for this message
Pedro Villavicencio (pedro) wrote :

I've managed to get a good valgrind log which i'm adding on the upstream bug now. Setting this to Triaged.

Changed in brasero (Ubuntu):
status: Incomplete → Triaged
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
Revision history for this message
Pedro Villavicencio (pedro) wrote :
Changed in brasero:
status: Unknown → New
Changed in brasero:
status: New → Invalid
Changed in brasero (Ubuntu):
status: Triaged → Fix Committed
status: Fix Committed → Triaged
Revision history for this message
mabawsa (mabawsa) wrote :

+1

sudo nautilus
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0x00
0:00:00.129403735 4115 0x17c4010 ERROR GST_INIT gst.c:901:ensure_current_registry_forking: child did not exit normally, terminated by signal

** (nautilus:4115): WARNING **: Failed to send buffer

** (nautilus:4115): WARNING **: Failed to send buffer

** (nautilus:4115): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:4115): WARNING **: No marshaller for signature of signal 'DownloadFinished'
** Message: Initializing gksu extension...

** (nautilus:4115): WARNING **: Failed to send buffer

** (nautilus:4115): WARNING **: Failed to send buffer

(nautilus:4115): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
Segmentation fault (core dumped)

Revision history for this message
mabawsa (mabawsa) wrote :

Strange thing is that the error keeps changing, and sometimes it works... (output from terminal below)

sudo nautilus
Sense key: 0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00 0x00
Initializing nautilus-open-terminal extension
Initializing nautilus-image-converter extension
Initializing nautilus-gdu extension

** (nautilus:4296): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:4296): WARNING **: No marshaller for signature of signal 'DownloadFinished'
** Message: Initializing gksu extension...
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.

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

the issue is fixed in 2.28 in karmic

Revision history for this message
royden (ryts) wrote :

gksudo Nautilus (and for that matter "sudo nautilus") work on my setup.

Revision history for this message
chet (chet-0x-henry) wrote :

gksudo nautilus now works for me as well but on exit it still segfaults

Revision history for this message
Delan Azabani (azabani) wrote :

#31 (Sebastian): if the latest is 2.28, (and mine's 2.27.91), why aren't I getting it thorough update-manager?

Revision history for this message
Saivann Carignan (oxmosys) wrote :

This is fixed with latest nautilus (1:2.28.0-0ubuntu2) and latest brasero (2.28.0-0ubuntu1) in Karmic, so I guess that the status could be set to fix released

Changed in brasero (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
dino99 (9d9) wrote :

My system is daily updated & this warning is still there with nautilus (1:2.28.0-0ubuntu2):

(nautilus:2844): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:2844): WARNING **: No marshaller for signature of signal 'DownloadFinished'
** Message: Initializing gksu extension...
Initializing nautilus-gdu extension

Changed in brasero:
importance: Unknown → Critical
status: Invalid → Fix Released
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Nautilus crash... raring
ii nautilus 1:3.6.3-0ubuntu5

tags: added: raring
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Crash nautilus

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
To post a comment you must log in.