GNOME Bugzilla – Bug 435398
crash in Movie Player: trying to start totem
Last modified: 2007-05-03 06:46:47 UTC
Version: 2.18.1 What were you doing when the application crashed? trying to start totem Distribution: Debian lenny/sid Gnome Release: 2.18.1 2007-04-29 (GARNOME) BugBuddy Version: 2.18.1 System: Linux 2.6.21.1 #1 PREEMPT Fri Apr 27 18:37:44 MST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 54165504 vsize: 54165504 resident: 24944640 share: 13393920 rss: 24944640 rss_rlim: 4294967295 CPU usage: start_time: 1178166341 rtime: 77 utime: 72 stime: 5 cutime:3 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/home/boat/garnome/bin/totem' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227827520 (LWP 13647)] [New Thread -1242920048 (LWP 13650)] [New Thread -1234527344 (LWP 13649)] 0xb7f42410 in __kernel_vsyscall ()
+ Trace 132036
Thread 1 (Thread -1227827520 (LWP 13647))
----------- .xsession-errors --------------------- Reason: You do not have a decoder installed to handle this file. You might need to install the necessary plugins.. ***MEMORY-WARNING***: gnome-terminal[13559]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this CalDAV Eplugin starting up ... ** (evolution-2.12:13587): DEBUG: mailto URL command: evolution-2.12 %s ** (evolution-2.12:13587): DEBUG: mailto URL program: evolution-2.12 Loading Spamassasin as the default junk plugin CalDAV Eplugin starting up ... ** (evolution-2.12:13629): DEBUG: mailto URL command: evolution-2.12 %s ** (evolution-2.12:13629): DEBUG: mailto URL program: evolution-2.12 Loading Spamassasin as the default junk plugin ** Message: totem_playlist_add_one_mrl (): r1.rm rtsp://212.77.1.198/farm/ra_source/encoder/r1.rm (null) Cannot access memory at address 0xa Cannot access memory at address 0xa --------------------------------------------------
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 408544 ***