GNOME Bugzilla – Bug 582746
crash in GNOME Commander: ??????? ????? ?????
Last modified: 2018-08-17 13:52:58 UTC
Version: 1.2.7 What were you doing when the application crashed? Пытался зайти через "new connection" на "ftp.gnome.org" I truing connect to ftp.gnome.org Distribution: Gentoo Base System release 2.0.0 Gnome Release: 2.24.3 2009-05-09 (Gentoo) BugBuddy Version: 2.24.2 System: Linux 2.6.29-gentoo-r1 #3 SMP Wed Apr 22 22:45:44 EEST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Modern_Time Icon Theme: Mist Memory status: size: 88190976 vsize: 88190976 resident: 43659264 share: 24088576 rss: 43659264 rss_rlim: 18446744073709551615 CPU usage: start_time: 1242382222 rtime: 200 utime: 178 stime: 22 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-commander' [Thread debugging using libthread_db enabled] [New Thread 0xb518d730 (LWP 17842)] [New Thread 0xb3c16b90 (LWP 17901)] 0xb7fae424 in __kernel_vsyscall ()
+ Trace 215481
----------- .xsession-errors (108890 sec old) --------------------- AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Начало воспроизведения... [mpeg4 @ 0x89094e0]Invalid and inefficient vfw-avi packed B frames detected VDec: запрос vo config - 608 x 272 (предпочитаемое цветовое пространство: Planar YV12) VDec: использую Planar YV12 в качестве выходного csp (не 0) Movie-Aspect - 2.24:1 - выполняю предварительное масштабирование для коррекции соотношения сторон фильма. VO: [xv] 608x272 => 608x272 Planar YV12 A: 0.2 V: 0.0 A-V: 0.173 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 0.2 V: 0.0 A-V: 0.154 ct: -0.002 2/ 2 ??% ??% ??,?% 1 0 A: 0.2 V: 0.1 A-V: 0.131 ct: -0.0 === ПРИОСТАНОВЛЕНО === ** (gnome-panel:2922): WARNING **: Invalid borders specified for theme pixmap: /home/ilian/.themes/Modern_Time/gtk-2.0/panel_button-normal.png, borders don't fit within the image A:4067.5 V:4067.5 A-V: -0.005 ct: 0.103 101689/101689 1% 1% 0.6% 0 0 A:4067.6 V:4067.6 A-V: -0.004 ct: 0.102 101690/101690 1% 1% 0.6% 0 0 A:4067.6 V:4067.6 A-V: -0.004 ct: 0.1 ...Too much output, ignoring rest... --------------------------------------------------
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!
I am first using GDB (Впервые использовал gdb, надеюсь, эти данные прояснят всю ситуацию) ilian@localhost ~ $ gdb gnome-commander GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... (gdb) run Starting program: /usr/bin/gnome-commander [Thread debugging using libthread_db enabled] [New Thread 0xb5148730 (LWP 20264)] Fontconfig error: "~/.fonts.conf", line 32: mismatched tag (gnome-commander:20264): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed [New Thread 0xb3bceb90 (LWP 20269)] [Thread 0xb3bceb90 (LWP 20269) exited] [New Thread 0xb3bceb90 (LWP 20270)] (gnome-commander:20264): libgnomevfs-CRITICAL **: gnome_vfs_uri_resolve_relative: assertion `relative_reference != NULL' failed (gnome-commander:20264): libgnomevfs-CRITICAL **: gnome_vfs_uri_get_host_name: assertion `uri != NULL' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb3bceb90 (LWP 20270)] 0xb62765ea in strcmp () from /lib/libc.so.6 (gdb) Quit (gdb) thread apply all bt
+ Trace 215501
Thread 3 (Thread 0xb3bceb90 (LWP 20270))
This appears to be a gnome-vfs issue. Might be a duplicate of bug 359145, but could you please install the debugging symbols package for gnome-vfs (http://live.gnome.org/GettingTraces/DistroSpecificInstructions has details on how to this) and then get us another stack trace? Thanks!
Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.27.23-78.2.50.fc9.x86_64 #1 SMP Mon May 11 11:11:33 EDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glider Icon Theme: Mist Memory status: size: 508813312 vsize: 508813312 resident: 47960064 share: 18616320 rss: 47960064 rss_rlim: 18446744073709551615 CPU usage: start_time: 1243271737 rtime: 1240 utime: 1167 stime: 73 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-commander' [Thread debugging using libthread_db enabled] [New Thread 0x7f0a1e708800 (LWP 2720)] [New Thread 0x41e57950 (LWP 2815)] 0x0000003821eda9f6 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 87 int result = INLINE_SYSCALL (poll, 3, CHECK_N (fds, nfds), nfds, timeout); Current language: auto; currently c
+ Trace 215691
Thread 2 (Thread 0x41e57950 (LWP 2815))
The attached stack trace (comment #4) is taken from gcmd crash: gnome-cmd-con-ftp.cc(38) void get_file_info_func(GnomeCmdCon*): ... GnomeVFSFileInfoOptions infoOpts = (GnomeVFSFileInfoOptions) (GNOME_VFS_FILE_INFO_FOLLOW_LINKS | GNOME_VFS_FILE_INFO_GET_MIME_TYPE | GNOME_VFS_FILE_INFO_FORCE_FAST_MIME_TYPE); con->base_info = gnome_vfs_file_info_new (); GnomeVFSResult res = gnome_vfs_get_file_info_uri (uri, con->base_info, infoOpts); where uri is constructed from text_uri=`ftp://anonymous:me%40provider.com@ftp.gnome.org//pub/GNOME/sources/gnome-commander' Hope it'll help, Piotr
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 359145 ***
*** Bug 586653 has been marked as a duplicate of this bug. ***
Bug 359145 was closed on 2007-03-30 -> the fix should have gone into gnome-vfs 2.18. The problem is still reproducible with gnome-vfs 2.22. The crash occurs only for uri: ftp://anonymous:me%40provider.com@ftp.gnome.org//pub/GNOME/sources/gnome-commander
gnome-vfs got deprecated in 2008. gnome-vfs is not under active development anymore and had its last code changes in 2011. Its codebase has been archived: https://gitlab.gnome.org/Archive/gnome-vfs/commits/master gio (in glib) and gvfs are its successors. See https://developer.gnome.org/gio/stable/ch33.html and https://people.gnome.org/~gicmo/gio-migration-guide/ for porting info. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of glib/gio/gvfs. Thanks!