No graphical login after leap 15 upgrade

English Install/Boot/Login
21

Without the xorg.conf I still cannot start a graphical user session. Using xdm I get a login screen, but after entering credentials the login screen re-appears. There some error messages in the log, but I 'm not sure what they mean.
After starting display-manager and an attempt to log in, journalctl says:


Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl systemd[1]: Starting X Display Manager...
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl display-manager[6899]: /etc/vconsole.conf available
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl display-manager[6899]: KEYMAP: us
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl display-manager[6899]: Command: localectl set-keymap us
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl display-manager[6899]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl dbus-daemon[1251]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.78' (uid=0 pid=6914 comm="localectl set-keymap us ")
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl systemd[1]: Starting Locale Service...
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl dbus-daemon[1251]: [system] Successfully activated service 'org.freedesktop.locale1'
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl systemd[1]: Started Locale Service.
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl root[6922]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl root[6922]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl kernel: **resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000dffff window]**
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl kernel: **caller _nv001169rm+0xe3/0x1d0 [nvidia] mapping multiple BARs**
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl kernel: nvidia-modeset: Allocated GPU:0 (GPU-c0ed6012-5f88-3a7b-9dfa-45b628e307ce) @ PCI:0000:01:00.0
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl display-manager[6899]: Starting service lightdm..done
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl systemd[1]: Started X Display Manager.
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl acpid[1293]: **client 6803[0:0] has disconnected**
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl acpid[1293]: **client connected from 6964[0:0]**
Jul 15 12:08:12 biesbosch.teslanet.tesla.demon.nl acpid[1293]: 1 client rule loaded
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl lightdm[6958]: **g_object_unref: assertion 'G_IS_OBJECT (object)' failed**
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[1]: Created slice User Slice of lightdm.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[1]: Starting User Manager for UID 484...
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd-logind[2086]: New session 10 of user lightdm.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[1]: Started Session 10 of user lightdm.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Reached target Paths.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Reached target Timers.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Starting D-Bus User Message Bus Socket.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Listening on D-Bus User Message Bus Socket.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Reached target Sockets.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Reached target Basic System.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Reached target Default.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Startup finished in 30ms.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[1]: Started User Manager for UID 484.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl lightdm[6975]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Started D-Bus User Message Bus.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl dbus-daemon[6995]: [session uid=484 pid=6995] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=484 pid=6993 comm="/usr/sbin/lightdm-gtk-greeter ")
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Starting Accessibility services bus...
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl dbus-daemon[6995]: [session uid=484 pid=6995] Successfully activated service 'org.a11y.Bus'
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Started Accessibility services bus.
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[6996]: dbus-daemon[7001]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=484 pid=6993 comm="/usr/sbin/lightdm-gtk-greeter ")
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl dbus-daemon[6995]: [session uid=484 pid=6995] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=484 pid=6993 comm="/usr/sbin/lightdm-gtk-greeter ")
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Starting Virtual filesystem service...
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[6996]: dbus-daemon[7001]: Successfully activated service 'org.a11y.atspi.Registry'
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[6996]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl dbus-daemon[6995]: [session uid=484 pid=6995] Successfully activated service 'org.gtk.vfs.Daemon'
Jul 15 12:08:13 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Started Virtual filesystem service.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[1]: session-10.scope: Killing process 6975 (lightdm) with signal SIGTERM.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[1]: session-10.scope: Killing process 6993 (lightdm-gtk-gre) with signal SIGTERM.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[1]: Stopping Session 10 of user lightdm.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl lightdm[6975]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[1]: Stopped Session 10 of user lightdm.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd-logind[2086]: Removed session 10.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[1]: Stopping User Manager for UID 484...
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Stopping Accessibility services bus...
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Stopping D-Bus User Message Bus...
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Stopping Virtual filesystem service...
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Stopped target Default.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Stopped D-Bus User Message Bus.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Stopped Accessibility services bus.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl lightdm[6958]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd-logind[2086]: New session 11 of user rogier.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[1]: Started Session 11 of user rogier.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl lightdm[7026]: pam_unix(lightdm:session): session opened for user rogier by (uid=0)
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Stopped Virtual filesystem service.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Stopped target Basic System.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Stopped target Paths.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Stopped target Timers.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Stopped target Sockets.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Closed D-Bus User Message Bus Socket.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Reached target Shutdown.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Starting Exit the Session...
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[6987]: Received SIGRTMIN+24 from PID 7042 (kill).
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[1]: Stopped User Manager for UID 484.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd[1]: Removed slice User Slice of lightdm.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[2800]: dbus-daemon[2805]: Activating service name='org.a11y.atspi.Registry' requested by ':1.4' (uid=1000 pid=7095 comm="nvidia-settings --load-config-only ")
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[2800]: dbus-daemon[2805]: Successfully activated service 'org.a11y.atspi.Registry'
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[2800]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl lightdm[7026]: pam_unix(lightdm:session): session closed for user rogier
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl systemd-logind[2086]: Removed session 11.
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[2800]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jul 15 12:08:50 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[2800]:       after 21 requests (19 known processed) with 0 events remaining.
Jul 15 12:08:51 biesbosch.teslanet.tesla.demon.nl kernel: nvidia-modeset: Freed GPU:0 (GPU-c0ed6012-5f88-3a7b-9dfa-45b628e307ce) @ PCI:0000:01:00.0
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000dffff window]
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl kernel: caller _nv001169rm+0xe3/0x1d0 [nvidia] mapping multiple BARs
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl kernel: nvidia-modeset: Allocated GPU:0 (GPU-c0ed6012-5f88-3a7b-9dfa-45b628e307ce) @ PCI:0000:01:00.0
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl acpid[1293]: client 6964[0:0] has disconnected
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl acpid[1293]: client connected from 7148[0:0]
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl acpid[1293]: 1 client rule loaded
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl lightdm[6958]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[1]: Created slice User Slice of lightdm.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[1]: Starting User Manager for UID 484...
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd-logind[2086]: New session 12 of user lightdm.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[1]: Started Session 12 of user lightdm.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Reached target Paths.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Starting D-Bus User Message Bus Socket.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Reached target Timers.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Listening on D-Bus User Message Bus Socket.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Reached target Sockets.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Reached target Basic System.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Reached target Default.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Startup finished in 30ms.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[1]: Started User Manager for UID 484.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl lightdm[7155]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Started D-Bus User Message Bus.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl dbus-daemon[7175]: [session uid=484 pid=7175] Activating systemd to hand-off: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.0' (uid=484 pid=7173 comm="/usr/sbin/lightdm-gtk-greeter ")
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl dbus-daemon[7175]: [session uid=484 pid=7175] Successfully activated service 'org.freedesktop.systemd1'
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Starting Accessibility services bus...
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl dbus-daemon[7175]: [session uid=484 pid=7175] Successfully activated service 'org.a11y.Bus'
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Started Accessibility services bus.
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[7176]: dbus-daemon[7181]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=484 pid=7173 comm="/usr/sbin/lightdm-gtk-greeter ")
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl dbus-daemon[7175]: [session uid=484 pid=7175] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=484 pid=7173 comm="/usr/sbin/lightdm-gtk-greeter ")
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Starting Virtual filesystem service...
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[7176]: dbus-daemon[7181]: Successfully activated service 'org.a11y.atspi.Registry'
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[7176]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl dbus-daemon[7175]: [session uid=484 pid=7175] Successfully activated service 'org.gtk.vfs.Daemon'
Jul 15 12:08:52 biesbosch.teslanet.tesla.demon.nl systemd[7167]: Started Virtual filesystem service.
22

