mullvad reconnect does nothing if currently disconnected

[attisimon]

Is it a bug?

• I know this is an issue with the app, and contacting Mullvad support is not relevant.

I have checked if others have reported this already

• I have checked the issue tracker to see if others have reported similar issues.

Current Behavior

mullvad connect will connect to the default server.
mullvad reconnect will disconnect and connect again the selected server.
mullvad disconnect will disconnect the VPN connection.

Running mullvad reconnect while mullvad is disconnected will do nothing, the VPN will stay disconnected and there is no output in the terminal.

Expected Behavior

Running mullvad reconnect while mullvad is disconnected should do one of the following:

1. connect to the last used location or to the default location (relay)
2. if for some reason point 1. is not wanted as an action, then at least return an exit message to the terminal, informing the user that nothing has been reconnected and some reason for this.

Steps to Reproduce

0. configure your mullvad account so it can be used in a terminal
1. mullvad connect to connect to the default location
2. mullvad status to check if connected
3. mullvad reconnect to reconnect
4. mullvad status to check if still connected
5. mullvad disconnect to disable vpn
6. mullvad status to make sure mullvad is disconnected
7. mullvad reconnect to try to reconnect
8. mullvad status to check if still disconnected or connected
9. (optional) mullvad connect & mullvad status just to see if there is any issue with connecting

Failure Logs

No response

Operating system version

openSUSE Tumbleweed 20240503 x86_64 Kernel 6.8.8

Mullvad VPN app version

mullvad-cli 2024.2

Additional Information

I am using Mullvad in the CLI, auto connect is set to on and it connects without any problems at every system startup. I have not experienced any problems, only this little inconvenience that I was expecting mullvad to reconnect even if the last state was 'disconnected'. There are no errors in the log, not connection issues, mullvad connect will connect as expected.
I discovered this using mullvad-cli 2024.2-beta1, but after submitting the issue, I have managed to test it on another machine with mullvad-cli 2024.2 and it behaves the same as described in this issue.