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 541597 - crash in Movie Player: crash after exit from fu...
crash in Movie Player: crash after exit from fu...
Status: RESOLVED DUPLICATE of bug 426990
Product: totem
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-07-04 20:29 UTC by uniok
Modified: 2008-07-05 01:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description uniok 2008-07-04 20:29:12 UTC 
Version: 2.22.2

What were you doing when the application crashed?
crash after exit from fullscreen mode


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-486 #1 Fri Jun 27 02:39:22 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mac4Lin_GTK_v0.4
Icon Theme: Mac4Lin_Icons_v0.4

Memory status: size: 137437184 vsize: 137437184 resident: 47665152 share: 15589376 rss: 47665152 rss_rlim: 4294967295
CPU usage: start_time: 1215202918 rtime: 5278 utime: 4978 stime: 300 cutime:4 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/totem'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6806ac0 (LWP 17886)]
[New Thread 0xb2072b90 (LWP 17895)]
[New Thread 0xb28f5b90 (LWP 17894)]
[New Thread 0xb34bfb90 (LWP 17893)]
[New Thread 0xb3d7ab90 (LWP 17892)]
[New Thread 0xb493cb90 (LWP 17891)]
[New Thread 0xb529fb90 (LWP 17890)]
[New Thread 0xb5f22b90 (LWP 17889)]
(no debugging symbols found)
0xb7f71430 in __kernel_vsyscall ()

+ Trace 202067

Thread 1 (Thread 0xb6806ac0 (LWP 17886))

  • #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 g_type_check_value_holds
    from /usr/lib/libgobject-2.0.so.0
  • #7 gst_value_get_fraction_numerator
    from /usr/lib/libgstreamer-0.10.so.0
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #17 ??
  • #0 __kernel_vsyscall 




----------- .xsession-errors ---------------------
** (nm-applet:3928): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.49" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:3928): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.49" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:3928): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.49" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:3928): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.49" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:3928): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.49" is not allowed to own the service "org.freedesktop.Networ
--------------------------------------------------
Comment 1 Philip Withnall 2008-07-05 01:05:08 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 426990 ***