After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 491058 - crash in Home Folder: searching for "*.mid" on...
crash in Home Folder: searching for "*.mid" on...
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-28 13:32 UTC by rogersoares
Modified: 2007-10-29 18:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description rogersoares 2007-10-28 13:32:10 UTC
What were you doing when the application crashed?
searching for "*.mid" on my home directory.
reproducible always.
fedora 7 with all updates.


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 94113792 vsize: 94113792 resident: 36667392 share: 22413312 rss: 36667392 rss_rlim: 4294967295
CPU usage: start_time: 1193577775 rtime: 266 utime: 172 stime: 94 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208592672 (LWP 2575)]
[New Thread -1253377136 (LWP 2671)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1253377136 (LWP 2671))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strstr
    from /lib/libc.so.6
  • #5 ??
  • #6 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #7 ??
  • #8 ??
  • #9 ??


----------- .xsession-errors ---------------------
localuser:roger being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2460
winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running
Initializing nautilus-image-converter extension
--- Hash table keys for warning below:
--> file:///user/roger
(nautilus:2664): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(nautilus:2575): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
Xlib: unexpected async reply (sequence 0x1ee6)!
--------------------------------------------------
Comment 1 André Klapper 2007-10-29 02:06:15 UTC
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: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, eel2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo.

More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 rogersoares 2007-10-29 15:51:32 UTC
Here it is:

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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 93990912 vsize: 93990912 resident: 36818944 share: 22392832 rss: 36818944 rss_rlim: 4294967295
CPU usage: start_time: 1193670475 rtime: 279 utime: 171 stime: 108 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208764704 (LWP 2578)]
[New Thread -1221940336 (LWP 2893)]
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1221940336 (LWP 2893))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 strstr
    from /lib/libc.so.6
  • #5 search_visit_func
    at nautilus-search-engine-simple.c line 221
  • #6 directory_visit_internal
    at gnome-vfs-directory.c line 401
  • #7 directory_visit_internal
    at gnome-vfs-directory.c line 426
  • #8 directory_visit_internal
    at gnome-vfs-directory.c line 426
  • #9 gnome_vfs_directory_visit_uri
    at gnome-vfs-directory.c line 495
  • #10 search_thread_func
    at nautilus-search-engine-simple.c line 269
  • #11 g_thread_create_proxy
    at gthread.c line 594
  • #12 start_thread
    from /lib/libpthread.so.0
  • #13 clone
    from /lib/libc.so.6


----------- .xsession-errors ---------------------
localuser:roger being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2462
winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running
Initializing nautilus-image-converter extension
--- Hash table keys for warning below:
--> file:///user/roger
(nautilus:2886): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(nautilus:2578): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
Xlib: unexpected async reply (sequence 0x1cad)!
Cannot access memory at address 0x1
Cannot access memory at address 0x1
--------------------------------------------------
Comment 3 André Klapper 2007-10-29 18:46:57 UTC
ah, thank you!
this bug has been fixed in version 2.20.0, see bug 454799.

*** This bug has been marked as a duplicate of 454799 ***