# Deactivating developer mode takes forever

Tracked by Jolla (In release)

I am on Xperia X and SF 2.2.0.29. When deactivating developer mode via settings menu, the status bar appears but doesn't see any progress. This stays there for minutes until I press the back button. Restart doesn't solve the problem. Is it possible to disable dev mode via terminal?

update: It doesn't take forever but 3 minutes or longer. So lets try to find a reason.

edit: on 3.0.2.8 same behaviour when activating developer mode. Had it active when i updated from 3.0.1...

edit retag close delete

1

@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.

( 2018-07-15 15:36:53 +0300 )edit

Why would one want to disable it anyway?

( 2018-07-16 17:26:58 +0300 )edit
1

I 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 :)

( 2018-07-16 17:29:00 +0300 )edit
1

@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.

( 2018-07-16 17:38:58 +0300 )edit
1

Well @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.

( 2018-07-16 17:59:08 +0300 )edit

Sort by » oldest newest most voted

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.

more

Thanks to @Edz and @omeena for the answers. It indeed works after 3-5min waiting.

Now when I try to access the developer tools I get "checking status" for around two minutes until I even see the dev tools menu.

I think this behavior is not intended by jolla, I hope this is a known bug now. Changed the title accordingly.

more

I noticed the same behavior: "Checking status" loading screen when opening developer tools and "Preparing changes" when disabling them, both staying there for a long time without showing any progress.

I don't know if this is related, but I also have troubles connecting to the device via SSH after enabling developer tools / remote connections. This can be solved by restarting the network connections in the Utilities. I'm not sure, but I'll investigate the issue further.

( 2018-07-16 11:06:29 +0300 )edit

A fix for this problem will be included in an upcoming release. Sorry for the trouble and thanks for your patience.

more

Thanks a lot for considering. I'll close the thread in good faith for the upcoming fix ;-)

( 2018-08-14 16:02:04 +0300 )edit

same for me, but after waitimg for 15 to 20 mins , I can see the option. this was not the case with earlier releases. Same prolong time occurs while deactivating the dev opt.

more