GNOME Bugzilla – Bug 455300
crash in Clock:
Last modified: 2007-07-10 13:32:58 UTC
Version: 2.18.2 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve-Lime Icon Theme: Fedora Memory status: size: 30294016 vsize: 30294016 resident: 9637888 share: 7553024 rss: 9637888 rss_rlim: 4294967295 CPU usage: start_time: 1184002127 rtime: 477 utime: 383 stime: 94 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/clock-applet' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208408352 (LWP 2488)] (no debugging symbols found) 0x002e2402 in __kernel_vsyscall ()
+ Trace 146826
Thread 1 (Thread -1208408352 (LWP 2488))
----------- .xsession-errors (2259 sec old) --------------------- localuser:esam being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2291 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Initializing nautilus-image-converter extension XS[src/xmms-sid.c:xs_init:216]: xs_init() XS[src/xs_config.c:xs_init_configuration:164]: initializing configuration ... XS[src/xs_config.c:xs_read_configuration:265]: loading from config-file ... XS[src/xs_config.c:xs_read_configuration:320]: OK XS[src/xmms-sid.c:xs_reinit:163]: initializing emulator engine #1... XS[src/xmms-sid.c:xs_reinit:177]: init#1: OK, 1 XS[src/xmms-sid.c:xs_reinit:189]: init#2: OK, 0 XS[src/xmms-sid.c:xs_init:226]: OK --------------------------------------------------
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 357939 ***