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 367591 - crash in File Browser: van directory veranderen...
crash in File Browser: van directory veranderen...
Status: RESOLVED DUPLICATE of bug 364864
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-30 12:47 UTC by s.vd.meijs
Modified: 2006-10-31 10:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description s.vd.meijs 2006-10-30 12:47:01 UTC 
What were you doing when the application crashed?
van directory veranderen op windows fileserver


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 114794496 vsize: 0 resident: 114794496 share: 0 rss: 30617600 rss_rlim: 0
CPU usage: start_time: 1162193940 rtime: 0 utime: 3047 stime: 0 cutime:2786 cstime: 0 timeout: 261 it_real_value: 0 frequency: 0

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 -1208813872 (LWP 2244)]
[New Thread -1231078512 (LWP 27883)]
(no debugging symbols found)
0x00779402 in __kernel_vsyscall ()

+ Trace 80396

Thread 2 (Thread -1231078512 (LWP 27883))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 dbus_malloc
    from /lib/libdbus-1.so.3
  • #8 dbus_watch_set_data
    from /lib/libdbus-1.so.3
  • #9 dbus_message_unref
    from /lib/libdbus-1.so.3
  • #10 dbus_pending_call_cancel
    from /lib/libdbus-1.so.3
  • #11 dbus_connection_send_with_reply_and_block
    from /lib/libdbus-1.so.3
  • #12 gnome_vfs_daemon_message_iter_get_file_info
    from /usr/lib/libgnomevfs-2.so.0
  • #13 gnome_vfs_daemon_message_iter_get_file_info
    from /usr/lib/libgnomevfs-2.so.0
  • #14 gnome_vfs_daemon_message_iter_get_file_info
    from /usr/lib/libgnomevfs-2.so.0
  • #15 gnome_vfs_daemon_set_current_connection
    from /usr/lib/libgnomevfs-2.so.0
  • #16 gnome_vfs_directory_open_from_uri_cancellable
    from /usr/lib/libgnomevfs-2.so.0
  • #17 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #18 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #19 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #20 gnome_vfs_is_primary_thread
    from /usr/lib/libgnomevfs-2.so.0
  • #21 g_thread_pool_push
    from /lib/libglib-2.0.so.0
  • #22 g_thread_create_full
    from /lib/libglib-2.0.so.0
  • #23 start_thread
    from /lib/libpthread.so.0
  • #24 clone
    from /lib/libc.so.6 






Comment 1


André Klapper





          2006-10-31 10:44:55 UTC
        



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 364864 ***