https://bugs.kde.org/show_bug.cgi?id=514728
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #4 from Zamundaaa <[email protected]> --- Alright, so "permission denied" is really the problem after all: > [ 269.994628] PM: suspend exit > [ 269.996308] [drm:drm_stub_open] > [ 269.996315] amdgpu 0000:c3:00.0: [drm:drm_open_helper] > comm="switcheroo-cont", pid=10643, minor=0 [...] > [ 269.996888] amdgpu 0000:c3:00.0: [drm:drm_ioctl] comm="elogind-daemon" > pid=3335, dev=0xe200, auth=1, DRM_IOCTL_SET_MASTER > [ 269.996897] amdgpu 0000:c3:00.0: [drm:drm_ioctl] comm="elogind-daemon", > pid=3335, ret=-16 [...] > [ 270.000812] amdgpu 0000:c3:00.0: [drm:drm_release] open_count = 36 > [ 270.000836] amdgpu 0000:c3:00.0: [drm:drm_file_free] > comm="switcheroo-cont", pid=10643, dev=0xe200, open_count=36 > [ 270.000900] amdgpu 0000:c3:00.0: [drm:_drm_lease_revoke] revoke leases for > 0000000086be1cdc 0 > [ 270.000918] amdgpu 0000:c3:00.0: [drm:drm_lease_destroy] drm_lease_destroy > 0 > [ 270.000920] amdgpu 0000:c3:00.0: [drm:drm_master_destroy] > drm_lease_destroy done 0 switcheroo-control seems to (accidentally) take drm master permissions here, so elogind's attempt at giving KWin drm master permissions fails. I don't know why drm master permissions would be in a different process than KWin at this point, but I'm certain it's not KWin's fault. Because drm master permissions are super terribly stupid, switcheroo-control is probably not doing anything wrong either. Most likely, elogind needs to just retry if it fails with EBUSY when setting up master permissions. So please report this at https://github.com/elogind/elogind/issues -- You are receiving this mail because: You are watching all bug changes.
