https://bugs.kde.org/show_bug.cgi?id=489777

            Bug ID: 489777
           Summary: Unable to see xwaylandbridge since specific commit on
                    repo
    Classification: Applications
           Product: XWaylandVideoBridge
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: plasma-b...@kde.org
          Reporter: k...@timkwakman.eu
                CC: aleix...@kde.org, k...@davidedmundson.co.uk
  Target Milestone: ---

Created attachment 171403
  --> https://bugs.kde.org/attachment.cgi?id=171403&action=edit
Left: Latest version (not showing up), right: old version before the commit
mentioned

***
The latest build from cdn.kde.org (date: 2024-06-26) no longer shows up in
Discord as an application. 

The issue appears to be happening since this commit:
https://invent.kde.org/system/xwaylandvideobridge/-/commit/9d7e44433f6bc62bb2bcc58f56774fe8d54ba841

I build a version from the commit right before it, and it started working again
perfectly. 
***

SUMMARY


STEPS TO REPRODUCE
1. Install the latest version (2024-06-26 as of today)
2. Start it
3. Open/Install Discord
4. Launch xwaylandbridge (flatpak run org.kde.xwaylandvideobridge)
5. Join a Discord server voice channel and try to share the application

OBSERVED RESULT
The xwayland application does not show up

EXPECTED RESULT
The application should show up

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 24.04
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Discord made a change where they are running on wayland now, trying to
screenshare will open their selector and spam the OS prompt but it will never
actually work. To work around that add the following variable (using flatsail
or something like that) when using Discord as a flatpak: XDG_SESSION_TYPE=x11

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to