Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-12-01 Thread Shai Berger
On Mon, 2 Dec 2019 07:54:21 +0100
"luca.pedrielli"  wrote:

> Il 01/12/19 19:18, Lisandro Damián Nicanor Pérez Meyer ha scritto:
> >
> > On Thu, 28 Nov 2019 at 07:06, luca.pedrielli 
> > wrote:  
> >> Il 27/11/19 15:14, Franklin Weng ha scritto:
> > >> Thanks.  With your survey I found a bug report for
> > >> plasma-workspace:
> > >>
> > >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429
> > >>
> > >> I've replied it.
> >> pkg problem?  
> > Indeed it was! Thanks **a lot** fro the triaging and the bug report!
> >
> > I have just uploaded the fix, so I guess it will be available in the
> > next mirror push.
> >  
> Installed and working in sid.
> 

Thanks a lot, Franklin, Luca and Lisandro!



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-12-01 Thread luca.pedrielli

Il 01/12/19 19:18, Lisandro Damián Nicanor Pérez Meyer ha scritto:

Hi!

On Thu, 28 Nov 2019 at 07:06, luca.pedrielli  wrote:

Il 27/11/19 15:14, Franklin Weng ha scritto:

luca.pedrielli 於 2019/11/27 下午6:25 寫道:

seems search for libkmodifierkey_xcb.so ..that I have not found in
debian

maybe plasma_engine_keystate.so have some ploblems

sddm themes, keyboardindicator, but also others plasmoids like
keystate, use qml scripts where the engine is keystate.

they work in buster, but not in testing.

Thanks.  With your survey I found a bug report for plasma-workspace:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429

I've replied it.


Thanks, Franklin


Hi Franklin,

I have rebuilded kguiaddons-5.62 on my pc.

a kmodifierkey_xcb.so is genereted, but non included in the .deb, so I have 
copied it in

/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/

and the error is gone.

logout/login and the key indicator(in some way) works.

pkg problem?

+

Indeed it was! Thanks **a lot** fro the triaging and the bug report!

I have just uploaded the fix, so I guess it will be available in the
next mirror push.

Once again, thanks a lot!!!




Installed and working in sid.

Thanks

--
Saluti, Luca Pedrielli



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-12-01 Thread Lisandro Damián Nicanor Pérez Meyer
Hi!

On Thu, 28 Nov 2019 at 07:06, luca.pedrielli  wrote:
>
> Il 27/11/19 15:14, Franklin Weng ha scritto:
>
> luca.pedrielli 於 2019/11/27 下午6:25 寫道:
>
> seems search for libkmodifierkey_xcb.so ..that I have not found in
> debian
>
> maybe plasma_engine_keystate.so have some ploblems
>
> sddm themes, keyboardindicator, but also others plasmoids like
> keystate, use qml scripts where the engine is keystate.
>
> they work in buster, but not in testing.
>
> Thanks.  With your survey I found a bug report for plasma-workspace:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429
>
> I've replied it.
>
>
> Thanks, Franklin
>
>
> Hi Franklin,
>
> I have rebuilded kguiaddons-5.62 on my pc.
>
> a kmodifierkey_xcb.so is genereted, but non included in the .deb, so I have 
> copied it in
>
> /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/
>
> and the error is gone.
>
> logout/login and the key indicator(in some way) works.
>
> pkg problem?
+

Indeed it was! Thanks **a lot** fro the triaging and the bug report!

I have just uploaded the fix, so I guess it will be available in the
next mirror push.

Once again, thanks a lot!!!



-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-30 Thread Jimmy Johnson

On 11/28/19 2:05 AM, luca.pedrielli wrote:

have rebuilded kguiaddons-5.62 on my pc.

a kmodifierkey_xcb.so is genereted, but non included in the .deb, so I 
have copied it in


/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/

and the error is gone.

logout/login and the key indicator(in some way) works.

pkg problem?


Saluti, Luca Pedrielli


Hi Luca, I upgraded to see the problem, and then downgraded 
'libkf5guiaddons5' to buster, did a 'apt-mark hold' on the package and 
solved the problem. Now I guess we wait for this group calling itself 
debian "linux" to catch up.


I run plasma5.17, framework5.64, qt5.12 on a couple other systems, never 
seen this problem before.


