Hi - Installed OpenSUSE Leap 15.4 from scratch. While I can’t confirm the exact order, I believe the initial graphical login after install was fine. However, I then used Yast to install the proprietary NVIDIA driver for my older laptop. That went fine. However, while I can’t be certain the issue started after this, I think after this the first time I login graphically my password is accepted but eventually without starting the desktop ,it returns me back to the graphical login window. I simply enter my password in again and then all is fine after that. I then noticed in my Xorg.0.log.old the following suggesting there is at least on the initial login a problem with the NVIDIA driver. Here’s the relevant lines from the log file. Any ideas? Thanks.
36.368] (EE)
36.369] (EE) Backtrace:
36.369] (EE) 0: /usr/bin/X (xorg_backtrace+0x65) [0x5560283b2285]
36.369] (EE) 1: /usr/bin/X (0x556028200000+0x1b5f59) [0x5560283b5f59]
36.369] (EE) 2: /lib64/libpthread.so.0 (0x7f9fbbfa7000+0x168c0) [0x7f9fbbfbd8c0]
36.369] (EE) 3: /usr/lib64/xorg/modules/drivers/modesetting_drv.so (0x7f9e32ad1000+0x8e4f) [0x7f9e32ad9e4f]
36.369] (EE) 4: /usr/bin/X (RRCrtcSet+0x7b0) [0x556028314290]
36.369] (EE) 5: /usr/bin/X (ProcRRSetCrtcConfig+0x29e) [0x5560283154de]
36.369] (EE) 6: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f9fb8532000+0x469da2) [0x7f9fb899bda2]
36.369] (EE)
36.369] (EE) Segmentation fault at address 0x200000053
36.369] (EE)
Fatal server error:
36.369] (EE) Caught signal 11 (Segmentation fault). Server aborting
36.369] (EE)
36.369] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
If the proprietary NVIDIA driver is segment faulting on your older Laptop then, that’s it.
Fatal server error:
36.369] (EE) Caught signal 11 (Segmentation fault). Server aborting
- A quick explanation – a “Segment Fault” occurs when something (often a driver) attempts to access memory which is not available – either the memory address is out of range or, the protection on certain parts of memory has denied the attempted access.
In your particular case, there is memory associated with the GPU which, for the case of an older Laptop, may not be sufficient for the newest proprietary driver.
- What happens if, you were to use the open source “nouveau
” and “modesetting” drivers?
Thanks very much for the response. WIth Leap 15.3, I had poor performance with Nouveau and so went with NVIDIA proprietary driver and had much better success and it was stable. Since my initial post, ,I discovered that if instead of logging in graphically, if I go to another character based window and login in as myself and then run “startx” it comes up immediately and is fine. I the exited out, rebooted and I no longer have the issue with the graphical login. Very strange but I’m happy. I though it might be a one off so rebooted and tried directly logging in from the graphical login and again, it works fine. And I had rebooted numerous times before this and it always failed the first time. No idea why that resolved it but it does seem to now be resolved. Thanks again for the offer to help.
Well, I was wrong. The issue had nothing to do with startx. The problem will again occur on the graphical login. The issue appears to occur when I have the second monitor plugged in. Accessing KDE works fine if I login from one of the tty windows (ALT-F1) and run startx. All is well. If I log off (not even reboot) and then login via the graphical login (ALT-F7), it will fail as described above the first time. It then returns to the graphical login window and if I do nothing but enter my password again, it logs in successfully. If I keep the second monitor unplugged while doing the graphical login until after the kde screen appears, then I can plug it back in and all is well again. This setup used to work perfectly on LEAP 15.3 utilizing the NVIDIA proprietary driver. The change was I went to Leap 15.4 and now I have this minor (but annoying) issue. Any more ideas? Thanks.
You want to get help without providing hardware info.
Post
inxi -aGz
Thanks for offering to help. Here’s the code.
Post
inxi -aGz
**Graphics: Device-1:** NVIDIA GK107M [GeForce GT 750M] **vendor:** Lenovo **driver:** nvidia **v:** 470.129.06
**alternate:** nouveau,nvidia_drm **bus-ID:** 01:00.0 **chip-ID:** 10de:0fe4 **class-ID:** 0300
**Device-2:** NVIDIA GK107M [GeForce GT 750M] **vendor:** Lenovo **driver:** nvidia **v:** 470.129.06
**alternate:** nouveau,nvidia_drm **bus-ID:** 02:00.0 **chip-ID:** 10de:0fe4 **class-ID:** 0302
**Device-3:** Realtek Lenovo EasyCamera **type:** USB **driver:** uvcvideo **bus-ID:** 2-1:2 **chip-ID:** 0bda:58b9
**class-ID:** 0e02 **serial:** <filter>
**Display:** x11 **server:** X.Org 1.20.3 **compositor:** kwin_x11 **driver:****loaded:** modesetting,nvidia
**unloaded:** fbdev,nouveau,vesa **alternate:** nv **display-ID:** :0 **screens:** 1
**Screen-1:** 0 **s-res:** 1920x1080 **s-dpi:** 139 **s-size:** 351x191mm (13.8x7.5") **s-diag:** 400mm (15.7")
**Monitor-1:** LVDS-0 **res:** 1920x1080 **hz:** 60 **dpi:** 141 **size:** 345x194mm (13.6x7.6") **diag:** 396mm (15.6")
**OpenGL:****renderer:** NVIDIA GeForce GT 750M/PCIe/SSE2 **v:** 4.6.0 NVIDIA 470.129.06 **direct render:** Yes
[/QUOTE]
Hi all - This is still occurring. Can anyone help? Thanks.
Try switching to a different DM: sudo update-alternatives --config default-displaymanager
You may show journal of display-manager.service:
**erlangen:~ #** journalctl -b -u display-manager.service
Jul 27 09:17:07 erlangen systemd[1]: Starting X Display Manager...
Jul 27 09:17:07 erlangen display-manager[983]: /etc/vconsole.conf available
Jul 27 09:17:07 erlangen display-manager[983]: KEYMAP: de-nodeadkeys
Jul 27 09:17:07 erlangen display-manager[983]: Command: localectl set-keymap de-nodeadkeys
Jul 27 09:17:07 erlangen display-manager[983]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Jul 27 09:17:07 erlangen sddm[1016]: Initializing...
Jul 27 09:17:07 erlangen sddm[1016]: Starting...
Jul 27 09:17:07 erlangen sddm[1016]: Logind interface found
Jul 27 09:17:07 erlangen sddm[1016]: Adding new display on vt 7 ...
Jul 27 09:17:07 erlangen sddm[1016]: Loading theme configuration from ""
Jul 27 09:17:07 erlangen sddm[1016]: Display server starting...
Jul 27 09:17:07 erlangen sddm[1016]: Running: /usr/bin/X -nolisten tcp -dpi 192 -auth /run/sddm/{a6cbe01b-1015-47d7-ab4a-6035d66daa43} -background none -noreset -displayfd 17 -seat seat0 vt7
Jul 27 09:17:07 erlangen systemd[1]: Started X Display Manager.
Jul 27 09:17:07 erlangen sddm[1016]: Setting default cursor
Jul 27 09:17:07 erlangen sddm[1016]: Running display setup script "/usr/etc/X11/xdm/Xsetup"
Jul 27 09:17:07 erlangen sddm[1016]: Display server started.
Jul 27 09:17:07 erlangen sddm[1016]: Socket server starting...
Jul 27 09:17:07 erlangen sddm[1016]: Socket server started.
Jul 27 09:17:07 erlangen sddm[1016]: Loading theme configuration from "/usr/share/sddm/themes/breeze-openSUSE/theme.conf"
Jul 27 09:17:07 erlangen sddm[1016]: Greeter starting...
Jul 27 09:17:07 erlangen sddm-helper[1141]: [PAM] Starting...
Jul 27 09:17:07 erlangen sddm-helper[1141]: [PAM] Authenticating...
Jul 27 09:17:07 erlangen sddm-helper[1141]: [PAM] returning.
Jul 27 09:17:08 erlangen sddm-helper[1141]: pam_unix(sddm-greeter:session): session opened for user sddm(uid=477) by (uid=0)
Jul 27 09:17:08 erlangen sddm[1016]: Greeter session started successfully
Jul 27 09:17:08 erlangen sddm[1016]: Message received from greeter: Connect
Jul 27 09:17:15 erlangen sddm[1016]: Message received from greeter: Login
Jul 27 09:17:15 erlangen sddm[1016]: Reading from "/usr/share/xsessions/plasma5.desktop"
Jul 27 09:17:15 erlangen sddm[1016]: Reading from "/usr/share/xsessions/plasma5.desktop"
Jul 27 09:17:15 erlangen sddm[1016]: Session "/usr/share/xsessions/plasma5.desktop" selected, command: "/usr/bin/startplasma-x11"
Jul 27 09:17:15 erlangen sddm-helper[1243]: [PAM] Starting...
Jul 27 09:17:15 erlangen sddm-helper[1243]: [PAM] Authenticating...
Jul 27 09:17:15 erlangen sddm-helper[1243]: [PAM] Preparing to converse...
Jul 27 09:17:15 erlangen sddm-helper[1243]: [PAM] Conversation with 1 messages
Jul 27 09:17:15 erlangen sddm-helper[1243]: [PAM] returning.
Jul 27 09:17:15 erlangen sddm[1016]: Authenticated successfully
Jul 27 09:17:15 erlangen sddm[1016]: Auth: sddm-helper exited successfully
Jul 27 09:17:15 erlangen sddm[1016]: Greeter stopped.
Jul 27 09:17:15 erlangen sddm-helper[1243]: pam_unix(sddm:session): session opened for user karl(uid=1000) by (uid=0)
Jul 27 09:17:15 erlangen sddm-helper[1243]: Starting: "/usr/etc/X11/xdm/Xsession \"/usr/bin/startplasma-x11\""
Jul 27 09:17:15 erlangen sddm[1016]: Session started
**erlangen:~ #**
On 15.3 and 15.4 I get null response from this command logged in as root.
To much tinkering? The default installation has it:
**6700K:~ #** journalctl -b -u display-manager.service --directory /mnt/@/var/log/journal/ --no-pager --priority info
Jul 27 09:34:30 Leap-15-4 systemd[1]: Starting X Display Manager...
Jul 27 09:34:30 Leap-15-4 display-manager[993]: /etc/vconsole.conf available
Jul 27 09:34:30 Leap-15-4 display-manager[993]: KEYMAP: de-latin1-nodeadkeys
Jul 27 09:34:30 Leap-15-4 display-manager[993]: Command: localectl set-keymap de-latin1-nodeadkeys
Jul 27 09:34:30 Leap-15-4 display-manager[993]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Jul 27 09:34:31 Leap-15-4 display-manager[961]: Starting service sddm..done
Jul 27 09:34:31 Leap-15-4 systemd[1]: Started X Display Manager.
Jul 27 09:34:33 Leap-15-4 sddm-helper[1150]: pam_unix(sddm-autologin:session): session opened for user karl by (uid=0)
Jul 27 09:34:33 Leap-15-4 sddm-helper[1150]: Starting: "/etc/X11/xdm/Xsession \"/usr/bin/startplasma-x11\""
Jul 27 09:45:45 Leap-15-4 sddm[1062]: **Authentication error: "Process crashed"**
Jul 27 09:45:45 Leap-15-4 sddm[1062]: **Auth: sddm-helper crashed (exit code 15)**
Jul 27 09:45:45 Leap-15-4 sddm[1062]: **Authentication error: "Process crashed"**
Jul 27 09:45:45 Leap-15-4 sddm[1062]: **Auth: sddm-helper exited with 15**
Jul 27 09:45:45 Leap-15-4 systemd[1]: Stopping X Display Manager...
Jul 27 09:45:47 Leap-15-4 sddm[1062]: **Signal received: SIGTERM**
Jul 27 09:45:47 Leap-15-4 sddm[1062]: **QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.**
Jul 27 09:45:47 Leap-15-4 display-manager[2162]: Shutting down service sddm..done
Jul 27 09:45:47 Leap-15-4 systemd[1]: display-manager.service: Deactivated successfully.
Jul 27 09:45:47 Leap-15-4 systemd[1]: Stopped X Display Manager.
**6700K:~ #**
Output resulted this time:
# journalctl -b -u display-manager.service --directory /var/log/journal/ --no-pager --priority info
-- Logs begin at Thu 2017-09-07 21:20:47 EDT, end at Sat 2022-07-23 01:32:49 EDT. --
Jun 03 20:35:50 ... kdm_config[930]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc
Jun 03 20:35:50 ... kdm_config[930]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /opt/kde3/share/config/kdm/kdmrc
Jun 03 20:35:50 ... kdm_config[930]: Multiple occurrences of key 'AllowShutdown' in section [X-:*-Core] of /opt/kde3/share/config/kdm/kdmrc
Jun 11 15:51:47 ... kdm[929]: X server for display :0 terminated unexpectedly
Those “Multiple” lines apparently result from some process that doesn’t know how to not count symlinks and the files they point to twice. /opt/kde3/share/config/kdm/ is symlinked to /etc/kde/config/kdm/ for admin convenience.
Two equal Nvidia mobile video cards in a laptop?! Without Intel or AMD builtin GPU?!
Is it possible? 
Try to debug it with using LiveISO or installing OS on another drive.