Summary: | Plasma crashed in ScreencastingPrivate::ScreencastingPrivate() after hovering taskmanager app icon | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Jakob Petsovits <jpetso> |
Component: | Task Manager and Icons-Only Task Manager | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | crash | CC: | ahiemstra, kde, nate, qydwhotmail |
Priority: | NOR | Keywords: | drkonqi, qt6 |
Version: | master | ||
Target Milestone: | 1.0 | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Jakob Petsovits
2023-12-12 05:43:09 UTC
Is that running against a self compiled kwin? It means it doesnt see that screencast interface which is expected if the prefixes both are running in don't match (system kwin and self build plasmashell) (In reply to David Redondo from comment #1) > Is that running against a self compiled kwin? It means it doesnt see that > screencast interface which is expected if the prefixes both are running in > don't match (system kwin and self build plasmashell) Yes, kwin is built with kdesrc-build (kf6-qt6 branch group) together with the rest of workspace. Info Center / Window Manager reports "KWin version: 5.90.90", "Operation Mode: Xwayland". I pasted the full KWin info text to https://invent.kde.org/-/snippets/2937. I also posted https://discuss.kde.org/t/missing-something-auth-related-in-my-plasma-6-setup-what-is-it/8685 in the hope that someone might have an idea what might be going wrong with my setup more generally. Happy to close this bug if the consensus is that Plasma doesn't mind a crash-level hard dependency on KWin-specific Wayland extensions, in which case the issue seems to be purely on my end. What kind of GPU does this system have? (In reply to Nate Graham from comment #3) > What kind of GPU does this system have? I pasted some KWin info into https://invent.kde.org/-/snippets/2937 a while ago. The GPU is a "Mesa Intel(R) UHD Graphics 620 (WHL GT2)". (In reply to David Redondo from comment #1) > Is that running against a self compiled kwin? It means it doesnt see that > screencast interface which is expected if the prefixes both are running in > don't match (system kwin and self build plasmashell) Indeed Info Center shows that the zkde_screencast_unstable_v1 interface isn't listed (Wayland info added to https://invent.kde.org/-/snippets/2937). But what exactly do you mean by "prefixes don't match"? I used standard install-sessions.sh to add a new SDDM session type, and I would have assumed that it sets the environment variables such that the self-compiled KWin gets preferred over the system-wide one. What is supposed to happen in a correct dev session and where can it fail? It's referring to the installation prefix. System installed things will be using `/usr` as prefix while self-built will be something like `$HOME/kde/usr` or similar. What the `install-sessions.sh` script does is purely copy a session configuration file from the self-built prefix to the system prefix, but that session configuration file will point at the self-built prefix. If you then run that session and launch software that is system-installed it will fail the KWin prefix check as the system software's prefix is `/usr` while KWin's prefix is `$HOME/kde/usr`. (In reply to Arjen Hiemstra from comment #6) > What the `install-sessions.sh` script does is > purely copy a session configuration file from the self-built prefix to the > system prefix, but that session configuration file will point at the > self-built prefix. If you then run that session and launch software that is > system-installed it will fail the KWin prefix check as the system software's > prefix is `/usr` while KWin's prefix is `$HOME/kde/usr`. Thanks Arjen. I've understood the overall idea of install-sessions.sh. What I don't quite understand, though, is how KWin in Info Center identifies itself as the one I built (5.91.90) and e.g. querying D-Bus for the process that provides org.kde.kglobalaccel [1] shows that my self-built $HOME/build/kde6/prefix/bin/kwin_wayland is in charge of that interface. The old Plasma 5 kwin binary doesn't even show up in `ps aux`. So the correct KWin seems to be running, but still lacks support for e.g. zkde_screencast_unstable_v1 (and apparently also the screenshot extension for Spectacle). Could there be something wrong with plugin paths perhaps? Or how else would the right KWin leave out important Wayland protocols? [1] qdbus org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID org.kde.kglobalaccel (courtesy of another bug report) Since this seems like it's a local configuration issue, let's close it and either continue the discussion elsewhere, or else in here with the bug report closed (since it's not a user-facing bug). |