Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#57543 - [dkms] Warning in dkms pre-hooks on kernel update
Attached to Project:
Arch Linux
Opened by Hervé (herve) - Saturday, 17 February 2018, 11:07 GMT
Last edited by Sébastien Luttringer (seblu) - Saturday, 26 May 2018, 22:51 GMT
Opened by Hervé (herve) - Saturday, 17 February 2018, 11:07 GMT
Last edited by Sébastien Luttringer (seblu) - Saturday, 26 May 2018, 22:51 GMT
|
DetailsHello,
Description: I didn't pay attention and ran a "pacman -Syu" while the shell was in an SMB share (through gnome-vfs). I got this warning in the shell (in French so I translated it back the best I could): :: Executing pre-transaction hooks... (1/1) Remove DKMS modules error: failed to determine current directory ==> dkms remove broadcom-wl/6.30.223.271 -k 4.15.3-1-ARCH I didn't get any warning on post-transaction hooks, and the "kernel-4.15.3-1-ARCH-x86_64" version of the module was properly removed, so I guess it was more troubling than necessary. So I set this report to very low severity. Additional info: * package version: dkms 2.5-1 * config and/or log files etc.: log posted above, I don't think more is necessary. Steps to reproduce: Shell session in a gnome-gvfs share, the working directory looked something like "/run/user/1000/gvfs/smb-share:server=freebox_server,share=hard%20drive/". |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Saturday, 26 May 2018, 22:51 GMT
Reason for closing: No response
Saturday, 26 May 2018, 22:51 GMT
Reason for closing: No response
Comment by Sébastien Luttringer (seblu) -
Tuesday, 17 April 2018, 22:52 GMT
Could you run again and show the output with the env variable DKMS_ALPM_HOOK_DEBUG set to 1?