Command to delete all of those files:

phablet@ubuntu-phablet:~$ rm ~/.cache/upstart/untrusted-helper-*

@that_rin So I've tried a couple of restarts and I've managed to get it "stuck" again. But the solution appears to be this simple:

phablet@ubuntu-phablet:~$ sudo restart ubuntu-location-service

My preferred method for using this workaround (worked a couple of times now):

1. Before restarting, turn on Wi-Fi and Location detection
2. Restart
3. Run sudo restart ubuntu-location-service from the terminal
4. Open the SensorsStatus app and navigate to the GPS screen
5. Wait until the GPS starts working

When it comes to testing on the device itself, the one thing I'd add is taking advantage of clickable --dirty.

http://clickable.bhdouglass.com/en/latest/commands.html?highlight=dirty:

A dirty build without cleaning the build dir can be achieved by running clickable --dirty.

This saves a lot of time at that stage of testing.

@hummlbach You're welcome.

The theme switcher is now available in v0.4.8 so no longer need to manually install the .click. Here's hoping that SuruDark gets more love over time.

Apologies to all for the mass call-outs used in this post -- I wouldn't usually do this. I've encountered a situation where extending rootfs and all subsequent customisations are lost. I'm sharing this as a warning for those who have already resized, a caveat for those considering to do so, and as a discussion point for how to move forwards.

Switching the release channel loses the extended rootfs

With hindsight, there's nothing surprising about this since the process of switching channels replaces /userdata/ubuntu.img.

@haveaniceday above:

Of course, this will probably break OTA updates...

@UniSuperBox above:

The image file can be resized, and I'm considering ways to make ubports-qa do this in case the user would prefer to use apt and turn off system-image upgrades.

I never had any issues with OTA updates, even after some fairly extensive hacking and customisations. Other than switching the channel, what other system-image upgrades could lead to this outcome?

Moving forward

@haveaniceday above:

I'll just repeat the steps for each release.

Essentially, this is all that can be done. But I managed to do some decent testing and found that this reconfiguration process can be made much easier. In my case, I made promising progress with SaltStack configuration management. Solutions involving tools such as this become viable once rootfs has been extended (in that the necessary packages can be installed). It wouldn't be too difficult to have a repo for collecting formulas that help automate this.

@vandys @arubislander @doniks Since you all appear to have gone through the resizing process, I hope you don't mind me drawing your attention to this post.

@Beton There was a DNS issue that needed to be resolved and an upgrade has also been performed during the downtime. Please use the following workaround for the time being: for the homeserver, append :8448 to the URL. So ubports.chat:8448 instead of ubports.chat.

Hey @that_rin, I'm with you. In my case, GPS has never worked, but I've only started using UBports recently, since the problems began. I did get a few suggestions from the main Telegram group, so I'm going to bring those over to this discussion, in case they provide any useful leads.

Debugging resource

myii, [18.11.18 01:11]
GPS has never worked on my Nexus 5 since first installation. SensorsStatus doesn't show any values. uNav has never resolved correctly. GPS is enabled and for each of the apps. What's the right way to troubleshoot this?

Rodney, [18.11.18 01:15]
[In reply to myii]
https://wiki.ubuntu.com/Process/Merges/TestPlan/location-service#Debugging

Rodney, [18.11.18 01:15]
ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles is probably of particular interest

myii, [18.11.18 01:26]
[In reply to Rodney]

phablet@ubuntu-phablet:~$ ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles
Attempted to unregister path (path[0] = com path[1] = ubuntu) which isn't registered
Problem executing the CLI: org.freedesktop.DBus.Error.ServiceUnknown: The name com.ubuntu.location.Service was not provided by any .service files

Rodney, [18.11.18 01:27]
i think you might need to run it with sudo

myii, [18.11.18 01:28]
Exact same output as above with sudo.

Starting ubuntu-location-service

Rodney, [18.11.18 01:27]
or maybe that means the location-service isn't running

Rodney, [18.11.18 01:28]
does it appear in ps afx|grep location output?

myii, [18.11.18 01:28]

 3777 ?        Ssl    0:00          \_ /usr/lib/arm-linux-gnueabihf/indicator-location/indicator-location-service
 7674 ?        Tsl    0:02          \_ system-settings settings:///location
23356 pts/19   S+     0:00              \_ grep --color=auto location
14209 ?        Ss     0:00 /usr/bin/ubuntu-location-provider-geoclue2

Rodney, [18.11.18 01:29]
try running sudo start ubuntu-location-service

myii, [18.11.18 01:30]

phablet@ubuntu-phablet:~$ sudo status ubuntu-location-service
ubuntu-location-service start/running, process 23508

myii, [18.11.18 01:31]
ubuntu-location-serviced-cli still returning the previous output.

Error in /var/log/syslog

myii, [18.11.18 01:31]
Noticed this in syslog:

Nov 18 00:37:58 ubuntu-phablet kernel: [ 1488.385225] init: ubuntu-location-provider-geoclue2 main process (9716) killed by SEGV signal
Nov 18 00:37:58 ubuntu-phablet kernel: [ 1488.385259] init: ubuntu-location-provider-geoclue2 main process ended, respawning

---

So no progress so far.

Potential solution (not just a workaround)

After various research and testing, I believe that I have a potential solution. Since the changes, my GPS is now usable and reliable. I can switch it on and off and still expect it to work, no workarounds necessary.

The fix has very simple changes that are reversible. Doesn't appear to be limited to Nexus 5, either.

The solution being tested:

* Simply change the GPS provider from wolfpack.geoclue2 to ubuntu.espoo

Steps to test the potential solution

