No graphical login after leap 15 upgrade

Hi,

Graphical login does not work after upgrade to leap 15 (was leap 42.3) .

At first sddm was constantly restarting, giving flashy screen. I installed the propriety NVIDIA driver to rule out nouveau issues. (had to deinstall and reinstall to get the nvidia modules loaded. ) .

Now, after boot, I get a black screen with a mouse cursor, but still no graphical login. Logging shows that sddm-greeter has core-dumped:


Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm[5772]: Greeter session started successfully
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-greeter[5846]: High-DPI autoscaling not Enabled
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-greeter[5846]: Reading from "/usr/share/xsessions/icewm-session.desktop"
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-greeter[5846]: Reading from "/usr/share/xsessions/icewm.desktop"
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-greeter[5846]: Reading from "/usr/share/xsessions/plasma5.desktop"
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-greeter[5846]: Reading from "/usr/share/xsessions/twm.desktop"
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-greeter[5846]: Reading from "/usr/share/xsessions/xsession.desktop"
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-greeter[5846]: inotify_add_watch("/usr/share/wayland-sessions") failed: "No such file or directory"
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-greeter[5846]: Loading theme configuration from "/usr/share/sddm/themes/breeze-openSUSE/theme.conf"
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Started D-Bus User Message Bus.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-greeter[5846]: Connected to the daemon.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm[5772]: Message received from greeter: Connect
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[1]: Started Process Core Dump (PID 5850/UID 0).
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-helper[5838]: [PAM] Closing session
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-helper[5838]: pam_unix(sddm-greeter:session): session closed for user sddm
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm-helper[5838]: [PAM] Ended.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm[5772]: Auth: sddm-helper exited with 7
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl sddm[5772]: Greeter stopped.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd-logind[1935]: Removed session 11.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[1]: Stopping User Manager for UID 491...
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Stopped target Default.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Stopping D-Bus User Message Bus...
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Stopped D-Bus User Message Bus.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Stopped target Basic System.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Stopped target Timers.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Stopped target Sockets.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Stopped target Paths.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Closed D-Bus User Message Bus Socket.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Reached target Shutdown.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Starting Exit the Session...
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5840]: Received SIGRTMIN+24 from PID 5853 (kill).
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[5841]: pam_unix(systemd-user:session): session closed for user sddm
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[1]: Stopped User Manager for UID 491.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd[1]: Removed slice User Slice of sddm.
Jul 12 11:56:54 biesbosch.teslanet.tesla.demon.nl systemd-coredump[5851]: **Process 5846 (sddm-greeter) of user 491 dumped core**.

There are no errors in /var/log/Xorg.0.log
Can anyone help?

the hardware:
AMD Phenom™ II X3 705e Processor
nVidia GK208 [GeForce GT 730]

Before you upgraded, did you install the proprietary nVidia driver or were you using the Nouveau driver?
And, if you were using the nVidia driver, which method did you use to install it?

From what you describe,
I’d suspect the GPU driver you’re using, and wouldn’t suspect the Display Manager as an accomplice.

Have you tried booting to Rescue Mode (When your Grub menu displays, select Advanced then the second entry of any kernel pair of entries).

If booting to rescue mode doesn’t work, you might try booting the LEAP 15 DVD, then select either a Rescue or Upgrade option, the object is to replace whatever GPU driver you’re now using with something safe and works, even if it’s for the moment not the optimal/best possible option.

TSU

Ctrl + Alt + F2> login>

su -

check with zypper or yast --ncurses> if there are updates

The Repositories you have activated will also be checked

The propriety Nvidia driver was indeed installed before upgrade.

Booting is no problem. The system boots and I can login the console normally. Just the graphical login screen doesn’t appear. So there is no need to use Rescue Mode I think.
I have a Mouse arrow on the screen. That means X is running, right? X wouldnt run when the NVidia driver isn’t working I assume… also Xorg.0.log shows no errors.
So looks like NVidia and X are happy

zypper update gives “Nothing to do.”
The update repositories are enabled, so the system should be up to date.

Remove and reinstall NVIDIA driver

Post:

ls -al /var/lib/sddm

Try

update-alternatives --config default-displaymanager

And choose not the auto mode, choose the manual mode.

It might also be helpful to know the method you are using to install your nVidia driver.
And, if you have problems using the nouveau driver

TSU

… or, even use this method to change to another display manager, such as XDM or LightDM, see if that solves your problem.

Tried this again. No change…

it gives:


ls -al /var/lib/sddm
total 20
drwxr-x---  5 sddm sddm 4096 May 14 23:31 .
drwxr-xr-x 74 root root 4096 Jul 10 22:30 ..
drwxrwxr-x  2 sddm sddm 4096 Jul 12 00:11 .cache
drwxrwxr-x  2 sddm sddm 4096 Jul 11 18:53 .config
drwxrwxr-x  3 sddm sddm 4096 Jul 11 18:53 .local

Choosing manual mode for sddm makes no difference.
When set to xdm a login screen shows. After entering credentials however no
session is started. The login screen reappears again…

Logging shows:



Jul 14 15:11:38 biesbosch.teslanet.tesla.demon.nl systemd-logind[1932]: New session 12 of user rogier.
Jul 14 15:11:38 biesbosch.teslanet.tesla.demon.nl systemd[1]: Started Session 12 of user rogier.
Jul 14 15:11:38 biesbosch.teslanet.tesla.demon.nl xdm[16711]: pam_unix(xdm:session): session opened for user rogier by (uid=0)
Jul 14 15:11:38 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[16096]: dbus-daemon[16103]: Activating service name='org.a11y.atspi.Registry' requested by ':1.10' (uid=1000 pid=16784 comm="nvidia-settings --load-config>
Jul 14 15:11:38 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[16096]: dbus-daemon[16103]: Successfully activated service 'org.a11y.atspi.Registry'
Jul 14 15:11:38 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[16096]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jul 14 15:11:38 biesbosch.teslanet.tesla.demon.nl xdm[16711]: pam_unix(xdm:session): session closed for user rogier
Jul 14 15:11:38 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[16096]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jul 14 15:11:38 biesbosch.teslanet.tesla.demon.nl at-spi-bus-launcher[16096]:       after 21 requests (19 known processed) with 0 events remaining.
Jul 14 15:11:38 biesbosch.teslanet.tesla.demon.nl systemd-logind[1932]: Removed session 12.
Jul 14 15:11:39 biesbosch.teslanet.tesla.demon.nl kernel: nvidia-modeset: Freed GPU:0 (GPU-c0ed6012-5f88-3a7b-9dfa-45b628e307ce) @ PCI:0000:01:00.0
Jul 14 15:11:40 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 14 15:11:40 biesbosch.teslanet.tesla.demon.nl kernel: caller _nv001169rm+0xe3/0x1d0 [nvidia] mapping multiple BARs
Jul 14 15:11:40 biesbosch.teslanet.tesla.demon.nl kernel: nvidia-modeset: Allocated GPU:0 (GPU-c0ed6012-5f88-3a7b-9dfa-45b628e307ce) @ PCI:0000:01:00.0
Jul 14 15:11:40 biesbosch.teslanet.tesla.demon.nl acpid[1114]: client 16705[0:0] has disconnected
Jul 14 15:11:40 biesbosch.teslanet.tesla.demon.nl acpid[1114]: client connected from 16832[0:0]
Jul 14 15:11:40 biesbosch.teslanet.tesla.demon.nl acpid[1114]: 1 client rule loaded

Looks like the connection to X doesn’t work, but why?

Used Yast and community nVidia repo. Sticked with this driver because graphics card worked fine with it before…

Also found this in Xorg.0.log:


 14429.304] (EE) systemd-logind: failed to get session: PID 16832 does not belong to any known session

Not sure what that means…

