GNOME Bugzilla – Bug 315704
new list view crashes Nautilus when subtrees are expanded and sorting is switched from ascending to descending
Last modified: 2005-10-03 08:47:03 UTC
Distribution: Ubuntu 5.10 (breezy) Package: nautilus Severity: Normal Version: GNOME2.11.92 2.11.92 Gnome-Distributor: Ubuntu Synopsis: new list view crashes Nautilus when subtrees are expanded and sorting is switched from ascending to descending Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.11.92 BugBuddy-GnomeVersion: 2.0 (2.11.4) Description: Description of the crash: Nautilus is crashing when I switch the direction of the sort on the Name column in my videos folder when in the new list view (some subtrees are expanded, and thumbnails are displayed). Steps to reproduce the crash: 1. Open up my /videos directory (nfs mount containing a 2- to 3-level deep tree of directories containing video files. 2. Expand to 2 levels deep (to show some thumbnails) 3. Change the sort direction from "^" to "v". 4. Crash frequently occurs. Expected Results: How often does this happen? Most of the time. Additional Information: Hopefully the backtrace will be useful. I have installed ubuntu's nautilus-dbg and libgtk2.0-0-dbg packages, to get line numbers in. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1225496896 (LWP 19934)] [New Thread -1233364048 (LWP 19944)] [New Thread -1233097808 (LWP 19943)] [New Thread -1232831568 (LWP 19942)] [New Thread -1232565328 (LWP 19941)] [New Thread -1232299088 (LWP 19940)] [New Thread -1232032848 (LWP 19939)] [New Thread -1231361104 (LWP 19938)] [New Thread -1227068496 (LWP 19935)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 62816
Thread 1 (Thread -1225496896 (LWP 19934))
v_pointer = 0xbfdfad18}, {v_int = -1217104096, v_long = -1217104096, v_int64 = -5228575260450457824, v_double = -1.174429027481664e-41, v_pointer = 0xb7747720}, {v_int = -1075860184, v_long = -1075860184, v_int64 = -5228775921181283032, v_double = -1.1356126857555118e-41, v_pointer = 0xbfdfad28}, {v_int = -1217104096, v_long = -1217104096, v_int64 = -5228575260450457824, v_double = -1.174429027481664e-41, v_pointer = 0xb7747720}, {v_int = -1075860184, v_long = -1075860184, v_int64 = -5229814319719404248, v_double = -1.003271540826498e-41, v_pointer = 0xbfdfad28}, {v_int = -1217104092, v_long = -1217104092, v_int64 = 3077863204, v_double = 1.5206664716952684e-314, v_pointer = 0xb7747724}, {v_int = -1217104068, v_long = -1217104068, v_int64 = -5227475027268176068, v_double = -1.4548726407700772e-41, v_pointer = 0xb774773c}, {v_int = 1, v_long = 1, v_int64 = 604948273945378817, v_double = 3.2115430408729813e-268, v_pointer = 0x1}} _n_values = #0 0xffffe410 in __kernel_vsyscall () ------- Bug moved to this database by unknown@gnome.bugs 2005-09-09 16:24 UTC ------- Unknown version 2.11.92 in product nautilus. Setting version to "2.11.x".
unique stack trace
Just reproduced in the latest ubuntu package: burner@phoenix:~$ nautilus --version Gnome nautilus 2.12.0 Here's the stack trace: Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1225845056 (LWP 6877)] [New Thread -1235203152 (LWP 6967)] [New Thread -1234936912 (LWP 6966)] [New Thread -1234670672 (LWP 6965)] [New Thread -1234404432 (LWP 6961)] [New Thread -1234138192 (LWP 6960)] [New Thread -1233466448 (LWP 6958)] [New Thread -1227580496 (LWP 6942)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 62971
Thread 1 (Thread -1225845056 (LWP 6877))
*** Bug 317661 has been marked as a duplicate of this bug. ***
Thanks for your bug report! This issue will be fixed as soon as http://mail.gnome.org/archives/nautilus-list/2005-October/msg00000.html is committed. Milestoning to 2.12.x, this should really make it into Nautilus 2.12.1.
Patch commited. Hopefully this will fix the problem.