keyboard accessibility problem with knetworkmanager error dialog

Bug #134302 reported by Michael Blakeley
4
Affects Status Importance Assigned to Milestone
knetworkmanager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: knetworkmanager

10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

$ uname -a
Linux mblakele-lt 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64 GNU/Linux
$ apt-show-versions knetworkmanager
knetworkmanager 1:0.2~r686534-0ubuntu1 installed: No available version in archive
$ apt-show-versions network-manager
network-manager/gutsy uptodate 0.6.5-0ubuntu9

Sometimes knetworkmanager can't seem to connect to a network, and displays an error message "Connection failure\nCould not connect to the network fubar\n[OK]".

Unexpected behavior: the user cannot hit "return" or use any other keyboard combination to get rid of the error message: keyboard input is going to a foreground application, not to knetworkmanager. The "ok" button *must* be clicked with a mouse. This is an accessibility problem, per KDE's UI policies (see http://accessibility.kde.org/developer/).

Suggested fix: turn this error message into a notification, instead, like the "link up" notification and other knetworkmanager messages. These notifications are configurable via ordinary KDE mechanisms, and fade out automatically after a few seconds.

I'll attach a screenshot to show the problem.

Revision history for this message
Michael Blakeley (mike+ubuntu) wrote :
Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 beta or later?

Changed in knetworkmanager:
status: New → Incomplete
Revision history for this message
Michael Blakeley (mike+ubuntu) wrote :

No, because knetworkmanager doesn't notify me about connection failures at all. I suppose you could call that an improvement.

network-manager-kde/intrepid uptodate 1:0.7svn864988-0ubuntu1

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

Any news on this? Is this still an issue for you in Ubuntu 9.04 or Ubuntu 9.10? Thank you

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

I suppose that even if things could be improved, they wouldn't be since the KDE3 version of KNM is no longer developed. We could probably count this as fixed.

Changed in knetworkmanager (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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