[kde-unstable] Plasma 5.11 beta

arojas · 2017-09-14 12:33:41

Plasma 5.11 beta is now available for testing in the [kde-unstable] repo. See https://www.kde.org/announcements/plasma-5.10.95.php for the release notes. Only x86_64 packages are available.

As usual, you need to have [testing] enabled. Report packaging issues to bugs.archlinux.org with the [kde-unstable] tag, and upstream issues to bugs.kde.org.

Happy testing!

raneon · 2017-09-14 16:56:20

Thanks. Plasma-Wayland has is still a lot of issues and glitches, I could use 5.10 by using some workarounds, but 5.11 doesn't look that good at the moment.

When I first started Plasma-Wayland I noticed the extrem font size. Previously I had to change on my 4K notebook screen to 160 dpi so that fonts look normal. Now with Plasma-Wayland 5.11 I had to change back to 96dpi, but then interfaces have been unsharp. But I found in the screen settings that there is a scaling factor on Plasma-Wayland (not on X11) that is set automatically to 2x. So this explains the bad scaling. Setting it back to 1x and then changing to 160 looks sharp and clear again. But it doesn't save this value, after next reboot is is set back automatically to 2x which is doesn't look sharp at all.

I would say a lot of things have regressed in Plasma-Wayland 5.11. On my Intel GPU it is nearly impossible to use, too many crashes/issues. Maybe it is better on a AMD GPU, I will try.

Last edited by raneon (2017-09-14 17:05:39)

sva_h4cky0 · 2017-09-14 16:56:24

dammmmm you're fast man, thanks

raneon · 2017-09-14 17:20:59

What really regressed as well is if you press Alt + F2 on Plasma-Wayland. Kwin is either really slow or it doesn't respond at all, so typing kill plasmashell and then running it again via the plasmashell command is often not possible. I assume because of some previous crashes, but I don't know.

Tromzy · 2017-09-14 20:01:28

raneon wrote:

Thanks. Plasma-Wayland has is still a lot of issues and glitches, I could use 5.10 by using some workarounds, but 5.11 doesn't look that good at the moment.
When I first started Plasma-Wayland I noticed the extrem font size. Previously I had to change on my 4K notebook screen to 160 dpi so that fonts look normal. Now with Plasma-Wayland 5.11 I had to change back to 96dpi, but then interfaces have been unsharp. But I found in the screen settings that there is a scaling factor on Plasma-Wayland (not on X11) that is set automatically to 2x. So this explains the bad scaling. Setting it back to 1x and then changing to 160 looks sharp and clear again. But it doesn't save this value, after next reboot is is set back automatically to 2x which is doesn't look sharp at all.
I would say a lot of things have regressed in Plasma-Wayland 5.11. On my Intel GPU it is nearly impossible to use, too many crashes/issues. Maybe it is better on a AMD GPU, I will try.

Do you use it on a multi-monitor setup ? It works bad on it, but on my machine it works quite good on a single monitor setup.

raneon · 2017-09-14 20:34:54

Tromzy wrote:

Do you use it on a multi-monitor setup ? It works bad on it, but on my machine it works quite good on a single monitor setup.

I always had very bad experience with multi-monitor setups including crashes, so I didn't even bother to test again. No, just a single 4k screen with a Intel GPU. If I could change the scaling factor down to 1x on Plasma-Wayland it would be great. Can you do this?

Something I noted now as well are the mouse clicks e.g. when marking text... they are completly inaccurate. Maybe it is related to the scaling of 2x, I never had such an issue on Plasma-Wayland before.

Last edited by raneon (2017-09-14 20:36:40)

JanKusanagi · 2017-09-18 14:59:44

i686 build seems to only provide a few packages, apparently.
I checked a few different mirrors, just in case.

Did something break?

Last edited by JanKusanagi (2017-09-18 15:11:53)

ewaller · 2017-09-18 15:09:55

JanKusanagi wrote:

i686 build seems to only provide a few packages, apparently.
I checked a few different mirrors, just in case.
Did something break?

https://www.archlinux.org/news/phasing- … 6-support/

arojas · 2017-09-18 15:12:20

JanKusanagi wrote:

i686 build seems to only provide a few packages, apparently.
I checked a few different mirrors, just in case.
Did something break?

arojas wrote:

Only x86_64 packages are available.

JanKusanagi · 2017-09-18 15:13:14

ewaller wrote:

JanKusanagi wrote:
i686 build seems to only provide a few packages, apparently.
I checked a few different mirrors, just in case.
Did something break?
https://www.archlinux.org/news/phasing- … 6-support/

Yes, I know about that, but the thing is, _some_ packages are there. Either it's no longer built (which would be totally understandable), or it still is, right?

EDIT:

arojas wrote:

Only x86_64 packages are available.

Sorry, I somehow didn't see that!

Thanks!

Last edited by JanKusanagi (2017-09-18 15:15:08)

raneon · 2017-09-18 17:15:31

I did report several bugs upstream to KDE and it seems that some of the Plasma-Wayland issues with high DPI will be addressed.

Jansen · 2017-09-21 15:46:49

Could you link the reports? I'm planing to test the Wayland sessions with three monitors of which one is a HiDPI one.

Buddlespit · 2017-09-22 10:22:56

Jansen wrote:

Could you link the reports? I'm planing to test the Wayland sessions with three monitors of which one is a HiDPI one.

https://wiki.archlinux.org/index.php/Of … e-unstable

Jansen · 2017-09-22 12:03:47

Buddlespit wrote:

Jansen wrote:
Could you link the reports? I'm planing to test the Wayland sessions with three monitors of which one is a HiDPI one.
https://wiki.archlinux.org/index.php/Of … e-unstable

I was asking for links to the bug reports of raneon...

Buddlespit · 2017-09-22 16:59:53

Wow... I know I'm dense first thing in the morning, but wow...

raneon · 2017-09-26 13:31:06

Jansen wrote:

Buddlespit wrote:
Jansen wrote:
Could you link the reports? I'm planing to test the Wayland sessions with three monitors of which one is a HiDPI one.
https://wiki.archlinux.org/index.php/Of … e-unstable
I was asking for links to the bug reports of raneon...

Specifically regarding HiDPI and the scaling factor on Wayland I have reported or followed the following issues:
https://bugs.kde.org/show_bug.cgi?id=384763 => now linked to https://bugs.kde.org/show_bug.cgi?id=384733
https://bugs.kde.org/show_bug.cgi?id=384765
https://bugs.kde.org/show_bug.cgi?id=384767
https://bugs.kde.org/show_bug.cgi?id=384769
https://bugs.kde.org/show_bug.cgi?id=384829

Personally I don't like the scaling factor, it makes a lot of things blurry and unsharp, at least I hope that we can turn it off in Plasma 5.11.

Regarding stability and daily use I think this bug is critical as well.
https://bugs.kde.org/show_bug.cgi?id=372789

In general I hope that the stability on Wayland will improve before release, but with Plasma 5.10 beta I had a lot of issues as well so that is why I'm still positive about the final 5.11 release.

As arojas said please report your bugs upstream, the issues I had as a normal user might be completely different with other hardware.

Last edited by raneon (2017-09-26 16:43:31)

hifi25nl · 2017-10-12 15:02:29

I have enabled kde-unstable and installed Plasma 5.11 without problems. Recently I have made the update to qt5 5.10 beta, I have 2 problems:
1) Analogue clock widget cannot start because of qml problems:

 
Error loading QML file: file:///usr/share/plasma/plasmoids/org.kde.plasma.analogclock/contents/ui/analogclock.qml:192:34: Type PlasmaCalendar.MonthView unavailable
file:///usr/lib/qt/qml/org/kde/plasma/calendar/MonthView.qml:222:22: DaysCalendar is not a type

2) i cannot print from Plasma applications (but I can print from LibreOffice etc.). I have a dialogue box for printing indicating the location of pdf file. However I cannot print to pdf or paper.

arojas · 2017-10-12 16:45:15

hifi25nl wrote:

1) Analogue clock widget cannot start because of qml problems

Will be fixed in plasma-frameworks 5.39

2) i cannot print from Plasma applications (but I can print from LibreOffice etc.). I have a dialogue box for printing indicating the location of pdf file. However I cannot print to pdf or paper.

Can't reproduce

PootisBird · 2017-10-12 19:54:30

GTK theme applet is not working for me. It keeps resetting cursors and icons to Adwaita, font to C059.

colinkeenan · 2017-10-13 16:30:43

arojas wrote:

hifi25nl wrote:
1) Analogue clock widget cannot start because of qml problems
Will be fixed in plasma-frameworks 5.39

I decided to search on "frameworks" in the packages. I just realized that the web search doesn't offer "kde-unstable" results. Searching with

pacman -Ss frameworks

returns only one relevant result:

kde-unstable/kdeclarative 5.38.0-2 (kf5) [installed]
    Provides integration of QML and KDE Frameworks

Anyway, I guess it's expected to be available tomorrow: https://community.kde.org/Schedules/Frameworks

Also, why is it necessary to enable [testing]? I decided to try [kde-unstable] without enabling [testing] and it seems to work.

Last edited by colinkeenan (2017-10-13 16:32:57)

Xabre · 2017-10-13 22:25:43

colinkeenan wrote:

I decided to search on "frameworks" in the packages. I just realized that the web search doesn't offer "kde-unstable" results. Searching with
pacman -Ss frameworks
returns only one relevant result:

He was refering to KDE frameworks 5.39 release, that is expected to be released on October 14, this Saturday. try with pacman -Sg kf5 to see all packages that belong to the group.

Last edited by Xabre (2017-10-13 22:28:36)

colinkeenan · 2017-10-13 22:33:21

Thanks @Xabre

pb · 2017-10-21 10:54:46

arojas wrote:

hifi25nl wrote:
1) Analogue clock widget cannot start because of qml problems
Will be fixed in plasma-frameworks 5.39
2) i cannot print from Plasma applications (but I can print from LibreOffice etc.). I have a dialogue box for printing indicating the location of pdf file. However I cannot print to pdf or paper.
Can't reproduce

I could confirm this issue. My system with Plasma 5.11/Qt5.9.2/KF5.39 (Arch testing) works perfectly. I can print everything with my Brother DCP-115C (yes, very old printer, but it works) and brother-mfc-210c (from AUR). I can print from all applications. After upgrade to kde-unstable repository (Qt5.10beta1 and some other packages) I cannot get access to printer at all.
When I try to use CUPS via localhost:631 I get this message:

This site can’t be reached

The webpage at localhost:631 might be temporarily down or it may have moved permanently to a new web address.
ERR_UNKNOWN_URL_SCHEME

When I try print from i.e. qupzilla, dialog box looks like this:

(My qupzilla is with LC_ALL=C, but this dialog is in Polish, but what is important: field "Plik wyjściowy" /it means "output file"/ is always "on" even, when printer is my Brother; when I cancel output file, I get this message:

The file is a read-only file.
Please select a different file name.

The same applies to other Qt based applications, but from Libre Office or GIMP I can print to my local printer.
After print something from Libre Office, I can get access to localhost:631.
There are some logs from CUPS from the moment I've tried to use printer with Qt5.10:
Access Log:

localhost - - [21/Oct/2017:07:40:08 +0200] "POST / HTTP/1.1" 200 412 Create-Printer-Subscriptions successful-ok
localhost - - [21/Oct/2017:08:38:27 +0200] "POST / HTTP/1.1" 200 181 Renew-Subscription successful-ok
localhost - - [21/Oct/2017:09:36:47 +0200] "POST / HTTP/1.1" 200 181 Renew-Subscription successful-ok
localhost - - [21/Oct/2017:10:35:07 +0200] "POST / HTTP/1.1" 200 181 Renew-Subscription successful-ok
localhost - - [21/Oct/2017:11:33:27 +0200] "POST / HTTP/1.1" 200 181 Renew-Subscription successful-ok
localhost - - [21/Oct/2017:12:10:04 +0200] "POST / HTTP/1.1" 200 150 Cancel-Subscription successful-ok
localhost - - [21/Oct/2017:12:12:09 +0200] "POST / HTTP/1.1" 200 412 Create-Printer-Subscriptions successful-ok
localhost - - [21/Oct/2017:12:38:20 +0200] "POST /printers/Brother_DCP-115C HTTP/1.1" 200 207 Create-Job successful-ok
localhost - - [21/Oct/2017:12:38:20 +0200] "POST /printers/Brother_DCP-115C HTTP/1.1" 200 12026 Send-Document successful-ok
localhost - - [21/Oct/2017:12:43:31 +0200] "GET /admin/log/access_log? HTTP/1.1" 401 0 - -

Error Log:

W [21/Oct/2017:07:38:21 +0200] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [21/Oct/2017:07:38:21 +0200] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [21/Oct/2017:07:38:21 +0200] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [21/Oct/2017:07:38:22 +0200] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [21/Oct/2017:07:38:22 +0200] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [21/Oct/2017:07:38:22 +0200] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [21/Oct/2017:12:10:47 +0200] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [21/Oct/2017:12:10:47 +0200] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [21/Oct/2017:12:10:47 +0200] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [21/Oct/2017:12:10:47 +0200] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [21/Oct/2017:12:10:47 +0200] CreateProfile failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files
W [21/Oct/2017:12:10:47 +0200] CreateDevice failed: org.freedesktop.DBus.Error.ServiceUnknown:The name org.freedesktop.ColorManager was not provided by any .service files

But as I can see, there isn't any logs from before I use print in Libre Office.

Similarly I can not use cups-pdf (in this case, to "output file" field isn't available.
I have one more option in "Printer" field - "print to file (PDF)" and it works.

Only one solution is to downgrade Qt5.10beta1 to Qt5.9.2.

hifi25nl · 2017-10-21 10:57:20

I confirm that. Downgrade to Qt 5.9.2 did solve the problem for me also.

arojas · 2017-10-21 11:18:27

pb wrote:

Only one solution is to downgrade Qt5.10beta1 to Qt5.9.2.

Please report this upstream

Arch Linux

#1 2017-09-14 12:33:41

[kde-unstable] Plasma 5.11 beta

#2 2017-09-14 16:56:20

Re: [kde-unstable] Plasma 5.11 beta

#3 2017-09-14 16:56:24

Re: [kde-unstable] Plasma 5.11 beta

#4 2017-09-14 17:20:59

Re: [kde-unstable] Plasma 5.11 beta

#5 2017-09-14 20:01:28

Re: [kde-unstable] Plasma 5.11 beta

#6 2017-09-14 20:34:54

Re: [kde-unstable] Plasma 5.11 beta

#7 2017-09-18 14:59:44

Re: [kde-unstable] Plasma 5.11 beta

#8 2017-09-18 15:09:55

Re: [kde-unstable] Plasma 5.11 beta

#9 2017-09-18 15:12:20

Re: [kde-unstable] Plasma 5.11 beta

#10 2017-09-18 15:13:14

Re: [kde-unstable] Plasma 5.11 beta

#11 2017-09-18 17:15:31

Re: [kde-unstable] Plasma 5.11 beta

#12 2017-09-21 15:46:49

Re: [kde-unstable] Plasma 5.11 beta

#13 2017-09-22 10:22:56

Re: [kde-unstable] Plasma 5.11 beta

#14 2017-09-22 12:03:47

Re: [kde-unstable] Plasma 5.11 beta

#15 2017-09-22 16:59:53

Re: [kde-unstable] Plasma 5.11 beta

#16 2017-09-26 13:31:06

Re: [kde-unstable] Plasma 5.11 beta

#17 2017-10-12 15:02:29

Re: [kde-unstable] Plasma 5.11 beta

#18 2017-10-12 16:45:15

Re: [kde-unstable] Plasma 5.11 beta

#19 2017-10-12 19:54:30

Re: [kde-unstable] Plasma 5.11 beta

#20 2017-10-13 16:30:43

Re: [kde-unstable] Plasma 5.11 beta

#21 2017-10-13 22:25:43

Re: [kde-unstable] Plasma 5.11 beta

#22 2017-10-13 22:33:21

Re: [kde-unstable] Plasma 5.11 beta

#23 2017-10-21 10:54:46

Re: [kde-unstable] Plasma 5.11 beta

#24 2017-10-21 10:57:20

Re: [kde-unstable] Plasma 5.11 beta

#25 2017-10-21 11:18:27

Re: [kde-unstable] Plasma 5.11 beta

Board footer