https://bugs.kde.org/show_bug.cgi?id=524029
Bug ID: 524029
Summary: XWaylandVideoBridge fullscreen window causes GNOME
panel to disappear and prevents mouse selection of
application windows
Classification: Applications
Product: xwaylandvideobridge
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
# XWaylandVideoBridge fullscreen window causes GNOME panel to disappear
## Environment
Fedora Linux 43
GNOME Shell 49.8
Mutter 49.7
Wayland session
XWaylandVideoBridge installed and automatically started
Graphics hardware:
* Intel UHD Graphics 630 — drives both monitors via DisplayPort
* NVIDIA RTX 3060 also installed, but no displays are connected to it
* BenQ GW2780 — 1920x1080 @ 60 Hz
* Dell P2210 — 1680x1050 @ 59.88 Hz
The problem occurs in an extended dual-monitor configuration.
## Problem
Intermittently, the GNOME top panel/status bar disappears on the primary
display on workspace 1 and mouse selection of visible application windows is
broken. Windows can be activated using the Super key.
The panel reappears while GNOME Overview is displayed by pressing the Super
key. Other workspaces display the panel normally. Returning to workspace 1
causes the panel to disappear again.
Moving all application windows from workspace 1 to another workspace does not
restore the panel.
No relevant GNOME Shell/Mutter errors appear in the user journal.
## GNOME Looking Glass investigation
While the problem was occurring, GNOME Looking Glass showed:
```
Main.panel.visible
true
```
but:
```
Main.layoutManager.panelBox.visible
false
```
Manually executing:
```
Main.layoutManager.panelBox.show()
```
immediately made the GNOME top panel visible again.
Checking Mutter's fullscreen state showed:
```
global.display.get_monitor_in_fullscreen(0)
true
```
and:
```
global.display.get_monitor_in_fullscreen(1)
false
```
There was no normal application intentionally running fullscreen on monitor 0.
Looking Glass's Windows view showed:
```
Wayland to X Recording bridge
```
with WM class:
```
xwaylandvideobridge
```
and its window property:
```
fullscreen = true
```
Thus Mutter considered the XWaylandVideoBridge window to be a fullscreen window
on monitor 0.
## Confirmation
>From a terminal I killed XWaylandVideoBridge.
Killing `xwaylandvideobridge` immediately caused the GNOME top panel to return
to normal operation.
I then disabled XWaylandVideoBridge's automatic startup by creating a per-user
autostart override:
```
~/.config/autostart/org.kde.xwaylandvideobridge.desktop
```
with:
```
Hidden=true
```
After logging out and back in, the problem has not recurred.
## Possibly related symptom
Before identifying XWaylandVideoBridge, I was also experiencing an intermittent
input problem on the BenQ display.
Existing application windows on that display would sometimes stop responding to
mouse clicks in their client areas. Mouse movement continued to work, title
bars could still be dragged, and newly created windows could receive mouse
clicks normally. Windows could be selected using the super key.
The problem:
* did not follow the DisplayPort cable
* did not follow the Intel DisplayPort connector
* did not change when the monitors' logical positions were reversed
* occurred with GNOME extensions disabled
* disappeared when the displays were mirrored
`wev` confirmed that newly created Wayland surfaces on the affected monitor
received normal pointer button press/release events.
Since disabling XWaylandVideoBridge autostart, this mouse-input problem has
also not recurred.
## Expected behavior
XWaylandVideoBridge should not leave a fullscreen window that causes Mutter to
report:
```
global.display.get_monitor_in_fullscreen(0) == true
```
when no screen-sharing operation requiring such a fullscreen surface is active.
It should not cause GNOME Shell to hide its panel.
## Actual behavior
XWaylandVideoBridge creates or leaves a window named:
```
Wayland to X Recording bridge
```
which Mutter sees as fullscreen on monitor 0.
GNOME Shell consequently hides `Main.layoutManager.panelBox`.
Terminating XWaylandVideoBridge immediately restores normal GNOME panel
behavior.
## Workaround
Disable XWaylandVideoBridge autostart using a per-user autostart override
containing:
```
Hidden=true
```
After doing this and logging out/in, GNOME has operated normally.
--
You are receiving this mail because:
You are watching all bug changes.
