Leap 15.4; Plasma 5.26.3; Frameworks 5.100.0; Qt 5.15.7 NVIDIA GeForce GTX 1650; desktop X11 not Wayland. I have a serious problem after an update that included the G06 nvidia drivers, from 525.53-15.1 to 525.53-16.1. The Plasma desktop comes up, but among several other things the windows have no titlebar or borders with all that that entails, click-to-focus doesn't work, and the four virtual desktops I normally use are absent. Overall the system is barely usable, and then only with difficulty. An attempt to re-instate the virtual desktops results in an error message that there was a problem requesting information from the compositor, and it's tempting to think that the problem might lie with the G06 driver update, though I guess it could be many other things beyond my ken. But I can't find a way of testing this by rolling back the nvidia packages. Is there one, or am I cast until there's another update??? -- Robin K Wellington "Harbour City" New Zealand
Le 23/11/2022 à 22:26, Robin Klitscher a écrit :
the nvidia packages. Is there one, or am I cast until there's another update???
if default btrfs, run the last snapshot from the grub menu? jdd -- mon serveur usenet: dodin.fr.nf c'est quoi, usenet? http://www.dodin.org/wiki/pmwiki.php?n=Usenet.Usenet
On 24/11/2022 10:32, jdd@dodin.org wrote:
Le 23/11/2022 à 22:26, Robin Klitscher a écrit :
the nvidia packages. Is there one, or am I cast until there's another update???
if default btrfs, run the last snapshot from the grub menu?
jdd
Thanks but sadly, I omitted to say that, being a dinosaur, I'm in ext4 not btrfs. -- Robin K Wellington "Harbour City" New Zealand
On Thursday 24 November 2022, Robin Klitscher wrote:
Leap 15.4; Plasma 5.26.3; Frameworks 5.100.0; Qt 5.15.7 NVIDIA GeForce GTX 1650; desktop X11 not Wayland.
I have a serious problem after an update that included the G06 nvidia drivers, from 525.53-15.1 to 525.53-16.1. The Plasma desktop comes up, but among several other things the windows have no titlebar or borders with all that that entails, click-to-focus doesn't work, and the four virtual desktops I normally use are absent. Overall the system is barely usable, and then only with difficulty.
An attempt to re-instate the virtual desktops results in an error message that there was a problem requesting information from the compositor, and it's tempting to think that the problem might lie with the G06 driver update, though I guess it could be many other things beyond my ken. But I can't find a way of testing this by rolling back the nvidia packages. Is there one, or am I cast until there's another update???
If you suspect the compositor, have you tried turning off compositing in settings display-and-monitor compositor? Have you tried logging in as a different user to see if it's just you? Would the G05 driver be of any use? Michael
On 2022-11-23 23:55, Michael Hamilton wrote:
On Thursday 24 November 2022, Robin Klitscher wrote:
...
Have you tried logging in as a different user to see if it's just you?
Also try a different desktop. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
On 24/11/2022 11:55, Michael Hamilton wrote: <...>
If you suspect the compositor, have you tried turning off compositing in settings display-and-monitor compositor?
Tried that. Didn't fix the problems. (As to why fault the compositor, it's only a guess, but it seemed like somewhere to start troubleshooting if only for purposes of elimination.
Have you tried logging in as a different user to see if it's just you?
I'm the only user, but I did try logging in as root. No change - the problems show up there too.
Would the G05 driver be of any use?
Haven't tried that. Yet. -- Robin K Wellington "Harbour City" New Zealand
On 24/11/2022 13:43, Robin Klitscher wrote:
On 24/11/2022 11:55, Michael Hamilton wrote: <...>
If you suspect the compositor, have you tried turning off compositing in settings display-and-monitor compositor?
Tried that. Didn't fix the problems. (As to why fault the compositor, it's only a guess, but it seemed like somewhere to start troubleshooting if only for purposes of elimination.
Wrong guess, I guess. I've just updated a standing Tumbleweed installation to use the latest nvidia G06 drivers on this same machine, and they work well.
So the issue with my Leap 15.4 installation looks likely to lie somewhere else. But heaven knows where. -- Robin K Wellington "Harbour City" New Zealand
On Thursday 24 November 2022, Robin Klitscher wrote:
On 24/11/2022 13:43, Robin Klitscher wrote:
On 24/11/2022 11:55, Michael Hamilton wrote: <...>
If you suspect the compositor, have you tried turning off compositing in settings display-and-monitor compositor?
Tried that. Didn't fix the problems. (As to why fault the compositor, it's only a guess, but it seemed like somewhere to start troubleshooting if only for purposes of elimination.
Wrong guess, I guess. I've just updated a standing Tumbleweed installation to use the latest nvidia G06 drivers on this same machine, and they work well.
So the issue with my Leap 15.4 installation looks likely to lie somewhere else. But heaven knows where.
I would try creating a new ordinary user. I would look for clues in: $HOME/.local/share/sddm/xorg-session.log On tumbleweed most of what used to go to xorg-session.log is now captured by journald, but I think Leap still uses the .log file. I wonder if something else could be wrong: broken update, lack of space? Perhaps rpm --verify --all or zypper verify might yield some clues. A fresh Leap install in a virtualbox would verify a generic non-Nvidia install works OK and perhaps serve as a point of comparison. But no one else is complaining, so I think this isn't likely to yield anything interesting. Best of luck. Michael
participants (4)
-
Carlos E. R. -
jdd＠dodin.org -
Michael Hamilton -
Robin Klitscher