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 442647 - crash in Open Folder: Consistant bug: crashes ...
crash in Open Folder: Consistant bug: crashes ...
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-05-31 17:46 UTC by genij.math
Modified: 2007-09-11 13:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description genij.math 2007-05-31 17:46:42 UTC
Version: 2.18.1

What were you doing when the application crashed?
Consistant bug: crashes on reaching a locked file.

I have 2 computers on the network, and I've connected them with Natuilus->File->Connect Server->SSH or something like this.
I was trying to copy the content of /var/cache/apt folder (a bunch of *.deb files AND the LOCKed file) from my remote computer to the local one, and Nautilus crashed on reaching the locked file.

I hope my report is useful.
Yevgen.


Distribution: Debian lenny/sid
Gnome Release: 2.18.2 2007-05-28 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-1-686-bigmem #1 SMP Sat May 26 17:38:54 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 85860352 vsize: 85860352 resident: 30072832 share: 15147008 rss: 30072832 rss_rlim: 4294967295
CPU usage: start_time: 1180633104 rtime: 746 utime: 699 stime: 47 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 -1226942784 (LWP 5424)]
[New Thread -1242506352 (LWP 5462)]
(no debugging symbols found)
0xb7332e29 in poll () from /lib/libc.so.6


----------- .xsession-errors (30 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-06-01 00:17:28 UTC
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. Thanks in advance!
Comment 2 genij.math 2007-06-01 07:31:00 UTC
OK, here is the best trace I was able to get.
My actions were:
 open /var/cache/apt/archives folder in the window;
 copy the file 'lock' (/var/cache/apt/archives/lock) into the clipboard;
 paste in home directory

Dialog that I don't have enough permissions to read the file appears; I click 'skip', and bugzilla dialog arises.

nautilus-debug-log.txt is generated, contains lines:
0x8180ee8 2007/06/01 02:05:09.1163 (USER): selection changed in window 0x882cbb8
	file:///var/cache/apt/archives/lock
0x8180ee8 2007/06/01 02:05:12.0326 (USER): copy the following URIs to "file:///home/yevgen/temp":
	file:///var/cache/apt/archives/lock
0x8de55e0 2007/06/01 02:05:15.3214 (USER): debug log dumped due to signal 11

Rmks: 
-coping several other files with the 'lock' gives the crash;
-dragging the file 'lock' to home directory works fine;
-works correctly on my second debian computer



Distribution: Debian lenny/sid
Gnome Release: 2.18.2 2007-05-28 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-1-686-bigmem #1 SMP Sat May 26 17:38:54 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 85954560 vsize: 85954560 resident: 29626368 share: 14979072 rss: 29626368 rss_rlim: 4294967295
CPU usage: start_time: 1180681330 rtime: 1083 utime: 1012 stime: 71 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 -1225988416 (LWP 5741)]
[New Thread -1266742384 (LWP 5923)]
0xb741ae29 in poll () from /lib/libc.so.6

Thread 2 (Thread -1266742384 (LWP 5923))

  • #0 ??
    from /lib/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 <signal handler called>
  • #3 ??
  • #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 copy_file
    at gnome-vfs-xfer.c line 1361
  • #8 copy_items
    at gnome-vfs-xfer.c line 1851
  • #9 gnome_vfs_xfer_uri_internal
    at gnome-vfs-xfer.c line 2594
  • #10 _gnome_vfs_xfer_private
    at gnome-vfs-xfer.c line 2680
  • #11 _gnome_vfs_job_execute
    at gnome-vfs-job.c line 1557
  • #12 thread_entry_point
    at gnome-vfs-job-queue.c line 65
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
  • #15 ??


----------- .xsession-errors (8 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Xlib: unexpected async reply (sequence 0x17bea)!
--------------------------------------------------
Comment 3 genij.math 2007-06-01 17:29:39 UTC
here's another trace: same problem

Distribution: Debian lenny/sid
Gnome Release: 2.18.2 2007-05-28 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-1-686-bigmem #1 SMP Sat May 26 17:38:54 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 84508672 vsize: 84508672 resident: 27799552 share: 14880768 rss: 27799552 rss_rlim: 4294967295
CPU usage: start_time: 1180714851 rtime: 635 utime: 592 stime: 43 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 -1226303808 (LWP 2527)]
[New Thread -1283839088 (LWP 2617)]
0xb73cde29 in poll () from /lib/libc.so.6

Thread 2 (Thread -1283839088 (LWP 2617))

  • #0 ??
    from /lib/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #2 <signal handler called>
  • #3 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #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 copy_file
    at gnome-vfs-xfer.c line 1361
  • #8 copy_items
    at gnome-vfs-xfer.c line 1851
  • #9 gnome_vfs_xfer_uri_internal
    at gnome-vfs-xfer.c line 2594
  • #10 _gnome_vfs_xfer_private
    at gnome-vfs-xfer.c line 2680
  • #11 _gnome_vfs_job_execute
    at gnome-vfs-job.c line 1557
  • #12 thread_entry_point
    at gnome-vfs-job-queue.c line 65
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
  • #15 ??


----------- .xsession-errors (6 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Xlib: unexpected async reply (sequence 0x5e41)!
(nautilus:2527): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed
--------------------------------------------------
Comment 4 André Klapper 2007-09-11 13:51:16 UTC
good trace, thanks!
the trace in bug 461765 even offers more symbol, marking as a duplicate therefore

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