That sounds like a zombie process ie one that did not terminate correctly

ps -A | grep 16832

to find name

hm, no zombie. it’s the X process…


ps -A | grep 16832
16832 tty7     00:00:00 X

Post:

zypper se -si kernel nvidia
zypper lr -d
cat /var/log/Xorg.0.log
/sbin/lspci -nnk | grep -EiA3 'vga|3d|display'

here it is…:


# zypper se -si kernel nvidia
Loading repository data...                                                                                    
Reading installed packages...                                                                                               
                                                                                                                                    
S  | Name                      | Type    | Version                             | Arch   | Repository                                        
---+---------------------------+---------+------------------------------------+--------+------------------------                            
i+ | kernel-default            | package | 4.4.138-59.1                        | x86_64 | (System Packages)                                        
i+ | kernel-default            | package | 4.12.14-lp150.12.4.1               | x86_64 | Main Update Repository 
i+ | kernel-default-devel      | package | 4.4.138-59.1                       | x86_64 | (System Packages)      
i+ | kernel-default-devel      | package | 4.12.14-lp150.12.4.1               | x86_64 | Main Update Repository 
i+ | kernel-devel              | package | 4.4.138-59.1                       | noarch | (System Packages)      
i+ | kernel-devel              | package | 4.12.14-lp150.12.4.1               | noarch | Main Update Repository 
i+ | kernel-firmware           | package | 20180416-lp150.1.4                 | noarch | Main Repository (OSS)  
i+ | kernel-macros             | package | 4.12.14-lp150.12.4.1               | noarch | Main Update Repository 
i+ | kernel-source             | package | 4.4.138-59.1                       | noarch | (System Packages)      
i+ | kernel-source             | package | 4.12.14-lp150.12.4.1               | noarch | Main Update Repository 
i+ | kernel-syms               | package | 4.4.138-59.1                       | x86_64 | (System Packages)      
i+ | kernel-syms               | package | 4.12.14-lp150.12.4.1               | x86_64 | Main Update Repository 
i+ | nvidia-computeG04         | package | 390.67-lp150.8.1                   | x86_64 | nVidia Graphics Drivers
i  | nvidia-gfxG04-kmp-default | package | 390.67_k4.12.14_lp150.11-lp150.8.1 | x86_64 | nVidia Graphics Drivers
i  | nvidia-glG04              | package | 390.67-lp150.8.1                   | x86_64 | nVidia Graphics Drivers
i  | nvidia-texture-tools      | package | 2.0.8-lp150.1.4                    | x86_64 | Main Repository (OSS)  
i  | x11-video-nvidiaG04       | package | 390.67-lp150.8.1                   | x86_64 | nVidia Graphics Drivers


zypper lr -d
Repository priorities are without effect. All enabled repositories share  the same priority.                                                                                     
                                                                                                                                                                                 
#  | Alias                           | Name                                     | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                       | Service
---+---------------------------------+-----------------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------+--------
 1 | download.nvidia.com-leap        | nVidia Graphics Drivers                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |  https://download.nvidia.com/opensuse/leap/15.0                            |        
 2 | download.opensuse.org-non-oss   | Main Repository (NON-OSS)                | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |  http://download.opensuse.org/distribution/leap/15.0/repo/non-oss/         |        
 3 | download.opensuse.org-non-oss_1 | Update Repository (Non-Oss)              | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |  http://download.opensuse.org/update/leap/15.0/non-oss/                    |        
 4 | download.opensuse.org-oss       | Main Repository (OSS)                    | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |  http://download.opensuse.org/distribution/leap/15.0/repo/oss/             |        
 5 | download.opensuse.org-oss_1     | Main Update Repository                   | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |  http://download.opensuse.org/update/leap/15.0/oss                         |        
 6 | openSUSE-Leap-15.0-1            | openSUSE-Leap-15.0-1                     | No      | ----      | ----    |   99     | rpm-md |  cd:///?devices=/dev/disk/by-id/ata-ASUS_DRW-24F1MT_S1AR6YDGA00289         |        
 7 | opensuse-guide.org-repo         | Libdvdcss Repository                     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |  http://opensuse-guide.org/repo/openSUSE_Leap_15.0/                        |        
 8 | packman.inode.at-suse           | Packman Repository                       | Yes     | (r ) Yes  | Yes     |   99     | rpm-md |  http://packman.inode.at/suse/openSUSE_Leap_15.0/                          |        
 9 | repo-debug                      | openSUSE-Leap-15.0-Debug                 | No      | ----      | ----    |   99     | rpm-md |  http://download.opensuse.org/debug/distribution/leap/15.0/repo/oss/       |        
