[kde-unstable] Plasma 5.10 beta

arojas · 2017-05-15 12:36:34

Plasma 5.10 beta is now available for testing in the [kde-unstable] repo. See https://www.kde.org/announcements/plasma-5.9.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. Note that [kde-unstable] also contains Qt 5.9 beta, so make sure to specify the Qt version when reporting issues upstream.

Happy testing!

Tromzy · 2017-05-15 13:12:02

On my machine the Plasma Wayland session is broken, all I get is a black screen with a mouse pointer.

Last edited by Tromzy (2017-05-15 13:31:32)

arojas · 2017-05-15 13:25:41

Tromzy wrote:

On my machine the Plasma session is broken, all I get is a black screen with a mouse pointer.

X or Wayland?

Tromzy · 2017-05-15 13:29:25

Sorry : Wayland. X Session works. I tried to revert back to the Qt5-wayland version on testing (5.8) but it did not help.

Last edited by Tromzy (2017-05-15 13:30:11)

KlavKalashj · 2017-05-15 13:29:46

Just installed it, seems to work fine here. Haven't experienced any issues yet. Looks very nice and smooth. Anyone know where to find the new Plymouth configuration kcm?

arojas · 2017-05-15 13:35:47

Tromzy wrote:

Sorry : Wayland. X Session works. I tried to revert back to the Qt5-wayland version on testing (5.8) but it did not help.

Yeah, Wayland session is completely borked again with Qt 5.9. Not sure if reporting it would do any good, since they didn't even fix it for Qt 5.8 yet

arojas · 2017-05-15 13:39:32

KlavKalashj wrote:

Anyone know where to find the new Plymouth configuration kcm?

In AUR when someone packages it. Plymouth is not supported in Arch

Tromzy · 2017-05-15 13:43:32

arojas wrote:

Tromzy wrote:
Sorry : Wayland. X Session works. I tried to revert back to the Qt5-wayland version on testing (5.8) but it did not help.
Yeah, Wayland session is completely borked again with Qt 5.9. Not sure if reporting it would do any good, since they didn't even fix it for Qt 5.8 yet

Too bad reverting to Qt5.8 does not help (Qt5.8 used to work fine with Plasma Wayland 5.9.)

arojas · 2017-05-15 13:49:11

Tromzy wrote:

Too bad reverting to Qt5.8 does not help (Qt5.8 used to work fine with Plasma Wayland 5.9.)

It worked with Qt 5.8 because we're reverting the qtwayland change that broke it. Upstream doesn't support anything newer than 5.7, which is obviously not an option for us.

Tromzy · 2017-05-15 13:55:44

arojas wrote:

Tromzy wrote:
Too bad reverting to Qt5.8 does not help (Qt5.8 used to work fine with Plasma Wayland 5.9.)
It worked with Qt 5.8 because we're reverting the qtwayland change that broke it. Upstream doesn't support anything newer than 5.7, which is obviously not an option for us.

So, will you revert the change that broke Qtwayland again ?

Loose_Control · 2017-05-15 14:53:10

Akregator is crashing with the Beta but i am guessing Qt 5.9 is causing that. (Some package probably needs a rebuild)
For some reason drkonqi isn't started.

