Password prompt "freezes" system during presence of a drop-down menu [hardy]

Bug #217551 reported by Nanley Chery
60
This bug affects 6 people
Affects Status Importance Assigned to Milestone
GNOME Keyring
Fix Released
High
gnome-keyring (Ubuntu)
Fix Released
High
Unassigned
Nominated for Hardy by Nanley Chery
Nominated for Intrepid by Denis Rut'kov
Nominated for Jaunty by Denis Rut'kov
Nominated for Karmic by Craig Hansen
network-manager-applet (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Hardy by Nanley Chery
Nominated for Intrepid by Denis Rut'kov
Nominated for Jaunty by Denis Rut'kov
Nominated for Karmic by Craig Hansen
vinagre (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Hardy by Nanley Chery
Nominated for Intrepid by Denis Rut'kov
Nominated for Jaunty by Denis Rut'kov
Nominated for Karmic by Craig Hansen

Bug Description

Binary package hint: gnome-keyring

While highlighting a security setting from the network manager drop-down menu (to manually connect to a network), I received a password prompt. This caused the computer to "freeze". I could move the mouse, but I couldn't click on anything; my only choice was to restart X. The prompt was caused by network manager automatically connecting to a preferred wireless network.

I have been able to reproduce this bug twice: the first time was accidentally and caused me to lose all my open windows - very frustrating. The second time was intentional. This should be fixed as it has a potentially catastrophic affect on wireless users (and maybe wired?): users can lose very important work if they have a blip in their internet connection - and possibly during other times when a admin password is asked for.

Fix: Show an error message stating that the mouse could not be grabbed.

Revision history for this message
Nanley Chery (nanoman) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

that's a network-manager wrong keyring usage

Revision history for this message
Eugenia Loli-Queru (eloli) wrote :

I have the EXACT same problem too. Gnome-keyring's popup password window freezes the desktop when I try to connect to my wifi router. For me, the ALT+CNTRL+Fn does not work, I had to completely kill ubuntu hardy.

Revision history for this message
Fabus (fabian-gebert-hh) wrote :

Exactly the same for me if the keyring asks for permission (deny, allow, always allow) when Evolution wants to access the google calendar password on a right click onto the corrensponding calendar item in the Evolution calendar view.
This bug already existed in Gutsy btw.

Revision history for this message
John Vivirito (gnomefreak) wrote :

Changed package task from network-manager to gnome-keyring because as i recall gnome-keyring handle all the Password prompts by default in Ubuntu/gnome

Revision history for this message
Sebastien Bacher (seb128) wrote :

why did you reassign to gnome-keyring? the issue seems to be that network manager call the gnome-keyring functions when it should not

Revision history for this message
John Vivirito (gnomefreak) wrote : Re: [Bug 217551] Re: Password prompt "freezes" system during presence of a drop-down menu [hardy]

Sebastien Bacher wrote:
> why did you reassign to gnome-keyring? the issue seems to be that
> network manager call the gnome-keyring functions when it should not
>
> ** Changed in: network-manager (Ubuntu)
> Sourcepackagename: gnome-keyring => network-manager
>
After re reading this bug a few times, it sounds like it is n-m but as I
understood it the password prompt caused the freeze.However isnt n-m
supposed to call gnome-key-ring when "root" or super user powers as needed?

--
Sincerely Yours,
     John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

Revision history for this message
Denis Rut'kov (dendron2000) wrote :

This bug is still present in Interpid.

Changed in network-manager:
status: New → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

could you pleaes update the bug description and add a simple step by step instruction on how to reproduce this?

Changed in network-manager:
status: Confirmed → Incomplete
Revision history for this message
Miloš Mandarić (mandzo18) wrote :

This is not network-manager bug, it's gnome-keyring bug.
Step to reproduce it:

1. Click to nm-applet and select connection(wired in my case)
2. Click again on nm-applet and move your mouse somewhere on any connection
3. The Unlock keyring appears and everything is blocked

To reproduce this bug you must be fast enough to do 2. before Unlock keyring appears.
When I do 2. it steal focus from keyring and you can't switch it to keyring in anyway because keyring has blocked everything.
This blocking feature of keyring is great, but also pretty annoying in this case.

Nanley Chery (nanoman)
Changed in gnome-keyring:
status: New → Confirmed
Revision history for this message
Fabus (fabian-gebert-hh) wrote :

Did you check if something like
$ sudo nano
yields "could not resolve hostname" on your computers or not?
Just mentioning that because since I solved that bug (adjusting the primary hostname and hostnames list in the network setup), the password dialog always works.

Revision history for this message
Miloš Mandarić (mandzo18) wrote :

No, I don't have that problem.

Revision history for this message
Fabus (fabian-gebert-hh) wrote :

I am sorry, I confused this bug with another bug. The one where the password prompt does not show up until you start the synaptic or whatever twice. That can be solved by solving that sudo-issue. Nevermind.

Revision history for this message
Denis Rut'kov (dendron2000) wrote :

Not fixed in intrepid, not fixed in jaunty. C'mon guys, this is REALLY irritating bug.

Revision history for this message
Denis Rut'kov (dendron2000) wrote :

No reason for 'incomplete' status.

Changed in network-manager:
status: Incomplete → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :

i wonder if the behaviour is the same with and without desktop effects (e.g. compiz vs. metacity)?

Revision history for this message
Denis Rut'kov (dendron2000) wrote :

Yes, same behavior.

Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in gnome-keyring:
assignee: nobody → desktop-bugs
importance: Undecided → High
status: Confirmed → Triaged
Revision history for this message
CrYpTiC_MauleR (crypticmauler) wrote :

I am having the same problem as well in Jaunty when network tries to connect to wireless. Sometimes I can click the power button on laptop to have a graceful shutdown other times even that does not work and I have forced to power down. Oddly this issue only occurs when I use the Broadcom STA driver, if I use the B43 driver it does not freeze the system. The moment the password prompt comes up the system will freeze. What drivers is everyone else using when this problem arises?

Revision history for this message
Fabus (fabian-gebert-hh) wrote :

It also occurs with iwlagn (Intel 4965 AGN)

Changed in gnome-keyring:
status: Unknown → Incomplete
Revision history for this message
pauls (paulatgm) wrote :

same bad news here on jaunty. broadcom 4328 with STA driver. It's a hard freeze that does not respond to Alt-SysRq-REISUB. have to hit power off button.

Revision history for this message
Karl Larsen (klarsen1) wrote :

 1. What is a key ring? Why is the key ring called when I try to turn on WiFi on Jaunty?
  2. I click on the WiFi symbol for my WiFi router and it should connect. But it does not.
 3. It brings up every time now a key ring panel that says there is an error in "/usr/bin/nm-applet" which wants to use the "default keyring, but it is locked.

When I first had Jaunty working it made me give a key ring a password. I gave it karl as a password because it was stupid. This worked for about a month. Now it is wanting my system password to I gather, unlock the default keyring, whatever that is....

The changes will lead to not being able to get WiFi working.

Revision history for this message
Karl Larsen (klarsen1) wrote :

Here is some fixes for Jaunty and Intrepid. In both with a terminal erase the keyring in the file
/home/your-name/.gnome2/. When you reboot your computer will not know how to start NetworkManager but you can train it again, like it is a new computer.

You can keep it away from keyring by hitting "deny" every time a stupid keyring panel comes up. But now You must use the password for your Wireless Router every time.

You can use keyring by giving it a real simple password like do and then whenever you login you just tell keyring do.

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

Also the remote desktop viewer "vinagre" has this problem (I'm in karmic now).
Should I add the package vinagre to the bug?

Revision history for this message
Karl Larsen (klarsen1) wrote : Re: [Bug 217551] Re: Password prompt "freezes" system during presence of a drop-down menu [hardy]

Nicolò Chieffo wrote:
> Also the remote desktop viewer "vinagre" has this problem (I'm in karmic now).
> Should I add the package vinagre to the bug?
>
 I do not know what vinagre is. I don't use it so can't
answer you. Sorry

Karl

--

 Karl F. Larsen, AKA K5DI
 Linux User
 #450462 http://counter.li.org.
         Key ID = 3951B48D

Revision history for this message
AB (aberte) wrote :

Note that the keyring dialog, when it cames to screen, it takes mouse and keyboard focus, even if you try to click elsewhere. It happens to me with Karmic.

Revision history for this message
Craig Hansen (craig-hansen) wrote :

I'll confirm that I get the problem with "vinagre" in Karmic as well. It happens if you hit a menu item immediately after starting the first remote session. The focus doesn't change to the key-ring pop-up, so you can't answer or dismiss the pop-up.

Changed in gnome-keyring:
status: Incomplete → Confirmed
Changed in gnome-keyring:
status: Confirmed → Fix Released
Changed in gnome-keyring:
importance: Unknown → High
Revision history for this message
Karl Larsen (klarsen1) wrote :

   I now have Ubuntu version 10.04.1 on my laptop and it uses wifi and to my great pleasure I selected the proper source and now it comes up every time. No sign of a keyring. I think the bug has been fixed in version 10.04.

Revision history for this message
Josh Benner (sjbenner) wrote :

I'm experiencing a similar issue on 10.04. When I log into my desktop session, gnome-do has keyboard focus but the keyring passwd prompt is the top-most window. No mouse cursor and I can not take keyboard focus from gnome-do.

Workarounds:
1) close gnome do <win>+<space>
2) set gnome-do preference 'hide window on first launch'

Revision history for this message
Grega Fajdiga (gregor-fajdiga-guest) wrote :

I have installed ubuntu 10.10 and am having the same problem as Josh Benner. If I install gnome-do, I get a gnome-keyring password prompt, and then the same problem as described above. The system freezes, although I can still move my mouse. I had to remove gnome-do until this issue is resolved :-(

Revision history for this message
Thomas Hood (jdthood) wrote :

Is this bug reproducible in Ubuntu 12.04?

Thomas Hood (jdthood)
Changed in network-manager (Ubuntu):
status: Confirmed → Incomplete
Thomas Hood (jdthood)
affects: network-manager (Ubuntu) → network-manager-applet (Ubuntu)
Changed in gnome-keyring (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
Changed in vinagre (Ubuntu):
status: New → Incomplete
Changed in gnome-keyring (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

I'm closing this bug due to no response from the reporters. Some have said it's fix. If anyone is still affected, please comment and we will reopen the bug again.

Changed in gnome-keyring (Ubuntu):
status: Incomplete → Invalid
status: Invalid → Fix Released
Changed in network-manager-applet (Ubuntu):
status: Incomplete → Fix Released
Changed in vinagre (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.