GNOME Bugzilla – Bug 579460
crash in Open Folder: I wanted to show propert...
Last modified: 2009-08-24 02:46:49 UTC
Version: 2.26.2 What were you doing when the application crashed? I wanted to show properties of a .mpeg video file. The preview thumbshot doesn't work. Distribution: Ubuntu 9.04 (jaunty) Gnome Release: 2.26.1 2009-04-14 (Ubuntu) BugBuddy Version: 2.26.0 System: Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10600000 Selinux: No Accessibility: Disabled GTK+ Theme: Human-Clearlooks Icon Theme: Human GTK+ Modules: canberra-gtk-module Memory status: size: 61022208 vsize: 61022208 resident: 22364160 share: 15339520 rss: 22364160 rss_rlim: 18446744073709551615 CPU usage: start_time: 1240093563 rtime: 139 utime: 119 stime: 20 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb6f76750 (LWP 1817)] 0xb7fff430 in __kernel_vsyscall ()
+ Trace 214595
Thread 1 (Thread 0xb6f76750 (LWP 1817))
----------- .xsession-errors (153 sec old) --------------------- Initializing nautilus-image-converter extension Initializing nautilus-open-terminal extension ** (nautilus:1592): WARNING **: Unable to add monitor: Not supported Initializing nautilus-image-converter extension Initializing nautilus-open-terminal extension ** (nautilus:1629): WARNING **: Unable to add monitor: Not supported checking for valid crashreport now ** (update-notifier:1214): DEBUG: crashreport_check Initializing nautilus-image-converter extension Initializing nautilus-open-terminal extension ** (nautilus:1817): WARNING **: Unable to add monitor: Not supported --------------------------------------------------
Hmm, the stacktrace here looks useless, as it doesn't show where the crash happens. If you can reproduce the bug, could you please run nautilus under 'gdb' and paste the output of 'thread apply all bt full' when nautilus crashes? Thanks.
Here is the output of gdb. GNU gdb 6.8-debian 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 "i486-linux-gnu"... (gdb) run Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] [New Thread 0xb6f80750 (LWP 12551)] [New Thread 0xb6d30b90 (LWP 12554)] Initializing nautilus-image-converter extension Initializing nautilus-open-terminal extension [New Thread 0xb52d2b90 (LWP 12555)] ** (nautilus:12551): WARNING **: Unable to add monitor: Not supported [New Thread 0xb49d5b90 (LWP 12556)] [New Thread 0xb41d4b90 (LWP 12557)] [Thread 0xb6d30b90 (LWP 12554) exited] [Thread 0xb49d5b90 (LWP 12556) exited] [Thread 0xb52d2b90 (LWP 12555) exited] [New Thread 0xb52d2b90 (LWP 12559)] [Thread 0xb41d4b90 (LWP 12557) exited] [New Thread 0xb41d4b90 (LWP 12560)] [Thread 0xb41d4b90 (LWP 12560) exited] [New Thread 0xb41d4b90 (LWP 12562)] [New Thread 0xb49d5b90 (LWP 12563)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb41d4b90 (LWP 12562)] 0xb3413f69 in ?? () from /usr/lib/i686/cmov/libavcodec.so.52 (gdb) thread apply all bt full
+ Trace 214617
The program is running. Exit anyway? (y or n)
Crashing inside of libavcodec, in FFMPEG territory. If you come up with a more detailed stacktrace with debug symbols for libavcodec, you should report it to them. Thanks for taking the time to report this bug. However, this application does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome. If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other. Thanks in advance!
*** Bug 592800 has been marked as a duplicate of this bug. ***