Bug #15433
Cannot open GNOME Settings menu on some computers since Tails 3.6
100%
Description
Some users with NVIDIA cards are reporting they are unable to open the Applications - System Tools - Settings menu since Tails 3.6.
I cannot reproduce.
Cards:
- 01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)
Subtasks
Related issues
|
Related to Tails - |
Confirmed | 2017-08-31 | |
|
Blocks Tails - |
Resolved | 2017-06-29 | |
|
Blocks Tails - |
Resolved | 2018-03-22 |
History
#1 Updated by intrigeri 2018-03-21 15:49:57
> Some users with NVIDIA cards are reporting they are unable to open the Applications - System Tools - Settings menu since Tails 3.6.
Could you please write down in the description of this ticket the corresponding WhisperBack report IDs, so I can take a look at the logs without having to hunt through my copious backlog? Thanks!
#2 Updated by intrigeri 2018-03-22 11:18:06
Here’s one: b88235ff80e38c431c8c319d692203ba. I see no obvious attempt to start the Settings menu in this forwarded bug report though. Only potentially relevant error in the logs: gnome-settings-[4958]: failed to set screen _ICC_PROFILE: Failed to open file '/home/amnesia/.local/share/icc/edid-e96d9f46bb7b9c0cced8b4b66692e737.icc': Permission denied
#3 Updated by intrigeri 2018-03-22 11:25:47
Another one: 87d41ce19266d364e7b06397ff4c493c.
To reproduce: open the system menu (top right of the screen), click Settings icon.
Symptoms: “screen goes completely black for 1 second, then comes back blue, with a white toolbar in top of the screen; Mouse is round loading icon; Can click in top right of toolbar. Toolbar then shows volume control and a round ’ pause’ button (2 stripes). Clicking ‘pause’ button gives screensaver. Clicking screensaver gets me back to blue screen.; No shutdown button on toolbar.”
It looks exactly as if the screen locker had been triggered. I suspect that user clicked the lock screen icon instead of the settings one.
#4 Updated by intrigeri 2018-03-22 13:33:54
- Subject changed from Cannot open GNOME Settings menu to Cannot open GNOME Settings menu on some computers since Tails 3.6
- Status changed from New to Confirmed
- Assignee deleted (
emmapeel)
intrigeri wrote:
> Another one: 87d41ce19266d364e7b06397ff4c493c.
> […]
> It looks exactly as if the screen locker had been triggered. I suspect that user clicked the lock screen icon instead of the settings one.
… except the user can reproduce this with Applications -> System Tools -> Settings. So I think the GNOME session crashed and they’re back in the GDM session. I’ve asked the OP to do some debugging steps.
#5 Updated by intrigeri 2018-03-22 17:43:20
- Assignee set to intrigeri
- Priority changed from Normal to Elevated
- Target version set to Tails_3.7
- QA Check changed from Info Needed to Dev Needed
- Type of work changed from Research to Code
Mar 22 15:51:07 amnesia gnome-control-center.desktop[9338]: libva info: VA-API version 0.39.4
Mar 22 15:51:07 amnesia gnome-control-center.desktop[9338]: libva info: va_getDriverName() returns -1
Mar 22 15:51:07 amnesia gnome-control-center.desktop[9338]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
Mar 22 15:51:08 amnesia gnome-control-center.desktop[9338]: libva info: VA-API version 0.39.4
Mar 22 15:51:08 amnesia gnome-control-center.desktop[9338]: libva info: va_getDriverName() returns -1
Mar 22 15:51:08 amnesia gnome-control-center.desktop[9338]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
Mar 22 15:51:08 amnesia gnome-control-center.desktop[9338]: libva info: VA-API version 0.39.4
Mar 22 15:51:08 amnesia gnome-control-center.desktop[9338]: libva info: va_getDriverName() returns 0
Mar 22 15:51:08 amnesia gnome-control-center.desktop[9338]: libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
Mar 22 15:51:08 amnesia gnome-control-center.desktop[9338]: libva info: va_openDriver() returns -1
Mar 22 15:51:08 amnesia gnome-control-center.desktop[9338]: libva info: VA-API version 0.39.4
Mar 22 15:51:08 amnesia /usr/lib/gdm3/gdm-x-session[5300]: Xorg: ../../../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
Mar 22 15:51:08 amnesia gnome-control-center.desktop[9338]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
Mar 22 15:51:08 amnesia gnome-control-center.desktop[9338]: after 11 requests (11 known processed) with 0 events remaining.The OP cannot reprodocue this after deinstalling va-driver-all i965-va-driver mesa-va-drivers gstreamer1.0-vaapi so I think that’s a regression caused by Feature #14580. Too bad nobody noticed that in 3.6~rc1 :/
#6 Updated by intrigeri 2018-03-22 17:43:37
- blocks
Feature #13245: Core work 2018Q1: Foundations Team added
#7 Updated by intrigeri 2018-03-22 17:44:15
- related to
Feature #14580: Support Video Acceleration API (VA-API) added
#8 Updated by intrigeri 2018-03-22 17:53:59
- Status changed from Confirmed to In Progress
- Assignee changed from intrigeri to anonym
- % Done changed from 0 to 50
- QA Check changed from Dev Needed to Ready for QA
- Feature Branch set to bugfix/15433-GNOME-settings-vs-VA-API
Documented the known issue + workaround on master, reverted that on the topic branch.
#9 Updated by intrigeri 2018-03-23 05:31:45
- blocks
Bug #15449: Intel VAAPI: Playing video with Totem freezes the system added
#10 Updated by intrigeri 2018-03-27 10:14:52
- Target version changed from Tails_3.7 to Tails_3.6.2
#11 Updated by anonym 2018-03-29 10:04:44
- Status changed from In Progress to Fix committed
- Assignee deleted (
anonym) - % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
#12 Updated by anonym 2018-03-30 16:59:49
- Status changed from Fix committed to Resolved