Re: "Clock" has quit unexpectedly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



L wrote:


On Fri, Jan 9, 2009 at 12:30 AM, Steve <zephod@xxxxxxxxxx <mailto:zephod@xxxxxxxxxx>> wrote:


    ---- L <yuanlux@xxxxxxxxx <mailto:yuanlux@xxxxxxxxx>> wrote:
     > On Thu, Jan 8, 2009 at 2:24 PM, L <yuanlux@xxxxxxxxx
    <mailto:yuanlux@xxxxxxxxx>> wrote:
     >
     > > Whenever I click on gnome clock icon
    (/usr/libexec/clock-applet), I always got this error
     > >
     > >
     > > "Clock" has quit unexpectedly
     > > If you reload a panel object, it will automatically be added
    back to the panel.
     > >
     > > Do not reload/Reload

    Huh! I can repeat this problem on my system:

    $ uname -a
    Linux xxx 2.6.27.9-73.fc9.x86_64 #1 SMP Tue Dec 16 14:54:03 EST 2008
    x86_64 x86_64 x86_64 GNU/Linux

    When I first clicked on the clock, I got a dialog saying that
    evolution wanted access to the keyring. I granted this permission
    and the calendar dropped down from the clock applet. Then I clicked
    on the tasks arrow. This is when I got the crash. From then on,
    whenever I click on the clock it crashes. I get this line in
    /var/log/messages:

    gnome-keyring-daemon[2831]: couldn't read 4 bytes from client:

    This sounded familiar so I googled and found this:

    https://bugzilla.redhat.com/show_bug.cgi?id=418731

    This bug says that this was an upstream bug and that it has been
    fixed. Has the solution not filtered down yet or could this be a
    different problem?
    $ rpm -qa | grep evol
    evolution-data-server-debuginfo-2.22.1-2.fc9.x86_64
    evolution-conduits-2.22.3.1-1.fc9.x86_64
    evolution-2.22.3.1-1.fc9.x86_64
    evolution-data-server-2.22.3-2.fc9.i386
    evolution-spamassassin-2.22.3.1-1.fc9.x86_64
    evolution-webcal-2.21.92-1.fc9.x86_64
    evolution-webcal-debuginfo-2.21.92-1.fc9.x86_64
    evolution-exchange-2.22.3-1.fc9.x86_64
    evolution-data-server-2.22.3-2.fc9.x86_64
    evolution-debuginfo-2.22.1-2.fc9.x86_64
    evolution-bogofilter-2.22.3.1-1.fc9.x86_64
    evolution-data-server-doc-2.22.3-2.fc9.x86_64
    evolution-data-server-devel-2.22.3-2.fc9.x86_64
    evolution-data-server-devel-2.22.3-2.fc9.i386

    $ rpm -qa | grep keyring
    gnome-keyring-devel-2.22.3-1.fc9.x86_64
    gnome-keyring-2.22.3-1.fc9.i386
    gnome-python2-gnomekeyring-2.22.0-4.fc9.x86_64
    gnome-keyring-pam-2.22.3-1.fc9.x86_64
    gnome-keyring-2.22.3-1.fc9.x86_64

    Steve.



have you got any lucky fix on this matter?

    --
    fedora-list mailing list
    fedora-list@xxxxxxxxxx <mailto:fedora-list@xxxxxxxxxx>
    To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
    Guidelines:
    http://fedoraproject.org/wiki/Communicate/MailingListGuidelines


Did this happen after a "Switch User"?

I have seen where the panel applications died for gnome users after running switch user. On F7, I deleted all the files and directories in the /tmp directory for the user affected and then panel applets started working again. It still happens and I have yet to install F10 on this machine.


--
Robin Laing

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux