Bug 1870182 - GNOME Classic fails to load in VM (Software rendering might be the culprit?)
Summary: GNOME Classic fails to load in VM (Software rendering might be the culprit?)
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2020-08-19 13:34 UTC by František Zatloukal
Modified: 2020-08-20 07:13 UTC (History)
10 users (show)

Fixed In Version: gnome-classic-session-3.37.90-2.fc33
Clone Of:
Environment:
Last Closed: 2020-08-20 07:13:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Entire journal log (339.39 KB, text/plain)
2020-08-19 13:34 UTC, František Zatloukal
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-shell issues 3088 0 None None None 2020-08-19 15:32:32 UTC

Description František Zatloukal 2020-08-19 13:34:21 UTC
Created attachment 1711884 [details]
Entire journal log

Description of problem:
When trying to launch GNOME Classic in a VM with virgl without OpenGL acceleration (that should be the GNOME Boxes default), screen stays black.

GNOME and GNOME on Xorg work fine.

Version-Release number of selected component (if applicable):
mutter-3.37.90-1.fc33.x86_64
gnome-shell-3.37.90-1.fc33.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install F33 20200818 into the VM, virgl as Video driver, OpenGL support disabled
2. Choose GNOME Classic

Actual results:
Black Screen.

Expected results:
Classic session should work.

Additional info:

It looks like this might affect all systems with 3D Software rendering, I'll verify that tomorrow.
 
Relevant log lines:
Aug 19 15:24:36 localhost.localdomain org.gnome.Shell.desktop[998]: libEGL warning: DRI2: failed to create dri screen
Aug 19 15:24:36 localhost.localdomain org.gnome.Shell.desktop[998]: libEGL warning: Not allowed to force software rendering when API explicitly selects a hardware device.
Aug 19 15:24:36 localhost.localdomain org.gnome.Shell.desktop[998]: libEGL warning: DRI2: failed to create dri screen
Aug 19 15:24:36 localhost.localdomain gnome-shell[998]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 10.0.0, 256 bits)), falling back to CPU copy path
Aug 19 15:24:36 localhost.localdomain dbus-broker-lau[1032]: Ready
Aug 19 15:24:36 localhost.localdomain org.gnome.Shell.desktop[1040]: libEGL warning: DRI2: failed to create dri screen
Aug 19 15:24:36 localhost.localdomain org.gnome.Shell.desktop[1040]: libEGL warning: Not allowed to force software rendering when API explicitly selects a hardware device.
Aug 19 15:24:36 localhost.localdomain org.gnome.Shell.desktop[1040]: libEGL warning: DRI2: failed to create dri screen
Aug 19 15:24:36 localhost.localdomain org.gnome.Shell.desktop[1040]: glamor: No eglstream capable devices found

Comment 1 Fedora Blocker Bugs Application 2020-08-19 13:37:38 UTC
Proposed as a Blocker for 33-beta by Fedora user frantisekz using the blocker tracking app because:

 GNOME Classic is offered on the login screen and it doesn't work with Software rendering.

Comment 2 Kalev Lember 2020-08-19 17:26:37 UTC
This is possibly because gnome-shell-extensions 3.37.90 update fell between cracks during F33 branching: gnome-shell-extensions-3.37.90-1.fc33 (https://koji.fedoraproject.org/koji/buildinfo?buildID=1588916) only got tagged with f34 and not with f33.

I've kicked off a rebuild; can you see if updating to gnome-classic-session-3.37.90-2.fc33 (https://koji.fedoraproject.org/koji/buildinfo?buildID=1595921) makes things work?

Comment 3 Adam Williamson 2020-08-19 19:23:28 UTC
I'd be -1 blocker on this because we don't intend to block on Classic, at least that's always been my understanding.

Comment 4 František Zatloukal 2020-08-20 06:28:45 UTC
Yes, gnome-classic-session-3.37.90-2.fc33 fixes the issue. Thanks Kalev for rebuild :)

Comment 5 Kalev Lember 2020-08-20 07:13:30 UTC
Great, thanks for checking!


Note You need to log in before you can comment on or make changes to this bug.