FS#51882 - [dkms] Hooks building stop right after an invalid kernel
Attached to Project:
Arch Linux
Opened by michael Lojkovic (zerophase) - Saturday, 19 November 2016, 02:07 GMT
Last edited by Sébastien Luttringer (seblu) - Saturday, 14 January 2017, 15:41 GMT
Opened by michael Lojkovic (zerophase) - Saturday, 19 November 2016, 02:07 GMT
Last edited by Sébastien Luttringer (seblu) - Saturday, 14 January 2017, 15:41 GMT
|
Details
Description:
The current version of lightdm fails to start. There's a couple newer versions than the current arch version. Additional info: lightdm 1:1.18.3-1 Steps to reproduce: Update nvidia drivers to the latest version, reboot, and lightdm should fail. |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Saturday, 14 January 2017, 15:41 GMT
Reason for closing: Fixed
Additional comments about closing: dkms-2.3-2
Saturday, 14 January 2017, 15:41 GMT
Reason for closing: Fixed
Additional comments about closing: dkms-2.3-2
KWin works though, but when I go in the Compositor settings in the control panel the window hangs...
EDIT: Blender 2.78 too
EDIT 2: Happens only with Steam open...
EDIT 3: Happens when there are two OpenGL apps open at the same time... (for example, if I try to start two blender instances, the second hangs undefinitely)
You says that a DKMS alpm script issue, could you provide the appropriate console output? The best would be with env variable DKMS_ALPM_HOOK_DEBUG set.
2) Could you point what's line is an bug. I don't see what's wrong.
Yes, I did. I believe I set it in /etc/environment
2) Could you point what's line is an bug. I don't see what's wrong.
I believe line 31 has the issue. If a kernel isn't completely uninstalled it's causing the hook to exit, upon hitting the condition and trying to install a dkms module. It looks like it bubbles up to line 80, returns from the function and exits from there.
2) Line 31 is:
11/21 14:00:17 [NOTICE] Download complete: /var/lib/pacman/sync/infinality-bundle.db.sig
Except you are using unsupported repo and packages, nothing is wrong at that line.
2) it's how the error is handled at line 81 that's the problem. If an error is found on line 31 pacman skips processing other kernels. How I look at it the return should be a continue at line 81. How it's working right now if a directory is corrupted other kernels won't receive the dkms update till that corrupted directory is fixed. (any other cause of throwing an error has the same effect)
Just replacing return with continue will allow functional kernels to still receive updates.
I get what you are reporting now, the issue only happen when at least one kernel is not dkms «compliant» and so all others build fail.