GNOME Bugzilla – Bug 563915
crash in Open Folder:
Last modified: 2008-12-10 04:15:08 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686-bigmem #1 SMP Wed Nov 26 20:00:34 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 67518464 vsize: 67518464 resident: 15560704 share: 12013568 rss: 15560704 rss_rlim: 4294967295 CPU usage: start_time: 1228860275 rtime: 78 utime: 62 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb69f4710 (LWP 4130)] 0xb7eeb424 in __kernel_vsyscall ()
+ Trace 210650
Thread 1 (Thread 0xb69f4710 (LWP 4130))
----------- .xsession-errors --------------------- This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. none found Throttle level is 0 seahorse nautilus module initialized Initializing gnome-mount extension (gnome-panel:3966): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 563916 has been marked as a duplicate of this bug. ***
*** Bug 563918 has been marked as a duplicate of this bug. ***
*** Bug 563919 has been marked as a duplicate of this bug. ***
Sergio: Please DO USE the simple-dup-finder.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 552414 ***
Andre is no exactly dup of 552414.
It is the same issue. :-)
I just explained Sergio about how traces can be tricky like here, when the crashing function is the same, but the rest of details in the trace would make you think other stuff is involved. Sergio, you owe Andre a beer. And you better pay him or he will come to kill you while you sleep. :-)