Thank you for looking into this. The problem occurs on my original database, as well as in any new database i create. both the new and old databases were created by exporting unencrypted JSONs from Aegis (android). creating a completely new db and adding entries manually also result in 000000. i believe the databases are in good working order because they both function properly when used with the flatpak release of otpclient (v3.1.1).
thanks again, bk > On 01/12/2023 10:27 PM JST Debian Bug Tracking System <ow...@bugs.debian.org> > wrote: > > > This is an automatic notification regarding your Bug report > which was filed against the otpclient package: > > #1028438: otpclient: OTP values are all 000000 > > It has been closed by Francisco Vilmar Cardoso Ruviaro <vil...@debian.org>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Francisco Vilmar Cardoso > Ruviaro <vil...@debian.org> by > replying to this email. > > > -- > 1028438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028438 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > Hi Buster Keaton, > I just upgraded otpclient from 2.6.3-2 to 3.1.1-1 and everything went fine, > this error you reported did not occur*. > > Here is part of my /var/log/apt/history.log: > Commandline: apt install otpclient > Upgrade: otpclient-cli:amd64 (2.6.3-2, 3.1.1-1), otpclient:amd64 (2.6.3-2, > 3.1.1-1) > > > The fact that you have deleted otpclient config (~/.config/otpclient.cfg) > would not solve the problem, what we need to preserve would be the > ~/otpclient.enc file, if you have the backup file of ~/otpclient.enc you > can try to restore and test if the OTP Values are valid. > > > * I close the bug after checking what has been reported, > so far I have not encountered any problems. > > Thanks! > -- > Francisco Vilmar Cardoso Ruviaro <vil...@debian.org> > 4096R: 1B8C F656 EF3B 8447 2F48 F0E7 82FB F706 0B2F 7D00 > Package: otpclient > Version: 3.1.1-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > the update from 2.6.3-2 to 3.1.1-1 seems to be when the issue was > introduced > > * What exactly did you do (or not do) that was effective (or > ineffective)? > ineffective measures taken: > reboot > uninstall (apt remove --purge otpclient), then reinstall (apt install > otpclient) > created a new database > deleted otpclient config (~/.config/otpclient.cfg) > i no longer have a deb for the previous version, so i am unable to > test that > > * What was the outcome of this action? > 000000 is always returned for every entry (about 20 distinct entriest > to choose from) > > * What outcome did you expect instead? > valid OTP codes > > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.1.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages otpclient depends on: > ii libbaseencode1 1.0.15-1 > ii libc6 2.36-8 > ii libcotp12 1.2.7-1 > ii libgcrypt20 1.10.1-3 > ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1 > ii libglib2.0-0 2.74.4-1 > ii libgtk-3-0 3.24.36-1 > ii libjansson4 2.14-2 > ii libpng16-16 1.6.39-2 > ii libprotobuf-c1 1.4.1-1+b1 > ii libqrencode4 4.1.1-1 > ii libsecret-1-0 0.20.5-3 > ii libuuid1 2.38.1-4 > ii libzbar0 0.23.92-7 > > otpclient recommends no packages. > > Versions of packages otpclient suggests: > pn otpclient-cli <none> > > -- no debconf information
