Marc Chamberlin composed on 2017-07-18 16:30 (UTC-0700):
Felix Miata wrote: ... AFAIK from my Googling, plasma5 is part of the sddm display manager and SDDM seems to be the setting recommended on All my Plasma 5 installations have either KDM or KDM3, neither lightdm nor sddm anywhere. For the 42.3 I did for my neighbor done Saturday night it's KDM3.
most of the websites I visited, to use as the display manager. There isn't any settings under either the DISPLAYMANGER or DEFAULT_WM that allow me to select "plasma5". Ditto for "kde5", under DEFAULT_WM I can only select either KDE or KDE4 if I want to use a KDE window manager. I tried both, and on a lark I also typed in KDE5 for the setting, but no joy on any of these... Please advise me on exactly what I should set> these two parameters to and/or if I am misunderstanding these settings. 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
On 07/18/2017 06:26 PM, Felix Miata wrote: 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....
...bigbang:/home/marc # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.4.74-18.20-default root=UUID=ebf32d3d-bbdd-4d70-99e5-c15735bcd81d ro resume=/dev/disk/by-uuid/befcf2d3-8c2c-484b-a196-55be5744a24f splash=silent quiet showopts Hmmm, then your problem probably nothing to do with modesetting.
You could try the other Xorg driver, but I do think '(EE) /dev/dri/card0' would apply to either. Xorg.0.log tells you which driver is in use, the large multiplicity of lines with INTEL(0) say intel driver, while MODESET(0) say integral modesetting driver in use. As long as mesa and kernel modesetting are not broken, Xorg will use intel if xf86-video-intel is installed, the integral driver if it is not.
Probably we need to see more of Xorg.0.log....
An interesting change has happened, I am no longer seeing the EE error messages in the Xorg.0.log file after making the changes to the DISPLAYMANAGER and DEFAULT_WM
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 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'. Jul 19 12:30:18 bigbang bash[1172]: channel: no 'mirrors.updates.spamassassin.org' record found, channel failed Jul 19 12:30:47 bigbang server[1855]: log4j:ERROR setFile(null,true) call failed. Jul 19 12:30:47 bigbang server[1855]: 19-Jul-2017 12:30:47.878 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more Filters failed to start. Full details will be found in the appropriate container log file Jul 19 12:30:47 bigbang server[1855]: 19-Jul-2017 12:30:47.878 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/JSPWiki] startup failed due to previous errors
and
dmesg ! grep fail
bigbang:/boot # dmesg | grep fail [ 0.040310] Ignoring BGRT: failed to map image memory [ 0.252121] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM [ 1.527930] [drm] failed to retrieve link info, disabling eDP
For voluminous things like Xorg.0.log, journal or full dmesg, share via pastebin, either install (if it isn't already) and use the susepaste command, or use http://susepaste.org/ or http://pastebin.com/ or one of the many others, or the web space provided by your ISP. I posted my Xorg.0.log file at http://susepaste.org/38204685 Enjoy! ;-)
Is the problem the same booting the previous (4.4.73) kernel? Yeah, I tried booting with the previous kernel to see if the desktop would come up, and it didn't... So something that is common to both is now broken... :-( Is there also an older kernel than 4.4.73?
No, it appears that I only have 2 kernels...
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 -rw-r--r-- 1 root root 500736 Dec 30 2016 message -rw-r--r-- 1 root root 1007254 Jun 24 07:28 symtypes-4.4.73-18.17-default.gz -rw-r--r-- 1 root root 1007576 Jul 1 01:18 symtypes-4.4.74-18.20-default.gz -rw-r--r-- 1 root root 356735 Jun 24 07:19 symvers-4.4.73-18.17-default.gz -rw-r--r-- 1 root root 356845 Jul 1 01:17 symvers-4.4.74-18.20-default.gz -rw-r--r-- 1 root root 377 Jun 24 07:19 sysctl.conf-4.4.73-18.17-default -rw-r--r-- 1 root root 377 Jul 1 01:17 sysctl.conf-4.4.74-18.20-default -rw-r--r-- 1 root root 3194167 Jun 24 07:07 System.map-4.4.73-18.17-default -rw-r--r-- 1 root root 3194251 Jul 1 01:13 System.map-4.4.74-18.20-default -rw-r--r-- 1 root root 6889858 Jun 24 07:29 vmlinux-4.4.73-18.17-default.gz -rw-r--r-- 1 root root 6888845 Jul 1 01:18 vmlinux-4.4.74-18.20-default.gz lrwxrwxrwx 1 root root 28 Jul 18 12:26 vmlinuz -> vmlinuz-4.4.74-18.20-default -rw-r--r-- 1 root root 5895880 Jun 24 08:14 vmlinuz-4.4.73-18.17-default -rw-r--r-- 1 root root 65 Jun 24 08:14 .vmlinuz-4.4.73-18.17-default.hmac -rw-r--r-- 1 root root 5895368 Jul 1 01:45 vmlinuz-4.4.74-18.20-default -rw-r--r-- 1 root root 65 Jul 1 01:45 .vmlinuz-4.4.74-18.20-default.hmac
What if anything does /var/lib/systemd/coredump/ contain? Is everything that is there timestamped since you did your updating?
bigbang:/boot # ls -al /var/lib/systemd/coredump/ total 2000 drwxr-xr-x 2 root root 16384 Jul 19 12:31 . drwxr-xr-x 8 root root 4096 Jul 4 09:16 .. -rw-r-----+ 1 root root 122736 Jul 19 12:31 core.kdeinit5.1000.f90aa36c75fa45f5b6925fe316117ee6.3360.1500492668000000.xz -rw-r-----+ 1 root root 269164 Jul 19 12:31 core.ksplashqml.1000.f90aa36c75fa45f5b6925fe316117ee6.3335.1500492668000000.xz -rw-r----- 1 root root 212664 Jul 18 13:43 core.sddm.0.6af6c36197af451f8c71854a8bafbc87.2949.1500410580000000.xz -rw-r----- 1 root root 169720 Jul 18 12:29 core.sddm-greeter.483.087a9332de504ef5a1140dfddca8c23b.3104.1500406176000000.xz -rw-r----- 1 root root 169560 Jul 18 14:29 core.sddm-greeter.483.516ece7fa9ad447b9ca78f10d8e98b69.3076.1500413381000000.xz -rw-r----- 1 root root 169440 Jul 18 15:42 core.sddm-greeter.483.61f03715e74749a5b47df3745f0b2157.3105.1500417723000000.xz -rw-r----- 1 root root 169728 Jul 18 13:18 core.sddm-greeter.483.6ac4b14ea0a8405e9c9c1ad0d686d345.3087.1500409127000000.xz -rw-r----- 1 root root 169548 Jul 18 13:34 core.sddm-greeter.483.6af6c36197af451f8c71854a8bafbc87.3034.1500410077000000.xz -rw-r----- 1 root root 169708 Jul 18 13:27 core.sddm-greeter.483.b9bb167aa2de4f58a10f149a1fa7c407.3058.1500409652000000.xz -rw-r----- 1 root root 169736 Jul 18 15:48 core.sddm-greeter.483.ba982bdf727a421c8a63d03b3f4c0537.3045.1500418122000000.xz -rw-r----- 1 root root 169264 Jul 18 11:33 core.sddm-greeter.483.c490cd1e96c84ea5b0cb762c7e01902c.3047.1500402826000000.xz
Does 'startx -- :1' from vtty login, either normally or as root, avoid the black screen? (I'm guessing not.)
No, it simply gave me the popup dialog error message about startx and then I lost the ability to show my key strokes... Just get output but no echo of keystrokes... But I did manage to capture the output from this startx command and saved it to a file. bigbang:/home/marc # cat startx.log xauth: file /home/marc/.serverauth.17979 does not exist X.Org X Server 1.18.3 Release Date: 2016-04-04 X Protocol Version 11, Revision 0 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux bigbang 4.4.74-18.20-default #1 SMP Fri Jun 30 19:01:19 UTC 2017 (b5079b8) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.74-18.20-default root=UUID=ebf32d3d-bbdd-4d70-99e5-c15735bcd81d ro re sume=/dev/disk/by-uuid/befcf2d3-8c2c-484b-a196-55be5744a24f splash=silent quiet showopts Build Date: 14 July 2017 05:36:29PM Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/home/marc/.local/share/xorg/Xorg.1.log", Time: Wed Jul 19 13:28:32 2017 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) Fatal server error: (EE) xf86OpenConsole: Switching VT failed (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/home/marc/.local/share/xorg/Xorg.1.log" for additional information. (EE) VGA Arbitration: Cannot restore default device. (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Cannot assign requested address xinit: server error ------------------------------------------------------------------------------------------- xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason? If so either use a display manager (strongly recommended) or adjust /etc/permissions.local and run "chkstat --system -- set" afterwards
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. Again, thanks for helping me, I know this is a LOT of info to grok! Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org