GNOME Bugzilla – Bug 554211
crash in Movie Player: Changing volume (from bo...
Last modified: 2008-09-28 19:38:10 UTC
Version: 2.22.2 What were you doing when the application crashed? Changing volume (from bottom right widget) in full-screen mode while a video was playing. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Wed Sep 10 16:46:13 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 149553152 vsize: 149553152 resident: 60944384 share: 29405184 rss: 60944384 rss_rlim: 4294967295 CPU usage: start_time: 1222626758 rtime: 1575 utime: 1455 stime: 120 cutime:3 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' [Thread debugging using libthread_db enabled] [New Thread 0xb6817720 (LWP 3263)] [New Thread 0xb194cb90 (LWP 3271)] [New Thread 0xb214db90 (LWP 3270)] [New Thread 0xb2969b90 (LWP 3269)] [New Thread 0xb39b1b90 (LWP 3268)] [New Thread 0xb41b2b90 (LWP 3267)] [New Thread 0xb5557b90 (LWP 3266)] [New Thread 0xb6201b90 (LWP 3265)] 0xb7f3d424 in __kernel_vsyscall ()
+ Trace 207504
Thread 4 (Thread 0xb2969b90 (LWP 3269))
----------- .xsession-errors --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/hercules:/tmp/.ICE-unix/2816 Shutdown failed or nothing to shut down. ** (gnome-settings-daemon:2874): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Aucun fichier ou répertoire de ce type Avertissement du gestionnaire de fenêtres : La lecture du fichier de session enregistré /home/alex/.metacity/sessions/default0.ms a échoué : Failed to open file '/home/alex/.metacity/sessions/de Initializing gnome-mount extension seahorse nautilus module initialized Cannot access memory at address 0x9 Cannot access memory at address 0x9 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 527572 ***