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 452093 - crash in Open Folder: Trying to open an FTP://...
crash in Open Folder: Trying to open an FTP://...
Status: RESOLVED DUPLICATE of bug 365624
Product: gtk+
Classification: Platform
Component: Backend: X11
unspecified
Other All
: High critical
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2007-06-29 00:09 UTC by David Hagood
Modified: 2007-11-08 21:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description David Hagood 2007-06-29 00:09:38 UTC 
Version: 2.19.4

What were you doing when the application crashed?
Trying to open an FTP:// url


Distribution: Fedora release 7.89 (Rawhide)
Gnome Release: 2.19.4 2007-06-17 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21.3 #2 SMP PREEMPT Wed May 30 22:06:30 CDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 241713152 vsize: 241713152 resident: 132947968 share: 27475968 rss: 132947968 rss_rlim: 4294967295
CPU usage: start_time: 1183047346 rtime: 3250 utime: 2913 stime: 337 cutime:141 cstime: 16 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 -1208625392 (LWP 941)]
[New Thread -1317975152 (LWP 3952)]
[New Thread -1301189744 (LWP 3907)]
(no debugging symbols found)
0xb7f89410 in __kernel_vsyscall ()

+ Trace 144484

Thread 2 (Thread -1317975152 (LWP 3952))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/libc.so.6
  • #5 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/gnome-vfs-2.0/modules/libftp.so
  • #6 ??
  • #7 ?? 


----------- .xsession-errors (8548606 sec old) ---------------------
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac00.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac01.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac04.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac08.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac10.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4e specified for 0x2e00003 (Initializi).
--------------------------------------------------
Comment 1 palfrey 2007-06-29 11:53:11 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 and
reopen this bug or report a new one. Thanks in advance!
Comment 2 David Hagood 2007-06-29 14:50:03 UTC 
Distribution: Fedora release 7.89 (Rawhide)
Gnome Release: 2.19.4 2007-06-17 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21.3 #2 SMP PREEMPT Wed May 30 22:06:30 CDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 103862272 vsize: 103862272 resident: 36655104 share: 26664960 rss: 36655104 rss_rlim: 4294967295
CPU usage: start_time: 1183127983 rtime: 195 utime: 171 stime: 24 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 -1209018608 (LWP 9880)]
[New Thread -1230853232 (LWP 10233)]
0xb7f29410 in __kernel_vsyscall ()

+ Trace 144619

Thread 2 (Thread -1230853232 (LWP 10233))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 865
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/libc.so.6
  • #5 do_read_directory
    at ftp-method.c line 2688
  • #6 gnome_vfs_directory_read_next_cancellable
    at gnome-vfs-directory.c line 234
  • #7 load_directory_details
    at gnome-vfs-job.c line 1477
  • #8 execute_load_directory
    at gnome-vfs-job.c line 1520
  • #9 _gnome_vfs_job_execute
    at gnome-vfs-job.c line 1674
  • #10 thread_entry_point
    at gnome-vfs-job-queue.c line 65
  • #11 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #12 g_thread_create_proxy
    at gthread.c line 594
  • #13 start_thread
    at pthread_create.c line 296
  • #14 clone
    from /lib/libc.so.6 


----------- .xsession-errors (8601220 sec old) ---------------------
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac00.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac01.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac04.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac08.
(gnome-terminal:19007): Vte-WARNING **: Can not find appropiate font for character U+ac10.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4e specified for 0x2e00003 (Initializi).
--------------------------------------------------
Comment 3 palfrey 2007-06-29 15:05:25 UTC 
Hm.. Looks like a gdk issue. Similar to Bug 354678, Bug 351208, and Bug 442647. Marking as NEW for the gtk/gdk guys.
Comment 4 palfrey 2007-11-08 21:56:26 UTC 
Huh. Looks like the gdk state is unimportant, and that it's probably a gnome-vfs deal.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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