https://bugs.kde.org/show_bug.cgi?id=447337
Andrey changed:
What|Removed |Added
Resolution|WAITINGFORINFO |UPSTREAM
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #30 from Conrad ---
sure, sounds good
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
Andrey changed:
What|Removed |Added
URL||https://gitlab.freedesktop.
|
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #29 from Andrey ---
You are welcome.
So I would open another bug about inverted NumLock in the config, and close
this one as Upstream.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #28 from Conrad ---
Thank you for your help so far! Upstream bug has been reported here:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/300
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #27 from Andrey ---
(In reply to Conrad from comment #26)
> I can confirm your suspicions. sway shows the same broken behavior as soon
> as numlock is turned on. So very likely an upstream problem.
>
Please report it here then and paste
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #26 from Conrad ---
I can confirm your suspicions. sway shows the same broken behavior as soon as
numlock is turned on. So very likely an upstream problem.
Regarding the 0/1 status in the config, this has been for years., so probably
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #25 from Andrey ---
(In reply to Conrad from comment #24)
> It does however not explain why neo2 layout would become unusable if numlock
> is on.
Can you try that on Gnome/etc.? Might be something with the layout itself.
Also, could anyone
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #24 from Conrad ---
Yes, that could be what is happening here.
It does however not explain why neo2 layout would become unusable if numlock is
on.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #23 from Andrey ---
(In reply to Conrad from comment #22)
> They do. They are written to the file like this as soon as I click the
> "apply" button in the system settings.
I have a theory then.
Earlier, you could "reset" non-working layout
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #22 from Conrad ---
They do. They are written to the file like this as soon as I click the "apply"
button in the system settings.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #21 from Andrey ---
(In reply to Conrad from comment #20)
> Yes, verified multiple times.
IIUC, the values look inverted, no?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #20 from Conrad ---
Yes, verified multiple times.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #19 from Andrey ---
(In reply to Conrad from comment #18)
> turn on sets it to 0, turn off sets it to 1.
Exactly like this, not the otherwise?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #18 from Conrad ---
turn on sets it to 0, turn off sets it to 1. The problem indeed only appears
when numlock is enabled.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
Andrey changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #16 from Conrad ---
I can't tell. My numlock is always off and I can't enable it. Probably some
other problem with legacy config files.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #15 from Andrey ---
So it's probably was enough to just press NumLock to make it work?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #14 from Conrad ---
The culprit is "NumLock=0". Removing the line or changing it to "NumLock=1"
resolves the problem.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #13 from Andrey ---
(In reply to Conrad from comment #12)
> Figured out the problem. It was caused by ~/.config/kcminputrc and more
> precisely by these lines:
>
> [Keyboard]
> KeyRepeat=repeat
> NumLock=0
> RepeatDelay=600
> RepeatRate=25
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #12 from Conrad ---
Figured out the problem. It was caused by ~/.config/kcminputrc and more
precisely by these lines:
[Keyboard]
KeyRepeat=repeat
NumLock=0
RepeatDelay=600
RepeatRate=25
It must have been created by some older version of
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #11 from Conrad ---
Thanks for your help so far! I tested with a newly created user just now and
the problem does not occur there. Any idea where I could start looking to
narrow down the cause?
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #10 from Andrey ---
You can test in VM, but if it works for Sway then it's probably something
different..
Still we need a way to reproduce it, so yes, please test on VM. You can use
Neon iso.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #9 from Conrad ---
No, sway is its own wayland compositor. "etc." sounded like that was what you
were asking for. Any way to test this without having to install the whole gnome
suite on my system?
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #8 from Andrey ---
(In reply to Conrad from comment #7)
> I have tried with "XKB_DEFAULT_LAYOUT=de XKB_DEFAULT_VARIANT=neo sway" and
> this worked as intended.
Is it on Gnome?
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #7 from Conrad ---
I have tried with "XKB_DEFAULT_LAYOUT=de XKB_DEFAULT_VARIANT=neo sway" and this
worked as intended.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #6 from Andrey ---
Can you try on Gnome Wayland etc.? It still might be upstream issue
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #5 from Conrad ---
As far as I can tell there is no difference no matter what settings I set or
how many layouts I configure.
~/.config/kxkbrc
[$Version]
update_info=kxkb_variants.upd:split-variants
[Layout]
DisplayNames=
LayoutList=de
https://bugs.kde.org/show_bug.cgi?id=447337
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=447337
--- Comment #3 from Conrad ---
Unfortunate typo: This bug is *not* a duplicate of 432436. It is not about
layout changing at all.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=447337
Conrad changed:
What|Removed |Added
Resolution|DUPLICATE |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=447337
Andrey changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
32 matches
Mail list logo
