answered
2018-07-16 11:39:32 +0300
Having analyzed the system log captured during the process, I'd say this is the reason why it takes so long:
Jul 16 10:15:10 Sailfish PackageKit[19962]: refresh-cache transaction /3163_edabdaae from uid 100000 finished with success after 91938ms
The same happens for me when opening the Developer Tools menu in Settings:
Jul 16 10:16:53 Sailfish PackageKit[19962]: refresh-cache transaction /3168_eededbdb from uid 100000 finished with success after 93820ms
The big question now is, why the refresh takes so long to complete. I've found the following entries in the log, but am not sure of they relate to the issue:
Jul 16 10:16:13 Sailfish [21111]: QObject::disconnect: Unexpected null parameter
Jul 16 10:16:18 Sailfish [19982]: [D] unknown:0 - connection-manager.cpp 171 onDisconnected Disconnected from daemon
Jul 16 10:16:30 Sailfish [19982]: [D] unknown:0 - void DBusConnector::storeCredentials(const QDBusMessage&)
Jul 16 10:16:32 Sailfish [19982]: [D] unknown:0 - void DBusConnector::storeCredentials(const QDBusMessage&)
Jul 16 10:16:34 Sailfish [19982]: [D] unknown:0 - void DBusConnector::storeCredentials(const QDBusMessage&)
Jul 16 10:16:36 Sailfish [19982]: [D] unknown:0 - void DBusConnector::storeCredentials(const QDBusMessage&)
Jul 16 10:16:39 Sailfish [19982]: [D] unknown:0 - void DBusConnector::storeCredentials(const QDBusMessage&)
Jul 16 10:16:41 Sailfish [19982]: [D] unknown:0 - void DBusConnector::storeCredentials(const QDBusMessage&)
Jul 16 10:16:48 Sailfish [19982]: [D] unknown:0 - void DBusConnector::storeCredentials(const QDBusMessage&)
Jul 16 10:16:50 Sailfish [19982]: [D] unknown:0 - void DBusConnector::storeCredentials(const QDBusMessage&)
Jul 16 10:16:51 Sailfish [19982]: [D] unknown:0 - void DBusConnector::storeCredentials(const QDBusMessage&)
They appear at least twice shortly before the "refresh-transaction success" message, but may be related to other sync / login tasks running simultaneously in the background (which makes analyzing the issue more difficult). I would be great if someone from Jolla could assist in analyzing the root cause of this issue.
I've copied the whole log (including potential entries from other tasks) here: https://pastebin.com/wLij4ef8
Please note the failed adding user 'sshd', data deleted entry there.
@Spark
I have 2 x Jolla1 devices, so I thought I would have a go at answering your question. Once I started the process to deactivate developer mode, a message shows under the progress bar "preparing changes" but it sat like it for at least 3 minutes, then I looked back and developer mode was finally deactivated.
Perhaps to try again and leave it to do its thing for a little bit longer than you did before.
Spam Hunter ( 2018-07-15 15:36:53 +0300 )editWhy would one want to disable it anyway?
( just asking )
juiceme ( 2018-07-16 17:26:58 +0300 )editI thought as much @juiceme, but then not everyone wants to play with developer mode, but also I suppose you could say that there is no harm in leaving it enabled unless you don't want the terminal icon on the launcher. Each to his/her own I guess :)
Spam Hunter ( 2018-07-16 17:29:00 +0300 )edit@juiceme I was never sure (in my limited knowledge) if the dev mode opens a port which can somehow be externally exploited, e.g. when the phone is connected to my PC or in an open wifi. So I mostly disable it when not in use.
Spark ( 2018-07-16 17:38:58 +0300 )editWell @Spark it does activate sshd but only when enabled.
So just leaving it there but not active is enough to make sure noting hazy gets done.
juiceme ( 2018-07-16 17:59:08 +0300 )edit