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 440608 - crash in Movie Player:
crash in Movie Player:
Status: RESOLVED INCOMPLETE
Product: totem
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-05-23 01:31 UTC by elmar
Modified: 2007-05-23 09:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description elmar 2007-05-23 01:31:13 UTC
Version: 2.16.6

What were you doing when the application crashed?



Distribution: Debian 3.1 (sarge)
Gnome Release: 2.18.1 2007-04-25 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.20.7-oregon.01heebs #1 PREEMPT Mon Apr 16 22:23:44 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Default
Icon Theme: gnome

Memory status: size: 129404928 vsize: 129404928 resident: 33705984 share: 13705216 rss: 33705984 rss_rlim: 4294967295
CPU usage: start_time: 1179883866 rtime: 108 utime: 98 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/totem'

(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 -1225889584 (LWP 13432)]
[New Thread -1322370160 (LWP 13445)]
[New Thread -1303565424 (LWP 13441)]
[New Thread -1295176816 (LWP 13440)]
[New Thread -1284899952 (LWP 13439)]
[New Thread -1272411248 (LWP 13438)]
[New Thread -1264022640 (LWP 13437)]
[New Thread -1255634032 (LWP 13436)]
[New Thread -1238697072 (LWP 13435)]
(no debugging symbols found)
0xb739f5c2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0


----------- .xsession-errors (544956 sec old) ---------------------
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
/bin/sh: /usr/bin/esd: No such file or directory
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-05-23 01:56:06 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to 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. Thanks in advance!
Comment 2 elmar 2007-05-23 09:09:01 UTC
The crash was triggered by a broken MPEG or AVI (don't even remember what it was, I've deleted it because it was broken).  I opened the the movie from nautilus and when the bug reporting tool opened I meant to click on "cancel" and hit "send" instead.

Ideally, totem would only complain about a broken movie file and not crash.  But since I don't have that particular movie anymore this case cannot be used to analyze the bug.