[01:21] <quidnu> Are there any known bugs preventing sound from working on bionic with intel-hda ?
[03:53] <CoJaBo> Is there anyway to debug why ubuntu bionic (server) is freezing? has been stable for several weeks now, and now has frozen up twice in 2 days
[03:55] <slidinghorn> CoJaBo: What exactly is "Freezing?"  
[03:56] <CoJaBo> It just completely stops responding; no response to keypress, can't ping it, display is on but no errors were printed
[03:59] <CoJaBo> There hadn't been any changes made in the several weeks before the first crash; nothing installed, updated, reconfigured, or rebooted at all, and the machine was mostly just sitting idle
[03:59] <slidinghorn> CoJaBo: first place to look is in /var/log/  and look at the syslogs from when it crashed
[04:00] <CoJaBo> After that, I updated everything, rebooted, and just left it sit; it wasn't even running most of the usual stuff (sshfs/fileserver), as I hadn't started that again
[04:01] <CoJaBo> There's nothing in /var/log/ that I can find from around the time of the crash; the last entry was several weeks prior, the one that'd been printed to console (from when I'd mounted a filesystem)
[04:01] <slidinghorn> CoJaBo: that's not possible.
[04:02] <CoJaBo> There's a few things from cron or logins or something, but they aren't errors and are also mostly hours before since the system was almost completely idle when it crashed
[04:03] <CoJaBo> slidinghorn: is there anything it's possible to determine from the system while it's still on and frozen?
[04:05] <slidinghorn> CoJaBo: Doesn't sound like ssh would respond, but you can try.  I guarantee you there's something in one of the syslogs in /var/log that will give you a hint, though.  Your statement that there's nothing beyond a couple weeks ago is simply not possible.
[04:06] <CoJaBo> slidinghorn: I had an ssh connection open (tho idle) and it timed out; I can't connect to anything on the server's IP, can't even ping it
[04:07] <CoJaBo> slidinghorn: It appears that it's just freezing and not writing anything at all to disk
[04:21] <Bashing-om> CoJaBo: Good for thought, fought that freezing up for 6 months on this system .,. installed the nvidia graphic's driver and no more freezes .
[04:23] <CoJaBo> Bashing-om: is that even possible to install if the system is console-only?
[04:24] <Bashing-om> CoJaBo: My understanding is that if you do not have a graphic's card installed ya got to make up a dummy .
[04:25] <CoJaBo> It has a gfx card installed, because the mobo doesn't have onboard one
[04:28] <Bashing-om> CoJaBo: That be good .. there is no longer a AMD proprietary driver :) Bit ya might do well to verify that the driver matches the card .
[04:29] <CoJaBo> Bashing-om: Why would that help if the system isn't using the graphics card for anything but text?
[04:30] <flocculant> nacc: not sure why a wiki page I edited once is mine :D
[04:30] <Bashing-om> CoJaBo: Got me . All I can relate is the driver ( module ) can and does some crazy things .
[04:32] <Bashing-om> CoJaBo: et all .. I be late for the date for some rack time .. take care and we do this later .
[04:32] <lotuspsychje> Bashing-om: when i apt-cache search wayland, nvidia 390 driver shows up :p
[04:34] <Bashing-om> lotuspsychje: Yepper . have not checked lately .. but the 390 driver in the repo may be the ;latest version still be what we want on wayland .
[04:35] <lotuspsychje> yeah just my thought
[04:36] <Bashing-om> lotuspsychje: Amd on nother sujhect ... we made it .. published ! https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue523
[04:36] <Bashing-om> subject*
[04:38] <Bashing-om> oooppps sorry for the off-topic .
[04:40] <USERNAME000> Hello,
[04:40] <lotuspsychje> welcome
[04:40] <USERNAME000> I'm having some issues with KVM on B.B.
[04:40] <nacc> flocculant: lol
[04:40] <USERNAME000> when running qemu it doesn't get kvm support
[04:41] <nacc> USERNAME000: run `kvm` ?
[04:41] <USERNAME000> qemu --enable-kvm 
[04:41] <nacc> or `kvm-ok` to see if it is supported
[04:41] <USERNAME000> kvm
[04:41] <USERNAME000> qemu-system-x86_64
[04:42] <USERNAME000> Shows cannot get kernel module permissions and fails
[04:47] <cpaelzer> USERNAME000: then /dev/kvm does not allow you
[04:47] <cpaelzer> that should be on root:kvm
[04:47] <cpaelzer> and you should be in group kvm
[04:47] <cpaelzer> usually
[04:47] <cpaelzer> check "id" if you are
[04:53] <USERNAME000> reinstalling now. 
[04:59] <CoJaBo> slidinghorn: Confirmed that, indeed, nothing at all whatsoever was written to the syslog at time of crash, at least that made it to disk; last entry was from a random cronjob about an hour before, in both cases
[05:15] <USERNAME00> Figured it out
[05:15] <USERNAME00> It was an issue of not adding the user to libvirt
[06:46] <CoJaBo> I've noticed a seperate issue now, after updating everythign to latest; I get a kernel panic, "attempted to kill init" when rebooting; happens 100% of the time, at the very end of shutdown (and of course after all the logging is shut down, so I can't see the top halfd of the message)
[07:55] <vlt> Hello. What is the replacement for /etc/network/interfaces on 18.04?
[08:02] <lindbergio> Has anyone figured out how to disable screen orientation in Bionic? I have tried setting the 'org.gnome.settings-daemon.peripherals.touchscreen orientation-lock' key to 'true' and 'org.gnome.settings-daemon.plugins.orientation active' key to 'false'.
[08:03] <TJ-> vlt: for Desktop installs it's Network Manager; for servers it's systemd-networkd. Both are using 'netplan' (netplan.io) as a configuration file front-end
[08:08] <vlt> TJ-: Thank you.
[08:10] <TJ-> netplan has a single purpose. Write config files for the network services. We create definitions in /etc/netplan/. At boot-time netplan converts that for NM or s-n and writes the appropriate config to /run/NetworkManager/ or /run/systemd/network/
[09:56] <Tm_T> I've noticed that since upgrading to 18.04 my Steam client fails to connect to servers
[09:56] <Tm_T> I did go in offline mode and installed client updates but that didn't change anything
[09:56] <Tm_T> iptables has no blocking rules
[10:10] <blackflow> Tm_T: DNS issues? Temporarily change the resolver in /etc/resolv.conf, say enter google's    nameserver 8.8.8.8    and see if that works.
[10:10] <Tm_T> I doubt but let's see
[10:10] <Tm_T> now I logged out and try log in again, fails
[10:10] <Tm_T> I can log in to android and website just fine
[10:11] <Tm_T> time to try traditional fix, reboot the whole machine
[10:21] <blackflow> Tm_T: did that fix it?
[10:23] <Tm_T> it did
[10:23] <Tm_T> it didn't even ask me to log in, it just went in smoothly
[10:24] <blackflow> well how about that.
[12:19] <Laibsch> Can somebody help me understand what's going on in bug 991471?
[12:20] <Laibsch> It still affects bionic and I'd like to see what I can do to get it fixed
[12:21] <Laibsch> IOW, how does the automatic mounting happen?
[14:28] <enyc> Laibsch: theres some other issue such that grub config / os-prober  wan't find typical other ubuntu installs on btrfs and put them in tnhe boot-menu!
[14:35] <sveinse> How come I can only find libportaudio2 but no libportaudio2-dev in 18.04 ?
[15:26] <mvvvv> Hi ... microcode-intel is installed on my updated 18.04 beta ... but it doesn't appear in ubuntu-drivers any more ... is it the new way to handle it ?
[15:54] <Bloviogot> hi
[16:02] <nacc> sveinse: there is no libportaudio2-dev in ubuntu period
[16:02] <nacc> sveinse: perhaps you meant portaudio19-dev ?
[16:04] <sveinse> nacc: There is a libportaudio2, so I assumed there would be a -dev version of it as well. Perhaps portaudio19-dev is the -dev package from the same source package that builds libportaudio2 ?
[16:36] <nacc> sveinse: yes it is.
[16:36] <nacc> sveinse: that's why i suggested it :)
[16:49] <andreas__> Hello, does someone know how to screen-capture or take regular screen shots of the gdm3 greeter prior to login? I have a few graphic glitches I want to record.
[16:50] <lotuspsychje> andreas__: does prt scr button not work on that stage?
[16:51] <lotuspsychje> andreas__: wich graphics card/driver are you on and logged into wayland or xorg?
[16:53] <andreas__> I'm on nouveau with an nvidia optimus card. The problem is only visible prior to login. After login to either xorg or wayland the lock screen/switch user works just fine.
[16:54] <brainwash> andreas__: I think the easiest way would be to take a picture with a smartphone or camera
[16:54] <lotuspsychje> andreas__: hmm preboot glitches is weird.. perhaps try a !nomodeset
[16:59] <brainwash> andreas__: I would test this also https://www.reddit.com/r/Ubuntu/comments/7q78jf/psa_if_youre_using_xorg_enable_xorg_backend_on/
[17:07] <andreas__> Thanks for the advice. I'm not trying to work my way around the problem. I think I'll go with phone/camera option. As I'm just curious about why it is happening, and having an image or video to show someone more knowledgeable than me might help shed some light on the situation.
[17:08] <brainwash> andreas__: testing with gdm3 on xorg vs wayland could help with the debugging
[17:14] <andreas__> so, is gdm3 greeter using xorg or wayland? if I'm not mistaken it was wayland in 17.10. And I assumed it is back to xorg for 18.04 since that's the default now? If so, should I test with "WaylandEnable=true" in the conf file?
[17:18] <andreas__> This is the only computer I have access to at the moment. I'll do a reboot and record the problems to start with. Then I'll try enabling/disabling wayland in gdm3 and see what happens. Thanks for the help thus far. Bye!
[19:03] <FurretUber> Hi, is there a way to make netconsole start VERY early at boot? Like, before everything possible?
[19:05] <lotuspsychje> FurretUber: can this help? https://wiki.ubuntu.com/Kernel/Netconsole
[19:06] <FurretUber> Adding it to kernel command line makes it lose around 6 seconds of logs, which was enough to make https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218 very hard to debug
[19:07] <FurretUber> I set netconsole to start on boot successfully, but it has a 6 seconds interval that caused a lot of trouble
[19:11] <alkisg> FurretUber: I haven't used it, but from what I can see, it's available even in the initramfs, so you could even set up networking in the initramfs (ip=dhcp) and put netconsole in /etc/modules and run update-initramfs
[19:11] <alkisg> That way it should be started even before / is loaded
[19:20] <FurretUber> https://wiki.ubuntu.com/KernelTeam/Netconsole/Early
[19:20] <FurretUber> Time to test
[19:22] <omarv> Hi all, I have ubuntu 18 installed, by now have a problem starting up,, could someone help me ? thanks  a lot
[19:35] <FurretUber> I have updated the initramfs to add netconsole and it worked, I have a log with the kernel panic. Thank you, very much
[19:37] <brainwash> omarv: usually one would describe the problem, and then wait for an answer
[19:44] <omarv> Iḿ not ubuntu user experimented, so I ´l try to explain: Failed to connect to lvmetad.Falling back to device scanning.
[19:46] <omarv> anyway it begins to starting up , by now stop starting resolvconf-pull-resolved.service
[19:49] <brainwash> omarv: is that a fresh installation of 18.04, or an upgrade from a previous version?
[19:52] <omarv> I installed it last week . version 18.04. It was working like a charm..until two hours ago, it crashed..
[19:53] <omarv> it is fresh installation, ..not comming from version 17.04
[19:54] <omarv> it is Linux 4.15.0-15-generic
[19:58] <brainwash> omarv: it cashed while doing what?
[19:58] <brainwash> omarv: also, was the system able to boot after all?
[19:59] <adalbert> Hi, I'm reading on the net that ubuntu 18 will ship with a gnome release with a memory leak? Is that true?
[19:59] <omarv> I just made a restart the system..
[20:00] <brainwash> adalbert: glad that you've provided a link to that claim..
[20:00] <adalbert> brainwash: just a sec ...
[20:01] <adalbert> https://www.omgubuntu.co.uk/2018/03/gnome-shell-has-a-memory-leak-and-it-might-not-be-fixed-for-ubuntu-18-04-lts
[20:01] <brainwash> omarv: still the same problem with slow starting services?
[20:03] <omarv> it starting the services , but suddenly stop to continue load it
[20:03] <brainwash> adalbert: the article mentions bug 1672297
[20:04] <brainwash> so, it will be fixed
[20:05] <adalbert> brainwash: That is good news!
[20:07] <omarv> no,..jajaj,.. because Im very impatient, and restarted the pc again...
[20:08] <brainwash> you still haven't described how the system crashed in the first place
[20:08] <omarv> need I to wait starting services going on..?
[20:09] <brainwash> maybe you can change the timeout for services, so you'll have to wait less
[20:09] <omarv> really not crashed,,I reboot the pc,,and then the problem arise..
[20:09] <brainwash> but could it be a hardware failure?
[20:09] <brainwash> aha
[20:10] <brainwash> so, some package update could be the culprit
[20:13] <omarv> yes , it should be a hw failure,, it said PCIe Bus Error, type= physical Layer
[20:14] <brainwash> well, not sure what can be done in this case other than replacing the faulty hardware
[20:15] <omarv> off course, then ,..I will double check the hardware..thanks
[20:15] <brainwash> please do
[20:16] <omarv> it is installed in a MSI GE62 Apache pro
[20:18] <omarv> may be the GPU was overheated, and previous to that I was running tensorflow in GPU ,..I think that was happened...
[20:20] <brainwash> I would boot the ubuntu 18.04 iso, and check if live mode is working
[20:22] <omarv> How can do that ? need I to reboot using iso image from USB memory ?
[20:22] <brainwash> yes
[20:23] <cram> hello i do upgrade xubuntu 17.10 to 18.10 and now black screen.
[20:23] <brainwash> you mean 18.04
[20:24] <omarv> ok,..I will do that..
[20:24] <cram> #ubuntu say me its because i have nividia and to come her for support.
[20:24] <cram> what can i do?
[20:24] <cram> yes i mean 18.04
[20:27] <brainwash> maybe bug 1752053
[20:27] <brainwash> I suggest reading the comments towards the bottom of the page
[20:29] <brainwash> another report bug 1764005
[20:30] <cram> ok but i have no console on the screen just xubuntu screen and after black screen
[20:31] <nacc> cram: go to a tty (ctrl+alt+f1, f2, etc.)
[20:33] <cram> ok do this and have console now but what next?
[20:33] <cram> i read the bottom page but do not understand very well
[20:34] <brainwash> what do you not understand?
[20:35] <cram> i have to install new packages for nvidia but what command line? is it apt-get isntall nvidia-driver-390?
[20:38] <cram> there s so much things i do not understand on this page
[20:41] <brainwash> cram: why did you install/upgrade to 18.04?
[20:42] <cram> because i think soon xubuntu 17.10 will not be maintened
[20:43] <nacc> cram: ... you have 3-4 months
[20:43] <cram> maybe it was a little bit soon
[20:43] <nacc> cram: and 18.04 isn't released yet
[20:44] <cram> ok i have misinterpreted
[20:44] <cram> but can i undo what have be done
[20:44] <nacc> cram: not really, no
[20:45] <cram> that's bad
[20:45] <IntelCore> ahhchoo
[20:46] <IntelCore> will 16.04 update to bionic?
[20:46] <nacc> IntelCore: in about 3 months
[20:46] <cram> but it must not be too difficult to had a repo in command line?
[20:46] <nacc> IntelCore: and when you ask it to, of course
[20:46] <nacc> cram: ... what does that have to do with anything?
[20:46] <nacc> cram: everything in 18.04 is after 17.10, so adding a repo won't do anything
[20:46] <IntelCore> oh.. hi nacc!  Yeah that. 
[20:47] <nacc> IntelCore: 16.04 -> 18.04.1 once it comes out
[20:47] <IntelCore> otherwise clean install 18.04 now?
[20:47] <cram> i think had ppa for nvidia driver
[20:47] <nacc> IntelCore: otherwise what?
[20:47] <nacc> IntelCore: you can `d-release-upgrade -d` to 18.04
[20:48] <nacc> do-release-upgrade, rather
[20:48] <nacc> IntelCore: but it's not officially offered until 18.04.1
[20:48] <IntelCore> launchpad showing 18.04beta
[20:48] <nacc> IntelCore: well, 18.04 isn't out yet
[20:48] <nacc> IntelCore: not sure what you mean by that last sentence
[20:48] <IntelCore> https://launchpad.net/ubuntu
[20:49] <nacc> IntelCore: ok, and what specific thing says "18.04beta" ?
[20:49] <IntelCore> the frozen build
[20:50] <nacc> IntelCore: i don't find the string 'frozen build' or '18.04beta' on the page
[20:50] <nacc> IntelCore: what are you actually asking?
[20:51] <IntelCore> http://releases.ubuntu.com/18.04/
[20:51] <IntelCore> That is there to download
[20:51] <nacc> you are better off always downloading the daily
[20:51] <nacc> beta 2 is just a point in time
[20:51] <nacc> ~11 days old, so you'd need to go through all the updates if you installed that
[20:51] <nacc> IntelCore: that's still not a question
[20:52] <IntelCore> Oh, well.. I want 18.04 before the approved three months
[20:53] <IntelCore> what is good to do?
[20:53] <cram> ok will read and try to understand all this...
[20:53] <cram> tahks for the help 
[20:53] <cram> by
[20:53] <cram> bye
[20:53] <nacc> IntelCore: you can upgrade or fresh install
[20:54] <tgm4883> IntelCore: Then get it Next Thursday, when it's released
[20:59] <omarv> brainwash:I was testing last time trying to start system again, and it stop starting and it said "Started Restore /etc/resolv.conf if the system crashed before thye ppp link was shut down",... What it means?
[21:06] <brainwash> I think it means that the system tries to restore a broken or invalid /etc/resolv.conf
[21:07] <brainwash> however, that shouldn't impact the boot process
[21:08] <brainwash> it could be the last message while the system was still booting ok
[21:08] <brainwash> ideally, you should share a photo of the boot screen
[21:08] <brainwash> so that we can get a better impression of what is going on
[21:09] <brainwash> other than that, did you boot into live mode yet?
[21:09] <IntelCore> Yea, I will Thursday, on a new partition.. put 18.04, and likely back-away from 16.04
[22:07] <omarv> brainwash:In doing USB iso image with Ubuntu 18.04
[23:38] <xuanrui> Hi all
[23:39] <xuanrui> I've been experiencing very, very frequent freezes on the latest release of 18.04...
[23:39] <xuanrui> *GUI freezes I mean
[23:41] <xuanrui> Has anyone experienced a similar issue? If so has it been fixed in the daily version?
[23:41] <xuanrui> (by latest release, I mean beta2)
[23:47] <andreas__> xuanrui: I have short freezes (especially during input, i.e. mouse and keyboard events) when I'm login on a wayland session. But I believe that is due to wayland not being stable enough yet, hence the defaulting to xorg (purely speculations from my part though). I haven't tried xorg enough yet to say anything conclusive.
[23:48] <xuanrui> I'm having extremely frequent freezes, like, completely freezes the GUI and I can't move anything anymore
[23:48] <xuanrui> have to resort to power-buttoning
[23:48] <xuanrui> I was thinking probably this was not a 18.04 issue but a result of old config files or sth...
[23:51] <andreas__> It's not that bad for me. You'll have to wait for someone more knowledgeable than me to reply.