slackware-current KDE5 startx failed
by zdolar from LinuxQuestions.org on (#4SVBG)
Hi!
Slackware64-current form 10.10.2019. Clean install, KDE4 works.
I downloaded Ktown Erics KDE-5.19.10 packages to replace KDE4.
README:
1. slackpkg remove kde
2. upgradepkg --reinstall --install-new x86_64/deps/*.t?z
3. upgradepkg --reinstall --install-new x86_64/kde/*/*.t?z
4. find /etc/ -name "*.new" - there is none.
5. reboot
All above finished without errors & warnings.
After a reboot startx after a brief display blink, returns to text mode.
This is full output of startx:
Quote:
How to resolve this?
Slackware64-current form 10.10.2019. Clean install, KDE4 works.
I downloaded Ktown Erics KDE-5.19.10 packages to replace KDE4.
README:
1. slackpkg remove kde
2. upgradepkg --reinstall --install-new x86_64/deps/*.t?z
3. upgradepkg --reinstall --install-new x86_64/kde/*/*.t?z
4. find /etc/ -name "*.new" - there is none.
5. reboot
All above finished without errors & warnings.
After a reboot startx after a brief display blink, returns to text mode.
This is full output of startx:
Quote:
| root@ProBook:~# startx xauth: file /root/.serverauth.1523 does not exist X.Org X Server 1.20.5 X Protocol Version 11, Revision 0 Build Operating System: Slackware 15.0 Slackware Linux Project Kernel command line: BOOT_IMAGE=kernel-5.3.7 ro root=803 Build Date: 26 June 2019 02:19:39PM Current version of pixman: 0.38.4 (==) Using default built-in configuration (39 lines) The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Unsupported high keycode 372 for name <I372> ignored > X11 cannot support keycodes above 255. > This warning only shows for the first high keycode. > Internal error: Could not resolve keysym XF86MonBrightnessCycle > Internal error: Could not resolve keysym XF86RotationLockToggle Errors from xkbcomp are not fatal to the X server xinit: connection to X server lost waiting for X server to shut down (II) Server terminated successfully (0). Closing log file. |