GNOME Bugzilla – Bug 528107
crash in Clock: noyhinh
Last modified: 2008-04-15 06:20:28 UTC
Version: 2.22.0 What were you doing when the application crashed? noyhinh Distribution: Unknown Gnome Release: 2.22.0 2008-03-11 (Foresight Linux) BugBuddy Version: 2.22.0 System: Linux 2.6.23.16-0.0.1.smp.gcc4.1.x86_64 #1 SMP Mon Feb 11 22:41:48 EST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Foresight Icon Theme: Tango Memory status: size: 335556608 vsize: 335556608 resident: 16945152 share: 10653696 rss: 16945152 rss_rlim: 18446744073709551615 CPU usage: start_time: 1208179542 rtime: 276 utime: 255 stime: 21 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/clock-applet' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x2b25d41ea2d0 (LWP 3192)] 0x00002b25cdda79ff in waitpid () from /lib64/libpthread.so.0
+ Trace 195231
Thread 1 (Thread 0x2b25d41ea2d0 (LWP 3192))
----------- .xsession-errors (2058 sec old) --------------------- 4/14/2008 6:47:46 AM [Info]: Updated first results for 'c'. 4/14/2008 6:47:46 AM [Info]: Updated first results for 'd'. 4/14/2008 6:47:46 AM [Info]: Updated first results for 'e'. 4/14/2008 6:47:46 AM [Info]: Updated first results for 'f'. 4/14/2008 6:47:46 AM [Info]: Updated first results for 'g'. 4/14/2008 6:47:46 AM [Info]: Updated first results for 'h'. 4/14/2008 6:47:46 AM [Info]: Updated first results for 'i'. 4/14/2008 6:47:46 AM [Info]: Updated first results for 'j'. Could not fetch recommendations: Error: NameResolutionFailure ** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3 GStreamer stream error: CodecNotFound gnome-mount 0.7 4/14/2008 6:48:46 AM [Info]: Updated "Directory Scanner" Item Source. ...Too much output, ignoring rest... --------------------------------------------------
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 525754 ***