Re: [orca-list] Arch users good news, found the cause of getting stuck in top panel issue

[Michael Whapples <mwhapples aim com>]

You actually seem to have spotted the real problem, not thorough enough 
checking on my part. So what happens when a menu is opened? I guess 
gives a good starting point for looking for what is going wrong.

Michael Whapples
On 01/-10/-28163 08:59 PM, Steve Holmes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> Sorry Dude,  No work here.
>
> I just went through trying the top level panel with the cirtificate
> keyring program near the top of the startup list both checked and
> unchecked and the effect was the same.  Now I did notice one thing; if
> I get into the top panel and tab around in there, all is fine and I
> can shift+ctrl+tab in and out of there as long as I don't open the
> menu.  Once I open any of the menus and/or execute a program from the
> menu, I'm forever stuck there and the only keystroke that works for me
> then is the ctrl+alt+backspace to get out and start over.
>
> On Tue, Apr 20, 2010 at 11:05:33PM +0100, Michael Whapples wrote:
>    
> > Hello,
> > I think it was last week someone reported a problem with getting
> > stuck in the top panel (using ArchLinux) and I had also encountered
> > it. Well some good news, I think I have the cause found. It seems to
> > be the gnome-keyring-daemon application.
> >
> > To fix this you can remove this application from the automatic start
> > up by going to the top menu (alt+f1), pressing right twice to get
> > the system menu, press down for the preferences menu, press right to
> > enter the menu and find start up applications. In the list find the
> > option for "Certificate and key storage" and press space to uncheck
> > it and then tab to close. You may need to log out and back in for
> > the change to take affect.
> >
> > Now the technical questions: This is loosing functionality (that
> > application must be there for a reason and we shouldn't miss out on
> > those features), so what is it about it causing the problem? Is it
> > something specific to how Arch starts it (eg. arguments)? Is there
> > an alternative which doesn't cause the problem?
> >
> > Michael Whapples
> > _______________________________________________
> > orca-list mailing list
> > orca-list gnome org
> > http://mail.gnome.org/mailman/listinfo/orca-list
> > Visit http://live.gnome.org/Orca for more information on Orca.
> > The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> > Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
> > Log bugs and feature requests at http://bugzilla.gnome.org
> > Find out how to help at http://live.gnome.org/Orca/HowCanIHelp
> >      
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEAREDAAYFAkvO37oACgkQWSjv55S0LfHVNgCdFIb5V/FaBAXLtzNnUwTl0vqP
> SPoAnR+zvM0JgHTds83OtL0k0pvZFJMg
> =TMkW
> -----END PGP SIGNATURE-----
>
>