Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RingCentral Linux client freezes entire Qubes desktop #5499

Closed
Elijah-C-G opened this issue Dec 2, 2019 · 5 comments
Closed

RingCentral Linux client freezes entire Qubes desktop #5499

Elijah-C-G opened this issue Dec 2, 2019 · 5 comments
Labels
C: other eol-4.0 Closed because Qubes 4.0 has reached end-of-life (EOL) P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@Elijah-C-G
Copy link

Qubes OS version
Qubes 4.0

Affected component(s) or functionality
Dom0 display - the entire desktop

Brief summary
When attempting to share my screen via RingCentral, the desktop locks in to an unresponsive RingCentral window and there is no clear way to regain control.

To Reproduce
Steps to reproduce the behavior:

  1. Install the RingCentral Linux client on to an AppVM, and make sure it is running.
  2. Have another program running in a window on that same AppVM. (The bug doesn't happen if RingCentral is the only running window on that AppVM.)
  3. Start a RingCentral meeting using your account.
  4. Attempt to share your screen.

Expected behavior
RingCentral does not render the entire Qubes desktop inoperable (and ideally also shares its screen for the AppVM)

Actual behavior
The Qubes desktop becomes inoperable, and a reboot is required to regain control of the system

Screenshots
If necessary, I can upload a video showing what happens.

@Elijah-C-G Elijah-C-G added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Dec 2, 2019
@andrewdavidwong andrewdavidwong added this to the Release 4.0 updates milestone Dec 3, 2019
@DemiMarie
Copy link

Zoom screensharing has similar problems.

One of the problems is that override redirect windows are not handled correctly by QubesOS’s GUI services.

@mfc
Copy link
Member

mfc commented May 11, 2020

Zoom screensharing has similar problems.

One of the problems is that override redirect windows are not handled correctly by QubesOS’s GUI services.

you can try what is suggested in this qubes-users thread:

The problem with Zoom is probably that it opens a transparent overlay, likely because of annotations. However, Qubes OS does not support transparency. There is a workaround that hides the overlay:

xdotool selectwindow windowunmap

@strugee
Copy link
Contributor

strugee commented Jul 16, 2020

Shouldn't this be a security bug? I thought an untrusted qube wasn't supposed to be able to DoS the dom0 desktop. I somehow managed to trigger this in Zoom this morning by having a Zoom call open and making a Firefox window in the same qube fullscreen. It broke my entire desktop, even after I quit Zoom, and typing anywhere (like in a terminal to kill the VM) did not work, including trusted shortcuts like Alt-Tab. Clicking buttons in the panel didn't work either.

@andrewdavidwong
Copy link
Member

Shouldn't this be a security bug? I thought an untrusted qube wasn't supposed to be able to DoS the dom0 desktop. I somehow managed to trigger this in Zoom this morning by having a Zoom call open and making a Firefox window in the same qube fullscreen. It broke my entire desktop, even after I quit Zoom, and typing anywhere (like in a terminal to kill the VM) did not work, including trusted shortcuts like Alt-Tab. Clicking buttons in the panel didn't work either.

That's a tough call. For example, XSAs that are DoS-only aren't considered to affect the security of Qubes OS, and we report them as such in the XSA Tracker. So, I'd defer to @marmarek to say whether this qualifies as a security bug.

@andrewdavidwong andrewdavidwong added the eol-4.0 Closed because Qubes 4.0 has reached end-of-life (EOL) label Aug 5, 2023
@github-actions
Copy link

github-actions bot commented Aug 5, 2023

This issue is being closed because:

If anyone believes that this issue should be reopened and reassigned to an active milestone, please leave a brief comment.
(For example, if a bug still affects Qubes OS 4.1, then the comment "Affects 4.1" will suffice.)

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: other eol-4.0 Closed because Qubes 4.0 has reached end-of-life (EOL) P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

5 participants