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 447775 - crash in Open Folder: Copying a file from disk...
crash in Open Folder: Copying a file from disk...
Status: RESOLVED DUPLICATE of bug 446868
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-15 05:17 UTC by nobody
Modified: 2007-06-23 11:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description nobody 2007-06-15 05:17:27 UTC 
Version: 2.18.1

What were you doing when the application crashed?
Copying a file from disk to usb key


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 504541184 vsize: 504541184 resident: 44490752 share: 26587136 rss: 44490752 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181868760 rtime: 787 utime: 673 stime: 114 cutime:144 cstime: 23 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496438992 (LWP 3260)]
[New Thread 1115699536 (LWP 11045)]
(no debugging symbols found)
0x00000030da6c7956 in poll () from /lib64/libc.so.6

+ Trace 141118

Thread 2 (Thread 1115699536 (LWP 11045))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #4 gnome_vfs_get_file_info_from_handle_cancellable
    from /usr/lib64/libgnomevfs-2.so.0
  • #5 gnome_vfs_get_file_info_from_handle
    from /usr/lib64/libgnomevfs-2.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #7 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #8 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #9 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #10 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #11 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #12 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #13 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #14 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #15 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #16 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #17 start_thread
    from /lib64/libpthread.so.0
  • #18 clone
    from /lib64/libc.so.6 


----------- .xsession-errors ---------------------
Initializing nautilus-search-tool extension
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
(gnome-terminal:3382): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:3382): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
(gnome-terminal:3382): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x1403d64 (bcg - File); these messages lack timestamps and therefore suck.
Error: Incorrect password
Xlib: unexpected async reply (sequence 0x1e94a)!
warning: .dynamic section for "/usr/lib64/libexif.so.12" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 André Klapper 2007-06-23 11:27:53 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 446868 ***