Re: Evolution fails to ask for password giving total freeze

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

 



On Wed, 2013-02-27 at 13:38 +0000, John Austin wrote:
> On Wed, 2013-02-27 at 11:40 +0000, John Austin wrote:
> > Hi
> > 
> > Hoping someone can help - my main app is failing!
> > 
> > Following a recent update evolution no longer functions
> > 
> > An error is given in orange window
> > 
> > "Error while performing operation
> > IMAP command failed: Please login first"
> > 
> > This is normal, however no Popup Window is given to permit login
> > 
> > Evo is then frozen
> > 
> > On a second machine that I have not updated today evo is fine, the popup
> > appears
> > (This is using the same system login and mail account, ldap and NFS4)
> > ie same home directory and hence the same ~/.config/evolution directory
> > 
> > yum update on the working machine shows that it wants to update the rpms
> > listed below - needless to say I haven't installed the updates on this
> > machine
> > 
> > It's not the kernel as I booted from the previous kernel on the
> > failing machine and it still fails
> > 
> > Any thoughts as to which of the following is the culprit ?
> > 
> > Has anyone else the same problem ?
> > 
> > Thanks
> > 
> > John
> > 
> > 
> 
> yum downgrade gcr
> 
> From gcr.x86_64 0:3.6.2-3.fc18 to gcr-3.6.2-1.fc18.x86_64
> 
> followed by a reboot seems to fix the problem but I am
> still getting nasty messages
> 
> ja@minix ~ 2$ evolution
> 
> ** (evolution:3091): WARNING **: Couldn't register with accessibility
> bus: Did not receive a reply. Possible causes include: the remote
> application did not send a reply, the message bus security policy
> blocked the reply, the reply timeout expired, or the network connection
> was broken.
> 
> ** (evolution-alarm-notify:3117): WARNING **: Couldn't register with
> accessibility bus: Did not receive a reply. Possible causes include: the
> remote application did not send a reply, the message bus security policy
> blocked the reply, the reply timeout expired, or the network connection
> was broken.
> 
> cat /var/log/messages
> Feb 27 13:17:24 minix gcr-prompter[3134]: atk_bridge_adaptor_cleanup:
> assertion `inited' failed
> 
> 
> Is this just my setup or something more?
> 
> I'm using XFCE, konsole, lightdm, ...
> 
> If there is any confirmation that it is not just me then I will
> post a bugzilla
> 
> John
> 
> 
This would appear to be associated with
https://bugzilla.redhat.com/show_bug.cgi?id=907156

gnome-keyring-daemon fails to unlock/spawn popup in shell when
auto-loggedin

John





-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux