[01:35] <Diagon> kernel: BUG: unable to handle page fault for address.
[01:35] <Diagon> Full logs: http://sprunge.us/tToAun
[01:35] <Diagon> Any thoughts?
[01:36] <TortillaSandwich> man, I installed DeepinDD just to check it out and now even though I've removed it I get nothing but a tonne of "system has ecountered an error" messages asking me to report them
[01:48] <sarnold> Diagon: nothing comes to mind immediately; I think, file a bug report against the kernel: ubuntu-bug linux
[01:49] <Diagon> sarnold - thanks.  could this be hardware?  any way to investigate that?
[01:49] <sarnold> Diagon: it's possible, but feels a bit unlikely to me for reasons I have trouble articulating..
[01:50] <sarnold> Diagon: memtest86 or memtest86+ might be able to help suggest if you've got memory failing.. maybe there's more notes elsewhere in dmesg about hardware problems
[01:51] <Diagon> I checked dmesg, but nothing ...
[01:52] <Diagon> Alright, will file bug, thanks.
[02:07] <Diagon> Reported here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949247
[02:08] <sarnold> woot, thanks
[02:12] <tomreyn> Diagon: maybe run a memtest, i found two reports for native_queued_spin_lock_slowpath where hardware problems seems to be the cause.
[02:13] <euouae> Hello I’m trying to install Ubuntu on an old macOS’s
[02:14] <euouae> after the boot, I get a “check file systems” which I cancel with control C and then I’m stuck with the logo
[02:14] <VMGuy23> let it check filesystems
[02:14] <euouae> Is there some background process going on? I can’t tell if I’m supposed to wait for something
[02:14] <euouae> I’m going to erase the whole disk though, why check?
[02:15] <VMGuy23> its checking the USB
[02:15] <euouae> Why does it say file not found then?
[02:16] <euouae> for a bunch of files it was checking, it would just say that they’re not found
[02:16] <tomreyn> because the installer was not properly written to the installer media
[02:16] <euouae> Hmm is there something special I need to do for macOS? I used dad
[02:16] <tomreyn> try using balena etcher, it verifies proper writes
[02:16] <euouae> dd
[02:17] <tomreyn> dd also works, but it wont verify the data written
[02:17] <euouae> Ok thank you, I must’ve been unlucky I guess
[02:17] <euouae> it seems that no file is found, everything was “not fiund”
[02:17] <euouae> that it checked
[02:18] <tomreyn> https://unix.stackexchange.com/questions/75483/how-to-check-if-the-iso-was-written-to-my-usb-stick-without-errors
[02:18] <tomreyn> that's your CLI alternative for verifying correct writes
[02:18] <euouae> Nice thank you
[02:18] <tomreyn> also check the iso you downloaded has a correct checksum
[02:19] <tomreyn> (do this first)
[02:19] <euouae> I’ll try again tomorrow, my friend over video is tied
[02:19] <euouae> tired
[02:19] <euouae> right, thank you
[02:22] <SoundWave> When creating/using column and bar chart,, how can I select wich 'data series' is a column and wich 'data series' is a line ?
[02:23] <tomreyn> you might need to name the application you're referring to there
[02:26] <SoundWave> oups!!! tomreyn, tought a was in libreoffice room
[02:26] <tomreyn> that's the other cubicle down the alley
[02:27] <SoundWave> lol
[02:36] <Diagon> tomreyn - thanks, will do....
[02:38] <tomreyn> Diagon: if this is a uefi booting system or recent hardware, you may want to use memtest86.com rather than memtest86 (which is in ubuntu and available from grub when bios booting)
[02:39] <tomreyn> * rather than memtest86+
[02:39] <Diagon> :thumbs-up:
[02:53] <[itchyjunk]> Hi, when trying to use apt, i get an error. is it safe to run the command being recommended to fix the issue?
[02:53] <[itchyjunk]> E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
[02:54] <sarnold> that's probably the right command to use, yeah
[02:54] <sarnold> depending upon what happened before, you might *also* need to do something else, but running that command now should give you a good idea of what needs to be done
[02:55] <[itchyjunk]> ty
[03:37] <bobdobbs> Hi all. I've recently started using KDE/plasma. And it looks and feels great! However, I have encountered one issue: some applications have unreadable dialogues. This is a dialogue presented by GIMP: https://imgur.com/4xn8swo
[03:38] <bobdobbs> There is actually text in the fields 'Template', 'Width' and 'Height'. But in these dialogues the text is black on a very dark brown. So the text is just about entirely invisible
[03:51] <lotuspsychje> bobdobbs: could it be a theme flaw perhaps?
[03:51] <bobdobbs> lotuspsychje: I guess? But I'm not even sure what that means.
[03:51] <lotuspsychje> bobdobbs: try testing another theme, see if you can reproduce that
[03:52] <bobdobbs> ok
[03:53] <bobdobbs> lotuspsychje: k, I've switched from 'Breeze Dark' to 'Kubuntu'. The issue persists.
[03:54] <bobdobbs> Problem persists if I switch to 'Breeze'
[03:56] <lotuspsychje> bobdobbs: tnx for testing, i dont seem to find bugs under template right away on gimp; https://bugs.launchpad.net/ubuntu/+source/gimp/+bugs?orderby=importance&start=0
[03:56] <bobdobbs> lotuspsychje: I'm installing a bunch of themes now from the Global Themes UI. I didn't know that there were so many!
[03:57] <lotuspsychje> bobdobbs: so are you claiming switching themes, you cant read the text because too dark?
[03:57] <bobdobbs> lotuspsychje: I should add: I've had this issue over the years - pretty much every time I've switched from Gnome to KDE. I've just never tried to deal with it before, because I've never settled into KDE
[03:58] <bobdobbs> lotuspsychje: that's rught, yes
[03:59] <lotuspsychje> bobdobbs: maybe you could talk to the kubuntu crew first, but if you cant solve it, you could file a new !bug
[04:01] <bobdobbs> lotuspsychje: At this point I'm assuming it's not a bug. I figure it's more likely to be an issue that can be solved by tweaking a setting. I think that basicaly I'm running an app built for Gnome within a KDE environment. So maybe the GIMP UI's are picking up some UI settings from Gnome, some from KDE..
[04:01] <bobdobbs> I dunno. That's a wild guess really
[04:02] <bobdobbs> But... where can I talk to the kubuntu folks? Do they have an irc channel?
[04:02] <lotuspsychje> bobdobbs: if something isnt working by default, i would assume its a bug
[04:02] <lotuspsychje> bobdobbs: #kubuntu and #kde
[04:02] <bobdobbs> thanks
[05:48] <xdfreak22> anyone else use linux and unix?
[06:11] <artu59> ciao a tutti
[06:17] <katnis> what are the most used commands on ubuntu?
[06:17] <yukiup> ls
[06:17] <yukiup> cd
[06:18] <yukiup> nano!
[06:18] <katnis> i tried nano once and it was kinda fresh for me
[06:18] <katnis> ctrol + buttons to control stuff
[06:18] <katnis> ls, cd...
[06:18] <katnis> thank you
[06:18] <katnis> vi?
[06:19] <katnis> yukiup: do you know about vi
[06:19] <yukiup> yes
[06:19] <yukiup> but i like nano
[06:19] <yukiup> there is also grep
[06:19] <katnis> yeah i  see people prefer nano
[06:19] <katnis> nano and vi
[06:19] <katnis> oh
[06:19] <katnis> grep! i have seen it before :D
[06:19] <yukiup> less
[06:19] <yukiup> rm
[06:20] <yukiup> man
[06:22] <yukiup> sudo, apt
[06:24] <katnis> manual?
[06:24] <katnis> oh yes
[06:24] <katnis> sudo su
[06:24] <yukiup> :p your not supposed to use su!
[06:25] <yukiup> chmod
[06:26] <Nitrigaur> TJ-, If you have any time today, I' d love to discuss my ubuntu 20.04 setup using your article: https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019. I have started my VM linked to my physical SSD and I'm in Busybox, since grub is unable to find /dev/vgubuntu-lvroot
[06:45] <artu59> list
[06:46] <artu59> !list
[06:51]  * dodocrypto hi all back
[07:03] <mr_lou> Hello. I've used dd to write Hiren's BootCD onto USB... but how to make it bootable?
[07:04] <mr_lou> Startup Disk Creator won't accept the ISO.
[07:13] <unixbeard> I have a weird problem with Ubuntu 20.04, probably more an issue with my onboard Intel gigabit NIC.  I have a ROG Strix I think, on this system, and periodically, randomly, the (wired) network just stops.
[07:13] <unixbeard> Local network, everything, then it starts working again after a bit.
[07:15] <unixbeard> Any suggestion on where to start?  I can't see any immediate solution other than rebuilding kernel and seeing if I can get specific with an intel nic driver, since I'm using the latest update for 20.04.
[07:23] <u0_a870> l0de
[07:24] <u0_a870> |shark|
[07:26] <alkisg> unixbeard: do you have any other ubuntu devices on the same network? Does the problem happen on them? If so, it would be an issue with the dhcp renewals
[07:26] <alkisg> If not, check the output of the `dmesg` command for kernel warnings/errors
[07:27] <alkisg> And, what's the output of `ip a` when the issue happens....
[07:38] <pycurious> I want to shutdown my VMs at reboot or shutdown and switch them back on when the machine boots. Where can I insert these commands? Or do i have to write a systemd service for it?
[07:40] <alkisg> pycurious: you can type `sudo crontab -e` and add an "@reboot command" line there
[07:40] <alkisg> Or of course you can add a systemd unit
[07:52] <unixbeard> alkisg: I do, and the problem does not happen with them.  I have the same hardware (sans video card) on another computer running windows 10, and it doesn't seem to have this problem.
[07:52] <TJ-> Nitrigaur: I'm just waking up; need a coffee
[07:52] <Nitrigaur> TJ-, Enjoy :-)
[07:52] <unixbeard> alkisg: All the static systems have long leases, and I checked with pfsense (had similar thoughts...) but maybe that is somehow an issue.
[07:53] <alkisg> unixbeard: ok, start with `dmesg` and `ip a` when the issue happens
[07:54] <unixbeard> alkisg: frustratingly I don't get any issues from dmesg.
[07:54] <alkisg> unixbeard: and `ip a` shows that the ip/lease are still active?
[07:54] <unixbeard> alkisg: I double checked my mac address in pfsense and the system has a static lease.
[07:54] <unixbeard> Well, I will try that soon when it randomly drops.
[07:55] <alkisg> A static reservation doesn't always mean an infinite lease lifetime
[07:55] <alkisg> It might mean "just give it the same ip when it asks again"
[07:55] <alkisg> OK, let's see then
[07:55] <unixbeard> I have not been enjoying new hardware; my monitor doesn't detect activity on this workstation, but I think it was in sleep mode?  I installed caffeine to just disable it even though I thought I disabled all sleep related crud on here.
[07:56] <unixbeard> Okay, yeah, I am not sure.  It shows no start/end time for lease on static assigned stuff, but that's pfsense/bsd and I'm not sure how the dhcpd works on there.
[07:56] <unixbeard> The non-static lease stuff does have start/end times listed for lease.
[07:56] <alkisg> You can check the monitor status over ssh, without waking it up locally
[07:56] <unixbeard> On the local network, ssh/ping dies inbound/out on that system.
[07:57] <unixbeard> So I tried to ssh to it from my nearby windows system, and ping it, and it is effectively dead after it goes to sleep.  I can ssh to another ubuntu system with mostly similar hardware upstairs.
[07:57] <alkisg> When monitor goes off?
[07:57] <alkisg> Or when the intel issue happens?
[07:57] <alkisg> Ah if the system goes to sleep, its a completely different thing than if the monitor goes to sleep
[07:57] <alkisg> Suspend/resume might be buggy due to a lot of kernel drivers or system hooks
[07:57] <unixbeard> Well the monitor is another PITA, it's a curved gaming monitor and I have it plugged into a power switch because it has a hardware problem (samsung g7?)
[07:59] <unixbeard> So I just power cycle it when I need a display, otherwise it will not 'wake up' and detect either system if it's been idle long enough.  There's actually a hardware issue there ... I declined having it repaired, anyway.
[07:59] <TJ-> Nitrigaur: OK, I'm (almost all) here although brain may be slow! Your summary about being it booting into the busybox shell would mean GRUB stage was fine but the initialramfs has a problem
[08:04] <TJ-> unixbeard: what precise Intel device is it? what does this report? "lspci -nnk -d ::200"
[08:05] <TJ-> unixbeard: sounds like an issue we see mostly with I219-V I think is the model, and its EEE power saving modes
[08:08] <Nitrigaur> TJ-, Well, in my busybox (VM) I can only see /sda devices, no nvme* at all
[08:09] <Nitrigaur> TJ-, My girlfriend just PM'd me that she's coming down and she expects a breakfast. So, I have to tend to that first.
[08:10] <TJ-> Nitrigaur: unless you're doing pass-through / VFIO that is what I'd expect the hypervisor to do. Which hypervisor are you using?
[08:11] <TJ-> Nitrigaur: this is why we use UUIDs and file-system labels rather than absolute device names - for portability. Device names can change between boots depending on when the kernel sees the device and intialises the device relative to other similar devices
[08:18] <Nitrigaur> TJ-, I'm using KVM
[08:18] <Nitrigaur> TJ-, update: Bread is in the oven, so breakfast is sorted ;-)
[08:20] <Nitrigaur> TJ-, I do see a /cryptroot, so that's encouraging, isn't ?
[08:23] <Nitrigaur> TJ-, inside that cryptroot is a crypttab with only 1 byte in it. That's a bit strange
[08:25] <TJ-> Nitrigaur: that's the problem then!
[08:26] <Nitrigaur> TJ-, Should I chroot into the vgubuntu-lvroot from my terminal to see what's going on, or to test some more?
[08:26] <TJ-> Nitrigaur: find the crypt device so you can manually unlock it
[08:26] <TJ-> (from inside the busybox shell)
[08:26] <TJ-> Nitrigaur: try "blkid" in busybox
[08:28] <Nitrigaur> TJ-, I see it and it does have the same UUID as mentioned as in grub, so that went well. Strange that it is not mounting properly from grub
[08:30] <Nitrigaur> TJ-, I have successfully opened both crypted devices and I can see them in my /dev/mapper
[08:30] <TJ-> Nitrigaur: at this stage it has /nothing/ to do with GRUB; GRUB is long gone. Now it is a problem created by the crytpsetup hooks when update-initramfs was called
[08:30] <TJ-> Nitrigaur: good, so now try "vgchange -ay"
[08:30] <TJ-> Nitrigaur: that should if not already, detect the VG and activate the LVs
[08:31] <Nitrigaur> TJ-, Yes, it did :-)
[08:31] <TJ-> now 'exit' and the init should resume and boot
[08:32] <Nitrigaur> That's right, I'm in now. So how do I go about fixing my initramfs permanently?
[08:33] <Nitrigaur> TJ-, ^
[08:33] <TJ-> Nitrigaur: first check the real /etc/crypttab is valid. Best to pastebin it for me so I can be sure there's no weird syntax that'll trip up the cryptsetup hook scripts
[08:35] <Nitrigaur> TJ-, I will in a bit, but I'm going to join my Girl Friend first for some Breakfast. Can't keep her waiting ;-) . Thank you so much again. I'll return after breakfast.
[08:36] <Nitrigaur> TJ-, I' ll pastebin my crypttab first though
[08:39] <Nitrigaur> TJ-, Here you go and thanks in advance for your analysis: https://paste.ubuntu.com/p/5m7jwSCcRT/
[08:43] <TJ-> Nitrigaur: that looks fine, so when you're back we can test what update-initramfs is doing, with "sudo update-initramfs -v -u -k $(uname -r) |& tee /tmp/initrd.log" and then "T=$(mktemp -d); pushd $T; sudo unmkinitramfs /boot/initrd.img-$(uname -r) . ; cat ./main/cryptroot/crypttab "
[09:08] <unixbeard> def a hardware/kernel problem
[09:09] <TJ-> unixbeard: did you see my earlier comments?
[09:09] <unixbeard> TJ-: no, I am running in a screen now so I won't lose text again.
[09:09] <TJ-> unixbeard: sounds like an issue we see mostly with I219-V I think is the model, and its EEE power saving modes
[09:09] <unixbeard> I went looking at my old dmesg and /var/crash to find (among other things) a potential issue with my video card.
[09:09] <TJ-> unixbeard: what precise Intel device is it? what does this report? "lspci -nnk -d ::200"
[09:09] <unixbeard> Oh!  I also saw that, eeepc stuff (hah)
[09:10] <unixbeard> One sec.
[09:10] <unixbeard> TJ-: This caught my eye: kernel: eeepc-wmi eeepc-wmi: Detected ASUSWMI, use DCTS ?
[09:11] <unixbeard> TJ-: using igc, Ethernet controller [0200]: Intel Corporation Device [8086:15f3] (rev 02)
[09:12] <Nitrigaur> TJ-, btw, on this machine I'm working on 21.10 instead, though that *should* not make much of a difference
[09:12] <unixbeard> ...but like I said, I also *just* got a crash in gnome-shell related to nvidia I guess, so I'm using v. 470 over 460.  Hopefully that takes care of that particular issue.
[09:12] <TJ-> unixbeard: check the eee state with ethtool
[09:13] <TJ-> unixbeard: also, I'd suspect the mobo's firmware ACPI since that affects power-saving configuration before OS starts
[09:13] <TJ-> unixbeard: can you share the complete kernel log? " journalctl -k | nc termbin.com 9999 "
[09:14] <unixbeard> TJ-: Maybe, sec.
[09:14] <unixbeard> TJ-: I don't see anything about EEE state using ethtool on my device.
[09:15] <unixbeard> EEE status: disabled <- sorry
[09:15] <TJ-> for others who are interested: "ethtool --show-eee <interface>"
[09:16] <Nitrigaur> TJ-, I have executed both the mkinitramfs and the extraction of the initramfs image
[09:16] <pikapika> Whats the recommended way to copy over a dead project to a new distro?
[09:16] <pikapika> ie an app that was in your existing install but likewly won't be in the new ubuntu since project appears dead
[09:17] <TJ-> unixbeard: so now we need to know *exactly* what the symptoms are when it fails. does the link goto state DOWN, does it just lose its DHCP lease, does "tcpdump -vvni <interface>" still show two-way traffic
[09:17] <Nitrigaur> pikapika, does that package have source code? In that case, you could just compile it yourself
[09:17] <pikapika> I'll have to see if it does
[09:17] <TJ-> Nitrigaur: does the ./main/cryptroot/crypttab have the correct entry?
[09:19] <unixbeard> TJ-: Hmm, can I message the termbin link to you?
[09:20] <Nitrigaur> TJ-, I' ll check to see if the UUID's match, just a sec...
[09:20] <TJ-> unixbeard: it's OK to share here, it's only the kernel log
[09:20] <pikapika> I should save up the source before it vanishes
[09:20] <pikapika> or even worse if it becomes some paid close source thing
[09:21] <TJ-> pikapika: you can always fetch the most recent source from the archive and do a dpkg-buildpackage locally
[09:21] <pikapika> Oh right, yeah good point that the Ubuntu repos themselves would have a source code
[09:21] <Nitrigaur> TJ-, Yes, it does :-)
[09:21] <unixbeard> TJ-: https://termbin.com/sz7t
[09:21] <pikapika> so I could save up the stuff from my current ubuntu
[09:21] <pikapika> and copy it over in case the new ubuntu has removed it
[09:22] <TJ-> Nitrigaur: OK, so now do another boot attempt with what we know is a known-good configuration. Ensure you're booting the exact same kernel version so it used this initrd-img we've just checked.
[09:22] <Nitrigaur> TJ-, aye. Rebooting now...
[09:24] <TJ-> unixbeard: 1st thing I'd do is update the mobo firmware to the lateset version. Currently it is on 0805 7/1/2020 but latest is 2423 26/8/21
[09:25] <TJ-> unixbeard: and there are a few "Improve system performance" generic isses listed in the various version changelogs  https://rog.asus.com/uk/motherboards/rog-strix/rog-strix-b550-e-gaming-model/helpdesk_bios
[09:25] <Nitrigaur> TJ-, works straight away :-)
[09:25] <TJ-> Nitrigaur: so that somehow got corrupted
[09:26] <Nitrigaur> TJ-, I'll try booting from the latest kernel now, to see if that works as well. What I noticed is that I got two shim-related lines, that I did not see during the previous boot.
[09:29] <TJ-> unixbeard: also, there may be a microcode update in those firmware updates that may fix the "__common_interrupt: 1.55 No irq handler for vector" happening on each core
[09:30] <TJ-> unixbeard: and related to the GPU: 2pci 0000:07:00.0: 32.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x16 link at 0000:00:03.1 (capable of 126.016 Gb/s with 8.0 GT/s PCIe x16 link)"
[09:31] <Nitrigaur> TJ-, I have made a screenshot. Do you want to see that (btw.: The new kernel boots up fine as well ;-) ) What I' m really curious about is what went wrong. I would like to preserve this setup along with an ansible-script so I can recreate my machine from scratch should I need a new machine or when I decide to scrap everything )except my data of course and start with a fresh machine.
[09:32] <unixbeard> TJ-: it just did it again, the network indicator in the upper right of my dekstop had a question mark over it, ip a said the link state as up though.
[09:32] <TJ-> Nitrigaur: no idea how the crypttab got corruped that way and it'd be very hard to track down unless you can reproduce it
[09:33] <TJ-> unixbeard: arghh, and I sent you some messages!
[09:33] <TJ-> unixbeard: what was the last you saw from me?
[09:33] <unixbeard> TJ-: I'll update the firmware, yeah.
[09:33] <unixbeard> TJ-: I'm running in a screen so no problems.
[09:33] <TJ-> unixbeard: oh yeah, you did say :)
[09:34] <unixbeard> Also it didn't go down long enough to end the session.
[09:34] <Nitrigaur> TJ-, I have already reproduced it on a 20.04 based VM on my work PC. This machine had exactly the same flaw as my last setup. i.e.: It dropped to Busybox.
[09:34] <TJ-> unixbeard: when it dies next time have a "sudo tcpdump -vvni enp6s0" ready to go and see if there's two-way traffic still (broadcasts and multicast traffic most likely)
[09:35] <TJ-> Nitrigaur: and you're doing this via ansible playbook and scripts?
[09:35] <unixbeard> TJ-: queued up, thank you!
[09:35] <Nitrigaur> TJ-, Not yet, but I plane to ;-)
[09:35] <Nitrigaur> TJ-, plane -> plan
[09:35] <unixbeard> I am thinking at this point it's problem a problem that will wind up being resolved in firmware.
[09:35] <unixbeard> it's probably a problem even
[09:35] <TJ-> Nitrigaur: so this has happened twice but with you building the installs manually?
[09:36] <Nitrigaur> TJ-, Yes
[09:36] <TJ-> Nitrigaur: I have to point the finger at you then :D
[09:36] <Nitrigaur> TJ-, Fair enough :-D
[09:37] <TJ-> Nitrigaur: the only way I can see that happening is if update-initramfs is run before /etc/crypttab has been fully configured
[09:37] <Nitrigaur> TJ-, I *did* follow your instructions though.
[09:37] <TJ-> Nitrigaur: lots of people have done that and it has worked so there is likely something in your workflow that causes this
[09:37] <Nitrigaur> TJ-, Let me check in my post-setup.bash script...
[09:38] <Nitrigaur> TJ-, update-initramfs is all the way at the bottom, so it is not sequence related.
[09:39] <BCB> just upgraded to Ubuntu 20.04.3 LTS and now OpenDKIM will not start up Here is the output from sudo systemctl start opendkim and journalctl -xe https://dpaste.com/DN92JDJE3.txt
[09:40] <TJ-> Nitrigaur: let me state some facts. 1. as initrd.img has a /cryptroot/crypttab that tells us cryptsetup-initramfs hooks were triggered when "update-initramfs" ran. That means they saw an entry in /etc/crypttab that is a container for the root-fs. The hook script then should read /etc/crypttab line that matches, then write a modified form of that line to the /tmp/.mkinitramfs/cryptroot/crypttab file
[09:40] <TJ-> in the initrd.img it is assembling.
[09:40] <BCB> sorry if I missed a previous response
[09:40] <TJ-> Nitrigaur: from that you can see that either the 'write' process failed or, when the system boots, somehow that file is corrupted within the initrd-img, which seems more unlikely
[09:41] <BCB> I'm using OpenDKIM Filter v2.11.0
[09:41] <BCB> I can't seem to find an OpenDKIM channel
[09:41] <TJ-> Nitrigaur: in your script you need to add a step to use unmkinitramfs and inspect the /cryptroot/crypttab to ensure it was written correctly, like we did manually earlier
[09:42] <Nitrigaur> TJ-, I'll postbin my exact setup-script. Note that I'm running this line by line, by copy-pasting from it into the terminal, or I cannot enter my LUKS keys.
[09:43] <TJ-> Nitrigaur: ok :)
[09:43] <TJ-> BCB: check "journalctl -u opendkim.service -n 300" for more clues
[09:43] <BCB> TJ- will do.  thank you
[09:44] <Nitrigaur> TJ-, Here you go: https://paste.ubuntu.com/p/B2CQvxWGn9/
[09:44] <TJ-> BCB: locate the most recent "Starting ..." and hopefully you'll get a clue
[09:45] <Nitrigaur> TJ-, It's probably just a typo somewhere. It mostly is ;-)
[09:45] <BCB> TJ- Nitrigaur "opendkim: milter socket must be specified"
[09:48] <Nitrigaur> TJ-, I cannot thank you enough for walking me through this. Very much appreciated :-D IT was my first taste at actually fixing things from Busybox and I have been running Linux for about 24 years now.
[09:48] <TJ-> Nitrigaur: nothing obvious there, so as I said check the actual content of the created initrd.img-$version using unmkinitramfs
[09:52] <Nitrigaur> TJ-, I will. I'll restart my laptop proper this time to see if it works outside my VM as well. Thanks again and have a lovely Weekend :-)
[10:00] <BCB> TJ- mail.log is reporting: key data is not secure: /etc/opendkim is writeable and owned by uid 106 which is not the executing uid
[10:00] <BCB> TJ- private key is set to: -rw------- 1 opendkim opendkim  887 Dec 28  2016 default.private
[10:00] <BCB> ???
[10:01] <BCB> TJ- Oct 30 05:52:40 server opendkim[33759]: vital: key data is not secure: /etc/opendkim is writeable and owned by uid 106 which is not the executing uid (0)
[10:02] <TJ-> BCB: the messages says "/etc/opendkim" not "/etc/opendkim/default.private"
[10:02] <TJ-> BCB: so secure the directory correctly
[10:02] <TJ-> BCB: also it sounds the process is starting as UID 0 rather than its expected ID?
[10:03] <TJ-> BCB: is 106 opendkim ?
[10:03] <unixbeard> TJ-: Got a broken pipe ... argh.
[10:03] <BCB> TJ- how do I tell
[10:03] <TJ-> BCB: "getent passwd opendkim"
[10:04] <TJ-> unixbeard: call a plumber! :P
[10:04] <BCB> TJ- opendkim:x:106:115::/var/run/opendkim:/bin/false
[10:04] <BCB> do I chmod 600 the opendkim folder
[10:04] <TJ-> BCB: so that is the 106 mentioned.
[10:05] <TJ-> BCB: I think you need to figure out why opendkim service is reporting the UID issue
[10:06] <TJ-> BCB: generally what happens with system services is, they're initially started as root but then once they're done essential things that require UID 0, they switch to a less privileged user, which in this case will be opendkim (106) to run as
[10:07] <TJ-> BCB: you said this is an upgrade to 20.04.3 ... what was the previous release version? this looks like a letover from the previous version
[10:08] <BCB> TJ- 16.04.7 LTS
[10:08] <BCB> I upgraded twice
[10:08] <BCB> this week
[10:14] <TJ-> BCB: that is likely the cause then. Also, the package is untouched by Ubuntu, it is imported directly from Debian, so maybe there are some Debian bug reports about this
[10:20] <BCB> TJ- I'm reviewing an installation guide for OpenDKIM on Ubuntu 20
[10:23] <dineshhannurkar> ubuntu error
[10:24] <dineshhannurkar> ubuntu error
[10:51] <Bardon> Hello, I'm on 21.10, I'd like to use Eclipse to run some java code. I did sudo snap install eclipse --classic, then I believe I did sudp apt install default-jre (but it was a long time ago so I'm note sure). At least I have "default-jre/impish,now 2:1.11-72build1 amd64" installed
[10:51] <Bardon> But when I try to run the code, it says "ava.lang.UnsupportedClassVersionError: Main has been compiled by a more recent version of the Java Runtime (class file version 59.0), this version of the Java Runtime only recognizes class file versions up to 55.0"
[10:51] <Bardon> So, can I just class file version 59.0 on Ubuntu?
[10:54] <Bardon> I have "OpenJDK Runtime Environment (build 11.0.12+7-Ubuntu-0ubuntu3)" and "openjdk version "11.0.12" 2021-07-20"
[10:57] <BCB> TJ- it was a permission issue. Khepra in ##email suggested chmod and chown cmds. All set now.  Thank you.
[10:57] <Bardon> I tried installing openjdk-18-jre but it doesn't seem to fix it
[11:00] <TJ-> BCB: it looked that way, glad it is solved
[11:08] <TwGianT> Is it possible to get the icons below my favorites on the dock (bar on left side of the screen) from re-arranging themselves? I find it very distracting.
[12:30] <_ganapathi_> In some cases building debian file might required dsc file. is there any way to generate dsc automatically ?. like generating tar file and adding checksum into dsc file .
[12:41] <TJ-> _ganapathi_: "dpkg-source --build ..."
[12:45] <_ganapathi_> Ok. Thanks.
[12:49] <BluesKaj> Hi folks
[12:53] <_ganapathi_> dsc have checksum. its mandatory ?. or optional.
[12:59] <gabriel> ?
[12:59] <tomreyn> !
[13:05] <_ganapathi_> debian build have dsc file. some builder required dsc file. usually dsc file have checksum of tar.xz file . so am asking here as checksum line on dsc file is mandatory for build or not
[13:14] <tomreyn> _ganapathi_: there'a at least one channel related to debian packaging on oftc, this may be a better place to get help with it.
[13:22] <Andy_Flatline> There's a weird problem with my Ubuntu 20.04. When I first turn on the laptop, it is extremely laggy for about 10 minutes. I mean, so bad that the mouse pointer will barely work and the keyboard will barely type letters. All of the windows take much longer to open, etc. So virtually unusable. When I leave the laptop alone for 10-15 minutes. This strange lagginess goes away. Has anyone encountered this problem before?
[13:26] <tomreyn> Andy_Flatline: is this a fresh 20.04 installation, or did you upgrade? which cpu and how much RAM?
[13:27] <tomreyn> to answer the last two questions and enable us to look for hardware / firmware related problems, you could run this to share the first 1000 lines of your system log:   journalctl -b | nc termbin.com 9999    post the url it reports here
[13:29] <Andy_Flatline> No, it's been on this laptop for about 6 weeks. The CPU is an Intel Core i5-5200U. I have 8GB of ram.
[13:30] <tomreyn> that should be fine, so it has to be something else (and the logs might help)
[13:32] <tomreyn> the symptoms you're discussing would match "tracker", a file indexer (not user tracking), but this is not usually noticable unless you're short of ram or with a slow cpu
[13:36] <Andy_Flatline> The command you gave me for the log isn't doing anything
[13:40] <FreeBDSM> Hi. Is it okay that stopping and disabling snapd breaks apparmor systemd unit?
[13:40] <gamer> yes
[13:40] <gamer> but take snapshots before doing that
[13:40] <FreeBDSM> too late
[13:41] <gamer> thats okay
[13:41] <gamer> you should always take backup
[13:42] <FreeBDSM> no point, I don't know how to restore
[13:42] <FreeBDSM> app armor sounds like something important for security or something
[13:42] <gamer> kind of
[13:42] <gamer> but you can restore it
[13:42] <FreeBDSM> shouldn't I just delete the conflicting /etc/apparmor.d/usr.lib.snapd.snap-confine.real?
[13:43] <gamer> nope
[13:43] <FreeBDSM> why? I disabled snapd
[13:43] <FreeBDSM> and that file has snapd in its name
[13:43] <FreeBDSM> so it's a metastasis of that snapd cancer
[13:43] <gamer> you should take that file and rename it.
[13:43] <FreeBDSM> okay
[13:43] <tomreyn> Andy_Flatline: try this:  dmesg | nc termbin.com 9999
[13:44] <tomreyn> Andy_Flatline: it wont work if the system is offline, though?
[13:47] <FreeBDSM> how does apparmor know about /var/lib/snapd/apparmor/?
[13:47] <FreeBDSM> found new metastases
[13:49] <tomreyn> snapd uses apparmor a lot for confinement, it's logical to me that there are many relations between the two.
[13:49] <FreeBDSM> I disabled snapd
[13:49] <FreeBDSM> apparmor now fails to start
[13:49] <FreeBDSM> it's not logincal that if snapd uses apparmor that apparmor might break when snapd is disabled
[13:50] <tomreyn> probably not, but i don't know what the error message is or what ubuntu version you're referring to. and i don't really want to support snap, so...
[13:51] <FreeBDSM> no one wants to support snap
[13:51] <tomreyn> not true, some people do so regularly here
[13:51] <FreeBDSM> `apt list --installed | grep snap` says I have `gir1.2-snapd`, `libsnapd-glib1` and `libsnappy1v5`
[13:53] <FreeBDSM> well, moved that cancer away from those locations and apparmor now starts fine
[13:53] <FreeBDSM> dunno what it does though
[13:54] <tomreyn> that might be part of the problem
[13:59] <FreeBDSM> just found out that linux mint is basically ubuntu-snap+cinnamon and if cinnamon is something like xfce (or can be replaced with it) - then I finally found what to migrate to (currently stuck with ubuntu 18.04 and it's support gets slowly dropped by the world)
[14:44] <euouae> Hello I'm trying to install kubuntu on an old mac, from usb. I see the Kubuntu splash logo, I cancel the filesystem check, and then it gets "stuck" in the splash screen. Is something supposed to happen?
[14:45] <ioria> euouae, most of the times, is a graphic issue; you might use 'nomodeset'  ; what's your video card ?
[14:46] <euouae> I'm not sure
[14:46] <euouae> How to set nomodeset?
[14:46] <ioria> !nomodeset
[14:49] <euouae> It has `quiet splash ---`
[14:49] <euouae> What's that --- doing there? Write nomodeset after it?
[14:50] <ioria> yes
[14:51] <ioria> no, i mean before --- , just after splash
[14:51] <euouae> got it
[14:59] <euouae> ioria It still seems to be 'stuck' in the splash
[14:59] <euouae> Is there a way to look at what happens in the background?
[14:59] <ioria> euouae, esc iirc
[15:00] <ioria> euouae, how did you do the usb ?
[15:00] <euouae> I just flashed it with balena etcher
[15:00] <euouae> I didn't do the disk util preparation step with the partition. Maybe I should try that
[15:01] <ioria> euouae, how much ram do you have ?
[15:01] <euouae> I think it's 2GB
[15:01] <ioria> euouae, for kubuntu it's not enough
[15:01] <euouae> Do you think it's a ram issue then?
[15:02] <ioria> but it should install anywys
[15:02] <ioria> nope
[15:02] <ioria> euouae, 2G is good forlubuntu nowadays
[15:03] <euouae> esc doesn't do anything
[15:04] <ioria> euouae, alt+f1   (or fx)
[15:04] <euouae> alt+f1 doesn't do it
[15:05] <euouae> neither ctrl/cmd/option +f1
[15:05] <ioria> euouae, i suggest you make the usb again (maybe try with lubuntu)
[15:06] <euouae> okay, thank you
[15:06] <ioria> ok
[15:08] <euouae> Does lubuntu have ftp releases?
[15:08] <euouae> I can't download https downloads because the certs on macOS are invalid and the download interrupts for some reason
[15:09] <ioria> euouae, torrents ?
[15:11] <tomreyn> euouae: there are also plain http mirrors
[15:13] <tomreyn> http://cdimage.ubuntu.com/lubuntu/releases/
[15:13] <euouae> thanks!
[15:14] <tomreyn> you're welcome
[15:28] <euouae> Ok currently looking at the lubuntu splash screen and waiting
[15:30] <TJ-> euouae: tap Esc to see what splash is hiding :)
[15:30] <euouae> good idea, it works this time :)
[15:31] <euouae> something about correcting GPT PMBR size mismatch by "write". 16+0 records in, 16+0 records out, and that's where the cursor is blinking
[15:34] <euouae> yeah nothing else is happening
[15:37] <euouae> This is roughly what I'm looking at, https://paste.debian.net/1217384/ I wasn't able to make out everything from the picture I took
[15:38] <euouae> I think I need to do the step where I set up the partitions right before I flash the medium
[15:41] <ioria> euouae, try rufus with the default settings : https://rufus.ie/en/
[15:57] <euouae> I've tried with disk utility, I still get the same messages except one more that talks of the 4th partition having an ext4 filesystem
[16:00] <EriC^^> euouae: what are you trying to flash? which iso?
[16:00] <euouae> the amd64 one
[16:00] <euouae> I've tried with kubuntu and lubuntu
[16:00] <euouae> The 21.04 version
[16:00] <ioria> euouae, if you are on a unix-like system, you can also use 'dd'
[16:03] <euouae> I guess there's something I'm forgetting to do or something is going wrong but I don't know what exactly
[16:07] <euouae> I'll use rufus. Disk Utility didn't work out... I'm wondering if the hardware is 32bit? I doubt it but not sure
[16:08] <euouae> oh wait, things are happening all of the sudden!
[16:08] <ravage> Sometimes the installer really hangs for ages
[16:10] <ravage> But you should really install 21
[16:10] <ravage> 10
[16:10] <ravage> Support for non LTS releases is not long and you will need to update soon
[16:10] <ravage> So better start with a current release
[16:11] <euouae> wait, isn't 21.04 the LTS?
[16:12] <ravage> no
[16:12] <euouae> oh my god
[16:12] <ravage> current LTS is 20.04
[16:12] <euouae> ugh so frustrating
[16:12] <ravage> next will be 22.04
[16:12] <euouae> Is it possible to upgrade/downgrade to LTS from a fresh 21.04 install?
[16:13] <ravage> no
[16:13] <cbreak> euouae: yes, but only a newer LTS
[16:13] <ravage> well
[16:13] <ravage> no downgrades
[16:13] <cbreak> the next LTS will be 22.04
[16:13] <ravage> you can always update
[16:14] <euouae> I think I'll upgrade to 22.04, can't repeat these steps again it's too much :P we've burned 5 OSes through videochat
[16:14] <ravage> so you could update to 21.10 now and next year to 22.04
[16:14] <cbreak> ubuntu isn't that hard to install, is it?
[16:15] <euouae> cbreak it's hard to explain all the steps to someone over videochat, and the installer takes about 30 minutes to get going
[16:15] <cbreak> :/
[16:15] <cbreak> euouae: once you're on 22.04, be sure to switch the auto-update track to LTS, or you might accidentally go to 22.10
[16:15] <euouae> No idea why, I even cancel the filesystem check :P old hardware + hard disk I guess
[16:16] <tomreyn> euouae: maybe the hdd is just broken? have yuo tried to examine this, yet?
[16:16] <ravage> i had the hanging installer a few times too. never found out why. waiting helps
[16:16] <cbreak> euouae: one of my coworkers likes to install the server version without anything, and then only installing minimal desktop stuff as needed
[16:16] <euouae> tomreyn possibly, it's old hardware donated by an IT dept
[16:17] <cbreak> but, I don't think I'd install anything on a hard disk these days. SSDs are just too good
[16:17] <tomreyn> euouae: lack of ram can also cause weird installation issues. but most of the time it's due to broken (removable) flash storage
[16:17] <cbreak> also not too expensive nowadays. But my scale might be misaligned with the general public on this :D
[16:17] <euouae> the cool thing about this mac is that it has a huge screen, maybe 21'' or more
[16:17] <tomreyn> oh it's a mac
[16:18] <cbreak> yes. My scale definitely is misaligned. I have a "small" 24 inch screen
[16:18] <euouae> cbreak hehe yeah you're a techie... my wife calls it the "textbox"
[16:18] <tomreyn> wait, 2G RAM only?
[16:18] <euouae> teh textbox is the terminal
[16:19] <tomreyn> if that is so, then don't waste your time
[16:19] <euouae> What do you mean?
[16:20] <tomreyn> if you just have 2GB RAM then you won't have a good experience with any of the official flavours
[16:20] <cbreak> ubuntu server might work fine.
[16:20] <cbreak> maybe with some minimal WM
[16:20] <euouae> the /lightweight/ lubuntu will be bad? How come?
[16:20] <tomreyn> and desktop installers will most likely just do what you've reported
[16:21] <tomreyn> it's no lightweight, it used to be
[16:21] <euouae> lol
[16:21] <rfm> I find my 2GB Acer One does OK with xubuntu
[16:21] <tomreyn> compared to gnome, still a bit maybe
[16:21] <cbreak> euouae: on an actual hard disk, swap will be very slow
[16:21] <cbreak> and with 2GB, you might actually need swap
[16:21] <cbreak> you should check
[16:22] <tomreyn> rfm: did you install it using the desktop installer? which one?
[16:22] <cbreak> (with something like htop, btop, bpytop or even swapon I suppose)
[16:23] <rfm> tomreyn, it would have been the normal xubuntu install at time time (probably 18.04; it's been upgraded since then)
[16:23] <tomreyn> rfm: and which web browser are you using?
[16:24] <tomreyn> is that "acer aspire one"?
[16:25] <rfm> I use chrome,  I don't open a zillion tabs, mind.   Yes, asipre one, with the Atom processor.  It came with 1GB ram, I upgraded it to 2GB which is the max for the processor.
[16:25] <tomreyn> and that's a 64-bit one?
[16:26] <tomreyn> euouae: i guess you could try rfm's setup then.
[16:27] <euouae> xubuntu or lubuntu should both work I suppose. I'm giving it a try for now with the graphic installer
[16:27] <rfm> Yes, 64 bit.   The reason I keep this old thing going is it is the last laptop left in the house with a ethernet connector, which is useful when checking wiring...
[16:27] <tomreyn> rfm: hehe, okay, so it's not a daily driver, i see.
[16:27] <ravage> rfm: a USB ethernet dongle is like 10$. just saying :D
[16:29] <rfm> ravage, yeah but it's inconvenient to run around the house with the extra dingus hanging out
[16:29] <ravage> true. always a bad idea to run around the house with a dingus hanging out.
[16:29] <tomreyn> ...
[16:33] <euouae> FAILED to start snap daemon and that's it
[16:33] <cbreak> doesn't sound too bad
[16:34] <cbreak> all that snap stuff sucks ram anyway due to all that duplication going on
[16:34] <euouae> it won't proceed though
[16:34] <tomreyn> what is "it"?
[16:35] <tomreyn> lubuntu 21.04 amd64 installation?
[16:35] <euouae> I'm not sure what process it is, but yeah that one tomreyn
[16:36] <tomreyn> do you know which mac model this is?
[16:36] <euouae> no wait! we _got_ a desktop!
[16:36] <ravage> euouae: i thing the general solution to your problems with this old hardware is patience :)
[16:36] <ravage> *think
[16:37] <tomreyn> i think the ubuntu installer would just fail with 2 GB RAM
[16:37] <euouae> ravage I wish there was an indication that /something/ is happening :( It's hard to know whether something has crashed or not. I guess things don't crash
[16:37] <tomreyn> no, they get killed by OOM killer
[16:37] <ravage> xubuntu claims to run smoothly with 2GB. but i havent tried it for a long time
[16:38] <ravage> or maybe they just did not update their website since 2010
[16:39] <tomreyn> https://xubuntu.org/requirements/ says 512 MB RAM, I doubt this would work.
[16:42] <alkisg> The light flavors can boot 18.04 32bit with 512 MB RAM. While 64bit needs about 150% of the RAM that the 32bit version needs
[16:42] <alkisg> So my standard advice to schools here is "If your PC has <=2GB RAM, stick with 18.04"
[16:42] <euouae> schools with linux? nice
[16:42] <tomreyn> you mean ubuntu 18.04 then, not one of the other flavours?
[16:44] <FreeBDSM> has ubuntu already decided to stop focusing on snap technology?
[16:44] <alkisg> No, gnome is too resource hungry for older PCs, we don't use it at all as usually schools are 5 years behind the rest of the world, hardware-wise
[16:44] <ravage> !discuss | FreeBDSM
[16:44] <alkisg> But mate, kde, xubuntu, lubuntu are all fine
[16:44] <tomreyn> alkisg: but the other flavours are EOL, right
[16:45] <ravage> maybe thats a good place for this RAM discussion too now
[16:45] <tomreyn> i can't actually seem to spot an i686 18.04 download either
[16:46] <euouae> alkisg are you talking about Greece? (I'm Greek)
[16:46] <alkisg> tomreyn: eol => yes, but between "not working" and "working eol", there's no choice really
[16:46] <tomreyn> alkisg: okay, i see
[16:47] <FreeBDSM> alkisg: does it have to be ubuntu?
[16:47] <alkisg> tomreyn:  http://cdimage.ubuntu.com/ubuntu-mate/releases/18.04/release/ubuntu-mate-18.04.5-desktop-i386.iso
[16:47] <FreeBDSM> ubuntu is not targeted for low-resource PCs
[16:47] <alkisg> euouae: yes
[16:47] <alkisg> FreeBDSM: the resource hungry application is the web. NOT the browsers. The web itself, with all the fancy javascript
[16:47] <euouae> alkisg How come you're installing linux in schools? Is that part of your job or how does that happen? It surprises me
[16:48] <tomreyn> alkisg: thanks, i did spot the xubuntu i386 iso there. but, yes, EOL, i wouldn actually look for some other distro then.
[16:48] <FreeBDSM> alkisg: that's a school? just ban web and browsers, lol.
[16:48] <alkisg> euouae: I'm an IT teacher, that has been appointed at a support office for schools for the past 10 years. See a map of schools there; and in the main site it has a why/how: https://ts.sch.gr/wiki/Linux/LTSP/Προχωρημένα/Χάρτης
[16:49] <FreeBDSM> send dzadziki plx
[16:49] <alkisg> Haha
[16:50] <euouae> alkisg interesting. Shame that obsolete software is being installed though
[16:50] <euouae> i.e. unsupported & insecure
[16:51] <FreeBDSM> there's no general solution for this problem
[16:51] <alkisg> Newer computer labs get 20.04 mate
[16:51] <FreeBDSM> constant updating == constant alpha-testing
[16:51] <euouae> You could go with debian instead of ubuntu and not have to worry so much about this
[16:51] <alkisg> Older ones get the same experience with 18.04 mate, yet with some security considerations, and that's acceptable to many schools
[16:52] <FreeBDSM> stuff is always broken in one way or the other (security vulns or broken functionality / ux / habits)
[16:52] <alkisg> I've installed debian in some of the schools as an experiment, but it'll need a lot of local polishing, it's not as desktop-ready as ubuntu
[16:53] <FreeBDSM> one man can't maintain (with good quality) a complex system such as an OS targeted for very wide set of users (I bet you have more than just a few PCs)
[16:54] <alkisg> With 1000+ schools, we have more than 10000 PCs, yeah; but with our own educational app repository, we manage fine
[16:54] <FreeBDSM> in the long run, IMO, it's easier and better to just stick to the 'upstream'/'defaults' as much, as possible
[16:57] <euouae> alkisg cool!
[16:57] <euouae> Kids should learn python! :D
[16:57] <onelegend> yeah
[16:57] <onelegend> python has very powerful libraries
[16:58] <onelegend> and while the whitespacing requirements might be annoying for some, it's a great way to force new programmers into writing clean code
[17:05] <euouae> How can I connect the wireless keyboard for the installation step?
[17:08] <alkisg> Yeah python is taught in many of the high school grades here
[17:12] <euouae> alkisg during _my_ schooling I recall many bad experiences
[17:12] <euouae> So I'm glad to hear about ubuntu on schools, that's great progress
[17:14] <euouae> (e.g. we had a book calling CDs "new technology")
[17:15] <alkisg> euouae: linux has been in some greek schools since 2000, but noone was using it. The good experience started in 2007+; this is also when it started becoming popular
[17:15] <euouae> That's around the time I graduated hehe
[17:15] <alkisg> Yeah books get updated every ...15 years, they're bound to be old at some point. But anyway I think we're completely offtopic now
[17:16] <pycurious> alkisg: thanks!
[17:16] <alkisg> 👍️
[17:16] <pycurious> Any ideas on what this is and how to debug this from dmesg -> [   68.163351] Out of memory: Killed process 671 (freshclam) total-vm:501900kB, anon-rss:358012kB, file-rss:0kB, shmem-rss:0kB, UID:114 pgtables:824kB oom_score_adj:0
[17:17] <cbreak> pycurious: looks like your system went OOP because it's linux, and keeps overpromising and underdelivering, and then just goes around killing off processes to free up space again
[17:17] <alkisg> It means that your OS detected an out of memory (RAM) condition, and it selected to kill freshclam to reclaim memory
[17:23] <pycurious> I guess I'll remove freshclam
[17:23] <FreeBDSM> do people nowadays use rsh? or did ssh replace rsh completely?
[17:23] <pycurious> Freeaqingme: only ssh for me
[17:24] <onelegend> https://github.com/hakavlad/nohang
[17:24] <cbreak> pycurious: the OOM killer's victims are not neccessarily to blame
[17:26] <onelegend> FreeBDSM: nah, it's all SSH these days man
[17:27] <tomreyn> euouae: i just installed xubuntu 21.10 amd64 on a VM with 1024 MB RAM (and 20 MB VRAM on top) with installer defaults, so that's possible.
[17:29] <FreeBDSM> does anyone use pssh/pdsh?
[17:30] <euouae> tomreyn thank you! lubuntu graphic installer has almost crashed right now : (
[17:30] <onelegend> FreeBSDM: funny thing is, telnet supports kerberos encryption and authentication
[17:30] <euouae> I think there may be an issue with the wireless apple keyboard as well. I'll have to figure that out. We're postponing the installation until next weekend
[17:33] <FreeBDSM> is there web indes of ubuntu repos?
[17:33] <FreeBDSM> index*
[17:33] <FreeBDSM> I'd like to see if packages like pdsh/pssh are still available in more recent ubuntus
[17:34] <onelegend> archive.ubuntu.org
[17:34] <onelegend> archive.ubuntu.com
[17:34] <onelegend> sorry wrong link
[17:34] <onelegend> don't go to the first one lol
[17:34] <FreeBDSM> http://archive.ubuntu.com/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/
[17:35] <FreeBDSM> damn, I hate ubuntu naming
[17:36] <FreeBDSM> onelegend: how to use that stuff?
[17:36] <FreeBDSM> http://archive.ubuntu.com/ubuntu/dists/bionic/
[17:37] <euouae> Actually I have a 3.06 GHz Intel Core 2 Duo, 4GB ram
[17:37] <euouae> Okay, that sounds quite decent. I don't know why the installer was so painfully slow
[17:37] <ravage> FreeBDSM: https://packages.ubuntu.com/bionic/pdsh
[17:40] <FreeBDSM> ravage: thanks, I hoped I could see contents of installed files, but turns out that just metadata was enough
[17:40] <FreeBDSM> so pssh/pdsh are kept alive
[17:41] <FreeBDSM> pdsh, however, depends on rsh-client and rsh is a dead tech
[17:42] <FreeBDSM> pdsh package links to project's homepage at https://computing.llnl.gov/linux/pdsh.html which returns 404
[17:42] <TJ-> FreeBDSM: see https://packages.ubuntu.com
[17:42] <ravage> the universe repo is the place for packages to slowly die. so it seems appropiate
[17:43] <TJ-> https://packages.ubuntu.com/impish/pdsh
[17:43] <TJ-> Towards the end of the page there are links to lists of files for each architecture
[17:44] <FreeBDSM> TJ-: that's metadata
[17:44] <FreeBDSM> (file names, without files themselves)
[17:45] <TJ-> FreeBDSM: well yes, if you want that, go to the source
[17:45] <FreeBDSM> yeah, that's what I meant
[17:45] <Sven_vB> hi! on focal I ran "ubuntu-drivers autoinstall" in hopes it would make my video capture card work. it installed some nvidia drivers. after reboot, my initrd output is written in huge letters (80x25 text mode probably), and X fails to start with "(EE) Fatal server error:(EE) no screens found(EE)". is there an easy way to recover?
[17:45] <FreeBDSM> you see, the package contents seem to differ in size, but the lists of files are the same, but then I noticed package's version got also bumped
[17:47] <Sven_vB> otherwise, I'd reinstall, but my script for that includes "ubuntu-drivers autoinstall" usually. do I need to disable that entirely for this machine, or can I exclude the breaking driver specifically?
[17:48] <FreeBDSM> https://www.google.com/search?q=pdsh+site%3Acomputing.llnl.gov returns 0 resoolts, I think it's time to just kill pdsh package in favor of pssh, they seem to do the same thing and pssh at least has a git repo
[17:50] <cbreak> Sven_vB: and if you start X manually?
[17:50] <Sven_vB> cbreak, no, lightdm manages it for me
[17:50] <cbreak> maybe you can fix the config before (if it's a config problem)
[17:50] <cbreak> yeah. but you're not forced to use it
[17:51] <FreeBDSM> read x's log
[17:51] <cbreak> you can switch to an other TTY or so with ctrl-alt-F3 or something like that
[17:52] <ravage> Sven_vB: if you did not you the nvidia driver before and installing it caused your problem try https://p.haxxors.com/m5v8pa9f.txt
[17:52] <ravage> i assume you use gnome desktop
[17:53] <Sven_vB> FreeBDSM, good hint. it had a message which log file I should read for details. will do that.
[17:53] <ravage> the purge command sometimes removes the desktop package. so the install command is just to make sure it is still there
[17:53] <FreeBDSM> Sven_vB: lsof it
[17:54] <Sven_vB> cbreak, yes, I have working local TTY shells, working SSH and working nullmodem shell
[17:55] <Sven_vB> ravage, thanks, will read
[17:55] <cbreak> I sometimes had problems with conflicts between the ubuntu nvidia and the nvidia nvidia drivers
[17:55] <TJ-> FreeBDSM: a package that doesn't have "ubuntu" in its version is directly imported from Debian, so you'll find the source there. Best way to then drill down is via Debian Package Tracker to find bugs, source-code, etc.,.e.g  https://tracker.debian.org/pkg/pdsh
[17:55] <cbreak> but manually removing all traces of ubuntu's and installing nvidia's helped fix that...
[17:55] <TJ-> FreeBDSM: "links" on the right side will have a "browse the source code"
[17:56] <FreeBDSM> TJ-: thanks!
[17:58] <Sven_vB> now that I think of it, I remember I configured something to avoid installing proprietary nvidia drivers. I wonder how ubuntu-drivers could seem to succeed installing them, then. I guess I should somehow configure it to install all drivers _except_ proprietary nVidia drivers.
[17:59] <FreeBDSM> TJ-: https://software.llnl.gov/repo/#/chaos/pdsh followed some links and found new homepage for pdsh
[17:59] <FreeBDSM> if you can - you might want to update the url at packages.ubuntu.com
[17:59] <TJ-> FreeBDSM: it's not done there
[18:00] <Sven_vB> ravage, I'd like to not install ubuntu-desktop because it has dependencies that I dislike. what's that step meant to really do?
[18:00] <TJ-> FreeBDSM: it comes from the package itself (debian/control) but as you'll see on Debian Tracker the automatic tools have already reported that problem
[18:00] <ravage> Sven_vB: then check what the purge command removed and manually reinstall what you need
[18:01] <Sven_vB> ravage, I see, ok.
[18:01] <FreeBDSM> TJ-: so if a ticket stays unclosed in debian (which is ubuntu's upstream in this case) - ubuntu will not fix it locally?
[18:01] <TJ-> FreeBDSM: "actions needs" > " Problems while searching for a new upstream version " > "uscan had problems while searching for a new upstream version:"
[18:01] <TJ-> FreeBDSM: unless the package is in Ubuntu's main component, /or/ for package in universe some Ubuntu dev wants to maintain it.
[18:02] <FreeBDSM> got it
[18:02] <TJ-> FreeBDSM: we try to make all common changes upstream in Debian so everyone benefits
[18:03] <TJ-> FreeBDSM: the Debian tooling will have emailed the listed Debian maintainers(s)
[18:03] <FreeBDSM> well, debian guys are not even aware that the package has newer releases
[18:04] <TJ-> FreeBDSM: because the upstream link has broken, but they will be aware of that breakage. Once they find time to fix the debian/watch file with the correct URL it'll all straighten out
[18:05] <FreeBDSM> they are aware, they don't care
[18:06] <FreeBDSM> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940539 created 2 years ago
[18:06] <TJ-> FreeBDSM: it looks like at least one of the maintainers hasn't been active for a couple of years
[18:06] <FreeBDSM> he ded, probably
[18:08] <FreeBDSM> https://github.com/bpellin here he is, alive and even partially active
[18:09] <FreeBDSM> he just gave up on debian, I guess
[18:10] <TJ-> FreeBDSM: this is where community contributions come in; you could create a patch to fix that since you're interested in that package
[18:11] <FreeBDSM> I did my best, I pointed at some stuff on IRC, surely that's more than enough
[18:12] <Sven_vB> ravage, reinstalling fixed it. :)
[18:12] <TJ-> FreeBDSM: no, this isn't for devs or packages, thats done in email via the bug trackers in Debian
[18:12] <ravage> Sven_vB: nice
[18:13] <Sven_vB> now what should I do instead of "ubuntu-divers autoinstall" to keep the comfort of making stuff "just work" except for the nvidia drivers that it had installed?
[18:13] <Sven_vB> *drivers
[18:13] <ravage> ubuntu-drivers list
[18:13] <ravage> will show you what drivers it can manage for you
[18:13] <ravage> but im almost sure the only thing it will show is the nvidia driver
[18:16] <Sven_vB> currently, it prints only one line, "nvidia-340". is it meant to output one driver name per line? then I would filter out "nvidia-340" lines, comma-glue together all others and run ubuntu-drivers install "$GLUED_NAMES"?
[18:17] <Sven_vB> (man ubuntu-drivers: "No manual entry for ubuntu-drivers")
[18:18] <Sven_vB> the comma glue idea I got from ubuntu-drivers --help
[18:18] <ravage> it prints our all available drivers. so there is only one available for your system
[18:18] <Guest87> who has any support questions
[18:18] <Guest87> does someone need help
[18:19] <Sven_vB> ravage, yeah, which is unfortunate because I cannot see in which format it would report potential other drivers.
[18:19] <tomreyn> Guest87: hi, i'd say just wait till someone asks a question. and maybe set a better nickname in the meantime.
[18:20] <ravage> Sven_vB: https://p.haxxors.com/qp7vhftv.txt
[18:21] <Sven_vB> ravage, thanks! can you give me the "ubuntu-drivers devices" as well for comparison?
[18:21] <ravage> https://p.haxxors.com/h57cydiv.txt
[18:22] <Guest87> i made an ubuntu 21.10 live usb, is it safe to not have the ubuntu symlink in the root directory of the usb?
[18:22] <Sven_vB> will the first word after "driver   :" always be an apt package name or can it be something other?
[18:22] <ravage> Sven_vB: looks like it is always a package yes
[18:23] <Sven_vB> ravage, ok, I guess I'll use that then. thanks again!
[18:26] <Sven_vB> in case someone wants to optimize the "ubuntu-drivers autoinstall", in my case the card identifies as "lspci -ks 05:00.0¶ 05:00.0 VGA compatible controller: NVIDIA Corporation G94 [GeForce 9600 GT] (rev a1)¶         Subsystem: ASUSTeK Computer Inc. G94 [GeForce 9600 GT]" and nouveau works for me.
[18:28] <Guest87> is it safe to not have the ubuntu symlink in an ubuntu live cd
[18:50] <Sven_vB> Guest87, not sure which one you meant, but probably yes.
[19:13] <TJ-> Guest87: isn't that symlink used for the CD archive repo pool?
[19:45] <nishijima03> hello
[19:46] <nishijima03> did you looked at gnome 40 performance?
[19:47] <Eickmeyer> nishijima03: Do you have a support question?
[19:48] <nishijima03> Nope :>
[19:48] <Eickmeyer> !ot | nishijima03
[20:49] <keyjoo_> words
[20:51] <pinky_> dumb question but is there a small netinstall image for 21.04 ?
[20:53] <EriC^^> !mini | pinky_
[20:53] <EriC^^> there should be
[20:53] <pinky_> thanks thats exactly what i want and i found that page but where is 21.04 ?
[20:54] <pinky_> am i blind? :)
[20:54] <tomreyn> IIRC it no longer exists
[20:54] <keyjoo_> ff
[20:54] <pinky_> http://cdimages.ubuntu.com/netboot/focal/
[20:54] <tomreyn> it was based on debian installed, which was legacy, and probably dropped by now
[20:54] <pinky_> clicking 'Intel & AMD x86 Guide' takes me to a very confusing page
[20:55] <tomreyn> https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510
[20:55] <tomreyn> oh, same url :)
[20:55] <pinky_> yeah i found this, too this is a link from there which is a 404 http://releases.ubuntu.com/focal/ubuntu-20.04.1-live-server-amd64.iso
[20:57] <pinky_> actually wait i found it, that page is just way too fancy
[20:57] <TheFatherMind> Greetings!  aptsh became unavailable after one of my upgrades some time back.  I would really like to use it again.  how do I get it back in?
[21:02] <tomreyn> TheFatherMind: was this ever in ubuntu? which package?
[21:03] <TheFatherMind> well I used to be able to install it with apt  'aptsh' it was a sort of shell for apt.
[21:03] <tomreyn> looks like it was in bionic's universe https://packages.ubuntu.com/search?keywords=aptsh
[21:05] <TheFatherMind> Yeah it is not in the repository anymore.
[21:05] <tomreyn> TheFatherMind: it was dropped off debian, apparently for dependency issues
[21:05] <TheFatherMind> Oh dear... this makes me so sad.
[21:05] <TheFatherMind> I had an uncle with dependency issues.  He was never the same again.
[21:06] <TheFatherMind> So I imagine getting it installed in the more current versions would be very difficult.
[21:06] <ravage> there is no current version
[21:07] <ravage> website does not exist. last update on sourceforce is from 2014
[21:07] <ravage> i would call is dead
[21:09] <TheFatherMind> aptsh is dead.
[21:09] <TheFatherMind> done!
[21:09] <tomreyn> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930680
[21:09] <TheFatherMind> Thank you for taking the time to talk to me about this.  I deeply appreciate it.
[21:11] <tomreyn> you're welcome :)
[21:34] <pinky_> so i guess the text installer doesn't support everything? i don't see how you create zfs on root https://linsomniac.gitlab.io/post/2020-04-09-ubuntu-2004-encrypted-zfs/
[21:37] <tomreyn> pinky_: this article is about the (graphical) desktop installer
[21:38] <tomreyn> (and i do not know whether or not the server installer supports zfs encryption on the root file system)
[21:39] <toddc> zfs encryption not yet but soon
[21:46] <pinky_> ah ok thanks
[22:14] <arh> Hello people. This is urgent for me so I appreciate if someone can help me. I want to let someone login to my Ubuntu 20.04 VPS using their SSH key. I added their keys to authorized_keys file and changed the permission of .ssh folder and the authorized_keys files to 700 and 600. Now they should be able to login right? But when I type ssh IP, it asks me for password, but when I type ssh ubuntu@IP, it doesn't require a password and logs in but I can't use the
[22:14] <arh> sudo command.
[22:15] <arh> I changed the permissions using this command: $ chmod 700 -R ~/.ssh && chmod 600 ~/.ssh/authorized_keys
[22:15] <arh> When I want to reboot or do some stuff, it says permission denied. So I think there's still need for sudo and therefore a password.
[22:15] <arh> How can I fix this?
[22:21] <jhutchins> I think I have some issues with some of my chrome extensions.
[22:21] <jhutchins> Next, they must log in as a user with an account on the target system.
[22:26] <tomreyn> arh: so, there are mostly two commonly used authentication methods for the connection from a local computer to a remote ssh server: one is (ssh) password authentication, i.e. the password is sent to the ssh server and it checks whether this matches the password of the remote (on server) user you are trying to login to. and then there is key authentication, where your ssh client uses your locally stored ssh private key to authenticate to the
[22:26] <tomreyn> server as the given user. for this to work, the server must already have the public pkey of this ssh key pair, stored in the target users' ~/.ssh/authorized_keys - and the target user must be able to read this public key. an ssh private key *may* have an additional password on it, i.e. be locally encrypted with a password to safeguard against someone getting access to your computer just copying it.
[22:27] <cuddylier> I've upgraded my Ubuntu 20.04 to 5.14.14 kernel but I need to use turbostat and it requires the linux-tools package for the kernel. I cannot find a tools package for the 5.14.14-051414 kernel, does one not exist?
[22:27] <tomreyn> arh: and then there is sudo on the server, which may be set up to require the executing users' password to carry out administrative tasks. that's how ubuntu usually sets up the first user.
[22:27] <tomreyn> (that is the one created *after+ the root user)
[22:29] <ravage> cuddylier: 5.14 is not a supported kernel on 20.04. so there is no such package
[22:29] <arh> tomreyn, so I have to give them the user's password to let them use sudo, right?
[22:30] <arh> Actually, I should change the root password, right?
[22:30] <arh> sudo passwd root
[22:30] <arh> And then give the password to that person.
[22:30] <arh> Is it correct tomreyn?
[22:31] <tomreyn> arh: with this explained, looking at your questions, you seem to be working on some different issues: (1) which  is the right remote user to login to, for you, and (possibly a different one) for the other person you are trying to grant access? (2) should your or the uother person's remote user be able to run administrative commands (as root) through sudo? and if so, should sudo prompt them for their remote users' password? (3) how do you install
[22:31] <tomreyn> the ssh public key of this other person you want to grant access, and on which remote user.
[22:31] <tomreyn> arh: there should be no root password normally.
[22:32] <tomreyn> arh: you should probably have two separate remote user accounts, one for the other person and one for you. both you and the other person would then    ssh myremoteuser@remoteserver
[22:33] <tomreyn> arh: that way you can have differnet sudo passwords for your self and the other person
[22:33] <arh> tomreyn, (1) there's only one user on this machine. Should I create a new account for them? (2) Yes they should be able to, I want them to run/install/modify some stuff
[22:34] <arh> Ah OK.
[22:34] <rfm> arh, and you can put e.g. "theiruser ALL=(ALL) NOPASSWD:ALL" in /etc/sudoers (or a file in /etc/sudoers.d), then they could sudo without a password.  (This is what the AWS ubuntu images do...)
[22:35] <arh> So I should create a new user with addministrative access for them first.
[22:36] <tomreyn> arh: to (1) that can be a good approach, yes.  (2) then do as rfm says if you want them to be able to sudo with entering a password, or do     sudo adduser otheruser sudo    if you want them to be able to sudo with entering their remote users' password
[22:37] <tomreyn> (2) then do as rfm says if you want them to be able to sudo withOUT entering a password, or do     sudo adduser otheruser sudo    if you want them to be able to sudo with entering their remote users' password
[22:37] <tomreyn> ^ fixed ;)
[22:43] <arh> tomreyn, rfm, I create a user with root access for them. Now can you please tell me, if they set up something, say a Nextcloud instance, and I delete their username, will the that setup be deleted too?
[22:44] <tomreyn> arh: it wont
[22:44] <tomreyn> it may stop working, though, depending on how they set it up
[22:44] <arh> tomrey, rfm, thank you guys very much. I really appreciate it.
[22:45] <tomreyn> arh: you're welcome. make sure to tell them which remote user the need to ssh in with (by default, and ssh client will try to login to the remote server with the same username they are running as locally)
[22:46] <TJ-> sounds like the perfect scenario for using an unprivileged container for the user, then they get a complete OS and root inside it, with no impact on the host
[23:58] <Gallomimia> can someone remind me what to do to recreate my swapfile and turn it back on?
[23:58] <Gallomimia> i know... swaponn. what about fstab