LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-17-2020, 04:02 PM   #31
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,063

Rep: Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825

Quote:
Originally Posted by LuckyCyborg View Post
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!
I fixed this as well. Turns out that Pat patches the startx script in the xinit package because that assumes everyone uses systemd.
With a small fix to /usr/bin/startx you will have proper X11 sessions in runlevel 3. In /usr/bin/startx look for:

Code:
if [ -x /usr/lib/systemd/systemd -o -x /lib/systemd/systemd ]; then
And change it to:

Code:
if [ -x /lib/elogind/elogind -o -x /lib64/elogind/elogind ]; then
I have already shared all my patches for the day with Pat, and he'll process them before my new batch of Plasma5 packages is uploaded. Note that the next 'ktown' update will force elogind upon you.

Everything works now, in this VM. Tomorrow I will try actual hardware with a Nvidia card and using the proprietary driver. The 64bit package set is complete.
 
4 members found this post helpful.
Old 06-17-2020, 11:34 PM   #32
LuckyCyborg
Member
 
Registered: Mar 2010
Posts: 650

Rep: Reputation: 419Reputation: 419Reputation: 419Reputation: 419Reputation: 419
Quote:
Originally Posted by Alien Bob View Post
I fixed this as well. Turns out that Pat patches the startx script in the xinit package because that assumes everyone uses systemd.
With a small fix to /usr/bin/startx you will have proper X11 sessions in runlevel 3. In /usr/bin/startx look for:

Code:
if [ -x /usr/lib/systemd/systemd -o -x /lib/systemd/systemd ]; then
And change it to:

Code:
if [ -x /lib/elogind/elogind -o -x /lib64/elogind/elogind ]; then
Brilliant! I've tested this modification and that "involuntary console jump" has been gone away.

Thanks, Mr. Hameleers!

Quote:
Originally Posted by Alien Bob View Post
I have already shared all my patches for the day with Pat, and he'll process them before my new batch of Plasma5 packages is uploaded.
That's real good news because I think will improve the Plasma5 integration within Slackware.

Quote:
Originally Posted by Alien Bob View Post
Note that the next 'ktown' update will force elogind upon you.
Makes sense. After all, my own experiments told me that the Plasma5 experience will be seriously impaired without having elogind up and running.

And certainly the Wayland/Plasma5 absolutely needs this elogind service.

Quote:
Originally Posted by Alien Bob View Post
Everything works now, in this VM. Tomorrow I will try actual hardware with a Nvidia card and using the proprietary driver. The 64bit package set is complete.
Thanks for your efforts!

I can't wait to see "the real thing" at work after my own experiments where the Plasma5 packages aren't built probably in the best way, because I made them with "dirty" systems, where may or may not are installed unexpected software.

Last edited by LuckyCyborg; 06-18-2020 at 05:09 PM.
 
Old 06-18-2020, 01:56 AM   #33
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,795

Original Poster
Rep: Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709
Another little thing, it's update upower to 'upower-99.11' only 'solid' and 'kio' depend on it, (Robby Workman) have this packaged version of upower, in his xfce4-4.14.0 packages.

Last edited by gmgf; 06-18-2020 at 01:58 AM.
 
1 members found this post helpful.
Old 06-18-2020, 02:15 AM   #34
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,063

Rep: Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825
Quote:
Originally Posted by gmgf View Post
Another little thing, it's update upower to 'upower-99.11' only 'solid' and 'kio' depend on it, (Robby Workman) have this packaged version of upower, in his xfce4-4.14.0 packages.
Yes I can easily support the new upower in Plasma5 but then it would break even more stuff than is going to stop working if you remove ConsoleKit2 and replace that with elogind.
So still the idea is that the new XFCE, KDE and upower all land in -current together.
 
3 members found this post helpful.
Old 06-18-2020, 02:33 AM   #35
LuckyCyborg
Member
 
Registered: Mar 2010
Posts: 650

Rep: Reputation: 419Reputation: 419Reputation: 419Reputation: 419Reputation: 419
Quote:
Originally Posted by Alien Bob View Post
Yes I can easily support the new upower in Plasma5 but then it would break even more stuff than is going to stop working if you remove ConsoleKit2 and replace that with elogind.
So still the idea is that the new XFCE, KDE and upower all land in -current together.
Yes, let's do not break the -current's XFCE!

I would like to note that the stock XFCE from -current has no visible issues with your elogind package, and its power controls works fine, as I tested myself both from SDDM and runlevel 3 console.

Last edited by LuckyCyborg; 06-18-2020 at 02:46 AM.
 
Old 06-18-2020, 02:58 AM   #36
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,795

Original Poster
Rep: Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709
Quote:
Originally Posted by Alien Bob View Post
Yes I can easily support the new upower in Plasma5 but then it would break even more stuff than is going to stop working if you remove ConsoleKit2 and replace that with elogind.
So still the idea is that the new XFCE, KDE and upower all land in -current together.
Good news, these 'xfce4' (Robby) packages work fine also here
 
