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 526167 - crash in Movie Player: nada o micro estava em e...
crash in Movie Player: nada o micro estava em e...
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-04-04 15:29 UTC by diogoiori
Modified: 2008-04-04 16:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description diogoiori 2008-04-04 15:29:25 UTC
Version: 2.20.3

What were you doing when the application crashed?
nada o micro estava em espera


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 152563712 vsize: 152563712 resident: 39202816 share: 14520320 rss: 39202816 rss_rlim: 4294967295
CPU usage: start_time: 1207312132 rtime: 54 utime: 46 stime: 8 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 0xb6d9e720 (LWP 19792)]
[New Thread 0xb205db90 (LWP 19799)]
[New Thread 0xb285eb90 (LWP 19798)]
[New Thread 0xb322cb90 (LWP 19797)]
[New Thread 0xb3e16b90 (LWP 19796)]
[New Thread 0xb4617b90 (LWP 19795)]
[New Thread 0xb4e80b90 (LWP 19794)]
[New Thread 0xb5ea6b90 (LWP 19793)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 3 (Thread 0xb285eb90 (LWP 19798))

  • #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 ---------------------
(bug-buddy:19749): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
(bug-buddy:19749): Gtk-CRITICAL **: gtk_builder_get_object: assertion `GTK_IS_BUILDER (builder)' failed
(bug-buddy:19749): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed
(bug-buddy:19749): Gtk-CRITICAL **: gtk_builder_get_object: assertion `GTK_IS_BUILDER (builder)' failed
(bug-buddy:19749): Gtk-CRITICAL **: gtk_widget_size_request: assertion `GTK_IS_WIDGET (widget)' failed
(bug-buddy:19749): Gtk-CRITICAL **: gtk_builder_get_object: assertion `GTK_IS_BUILDER (builder)' failed
(bug-buddy:19749): Gtk-CRITICAL **: gtk_window_resize: assertion `GTK_IS_WINDOW (window)' failed
totem: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Assertiva `pthread_mutex_unlock(&m->mutex) == 0' falhou.
totem: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Assertiva `pthread_mutex_unlock(&m->mutex) == 0' falhou.
--------------------------------------------------
Comment 1 Philip Withnall 2008-04-04 16:47:55 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 ***