1. Check that the fix is even needed (may already be using ubuntu.espoo) -- run in the terminal:

$ ps aux | grep [l]ocation-service | grep provider
root       987  0.0  0.5 146540  9852 ?        Ssl  19:19   0:00 /usr/bin/ubuntu-location-serviced --bus system --provider gps::Provider --provider remote::Provider --remote::Provider::name=com.ubuntu.espoo.Service.Provider --remote::Provider::path=/com/ubuntu/espoo/Service/Provider

* Like above, if you see ubuntu.espoo in the output, then the fix is already in place
* The fix below only works if you see wolfpack.geoclue2

2. Run the following commands from the terminal:

# -------------------------------------------
# **NO LONGER REQUIRED, IGNORE THIS SECTION**
# -------------------------------------------

# (Optional) Save a copy of the file to your home directory
$ cp /etc/init/ubuntu-location-service.override ~

# Make the root partition writable 
$ sudo mount -o remount,rw /

# The following command changes `wolfpack.geoclue2` to `ubuntu.espoo` in both places in the file
$ sudo sed -i -e 's:wolfpack\(.\)geoclue2:ubuntu\1espoo:' /etc/init/ubuntu-location-service.override

# (Optional) Check that the changes have been made successfully
$ grep espoo /etc/init/ubuntu-location-service.override
    opts="$opts --remote::Provider::name=com.ubuntu.espoo.Service.Provider"
    opts="$opts --remote::Provider::path=/com/ubuntu/espoo/Service/Provider"

[Update] Start from here:

3. Before restarting, turn on Wi-Fi and Location detection
4. Restart
5. Open the Active Screen app and ensure that the screen stays on while attempting to get the fix
6. Open the SensorsStatus app and navigate to the GPS screen
7. Wait until the GPS starts working (the first fix can take a while)

Once the GPS starts working, it should be fine with the various apps that use it, such as uNav, OpenStreetMap, GoogleMaps UT, etc.

Steps to reset to the original configuration

1. Run the following commands from the terminal:

# -------------------------------------------
# **NO LONGER REQUIRED, IGNORE THIS SECTION**
# -------------------------------------------

# Make the root partition writable 
$ sudo mount -o remount,rw /

# Reset back to `wolfpack.geoclue2`
$ sudo sed -i -e 's:ubuntu\(.\)espoo:wolfpack\1geoclue2:' /etc/init/ubuntu-location-service.override

# (Optional) Check that the changes have been made successfully
$ grep wolfpack /etc/init/ubuntu-location-service.override
    opts="$opts --remote::Provider::name=com.wolfpack.geoclue2.Service.Provider"
    opts="$opts --remote::Provider::path=/com/wolfpack/geoclue2/Service/Provider"

* The reset will be complete once you restart

I removed all bookmarks from all folders

@wartburgritter So you want to clear all bookmarks and start over? If so, a direct way of doing that is by deleting (or renaming) ~/.local/share/morph-browser/bookmarks.sqlite. When you reopen Morph, bookmarks will be reset to the default.

This has worked for numerous users: https://forums.ubports.com/post/13645.

I've found running these commands works more reliably from fastboot mode.

@Beton If the above works for you, then please mark this post as resolved. Thanks.

@Beton OK, it should be fixed now and you shouldn't have to change anything. Just use ubports.chat as you originally were. Apologies for the loss of service.

@Beton There was a DNS issue that needed to be resolved and an upgrade has also been performed during the downtime. Please use the following workaround for the time being: for the homeserver, append :8448 to the URL. So ubports.chat:8448 instead of ubports.chat.

@Flohack All working well since. Just found another couple of logs that are still "unhandled":

- Unhandled push type:  "CHAT_MESSAGE_GIF"
- Unhandled push type:  "PINNED_TEXT"

Command to delete all of those files:

phablet@ubuntu-phablet:~$ rm ~/.cache/upstart/untrusted-helper-*

This has worked for numerous users: https://forums.ubports.com/post/13645.

I've found running these commands works more reliably from fastboot mode.

@obacht This has come up a few times in the UBports Telegram groups. The last example was only yesterday:

Tom Rhodes, [07.04.19 14:06]
Hey does anyone know why a fresh install is taking up 29.6Gb of a nexus 7 (flo)?

Tom Rhodes, [07.04.19 14:11]
[ Photo ]

Tom Rhodes, [07.04.19 14:12]
29.5 to be exact

Rodney, [07.04.19 14:14]
You had about that much space used up under Android? And didn't select wipe option in installer?

Tom Rhodes, [07.04.19 14:15]
nope i had wipe selected

Tom Rhodes, [07.04.19 14:15]
doing an erase and reset from the OS to see if it can clean up

Tom Rhodes, [07.04.19 14:17]
that seemed to work

Tom Rhodes, [07.04.19 14:18]
I now have 26Gb free

Tom Rhodes, [07.04.19 14:18]
wipe was selected on the installer, but it dropped the connection when pushing once, about halfway through, then it restarted, so maybe that might have somethign to do with it

So reinstalling with wipe selected should do the trick. If you've got any more concerns, it's probably best to join the Welcome and Install group on Telegram and ask there: https://t.me/WelcomePlus.

@lduboeuf Maybe @kugiigi can be more specific but I know he was working on this recently. Probably:

• https://github.com/kugiigi/palitan-app

Good work! We need to get @nanu-c on here to get some more comparisons...

I removed all bookmarks from all folders

@wartburgritter So you want to clear all bookmarks and start over? If so, a direct way of doing that is by deleting (or renaming) ~/.local/share/morph-browser/bookmarks.sqlite. When you reopen Morph, bookmarks will be reset to the default.