GNOME Bugzilla – Bug 499592
crash in Computer: Opening the properties o...
Last modified: 2007-12-21 03:25:46 UTC
Version: 2.18.3 What were you doing when the application crashed? Opening the properties of a WAV file Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21.1 #7 Mon Nov 19 19:17:59 CET 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Nuovo Memory status: size: 80883712 vsize: 80883712 resident: 31813632 share: 15376384 rss: 31813632 rss_rlim: 4294967295 CPU usage: start_time: 1196020603 rtime: 433 utime: 419 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6d546b0 (LWP 3933)] (no debugging symbols found) 0xb7f06410 in __kernel_vsyscall ()
+ Trace 179605
Thread 1 (Thread 0xb6d546b0 (LWP 3933))
----------- .xsession-errors (22985 sec old) --------------------- miszka^7 fragged BLUE's flag carrier! ^^8UnnamedPlayer^7 was railed by miszka^7 ^^8UnnamedPlayer^7: ^2:D miszka^7 returned the RED flag! SMB^7 got the BLUE flag! miszka^7 was in the wrong place. Vador^7 got the RED flag! NK^7 connected ^^8UnnamedPlayer^7 fragged RED's flag carrier! SMB^7 was railed by ^^8UnnamedPlayer^7 [^6J^7]Cacatoes^7: ^2lowl pako_PL^7 fragged BLUE's flag carrier! Vador^7 was railed by pako_PL^7 ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
Created attachment 99689 [details] StackTrace given using gdb
Just to add : I'm not sure what I gave is enough. I installed debugging packages but Bugbuddy doesn't appear anymore to report the bug so I used gdb. I can try other ways if needed.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 440988 ***