search

kinu-garage / hut_10sqft

Computer setup tools for my own environment, and public discussion place holder.
2 stars 1 forks source link

[serval] Can't logon desktop after upgrading to 18.04 #282

Closed 130s closed 5 years ago

130s commented 6 years ago

ssh does get through. I need to take deeper look.

$ tail -n 50 /var/log/syslog
Mar 28 14:45:43 130s-serval NetworkManager[1161]: <info>  [1522273543.7034] dhcp4 (wlan0):   lease time 86400
Mar 28 14:45:43 130s-serval NetworkManager[1161]: <info>  [1522273543.7035] dhcp4 (wlan0):   nameserver '8.8.4.4'
Mar 28 14:45:43 130s-serval NetworkManager[1161]: <info>  [1522273543.7036] dhcp4 (wlan0):   nameserver '8.8.8.8'
Mar 28 14:45:43 130s-serval NetworkManager[1161]: <info>  [1522273543.7036] dhcp4 (wlan0):   domain name 'hsd1.ca.comcast.net.'
Mar 28 14:45:43 130s-serval NetworkManager[1161]: <info>  [1522273543.7037] dhcp4 (wlan0): state changed unknown -> bound
Mar 28 14:45:43 130s-serval avahi-daemon[1217]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.51.
Mar 28 14:45:43 130s-serval avahi-daemon[1217]: New relevant interface wlan0.IPv4 for mDNS.
Mar 28 14:45:43 130s-serval avahi-daemon[1217]: Registering new address record for 192.168.0.51 on wlan0.IPv4.
Mar 28 14:45:43 130s-serval NetworkManager[1161]: <info>  [1522273543.7072] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 28 14:45:43 130s-serval NetworkManager[1161]: <info>  [1522273543.7092] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 28 14:45:43 130s-serval NetworkManager[1161]: <info>  [1522273543.7095] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 28 14:45:43 130s-serval dhclient[3600]: bound to 192.168.0.51 -- renewal in 32465 seconds.
Mar 28 14:45:43 130s-serval NetworkManager[1161]: <info>  [1522273543.7716] device (wlan0): Activation: successful, device activated.
Mar 28 14:45:43 130s-serval dbus-daemon[1035]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=1161 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Mar 28 14:45:43 130s-serval systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 28 14:45:43 130s-serval systemd[1]: Starting resolvconf-pull-resolved.service...
Mar 28 14:45:43 130s-serval dbus-daemon[1035]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mar 28 14:45:43 130s-serval systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 28 14:45:43 130s-serval nm-dispatcher: req:1 'up' [wlan0]: new request (2 scripts)
Mar 28 14:45:43 130s-serval nm-dispatcher: req:1 'up' [wlan0]: start running ordered scripts...
Mar 28 14:45:43 130s-serval systemd[1]: Started resolvconf-pull-resolved.service.
Mar 28 14:45:43 130s-serval systemd[1]: Reloading OpenBSD Secure Shell server.
Mar 28 14:45:43 130s-serval systemd[1]: Reloaded OpenBSD Secure Shell server.
Mar 28 14:45:43 130s-serval systemd[1]: Reloading OpenBSD Secure Shell server.
Mar 28 14:45:43 130s-serval systemd[1]: Reloaded OpenBSD Secure Shell server.
Mar 28 14:45:43 130s-serval avahi-daemon[1217]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::234b:2ecc:108a:a862.
Mar 28 14:45:43 130s-serval avahi-daemon[1217]: New relevant interface wlan0.IPv6 for mDNS.
Mar 28 14:45:43 130s-serval avahi-daemon[1217]: Registering new address record for fe80::234b:2ecc:108a:a862 on wlan0.*.
Mar 28 14:45:44 130s-serval NetworkManager[1161]: <info>  [1522273544.3470] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Mar 28 14:45:44 130s-serval NetworkManager[1161]: <info>  [1522273544.3510] dhcp6 (wlan0): dhclient started with pid 3757
Mar 28 14:45:44 130s-serval systemd[1]: Starting resolvconf-pull-resolved.service...
Mar 28 14:45:44 130s-serval systemd[1]: Started resolvconf-pull-resolved.service.
Mar 28 14:45:44 130s-serval dhclient[3757]: XMT: Info-Request on wlan0, interval 1020ms.
Mar 28 14:45:44 130s-serval dhclient[3757]: RCV: Reply message on wlan0 from fe80::425d:82ff:feef:2e62.
Mar 28 14:45:44 130s-serval NetworkManager[1161]: <info>  [1522273544.6348] dhcp6 (wlan0):   nameserver '2001:558:feed::1'
Mar 28 14:45:44 130s-serval NetworkManager[1161]: <info>  [1522273544.6349] dhcp6 (wlan0):   nameserver '2001:558:feed::2'
Mar 28 14:45:44 130s-serval NetworkManager[1161]: <info>  [1522273544.6350] dhcp6 (wlan0): state changed unknown -> bound
Mar 28 14:45:44 130s-serval NetworkManager[1161]: <info>  [1522273544.6398] dhcp6 (wlan0): client pid 3757 exited with status 0
Mar 28 14:45:44 130s-serval NetworkManager[1161]: <info>  [1522273544.6398] dhcp6 (wlan0): state changed bound -> done
Mar 28 14:45:44 130s-serval nm-dispatcher: req:2 'dhcp6-change' [wlan0]: new request (2 scripts)
Mar 28 14:45:44 130s-serval nm-dispatcher: req:2 'dhcp6-change' [wlan0]: start running ordered scripts...
Mar 28 14:45:44 130s-serval whoopsie[2004]: [14:45:44] Cannot reach: https://daisy.ubuntu.com
Mar 28 14:45:44 130s-serval whoopsie[2004]: [14:45:44] offline
Mar 28 14:45:45 130s-serval avahi-daemon[1217]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::234b:2ecc:108a:a862.
Mar 28 14:45:45 130s-serval avahi-daemon[1217]: Joining mDNS multicast group on interface wlan0.IPv6 with address 2601:204:db80:2f40:fd64:be78:c95f:7654.
Mar 28 14:45:45 130s-serval avahi-daemon[1217]: Registering new address record for 2601:204:db80:2f40:fd64:be78:c95f:7654 on wlan0.*.
Mar 28 14:45:45 130s-serval avahi-daemon[1217]: Withdrawing address record for fe80::234b:2ecc:108a:a862 on wlan0.
Mar 28 14:45:45 130s-serval avahi-daemon[1217]: Registering new address record for 2601:204:db80:2f40:c297:7e4:ffcf:309b on wlan0.*.
Mar 28 14:45:46 130s-serval whoopsie[2004]: [14:45:46] online
Mar 28 14:45:56 130s-serval ntpdate[3682]: adjust time server 97.127.68.189 offset -0.017598 sec
130s commented 5 years ago

When I rebooted, I saw log printed on CLI that says something like:

Failed to start NVIDIA daemon
130s commented 5 years ago

Switching to lightdm (as suggested) didn't help.

130s commented 5 years ago

Not sure which one exactly worked out, but after the following, I'm now able to log on to the desktop.

sudo apt-get purge nvidia*
sudo apt-get install system76-driver system76-firmware
sudo apt-get autoremove 
sudo service lightdm restart
sudo reboot