[plasmashell] [Bug 481058] Recording windows or screens with OBS or spectacle is broken in Plasma 6 RC2 on Wayland: Failed to start pipewire screencast
https://bugs.kde.org/show_bug.cgi?id=481058 --- Comment #13 from Melechtna Antelecht --- (In reply to Zane from comment #12) > (In reply to Melechtna Antelecht from comment #9) > > > > Is there anything specific that happens when you relog? I can't even get it > > to work again once after it gets "on its shit" without a full config flush > > since I can't seem to isolate which one causes this weirdness. > > I've found that when I relog, some processes (specifically the user dbus > daemon, and pipewire) have persisted from the previous session. It's quite > annoying tbh (even happens in Plasma 5). > To work around this, after logging out I always enter a tty, "pkill -u > $USER" everything, verify everything's dead, and only _then_ log back in. > > I suspect the core of this issue is caused by some dbus-related state going > wonky somehere, in which case killing dbus temporarily solves it. I'd agree, except, the issue occurs for me from first login (cold boot), until I relog (sometimes multiple are needed). So it can't be that, at least not in my case. Unless somehow these persist between reboots, and somehow I don't think so. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481058] Recording windows or screens with OBS or spectacle is broken in Plasma 6 RC2 on Wayland: Failed to start pipewire screencast
https://bugs.kde.org/show_bug.cgi?id=481058 --- Comment #11 from Melechtna Antelecht --- (In reply to Guido Winkelmann from comment #10) > I can't see why this bug has been marked as solved and "not a bug". It's > clearly still a bug, it's clearly a regression a from 5.27, and it's clearly > not caused just by pipewire not actually running, since all reporters so far > could confirm that, yes, pipewire is really running the whole time and > reachable from various other pipewire frontends. > > From my point of view, this is even a rather major bug. It's also not just a genroo thing, I for one am using Fedora, but had similar issues on Arch, which is SystemD, so it's not openrc related either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481058] Recording windows or screens with OBS or spectacle is broken in Plasma 6 RC2 on Wayland: Failed to start pipewire screencast
https://bugs.kde.org/show_bug.cgi?id=481058 --- Comment #9 from Melechtna Antelecht --- (In reply to Zane from comment #8) > I think there may be two separate issues being discussed here. > > I'm seeing the same "[pipewire] Failed to start screencast, denied or > cancelled by user" issue, and I'm using systemd. > Pipewire is running the entire time, qpwgraph works, my music keeps playing. > Logging in and out again fixes it for one run. If I exit OBS and then reopen > it, the behaviour reproduces. > > All of this was working on 5.27.10, so I suggest we reopen this. Is there anything specific that happens when you relog? I can't even get it to work again once after it gets "on its shit" without a full config flush since I can't seem to isolate which one causes this weirdness. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481058] Recording windows or screens with OBS or spectacle is broken in Plasma 6 RC2 on Wayland: Failed to start pipewire screencast
https://bugs.kde.org/show_bug.cgi?id=481058 --- Comment #6 from Melechtna Antelecht --- https://pastebin.com/L9BSVK9H Here's an strace for OBS, I'm completely out of ideas. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481058] Recording windows or screens with OBS or spectacle is broken in Plasma 6 RC2 on Wayland: Failed to start pipewire screencast
https://bugs.kde.org/show_bug.cgi?id=481058 Melechtna Antelecht changed: What|Removed |Added CC||melech...@gmail.com --- Comment #4 from Melechtna Antelecht --- Yesterday, I created a new user account, and screen sharing worked there. So I completely nuked my settings for everything not vital (saves, browser history, etc.), and this got screen sharing working on my main account. Tested a live stream, all good. Wake up the next day, login, and it's back to being broken with this error in everything [pipewire] Failed to start screencast, denied or cancelled by user Meaning, it's likely broken by a config change after one user login, perhaps on the next session after using screen share of any kind. I'd be fine with wiping said config at login for now, but I have absolutely no idea which one is relavent. I have so far tried deleting the xdg config, and the entire pipewire config folder and relogging, and these didn't work to clear the issue for even one session, but doing a mass wipe did, so it would likely be a good idea to hunt down which config is creating the problem so this issue can be resolved. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 434403] Plasma on Wayland didn't start with a systemd error "user@1000.service: Failed to attach to cgroup /user.slice/user-1000.slice/user@1000.service: Device or resource busy" afte
https://bugs.kde.org/show_bug.cgi?id=434403
Melechtna Antelecht changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
CC||melech...@gmail.com
--- Comment #2 from Melechtna Antelecht ---
I can confirm that this issue very much stems from
plasma-dbus-run-session-if-needed seeming to have no idea of the dbus session
is needed. The best solution I've been able to come too, and I'm apparently not
the only one,
https://bugzilla.redhat.com/show_bug.cgi?id=1897717
Is to modify the plasmawayland.desktop in /usr/share/wayland-sessions/ to
simply throw out the detector script and just run dbus-run-session instead,
then plasma starts normally. So clearly whatever this is doing
drs=
if [ -z "${DBUS_SESSION_BUS_ADDRESS}" ]
then
drs=dbus-run-session
fi
exec ${drs} "$@"
Doesn't do its job.
--
You are receiving this mail because:
You are watching all bug changes.
