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 91822 - Nautilus crash in applications:///
Nautilus crash in applications:///
Status: RESOLVED INCOMPLETE
Product: gnome-vfs
Classification: Deprecated
Component: Module: vfolder
2.0.x
Other other
: High critical
: ---
Assigned To: Alex Graveley
Luis Villa
Depends on:
Blocks:
 
 
Reported: 2002-08-27 17:37 UTC by Havoc Pennington
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description Havoc Pennington 2002-08-27 21:24:22 UTC
Package: gnome-vfs
Severity: normal
Version: 2.0.5
Synopsis: Nautilus crash in applications:///
Bugzilla-Product: gnome-vfs
Bugzilla-Component: Module: vfolder
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Clicking in applications with somewhat-post-null Red Hat rawhide.

This may be Red Hat specific caused by our current libc or changes to
make the vfolder backend read-only. Reporting trace so I can get to it,
and in case it has been reported 
before.



Debugging Information:

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

(no debugging symbols found)...[New Thread 1024 (LWP 27267)]
[New Thread 2049 (LWP 27275)]
[New Thread 1026 (LWP 27276)]
[New Thread 2051 (LWP 27277)]
[New Thread 3076 (LWP 27279)]
0x420a0969 in wait4 () from /lib/i686/libc.so.6

Thread 5 (Thread 3076 (LWP 27279))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 gnome_vfs_thread_pool_wait_for_work
    from /usr/lib/libgnomevfs-2.so.0
  • #4 thread_entry
    from /usr/lib/libgnomevfs-2.so.0
  • #5 g_thread_create_proxy
    from /usr/lib/libglib-2.0.so.0
  • #6 pthread_start_thread
    from /lib/i686/libpthread.so.0

Thread 4 (Thread 2051 (LWP 27277))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 pthread_cond_wait
    from /lib/i686/libpthread.so.0
  • #3 gnome_vfs_thread_pool_wait_for_work
    from /usr/lib/libgnomevfs-2.so.0
  • #4 thread_entry
    from /usr/lib/libgnomevfs-2.so.0
  • #5 g_thread_create_proxy
    from /usr/lib/libglib-2.0.so.0
  • #6 pthread_start_thread
    from /lib/i686/libpthread.so.0

Thread 3 (Thread 1026 (LWP 27276))

  • #0 sigsuspend
    from /lib/i686/libc.so.6
  • #1 __pthread_wait_for_restart_signal
    from /lib/i686/libpthread.so.0
  • #2 __pthread_alt_lock
    from /lib/i686/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/i686/libpthread.so.0
  • #4 gnome_vfs_monitor_do_add
    from /usr/lib/libgnomevfs-2.so.0
  • #5 gnome_vfs_monitor_add
    from /usr/lib/libgnomevfs-2.so.0
  • #6 setup_dir_monitor
    from /usr/lib/gnome-vfs-2.0/modules/libvfolder-desktop.so
  • #7 monitor_setup
    from /usr/lib/gnome-vfs-2.0/modules/libvfolder-desktop.so
  • #8 get_vfolder_info_unlocked
    from /usr/lib/gnome-vfs-2.0/modules/libvfolder-desktop.so
  • #9 get_vfolder_info
    from /usr/lib/gnome-vfs-2.0/modules/libvfolder-desktop.so
  • #10 do_get_file_info
    from /usr/lib/gnome-vfs-2.0/modules/libvfolder-desktop.so
  • #11 gnome_vfs_get_file_info_uri_cancellable
    from /usr/lib/libgnomevfs-2.so.0
  • #12 execute_get_file_info
    from /usr/lib/libgnomevfs-2.so.0
  • #13 gnome_vfs_job_execute
    from /usr/lib/libgnomevfs-2.so.0
  • #14 thread_routine
    from /usr/lib/libgnomevfs-2.so.0
  • #15 thread_entry
    from /usr/lib/libgnomevfs-2.so.0
  • #16 g_thread_create_proxy
    from /usr/lib/libglib-2.0.so.0
  • #17 pthread_start_thread
    from /lib/i686/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-08-27 17:24 -------

Reassigning to the default owner of the component, jirka@5z.com.

Comment 1 Andrew Sobala 2002-08-27 22:16:50 UTC
Can't find any duplicates, but the simple dup finder script barfs on
this stack trace which makes it quite a bit harder :-)
Comment 2 Luis Villa 2002-09-10 15:35:44 UTC
Look useful at all, Alex?
Comment 3 Alex Graveley 2002-11-08 16:18:07 UTC
Nope, I can't tell anything from that trace since that vfolder code
calls into other vfs methods, so it could be anythign causing the crash.
Comment 4 Luis Villa 2002-11-12 05:05:45 UTC
Closing, then.