/srv/irclogs.ubuntu.com/2019/10/11/#ubuntu+1.txt

svendreI got ZFS up and running on root with the daily snapshot!05:00
svendreI 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:01
svendreThe 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:02
svendresudo apt remove gnome* and install KDE plasma, and the world is good now.05:04
tomreynwonko: hmm, can you pipi the output to hd ?06:18
tomreyn*pipe ;)06:18
lotuspsychjesvendre: there were some known bugs about zfs going, perhaps join #ubuntu-desktop too, might be interesting for the devs to know your experience07:28
lotuspsychjebug #184771907:44
ubottubug 1847719 in ubiquity (Ubuntu) "The experimental zfs "Write to change disks" shows an ext4 partition will be created" [Undecided,New] https://launchpad.net/bugs/184771907:44
lotuspsychjebug #184771107:44
ubottubug 1847711 in zsys (Ubuntu) "Move zsys tags from org.zsys to com.ubuntu.zsys" [Undecided,New] https://launchpad.net/bugs/184771107:44
wonkotomreyn: https://paste.ubuntu.com/p/TgFBbvnGrq/12:31
wonkotomreyn: 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:34
tomreynwonko: https://serverfault.com/questions/792825/nginx-proxy-returns-binary-data12:45
wonkocurl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number12:47
wonkobut also, where have my config files gone? :)12:48
=== lotus|i5 is now known as lotuspsychje
tomreynI 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
wonkodid you see my second message after the paste link?12:50
tomreynyes, you mention certbot there, which suggests you did change the configuration12:51
wonkoyes, which is why i blew it all away in case certbot did something12:51
wonkobut why didn't I get /etc/nginx back?12:51
tomreyndpkg -l *nginx*12:51
tomreyn...shows nothing installed?12:52
wonkoii  nginx          1.16.1-0ubuntu2 all          small, powerful, scalable web/proxy server12:52
tomreynoh you said it's still installed, sorry12:53
tomreynso you removed /etc/nginx but did not uninstall nginx? why would you do that.12:53
wonkono, that's not what I did12:53
wonkoI uninstalled nginx12:53
wonkodeleted /etc/nginx12:53
wonkoand re-installed nginx12:53
tomreynah, that's good to know12:54
wonkowhich should have created /etc/nginx with the default config, but that's not there12:54
wonkobut it *is* running12:54
ducassehas testing of the upgrade path from disco to eoan started yet?12:54
tomreynwonko: there are several nginx packages12:55
wonkoI believe only one is named `nginx` though. :-D12:55
tomreyn"dpkg -l *nginx*" only listed this one package as installed?12:55
lotuspsychjeducasse: i noticed some upgrade bugs to ermine, in #ubuntu-bugs-announce12:56
wonkotomreyn: yes12:56
tomreynwonko: when you uninstalled nginx, did you --purge it?12:57
wonkoyes12:57
lotuspsychjeducasse: bug #1847615 was one12:57
ubottubug 1847615 in linux (Ubuntu) "After upgrading Ubuntu 19.10 sound not working on HP EliteDesk 800 G2 SFF" [Undecided,Invalid] https://launchpad.net/bugs/184761512:57
tomreynwonko: 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
wonkonope12:58
tomreynhmm i can't think of a situation where all of this would come together.12:58
lotuspsychjeducasse: second: bug #184760312:59
ubottubug 1847603 in lightdm (Ubuntu) "After upgrading Ubuntu 19.10 second screen not detected" [Undecided,Invalid] https://launchpad.net/bugs/184760312:59
wonkoOk, so let's try to get back to the beginning12:59
wonkoI'll remove nginx and then we'll go from there12:59
ducasselotuspsychje: both of those are marked 'invalid'13:00
lotuspsychjeducasse: so i guess upgrading might work?13:01
wonkotomreyn: 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:01
wonkodpkg-query: no packages found matching *nginx*13:02
tomreyn...13:02
wonkoThat's more clean. :)13:02
wonkonow let's try this again13:02
tomreyni just installed nginx on a 19.10 system, did curl http://localhost and got the default web page.13:02
ducasselotuspsychje: i hope so :)13:02
wonkoyes, and so did I. So certbot indeed did something stupid. Sorry to have wasted your time.13:03
ducasselotuspsychje: both those bugs were due to missing the extra modules package13:03
wonkoI'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:03
lotuspsychjeducasse: yeah13:04
wonkoOh, because I bet something else installed them13:04
tomreynremoving nginx would not remove, for example, nginx-core13:04
wonkoafter having done apt install nginx I *only* get the nginx listing in the output of dpkg -L *nginx*13:04
tomreynnginx depends on nginx-core though+13:05
tomreynor one of the other models13:05
tomreyn-full, -light, -extras13:06
tomreynso 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 situation13:07
wonkoI at least have an /etc/nginx. :)13:15
wonkodpkg -l *nginx* | pastebinit -- https://paste.ubuntu.com/p/wwtNjVdqpK/13:16
wonkooh, that's -l13:16
wonkono, that's right, sorry, confusing myself13:16
wonkotomreyn: you know what? dpkg -l *nginx* doesn't work the way you think it is. :)13:17
tomreynbut 'dpkg -l *packagename*' won't like packages in states other than ii13:17
wonkodpkg -l | grep nginx | pastebinit -- https://paste.ubuntu.com/p/6SgJBxYZcT/13:18
wonkothose are all ii13:18
tomreyni should mayve put this pattern in quotes, do you have a non default shell?13:19
wonkonope, default bash13:19
wonkoat least I know who's to blame now, so I guess I'll go back to doing battle with certbot. :)13:20
tomreynhttps://termbin.com/393nj13:20
tomreynoutput of    dpkg -l *nginx*    on my 19.10 installation after "apt install nginx"13:21
tomreyndefault shell13:21
wonkoI still don't get that13:21
tomreynis this a fresh install?13:22
wonkoyes13:22
tomreyndid you copy dotfiles from elsewhere?13:22
wonkoyou may remember my upgrade didn't go well. :)13:22
wonkoyes, i restored my homedir13:22
tomreynok, i know whom to blame now, too.13:22
wonkowhat would cause dpkg to change its output?13:23
erle-Is there a known solution to bcmwl not working in 19.10?17:45
tomreynis it a known bug?18:03
tomreyngenerally, there will be no solutions without bug reports.18:04
tomreynerle-: ^18:04
erle-tomreyn, there are reports since July18:45
tomreynerle-: bug reports on launchpad?18:46
erle-yes18:46
tomreynwhich ones?18:46
erle-hm, that one seems fixed18:47
erle-I should have looked more closely18:47
erle-https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/183621118:47
ubottuLaunchpad bug 1836211 in bcmwl (Ubuntu) "bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic)" [Undecided,Fix released]18:47
erle-in my case it fails to load wl.ko18:47
erle-it does not fail to build18:47
tomreynerle-: 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 report18:53
erle-thanks18:53
erle-just wanted to know if this is known already18:53
tomreynthat's what searching launchpad is best used for18:54
tomreynwith the advanced search you can search for tags, and release specific bug reports should be tagged with the release codename18:56
tomreynso you can search for tag "eoan"18:56
tomreynhttps://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.t18:56
tomreynags_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=Search18:56
tomreynoh my, that's a long link, sorry18:56
johnjbogleI'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 18:57
johnjbogle<johnjbogle> 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:57
tomreynerle-: short link ;) https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bugs?field.tag=eoan18:58
tomreynjohnjbogle: you also told us this is Ubuntu 19.10 (pre-release) and the wireless chipset is an Intel 7260 [8086:08b1]18:59
tomreynjohnjbogle: in the "lspci ..." output from earlier, does it say "Kernel driver in use: iwlwifi" ?19:00
johnjbogleOh yes, sorry I should have copied down that info too. thx19:00
tomreynno worries ;)19:01
tomreynjohnjbogle: also the output of "uname -r" please19:01
johnjbogleyes it does19:01
johnjbogle5.3.0-13-lowlatency19:02
tomreynhmm 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
johnjbogleRight now, no. 19:04
tomreynis there any way you could sum up what these commands your seasoned friends suggested to put into place are?19:05
tomreynalso, would you loose anything by reinstalling?19:05
johnjbogleOk I can list some of the commands from my terminal history...19:07
johnjbogleYes I would lose some files.19:08
tomreynjohnjbogle: and you have no android phone or tab and usb wire there?19:08
johnjbogleAlready tried hotspotting yesterday, didn't work19:15
johnjbogleHere's the list of those commands we tried...19:15
johnjboglesudo 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:15
tomreynok, 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=119:16
johnjboglevt.handoff=719:18
tomreynok, but no other options are added?19:19
tomreyni mean extra words19:19
johnjboglenone19:19
johnjbogleno19:19
tomreynand does     apt list linux-firmware      say something about    "installed"?19:19
johnjbogleyes19:20
tomreynjohnjbogle: how many lines of output does this give? if just one, can you type it?   journalctl -b | grep 'iwlwifi.* firmware'19:24
johnjbogle2 lines19:25
johnjboglewell, 1.519:25
tomreyncan i see them, please19:26
tomreynyou could also take photos and upload them to imgur.com if that's easier19:27
johnjbogleOct 11 [time] [my-laptop-name] kernal: iwlwifi 0000:02:00.0: loaded firmware version 17.3216344376.0 op_mode iwlmvm19:28
tomreynthat's it, anything else?19:29
johnjboglethat's all19:29
tomreyncan you run this (slightly modified) again:   sudo lspci -knnv | grep -A15 Wireless19:30
tomreynand get me the full first line starting at "Intel"?19:30
johnjbogleIntel Corporation Wireless 7260 [8086:08b1] (rev bb)19:32
tomreynthanks. and what does    sudo rfkill list all    report? you can sum it up19:33
tomreynactually just tell me whether anything is soft or hard blocked19:34
johnjbogleSoft Blocked, no. Hard blocked, no. 19:34
tomreyndoes    nmcli c    list your wireless connection?19:35
tomreynand does it list a "DEVICE" for this one?19:36
johnjbogle3: phy0: Wireless LAN = soft/hard: no. 6: dell-rbtn: Wireless LAN = soft/hard: both YES. 7: nfc0: NFC = soft/hard: both no.19:36
johnjboglenmcli c = Yes it does list it19:37
johnjboglelist a device? I'm not sure19:38
tomreynjohnjbogle: on the line where you recognized your wireless access point (router), the last column may list a DEVICE or nothing19:38
johnjbogleNames it lists: virbro , Auto Ethernet , Floor304 [that's my router]19:39
tomreynok, so for Floor304, the right.most column says what?19:39
johnjbogleType (in same order): bridge , ethernet , wifi19:39
johnjbogleDEVICE: virbro , -- , --19:40
geniivalorie: This issue looks suspiciously like what I helped that guy recompile the iwlwifi drivers for the other day19:40
valorieaha19:40
tomreyngenii, valorie: if you have any idea / suggestions, i'm all ears, would expect this to just work19:41
tomreynbut the kernel is a bit outdated19:41
valorieoh ha19:41
johnjbogleSo for Floor304, right-most column says: --19:41
valorieyou give me far too much credit for knowing anything about this stuff19:41
tomreynhehe ok, dont worry then valorie 19:41
tomreynwill just poke around a bit19:42
valorieI did manage to make nmcli work for me once upon a time19:42
tomreynjohnjbogle: thanks. would you remember the password to login to it if you had to?19:42
geniitomreyn: 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
johnjboglei think so 19:42
tomreynthanks genii, i guess i may have it, too, then.19:43
tomreynvalorie: do you know anyhting i could search for in the backscroll?19:43
geniiBasically 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 yourself19:44
tomreynjohnjbogle: can you run    nm-connection-editor     and just delete this "Floor304" network connection19:44
tomreyngenii: yes i heard about this. this one is not really new, though.19:44
tomreynbeen supported since linux 3.1619:45
valorieI lost my backscroll when the power went out to my wifi last night19:45
valorie:(19:45
johnjbogleok done19:46
tomreynok, no worries valorie ;)19:46
tomreynjohnjbogle: now just use the top right icon to reconnect19:46
tomreynyou can close the nm-connection-editor window19:46
johnjboglenothing happens19:47
tomreynjohnjbogle: okay, delete it again using nm-connection-editor19:48
johnjbogleSorry, already deleted it, and closed the window, but when I try to connect via topright menu item, it does not connect.19:49
tomreynok, now i'd like you to again open nm-connection.editor and delete Floor304 again by dselecting it and clicking the "minus" on the bottom19:51
tomreyn* selecting, not "dselecting" ;)19:51
johnjbogleok will do....19:51
tomreynnow tell me what does "uptime" report how long this computer has been running?19:52
johnjbogleJust opened the Net.Connetions window, Floor304 is not listed there now.19:53
tomreynok19:53
tomreynplease close the nm-connections-editor window19:53
tomreynalso, is this a laptop or desktop computer?19:53
johnjbogleok19:53
tomreynjohnjbogle: how are you coming?19:55
johnjboglesorry didnt see your last question. It is a laptop19:56
tomreyn<tomreyn> now tell me what does "uptime" report how long this computer has been running?19:56
johnjbogleDell Latitude E744019:56
tomreynplease see above19:57
johnjbogle02:56:53 up  8:09, 1 user, load avg: 0.03, 0.07, 0.0619:57
tomreynalso tell me how many lines of output does this generate?    lsmod | grep iwl19:57
tomreynit's late where you are ;)19:58
johnjbogle4 lines19:58
johnjboglehaha its only 3am19:58
tomreyncan you tell me what it says on the first columns of these 4 lines19:59
johnjbogleiwlmvn , mac80211 , iwlwifi , cfg8021120:01
tomreynokay, now run:  sudo rmmod iwlwifi20:02
tomreynactually this:  sudo rmmod -v iwlwifi20:02
johnjbogleerror, iwlwifi in use by iwlmvm20:03
tomreynjohnjbogle: okay, now run:  sudo rmmod -v iwlmvm20:05
tomreynthen again: sudo rmmod -v iwlwifi20:05
johnjbogleok20:06
tomreynboth done?20:07
tomreyniwlmvm + iwlwifi ?20:07
johnjbogleyes both20:07
tomreynnow open another terminal window and run this    journalctl -fn020:07
tomreynkeep it running, we'll just use it as a monitor20:08
johnjbogleok done20:08
tomreynnow check if you can connect to any wireless networks20:08
tomreynor whetehr any are listed (top right corner icon)20:09
johnjboglenothing listed in topright20:09
tomreynis the "journalctl" terminal window already flooded with text?20:10
tomreynif it is, press enter there a few times20:10
johnjbogleyes, ok20:11
tomreynokay, now do this in the non-"journalctl" terminal window:   sudo modprobe -v iwlmvm20:11
tomreynand then    sudo modprobe -v  iwlwifi20:11
tomreynthen 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
johnjboglebtw, 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:12
tomreynthats fine20:13
johnjbogleok20:13
tomreynthe idea of pressing enter is just to make it easier to tell on the scrollback where you were last reading20:13
tomreyn(it should have added some blank lines)20:14
johnjbogleright, but there's so much text that scrolling back up you can't see any blank lines20:15
johnjboglebecause 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 sense20:17
tomreyni see, ok, then let's do it again differently.20:17
johnjbogleAlso, as soon as I move the scrollbar up any amount, it automatically jumps right back down to the bottom.20:17
johnjbogleok20:18
tomreynpress ctrl-c on the journalctl window so you get the normal prompt again20:18
johnjbogleok20:18
tomreyntype "clear" there20:18
tomreynthen:  sudo rmmod -v iwlmvm; sudo rmmod -v iwlwifi20:19
johnjboglectrl-c, clear in the window with all the text?20:19
tomreynyes20:19
tomreyn<tomreyn> then:  sudo rmmod -v iwlmvm; sudo rmmod -v iwlwifi20:20
johnjboglectrl-c doesnt seem to do anything. And then not able to type clear 20:20
tomreynhmm ok then just close this window20:20
tomreynand open a new one20:20
johnjbogleok20:20
tomreynmaximize this window20:21
tomreynthen:  sudo rmmod -v iwlmvm; sudo rmmod -v iwlwifi20:21
tomreynthen:  journalctl -kfn020:21
tomreynat this point, check and tell me whether the top-right network connections thing still lists any wireless networks to connect to.20:23
johnjbogletopright menu lists no connections20:23
tomreynokay, now back to the other terminal window, or open a new one if none are left20:24
johnjbogleok20:25
tomreynthen: sudo modprobe -v iwlwifi20:25
johnjbogleok20:26
tomreynthen back to the journalctl window, press Ctrl-C there, it should bring back the command prompt20:26
tomreynnow try to connect to the wireless using the top right icon20:27
johnjboglectrl-c didnt do anything.20:28
tomreynstrang. does ctrl-z do anything there?20:29
johnjbogleyes20:30
johnjbogle[1]+  Stopped       journalctl -kfn020:31
tomreynok20:31
tomreynso can you now connect to the wireless?20:31
johnjbogleok so now there is the wireless connection/options/settings in the topright menu20:33
tomreynright, and can you connect to your access point?20:33
johnjbogleBut when I select Turn On, nothing happens20:33
tomreynokay, that's what happened last time, too?20:33
johnjbogleNo local [neighbor's] connections are listed.20:34
johnjbogleCorrect20:34
tomreynnow see the journalctl windo's scrollback, look for potential error messages20:34
tomreynyou should be able to review those logs easier now20:34
tomreynit should not be as much as before20:35
johnjbogleThere's only a total of 8 lines.20:35
tomreyngood, 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:36
johnjbogleNothing like those, no20:38
tomreynwe'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:38
tomreynbut i'd also like to give up here for now, need a break.20:39
johnjboglehaha no worries, thanks much anyway20:39
tomreynyou can always backup your data and reinstall using ubuntu 18.04.3 LTS20:40
johnjbogleBut 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:40
tomreynchances are it'll just work then. you can also just try from the live / installer system20:41
tomreynthe one who needs a break is me20:41
johnjbogleI've already restarted/rebooted many many times the last few days since this started. Definately does not help with anything :(20:41
tomreynokay, looks like you've pretty much come to a dead end. i suggest installing 18.04.320:42
johnjbogleaha no worries. Is there anyone else who can assist? Or should I come back to here after how long?20:42
johnjboglehmm... 20:42
tomreynyou 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:43
tomreynif 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
tomreyngood luck, and see you later, johnjbogle 20:44
johnjboglethanks much for all20:45
tomreynyou're welcome. oh and also consider a firmware upgrade. your current bios version can be listed with    journalctl -b | grep 'DMI:'20:47
tomreynlatest bios is Version A27 https://www.dell.com/support/home/uk/en/ukbsdt1/drivers/driversdetails?driverid=kdfy1&oscode=biosa&productcode=latitude-e7440-ultrabook&lwp=rt20:53
tomreynbios upgrade procedure https://wiki.archlinux.org/index.php/Dell_Latitude_E7440#Check_the_BIOS_firmware_first20:54

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!