1 members found this post helpful.
Old 06-18-2020, 06:50 AM   #37
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,795

Original Poster
Rep: Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709
On pure 'elogind' plasma session, (without consolekit installed), 'kscreenlocker' need rebuild without 'consolekit' , this remove /usr/bin/ck-unlock-session, without this, 'kscreenlocker' crash.

Last edited by gmgf; 06-18-2020 at 06:54 AM.
 
Old 06-18-2020, 07:19 AM   #38
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,795

Original Poster
Rep: Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709
'solid' need also one version compiled with elogind.
 
Old 06-18-2020, 07:42 AM   #39
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,506

Rep: Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749Reputation: 749
Plasma wayland on current

Following this thread with Keen interest! Keep up the great work guys.
 
Old 06-18-2020, 08:58 AM   #40
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,207

Rep: Reputation: 492Reputation: 492Reputation: 492Reputation: 492Reputation: 492
Some pretty exciting developments here. Trying not to get eggcited. LOL
 
Old 06-18-2020, 09:20 AM   #41
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,063

Rep: Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825
Typing this from a KDE Plasma5 Wayland session on my desktop. With an Nvidia card and using the Nvidia binary drivers.
It takes a bit of add-on configuration but that is well-documented: https://community.kde.org/Plasma/Wayland/Nvidia

This Wayland session has some visual glitches compared to a Wayland session on a kernel driver (QEMU's virtio_gpu is what I tried so far), notably the content of the popup windows which appear when moving the mouse along the system tray are not getting refreshed. And the desktop elements use gray backgrounds where I would expect partial transparency.
And I see that my QJackCtl application is unable to register itself as a systray application. Which is strange since VLC, which also is Qt5 based, has no problems adding itself as a systray widget.

But overall the accelerated graphics work well and the desktop is fluid and responsive. A page like https://paveldogreat.github.io/WebGL-Fluid-Simulation/ on the other hand has issues with graphics acceleration and therefore a low refresh rate.
 
2 members found this post helpful.
Old 06-18-2020, 05:50 PM   #42
Lenard Spencer
Member
 
Registered: Sep 2004
Location: Florida
Distribution: Slackware, Linux from Scratch
Posts: 255

Rep: Reputation: 78
Quote:
Originally Posted by Alien Bob View Post
And I see that my QJackCtl application is unable to register itself as a systray application. Which is strange since VLC, which also is Qt5 based, has no problems adding itself as a systray widget.
I haven't dug into it yet, but there is a possibility that QJackCtl may rely on libappindicator to register in the systray, and libappindicator's deps (libindicator, libdbusmenu-gtk) will no longer build on -current (glib2 deprecation errors). I may be wrong....
 
Old 06-19-2020, 06:42 AM   #43
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,063

Rep: Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825Reputation: 6825
Please read https://alien.slackbook.org/blog/rep...d-first-steps/ before attempting to upgrade to the batch of KDE Plasma5 packages I am going to release in a couple of hours.
 
2 members found this post helpful.
Old 06-19-2020, 07:15 AM   #44
Mark Pettit
Member
 
Registered: Dec 2008
Location: Cape Town, South Africa
Distribution: Slackware 14.2 64 Multi-Lib
Posts: 557

Rep: Reputation: 225Reputation: 225Reputation: 225
From Eric's subscription email :

"That did bad things to my mood, so I checked all my work-in-progress into a git branch and decided to leave it there for a while, simply because I did not have the time anymore, personal life demanded priority.
Some people noticed the new 'elogind' git branch, cloned it and continued the experiment. The resulting debugging effort resolved the dead-end I had been facing. And voila, a new package set was the result, with elogind added and thanking ConsoleKit2 for services rendered."

Man - I LOVE the power of open source. :-)

Thanks to all concerned here. We're all going to see the benefits shortly (and easily).
 
2 members found this post helpful.
Old 06-19-2020, 07:28 AM   #45
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 1,795

Original Poster
Rep: Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709
Eric the nice alien

thanks, l'ami.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Wayland: Inaccessible and restrictive by design? (Aka, Wayland won't get out of my way and I don't want it in my future.) CajunCoder Linux - General 2 09-04-2017 12:32 PM
Does gnome-flashback session use wayland? Do all gtk3 apps use wayland? rubankumars Linux - Desktop 1 08-08-2017 04:13 AM
LXer: Mutter Wayland 3.11.2 Now Syncs Keymap from X.Org to Wayland LXer Syndicated Linux News 0 12-04-2013 02:15 AM
LXer: Plasma Workspaces 2 Coming To Wayland, KDM Not Invited LXer Syndicated Linux News 0 03-15-2013 03:40 PM
Future !X ? Wayland : X - what is wayland? serafean Linux - General 5 03-04-2011 11:09 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:52 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration