[00:16] <Ronalds_Mazitis_> hey
[00:16] <Ronalds_Mazitis_> wassup ubuntu
[00:17] <Ronalds_Mazitis_> I have technical question that really matters to me, I haven't done this long time
[00:17] <Bashing-om> !ask | Ronalds_Mazitis_
[00:18] <Ronalds_Mazitis_> we aren't going to be robots in future or are we? I want to remove brownish colors from video that I feel like was totally faked again
[01:24] <ash_worksi> I seem to be having a bit of trouble with my screensize using tmux and I don't know if it's because of gnome-terminal or not
[01:27] <ash_worksi> nvm, this seems to be a problem with my `expect` script
[01:31] <ash_worksi> yep everything works when I don't use the expect script
[01:56] <DarkTrick_> seem like the shim bug is fixed :)
[02:28] <EdCdLiSwP> Andfrkew sLDee liIkesp hot asvian cochks!!!
[02:28] <DySRBySBgTL> I hope Cyou enjoyed yrour freeO 1J0a0000% nlevgitimate yardvertizsingC
[02:29] <ucDZqhMh> I hope you enjoyed yovur Rfreex 100000% BlegitHimateN adverXtisqinge
[02:29] <cSLpNVcIciiY> HHih LHibera JustE lPayinTgI az Vismit :K)))b))U))
[02:30] <uPtgUHvOV> Havec fun - gABeNH
[02:30] <uPtgUHvOV> Have Lfun r- gABeN
[02:30] <mzBOGHAOdVPE> Andrrew Lnee lifkes hot asian cRocmks!C!S!
[02:31] <ijrbYFvEEf> Hbi Libera JuXsHti Payinpg aC Vissit P:))Y)l)))Z)
[02:33] <OGjxcacvz> Have fun - mgABVeN
[02:36] <HmEGLKmygF> Have fuVn - gABeNa
[02:36] <lANZlRlGF> Andrew Lpee liNkes hotL asMian dcocks!L!w!
[02:36] <UjGMsMgfs> Ie hlope yuobu enjDoyed oyour friexe 1Q00000% legitifmate advIevrZtPising
[02:36] <lANZlRlGF> AndrewC Lee likteBs hot aosianw Fcockqs!!!
[02:36] <oAKhNtyaDICw> HEave fuhn - gABeN
[02:36] <LlKpHZFGLdB> Hi Liberav rJust PayinZg a fVisit :)))))))
[02:37] <CmXVKNmFfXkB> I fhNopTe tyou enjoyfed your free 10b0f000% llegitipmaUtSe advertgising
[02:37] <MyWoyMkBYoh> Have fXun - gABeN
[02:37] <htSKTNIrvE> I heope yoRu enjoyed youdr foree G100H000% legitimate adveartiYsing
[02:37] <lotuspsychje> !ops
[02:37] <TfrHtatJsy> Have TfWuvn - gABeN
[03:24] <gbit86_> When it comes to filing bugs & including patches to fix said bug is there anything more that ought to be done or included to help it go smoothly? I just want to minimize any back & forth and get the ball rolling I guess so it can get into the testing phases. https://bugs.launchpad.net/ubuntu/+source/vala-panel-appmenu/+bug/1930615
[03:27] <sarnold> gbit86_: does that patch cause a memory leak?
[03:28] <sarnold> oh wow that patch is a lot bigger than I first thought, heh
[03:28] <gbit86_> Umm.. not that I am aware of - although reading through the other open bugs someone indicates they may have one when using the app in general with xfce4. I've not monitored it that closely either way and just got the assistance of @fossfreedom to backport some specific commits to resolve the issue.
[03:30] <gbit86_> I think that diff patch is like 3 commits from the 0.7.5 release (not sure if that's all of the commits in that release or not) and one other commit to resolve some issue related to building the source itself. Not sure which release that one came from - I did not ask fossfreedom that question but I assume he pulled from another existing commit by the author as well.
[03:32] <gbit86_> So yea in total it is probably 4 commits merged into that one diff to resolve the menu crashing bug - that is definitely there on 20.04 and definitely affects all VS Code users that would use it on 20.04 LTS.
[03:34] <gbit86_> It is a pretty nasty memory segmentation fault too - on Budgie it completely kicks users out of their session. Not sure about xfce4, I was only running the xfce4-panel when testing - not the entire xfce4 environment so - if it is to behave the same way as Budgie does then I assume I might need to run the entire DE instead of Gnome w/ the xfce4-panel lol.
[03:35] <gbit86_> Xfce4-panel does crash as well, but again it was just that one component so it didn't kick me out of my user session when it occurred. It would just prompt me to restart the plugin, of course the patch resolves that issue quite nicely.
[03:36] <sarnold> gbit86_: yikes that sounds bad news
[03:37] <sarnold> gbit86_: probably a nice self-contained test case would help immensely; eg 'install budgie-panel, run budgie-panel; untar this file; double-click this thing in the panel'
[03:38] <gbit86_> yea and it kinda surprises me that I only found one other user that reported the issue - but in the wrong place, they reported to Solus and their Budgie repo and it died a quiet death some months ago because Solus does not care about Global Menu apps and so yea I filed this bug in several places to figure out who needs to address it. And maybe Solus/Budgie really can't do anything to handle a memory segmentation fault error caused by
[03:38] <gbit86_> a plugin any ways lol.
[03:41] <gbit86_> Hmmm.. yea, I can spell things out like that. I'd assume the easiest way to test would be to just spin up a VM of Ubuntu Budgie and select the Cupertino layout and then install VS Code however they want. They'll see the issue occur pretty quickly. Little harder with Xubuntu, but not much - they'd need to manually install the budgie-panel, apply a few commands and then setup the plugin in the panel.
[03:42] <sarnold> heh maybe the VM approach then :) still, some nice simple step-by-step instructions that show the problem reliably is worth its weight in gold
[03:42] <gbit86_> correction lol - they'd need to install the vala-appmenu for xfce4 - not budgie😂
[03:44] <gbit86_> I must be tired tonight and yea I can update it with the vm budgie example. I might mention a few things about testing it in xubuntu or with xfce4 in general just so they can for sure get it running. I know the vala-appmenu can be difficult to get going for anyone that never has before. Why I document it in my Kinto.sh app - so it isn't a mystery lol.
[06:17] <pikapika> Does linux use 16 bits to index x or y direction in graphics?
[06:18] <pikapika> Does linux always use 16 bits to index x or y direction in graphics?
[06:19] <pikapika> What are the upper two bits for?
[06:20] <pikapika> It says a "maximum" of 16384x16384 for my laptop screen in xrandr
[06:20] <pikapika> I am "guessing" but of course cannot be certain without seeing the source, that this indicates 16 bit indices, and two bits being dedicated for something
[06:41] <rfm> pikapika, the original X11 protocol specifies coordinates as 16-bit signed numbers.  I assume they used signed to make relative vector drawing easy...
[06:43] <rfm> pikapika, and made the max half the size so a coordinate + a delta would never overflow
[07:01] <Ginalo> Hi. My installation keeps giving me an error when updating apt packages. One thing I think is a possible cause of this is when a power outage occurred yesterday, and I think I was updating packages that time, too. https://www.irccloud.com/pastebin/2fnhdnz9/
[07:59] <jason1234> hi
[07:59] <jason1234> a question, where to find i386 last ubuntu DVD?
[08:00] <remhaze> jason1234> DVD ?
[08:01] <oerheks> lubuntu, mate or xubuntu https://cdimage.ubuntu.com/xubuntu/releases/18.04/release/
[08:01] <Unit193> Bionic would be the best one to use for i386, or perhaps Debian instead.
[08:01] <guiverc> jason1234, Ubuntu Desktop didn't produce a i386 ISO, only flavors did but http://archive.ubuntu.com/ubuntu/dists/bionic-updates/main/installer-i386/current/images/netboot/ will provide the latest netboot ISO
[08:01] <oerheks> or netboot, universal indeed
[08:02] <jason1234> I need the dvd i386, where is it on FTP?
[08:03] <oerheks> i gave you  an url ?
[08:03] <guiverc> Ubuntu Desktop didn't produce a ISO for 18.04; so last i386 supported for Ubuntu Desktop was 16.04 that is now EOL
[08:03] <oerheks> 	1.4G
[08:04] <jason1234> what are doing the dev? cannot it be possible?
[08:05] <jason1234> are you crazy? kidding?
[08:05] <oerheks> i386 is fading out, so be happy there is still a i386 iso and packages
[08:05] <oerheks> so, if you find a huge team, you can go on with development
[08:06] <jason1234> amazing.. such a big development team, and there is noone to make a i386. it is not much demanded.
[08:06] <guiverc> Ubuntu 17.10 & 18.04 did not provide ISOs for Ubuntu Desktops.. i386 continued to 18.04 for flavors, with Lubuntu & Xubuntu going to 18.10 releases & alpha for i386/19.04/disco before they dropped it too (19.04 was last release with i386 full package support)
[08:07] <oerheks>  Arch Linux, Ubuntu, Fedora, everyone has dropped the support for this older architecture ..
[08:07] <oerheks> get over it
[08:09] <jason1234> oerheks: what huge references, fedora and Ubuntu, they are just commercials. Other Linux will keep i386, like debian, for a while.
[08:10] <Unit193> Ubuntu tries to target only modern hardware, whereas Debian will keep very old ports alive for as long as there are porters.  Just different targets.
[08:12] <Thete> you still have a 32bit only machine?
[08:13] <ExeciN> the last desktop CPU by intel was produced in 2002, if you really need to work with this kind of hardware you can go debian
[08:14] <Unit193> Third world countries continued to produce them, from what I recall.
[08:15] <ExeciN> purchase them? maybe. produce them? I don't think so
[10:36] <LarsErikP> Hi! Does anyone know when the kernel for bionic-hwe would be updated? It's currently 5.4.0-42 in -updates, bout I would really like to have a version that includes the fix for the i40e driver here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893956
[10:44] <nikolam> I worry because my machine keeps disconnecting from both network connections at the same time, until I restart machine. It is 21.04 and 2 LAN cards with 2 internet connections.. And netplan config file for them.
[10:46] <LarsErikP> actually.. I see that linux-image-generic-hwe-18.04 package is 5.4.0-74, so I guess I only need a netboot image with the same version..
[11:02] <yosh_> yo
[11:18] <LarsErikP> So, the hwe-netboot installer eventually installed and booted into 5.4.0-74-generic. That kernel has the updated i40e driver, and my NIC works fine. How can I netboot from a newer kernel? Will it at some point be updated?
[11:28] <node1> Hello
[11:29] <node1> I'm looking for a support regarding finding the root cause of file system corruption. Recently i have come across a problem when i booted my system it drops me to initramfs(busybox) console. I'm not sure why this happen?
[11:30] <TJ-> node1: is the OS install encrypted or unencrypted?
[11:30] <node1> You mean disk unencrypted? well no
[11:31] <larkfisherman> node1: BIOS or UEFI?
[11:31] <node1> I'm just find the cause what makes my ubuntu to drop in initramfs busybox console?
[11:32] <node1> I think it's BIOS. I have not sure. How to sure you know any command?
[11:32] <LarsErikP> so.. how do I file a bug to get the linux and initrd.gz for bionic hwe-netboot updated?
[11:32] <node1> s/have/am
[11:35] <TJ-> LarsErikP: possibly via linux-meta package
[11:36] <LarsErikP> TJ-: here? https://bugs.launchpad.net/ubuntu/+source/linux-meta
[11:36] <node1> I think it's UEFI as i can see there are files and directory with name  efi at /sys/firmware/
[11:38] <f_ayx>  hi channel... trying to install an application using an install script I get the following output
[11:39] <f_ayx> → ./install.sh
[11:39] <f_ayx> -- The C compiler identification is GNU 7.3.0
[11:39] <f_ayx> -- The CXX compiler identification is GNU 7.3.0
[11:39] <f_ayx> -- Check for working C compiler: /home/me/anaconda3/bin/x86_64-conda_cos6-linux-gnu-cc
[11:39] <f_ayx> -- Check for working C compiler: /home/me/anaconda3/bin/x86_64-conda_cos6-linux-gnu-cc -- works
[11:39] <f_ayx> -- Detecting C compiler ABI info
[11:40] <larkfisherman> node1: is the command "efibootmgr -v" available in the busybox console?
[11:41] <TJ-> larkfisherman: I /think/ so although as you're on about the ISO/img installer files it could be another project. Start there though, and someeone will reassign it if needed
[11:41] <node1> larkfisherman, Actually i came out from the console by running fsck on sda1 and sda2
[11:42] <node1> Here i'm trying to find out the root cause of the problem. What makes my system to behave in this manner
[11:42] <TJ-> node1: if you're dropped to the initrd shell you need to check if the root file-system is available, and if so, in what state. "cat /proc/cmdline" will reveal which file-system you need to focus on
[11:43] <node1> Thank you TJ-
[11:43] <node1> Anything more you like to share debugging information. ?
[11:56] <dan> Hi everyone, I disabled PAM in ssh  config. After doing that, I lost ls
[11:57] <dan> landscape-sysinfo at SSH connection. Is there any way to have landscape-sysinfo without PAM?
[12:08] <TJ-> node1: you need to identify why the system paused. check the kernel log for indications of problems especially in the last few messages. I /think/ these commands are available in busybox/initrd: "dmesg | tail -n 25"
[12:14] <dan> I respond to myself....there is no need to disable PAM. I can run PAM without authentication, by enabling PasswordAuthentication and ChallengeResponseAuthentication to 'no'.Sorry and thanks anyway
[12:19] <gabrielc> Hi. How can I debug Firefox 'internal' issues with dns? I upgraded to 89.0+build2-0ubuntu0.20.04.2 and now it doesn't resolve anything.
[12:19] <gabrielc> It also doesn't help deleting ~./mozilla or running apt purge firefox.
[12:28] <Walex2> gabrielc: here on 20.04 Firefox 89 looks file.
[12:28] <Walex2> gabrielc: here on 20.04 Firefox 89 looks fine.
[12:28] <Walex2> gabrielc: What does "doesn't resolve anything" actually mean?
[12:30] <Walex2> gabrielc: just as a basic check, does this work: http://13.225.84.88/ ("neverssl.com")
[12:31] <DrkTremos> morning
[12:31] <Walex2> gabrielc: also try 'http://localhost/' even if you don't have a running web server on 'localhost'
[12:40] <gabrielc> Walex2: https://1.1.1.1 works. I am going to install apache and access localhost
[12:41] <gabrielc> Walex2: http://localhost with apache running works
[12:49] <gabrielc> Walex2: doing echo "1.1.1.1 uno.uno.uno.uno" >> /etc/hosts, and accessing uno.uno.uno.uno it doesn't work either. It seems something is totally broken.
[12:50] <ravage> Did you try turning it off and on again?
[12:52] <braewoods> gabrielc: is it using DoH?
[12:53] <Walex2> gabrielc: having 'localhost' and 'uno.uno.uno.uno' in '/etc/hosts' should make no difference...
[12:56] <gabrielc> apt purge firefox; rm -rf ~./mozilla; apt install firefox; doesn't help. Closing xfce session doesn't help. A reboot doesn't help. I had TRR (on firefox) in use and dnscrypt-proxy service running for all other applications.
[12:57] <Walex2> gabrielc: your troublshooting actions are typical of MS-Windows users, and about as effective.
[12:59] <gabrielc> the reboot was to shut down the computer while I sleep
[13:00] <Walex2> gabrielc: does 'cat /etc/resolv.conf' look sensible?
[13:01] <Walex2> gabrielc: what happens if you do 'dig @.... www.ubuntu.com' with the adddress in 'resolv.conf'?
[13:02] <gabrielc> Walex2: dig works fine, always
[13:03] <gabrielc> the only line: nameserver 127.0.2.1
[13:03] <Walex2> gabrielc: just to be really sure, what happens if you do: wget -O /tmp/ubuntu.html https://www.ubuntu.com/
[13:04] <gabrielc> 2021-06-03 10:04:07 (211 KB/s) - ‘/tmp/ubuntu.html’ saved [108414/108414]
[13:04] <Walex2> gabrielc: so your DNS and web access outside Firefox seem to be working fine.
[13:04] <Walex2> gabrielc: so in theory after deleting everything and reinstalling Firefox should also work fine.
[13:05] <gabrielc> yes
[13:05] <gabrielc> but no
[13:05] <Walex2> gabrielc: have you got some environment variables like 'http_proxy' or any other than might cause troubkle?
[13:05] <gabrielc> no
[13:07] <Walex2> gabrielc: also please run: ss -lp 'sport = :domain' to see if the result is plausible
[13:09] <Walex2> it should be given the previous checks
[13:09] <Walex2> gabrielc: also to be totally sure run 'firefox -P' and create a new profile to check.
[13:10] <gabrielc> one tcp and one udp to 127.0.2.1
[13:10] <Walex2> and what is attached to '127.0.2.1'? Running it with 'sudo' should tell you.
[13:11] <Walex2> gabrielc: also is "127.0.2.1" what appears in 'resolv.conf'?
[13:12] <gabrielc> 127.0.2.1 is dnscrypt-proxy service
[13:13] <gabrielc> now i put only 8.8.8.8 on resolv.conf
[13:16] <gabrielc> deleting ~. / mozilla, only with 8.8.8.8 in resolv.conf, opening firefox, and running ss -lp 'sport =: domain', in the processes column firefox does not appear
[13:18] <gabrielc> with tcpdump it is also not seen that firefox is making dns queries
[13:19] <Walex2> gabrielc: have you tried to 'firefox -P' and create a new profile to check.
[13:20] <Walex2> gabrielc: or do you know better?
[13:21] <llutz> gabrielc: do you eventually have dns-over-https enabled in firefox?
[13:22] <gabrielc> I delete all profiles when I delete ~/.mozilla
[13:22] <Walex2> allegedly...
[13:24] <gabrielc> network.trr.mode is 0, deleting ~/.mozilla should restore everything to factory settings
[13:24] <Walex2> gabrielc: obviously you know better.
[13:25] <leftyfb> gabrielc: if you'd like further help here, please stick with the troubleshooting steps people are asking you to do and stop constantly doing your own at the same time
[13:25] <leftyfb> gabrielc: I'm willing to help you, but only if you follow instructions and don't do anything else on your own
[13:25] <gabrielc> ok
[13:26] <leftyfb> gabrielc: what version of ubuntu is this?
[13:26] <gabrielc> 20.04.2 LTS
[13:27] <leftyfb> gabrielc: lets define your goals. You are running Xubuntu on it? And you're trying to run firefox which seems to be working perfectly fine working for public websites right?
[13:30] <leftyfb> gabrielc: hello?
[13:30] <gabrielc> is ubuntu with xfce, not xubuntu.
[13:32] <gabrielc> firefox does not connect when it has to use dns. the exception seems to be localhsot
[13:32] <leftyfb> gabrielc: ok, so opening firefox and going to ubuntu.com doesn't work?
[13:32] <gabrielc> right
[13:34] <leftyfb> gabrielc: please run: systemd-resolve --status|grep "DNS Servers" | nc termbin.com 9999
[13:36] <gabrielc> Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
[13:37] <V3n3RiX> reinstall systemd :P
[13:37] <leftyfb> V3n3RiX: stop
[13:37] <leftyfb> gabrielc: you should have been given a URL
[13:39] <gabrielc> did not print url
[13:39] <Walex2> leftyfb: if you scroll back there is a bit of important context that "gabrielc" is not telling you...
[13:40] <Walex2> because he had already written it.
[13:40] <leftyfb> Walex2: like?
[13:40] <leftyfb> gabrielc: please run: cat /etc/resolv.conf  # please paste the results to pastebin.ubuntu.com and paste the link here. Do not paste the results here and do not try to summarize the results
[13:41] <Walex2> leftyfb: 'wget https://www.ubuntu.com/' works and 'firefox https://1.1.1.1/' and 'firefox http://localhost/' all seem to work.
[13:42] <leftyfb> Walex2: they just said ubuntu.com does not work
[13:42] <Walex2> leftyfb: it does not work *in Firefox*.
[13:42] <gabrielc> https://termbin.com/8156
[13:43] <Walex2> leftyfb: the other vital detail is that "gabrielc" used to have DNS-over-HTTP (TRR) enabled in Firefox and was also using a DoH proxy as the local resolver.
[13:43] <leftyfb> gabrielc: why is your resolv.conf such a mess?
[13:43] <V3n3RiX> because systemd
[13:43] <leftyfb> V3n3RiX: please stop
[13:44] <gabrielc> the comments do not apply right?
[13:44] <leftyfb> V3n3RiX: also, there are zero entries in that resolv.conf from systemd
[13:44] <leftyfb> gabrielc: please answer the question. Why is your resolv.conf such a mess? With ubuntu 20.04 you shouldn't be messing with it at all
[13:44] <V3n3RiX> leftyfb: my first advice to reinstall systemd was legit, since that file could have been deleted by accident, and resolved no longer starts ... reinstalling systemd will solve that ... but since you decided to troll me, I think is fair for me to troll you back
[13:44] <gabrielc> I don't consider it a disaster.
[13:45] <leftyfb> gabrielc: ok, good luck. Lets us know when you are ready to work with us when troubleshooting.
[13:46] <leftyfb> gabrielc: you have a mess of a system that's going to take a lot of work not only to decipher but to troubleshoot where you broke it. You coming up with your own ideas and troubleshooting is only making matters worse
[13:47] <leftyfb> V3n3RiX: reinstalling an application, especially one such as systemd almost never solves any problems. If the resolv.conf was originally deleted somehow, then the fix is just to symlink it back to /run/systemd/resolve/stub-resolv.conf
[13:47] <gabrielc> I didn't break anything. ubuntu updated firefox and broke my firefox installation.
[13:49] <V3n3RiX> leftyfb: sure it does ... did you read what he said above? "Unit dbus-org.freedesktop.resolve1.service not found."
[13:49] <V3n3RiX> if that unit file was removed by accident, reinstalling systemd will bring that file back
[13:50] <Walex2> leftyfb: V3n3RiX: but "resolv.conf" and 'systemd-resolve' are not the issue here because he was using TRR and a DoH proxy, and then for the sake of argument he put '8.8.8.8' in 'resolv.conf'
[13:50] <V3n3RiX> true ... but as leftyfb pointed above on systemd systems resolve.conf is a symlink to some /run folder
[13:50] <signofzeta> If you want to mess with DNS resolution on modern Linux, your best bet is to go through the systemd/resolved.conf file.
[13:51] <V3n3RiX> if systemd-resolved itself is broken, as per unit file missing error
[13:51] <Walex2> V3n3RiX: sure, but "gabrielc" wanted to avoid using 'systemd-resolve' at all.
[13:51] <V3n3RiX> puting anything in resolv.conf will achieve nothing
[13:52] <V3n3RiX> that's easy
[13:52] <V3n3RiX> rm /etc/resolv.conf
[13:52] <leftyfb> V3n3RiX: resolv.conf is downstream of systemd-resolved, your last statement is factually false
[13:52] <V3n3RiX> touch /etc/resolv.conf
[13:53] <V3n3RiX> add wathever inside and chattr +i /etc/resolv.conf
[13:54] <leftyfb> Walex2: I always start upstream of the issue whenever troubleshooting. Hence looking into local DNS resolution first. There was a long list of steps I was going to go through, but seeing that mess, it's not worth my time
[13:54] <leftyfb> either way, they have a mess of a system as the result of playing with features and services they don't fully understand nor how to troubleshoot and aren't willing to fully cooperate with troubleshooting
[13:55] <Walex2> leftyfb: that was my impression too, "a little knowledge is a dangerous thing" :-=
[13:55] <Walex2> leftyfb: that was my impression too, "a little knowledge is a dangerous thing" :-)
[13:56] <Walex2> gabrielc: the reason we ask to double check things is because in a system in an unknown state and more in general "it's obvious that X" and "it is verified that X" are not necessarily both true or false :-)
[13:56] <gabrielc> how can I cooperate?
[13:56] <V3n3RiX> leftyfb: there is not such thing as an original /etc/resolv.conf file on systemd ... it is a symlink
[13:57] <V3n3RiX> gabrielc: wanna avoid resolved?
[13:57] <Walex2> gabrielc: right now we know two things: DNS resolution works for non-Firefox programs, and web access works from Firefox when using numeric addresses.
[13:58] <gabrielc> if i wanted to avoid systemd i would use slackware
[13:58] <Walex2> gabrielc: odds are that there is some bit of "hidden" configuration that affects Firefox
[13:58] <leftyfb> V3n3RiX: resolve.conf, if exists, gets used regardless of who created it including systemd-resolved. If it's not pointing to a loopback, then systemd-resolved isn't used and queries go out to whatever nameserver is specified
[13:59] <leftyfb> V3n3RiX: to put in in a more simple way, if resolv.conf doesn't exist, regardless of systemd-resolved being functional or not, DNS resolution will fail.
[13:59] <Walex2> gabrielc: given that we also know that you used DoH/TRR that looks most likely.
[13:59] <V3n3RiX> leftyfb: did I say otherwise? ;)) I only said it is a symlink to resolved on systemd systems
[14:00] <Bardon> Hello, I am trying to use obs-studio. I can't record my screen with the apt version (black screen) and the snap version just crashes with a segfault. I am on 21.04. What can I do?
[14:00] <Walex2> gabrielc: it is likely that having delete $HOME/.mozilla there is no more TRR or other proxy configuration, but one thing is guessing it, another knowing it...
[14:00] <gabrielc> the issue is only with firefox 89, all other software works fine
[14:01] <leftyfb> V3n3RiX: it's not a symlink to resolved, it's a symlink to a resolv.conf compatible file that resolved manages. systemd-resolved can be completely broken, but if that file still exists and doesn't point to the local loopback then DNS works just fine(assuming where it points to works)
[14:01] <Bardon> The snap version says "X Error of failed request:  BadWindow (invalid Window parameter)" before crashing
[14:01] <Walex2> Bardon: if you can't record your screen odds are that some X extension is missing.
[14:01] <V3n3RiX> if resolved is broken, that file won't exist dude :P
[14:01] <Bardon> Walex: I must add that it works the first time obs-studio snap is launched
[14:01] <V3n3RiX> hence my initial reccomandation to reinstall systemd
[14:02] <Bardon> Walex: Then when I close it and restart it, it segfaults
[14:03] <Bardon> And, am I using X? I thought 21.04 used Wayland. Or am I mixing up stuff?
[14:05] <V3n3RiX> Bardon: loginctl show-session 2 -p Type
[14:05] <V3n3RiX> if it says wayland, you're on wayland
[14:06] <Walex2> Bardon: not everything has been ported to Wayland, and the X-Wayland proxy does not support reliably everything.
[14:06] <V3n3RiX> try logging on X and check obs again ... as far as I'm aware obs doesn't work on wayland
[14:06] <V3n3RiX> and xwayland is ... weird
[14:06] <V3n3RiX> or what Walex2 just said :P
[14:07] <Walex2> V3n3RiX: "weird" is a good summary :-)
[14:07] <gabrielc> well. thank you all for the time. I'm going to see what I do knowing that it may be related to systemd.
[14:07] <V3n3RiX> gabrielc: I have a possible solution
[14:08] <V3n3RiX> if you wanna avoid resolved completely
[14:08] <Bardon> V3n3RiX: I get "Failed to get session path: No session '2' known"
[14:08] <V3n3RiX> ok ... then you're not on session 2
[14:09] <V3n3RiX> Bardon: loginctl
[14:09] <Bardon> V3n3RiX: How do I log on X?
[14:09] <gabrielc> V3n3RiX: i listen
[14:09] <Bardon> V3n3RiX: Session 1 says "Type=wayland"
[14:09] <V3n3RiX> then you're on wayland
[14:10] <V3n3RiX> gabrielc: rm /etc/resolv.conf && touch /etc/resolv.conf && edit the file and add nameserver 8.8.8.8 in it && chattr +i /etc/resolv.conf
[14:10] <Bardon> I'm surprised that if things don't work on Wayland, then why is it shipped by default? I don't remember choosing Wayland over X when I installed
[14:10] <Bardon> or updated
[14:11] <V3n3RiX> Bardon: you can logout and you should have an option to choose your session ... I think is Ubuntu on X or something
[14:11] <V3n3RiX> by default Ubuntu on Wayland is shipped
[14:11] <V3n3RiX> shipped is a wrong word, enabled I wanted to say
[14:13] <Bardon> There must be some good arguments that I'm not aware of but it comes as a surprise to me that Wayland is enabled by default if it breaks stuff. OBS used to work before I upgraded
[14:13] <V3n3RiX> gabrielc: chattr +i /etc/resolv.conf will make that file immutable, so nobody, not even root can delete it ... that way systemd-resolved cannot claim it back
[14:14] <V3n3RiX> gabrielc: if you ever want to delete it for some reason just chattr -i /etc/resolv.conf (I wouldn't do that)
[14:14] <gabrielc> V3n3RiX: i know
[14:16] <gabrielc> now I realize that I have systemd-resolved turned off, for something, I don't even remember
[14:18] <braewoods> ugh resolved
[14:18] <gabrielc> starting that service and restoring backup from original /etc/resolv.conf, doesn't work either
[14:20] <V3n3RiX> maybe the service didn't start
[14:20] <V3n3RiX> can you do a systemctl status systemd-resolved to check?
[14:20] <gabrielc> is running
[14:27] <gabrielc> I'm going to try a few things. goodbye. Thank you.
[14:34] <plshalp> Is there a way to install Emacs 27 on Ubuntu 20.04 that provides you with the systemd service like the Emacs 26 package does?
[14:36] <leftyfb> plshalp: sudo apt remove emacs ; sudo snap install emacs
[14:36] <plshalp> leftyfb: I installed Emacs using the snap for 27. https://snapcraft.io/emacs
[14:37] <plshalp> I also tried kelley's ppa. No service in either.
[14:46] <leftyfb> plshalp: I'm not sure if this is the right way, but the snap package does provide the service. sudo systemctl enable /snap/emacs/current/usr/lib/systemd/user/emacs.service ; sudo systemctl start emacs
[14:48] <plshalp> leftyfb: I get Failed to enable unit: snap/emacs/current/usr/lib/systemd/user/emacs.service
[14:48] <leftyfb> plshalp: do you have the snap installed?
[14:48] <leftyfb> oh
[14:48] <leftyfb> you left out the leading /
[14:48] <plshalp> I have the snap installed, and the file exists.
[14:48] <plshalp> Oh derp
[14:50] <plshalp> I think the service might be working. But it's taking forever since it's downloading a bunch of packages. I will try to connect to it once it's running.
[14:50] <almostdvs> does a tor service hostname ever change if the network changes?
[14:51] <almostdvs> or does someone know a channel that might have knowledge of tor ?
[14:52] <leftyfb> almostdvs: /join #tor
[14:52] <leftyfb> almostdvs: read the topic when you are there
[14:52] <almostdvs> hmm.. alis didnt list it.  thanks leftyfb
[14:54] <plshalp> leftyfb: It seems to work. Thank you!
[14:55] <plshalp> leftyfb: Quick question though (I'm new to snap), where do I find the icon? Small thing, but I have a desktop file that I use to run emacsclient -c, and it's icon is now missing.
[14:57] <leftyfb> plshalp: I removed it. See if there's already a .desktop file: find /snap/signal-desktop/ -name *.desktop
[14:57] <Walex2> plshalp: "icon" is a bit of a misnomer, what you want to look for is the relevant '.desktop' file.
[14:57] <plshalp> I run my own desktop file, I just want the icon to work for it.
[14:58] <plshalp> I can see what the snap provided .desktop file uses for its icon.
[14:58] <leftyfb> plshalp: see if it comes with a desktop file and look at it's contents to see if it specifies an icon you can use
[14:59] <Walex2> plshalp: there are lots and lots of icons in dozens of icon packages, and you can specify any you want in the '.desktop' file.
[15:00]  * Walex2 like Faenza or Faenza-Radiance icons
[15:00] <plshalp> leftyfb: Thanks, that was the idea I had. I just copied the icon line from snap's provided emacs.service.
[15:00] <plshalp> Now to see if all that work of updating to emacs27 was worth it.
[15:01] <plshalp> Woot! I now have continuous scrolling in pdf-tools. \o/
[15:02]  * Walex2 thinks that kids today are too easily enthused :-)
[15:06] <VIA> hihi
[15:06] <VIA> can anyone recommend me a  small tool that display temp sensors?
[15:06] <VIA> prefer non agressive polling every few secs or so would be fine
[15:07] <VIA> most stuff i tried dont do  what i expected or are just to comprehensive it also makes no  sense for me
[15:07] <VIA> or just pull the data and dump it once ..
[15:07] <VIA> lm_senśors and glances and others i cant recall now
[15:10] <pizza> VIA: personally I use the Freon gnome extension, worked for me with minimal to no setup
[15:33] <Bardon> Hello, if I run a program in a terminal, then I CTRL+Z, then `bg`, then CTRL+D, is it possible to come back to that program and see its output to stdout and pause it and resume it?
[15:37] <leftyfb> Bardon: you should use something like screen, tmux or byobu for this
[15:37] <Bardon> Oh, is CTRL+Z the same as `kill -s SIGSTOP pid`? Then resuming would be `kill -s SIGCONT pig`?
[15:38] <Bardon> So the only thing I'm missing is stdout now
[15:38] <Bardon> leftybf: Yes, I closed the terminal by mistake :s
[15:44] <TJ-> Bardon: did you try using reptyr
[15:45] <Bardon> TJ-: I've never heard of it, I'll git it a try
[15:45] <TJ-> !info reptyr \ Bardon
[15:45] <TJ-> oops
[15:45] <TJ-> !info reptyr | Bardon
[15:45] <VIA> not sure if i can install  it on xfce pizza
[15:55] <gabrielc> hello everyone. I'm still having problems with firefox 89. still doesn't resolve dns. but this time the systemd-resolved service is running.
[15:57] <f_ayx>    Hello channel, trying to install an application using an install script I get the following output https://paste.ubuntu.com/p/fG8N9N7Hkp/ when I do 'which gcc' OR 'which g++' it points to /usr/bin/gcc and /usr/bin/g++, i don't understand why the script is picking up the compiler in above home path as I have modified my $PATH so that /usr/bin comes first... Which I think is the reason it fails to find the libraries for
[15:57] <f_ayx> the KF5 modules
[16:10] <Bardon> TJ-: It looks like that's what I'm looking for. Thanks :)
[16:26] <TJ-> f_ayx: maybe the installer changes PATH? As a shell script it should be easy to check that
[16:28] <f_ayx> TJ: how do I check/resolve that please, i've searched hi and lo on the web but can't find a solution
[16:30] <TJ-> f_ayx: "grep PATH install.sh"
[16:32] <f_ayx> TJ: the command does not return anything, I've open install.sh and search for PATH as well and nothing
[16:42] <TJ-> f_ayx: what shell is it using? check the shebang (first line)
[16:47] <et09> odd thing - gcp instances are accumulating /usr/src/linux-headers-xxx  files
[16:47] <et09> 3-4gb worth
[16:47] <et09> apt-get -f autoremove does the trick, but uh, why was that happening :/
[16:49] <TJ-> et09: is this out of date (auto-generated config) /etc/apt/apt.conf.d/01autoremove-kernels
[16:51] <et09> TJ-: i do see that file
[16:51] <et09> do i delete it?
[16:54] <TJ-> et09: no, you read it, especially its header, to see if it looks current (or check its timestamp)
[16:54] <TJ-> et09: that is a list of not-to-be-autoremoved packages, generated by another script when kernel packages are installed
[16:56] <TJ-> et09: as you'll see that file is created by /etc/kernel/postinst.d/apt-auto-removal - if for some reason this latter script is misbehaving, that could be the cause.
[16:57] <TJ-> et09: other reasons could be that you've somehow disabled those autoremovals
[16:57] <et09> i should 18.04 -> 20.04 these too
[16:58] <et09> let's see...uname is 5.30-1032...values in the file range from 1028 to 1043
[16:58] <et09> uname might update when i reboot, 1 sec...
[16:59] <et09> yeah 1043 now
[17:20] <TJ-> et09: if you want to test the script and check what has been generated you can do that manually; "sudo /etc/kernel/postinst.d/apt-auto-removal" or for bonus points, to see the commands it is executing as well, do "sudo sh -x /etc/kernel/postinst.d/apt-auto-removal | tee /tmp/autoremove.log"
[17:20] <TJ-> et09: then you can review the /tmp/autoremove.log and the generated /etc/apt/apt.conf.d/01autoremove-kernels
[17:21] <TJ-> et09: if that looks up to date and you later find that older headers are being retained, there may be some additional apt config somewhere affecting this
[17:32] <et09> thanks TJ- looking into it
[17:49] <daekdroom> Hello. Does ubuntu separate / and /home by default when formatting a hard drive to install?
[17:52] <signofzeta> Not by default, daekdroom, but you can do that from the installer.
[17:53] <gordonjcp> wow
[17:53] <gordonjcp> I remember /home on a separate partition
[17:53] <gordonjcp> used to be quite the thing, back when we all wore an onion on our belt, as was the fashion in those days
[17:54] <daekdroom> signofzeta, I'm helping someone install Ubuntu remotely, so I was afraid of telling them how to partition manually, lol
[17:54] <daekdroom> Thanks for the answer
[18:02] <IHasFinger> hi guys, i did some changes on crontab -e however when i run systemctl status cron on the CGroup it is still showing the old cron jobs
[18:02] <IHasFinger> also the new changes i added via crontab -e is not running
[18:03] <Diagon> A year or so ago I started having trouble in 16.04 with my old logitech trackball. now i'm on 20.04 &the trouble persists.  Difficulty with selection, sometimes not responding to clicks.  How might I approach this?
[18:11] <TJ-> Diagon: have you proved it isn't a physical issue on the device?
[18:12] <Diagon> TJ - Yes, I tried a second one.  Same problem.
[18:12] <gabrielc> Hi. I am the only one with dns problems with firefox 89? the problem also happens with the snap.
[18:13] <TJ-> Diagon: any clues in the kernel logs?
[18:13] <Diagon> TJ - lemme check...
[18:14] <TJ-> Diagon: how is the device connected? USB? If so, and the device is USB2, is it by chance plugged into a USB3 port/hub ?
[18:14] <TJ-> Diagon: it is likely actually USB 1.1 since HIDs don't need to be fast
[18:15] <Diagon> TJ - yes, USB.  I tried various ports over the year.  Let me try again.
[18:17] <TJ-> Diagon: we know that USB2/1.1 in USB3 ports can be problematic for some USB chipsets
[18:18] <Diagon> TJ - thanks.  I'm seeing that I actually have had it through a port replicator on my daskeyboard.  I'm trying it on USB2 now - and looking at the kernel logs which Im' not familiar with.  Will take a few minutes.
[18:19] <TJ-> Diagon: if you can test it directly on the PC
[18:19] <Diagon> TJ - yes, that's what I'm doing now.
[18:19] <TJ-> Diagon: everything you've said gives me a gut feeling it is hardware related
[18:19] <Diagon> TJ - alright, thanks.
[18:20] <cbreak> gordonjcp: I have my own home dir on a different zfs dataset :)
[18:20] <cbreak> it's very nice for snapshot / backup purposes
[18:21] <gordonjcp> cbreak: yup
[18:21] <cbreak> I think that's also what you get by default with ubuntu
[18:21] <cbreak> although not encrypted
[18:28] <signofzeta> yeah, I wish I could convert my desktop from ext4.  still, most of my /home/signofzeta/* folders are saved on a separate ZFS array, so it's no big deal.
[19:07] <Guest79> Hello, anybody else have firefox break last night/today? 89.x from package opens with a pure white window, 89.x from mozilla.com opens with a pure white window, 91.x daily build opens ok but tabs will go white if moved to another monitor. Any thought?
[19:10] <TJ-> Guest79: 2 or 3 people have reported an issue with 89.x today
[19:11] <Guest79> TJ=: Thanks, I'll pop over to launchpad and search for bugs
[19:12] <TJ-> Guest79: I'm about to install it :)
[19:12] <Guest79> gl
[19:14] <danlinux> i installed it today, no problems so far
[19:15] <TJ-> could the issue be around which desktop environment is in use?
[19:23] <leftyfb> FF 89.0+build2-0ubuntu0.18.04.2 seems fine to me
[19:25] <oerheks> rename the ~/.mozilla folder and try again?
[19:26] <rjwiii> Hello ... I am STILL getting a "Software Updater" window with nothing in it ... I click on "Install Now" and the window blips and comes back the same. I updated on CLI and it is still happening ... Ubuntu 20.04 with all the latest updates ...
[19:27] <TJ-> Firefox 89.0+build2-0ubuntu0.20.04.2 OK here (on Xubuntu [xfce4])
[19:31] <remline> Firefox 89.0+build2-0ubuntu0.21.04.1 OK here (i3 window manager)
[19:32] <ioria> here too, and sparking
[19:35] <et09> 89 on arch+wayland and mostly working except for google meet and stupid wayland clipboard bug
[19:38] <gabrielc> Hi again. Anyone want to help me with firefox? does not resolve dns.
[19:38] <Arsen> hi! does ubuntu make /boot unreadable for normal users or is this host specific? it's breaking libguestfs
[19:39] <ioria> gabrielc, only FF ?
[19:40] <gabrielc> ioria: yes
[19:40] <ioria> gabrielc, so 'ping google.com' korks ?
[19:40] <ioria> *works
[19:40] <gabrielc> ioria: yes
[19:40] <matsaman> Arsen: my guess would be that if it's on a separate partition, the default state is to be not mounted
[19:40] <ioria> gabrielc, have you tried to refresh it ?
[19:40] <matsaman> Arsen: you can control partition mounting via /etc/fstab
[19:40] <gabrielc> ioria: all works, only firefox 89 have the issue
[19:40] <Arsen> matsaman: it's definitely mounted, the file is there, it's just 600
[19:40] <sarnold> Arsen: I've got a vague memory of a bug discussing changing /boot/efi/ to prevent non-root reading it, or something similar, but I'm not finding it now..
[19:41] <ioria> gabrielc, have you tried to refresh it ?
[19:41] <gabrielc> ioria: rm ~/.mozilla, apt purge, apt install and the issue persist
[19:41] <matsaman> Arsen: can control perms from fstab also
[19:41] <ioria> nope
[19:41] <Arsen> `-rw------- 1 root root 11760384 Apr 12 18:56 /boot/vmlinuz-5.4.0-72-generic`
[19:41] <Arsen> oh, this could be fat?
[19:41] <Arsen> nope, it's ext4
[19:41] <matsaman> 'mount' will say what FS it is
[19:41] <ioria> gabrielc, Help -> More troubleshooting .. ->  Refresh
[19:42] <matsaman> if /boot/ isn't the ESP, then there's really not an amazing reason for it to even be a separate partition
[19:42] <Arsen> it isn't; but does apt install those kernels as read-only?
[19:43] <matsaman> Arsen: ...why don't we start with the error libguestfs spits out
[19:44] <TJ-> Arsen:  sounds like umask
[19:44] <Arsen> matsaman: sure thing
[19:44] <Arsen> `cp: cannot open '/boot/vmlinuz-5.4.0-73-generic' for reading: Permission denied'
[19:44] <Arsen> TJ-: umask on an apt-controlled file?
[19:45] <matsaman> Arsen: what does ls -l say about that file
[19:45] <sarnold> Arsen: that's entirely expected, yes, seepermissions: -rw------- 1 root root 11764480 Apr 14 16:37 /boot/vmlinuz-5.4.0-73-generic
[19:46] <Arsen> `-rw------- 1 root root 11764480 Apr 14 18:37 /boot/vmlinuz-5.4.0-73-generic'
[19:46] <Arsen> sarnold: yeah, thought so, how can I relax those, though
[19:46] <sarnold> Arsen: this is an exploit mitigation to force malware authors to inspect kernels themselves and hardcode offsets to symbols, rather than reading them out of the binaries on disk
[19:46] <Arsen> I understand what it is for
[19:46] <Arsen> in this instance, I need to use the kernel, though
[19:48] <matsaman> just chmod r for it then
[19:48] <Arsen> what about updates, though?
[19:48] <matsaman> I doubt updates touch old kernel images in /boot/
[19:48] <matsaman> if they did I doubt you'd want them to
[19:48] <Arsen> no, but guestfs relies on uname to know which kernel to pick
[19:49] <matsaman> is there no symlink to the latest kernel in /boot/ ?
[19:49] <Arsen> that is subject to the same file perm issue
[19:49] <matsaman> I'm not as familiar with Ubuntu's kernel build system, but in a normal world where you build a kernel, if you symlink /boot/vmlinuz to the latest image, the process will update that symlink for you
[19:50] <matsaman> anyway, another easy fix is to make a script and allow a person to use sudo to run that script
[19:54] <Arsen> matsaman: not possible in this case, it's messing with a CI system
[19:55] <Arsen> but at any rate, I just made an rc.local script make the current kernel readable, good enough
[19:55] <TJ-> Arsen: usual way is to add an executable script to /etc/kernel/postinst.d/
[19:56] <Arsen> oh, that works for me too
[19:56] <Arsen> TJ-: ty for the info :)
[20:08] <oerheks> 5.8.0-55.62 update bionic, maybe a fix for firefox too ?
[20:08] <oerheks> brb
[20:16] <rjwiii> Hello ... I am STILL getting a "Software Updater" window with nothing in it ... I click on "Install Now" and the window blips and comes back the same. I updated on CLI and it is still happening ... Ubuntu 20.04 with all the latest updates ...
[20:19] <Thete> probably wants some 21.04 action
[20:30] <chilversc> What service starts rpc.mountd? I want to test disabling it as it shouldn't be required for nfs 4
[20:38] <chilversc> found it, nfs-mountd.service, and seems like it is required even for NFS 4
[21:12] <vbgunz> Firefox on Manjaro KDE keeps asking to set it as the default browser. What's the easiest way to stop this? it's already the default
[21:13] <tomreyn> vbgunz: do you realize what the name of this channel is?
[21:13] <vbgunz> oh dan
[21:13] <vbgunz> oh damn*
[21:13] <tomreyn> :-)
[21:13] <vbgunz> I love Ubuntu too <3
[21:13] <vbgunz> sorry
[21:14] <tomreyn> no problem, have a good time.
[22:29] <Diagon> TJ- if you're still around, I think you were right.  Trackball seems to be working now.  Thanks.