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 485951 - crash in Open Folder: Even if nobody else is u...
crash in Open Folder: Even if nobody else is u...
Status: RESOLVED DUPLICATE of bug 461765
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-12 07:36 UTC by Dan Fujita
Modified: 2007-10-29 11:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Dan Fujita 2007-10-12 07:36:35 UTC
Version: 2.18.3

What were you doing when the application crashed?
Even if nobody else is using the files, even if I Press <cancel> it still crashes the program... (this is my second bug report on this)


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 86261760 vsize: 86261760 resident: 32997376 share: 20406272 rss: 32997376 rss_rlim: 4294967295
CPU usage: start_time: 1192174525 rtime: 432 utime: 388 stime: 44 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 -1208224032 (LWP 27481)]
[New Thread -1233130608 (LWP 27499)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1233130608 (LWP 27499))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #5 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #6 ??
  • #7 ??
  • #8 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
    from /lib/ld-linux.so.2
  • #13 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #14 ??
  • #15 ??
  • #16 _dl_fixup
    from /lib/ld-linux.so.2
  • #17 gnome_vfs_get_file_info_from_handle_cancellable
    from /usr/lib/libgnomevfs-2.so.0
  • #18 gnome_vfs_get_file_info_from_handle
    from /usr/lib/libgnomevfs-2.so.0
  • #19 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #20 ??
  • #21 ??
  • #22 ??


----------- .xsession-errors ---------------------
(bug-buddy:27405): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:27405): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** (nautilus:27433): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Dati"), please tell the gnome-vfs mailing list.
(nautilus:27433): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed
** Message: Hit unexpected error "Directory busy" while doing a file operation.
** (nautilus:27481): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Dati"), please tell the gnome-vfs mailing list.
(nautilus:27481): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed
** Message: Hit unexpected error "Directory busy" while doing a file operation.
Xlib: unexpected async reply (sequence 0x53c5)!
--------------------------------------------------
Comment 1 André Klapper 2007-10-29 01:54:13 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 Dan Fujita 2007-10-29 10:01:36 UTC
Hi!

I installed the requested libraries and reproduced the error again, here goes the 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.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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 89935872 vsize: 89935872 resident: 33959936 share: 17416192 rss: 33959936 rss_rlim: 4294967295
CPU usage: start_time: 1193402982 rtime: 2890 utime: 2335 stime: 555 cutime:0 cstime: 2 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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208416544 (LWP 3085)]
[New Thread -1302746224 (LWP 10002)]
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1302746224 (LWP 10002))

  • #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 _gnome_vfs_handle_do_get_file_info
    at gnome-vfs-handle.c line 185
  • #5 gnome_vfs_get_file_info_from_handle_cancellable
    at gnome-vfs-cancellable-ops.c line 223
  • #6 gnome_vfs_get_file_info_from_handle
    at gnome-vfs-ops.c line 355
  • #7 xfer_open_source
    at gnome-vfs-xfer.c line 1361
  • #8 copy_file
    at gnome-vfs-xfer.c line 1494
  • #9 copy_directory
    at gnome-vfs-xfer.c line 1679
  • #10 copy_directory
    at gnome-vfs-xfer.c line 1684
  • #11 copy_directory
    at gnome-vfs-xfer.c line 1684
  • #12 copy_items
    at gnome-vfs-xfer.c line 1857
  • #13 gnome_vfs_xfer_uri_internal
    at gnome-vfs-xfer.c line 2594
  • #14 _gnome_vfs_xfer_private
    at gnome-vfs-xfer.c line 2680
  • #15 execute_xfer
    at gnome-vfs-job.c line 1557
  • #16 _gnome_vfs_job_execute
    at gnome-vfs-job.c line 1680
  • #17 thread_entry_point
    at gnome-vfs-job-queue.c line 65
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 ??
    from /lib/libglib-2.0.so.0
  • #20 start_thread
    from /lib/libpthread.so.0
  • #21 clone
    from /lib/libc.so.6


----------- .xsession-errors ---------------------
warning: the debug information found in "/usr/lib/debug//usr/lib/libpangocairo-1.0.so.0.1600.4.debug" does not match "/usr/lib/libpangocairo-1.0.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libpango-1.0.so.0.1600.4.debug" does not match "/usr/lib/libpango-1.0.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so" (CRC misma
warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so" (CRC mis
warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so" (CRC misma
--------------------------------------------------
Comment 3 André Klapper 2007-10-29 11:49:18 UTC
thanks for the trace, this is exactly the same bug as bug 461765.
Comment 4 André Klapper 2007-10-29 11:49:46 UTC

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