└[~]> gdb akregator
GNU gdb (GDB) 7.12.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from akregator...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/akregator 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffc87be700 (LWP 1120)]
[New Thread 0x7fffc4837700 (LWP 1121)]
[New Thread 0x7fffbcd9e700 (LWP 1122)]
[New Thread 0x7fffb7fff700 (LWP 1124)]
[New Thread 0x7fffb77fe700 (LWP 1125)]
[New Thread 0x7fffb6ffd700 (LWP 1126)]
[New Thread 0x7fffb67fc700 (LWP 1127)]
[New Thread 0x7fffb5ffb700 (LWP 1128)]
[New Thread 0x7fffb57fa700 (LWP 1129)]
[New Thread 0x7fffb4ff9700 (LWP 1130)]
[New Thread 0x7fff93fff700 (LWP 1131)]
[New Thread 0x7fff937fe700 (LWP 1132)]
[New Thread 0x7fff92ffd700 (LWP 1133)]
[New Thread 0x7fff91ffb700 (LWP 1135)]
[New Thread 0x7fff927fc700 (LWP 1134)]
[New Thread 0x7fff917fa700 (LWP 1136)]
[New Thread 0x7fff90ff9700 (LWP 1137)]
[New Thread 0x7fff7bfff700 (LWP 1138)]
[New Thread 0x7fff7b7fe700 (LWP 1139)]
[New Thread 0x7fff7affd700 (LWP 1140)]
org.kde.pim.webengineviewer:  It's not necessary to check database now
[New Thread 0x7fff6a7fc700 (LWP 1141)]
[New Thread 0x7fff64fdb700 (LWP 1142)]
 void AdblockManager::reloadConfig() false    AdBlock::AdblockManager(0xc46d00)
[New Thread 0x7fff6376f700 (LWP 1145)]
[New Thread 0x7fff62b60700 (LWP 1148)]
"Tag 'a' is not defined in message {<__kuit_internal_top__>Weitere Informationen über die Verwendung von Akregator f...}."
"Tag 'a' is not defined in message {<__kuit_internal_top__>Weitere Informationen über die Verwendung von Akregator f...}."
org.kde.pim.webengineviewer: Database already initialized. It's a bug in code if you call it twice.
 void AdblockManager::reloadConfig() false    AdBlock::AdblockManager(0xd6a9c0)
"Tag 'a' is not defined in message {<__kuit_internal_top__>Weitere Informationen über die Verwendung von Akregator f...}."
"Tag 'a' is not defined in message {<__kuit_internal_top__>Weitere Informationen über die Verwendung von Akregator f...}."
bool DBusMenuExporterDBus::AboutToShow(int): Condition failed: menu
bool DBusMenuExporterDBus::AboutToShow(int): Condition failed: menu
[New Thread 0x7ffee0d80700 (LWP 1159)]
[Thread 0x7ffee0d80700 (LWP 1159) exited]
[snip (my RSS feed are just listed here)]
 void AdblockManager::reloadConfig() false    AdBlock::AdblockManager(0x32e7710)
kf5.kio.core: Invalid URL: QUrl("/favicon.ico")

Thread 1 "akregator" received signal SIGSEGV, Segmentation fault.
0x00007ffff46a05f7 in QMetaObject::cast(QObject const*) const () from /usr/lib/libQt5Core.so.5
(gdb)

Last edited by Loose_Control (2017-05-15 14:53:52)

Tromzy · 2017-05-15 15:00:14

Akregator works fine here.

nierro · 2017-05-15 16:31:00

Plasma-discover crashing without flatpak backend (packaging or upstream issue?):

no streams to aggregate!!
WARNING: Cannot find style "org.kde.desktop" - fallback: "/usr/lib/qt/qml/QtQuick/Controls/Styles/Desktop"
error loading "flatpak-backend" "Cannot load library /usr/lib/qt/plugins/discover/flatpak-backend.so: (libflatpak.so.0: cannot open shared object file: No such file or directory)" QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","MetaData":{},"className":"FlatpakBackendFactory","debug":false,"version":329984})
Errore di segmentazione (core dump creato)

With flatpak installed, everything's ok.

Everything else running smoothly as far as i can tell.

Last edited by nierro (2017-05-15 16:31:09)

arojas · 2017-05-15 16:38:53

Tromzy wrote:

So, will you revert the change that broke Qtwayland again ?

No, there have been many further code changes on top of it and it's no longer possible to simply revert that one commit.

arojas · 2017-05-15 16:39:15

nierro wrote:

Plasma-discover crashing without flatpak backend (packaging or upstream issue?):

Can't reproduce. Full backtrace?

nierro · 2017-05-15 16:41:24

@arojas: http://dpaste.com/05EGZE3
And: http://dpaste.com/1HG2CKN (coredumpctl)

Another thing: is there an UI to set touchpad/touchscreen gestures? It seems they're not working on my touchpad.

Last edited by nierro (2017-05-15 16:43:16)

arojas · 2017-05-15 16:46:12

nierro wrote:

Another thing: is there an UI to set touchpad/touchscreen gestures? It seems they're not working on my touchpad.

Touchpad gestures are Wayland only. For touchscreen: Desktop behaviour -> Touch Screen

nierro · 2017-05-15 16:51:54

arojas wrote:

Touchpad gestures are Wayland only. For touchscreen: Desktop behaviour -> Touch Screen

Oh, i see thanks! I'll have to wait until qt 5.9 fixes all of the blocking bugs for wayland session then...

Last edited by nierro (2017-05-15 16:52:02)

arojas · 2017-05-16 08:47:25

Please test the Wayland session with qt5-wayland-5.9.0beta3-2

Tromzy · 2017-05-16 09:23:20

arojas wrote:

Please test the Wayland session with qt5-wayland-5.9.0beta3-2

It works ! But there are a few issues. The mouse pointer is too big (maybe because I have a dual monitor setup with different resolutions ? "Fixed" by forcing 24px mouse pointer) ; Right clicking on the desktop makes the context popup always pop at the top left corner of the desktop instead of under the pointer ; I also experienced glitchy plasma panels (way too transparent) and sometimes the mouse pointer acted like I had the left click always pushed.

Edit : globally, popups, tooltips and notifications pop at completely random places.

Last edited by Tromzy (2017-05-16 09:26:49)

PootisBird · 2017-05-17 12:58:32

Not bad, X11 session has no regressions from two days of testing.

Wayland session is more stable, I'm no longer having problems with plasmoids. It's almost good to be a daily driver for me... Almost, beyond standard accessibility helper crash at login, popups showing at random corner or center, applets showing faded in, notifications stealing focus, kinfocenter segfaulting when switching tabs.

Edit.

Also, mouse pointer is fine in gtk apps but is huge in qt apps.

Recent apps/documents in fullscreen menu are blank.

Logout popup is a window with borders named ksmserver-logout-greeter.

Notifications are sometimes cut to 30% of their proper height.

My keyboard layout is not up properly.

Edit 2

It all seems to be a Qt problem at a first glance.

Last edited by PootisBird (2017-05-17 13:22:32)

KlavKalashj · 2017-05-19 12:43:07

Ok, I found a weird error. All the text in console gets completely garbled sometimes. If I resize the window or mark text with the mouse, it clears up but gets fuzzy again soon. Maybe a rebuild is needed against the new Qt version?

Edit: Here's a screenshot: http://i.imgur.com/PcVCqNl.png

Edit2: Issue seems resolved after the latest qt update.

Last edited by KlavKalashj (2017-05-23 05:31:52)

raneon · 2017-05-22 19:40:59

X11 session seems to work well. I have the following issues in Plasma-Wayland:
- Opening systemsettings will crash all panels, Plasma-Wayland needs to restore its state (not always successful). One example of several random crashes of Plasma-Wayland.
- Systemsettings is unstable and can crash when clicking trough the menu's, sometimes the window is then empty, no back button and closing and crash
- Window's, menu's and mouse over's are placed at wrong areas, mostly in corners
- When opening the KDE Application menu and closing it by clicking somewhere on the desktop, the mouse is in a selection mode (like when holding the left mouse key pressed) that can only be cancelled by making a double click.
- Transparency of the KDE Application menu is too high
- Some buttons cannot be clicked properly, only at their borders (e.g. in the applications menu)
- Volume button is missing
- Right click on the desktop and then left click doesn't hide pop-up menu
- Notifications steel active window input
- Top panel is over other windows when opening a new Plasma session
- Top left corner is sometimes occupied by some application like XWayland applications
- The mouse/keyboard don't work to remote SSH virtual machine in VirtManager (maybe related to bug https://bugzilla.redhat.com/show_bug.cgi?id=1413814)
- The Escape key (ESC) doesn't work in games correctly like Wither 2 or Tomb Raider, there is a notification to press 3 seconds ESC and then the input would be handled by Plasma again, but it doesn't work accurately. Switch to the desktop and back sometimes helps to get the mouse focus back again. If it doesn't work then in games the mouse can behave strange, fixed to one area and it moves fast and is not controllable.
- In the application menu the menu entries during mouse over are often too short, too long or totally limited to one line, even scroll bars are shown sometimes.
- KAccessHelper crash during every new Plasma session
- Some Wayland apps don't have a symbol like Nextcloud Client
- Num Lock key is not activated automatically even if activated keyboard settings
- Language selection is not shown in quick settings app in task bar

Tromzy · 2017-05-23 07:27:39

There is an updated QT5.9 wayland beta (4), maybe it fixes some problems ?

Edit : No, it fixes nothing.

Last edited by Tromzy (2017-05-23 07:33:20)

KlavKalashj · 2017-05-23 08:00:53

Tromzy wrote:

There is an updated QT5.9 wayland beta (4), maybe it fixes some problems ?
Edit : No, it fixes nothing.

See my last post. It fixed my screwed up Konsole.

Edit: Whoops, read to quickly. My issue had nothing to do with Wayland. Sorry.

Last edited by KlavKalashj (2017-05-23 08:01:27)

Arch Linux

#1 2017-05-15 12:36:34

[kde-unstable] Plasma 5.10 beta

#2 2017-05-15 13:12:02

Re: [kde-unstable] Plasma 5.10 beta

#3 2017-05-15 13:25:41

Re: [kde-unstable] Plasma 5.10 beta

#4 2017-05-15 13:29:25

Re: [kde-unstable] Plasma 5.10 beta

#5 2017-05-15 13:29:46

Re: [kde-unstable] Plasma 5.10 beta

#6 2017-05-15 13:35:47

Re: [kde-unstable] Plasma 5.10 beta

#7 2017-05-15 13:39:32

Re: [kde-unstable] Plasma 5.10 beta

#8 2017-05-15 13:43:32

Re: [kde-unstable] Plasma 5.10 beta

#9 2017-05-15 13:49:11

Re: [kde-unstable] Plasma 5.10 beta

#10 2017-05-15 13:55:44

Re: [kde-unstable] Plasma 5.10 beta

#11 2017-05-15 14:53:10

Re: [kde-unstable] Plasma 5.10 beta

#12 2017-05-15 15:00:14

Re: [kde-unstable] Plasma 5.10 beta

#13 2017-05-15 16:31:00

Re: [kde-unstable] Plasma 5.10 beta

#14 2017-05-15 16:38:53

Re: [kde-unstable] Plasma 5.10 beta

#15 2017-05-15 16:39:15

Re: [kde-unstable] Plasma 5.10 beta

#16 2017-05-15 16:41:24

Re: [kde-unstable] Plasma 5.10 beta

#17 2017-05-15 16:46:12

Re: [kde-unstable] Plasma 5.10 beta

#18 2017-05-15 16:51:54

Re: [kde-unstable] Plasma 5.10 beta

#19 2017-05-16 08:47:25

Re: [kde-unstable] Plasma 5.10 beta

#20 2017-05-16 09:23:20

Re: [kde-unstable] Plasma 5.10 beta

#21 2017-05-17 12:58:32

Re: [kde-unstable] Plasma 5.10 beta

#22 2017-05-19 12:43:07

Re: [kde-unstable] Plasma 5.10 beta

#23 2017-05-22 19:40:59

Re: [kde-unstable] Plasma 5.10 beta

#24 2017-05-23 07:27:39

Re: [kde-unstable] Plasma 5.10 beta

#25 2017-05-23 08:00:53

Re: [kde-unstable] Plasma 5.10 beta

Board footer