https://bugs.kde.org/show_bug.cgi?id=429022
Duncan <1i5t5.dun...@cox.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |1i5t5.dun...@cox.net
--- Comment #5 from Duncan <1i5t5.dun...@cox.net> ---
Seeing this bug here too.
Wayland functionality is finally "good enough" that I've been porting my
workflow and previously X-only scripts, hotkeys that don't work in wayland,
etc, over.
Noticed the "system bell" when (too frequently accidentally) toggling
capslock/numlock was missing and a couple days layer when the more pressing
porting issues were mostly done, tried to load the accessibility kcm.
It crashed. So did trying to start just the individual accessibility kcm from
krunner, or rather, nothing came up at all. Trying to run kcmshell5 kcm_access
in konsole crashes with a segfault.
straced it and the user config kaccessrc and its notifications rc were the last
files touched, along with kdeglobals, but they looked fine. Still I
temp-renamed them and tried again. Same segfault. Renamed them back.
Quit plasma-wayland to the CLI (no *DM here) and started plasma-X. Both the
caps-lock bell and the accessibility kcm worked fine.
Googled accessibility wayland on bugs.kde and found this. Trying to run X-only
code from a wayland app does explain things. =:^\
FWIW live-git frameworks/plasma/apps via gentoo/kde's overlay. From this bug
looks like this is being worked on but I'll have to do without
accidental-capslock toggling popup-notifications/bell until the fix lands. =:^(
On the plus side I've got what I consider the critical workflow and config
ported to wayland now and switched it to the default in my plasma startscript I
think yesterday. The switch has been a pain but definitely less so than say
the kde3/kde4 upgrade, by **FAR**, and about the same as the kde4/kde-plasma-5
upgrade, AND and it's mostly done, now. Kool job kdeers! =:^)
--
You are receiving this mail because:
You are watching all bug changes.
