No KB in Plasma (X11) after TW update
Hi all, I've just updated my TW installation (first update for 3-4 weeks, so included full glibc update) and after rebooting I have no KB in Qt applications under Plasma (X11). Non-qt applications are working ok (e.g. Thunderbird, Firefox, xterm) but no qt apps (i.e. no native KDE apps) are accepting keyboard input. I'm using nvidia drivers (installed "the hard way") with dkms. I've tried installing the 2 latest driver versions (465.24.02 and 460.73.01) as well as the version I was previously running (460.73) - no difference. I've tried rebooting to the kernel version I was previously running (5.11.6-1-default) and the latest (5.11.15-1-default) - no difference there either. Qt applications do work using a "Full Wayland" plasma session, but my desktop is borked using that and I cannot change the second monitor from "Folder View" to "Desktop View", no matter what I do ("Some settings are locked by the system administrator", which is weird). They don't work under Plasma Wayland (X11) or Plasma (X11). This would seem perhaps to point to an issue between X11 and KDE/Plasma, but not sure. Any hints/pointers? TIA, Rodney. -- ============================================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ==============================================================================
On 20/04/2021 14:49, Rodney Baker wrote:
Hi all,
I've just updated my TW installation (first update for 3-4 weeks, so included full glibc update) and after rebooting I have no KB in Qt applications under Plasma (X11). Non-qt applications are working ok (e.g. Thunderbird, Firefox, xterm) but no qt apps (i.e. no native KDE apps) are accepting keyboard input.
I'm using nvidia drivers (installed "the hard way") with dkms. I've tried installing the 2 latest driver versions (465.24.02 and 460.73.01) as well as the version I was previously running (460.73) - no difference.
I've tried rebooting to the kernel version I was previously running (5.11.6-1-default) and the latest (5.11.15-1-default) - no difference there either.
Qt applications do work using a "Full Wayland" plasma session, but my desktop is borked using that and I cannot change the second monitor from "Folder View" to "Desktop View", no matter what I do ("Some settings are locked by the system administrator", which is weird). They don't work under Plasma Wayland (X11) or Plasma (X11). This would seem perhaps to point to an issue between X11 and KDE/Plasma, but not sure.
Any hints/pointers?
TIA, Rodney.
Hmmm...just created a new test user, logged into a standard Plasma (X11) session, and everything worked, so it looks like a user-config issue that's been triggered by an updated package. The only question is, which config file? Looks like I'm reconfiguring my desktop from scratch, then. :( -- ============================================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ==============================================================================
Rodney Baker composed on 2021-04-20 15:18 (UTC+0930):
Hmmm...just created a new test user, logged into a standard Plasma (X11) session, and everything worked, so it looks like a user-config issue that's been triggered by an updated package.
The only question is, which config file? Looks like I'm reconfiguring my desktop from scratch, then.
Sometimes inexplicable Plasma behavior isn't any config file, but its cache. Log out of Plasma, log in on a vtty, delete ~/.config/*, log back into Plasma. Likely no need to mess with any config files. Cache is cache. It gets rebuilt as needed. Plasma corrupts it at its pleasure, that is, without warning or reproducible reason. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
On 2021-04-20 01:00:27 Felix Miata wrote:
|Rodney Baker composed on 2021-04-20 15:18 (UTC+0930): |> Hmmm...just created a new test user, logged into a standard Plasma (X11) |> session, and everything worked, so it looks like a user-config issue |> that's been triggered by an updated package. |> |> The only question is, which config file? Looks like I'm reconfiguring my |> desktop from scratch, then. | |Sometimes inexplicable Plasma behavior isn't any config file, but its | cache. Log out of Plasma, log in on a vtty, delete ~/.config/*, log back | into Plasma. Likely no need to mess with any config files. | |Cache is cache. It gets rebuilt as needed. Plasma corrupts it at its | pleasure, that is, without warning or reproducible reason.
Do you mean ~/.cache/* instead of ~/.config/*? Leslie -- openSUSE Leap 15.2 x86_64
J Leslie Turriff composed on 2021-04-20 01:22 (UTC-0500):
Felix Miata wrote:
Rodney Baker composed on 2021-04-20 15:18 (UTC+0930):
Hmmm...just created a new test user, logged into a standard Plasma (X11) session, and everything worked, so it looks like a user-config issue that's been triggered by an updated package.
The only question is, which config file? Looks like I'm reconfiguring my desktop from scratch, then.
Sometimes inexplicable Plasma behavior isn't any config file, but its cache. Log out of Plasma, log in on a vtty, delete ~/.config/*, log back into Plasma. Likely no need to mess with any config files.
Cache is cache. It gets rebuilt as needed. Plasma corrupts it at its pleasure, that is, without warning or reproducible reason.
Do you mean ~/.cache/* instead of ~/.config/*? Of course. I do that a lot, but usually I catch it before sending. Thx! -- Evolution as taught in public schools is, like religion, based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
participants (3)
-
Felix Miata -
J Leslie Turriff -
Rodney Baker