From: Jonathon Fernyhough <jonathon.fernyhough@york.ac.uk>
To: wireguard@lists.zx2c4.com
Subject: Re: Bug report: WG won't reinstall after some OS recover procedures
Date: Mon, 18 Dec 2017 14:43:10 +0000 [thread overview]
Message-ID: <9218a9a3-1821-f0ed-7c7a-42c123695a60@york.ac.uk> (raw)
In-Reply-To: <2d4283b6-e379-cbbe-d084-91de4e023eca@posteo.net>
[-- Attachment #1.1: Type: text/plain, Size: 1346 bytes --]
On 18/12/17 14:29, Nicholas Joll wrote:
> To Whom It May Concern
>
> What happened. (1) On a system on which Wireguard was working, I used
> the 'TimeShift' program to restore Linux Mint from backup - twice, on
> one occasion including within the restore a reinstall of Grub and
> rebuild of initramfs. (Points 2-3 that follow apply to both versions of
> the restore.) (2) After the restore, WG still worked. (3) I updated the
> kernel (on one occasion before rebooting, or another after rebooting).
> (4) WG no longer worked. When I tried to reinstall it, it gave
> 'post-install' messages about how the dkms module was installed already.
> All manner of package removal and purging and file deletion failed to
> achieve anything - until I discovered that deleting a file in
> /var/lib/dkms/wireguard/ (together with 'sudo dkms --reconfigure -a'?)
> fixed things.
>
> What should have happened. WG should be able to cope with such a
> restore. At worst, it should give the user messages about how to fix the
> problem.
>
> System Concerned: Linux Mint 18.3 Cinnamon; WG 0.0.20171211.
>
This sounds like an issue centred on DKMS rather than WireGuard itself.
Do you have any other DKMS-managed kernel modules? If so, how did they
cope with the restore process?
Which WireGuard packages are you using?
J
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-12-18 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 14:29 Nicholas Joll
2017-12-18 14:43 ` Jonathon Fernyhough [this message]
2017-12-18 14:47 ` Jason A. Donenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9218a9a3-1821-f0ed-7c7a-42c123695a60@york.ac.uk \
--to=jonathon.fernyhough@york.ac.uk \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).