On 2017-07-19 22:41, Marc Chamberlin wrote:
On 07/18/2017 06:26 PM, Felix Miata wrote:
Marc Chamberlin composed on 2017-07-18 16:30 (UTC-0700):
Edit /etc/sysconfig/displaymanager and /etc/sysconfig/windowmanager directly. They are supposedly self-documenting, although the displaymanager I'm looking at ATM on TW, with kdm-4.11.22, for DISPLAYMANAGER= lists neither lightdm nor sddm as options; mine has "kdm" set. For Plasma 5 to be default set "kde-plasma" as DEFAULT_WM= in windowmanager.
Hi Felix, OK, I followed your instructions and set my DISPLAYMANAGER to kdm, and DEFAULT_WM to kde-plasma. Upon reboot, I now do get a login screen but when I enter my name and password I again get the popup dialog saying " Could not start kdeinit5. Check your installation. ". I cannot get any further than this, if I click on OK it just represents me with the login screen and this cycle repeats. CTRL-ALT-F3 gets me to the command line screen....
You should try to start a non kde desktop. Like icewm.
A brief start would be journalctl | grep fail OK, here is what returned, I cut out some obvious stuff that was not applicable, such as messages about Fail2Ban, vsftpd authentication failures, smartd Prefailure attributes etc.....
bigbang:/boot # journalctl | grep "Jul 19" | grep fail
There is a better command than grep for the current boot session. Simply use "journalctl -b | grep -i fail". As it is, I don't know if the failures to mount /home are during start or during halt today:
Jul 19 12:29:25 bigbang dbus[1127]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Refusing activation, D-Bus is shutting down. Jul 19 12:29:38 bigbang systemd[1]: slash-websites.mount: Unit entered failed state. Jul 19 12:29:38 bigbang systemd[1]: mail.mount: Unit entered failed state. Jul 19 12:29:38 bigbang systemd[1]: SuSE42.1.mount: Unit entered failed state. Jul 19 12:29:38 bigbang systemd[1]: var-run-user-1000.mount: Unit entered failed state. Jul 19 12:29:38 bigbang systemd[1]: slash-srv.mount: Unit entered failed state. Jul 19 12:29:38 bigbang systemd[1]: home.mount: Unit entered failed state. Jul 19 12:29:38 bigbang systemd[1]: slash-data.mount: Unit entered failed state. Jul 19 12:29:38 bigbang systemd[1]: SuSE12.3.mount: Unit entered failed state. Jul 19 12:29:38 bigbang systemd[1]: slash-boot-efi.mount: Unit entered failed state. Jul 19 12:29:38 bigbang systemd[1]: slash-data1.mount: Unit entered failed state. Jul 19 12:29:38 bigbang systemd[1]: slash-var-run-user-1000.mount: Unit entered failed state. Jul 19 12:29:38 bigbang systemd[1]: slash-tmp.mount: Unit entered failed state. Jul 19 12:29:56 bigbang kernel: Ignoring BGRT: failed to map image memory Jul 19 12:29:56 bigbang kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM Jul 19 12:29:56 bigbang kernel: [drm] failed to retrieve link info, disabling eDP Jul 19 12:30:12 bigbang systemd[1]: Dependency failed for Network Manager Wait Online. Jul 19 12:30:12 bigbang systemd[1]: NetworkManager-wait-online.service: Job NetworkManager-wait-online.service/start failed with result 'dependency'.
Did the just completed reinstallation and/or updates rebuild both/all initrds? And you just went above my pay grade, I dunno how to answer this..... Are the timestamps on /boot/initrd* all fresh? If there is one that is not, can you boot from its kernel and not have the black screen problem? Here is what I see in /boot
bigbang:/boot # ls -al total 54112 drwxr-xr-x 4 root root 4096 Jul 18 12:29 . drwxr-xr-x 38 root root 4096 Jul 6 16:38 .. -rw-r--r-- 1 root root 1725 Oct 7 2016 boot.readme -rw-r--r-- 1 root root 178511 Jun 24 06:32 config-4.4.73-18.17-default -rw-r--r-- 1 root root 178538 Jul 1 00:46 config-4.4.74-18.20-default drwxrwxr-x 3 root root 16384 Dec 31 1969 efi drwxr-xr-x 7 root root 4096 Jul 18 12:27 grub2 lrwxrwxrwx 1 root root 27 Jul 18 12:26 initrd -> initrd-4.4.74-18.20-default -rw------- 1 root root 9923568 Jul 14 21:15 initrd-4.4.73-18.17-default -rw------- 1 root root 9865028 Jul 18 12:27 initrd-4.4.74-18.20-default
initrd-4.4.73 was not regenerated. But this seems to be normal, looking at mine.
What about 'WINDOWMANAGER=/usr/bin/icewm startx -- :1'?
WINDOWMANAGER ??? Are you asking me to set DEFAULT_WM to this value, or something else? I will await your reply before I do anything.
No, just type that line and press enter, in the console, as root. The variable is set for this command only, not saved to file, and not even for later commands. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)