Unable to change status using the keyboard

Bug #154816 reported by Nicolas Chachereau
10
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

In Pidgin's main window (Buddy List), use the keyboard to tab to the widget at the bottom, where you can change the status. When it has focus, activate it (using Enter or Space).

Expected Behaviour: the status list is shown, and it is possible to modify one's status using the keyboard. This is exactly what happens if you click on the widget instead of pressing enter or space while it has focus.

Observed Behaviour: the widget shows a "pushed" status, but the list is not shown and you can't change your status using the keyboard arrows.

Version information:
I updated Ubuntu to Gutsy Gibbon two days ago. The "About" dialog box says "Pidgin 2.2.1", and `aptitude show pidgin` says "Version : 1:2.2.1-1ubuntu4".

ProblemType: Bug
Architecture: i386
Date: Sat Oct 20 12:03:02 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.2.1-1ubuntu4
PackageArchitecture: i386
ProcCmdline: pidgin
ProcCwd: /home/nico
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=fr_CH.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux sous-sol-nc 2.6.22-14-386 #1 Sun Oct 14 22:36:54 GMT 2007 i686 GNU/Linux

Tags: apport-bug
Revision history for this message
Nicolas Chachereau (nicolas-chachereau) wrote :
Revision history for this message
Joanmarie (joanmarie-diggs-deactivatedaccount) wrote :

Confirmed. I just built 2.2.1 from the pidgin sourceforge source and things work as expected.

Revision history for this message
Joanmarie (joanmarie-diggs-deactivatedaccount) wrote :

2.2.2 came via Hardy today and the problem is fixed there. Given that this is a significant accessibility issue for people who are blind, I would request that the upgrade to pidgin 2.2.2 be included for Gutsy users.

Thanks!

Revision history for this message
Marlon Cisternas Milla (mcisternas-deactivatedaccount) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in pidgin:
status: New → Invalid
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.