Paring of smartphone as card reader not successful

Bug #1942649 reported by Stefan Strömer
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ausweisapp2 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After pairing my smartphone as a card reader it appears as "Parired, but unavailable" and is again listet as "Available remote device".
Stopping and restarting the remote connection in the smartphone app doesn't help.

[Impact]
Smartphones can't be used as card readers anymore in this version of ausweisapp2, which is probably the prevalent use case for the app.

[Test Plan]
Install and start AusweisApp2 on a smartphone, go to remote access and start pairing. Start AusweisApp2 on Ubuntu, go to Settings - Smartphone as card reader. Smartphone will be shown as available remote device. Click on "click to pair" and enter pairing code shown on smartphone. A notification will suggest successful pairing, but the AusweisApp2 now shows the smartphone as "paired, but unavailable".

Revision history for this message
Stefan Strömer (stefan-stroemer) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ausweisapp2 (Ubuntu):
status: New → Confirmed
Revision history for this message
Hans Dampf (hda22) wrote :

Possibly related to Bug #1921107 ?

Revision history for this message
John Paul Adrian Glaubitz (glaubitz) wrote :

@hda22: If that's true, someone has to ping the Ubuntu maintainers to import the latest version of the package from Debian. I don't have any control over the Ubuntu packages, unfortunately.

Hans Dampf (hda22)
description: updated
description: updated
description: updated
description: updated
Revision history for this message
Hans Dampf (hda22) wrote :

Contacted Ubuntu maintainers who pointed me to https://wiki.ubuntu.com/StableReleaseUpdates where I get stuck in Chapter 3 Step 3 to 4.

Hans Dampf (hda22)
description: updated
Revision history for this message
Hans Dampf (hda22) wrote :

After some experiments I found out that the version 1.20.2-1~ubuntu20.04.1~ppa1 found here https://launchpad.net/~misery/+archive/ubuntu/ppa actually fixes the bug - at least for me. So this should be more like a microrelease with a low risk of breaking other functionality compared to upgrading to the latest upstream release 1.22.2. Maybe misery's patch could easily be incorporated into the official ubuntu package.

Revision history for this message
Brian Murray (brian-murray) wrote :

That version of the package no longer exists in the PPA so it's hard to know what exactly the fix was. Regardless, I'm unsubscribing the Ubuntu Sponsors team from this bug report given that there isn't anything to upload to the Ubuntu archive at this point in time.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.