Skip to main content ↑ ↓
Topic: Updated to Plasma 6 and have a number of issues, and Wayland won't start (Read 626 times) previous topic - next topic
0 Members and 4 Guests are viewing this topic.

Updated to Plasma 6 and have a number of issues, and Wayland won't start

I did a `pacman -Syu` and noticed Plasma was updated to 6, which was concerning. And indeed, a large number of things are broken, and I'm looking for help on learning more info so I can fix them.

* I noticed Plasma Wayland is now the default in sddm. Attempting to login with that fails though, and `/var/log/sddm.log` shows:

```
[12:15:26.957] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt7 -auth /var/run/sddm/xauth_NrfRIV -noreset -displayfd 18
[12:15:26.981] (EE) DAEMON: Failed to read display number from pipe
[12:15:26.981] (II) DAEMON: Display server stopping...
[12:15:26.981] (WW) DAEMON: Attempt 1 starting the Display server on vt 7 failed
```

* I don't see anything unusual in /var/log/Xorg.0.log, except perhaps:

```
[   466.992] (II) LoadModule: "fbdev"
[   466.992] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[   466.993] (EE) Failed to load /usr/lib/xorg/modules/drivers/fbdev_drv.so: /usr/lib/xorg/modules/drivers/fbdev_drv.so: undefined symbol: fbdevHWSave
[   466.993] (EE) Failed to load module "fbdev" (loader failed, 0)
```

However I think this happens every time

* None of my custom keyboard shortcuts work. In the system settings UI under Keyboard -> Shortcuts, the icon for "Custom Shortcuts Service" is missing. It lists my custom shortcuts there but none of them work. I found https://forum.artixlinux.org/index.php/topic,6564.msg40026.html#msg40026 but downgrading kglobalaccel5 didn't work, and he said it was solved by upgrading to Plasma 6, which is what caused it for me

* Lots of things seem missing in the application launcher (meta key), with empty categories showing up for some reason: https://i.imgur.com/tgwd19w.jpeg

* Fonts look wrong, like they're not truetype.

* Icons in the task switcher in my vertical taskbar are larger

* The taskbars aren't aligned to the bottom and sides of the screen, they're about 10 pixels away.

* Konsole now attempts to find when doing `alt-f`, a bash shortcut to hump to the next word boundary

How can I troubleshoot Wayland not starting and my keyboard shortcuts in particular? My system isn't really custom in any way, I just used KDE's settings to set things the way I liked them, and now everything seems broken. I don't know if I was using Wayland before, I suspect not, but things like fonts being different, icon sizes being larger, and the taskbard not aligning to the bottom of the screen might indicate I was, maybe.

Is the upgrade to Plasma 6 known to be especially buggy?

Re: Updated to Plasma 6 and have a number of issues, and Wayland won't start

Reply #2 –
Quote from: nous – on
You may find this thread useful.


Thanks, though as I understand it the user had to select plasmax11 instead of Wayland, and his problem was solved. I did that as well, and at least got into Xorg, so I think the other issues are unrelated. And I would like to learn more about why Wayland is failing to start.

Regarding my issue #7, that was caused by the toolbars being set to "floating," which may be a new feature, and was turned on after the upgrade for some reason. Perhaps I can file a bug with KDE. I disabled "floating" and they look as I expected now.

Issue #8, I removed "Find" from the toolbar by right clicking it and configuring the toolbar, and that lets me used the bash shortcut `alt+f` as expected. Again I could file that as an unexpected behavior with KDE.

The other things, I'm still not sure about. Keyboard shortcuts probably being most critical.

Re: Updated to Plasma 6 and have a number of issues, and Wayland won't start

Reply #3 –
Quote from: user0938490 – on
* None of my custom keyboard shortcuts work. In the system settings UI under Keyboard -> Shortcuts, the icon for "Custom Shortcuts Service" is missing. It lists my custom shortcuts there but none of them work. I found https://forum.artixlinux.org/index.php/topic,6564.msg40026.html#msg40026 but downgrading kglobalaccel5 didn't work, and he said it was solved by upgrading to Plasma 6, which is what caused it for me
When you used to look at your keyboard shortcuts with Plasma 5 you were actually looking at 2 two different tools:
KGlobalAccel - Not so powerful.
KHotKeys -  Very powerful.

