Bug 379184 – crash in Movie Player:

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 379184 - crash in Movie Player:


Summary:	crash in Movie Player:


Status:	RESOLVED DUPLICATE of bug 367993

Product:	totem
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	General Totem maintainer(s)
QA Contact:	General Totem maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-25 16:20 UTC by nankai.wuli
Modified:	2006-11-25 19:55 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description nankai.wuli 2006-11-25 16:20:47 UTC

Version: 2.16.2

What were you doing when the application crashed?



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

Memory status: size: 61497344 vsize: 0 resident: 61497344 share: 0 rss: 23748608 rss_rlim: 0
CPU usage: start_time: 1164471631 rtime: 0 utime: 65 stime: 0 cutime:59 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 -1225845072 (LWP 5514)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 89302

Thread 1 (Thread -1225845072 (LWP 5514))

#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 strlen
from /lib/tls/i686/cmov/libc.so.6
#5 strdup
from /lib/tls/i686/cmov/libc.so.6
#6 xine_new_framegrab_audio_port
from /usr/lib/libxine.so.1
#7 ??
#8 ??
from /usr/lib/libxine.so.1
#9 ??
#10 ??
#0 __kernel_vsyscall

Comment 1 Jens Granseuer 2006-11-25 19:55:31 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 367993 ***