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 381290 - crash in Movie Player: Changing resolutions for...
crash in Movie Player: Changing resolutions for...
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: 2006-12-01 15:04 UTC by jolt
Modified: 2006-12-01 17:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jolt 2006-12-01 15:04:02 UTC 
Version: 2.16.2

What were you doing when the application crashed?
Changing resolutions for a VNC window


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

Memory status: size: 152838144 vsize: 0 resident: 152838144 share: 0 rss: 36143104 rss_rlim: 0
CPU usage: start_time: 1164984539 rtime: 0 utime: 3198 stime: 0 cutime:2536 cstime: 0 timeout: 662 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 -1225513296 (LWP 8201)]
[New Thread -1355113568 (LWP 8220)]
[New Thread -1342784608 (LWP 8218)]
[New Thread -1334391904 (LWP 8217)]
[New Thread -1324110944 (LWP 8216)]
[New Thread -1311618144 (LWP 8215)]
[New Thread -1302955104 (LWP 8214)]
[New Thread -1289995360 (LWP 8210)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 90842

Thread 1 (Thread -1225513296 (LWP 8201))

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


Iestyn Pryce





          2006-12-01 17:16:32 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 ***