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

Fedora RPM RStudio broken under Gnome/Xorg #7217

Closed
1 task
rsbivand opened this issue Jun 25, 2020 · 12 comments
Closed
1 task

Fedora RPM RStudio broken under Gnome/Xorg #7217

rsbivand opened this issue Jun 25, 2020 · 12 comments

Comments

@rsbivand
Copy link

@rsbivand rsbivand commented Jun 25, 2020

System details

RStudio Edition : Desktop
RStudio Version : 1.3.959
OS Version      : Fedora 32 under Xorg
R Version       : 4.0.2

See: https://community.rstudio.com/t/fedora-rpm-rstudio-broken-under-gnome-xorg/70806

The published RPM (https://download1.rstudio.org/desktop/centos8/x86_64/rstudio-1.3.959-x86_64.rpm) works under Gnome/Wayland on Fedora 31/32, but freezes non-reproducibly when Gnome is set to use Xorg not Wayland.

Why does this matter? Because Teams does not (yet) permit screen sharing under Wayland, but does under Xorg. However, since the RStudio IDE freezes under Gnome/Xorg (set the Fedora login to Xorg rather than Wayland - https://docs.fedoraproject.org/en-US/quick-docs/configuring-xorg-as-default-gnome-session/) unpredictably, it cannot be used for screen sharing through Teams. I'd be grateful for tips other than switching to Windows 10 after duplicating my whole teaching environment there.

Re-checking with the crash-handler on, the entries are empty, with:

$ od -b ~/.r/crashpad_database/settings.dat
0000000 163 144 120 103 001 000 000 000 001 000 000 000 000 000 000 000
0000020 000 000 000 000 000 000 000 000 322 326 133 036 153 121 272 113
0000040 207 220 222 164 031 027 372 014
0000050

Typically, the whole RStudio window goes blank apart from the top menu line, is unresponsive, and has to be killed, for example from the system monitor. To check the running session interface, use e.g.:

loginctl show-session 2 -p Type

Not a crash, a freeze, with no apparent activity from the crash handler (see above).

  • [ x] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
@ronblum
Copy link
Contributor

@ronblum ronblum commented Jun 25, 2020

@rsbivand Thank you for raising the issue! I'll mark it as a bug to review.

@rsbivand
Copy link
Author

@rsbivand rsbivand commented Jun 25, 2020

@ronblum Thanks. I realise that Gnome and QT5 are only distant relatives, and that this isn't RStudio's fault really (Teams should have reached Wayland capability for screen sharing). Any help would be welcome!

@chrisvwn
Copy link

@chrisvwn chrisvwn commented Jun 30, 2020

I actually have this same problem while using Wayland on Fedora 32. I also cannot reproduce it. It happens randomly - so far has happened as I click on unremarkable code in the editor.

RStudio Edition : Desktop
RStudio Version : 1.3.959
OS Version      : Fedora 32 (Workstation Edition) under wayland
R Version       : 3.6.3

I thought I would add a screenshot of the screen. The menus will open but all actions are non-functional. You have to kill the process.

Screenshot from 2020-06-30 12-06-50

@rsbivand
Copy link
Author

@rsbivand rsbivand commented Jul 5, 2020

@chrisvwn - yes, I see this too, unfortunately. But it less problematic than Xorg just not working. It looks as though more work is needed urgently on Wayland and Xorg for Fedora 32. Trying to help by building from source doesn't work either, as source builds fail for me immediately on F32.

@gtritchie
Copy link
Member

@gtritchie gtritchie commented Jul 5, 2020

Can you try the latest preview build from https://rstudio.com/products/rstudio/download/preview/ just to see if it behaves any differently?

@rsbivand
Copy link
Author

@rsbivand rsbivand commented Jul 5, 2020

@gtritchie
Copy link
Member

@gtritchie gtritchie commented Jul 5, 2020

Nothing specifically changed for this issue, just a minor Qt update but it did fix an issue related to new glibc on various recent distros that was leading to blank UI as described here so curious if it helps.

@rsbivand
Copy link
Author

@rsbivand rsbivand commented Jul 6, 2020

With preview 1.3.1054 no blank UI (yet) on Xorg, which was more sensitive. Have mostly run knit of existing files, but will try editing during the day.

@chrisvwn
Copy link

@chrisvwn chrisvwn commented Jul 6, 2020

@rsbivand Noted. Indeed it seems less severe with Wayland.

I will also try the preview and let you know if the problem recurs.

@gtritchie
Copy link
Member

@gtritchie gtritchie commented Jul 7, 2020

If this proves to have solved the issue, then this will be a duplicate of #6379. Leaving open for a bit longer, let me know how it is going (@rsbivand and @chrisvwn).

@chrisvwn
Copy link

@chrisvwn chrisvwn commented Jul 7, 2020

@rsbivand So far so good. I haven't encountered a repeat of the problem yet.

@gtritchie
Copy link
Member

@gtritchie gtritchie commented Jul 7, 2020

Great, I'm going to resolve this as a duplicate. Let me know if it reoccurs and I will reopen.

Duplicate of #6379

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants