Dialog provides no feedback after entering valid password

Bug #855177 reported by Marc Deslauriers on 2011-09-21
This bug affects 10 people
Affects Status Importance Assigned to Milestone
unity-greeter (Ubuntu)

Bug Description

At the login screen, after typing the user's password and hitting enter, the password dialog behaves unexpectedly, leading the user into believing something went wrong.

What currently happens:
1- user enters password, hits enter
2- Password box clears itself, and remains active
3- Nothing happens for a second, making the user think he needs to try his password again
4- Desktop logs in

What should happen:
1- user enters password, hits enter
2- Password remains in password box, password box becomes inactive
4- Desktop logs in

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: unity-greeter 0.0.8-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Tue Sep 20 19:57:15 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
SourcePackage: unity-greeter
UpgradeStatus: Upgraded to oneiric on 2011-08-16 (35 days ago)

Marc Deslauriers (mdeslaur) wrote :
Changed in unity-greeter (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Matt Fischer (mfisch) on 2012-06-30
summary: - Dialog behaves unexpectedly after entering password
+ Dialog provides no feedback after entering valid password
tags: added: raring

I can confirm that this bug is still present in Ubuntu 13.04.

Typically, you'd expect the cursor to change to something progressive (like an hour-glass or an animated cursor) to indicate that Ubuntu is "trying to do something". Instead, the system always seems to be locked up until login completes.

Additionally, in 13.04, there is a little icon like this (next to where you enter your password):

The only difference is that THIS TOO is LOCKED UP during login. It does NOT spin (like the one in the link above does).

Mitch Claborn (mitch-news) wrote :

A year and a half seems a long time to wait for a fix on what seems like a simple problem.

Well, you have to understand, when it gets marked as "medium" importance, that's practically equivalent to "won't fix" these days.

Apparently, the bug volume outweighs the number of developers these days. More of us need to step up, and download the code associated with these bugs, and submit proposed fixes.

I have programming experience, and I pick up on new languages very quickly, but I'm I'm always unclear on:

1) Where do I get the current code,
2) How do I submit a proposed change.

Once, I do this on one project, I'll do it on many. If some one will spoon feed me a little on one, I'll go on to help a lot on others.

So, would this be the authoritative place I'd get the current code:


If so, what environment would I want to pull it up in. Is it just text files?

Then we'd need to locate in code where that little spin icon is in code, and figure out how to make it actually spin.

We'd also want to locate the event where the password is submitted, and change the cursor to something besides the static arrow upon submission.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers