Revision history [back]

The following bug does both apply to Jolla 1 and Jolla C (Jolla Tablet untested).

I was running 2.1.0.11 with a lock code on my device which worked perfectly but right after I upgraded to 2.1.1.24 and rebooted I was told that my phone was locked due to too many wrong login attempts despite not having typed anything after reboot.

This fix doesn't work as changes written to *devicelock_settings.conf gets ignored despite being listed by /usr/lib/qt5/plugins/devicelock/encpartition --get-config-key.

A dirty fix was to rename /mnt/usr/share/lipstick/devicelock/devicelock_settings.conf to eg. devicelock_settings.conf_bk (via either ssh or recovery telnet). This makes it possible to boot the device and get in by typing my lock code, but the device lock entry in the Settings menu is gone. Renaming the settings file back to devicelock_settings.conf doesn't retore the menu entry.

The following bug does both apply to Jolla 1 and Jolla C (Jolla Tablet untested).

I was running 2.1.0.11 with a lock code on my device which worked perfectly but right after I upgraded to 2.1.1.24 and rebooted I was told that my phone was locked due to too many wrong login attempts despite not having typed anything after reboot.

This fix doesn't work as changes written to *devicelock_settings.conf gets ignored despite being listed by /usr/lib/qt5/plugins/devicelock/encpartition --get-config-key.

A dirty fix was to rename /mnt/usr/share/lipstick/devicelock/devicelock_settings.conf to eg. devicelock_settings.conf_bk (via either ssh or recovery telnet). This makes it possible to boot the device and get in by typing my lock code, but the device lock entry in the Settings menu is gone. Renaming the settings file back to devicelock_settings.conf doesn't retore the menu entry.

The following bug does both apply to Jolla 1 and Jolla C (Jolla Tablet untested).

I was running 2.1.0.11 with a lock code on my device which worked perfectly but right after I upgraded to 2.1.1.24 and rebooted I was told that my phone was locked due to too many wrong login attempts despite not having typed anything after reboot.

This fix doesn't work as changes written to *devicelock_settings.conf gets ignored despite being listed by /usr/lib/qt5/plugins/devicelock/encpartition --get-config-key.

A dirty fix was to rename /mnt/usr/share/lipstick/devicelock/devicelock_settings.conf to eg. devicelock_settings.conf_bk (via either ssh or recovery telnet). This makes it possible to boot the device and get in by typing my lock code, but the device lock entry in the Settings menu is gone. Renaming the settings file back to devicelock_settings.conf doesn't retore the menu entry.

[desktop]

The following bug does both apply to Jolla 1 and Jolla C (Jolla Tablet untested).

I was running 2.1.0.11 with a lock code on my device which worked perfectly but right after I upgraded to 2.1.1.24 and rebooted I was told that my phone was locked due to too many wrong login attempts despite not having typed anything after reboot.

This fix doesn't work as changes written to *devicelock_settings.conf gets ignored despite being listed by /usr/lib/qt5/plugins/devicelock/encpartition --get-config-key.

A dirty fix was to rename /mnt/usr/share/lipstick/devicelock/devicelock_settings.conf to eg. devicelock_settings.conf_bk (via either ssh or recovery telnet). This makes it possible to boot the device and get in by typing my lock code, but the device lock entry in the Settings menu is gone. Renaming the settings file back to devicelock_settings.conf doesn't retore the menu entry.

Settings file prior to upgrade (2.1.0.11) [desktop] nemo\devicelock\automatic_locking=0 nemo\devicelock\code_current_is_digit_only=1 nemo\devicelock\code_current_length=5 nemo\devicelock\code_last_changed=1501532585 nemo\devicelock\maximum_attempts=4

Settings file after upgrade (2.1.1.24)

[desktop]
nemo\devicelock\automatic_locking=0

nemo\devicelock\automatic_locking=0 nemo\devicelock\code_current_is_digit_only=1 nemo\devicelock\code_current_length=8 nemo\devicelock\code_last_changed=1466266383 nemo\devicelock\maximum_attempts=4 nemo\devicelock\peeking_allowed=1 nemo\devicelock\sideloading_allowed=1 nemo\devicelock\maximum_automatic_locking=-1 nemo\devicelock\absolute_maximum_attempts=-1 nemo\devicelock\current_attempts=4 nemo\devicelock\show_notification=1 nemo\devicelock\code_max_length=42 nemo\devicelock\code_min_length=5 nemo\devicelock\code_input_is_keyboard=false nemo\devicelock\code_max_age=0 nemo\devicelock\code_remember_previous=1 nemo\devicelock\expiration_notification_threshold=5 nemo\devicelock\expiration_notification_last_emitted=0 nemo\devicelock\encrypt_home=false nemo\devicelock\temporary_lock_timeout=-1 nemo\devicelock\supported_device_reset_options=Reboot nemo\devicelock\code_is_mandatory=false nemo\devicelock\code_generation=NoCodeGeneration

