Bug 906701 - Malfunctions when current user is logged in automatically (User Accounts Setting)
Summary: Malfunctions when current user is logged in automatically (User Accounts Sett...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milan Crha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-01 09:23 UTC by Cedric Sodhi
Modified: 2015-02-17 14:44 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:44:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 907156 0 unspecified CLOSED gnome-keyring-daemon fails to unlock/spawn popup in shell when auto-loggedin 2021-02-22 00:41:40 UTC

Internal Links: 907156

Description Cedric Sodhi 2013-02-01 09:23:17 UTC
When the current user is logged in automatically as by configuration in "System Settings > User Accounts", evolution fails to fetch mail from IMAP Servers (saying "Timeout was reached") and also refuses to quit (meaning when I choose Quit, it does not quit and has to be killed with kill -1).

This is competely fresh install of F18 without any (significant) modifications.

Comment 1 Cedric Sodhi 2013-02-01 09:33:25 UTC
It appears this has something to do with the keyring (partially, at least) which is not unlocked. There appears to be a bug in the keyring, given that when I open "Passwords and Keys" and explicitly choose "Unlock" on the "Login" Keyring (or any other locked entity in that context), nothing happens (least of all does the ring get unlocked).

Comment 2 Matthew Barnes 2013-02-01 11:47:26 UTC
Evolution version?

Comment 3 Cedric Sodhi 2013-02-03 13:57:09 UTC
Evolution 3.6.2, more detail can be found in Bug 907156 .
On the side of Evolution, this appears primarily related to how Evolution depends on the keyring to respond.

Comment 4 Milan Crha 2013-02-04 07:50:15 UTC
I guess you face [1], with a modification of stale password requests, which leads down to gcr. You may get a backtrace of evolution and evolution-source-registry to see where it got stuck, with debuginfo packages for evolution-data-server and evolution being installed, of the same version as their binary packages (a 3.6.3 is available in repositories now).

You can get the backtrace with command like this:
    $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt

and similarly for the evolution-source-registry process.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=681815

Comment 5 Fedora End Of Life 2013-04-03 16:05:56 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 6 Fedora Admin XMLRPC Client 2014-09-04 14:28:43 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Fedora End Of Life 2015-01-09 17:38:28 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2015-02-17 14:44:11 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.