I inserted my YubiKey, started up the GUI, after a short delay 'Unknown
error occurred' was reported at the top-right. This is a useless error
for a user, so I dug about - it turns out that the program DOES know
what is wrong - YubiKeyFinder::diagnostics is emitted with the text 'USB
Error: Access denied (insufficient permissions)' - the supposed 'Unknown
error' is coming from mainwindow.cpp:MainWindow::keyFound, line 549,
returning the value of OTHER_ERROR (only 2 error situations are handled
here).

The user needs to be given a real error in some sort of accessible
place, there appears to be no output to stdout or stderr, or commandline
flags to change this etc.

Why is accessing the key suddenly a permissions issue? I have confirmed
it is detected and I can change the configuration when sudo'd. I have
confirmed this is also a problem in a Debian Testing VM with sysvinit
(this machine is Devuan Testing).

The last time I needed to change the edit the key would've been ~1 month
ago, and it appears the package has updated since (haven't downgraded to
test).
Devuan Release: stretch/sid
  990 testing         10.1.0.3   500 quodlibet-unstable lazka.github.io
--- Package information. ---
Depends                   (Version) | Installed
===================================-+-================
libc6                     (>= 2.14) | libgcc1                  (>=
1:3.0) | libgl1-mesa-glx                     |  OR libgl1
          | libqt5core5a        (>= 5.6.0~beta) | libqt5gui5
  (>= 5.0.2) | libqt5widgets5           (>= 5.0.2) | libstdc++6
         (>= 5) | libykpers-1-1           (>= 1.14.0) | libyubikey0
          (>= 1.5) |

Recommends                     (Version) | Installed
========================================-+-===========
qt5-image-formats-plugins                | 5.6.1-2+b1


Package's Suggests field is empty.

I'd like to get upstream's opinion but I was able to get the
personalization-gui to work by adding thefollowing udev rule to
/etc/udev/rules.d/70-yubikey-ccid.rules

This version grants access to the logged in user but uses some systemd
features to do it, on a system without systemd you can probably set a
group ownership that the logged in user should have or use world
read/writable permissions.

# Yubico YubiKey
SUBSYSTEM=="usb", ATTRS{idVendor}=="1050", ATTRS{idProduct}==\
"0113|0114|0115|0116|0120|0200|0402|0403|0406|0407|0410", \
TAG+="uaccess"

The device the application needs access to gets created in
/dev/bus/usb/

Diane

I'd like to get upstream's opinion but I was able to get the
personalization-gui to work by adding thefollowing udev rule to
/etc/udev/rules.d/70-yubikey-ccid.rules

This version grants access to the logged in user but uses some systemd
features to do it, on a system without systemd you can probably set a
group ownership that the logged in user should have or use world
read/writable permissions.

# Yubico YubiKey
SUBSYSTEM=="usb", ATTRS{idVendor}=="1050", ATTRS{idProduct}==\
"0113|0114|0115|0116|0120|0200|0402|0403|0406|0407|0410", \
TAG+="uaccess"

The device the application needs access to gets created in
/dev/bus/usb/

Diane

Dear submitter,

as the package yubikey-personalization-gui has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1014276

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)