[05:00] <svendre> I got ZFS up and running on root with the daily snapshot!
[05:01] <svendre> I took three tries. Something weird about the installer happened. First two times booted with "try" into gnome and clicked the install icon and I got crashes part-way through. The third time, when it booted, it went right to the screen to choose between try and install, clicked install, and it worked that time.
[05:02] <svendre> The only difference I can think of was that the first couple times I used the bios UEFI to boot from the USB stick, and the third time I just let it boot on it's own, probably in a legacy mode.
[05:04] <svendre> sudo apt remove gnome* and install KDE plasma, and the world is good now.
[06:18] <tomreyn> wonko: hmm, can you pipi the output to hd ?
[06:18] <tomreyn> *pipe ;)
[07:28] <lotuspsychje> svendre: there were some known bugs about zfs going, perhaps join #ubuntu-desktop too, might be interesting for the devs to know your experience
[07:44] <lotuspsychje> bug #1847719
[07:44] <lotuspsychje> bug #1847711
[12:31] <wonko> tomreyn: https://paste.ubuntu.com/p/TgFBbvnGrq/
[12:34] <wonko> tomreyn: ready for round 2? I did `apt purge nginx; rm -rf /etc/nginx; apt install nginx` to get a clean install in case certbot did something dumb and now I have no /etc/nginx (although nginx is installed, running and serving up the same nonsense)
[12:45] <tomreyn> wonko: https://serverfault.com/questions/792825/nginx-proxy-returns-binary-data
[12:47] <wonko> curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number
[12:48] <wonko> but also, where have my config files gone? :)
[12:50] <tomreyn> I could not tell what you're doing, can't watch over your shoulder there. But I'm not convinced that you did "installed nginx, didn't do anything at all to the config so it's all default" and got this.
[12:50] <wonko> did you see my second message after the paste link?
[12:51] <tomreyn> yes, you mention certbot there, which suggests you did change the configuration
[12:51] <wonko> yes, which is why i blew it all away in case certbot did something
[12:51] <wonko> but why didn't I get /etc/nginx back?
[12:51] <tomreyn> dpkg -l *nginx*
[12:52] <tomreyn> ...shows nothing installed?
[12:52] <wonko> ii  nginx          1.16.1-0ubuntu2 all          small, powerful, scalable web/proxy server
[12:53] <tomreyn> oh you said it's still installed, sorry
[12:53] <tomreyn> so you removed /etc/nginx but did not uninstall nginx? why would you do that.
[12:53] <wonko> no, that's not what I did
[12:53] <wonko> I uninstalled nginx
[12:53] <wonko> deleted /etc/nginx
[12:53] <wonko> and re-installed nginx
[12:54] <tomreyn> ah, that's good to know
[12:54] <wonko> which should have created /etc/nginx with the default config, but that's not there
[12:54] <wonko> but it *is* running
[12:54] <ducasse> has testing of the upgrade path from disco to eoan started yet?
[12:55] <tomreyn> wonko: there are several nginx packages
[12:55] <wonko> I believe only one is named `nginx` though. :-D
[12:55] <tomreyn> "dpkg -l *nginx*" only listed this one package as installed?
[12:56] <lotuspsychje> ducasse: i noticed some upgrade bugs to ermine, in #ubuntu-bugs-announce
[12:56] <wonko> tomreyn: yes
[12:57] <tomreyn> wonko: when you uninstalled nginx, did you --purge it?
[12:57] <wonko> yes
[12:57] <lotuspsychje> ducasse: bug #1847615 was one
[12:58] <tomreyn> wonko: then it's unusual that /etc/nginx was still present (when no other *nginx* packages were installed anymore). was there a warning when you purged it that /etc/nginx could not be deleted?
[12:58] <wonko> nope
[12:58] <tomreyn> hmm i can't think of a situation where all of this would come together.
[12:59] <lotuspsychje> ducasse: second: bug #1847603
[12:59] <wonko> Ok, so let's try to get back to the beginning
[12:59] <wonko> I'll remove nginx and then we'll go from there
[13:00] <ducasse> lotuspsychje: both of those are marked 'invalid'
[13:01] <lotuspsychje> ducasse: so i guess upgrading might work?
[13:01] <wonko> tomreyn: oops, I PEBKACed. I did dpkg -L nginx and didn't put the *. THere was some other stuff (nginx-core, nginx-common, libnginx-mod-foo) stuff installed so I just purged all of that.
[13:02] <wonko> dpkg-query: no packages found matching *nginx*
[13:02] <tomreyn> ...
[13:02] <wonko> That's more clean. :)
[13:02] <wonko> now let's try this again
[13:02] <tomreyn> i just installed nginx on a 19.10 system, did curl http://localhost and got the default web page.
[13:02] <ducasse> lotuspsychje: i hope so :)
[13:03] <wonko> yes, and so did I. So certbot indeed did something stupid. Sorry to have wasted your time.
[13:03] <ducasse> lotuspsychje: both those bugs were due to missing the extra modules package
[13:03] <wonko> I'm confused as to why apt purge nginx wouldn't have cleared out those other things though? I mean, it even left running nginx processes. Ugh, no idea.
[13:04] <lotuspsychje> ducasse: yeah
[13:04] <wonko> Oh, because I bet something else installed them
[13:04] <tomreyn> removing nginx would not remove, for example, nginx-core
[13:04] <wonko> after having done apt install nginx I *only* get the nginx listing in the output of dpkg -L *nginx*
[13:05] <tomreyn> nginx depends on nginx-core though+
[13:05] <tomreyn> or one of the other models
[13:06] <tomreyn> -full, -light, -extras
[13:07] <tomreyn> so if you managed to only install the nginx package but no other *nginx* package was installed already or during the nginx installation now then you created the next impossible situation
[13:15] <wonko> I at least have an /etc/nginx. :)
[13:16] <wonko> dpkg -l *nginx* | pastebinit -- https://paste.ubuntu.com/p/wwtNjVdqpK/
[13:16] <wonko> oh, that's -l
[13:16] <wonko> no, that's right, sorry, confusing myself
[13:17] <wonko> tomreyn: you know what? dpkg -l *nginx* doesn't work the way you think it is. :)
[13:17] <tomreyn> but 'dpkg -l *packagename*' won't like packages in states other than ii
[13:18] <wonko> dpkg -l | grep nginx | pastebinit -- https://paste.ubuntu.com/p/6SgJBxYZcT/
[13:18] <wonko> those are all ii
[13:19] <tomreyn> i should mayve put this pattern in quotes, do you have a non default shell?
[13:19] <wonko> nope, default bash
[13:20] <wonko> at least I know who's to blame now, so I guess I'll go back to doing battle with certbot. :)
[13:20] <tomreyn> https://termbin.com/393nj
[13:21] <tomreyn> output of    dpkg -l *nginx*    on my 19.10 installation after "apt install nginx"
[13:21] <tomreyn> default shell
[13:21] <wonko> I still don't get that
[13:22] <tomreyn> is this a fresh install?
[13:22] <wonko> yes
[13:22] <tomreyn> did you copy dotfiles from elsewhere?
[13:22] <wonko> you may remember my upgrade didn't go well. :)
[13:22] <wonko> yes, i restored my homedir
[13:22] <tomreyn> ok, i know whom to blame now, too.
[13:23] <wonko> what would cause dpkg to change its output?
[17:45] <erle-> Is there a known solution to bcmwl not working in 19.10?
[18:03] <tomreyn> is it a known bug?
[18:04] <tomreyn> generally, there will be no solutions without bug reports.
[18:04] <tomreyn> erle-: ^
[18:45] <erle-> tomreyn, there are reports since July
[18:46] <tomreyn> erle-: bug reports on launchpad?
[18:46] <erle-> yes
[18:46] <tomreyn> which ones?
[18:47] <erle-> hm, that one seems fixed
[18:47] <erle-> I should have looked more closely
[18:47] <erle-> https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1836211
[18:47] <erle-> in my case it fails to load wl.ko
[18:47] <erle-> it does not fail to build
[18:53] <tomreyn> erle-: so, if it's still not working with the default kernel image, you probably need to file a new bug?
[18:53] <erle-> I will investigate and report
[18:53] <erle-> thanks
[18:53] <erle-> just wanted to know if this is known already
[18:54] <tomreyn> that's what searching launchpad is best used for
[18:56] <tomreyn> with the advanced search you can search for tags, and release specific bug reports should be tagged with the release codename
[18:56] <tomreyn> so you can search for tag "eoan"
[18:56] <tomreyn> https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.tag=eoan&field.t
[18:56] <tomreyn> ags_combinator=ANY&field.status_upstream-empty-marker=1&field.upstream_target=&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search
[18:56] <tomreyn> oh my, that's a long link, sorry
[18:57] <johnjbogle> I'm having some issue connecting to my local wifi. My machine isn't typically recognizing/detecting any wifi connections even though my apartment building has about 10-20 detectable wifi signals around me, and my wife's dell/ubuntu machine does. Already tried several terminal commands from the advice of a couple different seasoned linux friends, and I discovered that the commands would be reset/nullified if/when I restart/reboot, but if I put it 
 into sleep then wake it up not long after, then that seems to enable the new commands, thus allowing the wifi connections to be detected....until the next time I restart/reboot. I'm really not sure how this started. How can I fix my Network problem of not working properly? thx!
