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 427157 - crash in Movie Player: fadfad
crash in Movie Player: fadfad
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-07 04:27 UTC by xilihuala163
Modified: 2007-05-07 08:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description xilihuala163 2007-04-07 04:27:36 UTC 
Version: 2.16.2

What were you doing when the application crashed?
fadfad


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

Memory status: size: 154124288 vsize: 0 resident: 154124288 share: 0 rss: 32800768 rss_rlim: 0
CPU usage: start_time: 1175920021 rtime: 0 utime: 70 stime: 0 cutime:64 cstime: 0 timeout: 6 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 -1225640272 (LWP 23440)]
[New Thread -1345324128 (LWP 23451)]
[New Thread -1329071200 (LWP 23450)]
[New Thread -1320678496 (LWP 23449)]
[New Thread -1310397536 (LWP 23448)]
[New Thread -1297904736 (LWP 23447)]
[New Thread -1289241696 (LWP 23446)]
[New Thread -1280848992 (LWP 23443)]
[New Thread -1264358496 (LWP 23442)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 125683

Thread 5 (Thread -1310397536 (LWP 23448))

  • #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-07 10:37:22 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-07 08:56:39 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 ***