[07:28] <elbrus> jbicha: right. And upstream is probably willing to carry it as well.
[07:28] <elbrus> it should have been upsteamed long ago
[09:55] <JackFrost> LocutusOfBorg: Hrm, what was the reason to switch remmina away from ayatana indicators?
[11:27] <ginggs> flexiondotorg: Happy new year! do you think you could add Conflicts: telegram-desktop to your telegram PPA packages please?  It would prevent future bugs like LP: #1740708
[11:27] <ubottu> Launchpad bug 1740708 in telegram-desktop (Ubuntu) "package telegram-desktop 1.1.23-1 failed to install/upgrade: trying to overwrite '/usr/share/applications/telegramdesktop.desktop', which is also in package telegram 1.1.23-1~artful1.0" [Undecided,Invalid] https://launchpad.net/bugs/1740708
=== ogra_ is now known as ogra
[15:39] <Bh_> Hi, which kernel version does Ubuntu 18.04 nightly got? does it fix the issue which made 17.10 download link removed from ubuntu.com site?
[15:47] <acheronuk> Bh_: 4.13.0-17, which according to the bug report was never affected
[15:49] <Bh_> acheronuk: kewl, I think on installing it instead of 16.04 on my laptop, how stable is it?
[15:49] <acheronuk> Bh_: no idea. I run Kubuntu. That is is stable, which is all I can comment on
[15:51] <Bh_> acheronuk: Kubuntu nightly?
[15:51] <Bh_> or 17.10?
[15:51] <acheronuk> Both
[15:52] <Bh_> ok, kewl and thx :)
[15:56] <acheronuk> Bh_: development version is meant to be reasonable stable nowadays, but I would still only suggest running it if you have some significant experience running (and occasionally fixing) pre-release stuff
[15:58] <Bh_> acheronuk: I had 16.04 already and I wasn't able to make my second monitor (which is connected with HDMI to the laptop) to work no matter what I did (spent few good hours on it), if I remember correctly it was cause 16.04 didn't really knew how to work with laptops which got a gpu and a video card and it was said that it was fixed later on
[15:59] <Bh_> so I'm kinda stuck now
[16:00] <acheronuk> Bh_: fair enough. I'm just doing the mandatory (beware the -dev version may kill your kittens, type) warning ;)
[16:01] <acheronuk> albeit that most people developing it also run it with good stability.....
[16:02] <Bh_> acheronuk: hehehe thanks, I'll keep considering it
[16:02] <Bh_> It's those trailing dots which terrify me..... ;)
[16:03] <Bh_> acheronuk: btw, doesn't Ubuntu 16.04 will do an update to the buggy kernel? (guess not.... but just to be sure :))
[16:04] <Bh_> I'm more from the Internet server side systems development side of life :)
[16:04] <Bh_> minus the server itself though...
[16:06] <Bh_> acheronuk: btw I rechecked and its said at the bug report "Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous affected machines still suffered from a broken BIOS." so the nightly is stll bugged
[16:09] <acheronuk> Bh_: no, it's not. as the Bionic -release version never had the buggy driver enabled
[16:10] <acheronuk> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147
[16:10] <ubottu> Launchpad bug 1734147 in linux (Ubuntu) "Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models" [Critical,Confirmed]
[16:10] <acheronuk> Bionic is not an affected series
[16:10] <Bh_> acheronuk: ok so now I'm confused... its not only connected to the kernel version but also to something else?
[16:11] <Bh_> ahhhh artful & xenial are the series?  (did I mention that this is not my field? :))
[16:13] <acheronuk> Bh_: correct. I'm not usre if the buggy version was ever uploaded to bionic, but it certainly did not get to the -release pocket and hence the iso's from the info in that bug
[16:17] <Bh_> acheronuk: honestly I don't totally follow u.... :)
[16:17] <Bh_> how can u be sure about that?
[16:20] <dobey> are you on a lenovo laptop?
[16:22] <Bh_> dobey: HP
[16:23] <dobey> HP 14-r012la
[16:23] <dobey> that one?
[16:23] <Bh_> Nope, but I don't want to be the one will report my model ;)
[16:25] <Bh_> I got an Insyde BIOS for once...
[16:25] <acheronuk> Bh_: because the current kernel in bionic is the same as the artful one from before the bug was introduced
[16:27] <Bh_> also tried to upgrade 16.04 to 17.10 about a month ago, entire installation just crushed and Ubuntu never responded anymore no matter what I did, I got a new HD now and considering what to do
[16:29] <Bh_> acheronuk: according to https://bugzilla.kernel.org/show_bug.cgi?id=195951 the bug exist from at least kernel 4.11.2
[16:29] <ubottu> bugzilla.kernel.org bug 195951 in Other "Booting kernel 4.11 triggers a reset of UEFI firmware settings on the next boot" [Normal,New]
[16:32] <dobey> assuming it's a kernel bug
[16:34] <Bh_> dobey: thats the bug ticket which is mentioned at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147 . honestly I think I'll just be safe and go for 16.04 for the time being, that's supposed to be a safe option for the time being, right? (the kernel wont get updated to the buggy version and such...)
[16:35] <ubottu> Launchpad bug 1734147 in linux (Ubuntu) "Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models" [Critical,Confirmed]
[16:46] <dobey> well, the hwe stack is supposed to get upgraded to the 17.10 kernel in the next few weeks
[16:46] <dobey> but i don't know how this issue will affect that schedule
[16:47] <dobey> #ubuntu-kernel is probably a better place to ask about kernel specific issues
[16:48] <Bh_> dobey: kewl thanks :)
[16:48] <Bh_> acheronuk: thanks again :)
[16:48] <Bh_> cheers!
[16:49] <acheronuk> I *think* the affected kernel only went into the hwe-edge channel so far on 16.04. at least, that was the channel the 16.04 fix was pushed to
[17:00] <acheronuk> and looks like the bionic kernel in -release is actually affected. concerning