[18:58] <tomreyn> erle-: short link ;) https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bugs?field.tag=eoan
[18:59] <tomreyn> johnjbogle: you also told us this is Ubuntu 19.10 (pre-release) and the wireless chipset is an Intel 7260 [8086:08b1]
[19:00] <tomreyn> johnjbogle: in the "lspci ..." output from earlier, does it say "Kernel driver in use: iwlwifi" ?
[19:00] <johnjbogle> Oh yes, sorry I should have copied down that info too. thx
[19:01] <tomreyn> no worries ;)
[19:01] <tomreyn> johnjbogle: also the output of "uname -r" please
[19:01] <johnjbogle> yes it does
[19:02] <johnjbogle> 5.3.0-13-lowlatency
[19:04] <tomreyn> hmm okay that's not the latest kernel, maybe this is what's breaking it. so, if i got you right, you can occasionally get online?
[19:04] <johnjbogle> Right now, no. 
[19:05] <tomreyn> is there any way you could sum up what these commands your seasoned friends suggested to put into place are?
[19:05] <tomreyn> also, would you loose anything by reinstalling?
[19:07] <johnjbogle> Ok I can list some of the commands from my terminal history...
[19:08] <johnjbogle> Yes I would lose some files.
[19:08] <tomreyn> johnjbogle: and you have no android phone or tab and usb wire there?
[19:15] <johnjbogle> Already tried hotspotting yesterday, didn't work
[19:15] <johnjbogle> Here's the list of those commands we tried...
[19:15] <johnjbogle> sudo iptables -F // sudo dhclient -r // sudo rfkill list all // sudo rfkill unblock wifi ; sudo rfkill unblock all //  sudo rfkill list all // sudo modprobe -r dell-laptop // sudo modprobe -r dell-laptop sudo rfkill unblock all // sudo rmmod // sudo rmmod dell-rbtn // 
[19:16] <tomreyn> ok, thanks.  does     cat /proc/cmdline     say anything other than this?     BOOT_IMAGE=/vmlinuz-5.3.0-13-lowlatency root=(some_path_or_id_here) ro quiet splash vt.handoff=1
[19:18] <johnjbogle> vt.handoff=7
[19:19] <tomreyn> ok, but no other options are added?
[19:19] <tomreyn> i mean extra words
[19:19] <johnjbogle> none
[19:19] <johnjbogle> no
[19:19] <tomreyn> and does     apt list linux-firmware      say something about    "installed"?
[19:20] <johnjbogle> yes
[19:24] <tomreyn> johnjbogle: how many lines of output does this give? if just one, can you type it?   journalctl -b | grep 'iwlwifi.* firmware'
[19:25] <johnjbogle> 2 lines
[19:25] <johnjbogle> well, 1.5
[19:26] <tomreyn> can i see them, please
[19:27] <tomreyn> you could also take photos and upload them to imgur.com if that's easier
[19:28] <johnjbogle> Oct 11 [time] [my-laptop-name] kernal: iwlwifi 0000:02:00.0: loaded firmware version 17.3216344376.0 op_mode iwlmvm
[19:29] <tomreyn> that's it, anything else?
[19:29] <johnjbogle> that's all
[19:30] <tomreyn> can you run this (slightly modified) again:   sudo lspci -knnv | grep -A15 Wireless
[19:30] <tomreyn> and get me the full first line starting at "Intel"?
[19:32] <johnjbogle> Intel Corporation Wireless 7260 [8086:08b1] (rev bb)
[19:33] <tomreyn> thanks. and what does    sudo rfkill list all    report? you can sum it up
[19:34] <tomreyn> actually just tell me whether anything is soft or hard blocked
[19:34] <johnjbogle> Soft Blocked, no. Hard blocked, no. 
[19:35] <tomreyn> does    nmcli c    list your wireless connection?
[19:36] <tomreyn> and does it list a "DEVICE" for this one?
[19:36] <johnjbogle> 3: phy0: Wireless LAN = soft/hard: no. 6: dell-rbtn: Wireless LAN = soft/hard: both YES. 7: nfc0: NFC = soft/hard: both no.
[19:37] <johnjbogle> nmcli c = Yes it does list it
[19:38] <johnjbogle> list a device? I'm not sure
[19:38] <tomreyn> johnjbogle: on the line where you recognized your wireless access point (router), the last column may list a DEVICE or nothing
[19:39] <johnjbogle> Names it lists: virbro , Auto Ethernet , Floor304 [that's my router]
[19:39] <tomreyn> ok, so for Floor304, the right.most column says what?
[19:39] <johnjbogle> Type (in same order): bridge , ethernet , wifi
[19:40] <johnjbogle> DEVICE: virbro , -- , --
[19:40] <genii> valorie: This issue looks suspiciously like what I helped that guy recompile the iwlwifi drivers for the other day
[19:40] <valorie> aha
[19:41] <tomreyn> genii, valorie: if you have any idea / suggestions, i'm all ears, would expect this to just work
[19:41] <tomreyn> but the kernel is a bit outdated
[19:41] <valorie> oh ha
[19:41] <johnjbogle> So for Floor304, right-most column says: --
[19:41] <valorie> you give me far too much credit for knowing anything about this stuff
[19:41] <tomreyn> hehe ok, dont worry then valorie 
[19:42] <tomreyn> will just poke around a bit
[19:42] <valorie> I did manage to make nmcli work for me once upon a time
[19:42] <tomreyn> johnjbogle: thanks. would you remember the password to login to it if you had to?
[19:42] <genii> tomreyn: I'm pretty busy at work right now, but I might be able to go through my backscroll in an hour or two for the solution of that other user ( or possibly valorie might be able to find it sooner)
[19:42] <johnjbogle> i think so 
[19:43] <tomreyn> thanks genii, i guess i may have it, too, then.
[19:43] <tomreyn> valorie: do you know anyhting i could search for in the backscroll?
[19:44] <genii> Basically it's that newer Intel adapters don't work with kernels previous to some version like 5.1 or 5.2, so the drivers have to be manually bac kported by compiling them yourself
[19:44] <tomreyn> johnjbogle: can you run    nm-connection-editor     and just delete this "Floor304" network connection
[19:44] <tomreyn> genii: yes i heard about this. this one is not really new, though.
[19:45] <tomreyn> been supported since linux 3.16
[19:45] <valorie> I lost my backscroll when the power went out to my wifi last night
[19:45] <valorie> :(
[19:46] <johnjbogle> ok done
[19:46] <tomreyn> ok, no worries valorie ;)
[19:46] <tomreyn> johnjbogle: now just use the top right icon to reconnect
[19:46] <tomreyn> you can close the nm-connection-editor window
[19:47] <johnjbogle> nothing happens
[19:48] <tomreyn> johnjbogle: okay, delete it again using nm-connection-editor
[19:49] <johnjbogle> Sorry, already deleted it, and closed the window, but when I try to connect via topright menu item, it does not connect.
[19:51] <tomreyn> ok, now i'd like you to again open nm-connection.editor and delete Floor304 again by dselecting it and clicking the "minus" on the bottom
[19:51] <tomreyn> * selecting, not "dselecting" ;)
[19:51] <johnjbogle> ok will do....
[19:52] <tomreyn> now tell me what does "uptime" report how long this computer has been running?
[19:53] <johnjbogle> Just opened the Net.Connetions window, Floor304 is not listed there now.
[19:53] <tomreyn> ok
[19:53] <tomreyn> please close the nm-connections-editor window
[19:53] <tomreyn> also, is this a laptop or desktop computer?
[19:53] <johnjbogle> ok
[19:55] <tomreyn> johnjbogle: how are you coming?
[19:56] <johnjbogle> sorry didnt see your last question. It is a laptop
 now tell me what does "uptime" report how long this computer has been running?
[19:56] <johnjbogle> Dell Latitude E7440
[19:57] <tomreyn> please see above
[19:57] <johnjbogle> 02:56:53 up  8:09, 1 user, load avg: 0.03, 0.07, 0.06
[19:57] <tomreyn> also tell me how many lines of output does this generate?    lsmod | grep iwl
[19:58] <tomreyn> it's late where you are ;)
[19:58] <johnjbogle> 4 lines
[19:58] <johnjbogle> haha its only 3am
[19:59] <tomreyn> can you tell me what it says on the first columns of these 4 lines
[20:01] <johnjbogle> iwlmvn , mac80211 , iwlwifi , cfg80211
[20:02] <tomreyn> okay, now run:  sudo rmmod iwlwifi
[20:02] <tomreyn> actually this:  sudo rmmod -v iwlwifi
[20:03] <johnjbogle> error, iwlwifi in use by iwlmvm
[20:05] <tomreyn> johnjbogle: okay, now run:  sudo rmmod -v iwlmvm
[20:05] <tomreyn> then again: sudo rmmod -v iwlwifi
[20:06] <johnjbogle> ok
[20:07] <tomreyn> both done?
[20:07] <tomreyn> iwlmvm + iwlwifi ?
[20:07] <johnjbogle> yes both
[20:07] <tomreyn> now open another terminal window and run this    journalctl -fn0
[20:08] <tomreyn> keep it running, we'll just use it as a monitor
[20:08] <johnjbogle> ok done
[20:08] <tomreyn> now check if you can connect to any wireless networks
[20:09] <tomreyn> or whetehr any are listed (top right corner icon)
[20:09] <johnjbogle> nothing listed in topright
[20:10] <tomreyn> is the "journalctl" terminal window already flooded with text?
[20:10] <tomreyn> if it is, press enter there a few times
[20:11] <johnjbogle> yes, ok
[20:11] <tomreyn> okay, now do this in the non-"journalctl" terminal window:   sudo modprobe -v iwlmvm
[20:11] <tomreyn> and then    sudo modprobe -v  iwlwifi
[20:12] <tomreyn> then check the "journalctl" window and see whether anything was logged after those empty lines you produced by pressing enter *that looks like an error message*, and if so, tell me.
[20:12] <johnjbogle> btw, nothing really happens when i hit enter several times, it just repopulates with text, and upon scrolling up, doesn't look like there are any empty lines.
[20:13] <tomreyn> thats fine
[20:13] <johnjbogle> ok
[20:13] <tomreyn> the idea of pressing enter is just to make it easier to tell on the scrollback where you were last reading
[20:14] <tomreyn> (it should have added some blank lines)
[20:15] <johnjbogle> right, but there's so much text that scrolling back up you can't see any blank lines
[20:17] <johnjbogle> because just moving the scrollbar just a tiny fraction, moves through so many massive amount of lines, its impossible to scroll slow/small enough. Hope that makes sense
[20:17] <tomreyn> i see, ok, then let's do it again differently.
[20:17] <johnjbogle> Also, as soon as I move the scrollbar up any amount, it automatically jumps right back down to the bottom.
[20:18] <johnjbogle> ok
[20:18] <tomreyn> press ctrl-c on the journalctl window so you get the normal prompt again
[20:18] <johnjbogle> ok
[20:18] <tomreyn> type "clear" there
[20:19] <tomreyn> then:  sudo rmmod -v iwlmvm; sudo rmmod -v iwlwifi
[20:19] <johnjbogle> ctrl-c, clear in the window with all the text?
[20:19] <tomreyn> yes
 then:  sudo rmmod -v iwlmvm; sudo rmmod -v iwlwifi
[20:20] <johnjbogle> ctrl-c doesnt seem to do anything. And then not able to type clear 
[20:20] <tomreyn> hmm ok then just close this window
[20:20] <tomreyn> and open a new one
[20:20] <johnjbogle> ok
[20:21] <tomreyn> maximize this window
[20:21] <tomreyn> then:  sudo rmmod -v iwlmvm; sudo rmmod -v iwlwifi
[20:21] <tomreyn> then:  journalctl -kfn0
[20:23] <tomreyn> at this point, check and tell me whether the top-right network connections thing still lists any wireless networks to connect to.
[20:23] <johnjbogle> topright menu lists no connections
[20:24] <tomreyn> okay, now back to the other terminal window, or open a new one if none are left
[20:25] <johnjbogle> ok
[20:25] <tomreyn> then: sudo modprobe -v iwlwifi
[20:26] <johnjbogle> ok
[20:26] <tomreyn> then back to the journalctl window, press Ctrl-C there, it should bring back the command prompt
[20:27] <tomreyn> now try to connect to the wireless using the top right icon
[20:28] <johnjbogle> ctrl-c didnt do anything.
[20:29] <tomreyn> strang. does ctrl-z do anything there?
[20:30] <johnjbogle> yes
[20:31] <johnjbogle> [1]+  Stopped       journalctl -kfn0
[20:31] <tomreyn> ok
[20:31] <tomreyn> so can you now connect to the wireless?
[20:33] <johnjbogle> ok so now there is the wireless connection/options/settings in the topright menu
[20:33] <tomreyn> right, and can you connect to your access point?
[20:33] <johnjbogle> But when I select Turn On, nothing happens
[20:33] <tomreyn> okay, that's what happened last time, too?
[20:34] <johnjbogle> No local [neighbor's] connections are listed.
[20:34] <johnjbogle> Correct
[20:34] <tomreyn> now see the journalctl windo's scrollback, look for potential error messages
[20:34] <tomreyn> you should be able to review those logs easier now
[20:35] <tomreyn> it should not be as much as before
[20:35] <johnjbogle> There's only a total of 8 lines.
[20:36] <tomreyn> good, so you have less to review. does it say "E:" (as in "error") or "error" verbatim or warning or "W:" or "cannot" or similar?
[20:38] <johnjbogle> Nothing like those, no
[20:38] <tomreyn> we've now spent two hours on this. this computer has been runnign for a while, and i assume you may have put it to suspend and resumed from that since. suspend / resume could cause instabilities. i suggest you reboot and try connecting again.
[20:39] <tomreyn> but i'd also like to give up here for now, need a break.
[20:39] <johnjbogle> haha no worries, thanks much anyway
[20:40] <tomreyn> you can always backup your data and reinstall using ubuntu 18.04.3 LTS
[20:40] <johnjbogle> But yeah, I don't think it needs a break after only 2 hours, has an i7 and 32gb ram + OS on ssd, so probably should be good for a while :)
[20:41] <tomreyn> chances are it'll just work then. you can also just try from the live / installer system
[20:41] <tomreyn> the one who needs a break is me
[20:41] <johnjbogle> I've already restarted/rebooted many many times the last few days since this started. Definately does not help with anything :(
[20:42] <tomreyn> okay, looks like you've pretty much come to a dead end. i suggest installing 18.04.3
[20:42] <johnjbogle> aha no worries. Is there anyone else who can assist? Or should I come back to here after how long?
[20:42] <johnjbogle> hmm... 
[20:43] <tomreyn> you can sum up the issue again on a pastebin and ask for help here (less likely to work, since this is a pre-release version) or in #ubuntu (when you are running 18.04.3 LTS)
[20:44] <tomreyn> if you get the system online by some other means this will certainly be a huge leap forward in getting a chance to fix it for good.
[20:44] <tomreyn> good luck, and see you later, johnjbogle 
[20:45] <johnjbogle> thanks much for all
[20:47] <tomreyn> you're welcome. oh and also consider a firmware upgrade. your current bios version can be listed with    journalctl -b | grep 'DMI:'
[20:53] <tomreyn> latest bios is Version A27 https://www.dell.com/support/home/uk/en/ukbsdt1/drivers/driversdetails?driverid=kdfy1&oscode=biosa&productcode=latitude-e7440-ultrabook&lwp=rt
[20:54] <tomreyn> bios upgrade procedure https://wiki.archlinux.org/index.php/Dell_Latitude_E7440#Check_the_BIOS_firmware_first