GNOME Bugzilla – Bug 527082
crash in Clock: Logged in and it crashed...
Last modified: 2008-04-09 11:27:14 UTC
Version: 2.22.1 What were you doing when the application crashed? Logged in and it crashed on me. Distribution: Fedora release 8.92 (Rawhide) Gnome Release: 2.22.1 2008-04-07 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.25-0.204.rc8.git4.fc9.i686 #1 SMP Mon Apr 7 11:33:46 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499901 Selinux: No Accessibility: Enabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 66777088 vsize: 66777088 resident: 18178048 share: 12787712 rss: 18178048 rss_rlim: 4294967295 CPU usage: start_time: 1207726063 rtime: 37 utime: 32 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/clock-applet' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb7fbd730 (LWP 3898)] 0x00131416 in __kernel_vsyscall ()
+ Trace 194692
Thread 1 (Thread 0xb7fbd730 (LWP 3898))
----------- .xsession-errors (50 sec old) --------------------- evolution-alarm-notify-Message: Wed Apr 9 09:27:39 2008 CalDAV Eplugin starting up ... Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:3766): DEBUG: mailto URL command: evolution %s ** (evolution:3766): DEBUG: mailto URL program: evolution (rhythmbox:3904): Rhythmbox-WARNING **: Could not open device /dev/radio0 Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::odd-row-color' of type `GdkColor' from rc file value "((GString*) 0x9b784b0)" of type `GString' Couldn't open sftp://kmaraas@window.gnome.org:22/home/users/kmaraas/public_html/calendar.ics: Tidsavbrudd nådd (evolution:3766): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: Ingen treff) --------------------------------------------------
fixed in 2.22.1.1 *** This bug has been marked as a duplicate of 527016 ***