Can confirm, i've started seeing this frequently

From what I've tested it looks like it is cause by autoupdate. User put the machine in the sleep mode, when waking up and being on lock screen app detects that update is available and start updating and restarting app, so when user enters password it see app in setup state

@brianp Should I change this behavior somehow ? Like maybe preventing autoupdate in sleep mode or something ?

Is that something we can detect?

@brianp

use sys_info::{PowerStatus, SystemExt};

fn main() {
    let power_status = PowerStatus::new().unwrap();
    if power_status.is_sleeping() {
        println!("The system is in sleep mode.");
    } else {
        println!("The system is not in sleep mode.");
    }
}

Found something like this

If the system is asleep, let's do an update check as if the user does not have the auto-update feature turned on.

1. Check for update
2. Present a dialog asking if the user would like to update as the upgrade could not be processed while in sleep mode

It's essentially the same process as not having the auto update feature turned on, but the messaging explains why we didn't do the update.

Okay, sounds good

@brianp What do you think maybe about also changing auto update a bit because now if it detects update it proceed with it straight away and new users maybe even don't know what is happening. What about displaying modal with something like "New version detected: Tari Universe 0.9.0. Updating in 5 . 4 . 3 . 2 . 1" and adding button to cancel it

@Misieq01 having no user interaction on a regular update is by design. It is supposed to be as low a barrier as possible for the update to occur. If auto-update is not turned on, the user receives this dialog to ask if they'd like to update.

When the feature is turned on, it should be seamless.

Except for now, for the machine may be asleep.

@MCozhusheck #1335 was merged, could you test it again and see if issue persist for you ?