GNOME Bugzilla – Bug 456131
Fedora 7: crash in strstr / .... / gnome_vfs_directory_visit_uri
Last modified: 2007-09-28 19:33:32 UTC
Version: 2.18.3 What were you doing when the application crashed? 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.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy P Icon Theme: dlg-neu Memory status: size: 451776512 vsize: 451776512 resident: 28286976 share: 18579456 rss: 28286976 rss_rlim: 18446744073709551615 CPU usage: start_time: 1184216249 rtime: 105 utime: 94 stime: 11 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496393264 (LWP 16895)] [New Thread 1126189392 (LWP 16909)] (no debugging symbols found) 0x00000032f6ec82e6 in poll () from /lib64/libc.so.6
+ Trace 147435
Thread 2 (Thread 1126189392 (LWP 16909))
----------- .xsession-errors --------------------- Message: alsa mixer timed out Message: alsa mixer timed out Message: alsa mixer timed out Message: alsa mixer timed out Message: alsa mixer timed out Message: alsa mixer timed out Message: alsa mixer timed out Message: alsa mixer timed out Message: alsa mixer timed out This sound card's driver does not support direct access The (slower) DirectSound HEL mode will be used instead. This sound card's driver does not support direct access The (slower) DirectSound HEL mode will be used instead. (nautilus:16895): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed --------------------------------------------------
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!
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
*** Bug 456404 has been marked as a duplicate of this bug. ***
*** Bug 456940 has been marked as a duplicate of this bug. ***
*** Bug 456941 has been marked as a duplicate of this bug. ***
*** Bug 456980 has been marked as a duplicate of this bug. ***
*** Bug 457252 has been marked as a duplicate of this bug. ***
*** Bug 460061 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 454799 ***
*** Bug 464189 has been marked as a duplicate of this bug. ***
*** Bug 464132 has been marked as a duplicate of this bug. ***
*** Bug 481258 has been marked as a duplicate of this bug. ***
*** Bug 481376 has been marked as a duplicate of this bug. ***