You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the Mirall client on an x64 installation of Linux Mint / MATE.
The client is configured to be started automatically by MATE.
It seems that Mirall cannot wait for NetworkManager to initialize the wifi connection but tries to connect the owncloud server immediately and when it fails (since there is no network yet) it reports the error in a dialog and then freezes when I close the dialog window.
I say "it freezes", because it doesn't display its icon on the taskbar and doesn't seem to be doing anything cannot be started properly after NetworkManager has connected to the wifi network.
If I kill the failed "owncloud" process (Mirall) with killall, then it becomes possible to properly start Mirall.
Mirall should be able to re-try connecting to the owncloud server repeatedly and it shouldn't freeze.
The text was updated successfully, but these errors were encountered:
I am using the Mirall client on an x64 installation of Linux Mint / MATE.
The client is configured to be started automatically by MATE.
It seems that Mirall cannot wait for NetworkManager to initialize the wifi connection but tries to connect the owncloud server immediately and when it fails (since there is no network yet) it reports the error in a dialog and then freezes when I close the dialog window.
I say "it freezes", because it doesn't display its icon on the taskbar and doesn't seem to be doing anything cannot be started properly after NetworkManager has connected to the wifi network.
If I kill the failed "owncloud" process (Mirall) with killall, then it becomes possible to properly start Mirall.
Mirall should be able to re-try connecting to the owncloud server repeatedly and it shouldn't freeze.
The text was updated successfully, but these errors were encountered: