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 422814 - crash in Movie Player: Changing resolution.
crash in Movie Player: Changing resolution.
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-03-25 22:23 UTC by fervidfrogger
Modified: 2007-03-27 21:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description fervidfrogger 2007-03-25 22:23:27 UTC 
Version: 2.16.2

What were you doing when the application crashed?
Changing resolution.	


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

Memory status: size: 146423808 vsize: 0 resident: 146423808 share: 0 rss: 27656192 rss_rlim: 0
CPU usage: start_time: 1174853351 rtime: 0 utime: 280 stime: 0 cutime:262 cstime: 0 timeout: 18 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 -1225316688 (LWP 8902)]
[New Thread -1328735328 (LWP 8916)]
[New Thread -1320342624 (LWP 8915)]
[New Thread -1310061664 (LWP 8914)]
[New Thread -1297568864 (LWP 8913)]
[New Thread -1288905824 (LWP 8912)]
[New Thread -1280513120 (LWP 8909)]
[New Thread -1264006240 (LWP 8908)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 122215

Thread 1 (Thread -1225316688 (LWP 8902))

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


Susana





          2007-03-27 21:45:27 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 351181 ***