| Age | Commit message (Collapse) | Author |
|---|
|
- Add a new handler for a zmq/thread-safe log send between components.
- Update the log window to use this new handler.
- Remove old custom handler
We have implemented a new handler that uses logbook, so this one is no
longer needed.
- Adapt log silencer to new handler
- Use log file always as default
- Related: #6733
|
|
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
|
|
Polkit was being launched and detected correctly, but Bitmask didn't
propagate this result to upper layers, so mainwindow thought the
platform wasn't initialized and then quitted without explanation.
Tested on debian testing, on June 5th 2015, using i3 window manager.
- Resolves: #6652
|
|
The backend was unsetting the soledad proxied object before actually calling
the soledad close() method and this was causing the application to hang when
exitting.
As the local soledad component's cancel_bootstrap() method is called before
the close() method, we'd better not unset the proxied object there, and let
only the close method do it. This commit fixes this by just removing the line
that unsets the proxied object in the wrong place.
|
|
If the events server is initialized in a different process than the backend,
the txzmq socket raises an "zmq.error.ZMQError: Interrupted system call"
exception during the events server initialization. Despite that, communication
seems to work flawlessly after the initialization.
Moving the events server initialization to the same process as the backend
causes the exception to not be raised during events server intialization.
|
|
- 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
|
|
- Related: #6876
|
|
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
|
|
- Resolves: #6426
- Resolves: #6681
|
|
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
|
|
|
|
Decouple SRPRegister from QT signaler and create SRPRegisterImpl
|
|
Decouple SRPAuth from QT signaler and move it to SRPAuthImpl
|
|
On SRP#authenticate, no need to use so many threads.
|
|
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
|
|
This concern is addressed by the following mail pullreq, that will be
into 0.4.0 release:
https://github.com/leapcode/leap_mail/pull/175
By the way, it is really funny that I cannot tell if this comment was
written by meskio, as the blame says, or if I was the original author of
the remark. I should stop drinking so much coffee.
|
|
The code was using 'fail' which is not a Deferred method.
- Resolves: #6772
|
|
Resolves: #6713
|
|
|
|
|
|
... on them, to user-writeable only.
I think we could consider ipc for the curve-case too, at least for the
platforms that support them.
|
|
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
|
|
|
|
the set_proxies_cb function in backend/components expects to have access
to these public properties.
|
|
This closes: #6658 and #6691
|
|
|
|
|
|
factory.do_Stop will handle this now.
|
|
we should deal with this with pure deferreds
|
|
|
|
|
|
From kali: add some notes about the improper handling of the mailbox
required to initialize the account, and draft some notes about how
to improve this in next iterations.
|
|
|
|
fix also a typo when logging errors
|
|
FIX: Login attempt is made against previously selected provider.
Closes #6654.
Remove unused comments as well.
|
|
This causes (on certain scenarios) the app to segfault and it is really
hard to debug.
|
|
Now it's working and no longer segfaults, so we can enable safely this
feature again.
Stop tracking the gui connections on wizard.
|
|
|
|
Remove srpauth obsolete tests.
Remove providerconfig obsolete test.
Set as mandatory the signaler object on ProviderBootstrapper and
EIPBootstrapper.
Closes #6631.
|
|
The set syntax using {} works for python >= 2.7, so failed on 2.6.
Closes #6638.
|
|
This reverts commit 93750f2371555ad0c769c62c1bd179e2b96c282c.
|
|
This temporary hack prevents the app to have segfaults when the first
run wizard finishes.
For more information look at https://leap.se/code/issues/6597
|
|
Fix typo for signal disconnection.
The backend is the one who always creates the certificates. Either if it
is run separately or in a process in the same app as the frontend.
|