10 | repo-debug-non-oss              | openSUSE-Leap-15.0-Debug-Non-Oss         | No      | ----      | ----    |   99     | rpm-md |  http://download.opensuse.org/debug/distribution/leap/15.0/repo/non-oss/   |        
11 | repo-debug-update               | openSUSE-Leap-15.0-Update-Debug          | No      | ----      | ----    |   99     | rpm-md |  http://download.opensuse.org/debug/update/leap/15.0/oss/                  |        
12 | repo-debug-update-non-oss       |  openSUSE-Leap-15.0-Update-Debug-Non-Oss | No      | ----      | ----     |   99     | rpm-md |  http://download.opensuse.org/debug/update/leap/15.0/non-oss/              |        
13 | repo-source                     | openSUSE-Leap-15.0-Source                | No      | ----      | ----    |   99     | rpm-md |  http://download.opensuse.org/source/distribution/leap/15.0/repo/oss/      |        
14 | repo-source-non-oss             | openSUSE-Leap-15.0-Source-Non-Oss        | No      | ----      | ----    |   99     | rpm-md |  http://download.opensuse.org/source/distribution/leap/15.0/repo/non-oss/  |  


# /sbin/lspci -nnk | grep -EiA3 'vga|3d|display'
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device [1043:84f5]
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia



cat /var/log/Xorg.0.log : https://pastebin.com/JZanRNvG

There is also an old kernel on the system, but the right one is booted as is shown by:


# uname -a
Linux xxx 4.12.14-lp150.12.4-default #1 SMP Tue May 22 05:17:22 UTC 2018 (66b2eda) x86_64 x86_64 x86_64 GNU/Linux

7399.280] (==) Using config file: “/etc/X11/xorg.conf”

Thats often an Problem, maybe rename it to xxxx.bak and restart.

Also post:

cat /proc/cmdline

because:

7399.279] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.12.14-lp150.12.4-default root=UUID=4bde1423-24fb-4e62-8c62-b83e1f8ecc62 nomodeset resume=/dev/disk/by-label/swap splash=silent quiet showopts resume=/dev/disk/by-label/swap splash=silent quiet showopts resume=/dev/disk/by-label/swap splash=silent quiet showopts resume=/dev/disk/by-label/swap splash=silent quiet showopts resume=/dev/disk/by-label/swap splash=silent quiet showopts resume=/dev/disk/by-label/swap splash=silent quiet showopts

OK, renamed xorg.conf. Makes no difference…

now the contents of /proc/cmdline is:


# cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.12.14-lp150.12.4-default root=UUID=4bde1423-24fb-4e62-8c62-b83e1f8ecc62 resume=/dev/disk/by-label/swap splash=silent quiet showopts resume=/dev/disk/by-label/swap splash=silent quiet showopts resume=/dev/disk/by-label/swap splash=silent quiet showopts resume=/dev/disk/by-label/swap splash=silent quiet showopts resume=/dev/disk/by-label/swap splash=silent quiet showopts resume=/dev/disk/by-label/swap splash=silent quiet showopts

Don’t know where the duplication of the parameters comes from. Does it harm?

In previous log there was ‘nomodeset’ present. Added this once in grub as a test. It isn’t there anymore and I cannot see that it makes any dfference.