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 519534 - 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-29 15:08 UTC by conrad
Modified: 2008-02-29 16:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description conrad 2008-02-29 15:08:40 UTC
Version: 2.20.3

What were you doing when the application crashed?



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

System: Linux 2.6.14.3 #6 Mon Feb 4 20:34:50 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 154509312 vsize: 154509312 resident: 43143168 share: 20512768 rss: 43143168 rss_rlim: 4294967295
CPU usage: start_time: 1204297716 rtime: 214 utime: 200 stime: 14 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 0xb6ceb6b0 (LWP 5158)]
[New Thread 0xb19a3b90 (LWP 5166)]
[New Thread 0xb2244b90 (LWP 5165)]
[New Thread 0xb2a44b90 (LWP 5164)]
[New Thread 0xb3411b90 (LWP 5163)]
[New Thread 0xb3ffab90 (LWP 5162)]
[New Thread 0xb47fab90 (LWP 5161)]
[New Thread 0xb5064b90 (LWP 5160)]
[New Thread 0xb607fb90 (LWP 5159)]
(no debugging symbols found)
0xb71d55bd in poll () from /lib/libc.so.6

Thread 4 (Thread 0xb2a44b90 (LWP 5164))

  • #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/libpulse.so.0
  • #10 ??
    from /usr/lib/libpulse.so.0
  • #11 ??
  • #12 ??
    from /usr/lib/libpulse.so.0
  • #13 ??
  • #14 ??
    from /usr/lib/libpulse.so.0
  • #15 ??
  • #16 pa_threaded_mainloop_unlock
    from /usr/lib/libpulse.so.0


----------- .xsession-errors (90850 sec old) ---------------------
ALSA lib conf.c:3982:(snd_config_expand) Evaluate error: No existe el dispositivo
ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default
ALSA lib pcm_hw.c:1207:(_snd_pcm_hw_open) Invalid value for card
ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_card_driver returned error: No existe el dispositivo
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_concat returned error: No existe el dispositivo
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_refer returned error: No existe el dispositivo
ALSA lib conf.c:3982:(snd_config_expand) Evaluate error: No existe el dispositivo
ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM default
ALSA lib pcm_hw.c:1207:(_snd_pcm_hw_open) Invalid value for card
ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:3510:(_snd_config_evaluate) function snd_func_card_driver returned error: No existe el dispositivo
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Philip Withnall 2008-02-29 16:51:18 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 ***