Thanks for pointing to the problem.
--
Jimmy Johnson

19.09.KDE5 - Intel i7-3540M - EXT4 at sda10
Registered Linux User #380263



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-28 Thread Franklin Weng
Hi Luca,

luca.pedrielli  於 2019年11月28日 週四 18:06 寫道:

> Il 27/11/19 15:14, Franklin Weng ha scritto:
>
> luca.pedrielli 於 2019/11/27 下午6:25 寫道:
>
> seems search for libkmodifierkey_xcb.so ..that I have not found in
> debian
>
> maybe plasma_engine_keystate.so have some ploblems
>
> sddm themes, keyboardindicator, but also others plasmoids like
> keystate, use qml scripts where the engine is keystate.
>
> they work in buster, but not in testing.
>
>
> Thanks.  With your survey I found a bug report for plasma-workspace:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429
>
> I've replied it.
>
>
> Thanks, Franklin
>
>
>
> Hi Franklin,
>
> I have rebuilded kguiaddons-5.62 on my pc.
>
> a kmodifierkey_xcb.so is genereted, but non included in the .deb, so I
> have copied it in
>
> /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/
>
> and the error is gone.
>
> logout/login and the key indicator(in some way) works.
>
> pkg problem?
>

Maybe, but I'm not able to find the file with apt-file in Buster, so I'm
not sure why Buster could work.

Could you please reply to the bug report, and probably attach the so file,
so that the reporter can temporarily solve his problem.  This issue seems
to bother him very much.


Regards, Franklin


Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-28 Thread luca.pedrielli

Il 27/11/19 15:14, Franklin Weng ha scritto:

luca.pedrielli 於 2019/11/27 下午6:25 寫道:

seems search for libkmodifierkey_xcb.so ..that I have not found in
debian

maybe plasma_engine_keystate.so have some ploblems

sddm themes, keyboardindicator, but also others plasmoids like
keystate, use qml scripts where the engine is keystate.

they work in buster, but not in testing.


Thanks.  With your survey I found a bug report for plasma-workspace:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429

I've replied it.


Thanks, Franklin



also systemsettings -> numlock on starting session is working too

--
Saluti, Luca Pedrielli



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-28 Thread luca.pedrielli

Il 27/11/19 15:14, Franklin Weng ha scritto:

luca.pedrielli 於 2019/11/27 下午6:25 寫道:

seems search for libkmodifierkey_xcb.so ..that I have not found in
debian

maybe plasma_engine_keystate.so have some ploblems

sddm themes, keyboardindicator, but also others plasmoids like
keystate, use qml scripts where the engine is keystate.

they work in buster, but not in testing.


Thanks.  With your survey I found a bug report for plasma-workspace:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429

I've replied it.


Thanks, Franklin



with kmodifierkey_xcb.so also sddm capslock alert is working ;)

--
Saluti, Luca Pedrielli



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-28 Thread luca.pedrielli

Il 27/11/19 15:14, Franklin Weng ha scritto:

luca.pedrielli 於 2019/11/27 下午6:25 寫道:

seems search for libkmodifierkey_xcb.so ..that I have not found in
debian

maybe plasma_engine_keystate.so have some ploblems

sddm themes, keyboardindicator, but also others plasmoids like
keystate, use qml scripts where the engine is keystate.

they work in buster, but not in testing.


Thanks.  With your survey I found a bug report for plasma-workspace:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429

I've replied it.


Thanks, Franklin



Hi Franklin,

I have rebuilded kguiaddons-5.62 on my pc.

a kmodifierkey_xcb.so is genereted, but non included in the .deb, so I 
have copied it in


/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/

and the error is gone.

logout/login and the key indicator(in some way) works.

pkg problem?


Saluti, Luca Pedrielli



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-27 Thread luca.pedrielli

Il 27/11/19 15:14, Franklin Weng ha scritto:

luca.pedrielli 於 2019/11/27 下午6:25 寫道:

seems search for libkmodifierkey_xcb.so ..that I have not found in
debian

maybe plasma_engine_keystate.so have some ploblems

sddm themes, keyboardindicator, but also others plasmoids like
keystate, use qml scripts where the engine is keystate.

they work in buster, but not in testing.


Thanks.  With your survey I found a bug report for plasma-workspace:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429

