[08:14] <OlofL> If I install beta 1804.  will I get 1804 LTS when it is released or will I continue to use use beta software?
[08:17] <Faux> OlofL: You can switch between beta and LTS at any time; I don't know what the installer does today, but it's just a config option.
[08:19] <lotuspsychje> !final | OlofL 
[08:19] <ubottu> OlofL: If you install a development version of Ubuntu bionic and keep up with package updates, then you will be upgraded to the official release of 18.04 when it comes out. To make sure, type « sudo apt update && sudo apt full-upgrade » in a terminal.
[08:19] <OlofL> Faux: so if I change to LTS on launch date, there will be no installed beta software and everything if there are beta software installed it will revert to whatever is in lts _
[08:19] <OlofL> ?
[08:20] <Faux> In theory, yes! In practice, some stuff is fixed on installation and there's nothing you can do about that. In the same wy that if you install the 1604LTS today, then upgrade to 1804LTS on release, you wouldn't have the same system as if you just installeed 1804.
[08:20] <ducasse> OlofL: you don't change anything, you just update packages. update on launch day, and you will be on the final release
[08:44] <OlofL> How do I know if I am on lts beta or some kind of bleeding edge supertest build?
[08:46] <SwedeMike> OlofL: if you installed the beta, then you just keep doing dist-upgrade and you'll end up with the relase version. 
[08:47] <SwedeMike> OlofL: ubuntu is not a "build", it's a lot of different packages combined into something, and each of these packages can be updated at any given time. Recommendation is to stay updated.
[11:18] <Exterminador> hello guys. anyone knows how to solve this?  https://www.irccloud.com/pastebin/YpZHVPTc/
[11:42] <forester> Hi. Does beta-ubuntu Kylin have UKUI? if not then what it have?
[11:43] <forester> And what is better to do? Download beta1 or daily build?
[11:46] <forester> I meant daily-live or beta1.
[11:47] <forester> I am going to download for testing (using). What is better to download?
[11:47] <forester> bet1 or daily-live?
[11:47] <forester> beta1*
[12:15] <tomreyn> if you don't mind broken functionality (may be fully broken), get the latest
[12:16] <tomreyn> if you want something recent, but hwere much already works, get the beta
[12:22] <tomreyn> http://www.ubuntukylin.com/Community/show.php?lang=cn&id=313
[12:22] <forester> tomreyn: Thank you. I suppose so.
[12:23] <tomreyn> about ukui, i suggest you check on their forums https://www.ubuntukylin.com/ukylin/portal.php
[12:24] <tomreyn> https://www.ubuntukylin.com/ukylin/forum.php?mod=viewthread&tid=179907  says 'UKUI'
[13:54] <enyc> TJ-: meow
[13:55] <enyc> TJ-: can you post on bug  1601997  about your server use-case example?
[13:55] <ubottu> bug 1601997 in e2fsprogs (Ubuntu) "Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs" [High,Triaged] https://launchpad.net/bugs/1601997
[13:55] <enyc> TJ-: and add to the mailing-list-thread thats' been started?
[13:56] <TJ-> enyc: once I've done the tests
[13:57] <enyc> ok juts it needs to go through quickly soon to get discussed in time
[13:57] <enyc> TJ-: i tested and found grub2 NOT a problem even back to 14.04
[13:57] <enyc> i.e. bios-based multibooting not a problem
[13:58] <TJ-> right, the GRUB ext code is mostly ext2/3/4 compatible and ignores extended features
[13:59] <enyc> yes, though some anecdotes suggested possible issues, so i tested explicitly
[13:59] <enyc> cjwatson looked in grub git tree etc and thought there SHOULDN'T be, and i confirmed in practice, as far as I could tell
[14:15] <TJ-> well Colin is rather familiar with the codebase as a former and occassional GRUB developer :)
[14:23] <enyc> nodsnods
[14:24] <enyc> you are doing test on datnacentre cases, ISCSI host case aiui
[14:25] <TJ-> yes
[14:25] <enyc> just putting some mentions into bug anyway as some pontis
[14:33] <enyc> TJ-: posted on above bug nonetheless
=== J03Y is now known as j03y
[17:48] <demuxer>  What's your main innovation for the Bionic release?
[17:56] <nacc> demuxer: this is the support channel
[17:56] <nacc> demuxer: do you have a support topic?
[19:03] <FurretUber> Hi, my QEMU virtual machines using -vga qxl are crashing: https://paste.ubuntu.com/p/FMKPtbyhZm/
[19:04] <FurretUber> Initially I would run that command as root, but I've added my user to disk and kvm groups, so it is running as my user
[19:05] <FurretUber> It was supposed the problem was because, when running them as root, the DISPLAY variable was not available. However, this crash happened as a normal user
[19:19] <FurretUber> I can't report the bug (I'm trying with: ubuntu-bug /var/crash/_usr_bin_qemu-system-x86_64.1000.crash) as it says the core dump is invalid
[19:37] <pgoetz> I've installed 18.04 on a couple of systems with Nvidia video cards + nvidia-390 drivers.  On both systems different applications spit out the following error message: libGL error: failed to load driver: swrast 
[19:39] <pgoetz> Googling hasn't offered a clue as to why this is happening.  
[19:39] <Faux> Are you up to date? There were some issues that have been resolved by updating libegl (about a week ago).
[19:40] <pgoetz> Hi - yes, I'm up to date.  I just checked 5 minutes ago.
[19:41] <Faux> Oh no! :)
[19:41] <pgoetz> Also, I don't think the Nvidia drivers use the Mesa GL libraries?  I think they have their own.
[19:42] <archetech-U> yup
[19:43] <pgoetz> Maybe the Nvidia drivers just aren't ready for 18.04, although I can't imagine why not.  On the newer GTX cards nouveau seems to be horribly unstable, which is why I went to the proprietary drivers.
[19:43] <Faux> The 390 drivers are pretty screwed performance wise for me, but nobody seems to care. :)
[19:44] <pgoetz> @Faux have you tried downgrading to an earlier release?
[19:45] <Faux> Of the drivers? They're not available in 18.04. Of Ubuntu? Nah, it'll get fixed or I'll be reinstalling.
[19:45] <pgoetz> Also, has anyone else noticed a power regression introduced with an update a few days ago?  One machine was happily working until an update on Monday (03/12).  Now the machine seems to be spontaneously suspending after some amount of time  even though suspend is turned off.
[19:47] <pgoetz> OK, failed to take note that only the 390 drivers were available for 18.04 -- thanks for saving me some time.
[19:47] <pgoetz> On what card is the 390 performance bad?
[19:48] <pgoetz> I haven't noticed anything on GTX 1070 or GTX 1050 Ti
[19:50] <Faux> I'm on a 1050Ti. It doesn't appear to be universal, which doesn't help with people caring about it.
[19:51] <pgoetz> What are the details of your performance issues?  I'm wondering if my 1050Ti machine is having similar problems, but the user doesn't notice because he uses graphics fairly minimally.
[19:53] <pgoetz> Also, assuming you've upgraded to 390.42
[19:53] <pgoetz> There were issues with 290.25
[19:53] <pgoetz> 390.35
[19:53] <pgoetz> I can't type:  390.25
[20:01] <Faux> The easiest way to reproduce it is to play with satellite/birdseye in binary Google Chrome.
[20:01] <Faux> In Google Maps.
[20:02] <Faux> There's a bug but my network is crapping out too much to find it. >.<
[20:02] <Faux> (Because I'm in a tunnel, not because I'm running 18.04; different machine.)
[20:03] <Faux> https://bugs.launchpad.net/bugs/1755182
[20:03] <ubottu> Launchpad bug 1755182 in nvidia-graphics-drivers-390 (Ubuntu) "Horrendous latency in Chrome" [Undecided,New]
[20:13] <pgoetz> @Faux I would take this upstream to nvidia.  I can't fathom how it would have anything to do with 18.04/4.15 kernel/gnome
[20:14] <Faux> There's already a useless forum thread. I want Ubuntu not to release with 390.
[20:14] <Faux> (I know that wont' happen.)
=== czesmir_ is now known as czesmir