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 385199 - crash in Movie Player: change the resolution
crash in Movie Player: change the resolution
Status: RESOLVED DUPLICATE of bug 367916
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: 2006-12-12 20:56 UTC by laggil
Modified: 2006-12-12 21:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description laggil 2006-12-12 20:56:38 UTC 
Version: 2.16.2

What were you doing when the application crashed?
change the resolution


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

Memory status: size: 239300608 vsize: 0 resident: 239300608 share: 0 rss: 95477760 rss_rlim: 0
CPU usage: start_time: 1165930743 rtime: 0 utime: 97660 stime: 0 cutime:94413 cstime: 0 timeout: 3247 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 -1225918800 (LWP 30582)]
[New Thread -1332663392 (LWP 30593)]
[New Thread -1324270688 (LWP 30592)]
[New Thread -1313989728 (LWP 30591)]
[New Thread -1301496928 (LWP 30590)]
[New Thread -1292833888 (LWP 30589)]
[New Thread -1284404320 (LWP 30588)]
[New Thread -1267946592 (LWP 30585)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 93642

Thread 1 (Thread -1225918800 (LWP 30582))

  • #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


Christian Kirbach





          2006-12-12 21:10:25 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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