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 522610 - 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-03-15 14:11 UTC by bill.gates
Modified: 2008-03-15 17:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description bill.gates 2008-03-15 14:11:57 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-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Mist

Memory status: size: 159367168 vsize: 159367168 resident: 44875776 share: 17264640 rss: 44875776 rss_rlim: 4294967295
CPU usage: start_time: 1205590309 rtime: 166 utime: 141 stime: 25 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 0xb6df26b0 (LWP 18656)]
[New Thread 0xb0cffb90 (LWP 18668)]
[New Thread 0xb21beb90 (LWP 18667)]
[New Thread 0xb29bfb90 (LWP 18666)]
[New Thread 0xb338db90 (LWP 18665)]
[New Thread 0xb3f77b90 (LWP 18664)]
[New Thread 0xb4778b90 (LWP 18663)]
[New Thread 0xb4fd5b90 (LWP 18662)]
[New Thread 0xb609cb90 (LWP 18661)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 192492

Thread 4 (Thread 0xb29bfb90 (LWP 18666))

  • #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 (1713986 sec old) ---------------------
** (nm-applet:4580): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.29" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4580): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.29" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4580): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.29" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4580): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.29" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4580): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.29" is not allowed to own the service "org.freedesktop.Networ
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Philip Withnall 2008-03-15 17:25:26 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 ***