Trying to run KDE 6 Plasma with Wayland....

Does anyone have reports if the bumped Plasma/Frameworks versions (as shown in the screenie) fixed the current sore spots (screenies and plasmashell) ?
1731439321826.png

Not sure I want to spend a week compiling/downloading the up-to-date stuff to find out, the hardware I have easily available to me at the moment is pretty slow.
 
In post #456, I said that the crash was caused by a libc++ bug. It's not a bug in plasmashell, but it causes plasmashell to crash. The fix for the bug hasn't been added to the kde-it_goes_to_6 branch. But in the meantime, someone could try to recompile a port or ports using libstdc++, though I have no idea what specific port or ports need to be recompiled if the goal is to prevent triggering that bug.
 
Yeah, and after that libc++ bug is fixed, LLVM/Clang needs to be recompiled with a specific flag, then the FreeBSD kernel! (I noted the relevant bug in post #467).

And LLVM is on 19.1 series RN, as per llvm.org

Dunno who's gonna do the heavy lifting of making sure such details line up... But yeah, that's what it'll take to achieve the stable KDE 6 on Wayland on FreeBSD dream.

😩
 
astyle said:
Yeah, and after that libc++ bug is fixed, LLVM/Clang needs to be recompiled with a specific flag, then the FreeBSD kernel! (I noted the relevant bug in post #467).

And LLVM is on 19.1 series RN, as per llvm.org

Dunno who's gonna do the heavy lifting of making sure such details line up... But yeah, that's what it'll take to achieve the stable KDE 6 on Wayland on FreeBSD dream.

😩
Click to expand...

I don't think the bug mentioned in post #467 has anything to do with the xdg_popup bug occurring in the plasma wayland environment.
 
astyle said:
Code: 
 Operating System: FreeBSD 14.1
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.3
Kernel Version: 14.1-RELEASE-p5 (64-bit)
Graphics Platform: Wayland
Memory: 7.9 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 3000
Click to expand...
Code: 
Operating System: FreeBSD 15
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.7.
Qt Version: 6.7.3
Kernel Version: 15-CURRENT (64-bit)
Graphics Platform: Wayland
Memory: 7.9 GiB of RAM
Graphics Processor: llvmpipe

plasmashell no longer works, gives errors that some avx512fe is not a valid option. And Spectacle crashes with same error. And the right-click crash of plasmashell still persists 😭

BTW, Spectacle now depends on OpenCV, so it's a pain to compile. If I turn on all of the Makefile knobs for OpenCV, that's an additional 2 days of compiling!

The only improvement after 5 days of compiling on an i5 2467M: The clock widget is finally there. Was THAT worth spending 5 days for? :rolleyes: My personal answer is no, that was not worth spending 5 days on.

Worst part is, this all works perfect on Xorg, it can see my GPU (Mesa Intel HD 3000) no problem! 😩 And it doesn't crash.
 
Code: 
Operating System: FreeBSD 14
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.7
Qt Version: 6.7.3
Kernel Version: 14.1-RELEASE-p5 (64-bit)
Graphics Platform: Wayland
Memory: 7.9 GiB of RAM
Graphics Processor: llvmpipe

Now it complains about pipewire not being started. Worst part is, I have it installed, along with multimedia/wireplumber. And sometimes, it reports that it can actually properly see my GPU (Mesa Intel® HD Graphics 3000), but I can't seem to reproduce the exact conditions.

I also lost the clock widget from previous compilation attempt. And the right-click crash issue is still there, but the fix (Super + W, then run plasmashell) still doesn't work...

Spectacle complains about lack of Pipewire context, too... so it looks like we're getting somewhere, and whittling it down to a usable Pipewire installation.

Late edit: A workaround that I did find: Have Konsole installed, and have an extra tab open in it. Use that tab to run plasmashell as regular user. This will still produce complaints about being unable to connect to PipeWire, but at least it's the exact same text that I see on launch of KDE...

If anyone has any ideas how to fight these fires, please post here!
 
Well, well...

The more I play with KDE 6 on Wayland, the more I'm convinced that this is a Pipewire issue.

To start: I got Spectacle to partially work. The trick seems to be installing VA-API stuff:
I needed the Intel stuff because I have Intel hardware:
1733114567677.png

Unfortunately, I can only take 'Window Under Cursor' screenshots, I can't do 'Rectangular Region' or 'Full Screen'.

Also, as regular user, I have to start Pipewire by hand, and verify it with wpctl status (wpctl is provided by WirePlumber).

Konsole works fine, and its tabs feature comes in pretty handy for this:
1733115424798.png

The clock widget becomes available once I set the time zone correctly in the relevant KDE Control Module:
1733115660860.png

All of these screenies were taken under a full KDE 6 on Wayland on metal session... And oh, yeah, kdesu(1) works properly for a change. I compiled it with su rather than sudo/doas.
 
I was able to get rid of the right-clicking bug after adding CXXFLAGS+= -D_LIBCPP_TYPEINFO_COMPARISON_IMPLEMENTATION=2 to /etc/make.conf, then rebuilding freebsd base, and then rebuilding all ports.
 
Wow, now Spectacle screenshots and properly working PipeWire look like the only real showstoppers towards the dream of KDE 6 on Wayland on metal!
 
hi mate

i did get KDE 6 Wayland working in a jail
and i found the following commands worked to start pipewire

Code: 
pipewire -v &
wireplumber &
exec dbus-launch --exit-with-session ck-launch-session startplasma-wayland

pipewire-spa-oss isnt in quarterly
so you would have to build it from ports

i havent tried it so cant comment on the audio quality

tulilirockz

Thread 'Pipewire + pipewire-pulse as main audio server'

Pipewire is a really solid technology and I've been using it for a while on Linux, works great for routing, works great for pretty much everything. I've since tried out FreeBSD on a dual boot partition and I noticed that you guys do not use it! - using, instead, either OSS, Sndio, or something else. In order to get screencasting support on Niri, the wayland compositor i'm using, it requires pipewire to be running on the background (and the GNOME xdg-portal, too). I just thought that like, if I already have pipewire running, why not just use it instead of sndio? Would that be possible? I've...

FreshPorts -- audio/pipewire-spa-oss: PipeWire SPA plugin implementing a FreeBSD OSS backend

PipeWire module implementing an OSS backend.
www.freshports.org www.freshports.org
 
NapoleonWils0n said:
hi mate

i did get KDE 6 Wayland working in a jail
and i found the following commands worked to start pipewire

Code: 
pipewire -v &
wireplumber &
exec dbus-launch --exit-with-session ck-launch-session startplasma-wayland

pipewire-spa-oss isnt in quarterly
so you would have to build it from ports

i havent tried it so cant comment on the audio quality

tulilirockz

Thread 'Pipewire + pipewire-pulse as main audio server'

Pipewire is a really solid technology and I've been using it for a while on Linux, works great for routing, works great for pretty much everything. I've since tried out FreeBSD on a dual boot partition and I noticed that you guys do not use it! - using, instead, either OSS, Sndio, or something else. In order to get screencasting support on Niri, the wayland compositor i'm using, it requires pipewire to be running on the background (and the GNOME xdg-portal, too). I just thought that like, if I already have pipewire running, why not just use it instead of sndio? Would that be possible? I've...

FreshPorts -- audio/pipewire-spa-oss: PipeWire SPA plugin implementing a FreeBSD OSS backend

PipeWire module implementing an OSS backend.
www.freshports.org www.freshports.org
Click to expand...


Pipewire under control, somewhat. When logging in, wpctl shows video streams (see end of wpctl_status.txt). But launch anything at all on KDE 6 Wayland, and those video streams just disappear. And just restarting Pipewire doesn't seem to help, there's errors from that launch, and good luck trying to trace down where they're even coming from. To top it off, the original pipewire process seems to be getting killed so it doesn't show up when I run ps -ax | grep pipewire either as myself or root.

Screenshot quirks remain.

When using 'Window Under Cursor' button (as per Oleg_NYC 's suggestion earlier in this thread, I discovered that the bare desktop and taskbar somehow qualify as 'Window Under Cursor', but I still can't take a full screen dump with Spectacle. And all other screenshot tools are still based on grim and slurp, which are known to not work KDE 6 Wayland.
1733253126956.png

This ^ was taken with Spectacle!


And there's still some weird behavior that seems difficult to control. Sometimes I can click a button, sometimes not.
 

Attachments

It's interesting that recording with spectacle works (all three of its recording options work). Taking a Window Under Cursor screenshot works too. But Rectangular Region, Full Screen, and Active Window Screenshots can't be made.
 
meaw229a said:
I was able to make it work. KDE 5 and Wayland. However I was not able to get a higher screen resolution than 1024 x 768?
My monitor is 2k 2560 x 1440 max resolution. After lots of trial I gave up.
That said in the little 1024 x 768 low resolution window it was running nice and promising.
Click to expand...
I too get a fixed screen resolution of 1024x768 in wayland, with both plasma5-plasma and plasma6-plasma. Is there a way to enable other screen resolutions?; though i have not managed to go through all posts here, a forum search found only a handful of posts on screen resolution and I could not find a solution in them.
 
drr said:
I too get a fixed screen resolution of 1024x768 in wayland, with both plasma5-plasma and plasma6-plasma. Is there a way to enable other screen resolutions?; though i have not managed to go through all posts here, a forum search found only a handful of posts on screen resolution and I could not find a solution in them.
Click to expand...
hey, does Spectacle work properly under plasma5-plasma with Wayland specifically?
 
astyle said:
hey, does Spectacle work properly under plasma5-plasma with Wayland specifically?
Click to expand...
No, spectacle does not work for me in wayland under plasma5-plasma. Clicking the icon does nothing. Running it from konsole gives the following error.
Code: 
Remember requesting the interface on your desktop file: X-KDE-Wayland-Interfaces=zkde_screencast_unstable_v1
Screenshot request failed: "The process is not authorized to take a screenshot"
 

446628 – Spectacle : Screenshot request failed: "The process is not authorized to take a screenshot"

bugs.kde.org bugs.kde.org

forums.opensuse.org

Spectacle: Screenshot request failed: "The process is not authorized to take a screenshot"

Hi, Updated to latest TW snapshot 20240523 this morning and Spectacle no longer works (it worked perfectly fine last week on an older snapshot). Plasma version 6.0.4, on Wayland. No Spectacle window appears and no screenshot is taken when I start Spectacle using the print screen key or from...
forums.opensuse.org forums.opensuse.org
 
Oleg_NYC said:
In the x11 environment, spectacle would produce exactly the same errors when attempting to take screenshots unless it was started with the command dbus-run-session spectacle.
Click to expand...
I get the above error when running plasma with exec dbus-launch --exit-with-x11 ck-launch-session startplasma-wayland in my .xinitrc .
 
You must log in or register to reply here.
Back
Top