Testing Plasma 6 (Beta) on Endeavour OS - is this approach any good?

Just ran yay. Went without a hitch. Hurray. Some people have done a tremendous job.

I’ll do some proper testing coming weekend.

Perhaps you could have a look here:
https://bugs.kde.org/show_bug.cgi?id=477478
where I reported previews not showing up on my setup.

Nate, over at KDE, asks if I have kpipewire installed. I’m unsure how to check if a package is installed.

I did:

yay -Q | grep 'pipe'

and got:

gst-plugin-pipewire 1:1.0.0-1
kpipewire 5.90.0-1
libpipeline 1.5.7-1
libpipewire 1:1.0.0-1
pipewire 1:1.0.0-1
pipewire-alsa 1:1.0.0-1
pipewire-audio 1:1.0.0-1
pipewire-jack 1:1.0.0-1
pipewire-pulse 1:1.0.0-1

If I do yay kpipewire I get:

3 aur/kpipewire-git 5.28.80_r205.g67f8d36-1 (+1 0.00) 
    KDE Plasma Kpipewire
2 extra/kpipewire 5.27.9-1 (85.1 KiB 286.7 KiB) [plasma] (Installed: 5.90.0-1)
    Components relating to pipewire use in Plasma
1 kde-unstable/kpipewire 5.90.0-1 (125.3 KiB 424.9 KiB) [plasma] (Installed)
    Components relating to pipewire use in Plasma

Does that mean I have the packages Nate is inquiring about installed?

Just noticed that, on log in, the SDDM-screen is partly in the “locale” language and partly (day, month etc) in English. Will have a better look next time I boot.

Edit: Yup: day, month etc is in English. Text for “restart”, "sleep¨, “shutdown” etc is in the “locale” language.

I’ll look at my Plasma 5 setup to see if it’s the same there.

Yes, it’s this one: kde-unstable/kpipewire 5.90.0-1

Done. If you still can’t screenrecord at all - which works here - there seems something different wrong. I don’t want to jump in with vaguely similar symptoms derailing the issue for now.

Thanks.

Indeed, we mustn’t derail or obscure the issue.

I’m sure I’ll have some more time for further testing this weekend.

Perhaps of interest:

Hah, I rather like Niccolo’s videos, though I’m not a video person much, I prefer to read being able to do that at least 3x faster than watching someone talk.
I also feel terribly old, because these two look like teenagers to me (and I know they’re not, though maybe not too far beyond it). :slight_smile:

Same here.

It’s not me getting older, it’s the people around me getting younger.

Having updated my setup this morning, I will do some re-tests.

First: crashing “edit mode” of the panel.

Just changed the panel several times: position, width, float, transparency, height - no crashes whatsoever.

I’ll mark my bug report as solved.

Am gradually getting this Plasma 6 setup configured as I have setup my Plasma5 setup.

  • VPN (wireguard) connection set up.
  • regularly changing wallpapers
  • installed my preferred distraction-free text editor, password manager.

No problems getting this things installed so far.

Next step: install the network printer.

Nate Graham contacted me. He states:

“Sounds like there are packaging conflicts. You should only have one version of KPipeWire installed. If you’re using the Plasma 6 beta, the correct version is the 5.90 one.”

I wonder… Did I miss a step when upgrading/updating to Plasma 6, that may have caused me to have two KPipewires installed?
How can I check for more conflicting packages?

Edit: yay does not report any conflicts when I use it to update…

According to your output there’s only one version installed. Graham is probably not familiar with Arch.

If you query the local packages e.g. with yay -Qs kpipewire it will show the 5.90 version only.

True:

local/kpipewire 5.90.0-1 (plasma)
    Components relating to pipewire use in Plasma

Thanks!

Edit: clarified the info for Graham and asked what I can do to provide more info.

In the meantime: my Plasma 6 desktop starts to boringly look like my Plasma 5 desktop:

6 Likes

Speaking of Spectacle jpeg screenshots don’t work here and only create an empty file.

Hmmm, making screenshots with spectacle works well at my end; I tried .png and .jpeg. Both get saved. Though, jpeg in a different folder from png (weird, I think; I’ll have a look at the settings).

When I reported the “previews don’t show”-bug, Nate saw reason to ask if spectacle was also not working; he specifically asked about screenrecordings though.
I just tried making a screen recording twice again:
First time spectacle crashed, second time spectacle hung/stalled and needed to be forcefully shut down.

I’ll try some more scenario’s and see if I can get back traces.

Thanks for checking the jpeg screenshot.

While testing I noticed that spectacle gives some more information when started from the command line. Maybe something for you there. Also always worth watching the journal log during the failing operation.

I made a screenshot this morning…it worked fine.

Thank you for the suggestion.

I’ll check it out later today.

[Screenshots not working] For whatever reason - maybe the update, maybe not - my mime-associations got messed up. Who knows. This existing bug gave the hint what’s wrong.