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 433619 - 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-04-26 15:01 UTC by tomberthier
Modified: 2007-05-28 16:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description tomberthier 2007-04-26 15:01:49 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: 155004928 vsize: 0 resident: 155004928 share: 0 rss: 33501184 rss_rlim: 0
CPU usage: start_time: 1177599617 rtime: 0 utime: 419 stime: 0 cutime:342 cstime: 0 timeout: 77 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 -1226279248 (LWP 8763)]
[New Thread -1346409568 (LWP 8782)]
[New Thread -1330275424 (LWP 8776)]
[New Thread -1321882720 (LWP 8775)]
[New Thread -1311601760 (LWP 8774)]
[New Thread -1299108960 (LWP 8773)]
[New Thread -1290445920 (LWP 8772)]
[New Thread -1282016352 (LWP 8769)]
[New Thread -1265587296 (LWP 8767)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 5 (Thread -1311601760 (LWP 8774))

  • #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 palfrey 2007-04-26 15:59:51 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-05-28 16:40:44 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 ***