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 398864 - crash in Movie Player: Changing the hue and sat...
crash in Movie Player: Changing the hue and sat...
Status: RESOLVED DUPLICATE of bug 351181
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-01-20 22:22 UTC by mrjackdaw
Modified: 2007-02-06 00:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description mrjackdaw 2007-01-20 22:22:45 UTC 
Version: 2.16.2

What were you doing when the application crashed?
Changing the hue and saturation levels


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

Memory status: size: 160124928 vsize: 0 resident: 160124928 share: 0 rss: 41099264 rss_rlim: 0
CPU usage: start_time: 1169331623 rtime: 0 utime: 814 stime: 0 cutime:746 cstime: 0 timeout: 68 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 -1226180944 (LWP 5378)]
[New Thread -1346880608 (LWP 5396)]
[New Thread -1330160736 (LWP 5389)]
[New Thread -1321768032 (LWP 5388)]
[New Thread -1311487072 (LWP 5387)]
[New Thread -1298994272 (LWP 5386)]
[New Thread -1290331232 (LWP 5385)]
[New Thread -1281901664 (LWP 5382)]
[New Thread -1265521760 (LWP 5381)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 103887

Thread 1 (Thread -1226180944 (LWP 5378))

  • #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 _x_config_init
    from /usr/lib/libxine.so.1
  • #6 ??
    from /usr/lib/libxine.so.1
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall 






Comment 1


palfrey





          2007-01-20 23:04:32 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


Marc-Andre Lureau





          2007-02-06 00:33:05 UTC
        




*** This bug has been marked as a duplicate of 351181 ***