Bug 18110 - sddm login screen shows always message "CapsLock is turned on" when it's not true
Summary: sddm login screen shows always message "CapsLock is turned on" when it's not ...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-02 20:51 CEST by Piotr Mierzwinski
Modified: 2016-06-06 23:45 CEST (History)
2 users (show)

See Also:
Source RPM: sddm-0.13.0-2.mga6
CVE:
Status comment:


Attachments

Description Piotr Mierzwinski 2016-04-02 20:51:19 CEST
Description of problem:
I'm using sddm as login manager to login Plasma5 session. After Mageia starts on sddm login screen always is shown message saying "CapsLock is turned on". Of course CapsLock wasn't pressed before. Pressing CapsLock key nothing change.
I have default sddm configuration. Please check below:
[Autologin]
Relogin=false
Session=
User=

[General]
HaltCommand=
RebootCommand=

[Theme]
Current=breeze
CursorTheme=Adwaita

[Users]
HideShells=/sbin/nologin,/bin/false,/usr/sbin/nologin,/bin/true
HideUsers=mysql,apache,mldonkey
MaximumUid=65000
MinimumUid=500

Version-Release number of selected component (if applicable):
sddm-0.13.0-2.mga6

How reproducible:
Use sddm as login manager.

Steps to Reproduce:
1. install sddm
2. set sddm as default login manager (by systemctl for example)
2. restart system
3. check CapsLock info on login screen
Comment 1 Jüri Ivask 2016-04-03 20:04:03 CEST
Seems to happen only with breeze theme.
Upstream report here: https://github.com/sddm/sddm/issues/586

CC: (none) => jyri2000

Comment 2 Piotr Mierzwinski 2016-04-03 20:22:10 CEST
Bug is wired taking in consideration that breeze is the primary theme of Plasma 5 :/.
Bug report on OpenMandriva: https://issues.openmandriva.org/show_bug.cgi?id=1426 (url taken from above link)
Quoting last post from this report:
<cut>
 crisb 2016-03-16 22:42:58 CET

fixed in kguiaddons-5.20.0-2

caused by a missing req on Qt5X11Extras which was needed for the datasource to work with the modifier keys.
</cut>
I suppose this was fixed by maintainer of kguiaddons package.
Comment 3 Rémi Verschelde 2016-04-03 23:49:14 CEST
Assigning to Nicolas as SDDM maintainer. See comment 2 which suggests a fix directly in kf5guiaddons.

Assignee: bugsquad => mageia

Comment 4 David Walser 2016-06-06 17:30:50 CEST
Is this still valid?  KF5 has been updated in the past 2 months.
Comment 5 Rémi Verschelde 2016-06-06 18:25:37 CEST
I pushed kguiaddons-5.22.0-2.mga6 with new build dependencies on Qt5X11Extras (and X11), as they were indeed optional ones that we did not enable.

Could you check and confirm that it fixes the issue?
Comment 6 Barry Jackson 2016-06-06 22:51:56 CEST
Are you saying that kguiaddons should be required by something already installed?
I still have the issue and kguiaddons is not installed.

rpm -q kguiaddons
package kguiaddons is not installed.

CC: (none) => zen25000

Comment 7 Barry Jackson 2016-06-06 22:57:07 CEST
On last reboot it seems fixed, but I still don't have kguiaddons :\
I was certainly still seeing this yesterday but it's now gone.
Comment 8 Piotr Mierzwinski 2016-06-06 23:00:18 CEST
After last update I can confirm that now all is fine. I mean, using Breeze theme, there is no message "CapsLock is turned on" on login screen after Mageia started. CapsLock shows this message only when is turned on.

I also can't find it, but I'm able to find debuginfo package with this version.
Comment 9 Rémi Verschelde 2016-06-06 23:07:37 CEST
Only the SRPM is named kguiaddons, the binary RPMs are lib{,64}kf5guiaddons5.
Comment 10 Rémi Verschelde 2016-06-06 23:07:47 CEST
Closing as fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 11 Barry Jackson 2016-06-06 23:45:42 CEST
Ah right ;)
[baz@jackodesktop ~]$ rpm -qa -last|grep kf5guiaddons5
lib64kf5guiaddons5-5.22.0-2.mga6.x86_64       Mon 06 Jun 2016 18:17:42 BST

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