[access-level] maximum_automatic_locking=DeviceManagement absolute_maximum_attempts=DeviceManagement current_attempts=System show_notification=SecureUser code_max_length=DeviceManagement code_min_length=DeviceManagement code_input_is_keyboard=SecureUser code_max_age=SecureUser code_remember_previous=DeviceManagement expiration_notification_threshold=SecureUser expiration_notification_last_emitted=System encrypt_home=System temporary_lock_timeout=SecureUser supported_device_reset_options=Configuration code_is_mandatory=DeviceManagement code_generation=DeviceManagement code_last_changed=System

The following bug does both apply to Jolla 1 and Jolla C (Jolla Tablet untested).

I was running 2.1.0.11 with a lock code on my device which worked perfectly but right after I upgraded to 2.1.1.24 and rebooted I was told that my phone was locked due to too many wrong login attempts despite not having typed anything after reboot.

This fix doesn't work as changes written to *devicelock_settings.conf gets ignored despite being listed by /usr/lib/qt5/plugins/devicelock/encpartition --get-config-key.

A dirty fix was to rename /mnt/usr/share/lipstick/devicelock/devicelock_settings.conf to eg. devicelock_settings.conf_bk (via either ssh or recovery telnet). This makes it possible to boot the device and get in by typing my lock code, but the device lock entry in the Settings menu is gone. Renaming the settings file back to devicelock_settings.conf doesn't retore the menu entry.

Settings file prior to upgrade (2.1.0.11) [desktop] nemo\devicelock\automatic_locking=0 nemo\devicelock\code_current_is_digit_only=1 nemo\devicelock\code_current_length=5 emo\devicelock\code_current_length=8 nemo\devicelock\code_last_changed=1501532585 nemo\devicelock\maximum_attempts=4

Settings file after upgrade (2.1.1.24)

[desktop]
nemo\devicelock\automatic_locking=0

nemo\devicelock\code_current_is_digit_only=1 nemo\devicelock\code_current_length=8 nemo\devicelock\code_last_changed=1466266383 nemo\devicelock\maximum_attempts=4 nemo\devicelock\peeking_allowed=1 nemo\devicelock\sideloading_allowed=1 nemo\devicelock\maximum_automatic_locking=-1 nemo\devicelock\absolute_maximum_attempts=-1 nemo\devicelock\current_attempts=4 nemo\devicelock\show_notification=1 nemo\devicelock\code_max_length=42 nemo\devicelock\code_min_length=5 nemo\devicelock\code_input_is_keyboard=false nemo\devicelock\code_max_age=0 nemo\devicelock\code_remember_previous=1 nemo\devicelock\expiration_notification_threshold=5 nemo\devicelock\expiration_notification_last_emitted=0 nemo\devicelock\encrypt_home=false nemo\devicelock\temporary_lock_timeout=-1 nemo\devicelock\supported_device_reset_options=Reboot nemo\devicelock\code_is_mandatory=false nemo\devicelock\code_generation=NoCodeGeneration

nemo\devicelock\code_generation=NoCodeGeneration [access-level] maximum_automatic_locking=DeviceManagement absolute_maximum_attempts=DeviceManagement current_attempts=System show_notification=SecureUser code_max_length=DeviceManagement code_min_length=DeviceManagement code_input_is_keyboard=SecureUser code_max_age=SecureUser code_remember_previous=DeviceManagement expiration_notification_threshold=SecureUser expiration_notification_last_emitted=System encrypt_home=System temporary_lock_timeout=SecureUser supported_device_reset_options=Configuration code_is_mandatory=DeviceManagement code_generation=DeviceManagement code_last_changed=System

The following bug does both apply to Jolla 1 and Jolla C (Jolla Tablet untested).

I was running 2.1.0.11 with a lock code on my device which worked perfectly but right after I upgraded to 2.1.1.24 and rebooted I was told that my phone was locked due to too many wrong login attempts despite not having typed anything after reboot.

This fix doesn't work as changes written to *devicelock_settings.conf gets ignored despite being listed by /usr/lib/qt5/plugins/devicelock/encpartition --get-config-key.

A dirty fix was to rename /mnt/usr/share/lipstick/devicelock/devicelock_settings.conf to eg. devicelock_settings.conf_bk (via either ssh or recovery telnet). This makes it possible to boot the device and get in by typing my lock code, but the device lock entry in the Settings menu is gone. Renaming the settings file back to devicelock_settings.conf doesn't retore the menu entry.

Settings file prior to upgrade (2.1.0.11) (2.1.0.11):

[desktop]
 nemo\devicelock\automatic_locking=0
 nemo\devicelock\code_current_is_digit_only=1
 emo\devicelock\code_current_length=8
 nemo\devicelock\code_last_changed=1501532585
    nemo\devicelock\maximum_attempts=4
nemo\devicelock\maximum_attempts=4

Settings file after upgrade (2.1.1.24)(2.1.1.24):

[desktop]
nemo\devicelock\automatic_locking=0
nemo\devicelock\code_current_is_digit_only=1
nemo\devicelock\code_current_length=8
nemo\devicelock\code_last_changed=1466266383
nemo\devicelock\maximum_attempts=4
nemo\devicelock\peeking_allowed=1
nemo\devicelock\sideloading_allowed=1
nemo\devicelock\maximum_automatic_locking=-1
nemo\devicelock\absolute_maximum_attempts=-1
nemo\devicelock\current_attempts=4
nemo\devicelock\show_notification=1
nemo\devicelock\code_max_length=42
nemo\devicelock\code_min_length=5
nemo\devicelock\code_input_is_keyboard=false
nemo\devicelock\code_max_age=0
nemo\devicelock\code_remember_previous=1
nemo\devicelock\expiration_notification_threshold=5
nemo\devicelock\expiration_notification_last_emitted=0
nemo\devicelock\encrypt_home=false
nemo\devicelock\temporary_lock_timeout=-1
nemo\devicelock\supported_device_reset_options=Reboot
nemo\devicelock\code_is_mandatory=false
nemo\devicelock\code_generation=NoCodeGeneration

[access-level]
maximum_automatic_locking=DeviceManagement
absolute_maximum_attempts=DeviceManagement
current_attempts=System
show_notification=SecureUser
code_max_length=DeviceManagement
code_min_length=DeviceManagement
code_input_is_keyboard=SecureUser
code_max_age=SecureUser
code_remember_previous=DeviceManagement
expiration_notification_threshold=SecureUser
expiration_notification_last_emitted=System
encrypt_home=System
temporary_lock_timeout=SecureUser
supported_device_reset_options=Configuration
code_is_mandatory=DeviceManagement
code_generation=DeviceManagement
code_last_changed=System

The following bug does both apply to Jolla 1 and Jolla C (Jolla Tablet untested).

I was running 2.1.0.11 with a lock code on my device which worked perfectly but right after I upgraded to 2.1.1.24 and rebooted I was told that my phone was locked due to too many wrong login attempts despite not having typed anything after reboot.

This fix doesn't work as changes written to *devicelock_settings.conf gets ignored despite being listed by /usr/lib/qt5/plugins/devicelock/encpartition --get-config-key.

A dirty fix was to rename /mnt/usr/share/lipstick/devicelock/devicelock_settings.conf to eg. devicelock_settings.conf_bk (via either ssh or recovery telnet). This makes it possible to boot the device and get in by typing my lock code, but the device lock entry in the Settings menu is gone. Renaming the settings file back to devicelock_settings.conf doesn't retore the menu entry.

Settings file prior to upgrade (2.1.0.11):

[desktop]
nemo\devicelock\automatic_locking=0
nemo\devicelock\code_current_is_digit_only=1
emo\devicelock\code_current_length=8
nemo\devicelock\code_last_changed=1501532585
nemo\devicelock\maximum_attempts=4

Settings file after upgrade (2.1.1.24):

