Description of problem:
Logged in GNOME session, when I am going to get logged out
from gnome session, it "hangs" with showing a popup window
which tells that at-spi-registryd-wrapper still running.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. get logged in GNOME session
2. try to get logged out
See attached 2 png files
Created attachment 360671 [details]
popup window asking about logout
The popup window says: "Are you going to get logged out from this
system?". Now click "Log out" button.
Created attachment 360672 [details]
popup window showing that at-spi-registry-wrapper hanging
Then this popup window appears, showing:
"The following program is still running:
at-spi-registry-wrapper (no responding)
Lock the screen / Cancel / Log out anyway"
The program that is crashing at logout is actually at-spi-registryd.
*** This bug has been marked as a duplicate of bug 519239 ***
Unfortunately I still see this issue (i.e. my comment 2)
Hmm, I can't reproduce this.
Anything special in your setup wrt to a11y ?
What does startup applications list for AT-SPI ?
(In reply to comment #5)
> Anything special in your setup wrt to a11y ?
> What does startup applications list for AT-SPI ?
Does this mean the list on gnome-session-properties or something
yeah, gnome-session-properties. Does it list at-spi-registryd wrapper twice ?
Well, at-spi-registryd seems to be registered only once.
My applications list enabled on gnome-session-properties is:
- /usr/sbin/restorecond -u
- gnome-keyring-daemon --start
- imsettings-start --cond-start -n -q
- gnome-at-visual -s
do you have any a11y tools (like orca) running in your session ?
Well, at least orca and dasher are not installed on my system.
(however with gnome-at-properties "Enable assistive technologies" is on)
With gnome-at-properties->Accessibility, "Run at start" is not checked on
either "Visual" or "Mobility".
This issue is still reproducible for me.
Sorry, I'm out of ideas here
Well, it seems that I no longer see this issue.
Thank you anyway. Once closing.
After yesterday's update now I see this issue again (note that "yesterday"
is in Japan). Currently seems 100% reproducible.
Can you find out what package makes that difference ? By downgrading selected packages ?
Well, I tried to downgrade some packages, however currently
I am at a loss...
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
Still observable with current F-13 GNOME session.
By the way it seems that this leaves the following message on
gnome-session: WARNING: Client '/org/gnome/SessionManager/Client2' failed to reply before timeout
A couple of minor comments:
I regular get this with F12. I had AT enabled to test bug 558963 (which I got because I had AT enabled to test something else).
I wonder why this isn't assigned to at-spi.
It seems to be the same as https://bugs.launchpad.net/ubuntu/+source/at-spi/+bug/477978
I get this message after /*logging in*/ with gdm.
The message appears for about 20 seconds, disappears and Gnome starts.
Unfortunately I get this message on my Dell Notebook and on my HP Desktop-PC. The message appears on both system after installation from the Fedora 13-DVD and does also with all updates installed.
I get the message on about 70% of all starts.
I think, I know why I become that message.
I always activate in my 'Startup Applications Preferences' the 'Automatically remember running applications when logging out'-button.
So maybe the process try to restarts at login-time. Is there a possibility to 'blacklist' the service from that feature?
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
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 prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.
Thank you for reporting this bug and we are sorry it could not be fixed.