I've replied it.


Thanks, Franklin



Hi Franklin, thanks for bug-reporting.
Let's see what happens ;)

--
Saluti, Luca Pedrielli



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-27 Thread Franklin Weng

luca.pedrielli 於 2019/11/27 下午6:25 寫道:
>
> seems search for libkmodifierkey_xcb.so ..that I have not found in
> debian
>
> maybe plasma_engine_keystate.so have some ploblems
>
> sddm themes, keyboardindicator, but also others plasmoids like
> keystate, use qml scripts where the engine is keystate.
>
> they work in buster, but not in testing.
>

Thanks.  With your survey I found a bug report for plasma-workspace:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942429

I've replied it.


Thanks, Franklin




signature.asc
Description: OpenPGP digital signature


Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-27 Thread luca.pedrielli

Il 27/11/19 10:54, Franklin Weng ha scritto:



Jimmy Johnson 於 2019/11/27 下午2:08 寫道:

On 11/26/19 4:06 PM, Franklin Weng wrote:


Jimmy Johnson 於 2019/11/27 上午6:55 寫道:

On 11/26/19 11:26 AM, Shai Berger wrote:

For some reason, both Jimmy and Luca insist on connecting this to the
wrong problem:

On Tue, 26 Nov 2019 01:30:01 -0800
Jimmy Johnson  wrote:


On 11/25/19 7:10 AM, Franklin Weng wrote:

luca.pedrielli  於 2019年11月25日 週一 22:44


Numlock problems had already been reported

https://lists.debian.org/debian-kde/2019/09/msg00033.html


Not sure, but it looks like not the same problem.  My problem is
about the indicator not the status itself.  The NumLock/Capslock
status is correct according to the xset -q.



The settings for numlock have changed in testing kde5.
I think the systemsettings, input device module is suppose to be
handling numlock on/off at sddm start.



And Luca, later:


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872


Everything Luca and Jimmy are mentioning is about the state of
numlock when sddm or plasma start.

This is *not* what Franklin or I are talking about. We are talking
about Caps/Num Lock being at the state they should be, as set by
pressing the relevant keys. It is only the visual indicators which 
are
not working -- the systray icons in plasma, and the caps-is-on 
warning

in the lock or login screen.



Listen to me! Remove your numlockx software,


https://i.imgur.com/G4hSFii.png



go to /etc/sddm.conf and change it to on or off,


https://i.imgur.com/c4k4yTd.png


go to systemsettings and make sure keyboard, numlock is set to no 
change.


https://i.imgur.com/c3x5oSt.png


Do it and then come back


https://i.imgur.com/EMjLxsy.jpg

=> Login screen (taken from my phone, after all the settings above were
done of course), the CAPSLOCK warning is always shown

https://i.imgur.com/saGAqD7.png

=> Status of Capslock is off, Numlock is on, but the indicator (red
frame in left and bottom-right corner) shows nothing.


Have you tried a different keyboard layout? 


Not too many, but yes.

But as you may have known, no differences.

Also I've seen a new a package named 'numlock', remove it if it's 
installed.


It's never been installed in my Debian system.





and tell me I don't know what you're talking about. until then stuff a
sock!



You don't know what I'm talking about.



So do I have to stuff a sock now?


I don't know what you're doing. You look like a ms windows keyboard 
jockey in a gui environment. So until I know different, keep the sock 
stuffed.


Fortunately I don't understand what you mean.

Let me repeat Shai's quote, also my question:

Everything Luca and Jimmy are mentioning is about the state of
numlock when sddm or plasma start.

This is *not* what Franklin or I are talking about. We are talking
about *Caps/Num Lock being at the state they should be, as set by **
**pressing the relevant keys. It is only the visual indicators which 
are **
**not working -- the systray icons in plasma, and the caps-is-on 
warning **

**in the lock or login screen.*

I doubt if it is something wrong with D-bus, but I have no idea how to 
find the problem out.


When I asked in kde mailing list someone told me it should be Debian 
packager's issue.  And now in Debian-kde mailing list I have a pair of 
socks in my mouth.  You may or may not know, in 2017 KDE community 
selected one of the goals: onboarding and welcoming for newcomers[1].  
However IMO until now the _core_ people still haven't seen the real 
problem of KDE community, which -- fortunately or unfortunately -- you 
all have shown a perfect example.



