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 497742 - crash in Movie Player: je regardais un fichier ...
crash in Movie Player: je regardais un fichier ...
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: 2007-11-17 20:50 UTC by bertrand.grondin
Modified: 2007-11-18 18:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description bertrand.grondin 2007-11-17 20:50:55 UTC 
Version: 2.20.0

What were you doing when the application crashed?
je regardais un fichier .avi


Distribution: Debian lenny/sid
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.8.071117-gdn #1 SMP Sat Nov 17 11:22:37 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 152522752 vsize: 152522752 resident: 28913664 share: 15310848 rss: 28913664 rss_rlim: 4294967295
CPU usage: start_time: 1195332623 rtime: 126 utime: 104 stime: 22 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e50970 (LWP 10065)]
[New Thread 0xb15efb90 (LWP 10074)]
[New Thread 0xb1df0b90 (LWP 10073)]
[New Thread 0xb27beb90 (LWP 10072)]
[New Thread 0xb33a8b90 (LWP 10071)]
[New Thread 0xb3ba9b90 (LWP 10070)]
[New Thread 0xb4425b90 (LWP 10069)]
[New Thread 0xb5448b90 (LWP 10067)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 178398

Thread 3 (Thread 0xb1df0b90 (LWP 10073))

  • #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 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 __assert_fail
    from /lib/i686/cmov/libc.so.6
  • #10 pa_mutex_unlock
    from /usr/lib/libpulse.so.0
  • #11 pa_threaded_mainloop_unlock
    from /usr/lib/libpulse.so.0
  • #12 ??
    from /usr/lib/xine/plugins/1.1.8/xineplug_ao_out_pulseaudio.so
  • #13 ??
  • #14 ??
    from /usr/lib/xine/plugins/1.1.8/xineplug_ao_out_pulseaudio.so
  • #15 ??
  • #16 ?? 


----------- .xsession-errors (10 sec old) ---------------------
/etc/gdm/Xsession: Beginning session setup...
<stdin>:1:24: warning: missing terminating ' character
<stdin>:13:28: warning: missing terminating ' character
Xlib:  extension "XEVIE" missing on display ":0.0".
SESSION_MANAGER=local/salon:/tmp/.ICE-unix/4737
Avertissement du gestionnaire de fenêtres : « <Control>0x76 » trouvé dans la base de données de configuration n'est pas une valeur correcte pour la combinaison de touches « run_command_windo
Avertissement du gestionnaire de fenêtres : Impossible de charger le thème « Clearlooks » : Impossible de trouver un fichier valide pour le thème Clearlooks
Initializing gnome-mount extension
** Message: failed to load session from /home/bertrand/.nautilus/saved-session-3PLE0T
(gnome-panel:4813): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24
** Message: Failed to load /usr/share/icons/gnome/48x48/mimetypes/gnome-mime-application-pdf.png into memory: Failed to open file '/usr/share/icons/gnome/48x48/mimetypes/gnome-mime-application-pdf.png
sh: mpg123: command not found
totem: pulsecore/mutex-posix.c:98: pa_mutex_unlock:  l'assertion « pthread_mutex_unlock(&m->mutex) == 0 » a échoué.
--------------------------------------------------
Comment 1 Philip Withnall 2007-11-18 18:00:38 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 ***