Plasma wayland on current

LuckyCyborg · 06-16-2020, 03:49 PM

Quote:

Originally Posted by Alien Bob

Pity you did not supply diffs here, but I hope I can work out your modifications.

My bad! Next time I will try to present diffs.

Quote:

Originally Posted by Alien Bob

I observed similar behaviour in a QEMU virtual machine but I can not recall whether that was in runlevel 3.What I did experience using the QEMU "vmware" graphics, was that elogind thought that my console did not have graphical capabilities and as a result it refused to start a graphical session through "startx". But when I switched the QEMU graphics to "virtio" everything worked as expected and the virtual console switched to the graphical console as it should.

Hmmm...

It is not something regarding the graphics capabilities, in my opinion. Wayland/Plasma5 looks quite satisfied by my Radeon HD4250 (from the box where I play with it) also it feels considerable faster/snapier than the same X11/Plasma5 and it does considerable lower pressure in the 3D computing power - which I sincerely love it.

It is like more like an involuntary console switch. After you are jumped in the original text console, meanwhile the desktop loading goes in background, and if you wait enough, CTRL+ALT+F7 will jump you in a full loaded desktop.

Quote:

Originally Posted by Alien Bob

Also this I think I solved, but I can not recall what command to use. As I noted before, I am not 100% OK health-wise and this expresses itself in memory loss.

Let's hope you will remember how you did it.

And take care of your health, man! It's the most important thing...

Alien Bob · 06-16-2020, 03:52 PM

Quote:

Originally Posted by LuckyCyborg

Well, looks like there are some issues in the build system from "elogind" branch.

Long story short, apparently the powerdevil package has some config issues. I managed to build powerdevil packages which works perfectly for both elogind and ConsoleKit2 ways, with the following modifications.

Yeah like I expected... quick hacks, insufficient testing.
Good that I checked all this into git and you found it and ran away with it. I took your modifications - all of these were good and were needed of course - and will check those into git. Thanks!

LuckyCyborg · 06-16-2020, 03:58 PM

Quote:

Originally Posted by Alien Bob

Yeah like I expected... quick hacks, insufficient testing.
Good that I checked all this into git and you found it and ran away with it. I took your modifications - all of these were good and were needed of course - and will check those into git. Thanks!

I am glad to be of help!

However, I am aware that the much more experienced users than me would be of much greater help...
--------------------------------

BTW, you are kind to rename the polkit rules of powerdevil like you did in the associated post-install script?

I talk about the new "poweroff" -> "power" changes you did, where are expected the files:

Code:

post-install/powerdevil/10-enable-ck2-power.rules
post-install/powerdevil/10-enable-elogind-power.rules

Lenard Spencer · 06-16-2020, 08:50 PM

Just a couple of notes for everyone:
Plasma 5.19.1 hit the KDE server today, and yes it still has the same shutdown/reboot issue, but the powerdevil fixes posted here take care of that nicely. (Thank you Eric and LuckyCyborg!)

I did a COMPLETE build and install today on a clean 64-current partition, and on the target box (AMD FX-8350 4GHz with 32G DDR3-1866 RAM) the entire process (including all the deps) took a little over 7 hours. In deps/alldeps.SlackBuild you have to add exiv2 to the list or applications-extra/digikam will not build.

gmgf · 06-16-2020, 10:38 PM

Ok, thanks (LuckyCyborg)

More, i have also rebuild 'xorg-server' with 'elogind', just it need to remove this line '--disable-systemd-logind' in the /configure/xorg-server,
after, 'xorg-server' it's linked on the 'libelogind' and not work, if 'elogind' is uninstalled.
(For the moment I did not find the interest of this but maybe it is worth watching .....)

LuckyCyborg · 06-17-2020, 07:06 AM

Thanks, gentlemen! I'd just playing with this Wayland/Plasma5...

Mr. Hameleers, I may have another suggestion? Looks like there is missing the $ on the SLKELOGIND variable name:

https://git.slackware.nl/ktown/tree/...?h=elogind#n13

Instead of

Code:

if [ "SLKELOGIND" = "no" ]; then

I think should be

Code:

if [ "$SLKELOGIND" == "no" ]; then

Unless this change is made, the powerdevil would be built always in the elogind style as polkit configuration files.

Alien Bob · 06-17-2020, 07:09 AM

Good catch. I'll fix that;

LuckyCyborg · 06-17-2020, 07:12 AM

Quote:

Originally Posted by Alien Bob

Good catch. I'll fix that;

Thanks! Please look also for the polkit files names - for powerdevil.

https://git.slackware.nl/ktown/tree/...ules?h=elogind
https://git.slackware.nl/ktown/tree/...ules?h=elogind

I believe that they are supposed now to be named: 10-enable-ck2-power.rules and 10-enable-ck2-power.rules

This, according with:

https://git.slackware.nl/ktown/tree/...?h=elogind#n17
https://git.slackware.nl/ktown/tree/...?h=elogind#n23

PS. Also is missing an "=" in the IF from previous post, which I modified already. I forgot about it, even I made already the change locally.

Alien Bob · 06-17-2020, 07:22 AM

Thanks, also fixed in git. Man, I need to hibernate to get my focus back.

LuckyCyborg · 06-17-2020, 07:26 AM

Quote:

Originally Posted by Alien Bob

Thanks, also fixed in git. Man, I need to hibernate to get my focus back.

Thanks!

Please add another little change, mentioned in the previous post. That "=" should be "==" into

Code:

if [ "$SLKELOGIND" == "no" ]; then

There: https://git.slackware.nl/ktown/tree/...?h=elogind#n13

Alien Bob · 06-17-2020, 07:54 AM

Quote:

Originally Posted by LuckyCyborg

Thanks!

Please add another little change, mentioned in the previous post. That "=" should be "==" into

Code:

if [ "$SLKELOGIND" == "no" ]; then

There: https://git.slackware.nl/ktown/tree/...?h=elogind#n13

The double equal sign '==' is a bashism. The kde.SlackBuild executes with '/bin/sh' i.e. it runs in shell compatibility mode, and then a single '=' is preferred actually.

LuckyCyborg · 06-17-2020, 09:25 AM

Quote:

Originally Posted by Alien Bob

The double equal sign '==' is a bashism. The kde.SlackBuild executes with '/bin/sh' i.e. it runs in shell compatibility mode, and then a single '=' is preferred actually.

My bad! Sorry for the noise.

Alien Bob · 06-17-2020, 02:02 PM

Quote:

Originally Posted by LuckyCyborg

And, finally another question: is there a way to launch a Wayland/Plasma5 session from a runlevel 3 console, like startx?

Trying to launch from console startplasma-wayland ends in a failure with the message:

I have it running now - the command to use in runlevel 3 is "startkwayland".

LuckyCyborg · 06-17-2020, 02:08 PM

Quote:

Originally Posted by Alien Bob

I have it running now - the command to use in runlevel 3 is "startkwayland".

Ave Eric!

Thank you very much!

EDIT: Absolutely great! Not only it works perfectly, but also the power controls works fine, just like from the X11 session.

LuckyCyborg · 06-17-2020, 02:57 PM

Quote:

Originally Posted by LuckyCyborg

Not only it works perfectly, but also the power controls works fine, just like from the X11 session.

And there we go again...

So, the Wayland/Plasma5 launched from a runlevel 3 console works like a charm, using this "startkwayland" command. Of course, while using the elogind as session manager. Same does X11/Plasma when launched from SDDM.

However, even the X11/Plasma 5.19.1 presents that "involuntary console jump" at start, when it is launched from a runlevel 3 console with "startx" while using elogind.

BUT, the same (elogind powered) system runs fine the XFCE from console and this make me to doubt that is something regarding the X server.

A bit disappointing, as I hoped to be some obscure bug of Plasma, likely to be fixed in the next minor release...

Then, back at the drawing table!