nautilus crashed with SIGSEGV in g_main_context_dispatch()

Bug #821342 reported by Lukasz Olszewski
This bug affects 277 people
Affects Status Importance Assigned to Milestone
Nautilus
Expired
Critical
nautilus (Ubuntu)
Invalid
Medium
Unassigned
Oneiric
Won't Fix
Medium
Unassigned

Bug Description

Nautilus crashes occasionally during normal use ( difficult to reproduce ).

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CrashCounter: 1
Date: Fri Aug 5 10:28:51 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: nautilus -n
ProcEnviron:
 LANG=pl_PL.UTF-8
 SHELL=/usr/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x4bff0e: mov 0x390(%rax),%rdi
 PC (0x004bff0e) ok
 source "0x390(%rax)" (0xaaaaaaaaaaaaae3a) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to oneiric on 2011-08-03 (2 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Lukasz Olszewski (olszewskil) wrote :
visibility: private → public
Changed in nautilus (Ubuntu):
status: New → Confirmed
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 nautilus_icon_container_unfreeze_updates (container=0x327f400) at nautilus-icon-container.c:6853
 end_renaming_mode (container=0x327f400, commit=1) at nautilus-icon-container.c:8387
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed
Download full text (8.5 KiB)

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1 version 1:4.6.1-5ubuntu2 required, but 1:4.6.1-7ubuntu2 is available
outdated debug symbol package for libavahi-common3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
libglapi-mesa version 7.11~1-0ubuntu4 required, but 7.11-0ubuntu3 is available
outdated debug symbol package for libslang2: package version 2.2.4-2ubuntu1 dbgsym version 2.2.2-4ubuntu2
outdated debug symbol package for libtiff4: package version 3.9.5-1ubuntu1 dbgsym version 3.9.4-5ubuntu6
util-linux version 2.19.1-2ubuntu2 required, but 2.19.1-2ubuntu3 is available
libx11-xcb1 version 2:1.4.3-2ubuntu1 required, but 2:1.4.4-1ubuntu1 is available
fontconfig version 2.8.0-3ubuntu1 required, but 2.8.0-3ubuntu2 is available
outdated debug symbol package for libgdu0: package version 3.0.2-1ubuntu1 dbgsym version 2.32.1-0ubuntu4
libpam-modules version 1.1.3-1ubuntu3 required, but 1.1.3-2ubuntu1 is available
libjpeg62 version 6b1-1ubuntu1 required, but 6b1-1ubuntu2 is available
libgtk-3-common version 3.1.10-0ubuntu2 required, but 3.1.12-0ubuntu1 is available
libpam0g version 1.1.3-1ubuntu3 required, but 1.1.3-2ubuntu1 is available
outdated debug symbol package for dbus: package version 1.4.12-4ubuntu2 dbgsym version 1.4.6-1ubuntu6.1
dmsetup version 2:1.02.48-4ubuntu2 required, but 2:1.02.48-4ubuntu3 is available
outdated debug symbol package for busybox-initramfs: package version 1:1.18.4-2ubuntu1 dbgsym version 1:1.17.1-10ubuntu1
libfontconfig1 version 2.8.0-3ubuntu1 required, but 2.8.0-3ubuntu2 is available
libpam-modules-bin version 1.1.3-1ubuntu3 required, but 1.1.3-2ubuntu1 is available
outdated debug symbol package for libk5crypto3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
libpng12-0 version 1.2.44-2ubuntu1 required, but 1.2.46-3ubuntu1 is available
libudev0 version 172-0ubuntu5 required, but 173-0ubuntu3 is available
udev version 172-0ubuntu5 required, but 173-0ubuntu3 is available
outdated debug symbol package for libavahi-client3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for udisks: package version 1.0.3-1 dbgsym version 1.0.2-4ubuntu2
libgail-3-0 version 3.1.10-0ubuntu2 required, but 3.1.12-0ubuntu1 is available
libnotify4 version 0.7.3-1 required, but 0.7.3-2 is available
outdated debug symbol package for passwd: package version 1:4.1.4.2+svn3283-3ubuntu2 dbgsym version 1:4.1.4.2+svn3283-3ubuntu1
outdated debug symbol package for libkrb5-3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
libmount1 version 2.19.1-2ubuntu2 required, but 2.19.1-2ubuntu3 is available
outdated debug symbol package for libdatrie1: package version 0.2.4-3 dbgsym version 0.2.4-1
nautilus-data version 1:3.1.4-0ubuntu2 required, but 1:3.1.4-0ubuntu3 is available
outdated debug symbol package for liblaunchpad-integration-3.0-1: package version 0.1.54 dbgsym version 0.1.51
libxv1 version 2:1.0....

Read more...

tags: removed: need-amd64-retrace
Revision history for this message
Ronnie (ronnie.vd.c) wrote :

Got the same error after changing the .config/user-dirs.dirs file to a mounted disk

Revision history for this message
Ray Boyer (raybo) wrote :

Getting the same error on fresh install (today) with all available updates.

Revision history for this message
Keith Allcock (keith-allcock) wrote :

Just had this crash after closing nautilus after browsing connected phone media.. no other difference from other usage of nautilus which performed ok

Changed in nautilus (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Felix (apoapo) wrote :

Crashed after an update today. Could not see any direct relation to anything.

Revision history for this message
Callum Williams (thegooball) wrote :

Two seconds after everything has loaded on my 11.10 desktop it crashes every single time without fail.
Also it crashes when I switch user and then log back in.
At least it's consistent :)

Revision history for this message
Lukasz Olszewski (olszewskil) wrote :

Given this bug may affect large number of users and it sometimes may cause files being lost (if it crashes during mv as it happened to me) I think the importance level should be changed to High.

Changed in nautilus:
importance: Unknown → High
status: Unknown → New
Revision history for this message
lostprophet (matze-spam1) wrote :

had the same after closing nautilus. before i noticed that copy, cut and paste via strg + c x v didn't work, it was just working with right clicks...

Revision history for this message
Lukasz Olszewski (olszewskil) wrote :

The "ctrl+v" pasting problem is reported as a separate bug report (you can mark it as affecting you) : https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/827921

Revision history for this message
Lukasz Olszewski (olszewskil) wrote :

Callum if you experience these crashes on every boot can you provide a better backtrace as described here: https://wiki.ubuntu.com/Backtrace
This could really help working on this issue upstream. Thanks!

Changed in nautilus:
importance: High → Critical
status: New → Incomplete
Revision history for this message
Callum Williams (thegooball) wrote :

I'll do it as soon as I have a chance (today or tomorrow)

Revision history for this message
Callum Williams (thegooball) wrote :

Well this is good... I started up my laptop to read the backtrace page and set it up and nautilus didn't crash. I have restarted my laptop several times and it won't crash. Oh the irony :)
Can I set up the backtrace to run all the time for nautilus? Just in case it starts crashing again?

Revision history for this message
Lê Hoàng Phương (herophuong93) wrote :

Just open /usr/share/lib and change from the icon view to list view. IT CRASH.
In general, when changing from icon view to list view in a folder which have a lot of items (like in lib folder), nautilus always crashes (fortunately, next time open that folder, nautilus still save its view status so I don't have to change view again.)

Revision history for this message
Lukasz Olszewski (olszewskil) wrote : Re: [Bug 821342] Re: nautilus crashed with SIGSEGV in g_main_context_dispatch()

Yes, you can attach to the already running process or just kill nautilus
and start it in gdb as described on https://wiki.ubuntu.com/Backtrace
This way you can run it all the time witch gdb, however I was also not
able to reproduce this bug for 3 days now so maybe it's gone :?

Revision history for this message
Lukasz Olszewski (olszewskil) wrote :

herophuong93: you're right there but this is caused by a different bug (
bug 804133 )

Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :

This just happened to me shortly after I opened a tab in Nautilus to view some system folders, then switched back to Firefox.

Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :

What do you know, just happened again to me under similar circumstances. Maybe this is reproducible for me?

Also, could bug #849473 be a duplicate of this? It's not marked as such, but it's the first thing to come up when I do a Google search for the bug title.

Revision history for this message
Lukasz Olszewski (olszewskil) wrote :

WarriorIng64, if you can reproduce it then please install the nautilus-dbg package and follow the steps described on ubuntu wiki page: https://wiki.ubuntu.com/Backtrace
Please note that you can attach to the already running nautilus process and work normally until this bug reoccurs. At this step it is crucial to get a good backtrace of this one so your help will be very much appreciated.

Changed in nautilus (Ubuntu):
importance: Medium → High
tags: added: rls-mgr-o-tracking
Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :

Lukasz, not sure now if I can do that. After this morning's updates 3D stopped working entirely for me, and unfortunately it was Unity 3D's Alt+Tab that I was often using to trigger the crash. I am having trouble getting Unity 2D to do the same. Or maybe I was just (un)lucky before.

Nevertheless, I did get the nautilus-dbg package and I will be running nautilus from gdb from here on out, just in case.

Revision history for this message
Martin Pitt (pitti) wrote :

Not a lot of duplicates, not reproducible. Lowering importance.

Changed in nautilus (Ubuntu Oneiric):
importance: High → Medium
status: Confirmed → Won't Fix
tags: removed: rls-mgr-o-tracking
Revision history for this message
wavded (wavded) wrote :

I was able to cause this bug to happen by:

1. Connect to two remote servers (I used the Extra Pane F3 to seperate them)
2. Copy files from one to the other.
3. While the 'File Operations' dialog is working close the main nautilus window.
4. File Operations closes shortly after and got this crash report.

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

Thanks, Pedro could you check if the steps described lead to a bug?

Changed in nautilus (Ubuntu):
assignee: nobody → Pedro Villavicencio (pvillavi)
Revision history for this message
Pedro Villavicencio (pedro) wrote :

I'm not able to recreate the problem with the steps previously described, I've create two SSH connections to different machines and try to recreate the issue with no positive results, also did a mix of SSH/FTP and the issue was not present on any of those tests, do you have any other steps in order to reproduce it? Can you get a backtrace for us ? Thanks.

Changed in nautilus (Ubuntu):
assignee: Pedro Villavicencio (pvillavi) → nobody
status: Confirmed → Incomplete
Revision history for this message
Ant Dickens (antonydickens) wrote :

Occurred on removal of a usb pendrive. Couldn't reproduce crash though.

Revision history for this message
Vladimir Scherbaev (zemik) wrote :

want fix?!

Revision history for this message
Lotd (jonaskerwin) wrote :

Happend for me after doing sudo apt-get install nautilus-open-terminal then sudo nautilus -q and then trying to open nautilus thru the icon in Unity.

Revision history for this message
Joshua Lückers (joshualuckers) wrote :

I have seen this happen when I was doing some activities in a folder with PDF's in it. A few PDF's seemed to have a thumbnail rendered and a few others not. After closing Nautilus I got the crash report.

Revision history for this message
Pranesh Prakash (the-solipsist) wrote :

Sebastian, and all:
For me Nautilus crashes whenever I go to particular folders, so is reproducible that way.

One of those folders has files with the following extensions:
html
pdf
xls
txt
doc
odt
zip

txt~
html~

and two sub-folders. Let me know if I can help in testing the bug in any other way.

Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :

Pranesh, if you are able to consistently reproduce these crashes (I haven't been able to do so for a while now, despite my best efforts), if you could kindly look at comment #22 above and get us a backtrace with nautilus-dbg installed, I imagine that would still be VERY helpful.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Crash seems to happen in different ways for the reporters if you can reproduce it easily may you please write some easy steps to reproduce the issue ? Thanks.

Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :

Well, just got a crash while gdb was attached! Followed the steps at https://wiki.ubuntu.com/Backtrace to produce the following output, as requested. (The crash itself occurred just after I did a whole bunch of random stuff involving searching for files and switching tabs.)

Changed in nautilus (Ubuntu):
status: Incomplete → Confirmed
Changed in nautilus (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Matthias Niess (mniess) wrote :

nautilus is constantly crashing on me. fresh install on a samsung n130 netbook. Do you have enough information on this bug or should I do a backtrace?

Revision history for this message
soundlessthj (soundless-thj) wrote :
Download full text (4.8 KiB)

The core dump appears almost every time I list files under my home, the Ubuntu version is 11.04, here is a stack trace.

- snip -

Core was generated by `nautilus'.
Program terminated with signal 11, Segmentation fault.
#0 0x00941fc2 in g_type_check_instance_cast (type_instance=0x20, iface_type=141471128)
    at /build/buildd/glib2.0-2.28.6/./gobject/gtype.c:3989
3989 /build/buildd/glib2.0-2.28.6/./gobject/gtype.c: No such file or directory.
 in /build/buildd/glib2.0-2.28.6/./gobject/gtype.c
(gdb) where
#0 0x00941fc2 in g_type_check_instance_cast (type_instance=0x20, iface_type=141471128)
    at /build/buildd/glib2.0-2.28.6/./gobject/gtype.c:3989
#1 0x080b1add in nautilus_window_close_pane (pane=0x879c878) at nautilus-window.c:845
#2 0x00b311a9 in g_list_foreach (list=<value optimized out>, func=0x80b19a0 <nautilus_window_close_pane>, user_data=0x0)
    at /build/buildd/glib2.0-2.28.6/./glib/glist.c:938
#3 0x080b0590 in nautilus_window_destroy (object=0x8736008) at nautilus-window.c:648
#4 0x0093748c in g_cclosure_marshal_VOID__VOID (closure=0x86cf868, return_value=0x0, n_param_values=1,
    param_values=0x8933368, invocation_hint=0xbffcb8b0, marshal_data=0x80a3300)
    at /build/buildd/glib2.0-2.28.6/./gobject/gmarshal.c:79
#5 0x00919cc7 in g_type_class_meta_marshal (closure=0x86cf868, return_value=0x0, n_param_values=1, param_values=0x8933368,
    invocation_hint=0xbffcb8b0, marshal_data=0x4c) at /build/buildd/glib2.0-2.28.6/./gobject/gclosure.c:878
#6 0x0091b372 in g_closure_invoke (closure=0x86cf868, return_value=0x0, n_param_values=1, param_values=0x8933368,
    invocation_hint=0xbffcb8b0) at /build/buildd/glib2.0-2.28.6/./gobject/gclosure.c:767
#7 0x0092da49 in signal_emit_unlocked_R (node=0x86ccf38, detail=0, instance=0x8736008, emission_return=0x0,
    instance_and_params=0x8933368) at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c:3368
#8 0x00936b29 in g_signal_emit_valist (instance=0x8736008, signal_id=11, detail=0,
    var_args=0xbffcba6c "j\235", <incomplete sequence \354>) at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c:2983
#9 0x00936cc2 in g_signal_emit (instance=0x8736008, signal_id=11, detail=0)
    at /build/buildd/glib2.0-2.28.6/./gobject/gsignal.c:3040
#10 0x00dbb2c1 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x00ecd324 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x00ed8346 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x0091ebff in g_object_run_dispose (object=0x8736008) at /build/buildd/glib2.0-2.28.6/./gobject/gobject.c:945
#14 0x00dbbe7e in gtk_object_destroy () from /usr/lib/libgtk-x11-2.0.so.0
#15 0x0808134a in nautilus_main_event_loop_quit (explicit=1) at nautilus-main.c:154
#16 0x0093748c in g_cclosure_marshal_VOID__VOID (closure=0x8719300, return_value=0x0, n_param_values=1,
    param_values=0x8a39498, invocation_hint=0xbffcbc50, marshal_data=0x0)
    at /build/buildd/glib2.0-2.28.6/./gobject/gmarshal.c:79
#17 0x0091b372 in g_closure_invoke (closure=0x8719300, return_value=0x0, n_param_values=1, param_values=0x8a39498,
    invocation_hint=0xbffcbc50) at /build/buildd/glib2.0-2.28.6/./gobject/gclosure.c:767
#18 0x0092e048 in signal_emit_unlocked_R (node=0x86f72e8, detail=0, instance...

Read more...

Changed in nautilus:
status: Incomplete → New
Changed in nautilus:
status: New → Expired
Revision history for this message
dino99 (9d9) wrote :

This version has expired

Changed in nautilus (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.