Bug 1008680

You set this to critical - please elaborate what you think doesn't work as expected.

(In reply to Egbert Eich from comment #1)

I would appreciate if a login dialogue will be shown by at least one display manager (including “XDM 1.1.11-195.2”) also on my updated openSUSE Tumbleweed system.

I believe autologin is our default since ages, but if you manage to logout from your session (not sure whether all our desktops support this), you should see a login dialogue. Ok?

(In reply to Stefan Dirsch from comment #3)

I guess that I do not use the functionality “autologin” on my openSUSE system so far.

I can start to the run level “3” from my GRUB boot menu and activate the setting “DISPLAYMANAGER=xdm” by the configuration editor of the tool “YaST” in a text terminal.
How long will it usually take until the desired graphical login dialogue will be displayed on your current test systems after a command like  “init 5” was submitted?

This looks more like a driver issue then. Xserver should start immediately when running "init 5". Please attach your /var/log/Xorg.0.log.

(In reply to Stefan Dirsch from comment #5)
> Xserver should start immediately when running "init 5".

I observed also acceptable response times there in other software situations.



> Please attach your /var/log/Xorg.0.log.

Unfortunately, this file was not generated during my recent tries to reactivate the desired login dialogue so far.
Is it the “greeter” which does not appear on a virtual terminal as I was used too such a display?


Excerpt from my journal:
…
Nov 05 21:33:16.296701 Sonne systemd[1]: Started X Display Manager.
Nov 05 21:33:16.295595 Sonne display-manager[4653]: Starting service xdm..done
…
Nov 05 21:33:16.268104 Sonne root[4695]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
Nov 05 21:33:16.268067 Sonne root[4695]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
…
Nov 05 21:33:16.182560 Sonne systemd[1]: Received SIGRTMIN+21 from PID 4656 (plymouthd).
…
Nov 05 21:33:16.093739 Sonne display-manager[4653]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
Nov 05 21:33:16.080639 Sonne display-manager[4653]: Command: localectl set-keymap de-latin1-nodeadkeys
Nov 05 21:33:16.080542 Sonne display-manager[4653]: KEYMAP: de-latin1-nodeadkeys
Nov 05 21:33:16.080309 Sonne display-manager[4653]: /etc/vconsole.conf available
…
Nov 05 21:33:16.059341 Sonne systemd[1]: Started Show Plymouth Boot Screen.
…
Nov 05 21:33:16.047616 Sonne systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
…
Nov 05 21:33:16.022803 Sonne systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Nov 05 21:33:16.021681 Sonne systemd[1]: Starting X Display Manager...
Nov 05 21:33:16.019998 Sonne systemd[1]: Starting Activation of LVM2 logical volumes...
…



I expect that software components which are provided by the script “NVIDIA-Linux-x86_64-367.57.run” will work together with the other stuff as usual.

Well, if there is no /var/log/Xorg.0.log you're not using xdm, but a different display manager. Since you apparently have installed the NVIDIA driver I suggest to uninstall it again via

  nvidia-installer --uninstall

and try again (reboot). This may already fix the issue.

Running 

  X --verbose 7 --logverbose 7 -retro :9

on the Linux console should also create /var/log/Xorg.0.log.

(In reply to Stefan Dirsch from comment #7)
> Well, if there is no /var/log/Xorg.0.log you're not using xdm,

I hoped that the setting “DISPLAYMANAGER=xdm” was active for the desired login.


> but a different display manager.

I wonder still why it did not work for a few days.


>   nvidia-installer --uninstall
> 
> and try again (reboot).

I applied further software updates around “Mesa 13.0.0-599.2” and “xorg-x11-server 7.6_1.18.4-465.52” a moment ago after the mentioned command succeeded.
The reinstallation by the script “NVIDIA-Linux-x86_64-367.57.run” succeeded  also. The XDM “greeter” worked then as we usually expect it. The protocol file “/var/log/Xorg.0.log” is present again.

I would prefer to reactivate an other desktop environment than the current running session “KDE 5.27”.

This is due to NVIDIA's installer replacing half of the system's graphics driver stack. So with any system update you may run into this issue again. For our openSUSE Leap and SUSE LINUX enterprise products we're providing NVIDIA RPMs, which don't suffer from this issue. Unfortunately we currently cannot provide this service for Tumbleweed, since it relies on a stable Kernel ABI, which we cannot provide for Tumbleweed unfortunately.

(In reply to Stefan Dirsch from comment #9)
> Unfortunately we currently cannot provide this service for Tumbleweed,

This information seems to be reasonable to some degree.


> since it relies on a stable Kernel ABI,

How much did this aspect matter in my concrete software situation?


> which we cannot provide for Tumbleweed unfortunately.

This fact might be fine for the general use case.

I stumbled on a combination of software versions where something around the well-known tool “XDM 1.1.11-195.2” did not work as expected for a while.
Is anybody keen to find more out about related hiccups?