GNOME Bugzilla – Bug 87071
Nautilus crashes when sleecting a new theme
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: major Version: 2.0.0 Synopsis: Nautilus crashes when sleecting a new theme Bugzilla-Product: nautilus Bugzilla-Component: Preferences BugBuddy-GnomeVersion: 2.0 (2.0.1) Description: Description of Problem: Selecting a new theme from the Preferences dialog crashes Nautilus. Steps to reproduce the problem: 1. Open Preferences 2. Select any theme 3. Watch Nautilus crash Actual Results: Nautilus go bye-bye Expected Results: A new theme being applied. How often does this happen? Every time I decide I'm tired of the default and try changing it. Additional Information: This seems worse after building from the Debian source package. The previous Garnome package crashed about every other time I tried to change themes, but sometimes it worked. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 1024 (LWP 31362)] [New Thread 2049 (LWP 31363)] [New Thread 1026 (LWP 31364)] [New Thread 2051 (LWP 31365)] [New Thread 3076 (LWP 31366)] [New Thread 4101 (LWP 31367)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x71089f24 in wait4 () from /lib/libc.so.6
+ Trace 24574
Thread 6 (Thread 4101 (LWP 31367))
Thread 5 (Thread 3076 (LWP 31366))
Thread 4 (Thread 2051 (LWP 31365))
Thread 3 (Thread 1026 (LWP 31364))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-07-01 23:44 ------- The original reporter (trick@adonis.net) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Is this bug 84693, guys? [This is likely a dup of a bug marked a dup of that one, but... doesn't really look like it.]
_gtk_tree_view_queue_draw_node() doesn't call gtk_tree_view_set_reorderable(), and that doesn't call _gtk_tree_selection_internal_select_node(). So the stack trace looks pretty messed up. So it is difficult to spot the exact cause (and it works OK for me). I think it is probably the same as bug 85399. I'll mark as a dup, but reopen if you still see it in the next release of nautilus (with a better trace if possible!). *** This bug has been marked as a duplicate of 85399 ***