SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So far so good. No problems as yet. Have been running Plasma5 on current since Eric started supplying it a LONG time ago. Thank you Eric for all of your work. Merci PV, one major checkbox ticked.
...
I get a blank screen with a cursor at runlevel 4 (runlevel 3 with startx is all good though). Anyone know what might cause this issue?
I have the same issue. Removed ktown and installed vtown. Runlevel 4 has a blank screen with cursor. Runlevel 3 with startx works. Since I logged in at the CLI there is no Plasma login screen. That's were it hangs up on runlevel 4.
So far I have not seen any complaints as I did a partial install of Plasma (yes of course I excluded both Akonadi and KDEPim). The only weird thing, is that even though I know I chose CST during a fresh install of --Current - the time and timezone for KDE was not correct initially, so that was weird - but overall I like this and I am seriously looking at coming back to KDE since the 3.5 days is the last time I ever used KDE.
I have the same issue. Removed ktown and installed vtown. Runlevel 4 has a blank screen with cursor. Runlevel 3 with startx works. Since I logged in at the CLI there is no Plasma login screen. That's were it hangs up on runlevel 4.
Apparently, our BDFL is not habituated yet with the PAM tentacles...
So, seems that he does not shipped the PAM files on his own build of SDDM, with the consequence that the SDDM is DOA.
The fix is rather simple: to grab the files /etc/pam.d/sddm* from KTown's SDDM and to put them in the right place, then just reboot.
Last edited by LuckyCyborg; 11-04-2020 at 01:25 AM.
Apparently, our BDFL is not habituated yet with the PAM tentacles...
So, seems that he does not shipped the PAM files on his own build of SDDM, with the consequence that the SDDM is DOA.
The fix is rather simple: to grab the files /etc/pam.d/sddm* from KTown's SDDM and to put them in the right place, then just reboot.
The sddm package needs to be rebuilt after fixing "testing/source/vtown/kde/post-install/sddm.post-install", replacing the overlooked "sddm-qt5" string with "sddm". I notified Pat.
I have rebuilt the sddm package after replacing 'sddm-qt5' with 'sddm' in sddm.post-install. The sddm files are now present in /etc/pam.d.
Anyway after rebooting in runlevel 3 with 'startx', I still get a blank screen with a cursor.
Now it works. The "/etc/X11/xinit/xinitrc.plasma" was missing. What destroyed it in the upgrade from ktown to vtown ?
It is present in "/var/log/packages/plasma-workspace-5.19.4-x86_64-1alien" but not in "/var/log/packages/plasma-workspace-5.20.2-x86_64-1_vtown_1"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
