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 418366 - crash in Movie Player:
crash in Movie Player:
Status: RESOLVED DUPLICATE of bug 364037
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-03-14 21:21 UTC by bigis
Modified: 2007-04-15 11:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description bigis 2007-03-14 21:21:10 UTC 
Version: 2.16.2

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 151011328 vsize: 0 resident: 151011328 share: 0 rss: 32604160 rss_rlim: 0
CPU usage: start_time: 1173907249 rtime: 0 utime: 167 stime: 0 cutime:147 cstime: 0 timeout: 20 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225574736 (LWP 17033)]
[New Thread -1341867104 (LWP 17043)]
[New Thread -1326019680 (LWP 17042)]
[New Thread -1317626976 (LWP 17041)]
[New Thread -1307346016 (LWP 17040)]
[New Thread -1294853216 (LWP 17039)]
[New Thread -1286190176 (LWP 17038)]
[New Thread -1277760608 (LWP 17037)]
[New Thread -1261331552 (LWP 17036)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 118664

Thread 5 (Thread -1307346016 (LWP 17040))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ?? 






Comment 1


Christian Kirbach





          2007-03-15 20:01:10 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. Thanks in advance!







Comment 2


Philip Withnall





          2007-04-15 11:01:01 UTC
        



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 364037 ***