installing and removing snaps triggers display failures

Bug #1841971 reported by Chris Patterson
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
snapd
High
Unassigned

Bug Description

Hardware: Thinkpad 490s with Thinkpad USB-C Gen 2 Dock with connected displays

Upon installing/removing snaps, snapd will execute udevadm trigger --subsystem-nomatch=input.

Indirectly, I believe this causes the `drm` subsystem to be triggered which, in my case, results in my USB-C dock connected displays to be reset, and often not restored. Unplugging and replugging the dock doesn't always work (probably outside of the scope of snapd).

I assume the the trigger of drm subsystem shouldn't break like this, and the bug(s) may lie elsewhere. However, it may be useful to either:
(a) only trigger necessary subsystems (does DRM need to be triggered in the case of installing Firefox?) or
(b) support some sort of blacklist to prevent specific subsystems from being triggered when there are known issues.

I'll be back to attach some logs...

Thank you!

Revision history for this message
Chris Patterson (cjp256) wrote :
Revision history for this message
Chris Patterson (cjp256) wrote :
Revision history for this message
Chris Patterson (cjp256) wrote :
Revision history for this message
Chris Patterson (cjp256) wrote :
Revision history for this message
Chris Patterson (cjp256) wrote :
Changed in snapd:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Chris Patterson (cjp256) wrote :

FWIW, either there was a fix for this or updating to 20.04 resolved this issue for me. :)

To post a comment you must log in.