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 515206 - crash in Movie Player:
crash in Movie Player:
Status: RESOLVED DUPLICATE of bug 449658
Product: totem
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-02-08 14:04 UTC by christian
Modified: 2008-02-08 17:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description christian 2008-02-08 14:04:13 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-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 497618944 vsize: 497618944 resident: 57892864 share: 21733376 rss: 57892864 rss_rlim: 18446744073709551615
CPU usage: start_time: 1202479472 rtime: 106 utime: 86 stime: 20 cutime:0 cstime: 0 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b550dab1760 (LWP 7079)]
[New Thread 0x44007950 (LWP 7089)]
[New Thread 0x43806950 (LWP 7086)]
[New Thread 0x43005950 (LWP 7085)]
[New Thread 0x42804950 (LWP 7084)]
[New Thread 0x42003950 (LWP 7083)]
[New Thread 0x41802950 (LWP 7082)]
[New Thread 0x41001950 (LWP 7081)]
[New Thread 0x40800950 (LWP 7080)]
(no debugging symbols found)
0x00002b550a26eab6 in poll () from /lib/libc.so.6

Thread 4 (Thread 0x43005950 (LWP 7085))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 __assert_fail
    from /lib/libc.so.6
  • #8 ??
    from /usr/lib/libpulse.so.0
  • #9 ??
    from /usr/lib/xine/plugins/1.1.10/xineplug_ao_out_pulseaudio.so
  • #10 ??
    from /usr/lib/libxine.so.1
  • #11 ??
    from /usr/lib/libxine.so.1
  • #12 ??
    from /usr/lib/xine/plugins/1.1.10/xineplug_decode_mad.so
  • #13 ??
    from /usr/lib/libxine.so.1
  • #14 start_thread
    from /lib/libpthread.so.0
  • #15 clone
    from /lib/libc.so.6
  • #16 ??


----------- .xsession-errors ---------------------
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error Keine Berechtigun
You do not have permission to create a usershare. Ask your administrator to grant you permissions to create a share.
** (update-notifier:6192): WARNING **: no cdrom: disk
Fenstermanager-Warnung:last_user_time (1110323872) is greater than comparison timestamp (4183430194).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Fenstermanager-Warnung:0x3400091 (Synaptic) appears to be one of the offending windows with a timestamp of 1110323872.  Working around...

(synaptic:6537): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
** (update-notifier:6192): WARNING **: no cdrom: disk
totem: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Zusicherung »pthread_mutex_unlock(&m->mutex) == 0« nicht erfüllt.
--------------------------------------------------
Comment 1 Philip Withnall 2008-02-08 17:13:45 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 449658 ***