[02:06] <stochastix> Will try the 17.10 one
[02:38] <Boyette> hi
[05:10] <lotuspsychje> when i start simple scan it says i need a driver for my hp all in one, but when pressing download driver it says failed. anyone knows wich package this would be needed?
[05:21] <lotuspsychje> it worked earlier on 18.04 and on 16.04 on same machine
[05:27] <flocculant> lotuspsychje: hp deksjet scans ok here
[05:28] <lotuspsychje> tnx for testing flocculant 
[05:29] <lotuspsychje> !info sane
[05:31] <lotuspsychje> hplip-data was also installed and latest hmmm
[05:33] <flocculant> lotuspsychje: also I removed it and reinstalled - still finds what it needs to
[05:33] <flocculant> I assume it prints etc ok?
[05:35] <lotuspsychje> flocculant: yes printer works
[05:36] <lotuspsychje> flocculant: ah, ill try a purge good idea
[05:43] <lotuspsychje> flocculant: not on the machine atm, ill try in a bit :p
[05:44] <flocculant> good luck - you're lucky I was awake enough to do what I did :p
[05:44] <lotuspsychje> flocculant: haha
[05:44] <lotuspsychje> i surely am
[05:45] <flocculant> been awake since ~4am - alarm has just gone of ...
[05:45] <flocculant> still not had enough tea to be called alive and kicking just yet 
[05:45] <lotuspsychje> :p
[05:46] <lotuspsychje> a shower always works
[05:46] <flocculant> if I lived somewhere that had one ...
[05:46] <lotuspsychje> oh
[05:46] <lotuspsychje> im not gonna reccomend rain :p
[05:46] <flocculant> social housing 
[05:46] <flocculant> yea don't:D
[08:25] <lotuspsychje> im getting unmet dependecys and didnt add external ppa's https://hastebin.com/tunuzeyuvi.rb
[08:29] <Faux> It can also happen if you have older libraries installed. Or it could just be apt being terrible at dependency resolution. Generally you can just remove a randomly selected offending package, and try installing it again afterwards.
[08:29] <lotuspsychje> Faux: tried to pyrge that package but no dice
[08:29] <lotuspsychje> purge
[08:30] <Faux> Did you remove the :i386 version?
[08:30] <lotuspsychje> yeah
[08:31]  * Faux shrugs. Try aptitude, or wait a bit to see if it's an actual problem.
[08:31] <lotuspsychje> Faux: whats the dpkg method of purge force again?
[08:31] <Faux> Pardon?
[08:32] <lotuspsychje> instead of purge with apt, purge with dpkg to solve issues
[08:35] <lotuspsychje> dpkg -P nvm
[08:36] <lotuspsychje> hmm doesnt wanna purge neither
[09:14] <lotuspsychje> Faux: fixxed it https://askubuntu.com/questions/873565/broken-libperl5-package-when-trying-to-install-updates
[09:14] <Faux> Ew. :)
[11:57] <Faux> I'm getting audio dropouts using Google Maps' 3d/birdseye view in official Chrome stable.
[14:31] <swein> just upgraded/dist-upgraded my 18.04 desktop, boots to just past the ubuntu boot load in screen but display manager with login won't load
[14:35] <swein> can't drop to single user mode, just a mouse cursor and blank screen
[14:37] <Faux> Gpu driver has probably crashed X. Booting rescue mode from grub will let you get a shell.
[14:39] <swein> holding shift on reboot didn't get me into grub menu, weird
[14:39] <swein> I'm on an intel NUC skulltrail btw
[14:46] <swein> any other ideas to get into grub menu on reboot? holding left shift isn't working
[14:47] <Faux> Boot from a usb stick, edit the grub config to have a non-hidden timeout. (not a serious suggestion)
[14:47] <Faux> Sometimes keyboards don't work during early boot; mobo does'nt have a weird "bios keyboard" usb port or something?
[14:50] <swein> I'm using my ergodox infinity, but it works normally as other keyboards. I can try using another around my office
[14:50] <Faux> It's a mobo problem, not a keyboard problem.
[14:52] <swein> I'll check bios for options
[14:52] <swein> Faux: Thank you for helping
[14:53] <CoJaBo> Anyone know why networking would stop working after changing a SATA card?
[14:56] <swein> hit the card? or cables?
[14:56] <CoJaBo> It's built-in
[14:56] <swein> IRQ conflict ?:P
[14:56] <CoJaBo> Only thing I can think of is it changed the name somehow
[14:57] <swein> sdX shouldn't affect network interfaces
[14:57] <CoJaBo> I can do ifconfig enp42s0 [IP], but then I still cant get to the internet, just local
[14:58] <CoJaBo> And even then, it takes ~10 minutes to boot, since it waits a LONG time for network to come up
[15:00] <Faux> Oh, the card is working, but you don't get internet.
[15:01] <Faux> "dhclient -v enp42s0" will probably fix it. You need to argue with whatever network tool you're using (networkmanager, /etc/network/interfaces, nplan), though.
[15:04] <CoJaBo> Faux: What is the default, and how do i fix it to find the card again without doing this manually every boot?
[15:04] <Faux> The default depends on what phase of moon you installed in, and I know nothing about them. :)
[15:04] <CoJaBo> whats the current default then?
[15:05] <Faux> nplan/netplan is the new default.
[15:06] <Faux> Unless they've given up on that.
[15:07] <CoJaBo> how do i use that?
[15:08] <CoJaBo> /etc/netplan/01-netcfg.yaml lists a device name that doesn't exist
[15:09]  * Faux has no idea, as the upgrade has not broken it, so has left it alone.
[15:09] <CoJaBo> unrealted, but wtf is this File descriptor 3 (pipe:[44189]) leaked on vgs invocation. Parent PID 7115: grub-install
[15:10] <CoJaBo> Going to fix the name there, hope, and reboot i guess..
[15:10] <Faux> https://wiki.ubuntu.com/Netplan suggests running "generate"
[15:11] <Faux> Unless it's done on boot.
[15:14] <CoJaBo> Dunno; it booted this time, so something worked
[15:15] <CoJaBo> Faux: I upgraded the BIOS while troubleshooting the SATA card issue. The firmware manages the ethernet, apparently, so that's probably what changed the device name
[15:17] <CoJaBo> Faux: Huge thanks on the netplan thing tho, I would've never found that in a trillion years =D
[16:18] <swein> is 18.04 lightdm?
[16:18] <swein> I'm trying to fix intel driver crashing x,
[16:19] <swein> gdm I googled sorry
[16:21] <BenLubar__> Does Bionic require some new CPU feature that Xenial didn't?
[16:21] <nacc> BenLubar__: seems unlikely
[16:22] <BenLubar__> Hmm, I wonder why my headless Linux machine suddenly becomes unresponsive until I hold the power button :/
[16:25] <BenLubar> hmm, it appears to have gone into some kind of sleep mode, since when I pushed the power button it immediately started up and I was able to connect over ssh on the first try
[16:34] <swein> what a horrible expereience, can't even get to proper terminal to reinstall intel drivers and displaymanagers
[16:40] <nacc> BenLubar: interesting
[16:41] <nacc> swein: 'intel driver' ?
[16:42] <BenLubar> this probably isn't related, but after I rebooted the machine at the end of the upgrade process it didn't come back up (I think that's a problem that existed before I upgraded, though. Something to do with misconfigured bios.)
[16:45] <BenLubar_> ok, this is super weird, but... could my computer be running two copies of Ubuntu on the same filesystem simultaneously somehow?
[16:45] <nacc> BenLubar: not really, no.
[16:45] <BenLubar_> I'm gonna try sudo shutdown -h now and see if the computer shuts off or just goes into standby mode again
[16:45] <nacc> BenLubar: I guess it depends on what you mean by 'running'? :)
[16:51] <BenLubar> the message about "Your Hardware Enablement Stack (HWE) is supported until April 2019." is something I can ignore, right?
[16:51] <BenLubar> the documentation seems to imply that the message is only there because I'm on a prerelease version of Bionic
[16:53] <nacc> BenLubar: where do you see that?
[16:56] <BenLubar> nacc: when I log in over SSH
[16:56] <nacc> BenLubar: so from the motd?
[16:56] <BenLubar> yes
[16:56] <nacc> BenLubar: hrm, I don't see that from a login locally
[16:56] <nacc> BenLubar: lsb_release -a definitely says it's 18.04 ?
[16:57] <BenLubar> Release:        18.04
[17:01] <nacc> BenLubar: ok :)
[17:02] <nacc> BenLubar: dunno where that comes from then, as you obviously don't have a HWE stack
[17:13] <TJ-> it comes via /usr/lib/update-notifier/update-motd-hwe-eol
[17:16] <nacc> TJ-: interesting
[17:17] <swein> if 4.15 kernel booting of 18.04 freezes before getting to login screen, what would I do to fix it's display issues? I booted of the 4.13 kernel and did a dpkg-reconfigure gdm3 and rechose gdm3 (not lightdm) 
[17:17] <swein> are there packages I can --reinstall to fix booting to 4.15?
[17:18] <nacc> swein: does it "freeze" or do you hear the cpus spin up, or something else?
[17:18] <nacc> swein: oh it works ok with 4.13?
[17:18] <swein> yeah ubuntu splash screen loads, then when it normally gives you a login screen, I only see a mouse cursor.
[17:19] <nacc> swein: yeah i just had this issue
[17:19] <nacc> swein: (I think)
[17:19] <swein> I did a upgrade/dist-upgrade this morning. so it likely mangled my display driver/manager up in regards to 4.15 kernel
[17:19] <nacc> swein: can you reboot with nomodeset and see if it works? do you have an external monitor connected?
[17:19] <swein> two externals. it's an Intel NUC
[17:19] <nacc> swein: hrm
[17:19] <nacc> swein: ok, so i had somethjing symptomatically very similar
[17:19] <nacc> swein: it turned out aht wayland was running and was (i think) crashing/pegging the cpu
[17:20] <swein> could be that
[17:20] <nacc> swein: check (from 4.13) your /etc/gdm3/custom.conf
[17:20] <swein> I'll remove weyland
[17:20] <nacc> swein: and disable the wayland option, see if that 'fixess' it
[17:21] <swein> custom.conf doesn't have any options uncommented
[17:21] <swein> #waylandEnable=false it's commented out
[17:21] <nacc> swein: right, the one that disables wayland is commented out by default
[17:21] <nacc> swein: so uncomment it :)
[17:21] <swein> ahh
[17:21] <nacc> swein: it's super confusing
[17:21] <nacc> (at least to me)
[17:22] <swein> ok rebooting to see if 4.15 loads now
[17:22] <nacc> https://bugs.launchpad.net/bugs/1753576
[17:22] <nacc> swein: --^ taht's the bug i filed
[17:22] <nacc> i'm curious if you see the same issue, and why it's triggering for only some
[17:22] <swein> nacc: excellent , I'm booted in
[17:23] <nacc> swein: symptomatically, ihad the same problem, splash showed up on both monitors, then all of a sudden the primary laptop display shows the mouse and the normal greeter background, but then the cpu starts to peg
[17:23] <swein> that's what happens when you dist-upgrade from 17.10 to 18.04 and keep weyland around
[17:23] <nacc> and the secondary display still shows a frozen splash
[17:23] <nacc> swein: right, but this was working fine for me until monday morning when i rebooted
[17:23] <nacc> i've been on 18.04 for > 1 month
[17:23] <nacc> so i think they fubar'd something
[17:23] <nacc> such that the greeter session defaulted to wayland which simply doesn't work
[17:23] <nacc> but i'm not 100% sure
[17:23] <swein> I apprecaite you helping, I'd of never thought to do that
[17:24] <nacc> swein: np, please subscribe to that bug and indicate you hit the same issue with the sam eworakround
[17:24] <nacc> *same*
[17:24] <swein> will do
[17:24] <nacc> swein: thanks!
[17:24] <nacc> i'll try and get the desktop folks to prioritize it, it seems likely they'd have a NUC around to use
[17:25] <swein> I don't know if it's intel specific. it was obviously weyland related
[17:26] <swein> Why are they choosing to axe weyland already?
[17:26] <nacc> swein: yeah, i wonder since you have remote access to yours already, you might be able to get the debugging daniel asked for in teh bug
[17:26] <nacc> swein: heh, it's just not the default, it's still there
[17:26] <nacc> swein: and because of stuff like this, i expect (it's just not readyh)
[17:26] <nacc> you can't do remote desktop at all (it's incompatible with the model), etc. -- some key features
[17:27] <swein> I'm only running 18.04 develop to test for server changes. I'll need to upgrade my org to 18.04 eventually
[17:27] <swein> thanks again for your help
[17:38] <nacc> swein: np
[17:57] <BenLubar> can I disable power saving mode or something?
[18:56] <lotuspsychje> flocculant: scanner issue solved itself after a weird dependecy hell lol
[18:58] <flocculant> lotuspsychje: cool - glad to hear it :)
[18:58] <lotuspsychje> flocculant: now simple-scan showing hp photosmart 
[19:04] <lotuspsychje> flocculant: had one guy this morning perherhaps with grub flicker
 when you move to select item in GRUB menu with keyboard arrows, it displays screen a bit garbled
 nikolam: this is what you experience? https://launchpad.net/bugs/1752767
[19:08] <flocculant> lotuspsychje: if they're using artful I believe it's SRU/-proposed there
[19:09] <lotuspsychje> right
[19:22] <lotuspsychje> archetech-U: welcome
[19:25] <archetech-U> DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"
[19:25] <archetech-U> :) ty
[19:26] <archetech-U> enjoying the G3 beta