[00:01] tomreyn: thanks , ubottu [00:01] laserbeak4445: i would assume (don't really know netplan either, yet) that what you do not configur ein netplan won't get rendered into configurations and unconfigured NICs are not in use. [00:02] laserbeak4445: have you tried to verify this? [00:03] as a last resort you could always use rfkill [00:03] tomreyn: You mean verify with 'ip address show'? [00:04] laserbeak4445: ip l, ip a, ip r, yes [00:05] laserbeak4445: but also by looking at the systemd-networkd configuration netplan rendered. [00:07] tomreyn: 'ip a' tell me that the state of my wifi adapter is down so I guess it's a good sign [00:08] Hi, I'm trying to follow the walkthrough at https://help.ubuntu.com/community/ManyButtonsMouseHowto and the first thing he says to do is imwheel -c but when I do that all I get is "Configuration terminated by signal 11" Does anyone know of a better walkthrough? [00:09] and to check the systemd-networkd configuration netplan rendered, how can do that? [00:14] ok I figure it was with 'sudo systemctl status systemd-networkd' [00:15] right [00:15] when I check that, I get 'Link is not managed by us' beside the wifi adapter name..? [00:16] so it's not managed by systemd-networkd [00:16] meaning it wont bring it up === Guest11810 is now known as spion- [00:19] if it's not managed by systemd-networkd, could it also mean that it is manage by something else on the system or not really? [00:20] network-manager would be the other suspect [00:20] the actual systemd-networkd configuration file should reside in /etc/systemd/network/ [00:21] but it's 18.04 server. network-manager is not installed by default afaik [00:21] "nmcli d" to see what it manages [00:22] "dpkg -l networkmanager" to see whether it's installed (ii). [00:23] laserbeak4445: -server is expected to use systemd-networkd, and it's configured via netplan . [00:25] I can confirm, there is no network-manager installed on my 18.04 server and it seems to only use networkd, so I should be fine.. [00:25] hi im installing vbox guest additions to a ubuntu guest, but it doesnt seem to take any effect, following, https://websiteforstudents.com/installing-virtualbox-guest-additions-on-ubuntu-18-04-beta/ [00:26] Thanks guys for the help! [00:34] VectorX: you cna install them from a terminal and watch the output. i assume also that the virtualbox guest additions version in ubuntu 18.04 won't actually work with an ubuntu 18.04 guest, since they can be too old. [00:36] that's 'too old' as in lacking patches needed to make them work well on ubuntu 18.04. if you'll run the latest upstream release (they also provide an apt repository) it should work out. [00:36] tomreyn so how would i install it [00:37] VectorX: what is "it"? [00:37] vbox guest additions [00:38] im sorry let me rewrite that so it maybe a bit more clear [00:38] tomreyn so how would i install vbox guest additions on ubuntu 18.04 from the latest upstream as you mentioned [00:39] i found this, but i dont know how to install it https://launchpad.net/ubuntu/bionic/+source/virtualbox-guest-additions-iso [00:39] if that is something inline with what you are sayinh [00:39] you install the updated virtualbox release, then you insert the iso image on the guest's cdrom (using the menu option provided for it), then mount the iso on the guest, then change into the directory where you mounted it and run the installer .sh there and see what happens. [00:40] ok let me try that [00:41] so that's basically the same process as on the tutorial you followed, just that you do it on a newer virtualbox release and thus with a newer guest additions ISO [00:46] tomreyn thanks, that worked [00:46] All please take a look at this https://www.hublinux.com/ [00:47] ghost_, no spam, thanks. [00:47] Well I wouldn't call it spam but that's just me [00:52] apport by default must be breaking some new privacy rule [00:57] I just installed Ubuntu onto my XPS which has a touchscreen. When I tap it does a double click. Anyone know how to fix this? [01:19] list [01:19] LIST [01:21] slash list ? [01:22] Hi all [01:26] Hi AarKnos [01:28] Hi all [01:28] Hi all [01:40] can't login on xubuntu 18.04 in gui (only in tty); changing lightdm's config doesn't solve the issue 'cause accountservice is running - is there a way to turn it off or change its config? [01:50] or is it faster to reinstall os then trying to track down and fix this corruption (my /home is sepparate)? [01:51] RoadRunner: have a home partition now? if yes then re-install is faster [01:52] Two_Dogs: yes, I learned that lesson :) [01:53] RoadRunner: cool, re-install then [01:53] RoadRunner: save any folders/confs you tweaked [01:54] Two_Dogs: all the app specific confs should be in /home, that is the whole idea, right? [01:55] RoadRunner: yes, all those are safe, i meant something you tweaked on the system side [01:56] RoadRunner: usually done in /etc , if you did you would remember doing so === brainwash_ is now known as brainwash [01:57] for the future, is there a known issue with older aps using gtk 2, GL, etc. I would not want to be back in this boat again after installing something else tommorow? [01:58] RoadRunner: install plasma desktop and no gtk issues :) [01:58] "older apps"... who knows, in the future? [01:58] the corruption likely occured after I installed xscreensavers/rss-glx which must have affected gtk [01:59] oh, not the borked upgrade from 16.04 ? [01:59] or 17.10, whatever :-P [02:00] borked? :) [02:01] i notice borked networking on upgrades [02:02] xscreensavers were installed by "Software" and rss-glx by Synaptic everything seemed to be tied to bionic [02:03] oerheks: so its a known issue? [02:11] no idea there, https://bugs.launchpad.net/ubuntu/+source/rss-glx/+bugs [02:19] My Ubuntu bionic seems to have some memory recognition issue.. it shows total of 15GB as expected but the odd thing is, it shows used 6GB and free 2GB.. it seems to me the available memory is not matching the 16G total [02:22] gnuser: where are you looking at to get your numbers? [02:25] any recommenadations for a decent screensaver package that will not crash xubuntu 18.04? [02:28] RoadRunner: why not use pwr management, dim screen, suspend after ??min [02:30] RoadRunner: on the default 18.04 it is avail option/s [02:30] Two_Dogs: I like cool effects :) [02:30] ahh [02:31] RoadRunner: heres a cool effect, wallpaper [02:32] Two_Dogs: you are so retro :):) [02:32] screensaver is overhead [02:34] this corruption scarred me though, didn't think some app's gtk issue would deny me access to the system [02:34] seems odd that userspace app borks gdm [02:35] I am running xubuntu, in my case its lightdm [02:36] RoadRunner: lightdm was default install? [02:36] yes [02:36] RoadRunner: you got someway to connect to borked via ssh perhaps? [02:37] why? [02:37] RoadRunner: well then you could see where who did what in the library with the candlestick [02:38] I can get in with tty [02:38] logs/journalctl etc [02:38] then find cause of bork, the point is fixing issue, otherwise it might as well be windows [02:40] looked at /var/log/syslog but its over 100 screens of text and nothing jumped out at me (but then, I am no expert)... [02:42] RoadRunner: execute> journalctl -b --pri=3 ## them are errors only lines [02:43] is there a way to check my current install against a healthy one like with software updater or something? [02:44] comparing is so retro dude [02:45] :) [02:45] but beats looking for a needle in a haystack [02:45] errors stick out [02:45] which logs do you suggest I check? [02:46] i told you [02:46] RoadRunner: execute> journalctl -b --pri=3 ## them are errors only lines [02:46] I thought that command would work only on a specific log? [02:47] RoadRunner: no, that is userspace/systemspace errors, on journalctl anyway [02:47] RoadRunner: there is also xsession-errors log somewhere [02:48] ok, assuming I dig up something, how do I copy that output to a usb? [02:48] remember, I only have tty [02:51] RoadRunner: remember my asking about ssh in? [02:52] Two_Dogs: I remember, it's a no on that one [02:53] RoadRunner: you got something you could use to ssh into the borked from within the lan? phone? working linux? ipad? etc [02:54] hello? [02:55] I got a working linux on this lan, but then I'd have to install ssh on "borked" and I am afraid you'd have to spoon feed me through the rescue... [02:56] RoadRunner: well, right now all we are doing is playing suppose and maybe [02:57] i hate suppose and maybe, besides i gave you the command to get somewhere already [02:57] working on that now [02:57] its that or i continue to break virt of 18.04 just because [02:58] the gnome-shell panel cant be placed on top? [03:03] just tty [03:03] ran your command [03:03] got 8 lines of errors [03:05] RoadRunner: is pastebinit installed on borked? [03:05] RoadRunner, I wasn't here when this convo started but if you have errors it generally is a good idea to share them [03:05] RoadRunner: what syb0rg said :) [03:05] here is one: lightdm [729]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object [03:06] no pastebinit is not installed [03:06] RoadRunner: install it on borked [03:06] how? [03:06] RoadRunner: sudo apt install pastebinit [03:06] ok [03:06] on borked [03:07] RoadRunner: execute> journalctl -b --pri=3 | pastebinit ## gets url, share url here [03:08] Two_Dogs: after your command, can't get back to command input [03:08] RoadRunner: exact command executed, show here [03:09] Two_Dogs: I understand, but after running that command I can't get back to command input [03:09] http://paste.ubuntu.com/p/KFyCRbzdrd/ i tested here, works [03:10] RoadRunner: show command you executed here [03:10] journalctl -b --pri=3 | pastebinit <-- this is what i executed [03:11] Two_Dogs: journalctl -b --pri=3 | pastebinit ## <-is what I did [03:11] sorry: journalctl -b --pri=3 ## [03:12] journalctl -b --pri=3 | pastebinit <-- do RoadRunner [03:12] give me time to reboot, install pastbinit and run your command [03:13] RoadRunner: anything after a '#' is a remark and not code to run [03:15] gnome-shell is a very nice desktop actually, i have kde apps running with qt5ct and they look great [03:16] logout does not seem to be something ready available though [03:21] Two_Dogs: http://paste.ubuntu.com/p/zx3MStwf4S/ [03:23] those errors dont count :) [03:26] what are they? [03:26] RoadRunner: i would re-install lightdm [03:26] hey guys [03:26] i need some help booting into Ubuntu x.x [03:26] Two_Dogs: how? [03:27] RoadRunner: copy/paste & execute via terminal> sudo aptitude reinstall lightdm [03:27] i used Rufus to make a bootable usb stick [03:28] but i just booted into it and it just spit me into grub [03:28] it's been like 3 years since i last used Ubuntu how do i get in [03:28] been struggling to get my laptop working again since upgrading from Ubuntu 17.10 to 18.04. i have an NVIDIA GeForce GTX 1050 Ti graphics card. when i upgraded to 18.04 i started getting a black screen on boot after the Ubuntu splash screen. since then i have installed the nvidia-driver-396 from the graphics-drivers PPA. at first it didn't resolve my inability to boot, so i deleted === Wulf4 is now known as Wulf [03:29] i have the correct root i'm assuming (the USB stick) [03:29] but i don't know where to load the kernel from [03:30] i thought it would have just booted into Ubuntu, not grub [03:30] ... /etc/X11/xorg.conf per #72 from https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+index?comments=all. now my laptop boots, but i can't get it to display on my external monitor anymore. [03:30] Launchpad bug 1752053 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-390 fails to boot graphical display" [Critical,Fix released] [03:30] lighthunter: you installed over the older nvidia driver ? [03:31] .. [03:31] i ran `sudo apt purge *nvidia*` before installing nvidia-driver-396. [03:31] lighthunter: ok [03:31] (and sudo apt autoremove) [03:32] can someone please help me /_\ [03:32] lighthunter: Secure boot disabled ? [03:34] Two_Dogs: "aptitude" didn't fly [03:34] wait [03:34] there we go!! [03:34] Two_Dogs: how about just sudo apt install lightdm? [03:35] typed exit to reach windows boot manager, chose Ubuntu with CAPITAL U, and we in [03:35] :thinking; [03:36] but why were there two options in first place [03:36] one lowercase (grub), one uppercase (proper) [03:36] odd [03:37] good morning to all [03:37] that's an oxymoron [03:42] Bashing-om: yes, i disabled secure boot. [03:45] lighthunter: K; what now does the gpu-manager log relate ? pastebin ' cat /var/log/gpu-manager.log ' . [03:49] https://pastebin.com/hPZen7k3 [03:52] Two_Dogs: ok, removed, purged, reinstalled lightdm - no diff [03:52] ctrl + .alt + f1 sends me to GUI login instead of TTY in Ubuntu 18.04, is there a workaround for this? [03:52] TTY1* [03:53] lighthunter: Intel hybrid system .. what shows ' [03:54] echo $XDG_SESSION_TYPE ' ? [03:54] x11 [03:56] Two_Dogs: if you have any other ideas I'll be happy to try them [03:57] hai #ubuntu [03:57] lighthunter: so far so good . pastebin ' lsmod | grep nvidia ; dpkg -l | grep -i nvidia* ' . [03:59] hello? [04:00] I'm new here :) first time using an IRC client :) [04:00] Can someone tell me something I should now? :) please :) [04:01] Merysan: Welcome to ubuntu support :) [04:01] Thank you :) [04:01] I just followed a tutorial.. and it led me here :) === Tempesta_ is now known as Tempesta [04:02] Merysan: IRC is about asking specific questions that need answered, genreally "tell me something I should know" generally won't get responses [04:02] Merysan: this channel takes ubuntu issues/questions, feel free to ask 'if' you have a problem [04:04] gestalt _ruben [04:05] https://pastebin.com/4KnkKj4Z [04:06] Merysan: i will try to set a good example for you since i am currently asking for help ;). [04:08] okay :) I'll observe the community :) thanks for helping out :) [04:08] you should know what | does [04:08] lol maybe a good lesson is not 20 smiley faces over 4 lines of text :-b [04:09] Merysan: in the meantime, https://github.com/fizerkhan/irc-etiquette has a good summary of the differences between typical face-to-face human interactions and typical human interactions over IRC. [04:09] did Ubuntu change the behavior of ctrl+alt+f1? how can I get to TTY1 now? [04:09] lighthunter: Humm, Mo fault found to this time .. what shows ' sudo lshw -C display ' ? [04:11] https://pastebin.com/BTyVyZBP [04:11] jmw: The GUI now rins in TTY1 . [04:11] runs* [04:11] Bashing-om: hm - how can I get to a terminal, I've had to hard reboot several times because I can't get to a TTY1 terminal to kill software [04:12] Merysan: much of the rationale for that guide comes from the fact that there are, for example, 1,650 users (admittedly probably not all human) in this chatroom at the moment. [04:13] jmadero: Ctrl + Alt + F2 [04:13] (or F3, F4, ...) [04:13] jmadero: try as F2 ? [04:13] will try, brb [04:13] doesn't do anything at all [04:14] i have noticed that sometimes i have to try a few times and/or there is a considerable latency. [04:14] perhaps this is obvious, but you can use Ctrl + Alt + F1 to return to the GUI. [04:15] lighthunter: All the pieces are present . I do not have the skills to say why the desktop is a black screen :( [04:16] lighthunter: in all other versions of Ubuntu and in any other distro I've used F1 is for TTY1 terminal which was ALWAYS useful for killing software that is leaking memory or causing other issues [04:16] I may have to explore other distros again if I can't get to a TTY terminal - this is super weird [04:16] AH f3 ! [04:16] Bashing-om: to be clear, i can boot just fine ever since i deleted /etc/X11/xorg.conf. i simply can't get my computer to recognize an external monitor. [04:17] lighthunter: is the monitor connected now? [04:17] jmadero: yes, Ctrl + Alt + F1 was changed in Ubuntu to be the place the GUI lives. [04:17] Two_Dogs: yes [04:18] lighthunter: does 'xrandr' see both displays? [04:18] no [04:19] https://pastebin.com/tsafgT2p [04:19] lighthunter: Try from a cold boot with the external monitor connected . Does the kernel then pick it up ? [04:19] _running experiment... brb_ [04:20] !forum [04:20] The Ubuntu forums can be found at https://ubuntuforums.org. Kubuntu Forums are found at https://www.kubuntuforums.net. There is also a channel on freenode IRC #ubuntuforums [04:21] ubuntu forums borked or the link? [04:22] Two_Dogs: I am logged into the forum, I have not seen any issues .. lemme check again . [04:23] Bashing-om: share link pls [04:23] Two_Dogs: No problem with the dorum seen here . and the link is correct . [04:23] rebooting with the external monitor connected didn't do the trick, unfortunately. [04:24] Two_Dogs: Presently at https://ubuntuforums.org/search.php?searchid=17432753 . [04:25] lighthunter: excuse the obvious, but a known good cable ? [04:26] Bashing-om: your link works [04:26] he he, fair question. at the very least, i can promise you the cable worked before i upgraded to Ubuntu 18.04. [04:27] lighthunter: share Xorg.0.log pls === FutureShock is now known as Illinium [04:28] lighthunter: either i have seen you ask the same question once before or someone else has same issue or had [04:29] yeah, i was here earlier today too. thewaspsknees helped me get to the point where i am now since previously i couldn't even boot. there are a number of folks with my issue though. [04:30] Two_Dogs: would you like the Xorg.0.log in ~/.local/share/xorg/, /var/log/, or /var/lib/gdm3/.local/share/xorg/? [04:31] Bashing-om: i can confirm that the same HDMI cable currently works with a different laptop also running Ubuntu 18.04 (but lacking the oh so troublesome NVIDIA graphics card). [04:31] lighthunter: i hope the all say same thing, the gdm3 one [04:33] https://pastebin.com/NDReXp05 [04:37] Two_Dogs: lighthunter : Huh ? " 36.435] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) " new one on me ! [04:37] Bashing-om: thats a google [04:41] lighthunter: did you test with default driver? [04:42] do you mean the proprietary nvidia-390 driver, nouveau, or something else? [04:45] lighthunter: did you test with default driver? i mean using system with nvidia purged [04:46] yeah, i believe that would be the nouveau driver. i wasn't able to boot in that case without specifying nomodeset. [04:47] (that much was consistent between Ubuntu 17.10 and Ubuntu 18.04.) [04:48] lighthunter: ok, but were both displays avail? [04:49] lighthunter: install inxi [04:50] i didn't check :-/. [04:51] installing inxi [04:51] lighthunter: copy/paste & execute via terminal> inxi -SGrxxzc0 | nc termbin.com 9999 ## share link output here [04:51] there is no personal data in dump unless you are hardware [04:52] http://termbin.com/823v [04:55] lighthunter: copy/paste & execute via terminal> journalctl --dmesg --pri=3 | nc termbin.com 9999 ## share link output here [04:56] that ubuntu forum is difficult to search [04:58] http://termbin.com/izoe [04:58] which forum are you in out of curiosity? [04:59] Two_Dogs: search ubuntu forum - yeah . better result searching from google as ' site:ubuntuforums.org. ' . [04:59] oh, that ubuntu forum, lol; gotcha. === Jochen_wvdT is now known as Schlawiner [05:00] Bashing-om: thnks [05:05] lighthunter: copy/paste & execute via terminal> (inxi -CMxc0 ; inxi -lsmod ; dkms status) | nc termbin.com 9999 ## share link output here [05:08] http://termbin.com/o2cn (although it looks kinda funky... lots of special characters?) [05:09] https://goo.gl/4R8Lnu lighthunter you are not alone [05:10] lighthunter: inxi -.......Charlie-zero [05:10] Does anyone know how I can run a virtual Ubuntu on a Win10 machine using Hyper-V? If I turn off Hyper-V I can use VirtualBox, but I can't use Docker at the same time [05:12] lighthunter: copy/paste & execute via terminal> (lsmod ; dkms status) | nc termbin.com 9999 ## share link output here [05:13] Mimas: there a nice #vbox channel if you want [05:14] thanks lotuspsychje I'll check there [05:14] Two_Dogs: hmm... yeah... that was charlie zero [05:14] sorry that i can't confirm by copying and pasting [05:14] i am using an IRC client that has Ctrl + C bound to disconnect by default lol [05:16] lighthunter: copy/paste & execute via terminal> (lsmod ; dkms status) | nc termbin.com 9999 ## share link output here [05:17] http://termbin.com/pjp4 [05:20] lighthunter: can you disable onboard 'intel' graphics via bios? [05:23] will try... brb [05:38] hello [05:40] helo world [05:41] Two_Dogs: unfortunately, no, there is no way to disable intel in my UEFI settings :-/. [05:41] lighthunter: ok [05:42] ping [05:42] yes man [05:42] hello [05:43] hello [05:43] where is arch linux channel ? [05:43] #archlinux [05:43] but in #archlinux i should register ! how can i register ? [05:44] barcode: https://freenode.net/kb/answer/registration [05:45] matjam: thanks but i read it before and im confused :( [05:46] lighthunter: you have edited /etc/default/grub previously? [05:46] hey guys, I am having a really strange issue [05:46] barcode: barcode try #freenode [05:47] starting yesterday, my powerful laptop has gotten a lot slower on Ubuntu [05:47] and the reason is really weir [05:47] barcode: this channel is for Ubuntu support. [05:47] my CPU usage won't go above a certain percentage [05:47] causing my computer to lag [05:47] Guy1524_: your machine may be overheating, some chipsets throttle CPU when they are running hot. [05:47] assalamualaikum.. [05:47] my machine isn't hot though [05:48] it's a really strange issue [05:48] it might not feel hot to you but if the built-in sensor is faulty it could be reading a high temperature. [05:49] Two_Dogs: i don't recall ever editing /etc/default/grub, which i suppose isn't necessarily the same thing :-/. [05:49] What is the "madison" argument to apt-cache for? [05:49] hello man [05:49] https://paste.ubuntu.com/p/9575w2NZbN/ [05:50] lighthunter: copy/paste & execute via terminal> cat /etc/default/grub | nc termbin.com 9999 ## share link output here [05:50] SuperLag: if you "man apt-cache" and type "/madison" and hit enter, you'll see the explanation [05:50] it's weird because it just starte happening [05:50] I wasn't even doing much [05:50] when it started [05:51] matjam: Well, that was awesome: man: nroff: Bad system call (core dumped) [05:51] SuperLag: lol [05:51] lighthunter: what method did you use to install nvidia driver? [05:51] SuperLag: wow, that should not be happening [05:51] matjam: I've tried it with both bash and fish. Same result. [05:52] http://termbin.com/jib8 [05:52] "Software & Updates > Additional Drivers > Apply Changes" [05:52] SuperLag: you on 64bit? [05:52] matjam: yep [05:53] (before that i did sudo add-apt-repository ppa:graphics-drivers/ppa.) [05:55] matjam: i regester my nickname but can't find any emails on my mail account [05:55] lighthunter: what editor do you use ? and know how to edit system files? [05:56] vim and yes [05:56] barcode: check your spam folder [05:56] barcode: please ask in #freenode, this is not a support channel for freenode, #freenode is. [05:56] SuperLag: nothing [05:56] barcode: and like matjam said... #freenode [05:57] SuperLag: I see some related bugs in debian which look similar to that error message .. 18.04? [05:57] matjam: yep [05:57] GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.modeset=0" <-- lighthunter make change to file to reflect the added option [05:57] i915.modeset=0 <-- added to line lighthunter [05:58] roger; done. do i need to run sudo update-grub or something like that? [05:58] lighthunter: the point of the exercise is to blacklist i915 intel graphics [05:59] lighthunter: yes, do [05:59] update-grub, do [05:59] and now reboot? [05:59] yes do :) [05:59] yeehaw; brb [06:00] how are you [06:01] SuperLag: I feel like thats a bug in man-db [06:01] SuperLag: i looked on launchpad but dont see anything relevant [06:03] sleepy princess [06:03] matjam: so much for man lookups :D [06:04] hey man where are you life? [06:04] SuperLag: so http://manpages.ubuntu.com/manpages/bionic/man8/apt-cache.8.html [06:04] no one answer in #freenode :) hahaha [06:04] SuperLag: its some old command emulation thing. [06:05] barcode: we can't help you here, please just be patient there. [06:05] just kidding:D [06:05] matjam: okey thanks all [06:06] okey man:) === sapna is now known as sapna_ [06:11] assalamualaikum:D [06:11] matjam: interesting. Thank you. [06:12] Any of you folks use Docker on Ubuntu? (that's how I got to looking at apt-cache stuff) [06:12] yep [06:12] zeeb [06:13] I'm trying to figure out the right package name to install, because even though I've added the repo, there is no package called "docker-ce" === mkv is now known as m4v [06:14] SuperLag: probably because the bionic build doesn't exist yet: https://download.docker.com/linux/ubuntu/dists/bionic/pool/stable/amd64/ [06:14] matjam: looks like it's docker.io [06:15] as there was already a package called docker, but it's something else [06:15] whoami [06:15] yes, docker.io have not published docker for bionic yet. [06:15] I got the url from https://docs.docker.com/install/linux/docker-ce/ubuntu/#set-up-the-repository [06:15] docker in flatpak? [06:16] it does work here [06:16] at least there is some docker.io package https://packages.ubuntu.com/bionic/docker.io [06:16] SuperLag: you could install one of the packages from here https://download.docker.com/linux/ubuntu/dists/bionic/pool/test/amd64/ [06:16] Two_Dogs: boot hung at the splash screen with i915.modeset=0 :-/. [06:16] but you know, not supported, yadda yadda. What did the #docker peeps say [06:17] you should probably go talk to them. [06:17] matjam: I went there first. Pretty quiet this time of night. [06:17] well, you know, we only support #ubuntu in here, not docker .. [06:18] lighthunter: or nvidia is hanging at splash screen? [06:18] matjam: I knew the drill. Thank you for the goodwill, in any case. [06:18] unless its the docker package in ubuntu, then we can support that [06:18] ie, docker.io [06:19] Two_Dogs: certainly possible, i didn't mean to imply that it wasn't nvidia. [06:20] lighthunter: hard to tell, i'll assume i915 is not playing anymore if that option is used [06:21] lighthunter: something else, i would have expected nvidia install to blacklist i915 and nouveau, i915 was active in lsmod and inxi saw it also [06:22] lighthunter: what about the nvidia being borked, considered install of nvidia from nvidia web site? [06:23] lighthunter: besides everything else being possible cause, tried another kernel? your kernel is current? [06:25] could be ... i am reluctant to install from the .run if that's what you mean, because it isn't packaged and doesn't seem to uninstall properly. (also, it didn't come anywhere close to working for me on Ubuntu 17.10.) [06:26] i am on 4.15.0-22-generic. [06:26] i haven't tried another kernel yet. [06:26] i haven't tried the nvidia-390 PPA driver either. [06:27] lighthunter: the kernel on 17.10 was what? and were you using exact driver for nvidia also? [06:27] lighthunter: i would use the nvidia ppa before joebobs ppa [06:28] i was using nvidia-384 if i remember correctly [06:28]