When I update kernel I must reinstall the nvidia driver. If not I did not get the graphical interface to work.
I suggest you to try the following task that helped me, but without guarantee.

**boot in text mode** by editing the command line argument during bootup ( press key 'e' ) then **add init 3** to command line argument
then **press f10** to continue booting

If not already done : **zypper install** -t pattern devel_C_C++ devel_kernel

If not already done : **zypper install** dkms

**zypper up**

**systemctl enable dkms.service**
**systemctl start dkms.service**

run **yast** and Modify kernel boot : Add '**nomodeset**' on kernel boot  command line argument"

Run that command : '**echo blacklist nouveau >> /etc/modprobe.d/50-blacklist.conf && mkinitrd && reboot**'

List drm-kmp-default module installed : **zypper se -si drm-kmp-default**
Removed all drm-kmp-default if any installed : **zypper rm --name drm-kmp-default**

**cd to folder **where your nvidia driver is.

remove nvidia driver : Run this (based on a x86_64 driver) : **sh NVIDIA-Linux-x86_64-*.run --uninstall**

**reboot** in text mode ( as said at the beginning )

**cd to folder** where your nvidia driver is.

Install the driver : **sh NVIDIA-Linux-x86_64-*.run
**
just **reboot** and pray.

You can now **remove** 'nomodeset' in command line argument using yast
23

