Skip to content

Doesn't seem possible to actually disable the PIN, contrary to FAQ #412

@spillner

Description

@spillner

Describe the bug
I just upgraded from a very old, pre-PIN version of Oxide. After the upgrade, I was unable to skip setting a PIN (the button apparently for that purpose did nothing; only the "Set PIN" button let me advance). I then tried to clear my newly set PIN with xdg-settings set pin '' (as shown at https://oxide.eeems.codes/faq.html) and found that I was unable to login until I re-established a valid PIN.

To Reproduce

  1. [OPTIONAL] If running a pre-PIN version of Oxide:
    a. Update to the latest version of Oxide (2.8.4.-3) with opkg update && opkg upgrade or opkg install oxide
    b. Ensure Oxide is set as the launcher with launcherctl switch-launcher --start oxide
    c. Wait until the screen with the two "Skip" and "Set PIN" buttons appears (I don't remember the exact labels)
    d. Tap "Skip"
    e. Observe the button flashing, but the screen remaining at this dialog.
    f. Repeat steps 1.d and 1.e as many times as you desire.
    g. Tap "Set PIN" and reluctantly set a PIN
  2. ssh into your Remarkable and attempt to clear the PIN by running xdg-settings set pin ''.
  3. Wait for the screen to lock.
  4. Observe that you are at the PIN entry dialog, even though supposedly no PIN is set.
  5. Enter any four-digit combination, including your last actual PIN.
  6. Observe the "invalid PIN" error message
  7. Repeat steps 5 and 6 as many times as you desire.
  8. ssh into your Remarkable and run xdg-settings set pin 1234 to reestablish a valid PIN.
  9. Enter that PIN on the lock screen to regain normal access to your device.

Expected behavior
The user should be able to skip setting a PIN in the first place if not desired. If the user's PIN is set to the empty string (or probably anything other than a string of exactly four decimal digits), the user should never even be prompted with a lock screen.

Screenshots
None.

Version Information:

  • Device: reMarkable 2
  • OS: 2.12.3.606
  • Version: 2.8.4

Additional context

  • I have some custom tooling that relies on the old document format, but I could try upgrading if there's any reason to think it would make a difference
  • I have never installed any third-party software other than with opkg.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingto-triageThis needs to be triaged

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions