After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 573819 - User interface becomes unresponsive when Network manager applet attempts to enter default keyring
User interface becomes unresponsive when Network manager applet attempts to ...
Status: RESOLVED DUPLICATE of bug 571423
Product: seahorse
Classification: Applications
Component: Daemon
2.24.x
Other All
: Normal normal
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2009-03-02 20:52 UTC by Arto Huotari
Modified: 2009-03-03 00:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Arto Huotari 2009-03-02 20:52:24 UTC
Steps to reproduce:
1. Setup wireless network. Type restricted WEP shared password. 
2. Enable autologin (system -> administration -> login window -> security)
3. Shut down computer
4. Shut down wireless network
5. Turn on computer
6. When desktop has loaded open network manager applet menu with left mouse button. (When this bug was reproduced there were three wireless networks available in addtion to the one that was shut down. Computer was not connected to these networks) Keep the menu open like you would wait for the network to come available! With NM-applet menu I mean the quick laucher on the desktop panel. This quick launcer has two computer screens on it when there is no wireless network connected and it shows a blue bar graph when the wireless network is connected.
7. Turn on wireless network and wait until network has booted. 
8. When the NM-applet attempts to access the default keyring gnome (seahorse?) asks for password (allow of deny access to keyring). At this point the whole user interface will freeze. Note at this point you will have the NM-applet menu open and the password dialogue open. Mouse pointed can be moved but nothing can be done.


Stack trace:
Not available

Other information:
I sincerely do not know if Seahorse is the crashing application since the whole desktop freezez but I believe it is more useful to file this somewhere than nowhere.
Comment 1 Arto Huotari 2009-03-02 21:01:27 UTC
I set the priority to normal since despite that the bug is a crasher it causes only minor inconvenience and can be easily worked around by not opening the menu or by not using the automatic login.  

Comment 2 Stef Walter 2009-03-03 00:56:11 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 571423 ***