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