| Age | Commit message (Collapse) | Author |
|---|
|
Due to #7139 (the logbook log centralizer) logs from 3rd party libs are
included in the centralized logs with lots of debug information and we
don't want that.
We use the existing silencer to exclude logs that are not from leap
modules.
- Resolves: #7185
|
|
if the lsb_release utility is present on system, log part of its output
so we can have more information about the platform bitmask is running
on.
- Resolves: #7162
- Releases: 0.9.0
|
|
- Related: #7139
- Related: #7140
- Related: #7141
- Related: #7142
- Related: #7143
- Related: #7144
- Related: #7180
- Related: #7184
|
|
We don't need to run the event server on the backend if we are running
from the standalone bundle since the launcher takes care of that.
- Related: #7126
|
|
due to remaining bits that had not been changed after a refactor.
- Resolves: #7093
|
|
- Related: #6359
|
|
* Instead of checking if soledad is still syncing for the timeuot cancel
the delayed call.
* Count retries properly.
* Now soledad sync only returns SoledadError (#6981).
|
|
Before this commit, the backend used plain pyzmq bindings for communicating
with the frontend. This implements the txzmq twisted-powered bindings instead.
Closes: #6360
|
|
Change the 'ip' command location to support Fedora/RHEL distros.
/bin/ip is pressent on Debian/Ubuntu but not on Fedora.
/sbin/ip is a symlink to /bin/ip on Debian/Ubuntu and a binary on Fedora.
- Resolves: #6894
|
|
- Related: #6876
|
|
On 64bit Fedora/RHEL systems the python path is /usr/lib64 instead of
/usr/lib like on Ubuntu systems. This fix allows those users to use the
bootstrap_develop.sh script.
|
|
If the quit() call is triggered by the system logout we should not
disable the autostart. Otherwise bitmask won't autostart on the next
session start.
- Resolves: #6424
|
|
Catch the keyring.errors.InitError exception.
The automatic login sequence now stops correctly instead of freezing if
the user cancel the keyring open operation.
- Resolves: #6682
|
|
Replace the hardcoded port '1194' for the port specified in
eip-service.json.
Choose the best port to use according which one is enabled in the
eip-service.json file
Resolves: #6541
|
|
After a provider fails to pass the checks, the providers combo box is
not enabled when it should, we just took care of the provider line edit.
- Resolves: #6418
|
|
Also set text to 'bold' so it's easier to find at a first sight.
- Resolves: #5526
|
|
Resolves: #6713
|
|
|
|
|
|
|
|
|
|
FIX: Login attempt is made against previously selected provider.
Closes #6654.
Cherry-picked from release/0.8.x since it's a very annoying bug for the
testing cycles for the next release (0.9.0) -- kali.
|
|
FIX: Login attempt is made against previously selected provider.
Closes #6654.
|
|
Use global flag for ZMQ_HAS_CURVE.
Closes #6646
|
|
|
|
|
|
|
|
Closes #6717.
|
|
|
|
|
|
|
|
|
|
This reverts commit 93750f2371555ad0c769c62c1bd179e2b96c282c.
|
|
|
|
Closes #6123.
|
|
Closes #6150.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes #6048.
|
|
|
|
Add a platform independent release_lock helper, so all the SO dependent
code goes inside the locks file.
Also, do some code cleanup.
|
|
* Emit the `eip_missing_helpers` signal when the user chooses "Don't ask
me again".
* We emit that signal when some helper file is missing, even if the user
doesn't want a warning.
* Do the update of the eip enabled status with some delay to give some
time the eip machine to start and do what it needs with the
buttons/labels and avoid the 'hide turn on button if missing files'
being overridden.
Closes #5945.
|
|
- Don't disconnect logout signals, so when the wizard is triggered the
UI can reflect the logout result.
- Restore the selected provider when 'other...' is selected *before* the
provider_changed signal is emitted to avoid that option to keep
selected in case of some error.
- Avoid the currentIndexChanged to be triggered when we load the providers.
|
|
Closes #5996, #5997.
|
|
Closes #5995.
|