Franklin

[1] 
https://mail.kde.org/mailman/private/kde-ev-membership/2019-October/037029.html



$ plasmawindowed org.kde.plasma.keyboardindicator

return an error after testing update, while is working in buster:

---

Error: could not load plugin for platform "" error: "The shared library 
was not found." QObject(0x0)


---

$ strace -f plasmawindowed org.kde.plasma.keyboardindicator

-

14519 openat(AT_FDCWD, 
"/usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/dataengine/plasma_engine_keystate.so", 
O_RDONLY|O_CLOEXEC) = 22
14519 read(22, 
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@D\0\0\0\0\0\0"..., 832) 
= 832

14519 fstat(22, {st_mode=S_IFREG|0644, st_size=105120, ...}) = 0
14519 mmap(NULL, 107088, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 22, 0) = 
0x7fbbe4e3b000
14519 mmap(0x7fbbe4e3f000, 69632, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 22, 0x4000) = 0x7fbbe4e3f000
14519 mmap(0x7fbbe4e5, 16384, PROT_READ, 

Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-27 Thread Franklin Weng

Jimmy Johnson 於 2019/11/27 下午2:08 寫道:
> On 11/26/19 4:06 PM, Franklin Weng wrote:
>>
>> Jimmy Johnson 於 2019/11/27 上午6:55 寫道:
>>> On 11/26/19 11:26 AM, Shai Berger wrote:
 For some reason, both Jimmy and Luca insist on connecting this to the
 wrong problem:

 On Tue, 26 Nov 2019 01:30:01 -0800
 Jimmy Johnson  wrote:

> On 11/25/19 7:10 AM, Franklin Weng wrote:
>> luca.pedrielli  於 2019年11月25日 週一 22:44
>>>
>>> Numlock problems had already been reported
>>>
>>> https://lists.debian.org/debian-kde/2019/09/msg00033.html
>>>
>>>    
>> Not sure, but it looks like not the same problem.  My problem is
>> about the indicator not the status itself.  The NumLock/Capslock
>> status is correct according to the xset -q.
>
>
> The settings for numlock have changed in testing kde5.
> I think the systemsettings, input device module is suppose to be
> handling numlock on/off at sddm start.
>

 And Luca, later:

> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872

 Everything Luca and Jimmy are mentioning is about the state of
 numlock when sddm or plasma start.

 This is *not* what Franklin or I are talking about. We are talking
 about Caps/Num Lock being at the state they should be, as set by
 pressing the relevant keys. It is only the visual indicators which are
 not working -- the systray icons in plasma, and the caps-is-on warning
 in the lock or login screen.
>>>
>>>
>>> Listen to me! Remove your numlockx software,
>>
>> https://i.imgur.com/G4hSFii.png
>>
>>
>>> go to /etc/sddm.conf and change it to on or off,
>>
>> https://i.imgur.com/c4k4yTd.png
>>
>>
>>> go to systemsettings and make sure keyboard, numlock is set to no
>>> change.
>>
>> https://i.imgur.com/c3x5oSt.png
>>
>>> Do it and then come back
>>
>> https://i.imgur.com/EMjLxsy.jpg
>>
>> => Login screen (taken from my phone, after all the settings above were
>> done of course), the CAPSLOCK warning is always shown
>>
>> https://i.imgur.com/saGAqD7.png
>>
>> => Status of Capslock is off, Numlock is on, but the indicator (red
>> frame in left and bottom-right corner) shows nothing.
>
> Have you tried a different keyboard layout?  

Not too many, but yes. 

But as you may have known, no differences.

> Also I've seen a new a package named 'numlock', remove it if it's
> installed.

It's never been installed in my Debian system.


>
>>> and tell me I don't know what you're talking about. until then stuff a
>>> sock!
>
>> You don't know what I'm talking about.
>
>> So do I have to stuff a sock now?
>
> I don't know what you're doing. You look like a ms windows keyboard
> jockey in a gui environment. So until I know different, keep the sock
> stuffed.

Fortunately I don't understand what you mean.

Let me repeat Shai's quote, also my question:

Everything Luca and Jimmy are mentioning is about the state of
numlock when sddm or plasma start.

This is *not* what Franklin or I are talking about. We are talking
about *Caps/Num Lock being at the state they should be, as set by **
**pressing the relevant keys. It is only the visual indicators which are **
**not working -- the systray icons in plasma, and the caps-is-on warning **
**in the lock or login screen.*

I doubt if it is something wrong with D-bus, but I have no idea how to
find the problem out.

When I asked in kde mailing list someone told me it should be Debian
packager's issue.  And now in Debian-kde mailing list I have a pair of
socks in my mouth.  You may or may not know, in 2017 KDE community
selected one of the goals: onboarding and welcoming for newcomers[1]. 
However IMO until now the _core_ people still haven't seen the real
problem of KDE community, which -- fortunately or unfortunately -- you
all have shown a perfect example.


Franklin

[1]
https://mail.kde.org/mailman/private/kde-ev-membership/2019-October/037029.html



signature.asc
Description: OpenPGP digital signature


Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-26 Thread Jimmy Johnson

On 11/26/19 4:06 PM, Franklin Weng wrote:


Jimmy Johnson 於 2019/11/27 上午6:55 寫道:

On 11/26/19 11:26 AM, Shai Berger wrote:

For some reason, both Jimmy and Luca insist on connecting this to the
wrong problem:

On Tue, 26 Nov 2019 01:30:01 -0800
Jimmy Johnson  wrote:


On 11/25/19 7:10 AM, Franklin Weng wrote:

luca.pedrielli  於 2019年11月25日 週一 22:44


Numlock problems had already been reported

https://lists.debian.org/debian-kde/2019/09/msg00033.html

   

Not sure, but it looks like not the same problem.  My problem is
about the indicator not the status itself.  The NumLock/Capslock
status is correct according to the xset -q.



The settings for numlock have changed in testing kde5.
I think the systemsettings, input device module is suppose to be
handling numlock on/off at sddm start.



And Luca, later:


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872


Everything Luca and Jimmy are mentioning is about the state of
numlock when sddm or plasma start.

This is *not* what Franklin or I are talking about. We are talking
about Caps/Num Lock being at the state they should be, as set by
pressing the relevant keys. It is only the visual indicators which are
not working -- the systray icons in plasma, and the caps-is-on warning
in the lock or login screen.



Listen to me! Remove your numlockx software,


https://i.imgur.com/G4hSFii.png



go to /etc/sddm.conf and change it to on or off,


https://i.imgur.com/c4k4yTd.png



go to systemsettings and make sure keyboard, numlock is set to no change.


https://i.imgur.com/c3x5oSt.png


Do it and then come back


https://i.imgur.com/EMjLxsy.jpg

=> Login screen (taken from my phone, after all the settings above were
done of course), the CAPSLOCK warning is always shown

https://i.imgur.com/saGAqD7.png

=> Status of Capslock is off, Numlock is on, but the indicator (red
frame in left and bottom-right corner) shows nothing.


Have you tried a different keyboard layout?  Also I've seen a new a 
package named 'numlock', remove it if it's installed.



and tell me I don't know what you're talking about. until then stuff a
sock!



You don't know what I'm talking about.



So do I have to stuff a sock now?


I don't know what you're doing. You look like a ms windows keyboard 
jockey in a gui environment. So until I know different, keep the sock 
stuffed.

--
Jimmy Johnson

Devuan Beowulf KDE5 - AMD A8-7600 - EXT4 at sda8
Registered Linux User #380263



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-26 Thread Franklin Weng

Jimmy Johnson 於 2019/11/27 上午6:55 寫道:
> On 11/26/19 11:26 AM, Shai Berger wrote:
>> For some reason, both Jimmy and Luca insist on connecting this to the
>> wrong problem:
>>
>> On Tue, 26 Nov 2019 01:30:01 -0800
>> Jimmy Johnson  wrote:
>>
>>> On 11/25/19 7:10 AM, Franklin Weng wrote:
 luca.pedrielli  於 2019年11月25日 週一 22:44
>
> Numlock problems had already been reported
>
> https://lists.debian.org/debian-kde/2019/09/msg00033.html
>
>   
 Not sure, but it looks like not the same problem.  My problem is
 about the indicator not the status itself.  The NumLock/Capslock
 status is correct according to the xset -q.
>>>
>>>
>>> The settings for numlock have changed in testing kde5.
>>> I think the systemsettings, input device module is suppose to be
>>> handling numlock on/off at sddm start.
>>>
>>
>> And Luca, later:
>>
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505
>>>
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872
>>
>> Everything Luca and Jimmy are mentioning is about the state of
>> numlock when sddm or plasma start.
>>
>> This is *not* what Franklin or I are talking about. We are talking
>> about Caps/Num Lock being at the state they should be, as set by
>> pressing the relevant keys. It is only the visual indicators which are
>> not working -- the systray icons in plasma, and the caps-is-on warning
>> in the lock or login screen.
>
>
> Listen to me! Remove your numlockx software, 

https://i.imgur.com/G4hSFii.png


> go to /etc/sddm.conf and change it to on or off, 

https://i.imgur.com/c4k4yTd.png


> go to systemsettings and make sure keyboard, numlock is set to no change. 

https://i.imgur.com/c3x5oSt.png

> Do it and then come back 

https://i.imgur.com/EMjLxsy.jpg

=> Login screen (taken from my phone, after all the settings above were
done of course), the CAPSLOCK warning is always shown

https://i.imgur.com/saGAqD7.png

=> Status of Capslock is off, Numlock is on, but the indicator (red
frame in left and bottom-right corner) shows nothing.

> and tell me I don't know what you're talking about. until then stuff a
> sock!

You don't know what I'm talking about.

So do I have to stuff a sock now?


Franklin




signature.asc
Description: OpenPGP digital signature


Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-26 Thread Jimmy Johnson

On 11/26/19 11:26 AM, Shai Berger wrote:

For some reason, both Jimmy and Luca insist on connecting this to the
wrong problem:

On Tue, 26 Nov 2019 01:30:01 -0800
Jimmy Johnson  wrote:


On 11/25/19 7:10 AM, Franklin Weng wrote:

luca.pedrielli  於 2019年11月25日 週一 22:44


Numlock problems had already been reported

https://lists.debian.org/debian-kde/2019/09/msg00033.html

  

Not sure, but it looks like not the same problem.  My problem is
about the indicator not the status itself.  The NumLock/Capslock
status is correct according to the xset -q.



The settings for numlock have changed in testing kde5.
I think the systemsettings, input device module is suppose to be
handling numlock on/off at sddm start.



And Luca, later:


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872


Everything Luca and Jimmy are mentioning is about the state of
numlock when sddm or plasma start.

This is *not* what Franklin or I are talking about. We are talking
about Caps/Num Lock being at the state they should be, as set by
pressing the relevant keys. It is only the visual indicators which are
not working -- the systray icons in plasma, and the caps-is-on warning
in the lock or login screen.



Listen to me! Remove your numlockx software, go to /etc/sddm.conf and 
change it to on or off, go to systemsettings and make sure keyboard, 
numlock is set to no change. Do it and then come back and tell me I 
don't know what you're talking about. until then stuff a sock!

--
Jimmy Johnson

Devuan Beowulf KDE5 - AMD A8-7600 - EXT4 at sda8
Registered Linux User #380263



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-26 Thread luca.pedrielli

Il 26/11/19 20:26, Shai Berger ha scritto:

For some reason, both Jimmy and Luca insist on connecting this to the
wrong problem:

On Tue, 26 Nov 2019 01:30:01 -0800
Jimmy Johnson  wrote:


On 11/25/19 7:10 AM, Franklin Weng wrote:

luca.pedrielli  於 2019年11月25日 週一 22:44

Numlock problems had already been reported

https://lists.debian.org/debian-kde/2019/09/msg00033.html

  

Not sure, but it looks like not the same problem.  My problem is
about the indicator not the status itself.  The NumLock/Capslock
status is correct according to the xset -q.


The settings for numlock have changed in testing kde5.
I think the systemsettings, input device module is suppose to be
handling numlock on/off at sddm start.


And Luca, later:


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872

Everything Luca and Jimmy are mentioning is about the state of
numlock when sddm or plasma start.

This is *not* what Franklin or I are talking about. We are talking
about Caps/Num Lock being at the state they should be, as set by
pressing the relevant keys. It is only the visual indicators which are
not working -- the systray icons in plasma, and the caps-is-on warning
in the lock or login screen.

Thanks,
Shai.


What I say is that systemsetting is no more able to handle numlock 
on/off at session start and keyboardindicator


is no more working. This after KF and Qt updates.


--
Saluti, Luca Pedrielli



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-26 Thread Shai Berger
For some reason, both Jimmy and Luca insist on connecting this to the
wrong problem:

On Tue, 26 Nov 2019 01:30:01 -0800
Jimmy Johnson  wrote:

> On 11/25/19 7:10 AM, Franklin Weng wrote:
> > luca.pedrielli  於 2019年11月25日 週一 22:44
> >>
> >> Numlock problems had already been reported
> >>
> >> https://lists.debian.org/debian-kde/2019/09/msg00033.html
> >>
> >>  
> > Not sure, but it looks like not the same problem.  My problem is
> > about the indicator not the status itself.  The NumLock/Capslock
> > status is correct according to the xset -q.  
> 
> 
> The settings for numlock have changed in testing kde5.
> I think the systemsettings, input device module is suppose to be 
> handling numlock on/off at sddm start.
> 

And Luca, later:

> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872

Everything Luca and Jimmy are mentioning is about the state of
numlock when sddm or plasma start.

This is *not* what Franklin or I are talking about. We are talking
about Caps/Num Lock being at the state they should be, as set by
pressing the relevant keys. It is only the visual indicators which are
not working -- the systray icons in plasma, and the caps-is-on warning
in the lock or login screen.

Thanks,
Shai.



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-25 Thread luca.pedrielli

Il 25/11/19 22:39, Shai Berger ha scritto:

On Mon, 25 Nov 2019 23:10:57 +0800
Franklin Weng  wrote:


luca.pedrielli  於 2019年11月25日 週一 22:44 寫道:


Il 24/11/19 02:26, Franklin Weng ha scritto:


It looks like no problem in X window level, but the status does
not pass to sddm/plasma correctly.


No suggestion, but I can confirm this behaviour.

Numlock problems had already been reported

https://lists.debian.org/debian-kde/2019/09/msg00033.html
  

Not sure, but it looks like not the same problem.  My problem is
about the indicator not the status itself.  The NumLock/Capslock
status is correct according to the xset -q.


I can also confirm this. My situation is exactly what Franklin
described, with one exception: I use lightdm rather than sddm, and
there the "Caps On" warning is always off (even when caps is pressed),
not always on.

Shai



https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941505

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940872

--
Saluti, Luca Pedrielli



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-25 Thread Shai Berger
On Mon, 25 Nov 2019 23:10:57 +0800
Franklin Weng  wrote:

> luca.pedrielli  於 2019年11月25日 週一 22:44 寫道:
> 
> > Il 24/11/19 02:26, Franklin Weng ha scritto:
> >
> > > It looks like no problem in X window level, but the status does
> > > not pass to sddm/plasma correctly.
> >
> >
> > No suggestion, but I can confirm this behaviour.
> >
> > Numlock problems had already been reported
> >
> > https://lists.debian.org/debian-kde/2019/09/msg00033.html
> >  
> Not sure, but it looks like not the same problem.  My problem is
> about the indicator not the status itself.  The NumLock/Capslock
> status is correct according to the xset -q.
> 

I can also confirm this. My situation is exactly what Franklin
described, with one exception: I use lightdm rather than sddm, and
there the "Caps On" warning is always off (even when caps is pressed),
not always on.

Shai



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-25 Thread Jimmy Johnson

On 11/25/19 7:10 AM, Franklin Weng wrote:

luca.pedrielli  於 2019年11月25日 週一 22:44 寫道:


Il 24/11/19 02:26, Franklin Weng ha scritto:

Hi,


I'm using Debian testing and run KDE Plasma 5 (Framework 5.62.0, Qt
5.12.5, xcb window system, Application 19.08.1, kde-plasma-desktop version
5:104).  Originally the indicator worked: in sddm login screen it would
show warning when Capslock is ON; after logging into Plasma session a small
icon would show beside the system tray when Capslock is ON.  However from
some day it didn't work anymore.

The current status of my system is:

- In sddm login screen, the Capslock ON warning *always* shows.
- In Plasma the keyboard indicator plasmoids
(org.kde.plasma.keyboardindicator) shows nothing no matter what the
capslock/numlock status is.
- Using xset -q I can get *correct* Capslock/Numlock status.  Using
xev I can see events of Capslock key being pressed and released.

It looks like no problem in X window level, but the status does not pass
to sddm/plasma correctly.

Any idea or suggestion for finding or fixing the problem?


Regards, Franklin

No suggestion, but I can confirm this behaviour.

Numlock problems had already been reported

https://lists.debian.org/debian-kde/2019/09/msg00033.html

--
Saluti, Luca Pedrielli



Not sure, but it looks like not the same problem.  My problem is about the
indicator not the status itself.  The NumLock/Capslock status is correct
according to the xset -q.


I'm without systemd here, using sysvinit, so I was hesitant to speak up.

The settings for numlock have changed in testing kde5.
I think the systemsettings, input device module is suppose to be 
handling numlock on/off at sddm start.


Go to "/etc/sddm.conf" and look for "Numlock=none" for me that was the 
default I found and I changed it to on.


The options are none, off and on.

I also go to systemsettings/input device just to make sure the settings 
say to leave numlock along. Now it comes on at boot and stays on without 
installing any extra numlock software.


I hope that helps.
--
Jimmy Johnson

Slackware64 11.19.KDE5 - AMD A8-7600 - EXT4 at sda7
Registered Linux User #380263



Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-25 Thread Franklin Weng
luca.pedrielli  於 2019年11月25日 週一 22:44 寫道:

> Il 24/11/19 02:26, Franklin Weng ha scritto:
>
> Hi,
>
>
> I'm using Debian testing and run KDE Plasma 5 (Framework 5.62.0, Qt
> 5.12.5, xcb window system, Application 19.08.1, kde-plasma-desktop version
> 5:104).  Originally the indicator worked: in sddm login screen it would
> show warning when Capslock is ON; after logging into Plasma session a small
> icon would show beside the system tray when Capslock is ON.  However from
> some day it didn't work anymore.
>
> The current status of my system is:
>
>- In sddm login screen, the Capslock ON warning *always* shows.
>- In Plasma the keyboard indicator plasmoids
>(org.kde.plasma.keyboardindicator) shows nothing no matter what the
>capslock/numlock status is.
>- Using xset -q I can get *correct* Capslock/Numlock status.  Using
>xev I can see events of Capslock key being pressed and released.
>
> It looks like no problem in X window level, but the status does not pass
> to sddm/plasma correctly.
>
> Any idea or suggestion for finding or fixing the problem?
>
>
> Regards, Franklin
>
> No suggestion, but I can confirm this behaviour.
>
> Numlock problems had already been reported
>
> https://lists.debian.org/debian-kde/2019/09/msg00033.html
>
> --
> Saluti, Luca Pedrielli
>
>
Not sure, but it looks like not the same problem.  My problem is about the
indicator not the status itself.  The NumLock/Capslock status is correct
according to the xset -q.