[desktop]
nemo\devicelock\automatic_locking=0
nemo\devicelock\code_current_is_digit_only=1
nemo\devicelock\code_current_length=8
nemo\devicelock\code_last_changed=1466266383
nemo\devicelock\maximum_attempts=4
nemo\devicelock\peeking_allowed=1
nemo\devicelock\sideloading_allowed=1
nemo\devicelock\maximum_automatic_locking=-1
nemo\devicelock\absolute_maximum_attempts=-1
nemo\devicelock\current_attempts=4
nemo\devicelock\show_notification=1
nemo\devicelock\code_max_length=42
nemo\devicelock\code_min_length=5
nemo\devicelock\code_input_is_keyboard=false
nemo\devicelock\code_max_age=0
nemo\devicelock\code_remember_previous=1
nemo\devicelock\expiration_notification_threshold=5
nemo\devicelock\expiration_notification_last_emitted=0
nemo\devicelock\encrypt_home=false
nemo\devicelock\temporary_lock_timeout=-1
nemo\devicelock\supported_device_reset_options=Reboot
nemo\devicelock\code_is_mandatory=false
nemo\devicelock\code_generation=NoCodeGeneration

[access-level]
maximum_automatic_locking=DeviceManagement
absolute_maximum_attempts=DeviceManagement
current_attempts=System
show_notification=SecureUser
code_max_length=DeviceManagement
code_min_length=DeviceManagement
code_input_is_keyboard=SecureUser
code_max_age=SecureUser
code_remember_previous=DeviceManagement
expiration_notification_threshold=SecureUser
expiration_notification_last_emitted=System
encrypt_home=System
temporary_lock_timeout=SecureUser
supported_device_reset_options=Configuration
code_is_mandatory=DeviceManagement
code_generation=DeviceManagement
code_last_changed=System

The following bug does both apply to Jolla 1 and Jolla C (Jolla Tablet untested).

I was running 2.1.0.11 with a lock code on my device which worked perfectly but right after I upgraded to 2.1.1.24 and rebooted I was told that my phone was locked due to too many wrong login attempts despite not having typed anything after reboot.

This fix doesn't work as changes written to *devicelock_settings.conf gets ignored despite being listed by /usr/lib/qt5/plugins/devicelock/encpartition --get-config-key.

A dirty fix was to rename /mnt/usr/share/lipstick/devicelock/devicelock_settings.conf to eg. devicelock_settings.conf_bk (via either ssh or recovery telnet). This makes it possible to boot the device and get in by typing my lock code, but the device lock entry in the Settings menu is gone. Renaming the settings file back to devicelock_settings.conf doesn't retore the menu entry.

Settings file prior to upgrade (2.1.0.11):

[desktop]
nemo\devicelock\automatic_locking=0
nemo\devicelock\code_current_is_digit_only=1
emo\devicelock\code_current_length=8
nemo\devicelock\code_last_changed=1501532585
nemo\devicelock\code_last_changed=1466266383
nemo\devicelock\maximum_attempts=4

Settings file after upgrade (2.1.1.24):

[desktop]
nemo\devicelock\automatic_locking=0
nemo\devicelock\code_current_is_digit_only=1
nemo\devicelock\code_current_length=8
nemo\devicelock\code_last_changed=1466266383
nemo\devicelock\maximum_attempts=4
nemo\devicelock\peeking_allowed=1
nemo\devicelock\sideloading_allowed=1
nemo\devicelock\maximum_automatic_locking=-1
nemo\devicelock\absolute_maximum_attempts=-1
nemo\devicelock\current_attempts=4
nemo\devicelock\show_notification=1
nemo\devicelock\code_max_length=42
nemo\devicelock\code_min_length=5
nemo\devicelock\code_input_is_keyboard=false
nemo\devicelock\code_max_age=0
nemo\devicelock\code_remember_previous=1
nemo\devicelock\expiration_notification_threshold=5
nemo\devicelock\expiration_notification_last_emitted=0
nemo\devicelock\encrypt_home=false
nemo\devicelock\temporary_lock_timeout=-1
nemo\devicelock\supported_device_reset_options=Reboot
nemo\devicelock\code_is_mandatory=false
nemo\devicelock\code_generation=NoCodeGeneration

[access-level]
maximum_automatic_locking=DeviceManagement
absolute_maximum_attempts=DeviceManagement
current_attempts=System
show_notification=SecureUser
code_max_length=DeviceManagement
code_min_length=DeviceManagement
code_input_is_keyboard=SecureUser
code_max_age=SecureUser
code_remember_previous=DeviceManagement
expiration_notification_threshold=SecureUser
expiration_notification_last_emitted=System
encrypt_home=System
temporary_lock_timeout=SecureUser
supported_device_reset_options=Configuration
code_is_mandatory=DeviceManagement
code_generation=DeviceManagement
code_last_changed=System