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 493318 - crash in Open Folder: Checking which file caus...
crash in Open Folder: Checking which file caus...
Status: RESOLVED DUPLICATE of bug 493299
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-04 11:12 UTC by info
Modified: 2007-11-04 11:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description info 2007-11-04 11:12:35 UTC
Version: 2.18.3

What were you doing when the application crashed?
Checking which file causes the crash of bug 493299

I created a chrooted anonymous ftp server with only one link
poiting to the chrooted parant. This link triggers the
crash (i have tested other links, files as well).

The directory listing on the node:
  # pwd
  /home/ftp
  # ls -la
  total 8
  dr-xr-xr-x 2 ftp  ftp  4096 Nov  4 11:22 .
  drwxr-xr-x 8 root root 4096 Nov  4 11:21 ..
  lrwxrwxrwx 1 root root    2 Nov  4 11:21 p -> ..

Through "lftp":
  $ lftp paard
  lftp paard:~> ls
  lrwxrwxrwx    1 0        0               2 Nov 04 10:21 p -> ..


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.20-2936.fc7xen #1 SMP Fri Sep 21 11:56:20 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 471371776 vsize: 471371776 resident: 36311040 share: 20086784 rss: 36311040 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194174410 rtime: 124 utime: 106 stime: 18 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 46912496380976 (LWP 3976)]
[New Thread 1094719824 (LWP 3995)]
(no debugging symbols found)
0x0000003dc4ec82e6 in poll () from /lib64/libc.so.6

Thread 2 (Thread 1094719824 (LWP 3995))

  • #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 strcmp
    from /lib64/libc.so.6
  • #4 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/gnome-vfs-2.0/modules/libftp.so
  • #5 gnome_vfs_directory_read_next_cancellable
    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 /lib64/libglib-2.0.so.0
  • #11 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #12 start_thread
    from /lib64/libpthread.so.0
  • #13 clone
    from /lib64/libc.so.6


----------- .xsession-errors ---------------------
--- Hash table keys for warning below:
--> file:///home/marceln
(nautilus:3824): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
(bug-buddy:3901): GLib-GObject-WARNING **: invalid uninstantiatable type `expose-event' in cast to `GObject'
(bug-buddy:3901): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:3901): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:3901): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Xlib: sequence lost (0x12318 > 0x231c) in reply type 0x0!
--------------------------------------------------
Comment 1 info 2007-11-04 11:27:45 UTC
Closed as duplicate of 493299.

This was a test to find the cause of the crash.

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