[07:35] morning boys and girls. [08:41] Server upgraded to 18.04 :) [08:41] Perfect way to spend a Sunday morning [08:52] :) [08:54] upgraded myself on friday, spotted one wacking huge bug, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603 , thus had to disable bluetooth in the bios, to make the system usage. [08:54] Launchpad bug 1767603 in linux (Ubuntu) "BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel" [Undecided,New] [08:54] usable* [10:27] it amazes me that bt is still such a maybe it will and maybe it won't on linux... [10:37] Esp when you think "hang on, Android phones are all Linux..." [10:41] i have seen flaky bt on android. my fitness tracker wouldn't sync with app on older samsung i used last year if i had bt headphones connected at same time [10:42] had to turn off bt, turn off headset, turn on bt and then sync for reliable connection [10:42] just the samsung phone, all the others have worked fine [10:43] but other phones have had their quirks too === popeycor1 is now known as popeycore [18:49] \o/ Fresh install of Bionic Beaver since upgrade failed, wouldn't mind, it was virtually bog standard with only one ppa for Java [18:51] how did the upgrade fail? I'd had this machine upgraded during the alpha/beta? [18:54] It failed on restart, hung after starting GDM, I think it was to do with nvidia from repo's, that was the next commands being run after gdm starting, but I didn't bother investigating any further [18:55] ah [18:55] I'd take out any 3rd party driver before an upgrade and add it back later [18:56] It was from the offical repo's, so I wouldn't class that as 3rd party. Fair enough its a closed source binary, but I'd have expected that to have been tested [18:57] Probably just a one off issue over some random failure though