Franklin

>


Re: Capslock / Numlock indicator not work in KDE (& sddm)

2019-11-25 Thread luca.pedrielli

Il 24/11/19 02:26, Franklin Weng ha scritto:


Hi,


I'm using Debian testing and run KDE Plasma 5 (Framework 5.62.0, Qt 
5.12.5, xcb window system, Application 19.08.1, kde-plasma-desktop 
version 5:104).  Originally the indicator worked: in sddm login screen 
it would show warning when Capslock is ON; after logging into Plasma 
session a small icon would show beside the system tray when Capslock 
is ON.  However from some day it didn't work anymore.


The current status of my system is:

  * In sddm login screen, the Capslock ON warning *always* shows.
  * In Plasma the keyboard indicator plasmoids
(org.kde.plasma.keyboardindicator) shows nothing no matter what
the capslock/numlock status is.
  * Using xset -q I can get *correct* Capslock/Numlock status. Using
xev I can see events of Capslock key being pressed and released.

It looks like no problem in X window level, but the status does not 
pass to sddm/plasma correctly.


Any idea or suggestion for finding or fixing the problem?


Regards, Franklin 


No suggestion, but I can confirm this behaviour.

Numlock problems had already been reported

https://lists.debian.org/debian-kde/2019/09/msg00033.html

--
Saluti, Luca Pedrielli