Post:

cat /var/log/lightdm/lightdm.log
24

cat /var/log/lightdm/lightdm.log :


+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
+0.00s] DEBUG: Starting Light Display Manager 1.24.1, UID=0 PID=6958
+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-suse-defaults.conf
+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
+0.00s] DEBUG: Registered seat module local
+0.00s] DEBUG: Registered seat module xremote
+0.00s] DEBUG: Registered seat module unity
+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
+0.00s] DEBUG: Monitoring logind for seats
+0.00s] DEBUG: New seat added from logind: seat0
+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
+0.00s] DEBUG: Seat seat0: Starting
+0.00s] DEBUG: Seat seat0: Creating greeter session
+0.00s] DEBUG: Seat seat0: Creating display server of type x
+0.01s] DEBUG: Using VT 7
+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
+0.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
+0.01s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
+0.01s] DEBUG: XServer 0: Launching X Server
+0.01s] DEBUG: Launching process 6964: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
+0.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0
+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
+0.01s] DEBUG: User /org/freedesktop/Accounts/User1001 added
+0.01s] DEBUG: User /org/freedesktop/Accounts/User1010 added
+0.01s] DEBUG: User /org/freedesktop/Accounts/User1002 added
+0.01s] DEBUG: User /org/freedesktop/Accounts/User1011 added
+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added
+0.99s] DEBUG: Got signal 10 from process 6964
+0.99s] DEBUG: XServer 0: Got signal from X server :0
+0.99s] DEBUG: XServer 0: Connecting to XServer :0
+0.99s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
+0.99s] DEBUG: Seat seat0: Display server ready, starting session authentication
+0.99s] DEBUG: Session pid=6975: Started with service 'lightdm-greeter', username 'lightdm'
+1.01s] DEBUG: Session pid=6975: Authentication complete with return value 0: Success
+1.01s] DEBUG: Seat seat0: Session authenticated, running command
+1.01s] DEBUG: Launching process 6978: /etc/X11/xdm/Xsetup
+1.04s] DEBUG: Process 6978 exited with return value 0
+1.04s] DEBUG: Seat seat0: Exit status of /etc/X11/xdm/Xsetup: 0
+1.04s] DEBUG: Session pid=6975: Running command /usr/sbin/lightdm-gtk-greeter
+1.04s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
+1.04s] DEBUG: Session pid=6975: Logging to /var/log/lightdm/seat0-greeter.log
+1.10s] DEBUG: Activating VT 7
+1.10s] DEBUG: Activating login1 session 10
+1.10s] DEBUG: Seat seat0 changes active session to 10
+1.10s] DEBUG: Session 10 is already active
+1.25s] DEBUG: Greeter connected version=1.24.1 api=1 resettable=false
+1.64s] DEBUG: Greeter start authentication for rogier
+1.64s] DEBUG: Session pid=7026: Started with service 'lightdm', username 'rogier'
+1.65s] DEBUG: Session pid=7026: Got 1 message(s) from PAM
+1.65s] DEBUG: Prompt greeter with 1 message(s)
+37.49s] DEBUG: Continue authentication
+37.52s] DEBUG: Session pid=7026: Authentication complete with return value 0: Success
+37.52s] DEBUG: Authenticate result for user rogier: Success
+37.52s] DEBUG: User rogier authorized
+37.53s] DEBUG: Greeter sets language nl_NL.utf8
+37.59s] DEBUG: Greeter requests session plasma5
+37.59s] DEBUG: Seat seat0: Stopping greeter; display server will be re-used for user session
+37.59s] DEBUG: Terminating login1 session 10
+37.59s] DEBUG: Session pid=6975: Sending SIGTERM
+37.61s] DEBUG: Greeter closed communication channel
+37.61s] DEBUG: Session pid=6975: Exited with return value 0
+37.61s] DEBUG: Seat seat0: Session stopped
+37.61s] DEBUG: Seat seat0: Greeter stopped, running session
+37.61s] DEBUG: Launching process 7031: /etc/X11/xdm/Xstartup
+37.63s] DEBUG: Process 7031 exited with return value 0
+37.63s] DEBUG: Seat seat0: Exit status of /etc/X11/xdm/Xstartup: 0
+37.63s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
+37.63s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
+37.63s] DEBUG: Session pid=7026: Running command /etc/X11/xdm/Xsession /usr/bin/startkde
+37.63s] DEBUG: Creating shared data directory /var/lib/lightdm-data/rogier
+37.63s] DEBUG: Session pid=7026: Logging to .xsession-errors
+37.65s] DEBUG: Activating VT 7
+37.65s] DEBUG: Activating login1 session 11
+37.65s] DEBUG: Seat seat0 changes active session to 
+37.65s] DEBUG: Seat seat0 changes active session to 11
+37.65s] DEBUG: Session 11 is already active
+37.90s] DEBUG: Session pid=7026: Exited with return value 1
+37.90s] DEBUG: Seat seat0: Session stopped
+37.90s] DEBUG: Launching process 7140: /etc/X11/xdm/Xreset
+37.91s] DEBUG: Process 7140 exited with return value 0
+37.91s] DEBUG: Seat seat0: Exit status of /etc/X11/xdm/Xreset: 0
+37.91s] DEBUG: Seat seat0: Stopping display server, no sessions require it
+37.91s] DEBUG: Sending signal 15 to process 6964
+37.91s] DEBUG: Seat seat0 changes active session to 
+39.29s] DEBUG: Process 6964 exited with return value 0
+39.29s] DEBUG: XServer 0: X server stopped
+39.29s] DEBUG: Releasing VT 7
+39.29s] DEBUG: XServer 0: Removing X server authority /run/lightdm/root/:0
+39.29s] DEBUG: Seat seat0: Display server stopped
+39.29s] DEBUG: Seat seat0: Active display server stopped, starting greeter
+39.29s] DEBUG: Seat seat0: Creating greeter session
+39.29s] DEBUG: Seat seat0: Creating display server of type x
+39.29s] DEBUG: Using VT 7
+39.29s] DEBUG: Seat seat0: Starting local X display on VT 7
+39.29s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
+39.29s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
+39.29s] DEBUG: XServer 0: Launching X Server
+39.29s] DEBUG: Launching process 7148: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
+39.29s] DEBUG: XServer 0: Waiting for ready signal from X server :0
+40.25s] DEBUG: Got signal 10 from process 7148
+40.25s] DEBUG: XServer 0: Got signal from X server :0
+40.25s] DEBUG: XServer 0: Connecting to XServer :0
+40.25s] CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
+40.25s] DEBUG: Seat seat0: Display server ready, starting session authentication
+40.25s] DEBUG: Session pid=7155: Started with service 'lightdm-greeter', username 'lightdm'
+40.27s] DEBUG: Session pid=7155: Authentication complete with return value 0: Success
+40.27s] DEBUG: Seat seat0: Session authenticated, running command
+40.27s] DEBUG: Launching process 7158: /etc/X11/xdm/Xsetup
+40.30s] DEBUG: Process 7158 exited with return value 0
+40.30s] DEBUG: Seat seat0: Exit status of /etc/X11/xdm/Xsetup: 0
+40.30s] DEBUG: Session pid=7155: Running command /usr/sbin/lightdm-gtk-greeter
+40.30s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
+40.30s] DEBUG: Session pid=7155: Logging to /var/log/lightdm/seat0-greeter.log
+40.35s] DEBUG: Activating VT 7
+40.36s] DEBUG: Activating login1 session 12
+40.36s] DEBUG: Seat seat0 changes active session to 12
+40.36s] DEBUG: Session 12 is already active
+40.51s] DEBUG: Greeter connected version=1.24.1 api=1 resettable=false
+40.90s] DEBUG: Greeter start authentication for rogier
+40.90s] DEBUG: Session pid=7206: Started with service 'lightdm', username 'rogier'
+40.91s] DEBUG: Session pid=7206: Got 1 message(s) from PAM
+40.91s] DEBUG: Prompt greeter with 1 message(s)
25

OK, you suggest a manual reinstall of the driver. I did that several times using Yast. Do you think Yast did it not in the right way?

What puzzles me is that you suggest blacklisting **nouveau. **Thought that is nowadays cared for by the nVidia install automaticly.
On the other hand I see the nouveau module is loaded nevertheless. In my past experience X wouldn’t run when there a conflict there - doesn’t seem the case because X is running.

So, is nouveau suppost to being loaded together with nvidia??

26

I tried to use the nouveau driver instead of nvidia, in case the nvidia install goes wrong that should make a difference…

So I uninstalled nvidia using Yast. Afterwards the nvidia modules were still loaded in the kernel. Found and removed them them using lsmod | grep nvidia. Removed each module: modprobe -r <modulename> (account for their dependencies in the order of removal) . Made sure the nvidia rpm’s were really not installed any more, so I wouldn’t break the system.

After reboot the nvdia modules were back again… turns out the module were still present in the /lib/modules/4.12.14-lp150.12.4-default folder! (is this a caused by not removiing nvidia before leap 15 upgrade??).

So removed them by *rm /lib/modules/4.12.14-lp150.12.4-default/updates/nvidia.ko, **followed by depmod -a ; mkinitrd to make this permanent.

After reboot the nouveau driver was loaded and nvidia modules not anymore. No luck on the graphical login though. Still not working!

Searching further in fora I stumbled on others that had problems with displaymanagers, one had a problem with /tmp directory access. So looked into my /tmp and… (sigh) the logical volume of /tmp is full! Apparently /tmp is essential for creating graphical user sessions.

After cleaning up /tmp I can start KDE sessions again, problem SOLVED!
Installed the nvidia driver again and it runs without a problem.

Lessons learned:

  1. uninstall nvidia before openSuse upgrade (couldn’t this be automated?)
  2. cleanup /tmp regularly. (could software not cleanup their own mess?)
  3. On problems have quick look at the filesystem… :wink:

Thanks for all your support and suggestions!

27

On

  1. Should not be necessary, if the nvidia repo is set to the proper URL
  2. AFAIK cleanup of /tmp already is automated, but you may have hit an exceptional situation
  3. Always one of the things to check, yep :smiley:
28

The string init all by itself on a kernel command like that is inert, does nothing. The 3 all by itself causes the ‘init 3’ command’s closest systemd target multi-user to be applied instead of the default, which is usually graphical (init 5 equivalent).

29

Hi,

i’ve a similar problem with an Intel IGP on kernel 4.12.14-lp150.12.4-default, the only difference is that i’m able to start display manager with an old kernel… at random times.
I’m running on kernel 4.4.138-59-default at the time, with sddm and plasma5 as desktop.

 /usr/sbin/hwinfo --gfxcard  
08: PCI 02.0: 0300 VGA compatible controller (VGA)               
  [Created at pci.378]
  Unique ID: _Znp.bn_Uutzzxq8
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x0412 "Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller"
  SubVendor: pci 0x1458 "Gigabyte Technology Co., Ltd"
  SubDevice: pci 0xd000  
  Revision: 0x06
  Driver: "i915"
  Driver Modules: "drm"
  Memory Range: 0xf7800000-0xf7bfffff (rw,non-prefetchable)
  Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable)
  I/O Ports: 0xf000-0xf03f (rw)
  IRQ: 28 (69760 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00008086d00000412sv00001458sd0000D000bc03sc00i00"
  Driver Info #0:
    Driver Status: i915 is active
    Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
Primary display adapter: #8

This started after the upgrade, it dropped me on console when booting at default config, had to start lvl 5 manually everytime… now it just doesn’t work either that way.
I’ll be glad to provide any other info.
Regards

30

Your not alone :), I’m experiencing this too but for experimental purpose only I might try all the fix that I can search then if I might able to find a work around I’ll post it here.

31

Please try, a forced reinstall from a VT (tty1/tty2) prompt – user “root” – Ethernet cable plugged in – ( zypper install --force ) of:

  • sddm
  • sddm-branding-openSUSE
  • sddm-theme-openSUSE
  • kcm_sddm
  • kcm_sddm-lang

