| Age | Commit message (Collapse) | Author |
|---|
|
we've agreed that the autostart behaviour can be unexpected;
we'll expose the ability under preferences (it can be controlled via cli
right now).
|
|
|
|
some refactor, plus fix docs
|
|
|
|
|
|
- Closes: #511
|
|
|
|
|
|
There's some corner cases that were very badly captured. On the first
place, it's confusing to quit on connection errors.
Secondly, a side-effect of aborting the initialization of the bitmask
object was a semi-random segfault when trying to access the object.
Here I pass any connection errors to the gui, but leave to the user to
quit the app. This probably will need more work when we want to
terminate the app on unrecoverable errors (no polkit, etc...), but for
now it makes the systray much more usable.
- Resolves: #465
|
|
it seems this was an attempt to make this injectable for tests, but it
can work by changing config variables too.
|
|
|
|
Also disable autostart if manual quit, remove custom printer that was
used for i18n and disable previous autostart if -disable-autostart
We didn't disable autostart after the migration to qt.
- Resolves: #355 #289
|
|
A corrupted pid file, or a file that contains something else than a pid
number used to block bitmask-vpn from launch. Now if the file contains
something that is not expected it will log it and rewrite it.
I refactor de code so the pid file will be released on quit instead of
initialization.
- Resolves: #349
|
|
- Resolves: #326
|
|
|
|
|
|
Let's close properly without segfaults :)
|
|
just a minimal boilerplate. the idea is to import the qml files and
assert that the states/widgets change accordingly if we mock the backend
status.
- Closes: #300
|
|
|
