Ask / Submit

Where are all the situations gone? Long time passing...

asked 2017-10-11 15:16:03 +0300

breiti_oi gravatar image

updated 2017-10-12 13:08:10 +0300

Hi folks!

After update 2.1.1.x the situations app could not switch the Wi-Fi any more. According to the developer, it was because third-party developers with this firmware version is denied to access these functions. Now, after the next update to 2.1.2.x situations not even seem to be able to activate the flightmode, which reminds me of times when firmware 1.x.x.x was still marked as beta, no situations app for sfos was released and i had to switch everything by hand. That's also the reason why i marked this this question as bug, but jiit seems not to like this. ;)

So Jolla team, are there plans to be able to run timed or otherwise controlled tasks within the ambiances? Or is there anything else I can do to keep situations working, maybe with shell scripts?

EDIT: I just found >>THIS<<. So as workaround, i set the commands for enable/disable flightmode for user nemo within the sudoers file and call it within situations as a terminal command.

edit retag flag offensive close delete



This is how I fixed the wifi and bluetooth issues. You will needto install some sofware from OpenRepos though...

g ( 2017-10-11 15:46:49 +0300 )edit

@g thanks, at least i can the switch my wifi again :)

breiti_oi ( 2017-10-11 18:48:32 +0300 )edit

You don't necessarily need to install packages from OpenRepos. All you need is sudo (which can be installed form the mer-tools repository, see ), then you can add a sudo rule for nemo which allows to change / toggle connectivity via a command. I use this to disable WiFi when I'm away from home.

ghling ( 2017-10-12 17:25:27 +0300 )edit

@ghling which command do you use for switching the wifi? I tried with mcetool --disable-radio=wlan but it doesn't works

breiti_oi ( 2017-10-12 19:53:03 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2017-10-11 17:15:27 +0300

Jolla is increasing the security of SFOS by denying user applications access to low level DBus API's. Only privileged apps (aka root) can access those DBus API's now.

edit flag offensive delete publish link more



Clear. But not always great. So howto make situations privilleged?

pawel ( 2017-10-11 18:02:03 +0300 )edit

Well, increasing the security is one important thing and i really appreciate it, but what will be the next improvement? Maybe the user phonebook also represents a security risk, get blocked and you can "easily" enter the phone numbers by hand, instead of storing them? There must be some way to handle this for normal users, otherwise SFOS remains an operating system for "ambitious users", but not for the mass.

breiti_oi ( 2017-10-11 18:06:24 +0300 )edit

@pawel: How about using sudo to call situations?

breiti_oi ( 2017-10-11 18:07:52 +0300 )edit

You may give a look to /usr/share/mapplauncherd/privileges, it allows some of my personal executables to access people data for instance. Use at your own risks. And of course it's forbiden by harbour rules to modify this file.

Damien Caliste ( 2017-10-12 01:56:45 +0300 )edit

Is there a list of such api's?

tortoisedoc ( 2017-10-12 13:18:14 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2017-10-11 15:16:03 +0300

Seen: 775 times

Last updated: Oct 12 '17