Desktop logs out to lock screen (nvidia)

Hello,

  • _OpenMandriva Lx version:_rome

  • Desktop environment (KDE, LXQT…): plasma 6 wayland

  • Description of the issue (screenshots if relevant): after logging in the desktop goes to the lock screen after a few minutes. I changed the lock screen settings to never but that hasn’t changed anything. The screen even locks whilst i’m using the laptop.

  • Relevant informations (hardware involved, software version, logs or output…): i did a fresh install on an old lenovo Z710 ideapad intel i7 with 4th gen intergrated graphics, 12bg ram + nvidia 840m.

Welcome @richp to OpenMandriva and our forum. This forum is for users of OpenMandriva Linux operating systems.

OpenMandriva Forums are primarily users helping other users.

You are welcome to talk to our developers at OpenMandriva Chat.

Users with a problem need to read How to get better results when posting about problems before reporting any issue or problem. The article is not too long and Do Read.

When a new user has an issue please look in the documentation for OMLx. OpenMandriva wiki, Forum Resources guide and the “Search” function of the forum.

If you don’t find what you are looking for, try an Internet search. One can find out a lot from documentation or forum posts at other Linux distros. If user finds something written for another distro but you have some doubt ask at OpenMandriva Chat.

For serious technical issues and package/feature requests please file a bug report here.

Note: We are a small group. All the contributors and developers here are unpaid volunteers.
You can make OpenMandriva grow and improve by getting involved

Any help with testing would be appreciated whether one is technically proficient or a very non-technical user. The more people and more hardware we can get involved the better we can make OMLx releases and packaging. We do a lot of testing in VM’s as well. Developers tend to use Qemu, most user level testers use VirtualBox.

Certainly not normal behavior.

My guess is the OM’s implementation of Wayland does not work well on that hardware.
Suggestion install X11 and use that.

sudo dnf in task-plasma6-x11

Then logout and in lower left of login screen select Plasma X11.

Thanks for the reply, i’ve now tried that, but it kept happening even when logging into an x11 session. After spending some time digging through the settings menu to see if i had missed anything i decided to install rock. There is no problem with plasma5 so i think it may be a bug in plasma6. I think i will try installing arch and see if the problem persists. I will check back in when i have some results.

1 Like

You can try to add this to your ~/.config/kscreenlockerrc file. It has worked for me for X11 and wayland.

[Daemon]
Autolock=false
LockOnResume=false

Ok, sorry i made a mistake it’s not the lock screen i am actually being loged out, i did try editing the kscreenlockerrc file anyway but didn’t change anything. This afternoon have tried a number of things
1, upgrade rock to rome. This failed due to conflicts during the transaction test stage, i managed to get passed this by removing the conficting packages but then failed whilst running a grub 2 scriptlet. I had to reset the system but was unbootable after that.
2, installed archlinux with plasma desktop, worked fine
3, installed the rome plasma6 x11 iso, same problem
4, installed the rome plasma5 iso also the same problem

So it seems like rome doesn’t like my setup somehow because rock was fine until i botched the upgrade. I think i will try the gnome iso next to see if there is any difference between Qt and Gtk. Is it worth me submitting a bug report and how would i do that?

Thanks for the help so far.

Bug reports here. Select New issue>Bug report,

For problems like this we need to be able to see the terminal output posted here in a .txt file (if more than about 20 lines) or posted as code (using the </> icon. Please post all the output including the command used.

If you are being logged out we need to see logs to find out why you are being logged out.

I think if you were logged out you either log back in or open a VT and:

journalctl -b > journal.txt

and post the created journal.txt file here or better in your bug report.

Hello,
Would you please reword what is the issue about?
I have to admit I don’t understand :thinking:
Well, maybe I won’t be of help while talking of wayland but I read that it’s the same in x11.
Thank you.
By the way the default in OpenMandriva should be Screen Lock disabled and Energy Saving as well.
Look at systemsettings.

to clarify at the beginning i thought that after being logged in for a couple of minutes the desktop was closing to the lock screen but infact i was being logged out, i have made a copy of the journal but it is very long (over 2600 lines) so for now i will add only the last few lines at the moment i was logged out.

Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: "(**) Option \"fd\" \"29\"\n(II) event2  - Power Button: device removed\n"
Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: "(**) Option \"fd\" \"32\"\n(II) event5  - Video Bus: device removed\n"
Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: "(**) Option \"fd\""
Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: " \"33\"\n(II) event4  - Video Bus: device removed\n"
Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: "(**) Option \"fd\" \"34\"\n"
Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: "(II) event6  - Ideapad extra buttons: device removed\n"
Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: "(**) Option \"fd\" \"35\"\n(II) event0  - AT Translated Set 2 keyboard: device removed\n"
Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: "(**) Option \"fd\" \"36\"\n(II) event3  - SynPS/2 Synaptics TouchPad: device removed\n"
Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: "(II) "
Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: "AIGLX: Suspending AIGLX clients for VT switch\n"
Jan 08 22:47:02 openmandriva-x8664 kernel: nouveau 0000:01:00.0: Enabling HDA controller
Jan 08 22:47:02 openmandriva-x8664 kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/ldac
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSink/aptx
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/aptx
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSink/opus_g
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/opus_g
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSink/sbc
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/sbc
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/faststream
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSink/opus_05
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/opus_05
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint unregistered: sender=:1.99 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 08 22:47:02 openmandriva-x8664 wireplumber[1190]: spa.bluez5.midi: org.bluez.GattManager1.RegisterApplication() failed: GDBus.Error:org.bluez.Error.AlreadyExists: Already Exists
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/ldac
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSink/aptx
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/aptx
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSink/opus_g
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/opus_g
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSink/sbc
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/sbc
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/faststream
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSink/opus_05
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/opus_05
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 08 22:47:02 openmandriva-x8664 bluetoothd[804]: Endpoint registered: sender=:1.102 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: "(II) systemd-logind: got pause for 13:69\n"
Jan 08 22:47:02 openmandriva-x8664 sddm-helper-start-x11user[1938]: "(II) systemd-logind: got pause for 13:68\n(II) systemd-logind: got pause for 13:64\n(II) systemd-logind: got pause for 13:70\n(II) systemd-logind: got pause for 13:66\n(II) systemd-logind: got pause for 13:67\n"
Jan 08 22:47:08 openmandriva-x8664 kernel: ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM

if i need to add the entire journal should i do it the same way or can i attache it as a file?

sorry again, after reading the ‘how to post’ article the instructions are quite clear so the whole journal is now attached.
journal2.txt (374.3 KB)

1 Like

Oh logged out…
It happened also to me but that was in virtualbox machines (and I blamed vbox at that time).
Out of ideas then.

You need to have a developer look at that. Like in a bug report. All I can tell for sure is that there is stuff in there related to sddm that I do not see in my own journal.

ok will do thanks for all the help. Should i close this thread or wait to see if i get a solution seems like others may have the same problem.

It happened also to me but that was in virtualbox machines (and I blamed vbox at that time).

Leave it open. Never know a dev might see it tomorrow. FWIW a big advantage to bug reports is that they stay more single issue specific and all the info is in one place. Very helpful if an issue takes a bit of time to resolve.

That’s covered here
in this topic which we strongly suggest to check very often (always, if you see console listing a lot of packages to update, before start distro-sync)
ROME major upgrade expected

We publish there all important to know stuff and some workarounds if needed.
Enable notifications if not done already :wink:

I found a similar article specifically for upgradeing rock to rome whilst googling around I think i will try again, i’m curious if the logging out bug will be there afterwards.

These are the latest instructions for upgrading Rock/5.0 to ROME. You will still have Plasma5.

Bug report:
Being logged out shortly after logging in #3030

Hey, I started using OM ROME the other day and I’m running into this same problem. I also have a hybrid GPU setup with intel + nVidia (GT 730M). I’ve been able to log in from a virtual console (Ctrl+alt+f4) using startx, and everything else works fine, so the graphics stuff seems to be working fine. I still have to look at the logs, which I’ll hope to do soon to see what can be done.

However, I installed the nVidia proprietary drivers and the SDDM started to work propertly. Funny thing is my nVidia card isn’t supported by the latest driver, and if I use “inxi -Fxxxrz” it shows that card doesn’t have any driver. This could point to the nouveau driver having some kind of issue with the SDDM or login process (because right now its working for me after the startx thing), or the proprietary nvidia driver installation does something else that fixes the prblem.

These are my 2 cents for now. I can use my pc, so for now it’s okay. I hope to delve deeper into this this weekend.

2 Likes