Topics created by TLF

@lakotaubp thank you, I've updated the title to show that I am running 16.04 stable. Here are the log files in .cache/upstart as suggested. Which ones are relevant to this issue? I'll upload them to pastebin address-book-service.log.1.gz address-book-service.log.2.gz address-book-updater.log.1.gz address-book-updater.log.2.gz application-click-com.ubuntu.terminal_terminal_0.9.0.log application-click-com.ubuntu.terminal_terminal_0.9.0.log.1.gz application-click-logviewer.neothethird_logviewer_2.1.log application-failed.log.1.gz bluez-mpris-proxy.log.1.gz bluez-mpris-proxy.log.2.gz ciborium.log.1.gz ciborium.log.2.gz click-user-hooks.log.1.gz click-user-hooks.log.2.gz dbus.log dbus.log.1.gz dbus.log.2.gz dbus.log.3.gz dekkod-notify.log dekkod-notify.log.1.gz dekkod-notify.log.2.gz gnome-keyring.log.1.gz gnome-keyring.log.2.gz indicator-datetime.log.1.gz indicator-datetime.log.2.gz indicator-keyboard.log.1.gz indicator-keyboard.log.2.gz indicator-network.log indicator-network.log.1.gz indicator-network.log.2.gz indicator-network.log.3.gz indicator-network-secret-agent.log.1.gz indicator-sound.log maliit-server.log.1.gz maliit-server.log.2.gz maliit-server.log.3.gz media-hub.log media-hub.log.1.gz media-hub.log.2.gz media-hub.log.3.gz mediascanner-2.0.log.1.gz mediascanner-2.0.log.2.gz mediascanner-2.0.log.3.gz msyncd.log msyncd.log.1.gz msyncd.log.2.gz msyncd.log.3.gz mtp-server.log.1.gz mtp-server.log.2.gz nuntium.log nuntium.log.1.gz nuntium.log.2.gz nuntium.log.3.gz ofono-setup.log.1.gz ofono-setup.log.2.gz pulseaudio-trust-stored.log.1.gz pulseaudio-trust-stored.log.2.gz scope-registry.log scope-registry.log.1.gz scope-registry.log.2.gz scope-registry.log.3.gz session-migration.log.1.gz ssh-agent.log.1.gz ssh-agent.log.2.gz sync-monitor.log sync-monitor.log.1.gz sync-monitor.log.2.gz sync-monitor.log.3.gz telephony-service-indicator.log telephony-service-indicator.log.1.gz telephony-service-indicator.log.2.gz tone-generator.log tone-generator.log.1.gz tone-generator.log.2.gz ubuntu-location-service-trust-stored.log.1.gz ubuntu-location-service-trust-stored.log.2.gz ubuntu-push-client.log ubuntu-push-client.log.1.gz ubuntu-push-client.log.2.gz ubuntu-push-client.log.3.gz unity8-dash.log unity8-dash.log.1.gz unity8-dash.log.2.gz unity8-dash.log.3.gz unity8.log unity8.log.1.gz unity8.log.2.gz unity8.log.3.gz untrusted-helper-type-end-push-helper.log.1.gz url-dispatcher.log usensord.log.1.gz usensord.log.2.gz Here is /var/log/syslog https://www.dropbox.com/s/ug0632bcv34hepr/syslog.crash?dl=0 I will leave this file shared for as long as possible.

@lakotaubp Yes, Google allows me, and sends me an email to say my account is connected with a Linux Device. But I'm not connected, cause "System settings" remains spinning around and around and around the last step.

@truscellino Yes, it's still happening for me. Tapping the network name again doesn't help the situation. Surprisingly, turning WiFi off and on again doesn't help either (I would have expected this to work). The only solution is to turn airplane mode on and off again or to reboot the phone. I recently changed the channel my router uses and it had no effect on this issue. Good luck with your investigations. I have only one router and no convenient way to test others.