GNOME Bugzilla – Bug 460524
crash in Open Folder:
Last modified: 2007-08-22 19:23:54 UTC
Version: 2.19.5 What were you doing when the application crashed? Distribution: Fedora release 7.89 (Rawhide) Gnome Release: 2.19.5 2007-07-08 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23-0.45.rc0.git16.fc8 #1 SMP Mon Jul 23 09:35:47 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 104321024 vsize: 104321024 resident: 43163648 share: 28979200 rss: 43163648 rss_rlim: 4294967295 CPU usage: start_time: 1185446280 rtime: 200 utime: 157 stime: 43 cutime:74 cstime: 9 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208256752 (LWP 3218)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 150651
Thread 1 (Thread -1208256752 (LWP 3218))
----------- .xsession-errors (1026450 sec old) --------------------- report junk?? Retail Price: US $ 6720.00 save US $ 6590.05 AUTODESK AUTOCAD report junk?? Retail Price: US $ 6720.00 save US $ 6590.05 AUTODESK AUTOCAD ***MEMORY-WARNING***: gnome-terminal[3445]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this Loading "installonlyn" plugin creating 0x8d5d400 report junk?? i know what helps (gnome-terminal:3445): Vte-WARNING **: No handler for control sequence `device-control-string' defined. warning: mesa-libGL-6.5.2-13.fc7: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name --------------------------------------------------
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 the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces Also, this bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
*** Bug 466518 has been marked as a duplicate of this bug. ***
*** Bug 466332 has been marked as a duplicate of this bug. ***
*** Bug 466330 has been marked as a duplicate of this bug. ***
*** Bug 466302 has been marked as a duplicate of this bug. ***
*** Bug 467223 has been marked as a duplicate of this bug. ***
*** Bug 467221 has been marked as a duplicate of this bug. ***
*** Bug 466811 has been marked as a duplicate of this bug. ***
*** Bug 466586 has been marked as a duplicate of this bug. ***
*** Bug 468041 has been marked as a duplicate of this bug. ***
*** Bug 467785 has been marked as a duplicate of this bug. ***
*** Bug 467682 has been marked as a duplicate of this bug. ***
*** Bug 467678 has been marked as a duplicate of this bug. ***
*** Bug 467677 has been marked as a duplicate of this bug. ***
*** Bug 468595 has been marked as a duplicate of this bug. ***
*** Bug 468522 has been marked as a duplicate of this bug. ***
*** Bug 468475 has been marked as a duplicate of this bug. ***
*** Bug 468444 has been marked as a duplicate of this bug. ***
*** Bug 468054 has been marked as a duplicate of this bug. ***
*** Bug 468970 has been marked as a duplicate of this bug. ***
*** Bug 468805 has been marked as a duplicate of this bug. ***
*** Bug 468799 has been marked as a duplicate of this bug. ***
*** Bug 468641 has been marked as a duplicate of this bug. ***
http://bugzilla.gnome.org/show_bug.cgi?id=469056 sorry, i created a new one
from bug 469056:
+ Trace 157036
Hi Nepomuk, der Stacktrace in Bug 469056 ist etwas besser. Kannst du bitte auch noch die Pakete glib2-debuginfo und gtk2-debuginfo installieren, den Crash noch einmal verursachen, dann in Bug-Buddy auf den "Details"-Knopf klicken, den dort angezeigten Stacktrace kopieren und ihn dann hier als Kommentar hinzufügen? Ganz herzlichen Dank im voraus! (english: The trace at bug 469056 is a bit better. Can you please also install glib2-debuginfo and gtk2-debuginfo and attach the stacktrace here? Thanks in advance!)
*** Bug 469056 has been marked as a duplicate of this bug. ***
Hi Andre, danke für die Deutsche Unterstützung! (die debuginfo-Pakete konnte ich leider nicht in den Fedora-Repositories finden... ich glaube hier hat jemand geschrieben, dass diese dort zu finden seien; hab sie dann über google gefunden) _Hier sind die Crash-Details:_ Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 67026944 vsize: 67026944 resident: 25333760 share: 19251200 rss: 25333760 rss_rlim: 4294967295 CPU usage: start_time: 1187778672 rtime: 89 utime: 78 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208158496 (LWP 3073)] 0x00110402 in __kernel_vsyscall ()
+ Trace 157096
Thread 1 (Thread -1208158496 (LWP 3073))
This problem has already been fixed. It should be solved in the next software version (2.20). Dieses Problem ist bereits gefixt, der Fix wird in Version 2.20 enthalten sein. *** This bug has been marked as a duplicate of 459221 ***