[02:14] why does proxychains sometimes work and sometimes not work? [02:30] hi all, i problem with micork8s, is there a channel for it to join and ask question? [02:30] or I can just ask here? [02:31] basically i use microk8s via snapd and microk8s enable dns and then microk8s reset, but after reset k get all -A still show resources there (old pods spawned by 'microk8s enable dns' command), why? [02:31] probably #ubuntu-server will work better than here, but it doesn't come up often there, so .. maybe not even there :/ iirc microk8s folks have a discourse, though maybe they've got a mattermost .. [02:32] i tried #microk8s and just me there [02:32] :( [02:32] anyway if someone here from ubuntu can help? [02:33] snap version here: [02:33] https://0x0.st/ouPT.txt [02:34] i also got this error when i do *microk8s.reset*: sudo: symbol lookup error: /snap/core18/current/lib/x86_64-linux-gnu/libpthread.so.0: undefined symbol: __libc_vfork, version GLIBC_PRIVATE [02:34] i had both core18 and core installed via snap install [02:36] tmpm697: Pretty much noone here is from Canonnical, or Ubuntu. We are just fellow users who might have come across something like your problem before. [02:37] tmpm697: What snap did you try to install, and where was it from? [02:38] i tried to install microk8s, snap version posted above, i use archlinux [02:39] i expect microk8s.reset remove all resource but it did not. [02:39] tmpm697: Probably not going to get assistance here. [02:40] i'm going to #snappy for help. [02:40] tmpm697: Yeah, arch is different in exactly the sort of way that would cause that problem. [02:41] !arch [02:41] can't be, it's just snapd and its package [02:41] !archlinux [02:41] Other !Linux distributions besides !Ubuntu include: Debian, Mepis (using !APT); RedHat, Fedora, SUSE, Mandriva (using !RPM); Gentoo, Arch Linux, Manjaro, Slackware (using other packaging systems) [02:42] tmpm697: You're hitting a C library version difference in the code, and it's exactly that kind of detail that's different between distros. [02:43] ok let me check with archlinux guys [02:43] tmpm697: "undefined symbol" = me no speak language. [02:43] tmpm697: Sorry, I thought the factoid included support info for arch. Braindead bot.. [05:24] After an upgrade from xubuntu 16.04 to 18.xx to 20.04 this weekend I'm getting login screen loops when I put the laptop to sleep. https://www.maketecheasier.com/fix-ubuntu-login-loop/ and everything in https://askubuntu.com/questions/223501/ubuntu-gets-stuck-in-a-login-loop One weird thing is xubuntu-desktop isn't installed. Not using nvidia. [05:30] doc: Sometimes upgrades can go wonky like that. While it may be possible to repair the system at this point, it may be easier to simply boot the system from a live USB, copy over your personal data onto an external drive, and reinstall. Make sure to copy all your hidden files when you do this, so that you can keep any saved passwords from Firefox and any other important files. If you have other applications that require logins, you may [05:30] want to research where they store their data and back that up, too. [05:30] arraybolt3[m]: that was my worry. I've never once had a dist upgrade not need a wipe. [05:30] That's why I was still on 16.04 :( [05:30] (By "copy all your hidden files", I mean all the hidden files and folders in your /home/user directory.) [05:30] * doc nods [05:31] I have yet to ever do a dist-upgrade - I always clean install. [05:31] Was really hoping to avoid that :/ [05:32] Well, stick around for a while longer, maybe someone will know how to fix it. [05:32] yep, thanks! [06:51] hello! [06:51] goodbye! === diskin is now known as Guest993 === diskin_ is now known as diskin [08:37] lol === LjL^ is now known as LjL [09:16] hi all [09:16] is there (1) a way i can tell apt to please not ask me about restarting services after upgrades and (2) a way to tell it to not instruct me about any pending CPU microcode updates? [09:45] Hey all [10:00] I'd like to set up a repo mirror for Jammy. I was looking at apt-mirror (deprecated) and aptly (no new release since 1.4.0 in 2019). What are my alternatives [10:00] ? [10:02] doosboox: honestly I wouldn't deal with those, just use rsync on a cron/timer [10:03] murmel: No can do. I need to be able to pin versions of packages and filter stuff out. [10:05] doosboox: reprepo is what most use then. but no idea if you can pin versions (i assume) [10:10] murmel: I'm reading https://wikitech.wikimedia.org/wiki/Reprepro now and I don't see any indication that it's used to set up mirrors [10:11] doosboox: https://wiki.debian.org/DebianRepository/SetupWithReprepro [10:12] murmel: thanks! [10:16] it looks like reprepro hasn't been updated for three years [10:21] hmm [10:21] doosboox: just because it wasn't updated doesn't mean it doesn't work. otherwise as I said you can use rsync and implement a pin yourself. otherwise you can look into a complete lifecycle system like theforeman.org [10:21] did i ask a bad question? :( [10:22] rapha: hm? I was talking to doosboox [10:22] or I didn't see your question [10:23] hi. having issues with no sound (dummy output). installed different distro and updated bios as a last resort with no change. wondering if this could be anything else than a hardware problem at this point? [10:25] Zoa3333: did it ever work? [10:25] murmel: yes, it worked well a couple weeks ago. i started up a newly installed game (elder scrolls online) and about 5 minutes in all sound stopped working [10:26] Zoa3333: What hardware are you using? Like "Dell Inspiron 7000", or something like that. [10:26] arraybolt: the pc is custom built but using asus tuf gaming 550 pro [10:26] Zoa3333: Ack, what? Yikes. Maybe you can also do "lspci | nc termbin.com 9999" and then give us the link. [10:27] thank you, will do [10:28] arraybolt: https://termbin.com/k5gz2 [10:28] murmel: sorry, i didn't mean you specifically. just the face that not even a "sorry, it's not possible" came back. but perhaps it's just an odd question and noone knows... [10:29] OK, I see the audio device in there, so the hardware isn't just dead. That's good. [10:29] arraybolt: true. in the sound settings it says dummy output. however yesterday it all of a sudden recognised the device in there too. then after a restart it went back to dummy output [10:30] seemed very random since i had not changed anything other than restarted, which i have done many times now [10:30] arraybolt3[m]: are you sure? it sounds to me that those outputs are from the gpu [10:31] One of them's HDMI, but the other isn't. [10:31] But wait, that's a good point. Zoa3333: Is there anything in the drop-down that says "dummy output" other than dummy output? Like, if you click on "dummy output", do you see a different option in the list? [10:32] arraybolt3[m]: well that board uses a realtek device, which the second audio device *is not* [10:32] Oh crud. [10:32] arraybolt: no unfortunately. yesterday when the device was recognised briefly, i think 3 options were in the drop-down meny [10:33] and it was the correct device, i think. not the gpu [10:33] Zoa3333: Does both your monitor and motherboard (or GPU) support HDMI? And if so, do you have an HDMI cable lying around anywhere? You might be able to work around the issue by using the audio through your GPU. [10:34] aha, it seems as for the microcode thing you can just apt purge intel-microcode on a vm [10:34] arraybolt: i don't right now but might be able to get one. i tried plugging in my headphones in the monitor since they had a heasphone jack just in case but i got nothing out of that [10:35] headphone* [10:35] i've also tried in the back of the computer and so on, but that might not be relevant [10:35] rapha: you don't need the firmware, but why bother removing, as it's only a few megs [10:35] Zoa3333: Also, you might try opening up your desktop and cleaning it out. There might be a hardware short that's causing the problem. [10:36] Zoa3333: with your monitor it depends how you connected it to your pc. as most cables don't transport audio [10:36] Fun fact - the reason software bugs are called "bugs" is because a computer programmer lady for the Navy found a dead moth in the guts of the computer that was causing the thing to go haywire. [10:36] arraybolt: will try this, thank you [10:37] murmel: i understand [10:39] arraybolt: if cleaning it does not work, is it likely to be hardware? or should i continue investigating before using the warranty, in your opinion [10:39] i have tried getting it to work for almost two weeks [10:39] on and off, ofc. [10:40] Zoa3333: If it's not appearing in your lspci at all, the computer doesn't know it's there anymore. If cleaning doesn't do the trick, I'd use the warranty. [10:40] Zoa3333: never saw which other distro you tried. just make sure that it's not the kernel having a hicup [10:40] Zoa3333: If that's too much of a hassle, you might be able to find a USB audio card to get you back up and running. [10:41] Even if the kernel was being grumpy, something should at least pop up in lspci, right? [10:41] i went from mint cinnamon to ubuntu, so maybe that wasn't the smartest [10:41] i also reinstalled a few times [10:42] then after none of that worked i did a bios update today [10:43] Zoa3333: eh, so both ubuntu. well it's very unlikely that it's the kernel. imho sounds like rma [10:44] Yeah. Multiple distros not working, when it used to work? No card in lspci? Me thinketh yon sound card has bitten the silicon dust. Or at least has some serious issues. [10:44] i see. t's only a few months ago that i bought it. unfortunate but good that there is still warranty, i suppose [10:45] thanks a lot for the help. will try to clean and if that does not help i'll go for the warranty [10:45] Man, and you even used ASUS. I thought they were one of the best brands after my research when I was thinking of building my own PC. [10:45] arraybolt: me too, i am definitely surprised [10:46] shit happens, i guess. won't clutter the chat so have a good one. thanksd again [10:47] murmel: i'm trying to get rid of that nagging error message after every single use of apt. [10:47] murmel: and also removing it didn't work, it's a dependency for the kernel :( [10:50] arraybolt3[m]: not anymore. (imho) even asrock is better [10:51] rapha: which error message are you talking about? [10:51] Wow, last I checked, ASRock got some of the worst reviews. [10:51] and honestly manufacturing issues always happen [10:51] I was always happy with them, in comparison with asus (plus asus back io is weird imo) [10:52] OK, I'll stop with off-topic, especially since you're in the middle of a support chat. Good luck! [10:52] murmel: https://i.stack.imgur.com/a28OY.png [10:52] hmm maybe if i remove the needrestart package [10:53] rapha: Out of curiosity, have you rebooted in a while, or are you relying on Livepatch to keep your system on forever? [10:53] YAY!!! Finally! Freedom from the message! [10:54] rapha: sounds like you don't like using firmware updates to your host cpu? [10:54] arraybolt3[m]: it's a VM. the microcode patching will always fail. rebooting doesn't change anything. also, this box needs to keep running until multiple people come to a consensus about a reboot being okay now. so these messages are just nuisances. [10:54] murmel: as i said, it's a VM. [10:54] rapha: I am talking about the host [10:55] rapha: Hey, can you change the CPU version in your VM so it uses a QEMU CPU rather than an emulated Intel or AMD processor? [10:55] how would it make sense (or even work in a sane way) for any one of the VMs to upgrade the HV's microcode, murmel? [10:56] Or are you not using QEMU/virt-manager/Gnome Boxes? [10:56] arraybolt3[m]: that might cause a different instruction set to be available. i need the VM CPU to copy the host CPUI definition. [10:57] rapha: I was talking about the host OS not loading the newest blob, which means it has security flaws. I am not talking about you doing it. rather the sysadmin for the host [10:57] and this is all headless arraybolt3[m], no gnome boxes, good lord [10:58] rapha: I do a lot with VMs, but not in a server situation. Maybe the server needs a... reboot? That might actually be necessary, but be prepped for chaos if you're the one doing it, and prep your sysadmin for chaos if they're doing it. [10:58] murmel: i'm the sysadmin for the HV as well. which is Alpine Linux, not Ubuntu. and same problem about having to get multiple people's consensus(es?) before rebooting. and the machine is in a DMZ for exactly that reason. and i don't understand why wanting to disable an annoying and frankly quite unnecessary messages causes one to have to justify oneself? [10:59] anyhow, apt purge needreboot helped AND felt really really good [10:59] rapha: Processor microcode keeps you from having severe security incidents. If your server's processor isn't using the latest microcode, you could get pwned. [10:59] good lord [11:00] anyone know what "tee" means in this command? "wpa_passphrase Gabriel G\@br\!el1 | sudo tee temp.conf" [11:00] stop mansplaining people [11:00] and look up what a DMZ is [11:00] rapha: Since your VMs are mimicking the host's CPU, it's possible that they're able to see the outdated microcode, and you never see the error on your headless server. [11:00] arraybolt3[m]: I hope rapha knows what he is doing, otherwise we have another spammer [11:01] rapha knows what SHE's doing and you have a lot of patronizing going on in here [11:01] murmel: Hey, he had a legitimate question. And I only recently learned about the CVE nighmare. [11:01] anyhow thanks for listening and trying to help [11:01] s/he/she [11:01] have a nice day everyone [11:02] murmel: Man, I do hope she doesn't get her server pwned. I looked up a DMZ, that is not going to be enough to protect her. I should have linked to some stuff about Spectre and Meltdown. [11:03] arraybolt3[m]: DMZ helps, but not that much, depending on what her collegues/friends/customers? do [11:03] arraybolt3[m]: but those are exactly the reason why whole servers are being taken over [11:04] murmel: Who cares if you can hack into a network service when you can just leak RAM contents? Grab an encryption key and game over. [11:05] arraybolt3[m]: depends on the 'network' [11:05] True. [11:08] weedmic: The "tee" command in that command allows you to see what's being written to the temp.conf file. [11:08] "tee" takes the data that you pipe into it, saves it to a file, and forwards it to the next application in the pipeline (which, in that command, happens to be your terminal window). [11:09] So whatever wpa_passphrase throws onto standard output, gets thrown on your terminal screen and saved to temp.conf. === hayaliali is now known as alip [11:35] I am trying to do a custom cloud image build using packer. It works, however, my image is quite large and has lots of stuff installed in it when built. I cant seem to find any options in the docs to choose a minimal set of packages and the image ends up having lots of stuff in it I do not need. Does anyone have a link for documentation describing the package selection, or do I have to manually find [11:35] packages I dont need and uninstall them? :) [12:01] Hi all [12:03] This morning i installed a firmware upgrade for my Lenovo P52 through "Ubuntu Software". After rebooting, only windows 11 is bootable. I tried repairing grub using Boot Repair and also following the answer here. Both with no success. Any help? [12:04] The link to SO went missing: https://askubuntu.com/questions/719409/how-to-reinstall-grub-from-a-liveusb-if-the-partition-is-encrypted-and-there-i [12:05] MonsieurBon: did you make sure that grub is selected in uefi? [12:06] murmel, how do I do that? [12:11] MonsieurBon: depending on your device, it's f2 or del to enter uefi/bios [12:13] murmel, yes. grub is actually starting, but just showing a shell prompt. I might have missed a step. I'll retry! [12:14] MonsieurBon: ah, seems like your grub really got corrupted. [12:15] murmel, I think I forgot to mount the /boot partition (which is separate in my case) when following this guide https://askubuntu.com/questions/719409/how-to-reinstall-grub-from-a-liveusb-if-the-partition-is-encrypted-and-there-i [12:15] MonsieurBon: oh, yeah that's important as there is the config for grub [12:15] Is it possible to run Ubuntu on the M1 chip by now? [12:16] guy4545: no, they are still developing for it (on an arch base) [12:16] will still take awhile [12:16] murmel: Does that hold true for all Linux distros? [12:17] Yes. They're still porting the Linux kernel if I'm understanding correctly. [12:18] guy4545: as the devs are working with an arch base, upstreaming everything. that means if something works, it should run it's normal course at some point. but for now it's only usable as a server, gui still has no accel [12:19] arraybolt3[m]: they are mostly done with the kernel itself afair [12:19] now we are talking about gpu/nvme driver and other stuff [12:20] murmel: Ah, good to know. That's cool! [12:21] Hi all [12:21] I really hope that we can get to a point where it's usable. their build quality is miles ahead of any other manufacturer [12:21] but enough small talk here xD [12:22] murmel: This was a support question. [12:22] guy4545: Correct. murmel was getting off onto small talk, not you. [12:22] eh, I was talking about my rambling about build quality :) [12:23] murmel: But thanks, those were all questions I had. [12:23] guy4545: no problem :) [12:25] murmel, ok, better! I'm booted into ubuntu. Now the only problem is that Windows is missing from grub config. How do I recover that option? [12:25] MonsieurBon: make sure that you enable os-prober in /etc/default/grub [12:26] MonsieurBon: What version of Ubuntu are you on? (Sorry if you already said this, but I don't want to hunt through the history to find it.) [12:26] with GRUB_DISABLE_OS_PROBER=false [12:27] MonsieurBon: If you're using Ubuntu 22.04, I wrote a guide on getting your other operating systems to show up here: https://askubuntu.com/questions/1410398/just-installed-ubuntu-22-04-on-a-dual-boot-setup-now-my-other-os-isnt-showing [12:28] murmel, os_prober is enabled [12:29] MonsieurBon: does os-prober find your windows install? sudo os-prober [12:29] MonsieurBon: Can you do "sudo grub-mkconfig -o /boot/grub/grub.crg" and see if that fixes it? [12:30] murmel, yes [12:30] arraybolt3[m]: on deb/ubuntu we use update-grub [12:30] murmel: OK, good to know, I've always done grub-mkconfig. I'll look into update-grub. [12:31] arraybolt3[m]: it's just an alias for that command ;) [12:33] murmel, perfect, I think everything's back to normal! [12:34] MonsieurBon: nice [12:35] murmel, thx for your help === webchat20 is now known as kristenb [13:12] wide open question. i'm using a yubikey in ubuntu just fine. i'm using a citrix receiver to try and use the yubikey on a remote windoze VDI. the remote VDI sees the key via CAPI, it can query the certificate. however it fails to see the smartcard. i've tried running pcscd on ubuntu, it didn't seem to help. any ideas? [13:17] thanks @Kow [13:17] i got voiced eh? [13:20] 🦕 [13:21] nope [13:22] Can I program cpu fan curves for my amd ryzen 3xxx series cpu inside ubuntu/kde? === BiTCHiN is now known as PIE === PIE is now known as BiTCHiNPIE [13:59] is there a way to undo `ip link set dev address `? I don't see any unset option. The permaddr is still available with ip link... is awk the best way? [13:59] Hello guys.We have a problem with ubuntu on AMD A8-9600.Then PC is load we have AMD-Vi IOAPIC[1] not in IVRS table.Bios is updated,we can't disable IOMMU in bios,there is no option in bios/UEFI on this PC.After amd_iommu_dump=1 we reach command line,but can't start X. [14:01] neff: I'm not sure quite what's going wrong. Are you trying to do VFIO GPU passthrough? [14:01] Also, knowing the exact version of Ubuntu and the make and model of the computer you're using may be helpful. [14:03] arraybolt3[m]>no we not trying passthrough [14:04] We just trying to install it on PC [14:04] The pc specs is > [14:05] Processor AMD A8-9600 RADEON R7.Motherboard A320M-HCF [14:05] neff: If you're not doing passthrough, then why do you need to mess with the IOMMU? Is something else going wrong when "amd_iommu_dump" isn't used? [14:06] We don't need it,but it that system want [14:06] If Without this param PC not loading at all [14:07] We tried to disable iommu at all with iommu=off [14:07] No results [14:07] neff: Hrm... OK, let me do some research. [14:08] I cheked all what i can google.But nothing helps [14:09] I thing we need to disable some kernel modules,but wich i don't understand [14:09] hi guys, i made the update from 20.04 to 22.04 for testing it out and it worked surprisingly well except for one weird issue. If i run emacs --version or pulseaudio --version, or try to launch or build something that depends on those libs i keep getting these: http://ix.io/409r undefined symbol error. However if if i login to the same shell from ssh or simply run "newgrp" those problems get fixed, but doesn't matter if i reboot or [14:09] launch a new terminal inside the X session or tty i have that problem. And ive rebooted many times. What is going on here [14:09] neff: I think I found the instructions for disabling the IOMMU. [14:10] Where& [14:10] ? [14:10] https://download.gigabyte.com/FileList/Manual/mb_manual_ga-a320m-h_e_1201.pdf Page 30, near the bottom. [14:10] Turn off the IOMMU, then set "iommu=soft" in your kernel command line and see if that does it. [14:10] paste correction -> http://ix.io/409s [14:11] "iommu=soft" tried not works [14:11] neff: Are you able to turn off the IOMMU with the link I gave? [14:13] neff: which ubuntu variant and version are you trying to install on it? [14:14] 22.04 standart [14:14] desktop? [14:16] neff: Another thing you might try on your kernel command line is amdgpu.runpm=0 [14:16] mattf: did you reboot after the upgrade? are you using PPA? [14:16] many reboots [14:16] * PPAs [14:16] no ppas [14:16] i made a huge cleanup [14:16] and reinstall [14:17] reinstall meaning a fresh install? [14:17] tomreyn: please realize that those applicatiosn are working, it is a problem on my shell it seems [14:17] if i run newgrp it gets fixed, if i run from a launcher like albert or rofi emacs opens fine, from ssh it is also working [14:17] but if i reboot it is not fixed [14:18] what's your custom shell there? [14:18] It's virtualization. [14:19] tomreyn: zsh [14:19] Just try it, I found it in a bug report about AMD Ryzen IOMMU problems. [14:19] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747463 [14:19] Launchpad bug 1747463 in linux (Ubuntu Cosmic) "kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X" [Medium, Confirmed] [14:19] could this be some sort of weird env variables [14:20] mattf: and it works with bash? [14:20] no [14:20] mattf: Random shot in the dark, is LD_PRELOAD set weird? [14:20] maybe you are LD_PRELOAD'ing [14:20] arraybolt3[m]: no im not, just checked [14:21] mattf: what does this print: apt list --installed | grep ',local]$' 2>&1 | nc termbin.com 9999 [14:21] Well we continue diging [14:21] neff: how is virtualization involved there? [14:22] Look.IOMMU is system that makes virtualization.It helps to make transfer between real and virtual memory for example [14:23] I am not pro guy [14:23] are you installing ubuntu 22.04 on the bare metal or is there a virtualization layer in between? [14:23] tomreyn: AMD's IOMMU combined with the AMD graphics is causing Linux to crash for we dunno why. The bug report has the mess. [14:23] So i can't explane it to you good [14:23] At least I dunno why. [14:23] But virtualization is involved [14:23] arraybolt3[m], pretty old bugreport for 18.04 beta.. [14:23] arraybolt3[m]: the bug report you pointed to is for cosmic for an amd ryzen first generation cpu [14:24] ah, virtualisation.. you should mention that [14:24] neff, how much memory did you allocate for the vm? [14:24] It looked like close to the right processor, and it's still not marked as fixed, so I thought maybe it was relevant. [14:24] tomreyn: hah i found out, LD_LIBRARY_PATH is being set.... now i have to found out why but that is it [14:24] NO VM INVOLVED [14:25] oerheks: He's not using a VM. Virtualization technology is throwing a wrench in the works for some unknown reason. [14:25] But virtualization is involved ?? explain please? [14:25] mattf: okay, at least i got close ;) [14:25] oerheks: IOMMU go boom [14:25] oerheks: Makes Linux not boot [14:25] The modern OSes use virtualization to protect memmory [14:25] oerheks: Why IOMMU is interfering with Linux, only the guts of the system knows, and probably even it doesn't know why. [14:25] arraybolt3[m]: is there an error message printed on screen when you boot the installer normally? [14:26] tomreyn: You probably wanted to direct that at neff. [14:26] neff: is there an error message printed on screen when you boot the installer normally? [14:26] Yes it's installed without any known errors [14:26] arraybolt3[m]: that's right, sorry :) [14:26] But on boot makes mess [14:27] neff: is there an error message printed on screen when you boot the installed system the first time, normally? [14:27] if not, what else happens that is not expected? [14:28] neff: I'm wondering if maybe this isn't the fault of the IOMMU after all, since the installer boots. Perhaps you're trying to install the proprietary drivers when you install Ubuntu? If so, try not installing them, or if you're not installing them, try installing them. [14:28] tomreyn we have an error message and then system freezes [14:28] tomreyn: Their system won't boot. [14:28] neff: what does the error message say? [14:29] arraybolt3[m]: that's what i've gathered so far, but we need more details than that [14:29] neff: You can take a picture of it with your phone, upload it to Imgur, and send the link. [14:29] AMD-Vi [Firmware Bug]:IOAPIC[1] not in IVRS table [14:30] neff: does this also happen after you load manufacturer defaults in bios? [14:30] Guys - AMD Vi - IS virtualization [14:31] AMD I/O Virtualization Technology (IOMMU) [14:32] neff: this is a CPU / bios feature to allow for improved I/O virtualization. but whether or not that's enabled should not normally change whether or not your bare metal installation boots. [14:33] especially since you're not actually doing virtualization, from what we have gathered so far, but are just installing ubuntu 22.04 LTS on bare metal. [14:33] virtualization would be when you'd run a second operating system below ubuntu [14:34] tomreyn: I found the post on how to fix the problem, but it's tricky: https://ubuntuforums.org/showthread.php?t=2254677 [14:34] It's a BIOS bug, and a doozy of a bug, too. Some sort of table is broken, and you have to figure out where the BIOS writers botched it and then patch it yourself with some Linux options. [14:35] neff: Is that "AMD-Vi [Firmware Bug]" error the only one you see, or are there multiple lines like that? If there's multiple lines, can you show them all? [14:36] arraybolt3[m]: yes, that's well possible. i'm not yet sure whether this is the actual issue that's cuasing the system to fail to boot, or just yet another issue. [14:36] Only [14:36] !bootlog | neff [14:36] neff: To get a more verbose log of the boot process, remove "quiet" and "splash" from the kernel boot parameters and add "debug systemd.log_level=info". For info on editing kernel boot parameters, see https://wiki.ubuntu.com/Kernel/KernelBootParameters [14:37] I check it thank you! [14:37] I see, because all that does is get the IOMMU working, it's not something a user should usually have to do. [14:37] tomreyn: Brilliant, that will show us the exact kernel panic message (if the kernel is panicking). [14:38] hopefully so, yes [14:38] neff: You'll have a hard time typing the whole message, so if you have a camera, taking a picture of the mess on your screen and then sending it will make things easy. [14:38] a broken iommu configuration is obviously a very bad indication, too, but *may* not be why it's actually failing to boot [14:39] neff: you can share images with us by uploading them to imgur.com and then posting the http address ehre [14:39] here [14:41] is it normal that when a process eats all available memory (ram+swap) then it is killed including its parent process which would be the terminal? [14:41] I've seen the terminal crashing, and it took me a few times before realizing the compiler was eating all of the memory, as I could not see the proper error message of why the process was terminated [14:41] (this is only happening on 22.04, not on 20.04) [14:42] yte3: Sounds like you're hitting the notorious systemd-oomd issue. [14:43] arraybolt3[m]: it looks very likely. but what's the point of killing the terminal? [14:43] isn't killing the "bad" process enough? [14:43] Anyone here know how to disable systemd-oomd? Give the info to yte3, I think it will fix the issue he's experiencing. [14:44] neff: you wrote this is a "Motherboard A320M-HCF". which company is this from? [14:44] arraybolt3[m]: no, I don't need to disable systemd-oomd. I just needed to add more swap space [14:44] yte3: systemd-oomd looks at the processes to kill differently than the kernel OOM killer. It attacks an entire cgroup (dunno what all that means). So rather than killing one browser tab, you kill the whole browser. And presumably, rather than killing just the compiler, you also chuck the terminal. -_- [14:45] yte3: Oh, that makes sense. Do you already know how to do that? [14:45] arraybolt3[m]: yes, that fixed my oom issue [14:45] arraybolt3[m] my point is that killing the terminal is probably not desired [14:45] normally, killing the oom process should be enough [14:45] but I don't know the details of oomd either [14:46] yte3, https://www.omgubuntu.co.uk/2022/06/ubuntu-22-04-systemd-oom-killing-apps [14:46] yte3: Yeah. There's a whole entire thread of people trying to figure out what to do with systemd-oomd. I can bring up this problem on that thread (I think), and I believe I can forward the whole thread to you if you'd like. [14:46] neff: okay, this one apparently: https://linux-hardware.org/?view=computers&type=desktop&vendor=Gigabyte+Technology&model=A320M-H-CF [14:48] ioria, arraybolt3[m]: thanks for the pointer. that article mentions two bugs. I'll see if it makes sense to add a comment with my usecase [14:48] yte3, ok [14:51] neff: the bios update page for this mainboard says "NO Bristol Ridge processors support" for all *updated (but not for the original) BIOS versions. [14:52] neff: your CPU IS a bristol ridge generation CPU [14:53] tomreyn: Wow, so they released a BIOS update that got rid of CPU support? That's a new one for me. [14:53] oh good spot, tomreyn [14:54] arraybolt3[m]: it's either that or they missed to also note it for the original release. but seems like it can be worth a try. the A320 chipset is the very first there was for ryzen [14:55] and apparently to provide compatibility for newer CPUs they had to drop bristol ridge [15:02] neff: so, yes, you have an older cpu, which was only supported on the first release of the bios for this mainboard, you will need to downgrade the bios to the original version. === AKTheKnight3 is now known as AKTheKnight === caverton1 is now known as caverton [15:38] hello [15:45] :-) === jesopo is now known as jess [15:46] HI! I am getting this error with sudo https://www.sudo.ws/repos/sudo/rev/8c6eaa503793 , whats the best way to handle this for Ubuntu 22.04? [15:47] transhumanist, explain please? [15:48] what command did you use? is it mecurial ? [15:48] sudo -u ./uml-install-11-Inner.sh >> results in sudo: error initializing audit plugin sudoers_audit [15:49] host file looks like this https://bpa.st/2KMA [15:50] sudo -u .. why change user? [15:50] and what user? [15:51] oerheks: IIRC if arg is omitted for the -u option, the default is root [15:51] instead of doing sudo -s I want the script to run with users environment not as roots enviornment [15:52] hi Folks! how to add this package as an apt repository? https://launchpad.net/ubuntu/+source/gnome-sushi [15:52] transhumanist: sudo -E ? [15:52] the version currently offerred by default is broken [15:52] dauggy: for 20.04 its in universe repository. Enable it from GUI [15:53] if one wants to run that script as user, drop the sudo? [15:53] KBar: how to do that? [15:53] dauggy: Software & Updates, tick "blah-blah-blah (universe)" [15:54] then `sudo apt update && sudo apt install gnome-sushi` [15:54] that appears to work so far depesz thanks [15:54] KBar: i think that if you specify, for sudo, -u, then you also need to specify the target user. you can omit -u targetuser altogether and run as root, though. [15:54] yeah the thing is they provide the old version [15:54] I had that ticked [15:56] dauggy: which ubuntu version are you running there? [15:56] 20.04 [15:56] dauggy: what's the output of apt policy snome-sushi 2>&1 | nc termbin.com 9999 [15:57] dauggy: what's the output of apt policy gnome-sushi 2>&1 | nc termbin.com 9999 [15:57] ^ typo fixed [15:57] tomreyn: apt policy gnome-sushi 2>&1 | nc termbin.com 9999 [15:58] https://termbin.com/80a4 [15:58] dauggy: so version 3.34.0-2 is available on your 20.04 LTS 'focal' system. And the page you pointed to offers the exact same version for 'focal' [15:59] right, and I'd like to have the very latest one: 41.2-1 hoping they fixed the bug there [16:00] dauggy: that's like wanting a lambo engine on a ford truck. try backports mb? [16:00] dauggy: did you mean to ask "how do i install gnome-sushi version 41.2-1 on my Ubuntu 20.04 LTS system?" [16:00] tomreyn: yes! [16:00] !latest | dauggy [16:00] dauggy: Packages in Ubuntu may not be the latest. Ubuntu aims for stability, so "latest" may not be a good idea. Post-release updates are only considered if they are fixes for security vulnerabilities, high impact bug fixes, or unintrusive bug fixes with substantial benefit. See also !backports, !sru, and !ppa. [16:01] tomreyn: ah, I see the difference [16:01] dauggy: try `apt-get install -t focal-backports gnome-sushi`. may break your system [16:01] dauggy: the newer version would mostly likely not be fully compatible to the version of nautilus / gnome files / the gnome-shell you have now. [16:01] I see, many thanks! Will wait until summer to upgrade to newest lts [16:02] dauggy: you could also file a bug report, and look for existing bug reports [16:03] 20.04 has a good while to live. it's a universe package, so there's no guarantee that soemone will fix it in 20.04, but there's a chance. [16:04] I saw the bug open in the gitlab repository of the package, so maintainers must be aware of it. Thanks once more [16:04] well, fwiw its changelog suggests it's quite "lively" [16:07] dauggy: i don't necessarily want to convince you to file a bug against ubuntu, too, but to see this fixed in 20.04, just the upstream (gneom) developers fixing it would not be enough, because this fix would not land in 20.04 automatically (because the package version there is older) [16:07] but with a bug filed against the focal package, there would be a chance that someone would backport this fix into 20.04's version. [16:09] I see, my point was rather, that assuming the maintainer knows about the bug they would take care of of that themselves, no? [16:10] dauggy: that would be unusual unless they were also the package maintainer in ubuntu [16:10] depends on the severity of the bug [16:10] which is probably not the case for much gnome-like stuff. [16:11] if fixing the bug requires implementing additional features or bumping up its deps, its most likely not going to get backported [16:13] dauggy: sorry, you were probably referring to the ubuntu package maintainer, not the upstream software maintainer (which is what I understood). i second KBar's response then. [16:14] hmm, I'm using linux for a few years now and still didn't come to appriciate how complex the development pipline is. This is a gnome extension which development is indepent from gnome, which is indepenent from ubuntu itself, but is still would need to file a bug with ubuntu for them to backport the fix, correct? [16:16] there should be some central entity for managing this sort of things === vxwarlock is now known as vx_wan [16:17]