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 462726 - crash in Open Folder:
crash in Open Folder:
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-08-02 09:07 UTC by diogo
Modified: 2007-08-02 17:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description diogo 2007-08-02 09:07:10 UTC 
Version: 2.18.3

What were you doing when the application crashed?



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.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 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: 455647232 vsize: 455647232 resident: 34553856 share: 19238912 rss: 34553856 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186045494 rtime: 169 utime: 150 stime: 19 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496335920 (LWP 3735)]
[New Thread 1126189392 (LWP 4051)]
(no debugging symbols found)
0x0000003ba7cc82e6 in poll () from /lib64/libc.so.6

+ Trace 152276

Thread 2 (Thread 1126189392 (LWP 4051))

  • #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 /usr/lib64/libgnomevfs-2.so.0
  • #16 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #17 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #18 start_thread
    from /lib64/libpthread.so.0
  • #19 clone
    from /lib64/libc.so.6 


----------- .xsession-errors (6 sec old) ---------------------
localuser:darkscrolls being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3623
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Loading "protectbase" plugin
Loading "installonlyn" plugin
0 packages excluded due to repository protections
--- Hash table keys for warning below:
--> file:///home/darkscrolls
(nautilus:4039): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
warning: .dynamic section for "/lib64/libasound.so.2" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Iestyn Pryce 2007-08-02 17:03:19 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 ***