[01:07] <Guest98316> folks , i would like install beta version kylin 18.04 over my ubuntu 17.04 that Iḿ using now... can I do it without lost data?
[01:08] <bazhang> Guest98316, have you burned the iso to usb
[01:09] <Guest98316> all right... but during the instalation, how i need proceed instalation without keep my data? 
[01:09] <Guest98316> *how i need proceed installation keeping my data
[01:09] <bazhang> Guest98316, did you see the preserve /home option in the installer
[01:10] <Guest98316> understanding
[01:10] <Guest98316> tks bazhang
=== lisbeths is now known as johnnymacs
[05:25] <DarinMiller> anyone know how to enable dns from 18.04 recovery shell?
[05:26] <DarinMiller> adding nameserver x.x.x.x to /etc/resolv.conf is no longer an option.
[05:27] <DarinMiller> systemctl enable systemd-resolved    fails to find the service.
=== johnnymacs is now known as dorothyw
[05:54] <valorie> DarinMiller: sounds like a bug
[05:54] <valorie> is there one?
[05:56] <DarinMiller> I don't thinks its a bug, but the correct way to enable dns from the root recovery prompt is challenging to discover.
=== dorothyw is now known as johnnymacs
[07:37] <uzbek> hi
[07:37] <uzbek> i installed 17.10. how can i upgrade to 18.04 beta?
[07:38] <tsimonq2> uzbek: sudo do-release-upgrade -d in a terminal.
[07:38] <tsimonq2> Note that things could break; it's only a Beta.
[07:39] <flocculant> it's not even a beta :p
[07:54] <tsimonq2> Depends on how you look at it flocculant :P
[07:56] <flocculant> I look at it properly - there is no Ubuntu Beta, there are a some flavour Beta's - Ubuntu won't have a beta until after the Final Beta milestone, until then they only have dailies (assuming that it builds)
[10:06] <CoJaBo> Are there any known issues with Bionic running with IOMMU enabled? I have pretty severe instability and device hangs/errors without iommu=soft; not sure if OS bug, or something else
[11:22] <tomreyn> CoJaBo: not that i know of (it would be ridiculous to release with this kernel version if this was a general issue, but i'm sure it's not). check system logs and dmesg, check for bios / uefi upgrade availability, try a mainline kernel.
[11:24] <CoJaBo> tomreyn: It's running the latest BIOS. Did manage to confirm it happens with older stable kernels too
[11:33] <tomreyn> so it's old hardware?
[11:33] <tomreyn> what about the system ogs?
[11:33] <tomreyn> *logs
[11:34] <CoJaBo> It's fairly new; Ryzen3, X370
[11:34] <tomreyn> oh a rtyzen, and you're surprised about instability :)
[11:34] <tomreyn> https://bugzilla.kernel.org/show_bug.cgi?id=196683
[11:34] <ubottu> bugzilla.kernel.org bug 196683 in x86-64 "Random Soft Lockup on new Ryzen build" [Normal,New]
[11:36] <tomreyn> So it's actually UEFI and not BIOS. Disable "Power Supply Idle Control" and maybe C6, that should help.
[11:36] <CoJaBo> tomreyn: In most cases, the system just dies; these are the logs I've been able to get, all of them issues with various SATA cards: https://bugzilla.kernel.org/show_bug.cgi?id=196683
[11:37] <ubottu> bugzilla.kernel.org bug 196683 in x86-64 "Random Soft Lockup on new Ryzen build" [Normal,New]
[11:37] <tomreyn> that'S the same link i posted
[11:37] <CoJaBo> Not sure why it didn't copy: https://paste.debian.net/1013355/
[11:38] <tomreyn> when you say "the system dies" what does this look like, what do you see on screen, does it power off, reboot by itself?
[11:38] <tomreyn> or freeze?
[11:38] <CoJaBo> All LEDS go off, and monitor goes to standby, fans/PSU keep running
[11:39] <tomreyn> hmm those are sata errors. bad cable?
[11:40] <CoJaBo> Tried replacing SATA cable, drive, and controller. Only thing that makes any difference at all is setting iommu=soft
[11:41] <CoJaBo> Also tried different PCIe ports; same problem each, unless that option is set
[11:41] <tomreyn> it could be an issue with insufficient voltage or unstable currents.
[11:42] <tomreyn> (i.e. bad / insufficient / incorrectly wired power supply)
[11:43] <CoJaBo> It'd seem pretty weird for a kernel parameter to fix a PSU issue
[11:44] <tomreyn> true, i was assuming coincidence
[11:44] <CoJaBo> I did check the voltages at least with a multimeter, and it didn't pick up anything odd
[11:44] <CoJaBo> The SATA errors are reproducable 100% of the time; turning off that parameter causes them to happen again
[11:47] <tomreyn> okay this prooves me wrong, i guess
[11:47] <CoJaBo> The crashes were random, usually happening when dealing with SATA hotplug or SATA errors (I'm not sure if the first SATA errors, not in that log, were related to the problem; at that time, I figured it was a bad drive, and discarded it). Nonetheless, it has so far never crashed with iommu=soft, and had never made it more than 24 hours uptime without.
[11:47] <CoJaBo> The system also will not boot from a drive connected to that controller, as GRUB cannot find it. Tho that could be an entirely unrelated bug
[11:49] <tomreyn> i still think giving the "Power Supply Idle Control" option a shot can be worth it.
[11:50] <CoJaBo> I think my BIOS calls it something different, but it crashes in both settings
[11:50] <CoJaBo> I also turned off "Cool&Quiet" (which also might be the same thing), with no effect
[11:50] <tomreyn> that's something else
[12:02] <elhoir> hello guys
[12:02] <elhoir> seems that latest clamav update for bionic conflicts with spotify and virtualbox O_O
[12:02] <elhoir> how is that possible?
[12:03] <elhoir> https://pastebin.com/uRUgE2bW
[12:04] <elhoir> i made some tests, libvpx4 package is no longer available in bionic
[12:04] <elhoir> and virtualbox-5.2 depends on it
[12:04] <elhoir> in bionic it is named libvpx5
[12:06] <elhoir> is that a bug in virtualbox? in Ubuntu? none? both?
[12:31] <tomreyn> elhoir: it's hard to understand the output since it's not in english. you can create english language output by running "export LANG=C" before you run further commands (which then produce errors).
[12:32] <tomreyn> however, your output seem to indicate that there is no need for the libvpx4 package, it just points out that it's no longer needed and could be removed.
[12:33] <tomreyn> there is no package "virtualbox-5.2" in bionic, so if you have this from a third party (probably virtualbox's upstream apt repository) and it conflicts with bionic then that's not something ubuntu can fix.
[17:01] <stochastix> Whats the best way to keep 18.04 up to date with dev changes right now? apt-get upgrade perhaps?
[17:18] <stochastix> Reason im asking is because I did update and upgrade and dist-upgrade, and didnt get a lot of new packages, but I figure since it is in development there maybe should be more changes than what I saw.
[17:29] <TJ-> stochastix: 'apt update; apt full-upgrade'
[17:55] <stochastix> TJ-: Thanks, ran full-upgrade and looks like its already up to date then.
[18:19] <stochastix> What repo is php7.0-mcrypt supposed to be in?
[18:19] <stochastix> or even 7.2,  I cant find either
[18:20] <Faux> Didn't mcrypt get deprecated a long time ago?
[18:20] <stochastix> oh, maybe?  Im following a walkthrough for Nextcloud 13 on 18.04 and the person "installed" mcrypt
[18:21] <stochastix> ill look into it more thanks.
[18:21] <Faux> Or became part of core or something.
[18:22] <Faux> There's a php-mcrypt package in Artful so probably not. :)
[18:22] <stochastix> On the official NC 13 installation page they are still showing it as a recommended package too
[18:22] <stochastix> I dont think I need it right now anyways