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 <field.engineer@gmail.com>
wrote:
On 11/25/19 7:10 AM, Franklin Weng
wrote:
luca.pedrielli <agoiza@gmail.com>
於 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(0x7fbbe4e50000, 16384, PROT_READ,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 22, 0x15000) =
0x7fbbe4e50000
14519 mmap(0x7fbbe4e54000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 22, 0x18000) =
0x7fbbe4e54000
14519 close(22) = 0
14519 mprotect(0x7fbbe4e54000, 4096, PROT_READ) = 0
14519 statx(AT_FDCWD,
"./kf5/kguiaddons/kmodifierkey/kmodifierkey_xcb",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 statx(AT_FDCWD,
"./kf5/kguiaddons/kmodifierkey/kmodifierkey_xcb.so",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 statx(AT_FDCWD,
"./kf5/kguiaddons/kmodifierkey/libkmodifierkey_xcb",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 statx(AT_FDCWD,
"./kf5/kguiaddons/kmodifierkey/libkmodifierkey_xcb.so",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 statx(AT_FDCWD,
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_xcb",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 statx(AT_FDCWD,
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_xcb.so",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 statx(AT_FDCWD,
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/libkmodifierkey_xcb",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 statx(AT_FDCWD,
"/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/libkmodifierkey_xcb.so",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 statx(AT_FDCWD,
"/usr/bin/kf5/kguiaddons/kmodifierkey/kmodifierkey_xcb",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 statx(AT_FDCWD,
"/usr/bin/kf5/kguiaddons/kmodifierkey/kmodifierkey_xcb.so",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 statx(AT_FDCWD,
"/usr/bin/kf5/kguiaddons/kmodifierkey/libkmodifierkey_xcb",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 statx(AT_FDCWD,
"/usr/bin/kf5/kguiaddons/kmodifierkey/libkmodifierkey_xcb.so",
AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdaf8c6450) = -1 ENOENT
(File o directory non esistente)
14519 write(2, "Error: could not load plugin for"...,
110) = 110
-----------------------------------------------------------------------------------------------------------------------------------------
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.
--
Saluti, Luca Pedrielli
