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 514504 - crash in Movie Player: open video mpeg
crash in Movie Player: open video mpeg
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-05 11:19 UTC by robertokrauter
Modified: 2008-02-05 16:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description robertokrauter 2008-02-05 11:19:16 UTC
Version: 2.20.3

What were you doing when the application crashed?
open video mpeg


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 Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tangerine

Memory status: size: 142532608 vsize: 142532608 resident: 29270016 share: 15011840 rss: 29270016 rss_rlim: 4294967295
CPU usage: start_time: 1202210334 rtime: 162 utime: 148 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e426b0 (LWP 3507)]
[New Thread 0xb226db90 (LWP 3520)]
[New Thread 0xb2a6eb90 (LWP 3519)]
[New Thread 0xb343cb90 (LWP 3518)]
[New Thread 0xb4026b90 (LWP 3517)]
[New Thread 0xb4827b90 (LWP 3516)]
[New Thread 0xb5086b90 (LWP 3515)]
[New Thread 0xb60b8b90 (LWP 3514)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 3 (Thread 0xb2a6eb90 (LWP 3519))

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


----------- .xsession-errors ---------------------
GNOME PPP: STDERR: --> --> PAP (Password Authentication Protocol) may be flaky.
GNOME PPP: STDERR: --> Warning: Could not modify /etc/ppp/chap-secrets: Permission denied
GNOME PPP: STDERR: --> --> CHAP (Challenge Handshake) may be flaky.
GNOME PPP: STDERR: --> Pid of pppd: 3268
GNOME PPP: STDERR: --> Using interface ppp0
GNOME PPP: STDERR: --> Disconnecting at Tue Feb  5 12:15:34 2008
GNOME PPP: STDERR: --> The PPP daemon has died: Authentication error.
GNOME PPP: STDERR: --> We failed to authenticate ourselves to the peer.
GNOME PPP: STDERR: --> Maybe bad account or password? (exit code = 19)
GNOME PPP: STDERR: --> man pppd explains pppd error codes in more detail.
GNOME PPP: STDERR: --> I guess that's it for now, exiting
GNOME PPP: STDERR: --> The PPP daemon has died. (exit code = 19)
WVCONF: /home/krauter/.wvdial.conf
/usr/lib/iceweasel/firefox-bin: Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking
totem: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Asserzione `pthread_mutex_unlock(&m->mutex) == 0' fallita.
--------------------------------------------------
Comment 1 Philip Withnall 2008-02-05 16:56:51 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 ***