Then, check if, some old files (Leap 42.3 and older) are present in ‘/usr/share/sddm/themes/breeze-openSUSE/’.

  • I had “1920x1080.jpg” on one system – the Leap 42.3 sddm login splash – and “theme.conf.user” also present on other systems.
  • Remove these “no longer needed with Leap 15.0” files.
  • Check, against the file lists of the above packages ( rpm --query --list ) for any other Leap 42.3 (and older) files which are no longer needed.
  • With the user “root” (a “normal” user doesn’t find this command … ), execute ‘rpmconfigcheck’ and then, perform the housekeeping output by this check.
  • With the user “root”, execute ‘rpm --verify --all’ and then, perform the housekeeping output by this check.
32

Further to this issue with upgraded from Leap 42.3 to Leap 15.0 with a Nvidia graphic card, there’s also the following KDE Blog post: <https://blogs.kde.org/2018/07/21/upgrading-opensuse-leap-150>.

33

This is an old thread, but I found it researching the same problem. I will add my recent experience, in case it helps someone.

I merely did a typical online update with Leap 15.2, which included a kernel update, so I had to reboot. The system ended up booting fine, but sddm-greeter didn’t start so I had a blank screen with a mouse cursor on tty7. Reading through this thread, I started wondering. The proprietary NVIDIA driver loaded just fine because tty7 worked fine, and my dual-screen setup looked normal in text mode.

(Without the NVIDIA driver working, my second screen looks very strange in a text console because my two monitors have different resolutions. The fancy driver scales the smaller monitor properly to show the same thing.)

So, I fired up YaST in a terminal, headed to Software Management, and searched for ‘nouveau’. I discovered that two packages were loaded that I did not want loaded: xf86-video-nouveau and xf86-video-nv. Before I went full out like suggested above, I thought I’d just try deleting those two packages, so I did that. I tried to restart the display service, but didn’t do it right, so my blank screen on tty7 persisted.

So, I rebooted and all returned to normal. sddm started properly and I could log into the graphical session.

I don’t know why those two nouveau packages were installed, but I will guess that sddm-greeter got confused and crashed with them installed. This was a much simpler fix than uninstalling and then reinstalling the NVIDIA stuff.

34

nouveau is normally installed but NVIDIA driver should take president over it and you should never NEED to uninstall nouveau drivers. nv is a much older fall back driver and again no need to uninstall. The fact you had to points to something else wrong somewhere. :open_mouth:

35

“Had to” is too strong. I uninstalled those two drivers and rebooted, and everything worked again. It’s impossible to tell now if simply rebooting would’ve been sufficient. I just figured the nouveau drivers were unnecessary and it was worth a try to uninstall them before spending quite a bit more time uninstalling and reinstalling drivers that definitely appeared to work fine.

If something else is wrong somewhere else, I wouldn’t know because my XFCE session is doing just fine now. I don’t reboot very often, and the next time will be to upgrade to Leap 15.3, which I hope goes smoothly.

36

Performing an online upgrade from LEAP 15.2 to 15.3 I faced same result: black screen on VT7, blinking cursor, no login.

My machines history: fresh install LEAP 15.0 (XFCE, lighdm, NVIDIA drivers), then upgrades to 15.1, 15.2 and recently 15.3. No issues with previous upgrades.

Rebooting did not fix the issue. My personal fix was to deinstall (Yast/zypper) all propriety NVIDIA stuff. Then reboot and login was back in place based on nouveau graphics driver. BUT latest kernel upgrade triggered the same issue again, NVIDIA stuff was back in place and after reboot I had black VT7 with blinking cursor. Solution: same as before plus reboot …

Removed packages:


nvidia-computeG05-470.74-lp153.44.1.x86_64
nvidia-gfxG05-kmp-default-470.74_k5.3.18_57-lp153.44.1.x86_64
x11-video-nvidiaG05-470.74-lp153.44.1.x86_64
nvidia-glG05-470.74-lp153.44.1.x86_64

And this back screen issue was back with first kernel upgrade which did reinstall NVIDIA drivers. So, something seems to be wrong after installing NVIDIA drivers (which did work fine on 15.0, 15.1 and 15.2).

37

They got installed because the meta-package xorg-x11-driver-video got installed, which installs all 31 xf86-video-* packages.