KDE Plasma 5 Hits Testing!

Regnad Kcin · 11-06-2020, 08:28 AM

Quote:

Honestly, I have no pity for those who use the development tree (aka slackware-current) as a rolling release, even daring to use it on business.

It's a strange world for sure or maybe just strange folk on it.
I've been using 64-current for almost 6 years now
as my daily driver and dabbled with KDE5 for more than 5 years
and had it as my #1 DE for about 3 or 4 years.
Quite frankly I can't imagine what one's "business" might be
one does not avail himself of the power of -current and Plasma5...
There's lots of updated stuff that won't even run without them...

Maybe, maybe... if one had a server running some where with Slackware,
but really, -current is really quite stable.
I can't blame anytime that I had misfortunes on following -current.
And there is this thing called backups.
I have backups of stuff back to 1993.

"...and because of all their fears, their eyes can't hope to see
the beauty that surrounds them. Now, isnt it a ... " - Harrison

denydias · 11-06-2020, 08:55 AM

Hi there! I see people here happy with the news... I'm too. Upgraded yesterday from ktown. Everything worked fine just as expected. Thanks for the ones who spotted sddm conf and pam misses.

I bring some odd behavior since ktown age: in init 4, Plasma shutdown doesn't run /etc/rc.d/rc.6 or /etc/rc.d/rc.K, which leads to /etc/rc.d/rc.local_shutdown not being executed. When in init 3 things works as expected and rc.local_shutdown is run upon halt or reboot.

Is that a common Plasma behavior? Should I set /etc/rc.d/rc.local_shutdown to run (with sudo, of course) in logout scripts at systemsettings5? Is there something broke with Plasma in this regard?

hpfeil · 11-06-2020, 09:10 AM

As with all things Slackware, everything just works! Hip-hip-hurrah!
Kudos to Master Volkerding.

Toutatis · 11-06-2020, 09:11 AM

Just two problems on a laptop : when running 'startx' from console, a normal user cannot shutdown the system. And no battery is seen. upower gives error-messages

Quote:

-root-> upower -d

(upower:2224): libupower-glib-WARNING **: 15:58:09.590: Couldn't enumerate devices: Message recipient disconnected from message bus without replying

(upower:2224): UPower-WARNING **: 15:58:09.590: failed to enumerate: Message recipient disconnected from message bus without replying
-root-> upower -e

(upower:2231): libupower-glib-WARNING **: 15:58:23.797: Couldn't enumerate devices: Message recipient disconnected from message bus without replying

(upower:2231): UPower-WARNING **: 15:58:23.797: failed to enumerate: Message recipient disconnected from message bus without replying

-root-> /usr/libexec/upowerd

(upowerd:2241): UPower-ERROR **: 16:01:13.070: failed to get pokit authority: Error initializing authority: Erreur lors de l’appel de StartServiceByName pour org.freedesktop.PolicyKit1*: Cannot launch daemon, file not found or permissions invalid

I get also this in dmesg

Quote:

[ 44.328951] traps: upowerd[1413] trap int3 ip:7fc2d64bb7b5 sp:7ffe41982530 error:0 in libglib-2.0.so.0.6600.2[7fc2d6482000+82000]
[ 44.341496] traps: upowerd[1424] trap int3 ip:7fb1edf217b5 sp:7ffe72689e50 error:0 in libglib-2.0.so.0.6600.2[7fb1edee8000+82000]
[ 44.566796] fuse: init (API version 7.31)
[ 44.720981] kmixctrl[1374]: segfault at 0 ip 0000000000000000 sp 00007fffc75060b8 error 14 in kmixctrl[400000+2000]
[ 44.720984] Code: Bad RIP value.
[ 45.252325] traps: upowerd[1535] trap int3 ip:7ff80feee7b5 sp:7fff115a9a80 error:0 in libglib-2.0.so.0.6600.2[7ff80feb5000+82000]
[ 45.264188] traps: upowerd[1541] trap int3 ip:7ff1c95957b5 sp:7fff6db8a7d0 error:0 in libglib-2.0.so.0.6600.2[7ff1c955c000+82000]
[ 45.501154] traps: upowerd[1549] trap int3 ip:7f8067b8d7b5 sp:7fffeb05c610 error:0 in libglib-2.0.so.0.6600.2[7f8067b54000+82000]
[ 46.465077] traps: upowerd[1559] trap int3 ip:7f68094017b5 sp:7fff562e0d80 error:0 in libglib-2.0.so.0.6600.2[7f68093c8000+82000]
[ 46.476421] traps: upowerd[1565] trap int3 ip:7fdaeea157b5 sp:7fff8a7d2150 error:0 in libglib-2.0.so.0.6600.2[7fdaee9dc000+82000]
[ 46.979557] traps: upowerd[1588] trap int3 ip:7f7e220a37b5 sp:7ffd65cf7340 error:0 in libglib-2.0.so.0.6600.2[7f7e2206a000+82000]
[ 46.994285] traps: upowerd[1594] trap int3 ip:7f56f4eeb7b5 sp:7ffcacff9060 error:0 in libglib-2.0.so.0.6600.2[7f56f4eb2000+82000]
[ 56.312800] show_signal_msg: 7 callbacks suppressed
[ 56.312803] kmix[1446]: segfault at 0 ip 0000000000000000 sp 00007ffc47aaeb58 error 14 in kmix[400000+1f000]
[ 56.312810] Code: Bad RIP value.
[ 438.392220] traps: upowerd[1853] trap int3 ip:7feb06b277b5 sp:7ffe9a7b54e0 error:0 in libglib-2.0.so.0.6600.2[7feb06aee000+82000]
[ 438.406423] traps: upowerd[1865] trap int3 ip:7fd2d8c747b5 sp:7ffdaacbf950 error:0 in libglib-2.0.so.0.6600.2[7fd2d8c3b000+82000]
[ 438.940024] kmixctrl[1879]: segfault at 0 ip 0000000000000000 sp 00007ffe9bf94f08 error 14 in kmixctrl[400000+2000]
[ 438.940029] Code: Bad RIP value.
[ 439.714666] traps: upowerd[2003] trap int3 ip:7fb9390297b5 sp:7ffc1edcb0b0 error:0 in libglib-2.0.so.0.6600.2[7fb938ff0000+82000]
[ 439.726077] traps: upowerd[2009] trap int3 ip:7f1ffe5bc7b5 sp:7fff6a814550 error:0 in libglib-2.0.so.0.6600.2[7f1ffe583000+82000]
[ 440.018231] traps: upowerd[2017] trap int3 ip:7fc20b65b7b5 sp:7fff96387230 error:0 in libglib-2.0.so.0.6600.2[7fc20b622000+82000]
[ 440.241096] traps: upowerd[2025] trap int3 ip:7fb5287c87b5 sp:7ffe56fe85f0 error:0 in libglib-2.0.so.0.6600.2[7fb52878f000+82000]
[ 440.253984] traps: upowerd[2031] trap int3 ip:7f4cad1de7b5 sp:7ffdfce79d10 error:0 in libglib-2.0.so.0.6600.2[7f4cad1a5000+82000]
[ 441.295756] traps: upowerd[2058] trap int3 ip:7f5d40eb17b5 sp:7ffe192be190 error:0 in libglib-2.0.so.0.6600.2[7f5d40e78000+82000]
[ 441.308291] traps: upowerd[2066] trap int3 ip:7f82844607b5 sp:7ffd139f4fd0 error:0 in libglib-2.0.so.0.6600.2[7f8284427000+82000]
[ 520.517515] show_signal: 7 callbacks suppressed
[ 520.517517] traps: upowerd[2162] trap int3 ip:7f6021e467b5 sp:7ffe2fa9d9e0 error:0 in libglib-2.0.so.0.6600.2[7f6021e0d000+82000]
[ 596.589760] traps: upowerd[2188] trap int3 ip:7f460ee557b5 sp:7ffc7b61ef70 error:0 in libglib-2.0.so.0.6600.2[7f460ee1c000+82000]
[ 709.685954] traps: upowerd[2226] trap int3 ip:7f19543277b5 sp:7ffda230dfc0 error:0 in libglib-2.0.so.0.6600.2[7f19542ee000+82000]
[ 723.893526] traps: upowerd[2233] trap int3 ip:7f88717667b5 sp:7ffc5088f330 error:0 in libglib-2.0.so.0.6600.2[7f887172d000+82000]
[ 893.166977] traps: upowerd[2241] trap int3 ip:7ff7bf5ab7b5 sp:7ffe350c1090 error:0 in libglib-2.0.so.0.6600.2[7ff7bf572000+82000]
[ 971.222799] traps: upowerd[2247] trap int3 ip:7f052e08e7b5 sp:7ffd0d5bd900 error:0 in libglib-2.0.so.0.6600.2[7f052e055000+82000]
[ 1046.588465] traps: upowerd[2254] trap int3 ip:7f13b8d007b5 sp:7fff371ba410 error:0 in libglib-2.0.so.0.6600.2[7f13b8cc7000+82000]

cwizardone · 11-06-2020, 09:14 AM

Quote:

Originally Posted by cwizardone

I see Mr. Volkerding was kind enough to use the kde4 system tray icons for Vtown-kde5.
Nice touch!
Many thanks.

Now, if someone could convince the yaWP developer to update his excellent project for kde5, you might have something.

<--- big grin.

ZhaoLin1457 · 11-06-2020, 10:09 AM

Quote:

Originally Posted by denydias

Hi there! I see people here happy with the news... I'm too. Upgraded yesterday from ktown. Everything worked fine just as expected. Thanks for the ones who spotted sddm conf and pam misses.

I bring some odd behavior since ktown age: in init 4, Plasma shutdown doesn't run /etc/rc.d/rc.6 or /etc/rc.d/rc.K, which leads to /etc/rc.d/rc.local_shutdown not being executed. When in init 3 things works as expected and rc.local_shutdown is run upon halt or reboot.

Is that a common Plasma behavior? Should I set /etc/rc.d/rc.local_shutdown to run (with sudo, of course) in logout scripts at systemsettings5? Is there something broke with Plasma in this regard?

The shutdown init scripts are executed as usual, but you do not see their output until the init is reloaded, because their output is in VT where SDDM has. Likely VT7

Basically, you are switched to VT1 but the scripts continue to output to VT7. You can see a glimpse if you look careful, right before the VT switch is done.

I seen this behavior since long time, and long time ago I was even curious to switch immediately back in the VT7, being able to do it thanks of my slower boxes. And the shutdown messages was there, until the init reloads.

Anyway, I do not bothered much about this, considering that either elogind or SDDM does not like our VT dance, useless but imposed to them just to preserve an old behavior...

mlangdn · 11-06-2020, 10:13 AM

Quote:

Originally Posted by zux

I have now twice had an issue, where, after the screen has been locked for a longer time (more than couple of hours) I can no longer unlock it.
Mouse moves, but no option to enter the password appears.
I could press ALT+CTRL+BACKSPACE and restart the session, that fixed it.
Not easy to reproduce and investigate further, so I wanted to first ask if anyone else has had such issues?

My screen locked on me while I went to get a sandwich. I was gone 20 minutes or so. Came back to a black screen with this message in the middle:

Code:

The screen unlocker is broken and cannot be fixed. Press Ctrl+Alt+F2 to get another console and login as root. Run ck-unlock-session <session name>

That didn't work and hard reset to fix. Hasn't happened again????

ZhaoLin1457 · 11-06-2020, 10:16 AM

Quote:

Originally Posted by Toutatis

Just two problems on a laptop : when running 'startx' from console, a normal user cannot shutdown the system. And no battery is seen. upower gives error-messages

I get also this in dmesg

If is not clear yet for you that you have an issue with the upower daemon, there's how looks the output in my mini-PC:

Code:

root@darkstar:~# upower -d
Daemon:
  daemon-version:  0.9.23
  can-suspend:     yes
  can-hibernate:   no
  on-battery:      no
  on-low-battery:  no
  lid-is-closed:   no
  lid-is-present:  no
  is-docked:       no

ZhaoLin1457 · 11-06-2020, 10:21 AM