KHotKeys didn't work under wayland so they removed it in Plasma 6. The rational being "So we made the decision to double down on KGlobalAccel and just finally delete KHotkeys once and for all for Plasma 6, rather than awkwardly ship two parallel global shortcut systems, which was always very odd and really not justifiable at all."

But in a discussion about it they did say they would "migrate the existing KHotKey shortcuts to KGlobalAccel without the user noticing" and "migrate the dbus command/fake input to shell scripts with a desktop file and register them in KGlobalAccel"

Neither happened AFAICT. Not for me anyway.
So where you can you need to set them up again. I still haven't got round to working out how to replace the fake input key combinations I had setup.

The rest of it you'll just have to go through changing settings back to how you want them.
The panel thing is right click on the panel > Enter edit mode > Set 'floating' to Off

Re: Updated to Plasma 6 and have a number of issues, and Wayland won't start

Reply #4 –
Quote from: gripped – on
Quote from: user0938490 – on
* None of my custom keyboard shortcuts work. In the system settings UI under Keyboard -> Shortcuts, the icon for "Custom Shortcuts Service" is missing. It lists my custom shortcuts there but none of them work. I found https://forum.artixlinux.org/index.php/topic,6564.msg40026.html#msg40026 but downgrading kglobalaccel5 didn't work, and he said it was solved by upgrading to Plasma 6, which is what caused it for me
When you used to look at your keyboard shortcuts with Plasma 5 you were actually looking at 2 two different tools:
KGlobalAccel - Not so powerful.
KHotKeys -  Very powerful.

KHotKeys didn't work under wayland so they removed it in Plasma 6. The rational being "So we made the decision to double down on KGlobalAccel and just finally delete KHotkeys once and for all for Plasma 6, rather than awkwardly ship two parallel global shortcut systems, which was always very odd and really not justifiable at all."

But in a discussion about it they did say they would "migrate the existing KHotKey shortcuts to KGlobalAccel without the user noticing" and "migrate the dbus command/fake input to shell scripts with a desktop file and register them in KGlobalAccel"

Neither happened AFAICT. Not for me anyway.
So where you can you need to set them up again. I still haven't got round to working out how to replace the fake input key I had setup.

The rest of it you'll just have to go through changing setting back to how you want them.
The panel thing is right click on the panel > Enter edit mode > Set 'floating' to Off

Thanks for the context. I actually tried to read the Plasma 6 release information in a window that popped up, which might have told me that (?) but I accidentally closed it and wasn't sure how to get it back--and then immediately got distracted by unwelcome changes.

That sucks though. A failure to safely migrate user data should be a show-stopping bug for any major release.

Re: Updated to Plasma 6 and have a number of issues, and Wayland won't start

Reply #5 –
Quote from: user0938490 – on
That sucks though. A failure to safely migrate user data should be a show-stopping bug for any major release.
Well I thank you for motivating me to finally setup (again :) ) my simpler shortcuts.
You may find the actual shortcut names are still there. Along with the key combinations. They are just not set up to do anything.
You can find all the old commands that were associated with each shortcut in
~/.config/khotkeysrc
so long as you haven't deleted it.

I've just done the simple ones which are working again.
I'm going to use xdotool to replicate the few fake input shortcuts I had setup before.
I've no clue what KDE's Martin meant by "migrate the dbus command/fake input to shell scripts with a desktop file"? dbus yes. Fake input no.

It's my own fault for not accepting that wayland is wayland better. Where the definition of 'Wayland better" is "shit don't work". But "doesn't matter, just don't do that any more"
 

Re: Updated to Plasma 6 and have a number of issues, and Wayland won't start

Reply #6 –
Quote from: user0938490 – on
That sucks though. A failure to safely migrate user data should be a show-stopping bug for any major release.
This is the most likely reason. You can test it by creating a test account in your Artix (useradd -m test), delete .config and .local in /home/test, logout and login as the test user (lots of tests). You should get a vanilla plasma6.