Bug 1071907 - screen keyboard does not work for password pop up dialog
Summary: screen keyboard does not work for password pop up dialog
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 20
Hardware: All
OS: All
urgent
urgent
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-03 12:46 UTC by Moez Roy
Modified: 2014-05-29 23:26 UTC (History)
13 users (show)

Fixed In Version: gnome-shell-3.10.4-4.fc20
Clone Of:
Environment:
Last Closed: 2014-05-29 23:26:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 719451 0 None None None Never

Description Moez Roy 2014-03-03 12:46:42 UTC
screen keyboard does not work for password pop up dialog. for example when you want to install something you cannot type the password using the screen keyboard.

Comment 1 Parag Nemade 2014-03-03 13:00:40 UTC
give some example application which failed to use caribou.

Comment 2 Moez Roy 2014-03-03 16:56:56 UTC
(In reply to Parag from comment #1)
> give some example application which failed to use caribou.

Using Gnome-Shell: 
From yumex try to install (any) software. It will ask for admin password. Try entering the admin password using the on screen keyboad. It won't let you.

Comment 3 Moez Roy 2014-03-10 19:56:07 UTC
@Parag: Were you able to reproduce this with the above steps?

Comment 4 Parag Nemade 2014-03-11 02:59:50 UTC
Yes. I am able to reproduce this bug. The upstream bug for this is already opened at https://bugzilla.gnome.org/show_bug.cgi?id=719451

Comment 5 Moez Roy 2014-05-10 00:52:24 UTC
(In reply to Parag from comment #4)
> Yes. I am able to reproduce this bug. The upstream bug for this is already
> opened at https://bugzilla.gnome.org/show_bug.cgi?id=719451

any chance of backporting this fix?

thanks in advance

Comment 6 Parag Nemade 2014-05-10 09:27:31 UTC
This is fixed in gnome package, gnome-shell and I see there are no plans for backporting gnome-3.12 to F20. So you need to wait for F21...

Comment 7 Moez Roy 2014-05-21 15:02:20 UTC
(In reply to Parag from comment #6)
> This is fixed in gnome package, gnome-shell and I see there are no plans for
> backporting gnome-3.12 to F20. So you need to wait for F21...

Well I am hoping this patch can be applied to gnome-shell 3.10.x so this fix can come to F20.

Comment 8 Adam Williamson 2014-05-23 21:28:20 UTC
scratch build with the patches backported is running:

http://koji.fedoraproject.org/koji/taskinfo?taskID=6884102

can you grab that when it's done and let me know if it works? Thanks!

Comment 9 Moez Roy 2014-05-24 06:01:07 UTC
(In reply to Adam Williamson from comment #8)
> scratch build with the patches backported is running:
> 
> http://koji.fedoraproject.org/koji/taskinfo?taskID=6884102
> 
> can you grab that when it's done and let me know if it works? Thanks!

Thanks for that.

I can confirm the screen keyboard works with http://kojipkgs.fedoraproject.org//work/tasks/4104/6884104/gnome-shell-3.10.4-4.fc20.x86_64.rpm

Comment 10 Fedora Update System 2014-05-25 01:56:26 UTC
gnome-shell-3.10.4-4.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/gnome-shell-3.10.4-4.fc20

Comment 11 Fedora Update System 2014-05-25 23:28:59 UTC
Package gnome-shell-3.10.4-4.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-shell-3.10.4-4.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-6696/gnome-shell-3.10.4-4.fc20
then log in and leave karma (feedback).

Comment 12 Fedora Update System 2014-05-29 23:26:42 UTC
gnome-shell-3.10.4-4.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.