Quote:

Originally Posted by mlangdn

My screen locked on me while I went to get a sandwich. I was gone 20 minutes or so. Came back to a black screen with this message in the middle:

Code:

The screen unlocker is broken and cannot be fixed. Press Ctrl+Alt+F2 to get another console and login as root. Run ck-unlock-session <session name>

That didn't work and hard reset to fix. Hasn't happened again????

Hint: Plasma5 asking for "ck-unlock-session <session name>" while supposedly you run elogind?

So, did you still have the ConsoleKit2 installed in your system?

This is one of the things happening when you have both elogind and ConsoleKit2 in your box. Because the ConsoleKit2 daemon wouldn't stay dead.

I remember being bitten too by this behvior when testing first elogind powered release made by Mr. Hameleers, after forgetting to blacklist the ConsoleKit2, so it was added back by slackpkg.

Toutatis · 11-06-2020, 10:23 AM

@ZhaoLin1457

Everything was solved by applying 'update-pkg --reinstall' to all packages of vtown.
I don't know what happened, because everything worked correctly on another laptop with exactly the same installed packages.

denydias · 11-06-2020, 10:49 AM

Quote:

Originally Posted by ZhaoLin1457

The shutdown init scripts are executed as usual, but you do not see their output until the init is reloaded, because their output is in VT where SDDM has. Likely VT7

Basically, you are switched to VT1 but the scripts continue to output to VT7. You can see a glimpse if you look careful, right before the VT switch is done.

I seen this behavior since long time, and long time ago I was even curious to switch immediately back in the VT7, being able to do it thanks of my slower boxes. And the shutdown messages was there, until the init reloads.

Anyway, I do not bothered much about this, considering that either elogind or SDDM does not like our VT dance, useless but imposed to them just to preserve an old behavior...

Thanks, @ZhaoLin1457! I haven't noticed that, because when I shut down or restart via Plasma, as soon X is gone, I'm back to the console and I see only a small set of shutdown messages that is quite different from what the whole rc.local_shutdown should output.

But I'll look into it to find a way to confirm it run. Thanks a lot!

bassmadrigal · 11-06-2020, 11:06 AM

Quote:

Originally Posted by denydias

But I'll look into it to find a way to confirm it run. Thanks a lot!

You could add a really simple command to the rc.local_shutdown to verify... something like:

Code:

touch /local_shutdown-works

This would create a text file in the root partition and you could verify whether or not it is there on the next startup.

ZhaoLin1457 · 11-06-2020, 11:14 AM

Quote:

Originally Posted by bassmadrigal

You could add a really simple command to the rc.local_shutdown to verify... something like:

Code:

touch /local_shutdown-works

This would create a text file in the root partition and you could verify whether or not it is there on the next startup.

Believe or not, exactly this I did myself long time ago to confirm that the scripts are running, before wondering where they do output and observing the VT dance.

drgibbon · 11-06-2020, 11:18 AM

Quote:

Originally Posted by AlleyTrotter

Have you any idea which package contains liblmdb.so?

With slackpkg:

Code:

slackpkg file-search liblmdb.so

Or using the online Slackware package search, just change "Mode" to "content" and search for liblmdb.so.

Also, if you are missing packages you can do:

Code:

slackpkg install slackware64

to get a list of anything that's in the main tree but not installed (provided it's not blacklisted). I guess you drop the "64" if you're on 32-bit.

AlleyTrotter · 11-06-2020, 01:39 PM

Quote:

Originally Posted by drgibbon

With slackpkg:

Code:

slackpkg file-search liblmdb.so

Or using the online Slackware package search, just change "Mode" to "content" and search for liblmdb.so.

Also, if you are missing packages you can do:

Code:

slackpkg install slackware64

to get a list of anything that's in the main tree but not installed (provided it's not blacklisted). I guess you drop the "64" if you're on 32-bit.

Somewhere along the line lmdb.so quit working on my system. It was install but stopped working ???
Thanks to ZhaoLin1457 advising that the package was in slackware64/l/ and an upgradepkg --reinstall fixed everything.
Thank You for the response
John