Bug 519874 – 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 519874 - crash in Movie Player:


Summary:	crash in Movie Player:


Status:	RESOLVED DUPLICATE of bug 509753

Product:	totem
Classification:	Core
Component:	general
Version:	2.20.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:	2008-03-02 11:39 UTC by b.jurkic
Modified:	2008-03-02 12:39 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description b.jurkic 2008-03-02 11:39:19 UTC

Version: 2.20.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Gion

Memory status: size: 45301760 vsize: 45301760 resident: 17891328 share: 12529664 rss: 17891328 rss_rlim: 4294967295
CPU usage: start_time: 1204457946 rtime: 40 utime: 35 stime: 5 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ce36b0 (LWP 7849)]
[New Thread 0xb6167b90 (LWP 7854)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 191027

Thread 1 (Thread 0xb6ce36b0 (LWP 7849))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 strncpy
from /lib/i686/cmov/libc.so.6
#7 ??
from /usr/lib/gstreamer-0.10/libgstbluetooth.so
#8 ??
#9 ??
#0 __kernel_vsyscall



----------- .xsession-errors (73 sec old) ---------------------
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
/usr/lib/python2.4/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
Window manager warning: last_user_time (3076674608) is greater than comparison timestamp (1866955174).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2c00003 (Software U) appears to be one of the offending windows with a timestamp of 3076674608.  Working around...
current dist not found in meta-release file
Window manager warning: last_user_time (3076621360) is greater than comparison timestamp (1867033305).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2c00091 (Synaptic) appears to be one of the offending windows with a timestamp of 3076621360.  Working around...
--------------------------------------------------

Comment 1 Philip Withnall 2008-03-02 12:39:00 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 509753 ***