Not dual booting, but still it asked for a password so I assume it was my root password - but I still got the error. Is this a bug in Plasma then? Or, since it is /testing , and elogind might have something to do with it, since technically consolkit2 is in play?

I believe that the latest Plasma5 will not work well with ConsoleKit2.

And regarding with ConsoleKit2 vs. elogind, even it is supposed to be started only one by init scripts, both elogind and ConsoleKit daemons could be called in demand via DBUS, as some friends of mine claims from their experiences.

Then having both in the system is probably a recipe for disaster.

Anyway, I for one I uninstalled ConsoleKit2 since years ago, and I switched to elogind. For various reasons - which made me to use it even on systems with KDE4. And I see(n) no issues like the ones described by you.

So, my recommendation to nuke from orbit this derelict which nobody else uses today.

I meant that doing `ntpdate pool.ntp.org` from a terminal should set your system time correctly, and Plasma should follow that.

Regardless, I think something must be borked with authenticating to superuser through Plasma, since the "Set date and time automatically" option does not work for me either.

I don't have ConsoleKit2 installed either, but the "Set date and time automatically" option fails for me too (not that I need it, but still).

So it sounds that it is a Plasma bug.

Strange, mine's works fine.

Full install with all its bells (excluding KDE and KDEI) with full removal of my own last build of Plasma5 5.20 and its friends, then installed the VTown.

Works also fine with an unprivileged user, fresh created with no previous files in its home.

Hello,

I also have the black screen with sddm, and reinstalling vtown does not solve the issue (starting plasma with init 3 works well). Maybe ssdm is trying to use wayland by default? In ~/.local/share/sddm/ directory only found the wayland log, not an X server log, and I do not found the way to force sddm to use Xorg. In the latest release of alienBOB's ktown, it works well for me.

I use an nvidia graphics card, and afaik they do not support wayland. Anyone have the same problem? Besides that, the vtown packages works great!

Thanks.

I doubt it's a bug in Plasma, more likely something to do with packaging/Slackware config. I think I remember seeing this issue back on ktown, but I ignored it since I could set the time correctly through the terminal anyway.

Or maybe a Plasma5 packaging issue?

Hmm, I have no idea then!

In the past, when I suspected a user permissions issue on Plasma5, I've always triple checked the triad: elogind, dbus and polkit.

Could be too, but I don't know Alien Bob would have to confirm with Pat on that one if it is the case.

I installed it on my laptop, and everything seems to be working fine.

Is it just me, or does Okular in vtown sort of scroll weirdly jumpy through PDFs? Also, the back feature (shift-alt-left by default) seems to be busted (i.e., doesn't go back to the correct place in the document after clicking on a link). I tried clearing Okular's settings but no difference.

I tried it on a couple of multi-page pdf's and it was smooth and had never tried the alt-shift-left before but that works as well.

first time plasma user coming from vanilla 14.2 onto a clean-wiped / partition - previously backed-up.
the iso i burned from the main slackware64-current tree was slightly over 3.8Go and the full install 12Go then 14Go with vtown.

basically following the post #22 worked : I made some mistakes as some vtown packages didn't get upgraded (attica, libdbusmenu-qt, etc ...), used installpkg, maybe not the right choice ?

the login window, kde and xfce are quite pretty, time is right, weather is right, dolphin is right, okular works on 50Mo pdfs.

now i have to learn how to get back to fluxbox.

thanks,