Bug 389083 – Nautilus crash when Gnome is starting

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 389083 - Nautilus crash when Gnome is starting


Summary:	Nautilus crash when Gnome is starting


Status:	RESOLVED DUPLICATE of bug 364396

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-24 01:19 UTC by jg
Modified:	2007-01-03 20:28 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description jg 2006-12-24 01:19:20 UTC

What were you doing when the application crashed?
After chaning my theme and getting the crash (see other bug report which someone has added a stack trace blocker on) I log back in and get this crash. Then I get a popup saying:

 "There was an error starting the GNOME Settings Daemon.

Some things, such as themes, sounds, or background settings may not work correctly.

The Settings Daemon restarted too many times.

GNOME will still try to restart the Settings Daemon next time you log in."  [X Close]




Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 52883456 vsize: 0 resident: 52883456 share: 0 rss: 14110720 rss_rlim: 0
CPU usage: start_time: 1166922906 rtime: 0 utime: 76 stime: 0 cutime:74 cstime: 0 timeout: 2 it_real_value: 0 frequency: 9

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226709328 (LWP 7541)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 96591

Thread 1 (Thread -1226709328 (LWP 7541))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 gdk_event_apply_filters
at gdkevents-x11.c line 345
#6 gdk_event_translate
at gdkevents-x11.c line 894
#7 _gdk_events_queue
at gdkevents-x11.c line 2254
#8 gdk_event_dispatch
at gdkevents-x11.c line 2314
#9 IA__g_main_context_dispatch
at gmain.c line 2045
#10 g_main_context_iterate
at gmain.c line 2677
#11 IA__g_main_loop_run
at gmain.c line 2881
#12 IA__gtk_main
at gtkmain.c line 1024
#13 POA_Nautilus_MetafileMonitor__init
#14 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#15 ??
#0 __kernel_vsyscall

Comment 1 jg 2006-12-24 01:24:56 UTC

Not sure why the bug wizard set the subject to "crash in CD/DVD Creator: After chaning my theme a..." I didnt write that. Maybe the system garbled the beginning? it looks similar to my report.

This crashed while entering Gnome.

After changing my theme and getting the crash (see other bug report which someone has added a stack trace blocker on) I log back in and get this crash. Then I get a popup saying:

 "There was an error starting the GNOME Settings Daemon.

Some things, such as themes, sounds, or background settings may not work correctly.

The Settings Daemon restarted too many times.

GNOME will still try to restart the Settings Daemon next time you log in."  [X Close]

Cheers
Jon

Comment 2 jg 2006-12-24 01:36:39 UTC

I've updated the subject of this bug, as I have 3 stack trace all crashing at the same function from different applications (/usr/bin/gnome-power-manager, /usr/bin/gnome-panel etc). 

e.g.

Memory status: size: 46804992 vsize: 0 resident: 46804992 share: 0 rss: 13799424 rss_rlim: 0
CPU usage: start_time: 1166922906 rtime: 0 utime: 70 stime: 0 cutime:65 cstime: 0 timeout: 5 it_real_value: 0 frequency: 8

Backtrace was generated from '/usr/bin/gnome-panel'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225271632 (LWP 7539)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 96593

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
#5 gdk_event_apply_filters
at gdkevents-x11.c line 345
#6 gdk_event_translate
at gdkevents-x11.c line 894
#7 _gdk_events_queue
at gdkevents-x11.c line 2254
#8 gdk_event_dispatch
at gdkevents-x11.c line 2314
#9 IA__g_main_context_dispatch
at gmain.c line 2045
#10 g_main_context_iterate
at gmain.c line 2677
#11 IA__g_main_loop_run
at gmain.c line 2881
#12 IA__gtk_main
at gtkmain.c line 1024
#13 main
at main.c line 95

Comment 3 Christian Persch 2006-12-24 20:07:50 UTC

This has nothing to do with gnome_gtk_module_info_get which is just a libgnomeui symbol that appears in place of the signal handler; the real trace starts at #4.

Re-assigning to nautilus; but might be a gtk problem.

Comment 4 André Klapper 2007-01-03 20:28:02 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 364396 ***