[00:43] <rtpg> Upgraded to Ubuntu 22.04, and was wondering: is there no longer a keyboard shortcut to get the "search" thing in the activities pane? The keyboard shortcut I registered stopped working and I've been looking at the shortcuts trying to find it and failing
[02:15] <akp55> hey, i am trying to install some packages into my ubuntu, but it keeps saying that i have hash mismatches.  ive done the things from google about updating my sources.list and remove my /var/lib/apt list
[02:15] <akp55> but it still keeps failing and i cannot understand why
[02:16] <akp55> and i keep getting this W: GPG error: http://archive.ubuntu.com/ubuntu focal InRelease: The following signatures were invalid: BADSIG 3B4FE6ACC0B21F32 Ubuntu Archive Automatic Signing Key (2012) <ftpmaster@ubuntu.com>
[02:16] <leftyfb> akp55: ( cat /etc/os-release ; uname -a ; date ) | nc termbin.com 9999
[02:17] <sarnold> most of the time, hash sum mismatches come from ISPs doing some 'transparent proxying' -- you can almost always defeat that by switching to https mirrors -- I suggest looking through https://launchpad.net/ubuntu/+archivemirrors to find a mirror that offers https and is close enough to you that you can switch to it
[02:17] <akp55> leftyfb: https://termbin.com/97fa
[02:18] <leftyfb> akp55: maybe the way you have the networking setup for your VM?
[02:18] <akp55> ?  not sure why that would be an issue. its just bridged to the wifi network
[02:19] <akp55> never was an issue before.  i guess i can try to change the mode
[02:20] <akp55> uh huh.  i guess that was it
[02:20] <akp55> not really sure why that happened though
[02:35] <Linux> hello
[02:37] <Linux> hello
[02:37] <sarnold> wb
[02:37] <Crucifyy> wb
[03:53] <administrator_> hello
[03:53] <administrator_> anybody here
[03:53] <kostkon_> !anyone
[03:54] <administrator_> lunch time
[03:54] <administrator_> ?
[03:54] <administrator_> so quiet
[03:55] <administrator_> say sth.
[03:56] <Unit193> You have yet to actually ask an Ubuntu support question, so not much to say, administrator_.
[03:56] <administrator_> what the hell
[03:57] <administrator_> all die? haha
[06:10] <TheBigK> My optical drive is spinning up all the time... although its empty. https://paste.debian.net/1239980/ <- any idea about this?
[06:11] <TheBigK> i dont think the drive is broken... cause afaik it doesnt do it in windows...
[06:17] <Goose14> hello i've recently made partitions on my external hdd but it's not shown when i plug it in.. i used gparted how to fix this please
[06:54] <TheBigK> Goose14: are u sure u submitted it with gparted?
[06:55] <TheBigK> in gparted u need to do some sort of "run" command when u change the partitions
[06:55] <TheBigK> if u dont then it does nothing
[06:56] <Goose14> TheBigK , yes i did the apply changes buttun to write the changes, i've already the partitions i wanted on the disk but they don't show in my file manager or anywhere except for lsblk command
[06:56] <TheBigK> can u run fisk -l /dev/$URDEVICE
[06:56] <Goose14> i also ready this: if
[06:56] <Goose14>           Partition → Mount
[06:56] <Goose14>           is not visible, then gparted
[06:56] <Goose14>           does not know where the partition should be mounted
[06:56] <Goose14> but don't know if it's the problem
[06:57] <ducasse> Goose14: did you format them?
[06:57] <Goose14> ducasse yes
[06:57] <ducasse> partitions themselves won't show up, filesystems do
[06:58] <Goose14> 2 partitions with NTFS and one EXT4
[06:58] <ducasse> can you see them with lsblk?
[06:59] <Goose14> yes but in lsblk  at the end of the command it doesn't show any info under "fsavail" or " fuse" or " mountpoint" for those new 3 partitions
[07:00] <ducasse> they aren't mounted until they are selected in the file browser, afaik
[07:00] <Goose14> how to mount them in the file browser
[07:00] <ducasse> you can always mount them in fstab
[07:01] <ducasse> i don't use a file browser, but think they should just show up
[07:01] <descent3> how do i set the screen to sleep after longer? max is like 15 minutes
[07:01] <Goose14> in gparted there was no option to set a mount point or something like that
[07:02] <Goose14> i don't think they have a mountpoint
[07:02] <Goose14> they're just there
[07:02] <ducasse> if they don't have a set mountpoint the file manager should mount them under /media
[07:03] <ducasse> descent3: are you using wayland or x11?
[07:05] <ducasse> descent3: if you're on x11 you could try 'xset', it can set the timeout for both screen blank and dpms
[07:06] <descent2> ill figure it out, but they should make it longer like a 2 hour option. i want to leave my screensaver on for a bit
[07:07] <descent2> xscreensavers rss-glx coolness
[07:10] <descent2> i guess i could use x and just use the xscreensaver control panel. does the same thing i think
[07:10] <ducasse> descent2: try xset, 'xset s <timeout>' sets how many seconds before it blanks
[07:10] <descent2> ok cool
[07:10] <descent2> thanks
[07:10] <ducasse> doesn't work on wayland
[07:11] <descent2> ok
[07:12] <ducasse> if you give xset a second number, that is for the amount of time before it switches to another screensaver pattern/background
[07:35] <Diagon> How is it that on my 20.04 laptop, I have kernel 5.13, while on my two 20.04 KVM/QEMU VM's, the kernel is at 5.4?
[07:38] <alkisg> Diagon: read that one : https://wiki.ubuntu.com/Kernel/LTSEnablementStack
[08:22] <Goose14> hello, i've a partition on my hdd that's EXT4 fs - there's a folder inside named 'lost+found" taking about 10GB and i can't open it
[08:24] <Goose14> any idea what that might be?
[08:26] <ducasse> that is used by the filesystem, you can delete the files inside but keep the folder
[08:26] <ducasse> you need to be root to see the contents
[08:27] <ducasse> the files are from the fs trying to rescue files affected by errors
[08:27] <Goose14> ducasse, apparently there's nothing inside, but it still takes space
[08:28] <MonoL> Just did the update from 21.10 to 22.04
[08:28] <ducasse> i would leave it alone
[08:28] <MonoL> Took about half hour
[08:29] <Goose14> ok thanks
[08:30] <ducasse> Goose14: you can see if ls -la lists anything
[08:30] <Goose14> total 20
[08:30] <Goose14> drwx------ 2 root root 16384 May  5 00:53 .
[08:30] <Goose14> drwxr-xr-x 3 root root  4096 May  5 00:53 ..
[08:31] <ducasse> yeah, ignore those
[08:31] <Goose14> ok
[08:52] <eoli3n> Hi
[08:53] <eoli3n> I have an issue with ldap authentication on 22.04
[08:53] <eoli3n> that's really strange, because as root, I can su - ldapuser without problem
[08:53] <eoli3n> but if i try to connect with ssh or on lightdm, then the authentication fials
[08:53] <eoli3n> fails
[08:58] <Rumen> hi there
[08:59] <Rumen> getting non stop error in many apps it is:    Failed to load module "xapp-gtk3-module"
[08:59] <Rumen> Any idea how to fix that?
[09:00] <Rumen> This is after upgrade from Ubuntu 20.04 LTS to 22.04 LTS
[09:10] <eoli3n> when i run pam-auth-update, i don't see "ldap authentication"
[09:12] <timothy_> Hi, can files (nautilus) not connect to SMB2/SMB3 shares? Whenever I try to connect to my smb share on the nas (synology) it fails and the logs on the nas show nautilus is trying to connect with SMB1
[09:28] <naawb> hello, I updated to 22.04 LTS from 21.10 and now I dont have headphones sounds, but I do have speaker sounds... What should I do? I never use my screen speakers
[09:30] <naawb> just weird cus I was 2020- 2021 with no sounds, and they were finally fixed in 21.10, and now borken again on my laptop
[09:30] <naawb> Sadge
[09:33] <naawb> I can see headphones in settings menu, and the 'sound bar sound moving' but theres no output
[09:35] <jsetpal> hellooo
[09:35] <jsetpal> how is everyone doing this fine evening
[09:35] <naawb> bad my headphone sounds dont work after upgrade to 22.04
[09:36] <jsetpal> that's rough
[09:36] <jsetpal> your headphones specifically or bluetooth in general?
[09:37] <naawb> headphones. The sound bar is moving but there is no sounds - they worked before i upgrade djust now. Also speaker sounds from screen work
[09:38] <naawb> >left lul
[10:07] <ForeverNoob[m]> hello, I can see a package using `apt show <package>` on my Ubuntu 18.04 but I can't find it on https://packages.ubuntu.com/ - Is this expected?
[10:11] <tomreyn> ForeverNoob[m]: if it's not a package from ubuntu repositories, that's not unexpected
[10:12] <tomreyn> i.e. entirely normal if it's a package from an unofficial source (PPA or third party repository)
[10:13] <ForeverNoob[m]> tomreyn: does `apt show` tell me which repository it's from? I can't seem to find that information.
[10:13] <tomreyn> apt policy <package>    should
[10:13] <tomreyn> well, at least it says what is available and which version you have now
[10:14] <ForeverNoob[m]> hmm, doesn't really tell me where I installed it from though
[10:15] <ForeverNoob[m]> ah wait, I think it's a local package because `apt search <package>` is telling me `[installed,local]`
[10:16] <ForeverNoob[m]> still weird that apt fails to mention that in `apt show` or `apt policy` IMO
[10:16] <tomreyn> meaning it has no upgrade path, gets no security updates
[10:17] <tomreyn> apt does not track where a package was installed from (other than by log files)
[10:17] <ForeverNoob[m]> true, but it's a local app that doesn't connect to the network so it's somewhat safe.
[10:17] <ForeverNoob[m]> ah ok
[10:55] <cafe> hello
[11:04] <luna> hi
[11:08] <hiroot> hi
[11:21] <pycurious> My Machine just hangs - no keyboard - no screen movement. Nothing in the logs. If I reboot, everything works. It's a X570 Gigabyte MB X570. Any ideas on how to debug this?
[11:39] <lotuspsychje> pycurious: nothing in the logs is not possible, there's always something to look at
[11:39] <lotuspsychje> pycurious: sharing your dmesg in a pastebin would be good start
[11:42] <pycurious> https://dpaste.org/6kz3K - hope this helps?
[11:50] <BluesKaj> Hi all
[11:50] <lotuspsychje> pycurious: your dmesg looks pretty sane overall, just a few acpi issues i can see
[11:51] <lotuspsychje> pycurious: at wich point does things start freeze exactly?
[11:53] <pycurious> lotuspsychje: a few hours after the machine is booted up - typically when I am not in front of the desktop - it just hangs. The cpu fan is still spinning, the power on the gpus still looks like its on. The machine is dead - no ssh access, no keyboard, no monitor changes.
[11:54] <lotuspsychje> pycurious: can you leave a journalctl -f open and see what happens around freezing point?
[11:54] <lotuspsychje> pycurious: did you have this issue on this machine on other ubuntu releases/kernel(s) aswell?
[11:54] <pycurious> yes, i can - I somehow think, the power or the cpu just freezes, that is why the logs don't show anything. But I can try journalctl -f
[11:55] <pycurious> lotuspsychje: It was stable for the past month or so - till i added another graphics card. Could be the graphics card. But not sure.
[11:56] <lotuspsychje> pycurious: did you try switching nvidia drivers yet as a test?
[11:56] <pycurious> Driver Version: 510.60.02    CUDA Version: 11.6
[11:56] <pycurious> I've not
[11:57] <lotuspsychje> pycurious: ubuntu-drivers list
[11:58] <lotuspsychje> see what else you could try
[11:58] <pycurious> nvidia-driver-510-server, (kernel modules provided by linux-modules-nvidia-510-server-generic-hwe-20.04)
[11:58] <pycurious> nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04)
[11:59] <lotuspsychje> hmm
[11:59] <lotuspsychje> are you on desktop or server pycurious
[11:59] <neure> hi
[12:00] <pycurious> Desktop
[12:00] <neure> i need to downgrade from 20.04 to 18.04 and I was wondering if I can run the installer of 18.04 on running 20.04 or do I need to use an usb stick?
[12:56] <naawb> Is there some command to manually downgrade ubuntu? I just spent almost a year without sounds on 20-to21.04  which got fixed in 21.10 - and now i upgraded to 22.04 LTS and sounds are gone again on my headjack on my laptop xps 9700... I am just tired
[12:59] <lotuspsychje> naawb: you cant downgrade on ubuntu, try !backup your favorite ubuntu release/flavour
[12:59] <naawb> !backup
[13:00] <ioria> naawb, maybe this will help a bit : https://km.kkrach.de/p_dell_xps_17_9700/
[13:01] <naawb> ioria this was fixed for 21.10 its broken again
[13:01] <Maik> naawb: file a bug report
[13:02] <naawb> i did last time, it took a year for a fix, i dont have energy anymore, i will just downgrade or use windows
[13:03] <lotuspsychje> naawb: whats your old bug ID?
[13:03] <Maik> 21.10 will reach end of life in July, so installing that again will give you just a few months of support
[13:03] <naawb> 1912673
[13:04] <lotuspsychje> bug #1912673
[13:07] <lotuspsychje> naawb: keep in mind that you are also following the non lts route, installing 22.04 early might result in bugs here and there
[13:08] <naawb> ? thought it was officially released in Ubuntu 22.04 LTS on April 21, 2022
[13:09] <lotuspsychje> !ltsupgrade | naawb
[13:09] <lotuspsychje> naawb: its your choice to choose LTS or non-LTS route
[13:11] <naawb> I am not sure what you mean, i just choose 22.04 LTS from your website. Reason I started updating from 20.04 was because sounds didnt work
[13:11] <naawb> and people were saying it was fixed in a more up-to-date kernel
[13:12] <lotuspsychje> naawb: did you also test a clean install 22.04 to test that?
[13:12] <naawb> no i upgraded from 21.10 when it asked me to
[13:15] <naawb> I am just sad because i dont even have a weird laptop, its literally a dell xps, not CoolDYILappie, and basic thing like headphone sounds just dont work
[13:17] <jluc> maybe you can use some bluetooth device ?
[13:42] <ice9> I'm getting "Although GNOME Shell integration extension is running, native host connector is not detected" in the browser however the host connector is installed.
[14:58] <enigma9o7[m]> naawb, if I were you, i'd boot the 22.04 iso and see if sound works.  That way you'd know it's a configuration issue on your side.
[14:58] <enigma9o7[m]> Or, you'd know its a problem with ubuntu.
[15:30] <transhumanist> at config* | grep -i "CONFIG_ANDROID_BINDER_DEVICES"                        CONFIG_ANDROID_BINDER_DEVICES=""    is it no longer compiling binderfs and binder and ashmem support in ubuntu kernel?
[15:34] <transhumanist> I have kernel version 5.15.0-27-generic
[15:40] <enigma9o7[m]> Those modules are included with the default ubuntu kernel since like 5.4 or earlier including that version.... what is your question?
[15:41] <enigma9o7[m]> If yer trying to get waydroid working, good luck with that, I had it working on focal and impish (and bullseye) but cant get it working on jammy yet.
[15:42] <transhumanist> the config seems to show that its not enabled, or am I missreasding it?
[15:44] <transhumanist> the modules are not apparently loaded in to the kernel. I think this would explain why I cant do a sudo mkdir /dev/binder && sudo mount -t binder binder /dev/binderfs
[15:44] <transhumanist> ls -1 /dev/binderfs does show up , but /dev/binder does not while /dev/ashmem does show up
[15:45] <transhumanist> in addition it doesnt appear binder is in the /etc/modules
[15:45] <transhumanist> sudo modprobe binder modprobe: FATAL: Module binder not found in directory /lib/modules/5.15.0-27-generic
[15:50] <Jeremy31> transhumanist: https://askubuntu.com/a/1268069/300665
[15:59] <enigma9o7[m]> /lib/modules/5.15.0.27-generic/kernel/drivers/android/binder_linux.ko
[16:02] <scanno> Hmm why does firefox and Ubuntu software all of a sudden have a brown titlebar on Ubuntu 22.04? It was grey before.
[16:02] <enigma9o7[m]> That message you linked jermey is about ubuntu before 20.04.  Starting with 20.04 ashmem and binder were included in ubuntu kernel.
[16:06] <Jeremy31> enigma9o7[m]: The actual question was about Ubuntu 20.04
[16:07] <enigma9o7[m]> ya my bad i just looked breifly at what popped up and though tit was saying 19.10 or something
[16:08] <ogra> it was 19.10 (the anbox documentatio clearly says that)
[16:09] <ogra> (when the modules were introduced upstream)
[16:13] <Goose14> should i encrypt a partition on external HDD with luks or veracrypt better? i will only use linux
[16:16] <matsaman> despite veracrypt being maintained, compared to truecrypt, I don't think it was ever "fixed" to be actually worth using
[16:20] <matsaman> whatever you might use on your internal storage should be fine for linux only
[16:20] <matsaman> just keep in mind that other OSes like to ask users if they want to wipe out things they don't recognize
[16:21] <Goose14> ok thank you matsaman
[16:26] <transhumanist> Jeremy31: unfortunately the last link on that page says that the directory doesn't exist,if I create it binder still cant bind to it
[16:26] <transhumanist> ls -1 /dev/binder doesnt even show it
[16:26] <Jeremy31> ls -1 or ls -l
[16:28] <Jeremy31> transhumanist: mount -t binder binder /dev/binderfs
[16:35] <transhumanist> it works but ls -1 /dev/binder still shows nothing
[16:40]  * enigma9o7[m] uploaded an image: (583KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/aidvcNQViyXwzAuSONdWDNSk/Screenshot%20from%202022-05-05%2009-39-57.png >
[16:41] <Jeremy31> ls -l #small L not the number 1
[16:42] <Jeremy31> Might not matter
[16:44] <transhumanist> I got it working! https://bpa.st/FLMQ
[16:46] <shrooman> Hello, I mounted an extra partition in my fstab but I cannot modify the files unless I am root. How do I modify the mounted partition's permissions?
[16:50] <shrooman> hello?
[16:54] <Goose14> i've formatted a usb with ext4 but i can't copy files or create anything inside it
[16:57] <mnazwm> Goose14: dont be afraid to populate a virgin partition with files
[16:58] <Goose14> mnazwm  i don't know why i can't write on the usb space
[16:59] <abivado> goose14:you propably formated it as admin.
[16:59] <Goose14> yes i used sudo
[16:59] <leftyfb> Goose14: what filesystem did you format it as?
[16:59] <Goose14> Ext4
[16:59] <abivado> you need chmod 755
[16:59] <leftyfb> abivado: it doesn't matter what privs you format a drive as
[17:00] <leftyfb> Goose14: you need to set the perms in the fstab entry and make sure the location it's mounted on has the permissions you want
[17:00] <abivado> it has to user rights.
[17:00] <abivado> have
[17:00] <leftyfb> Goose14: https://help.ubuntu.com/community/Fstab
[17:02] <shrooman> how do I add permission so that a non root user can modify or delete files in a mounted filesystem?
[17:02] <leftyfb> shrooman: https://help.ubuntu.com/community/Fstab
[17:03] <shrooman> its already mounted in my fstab, maybe what options would help
[17:04] <leftyfb> shrooman: you need to verify that it's fstab entry is correct for the permissions you want. Also make sure the mount point has the permissions you want
[17:04] <leftyfb> shrooman: please read the wiki page I gave you to understand the right permissions and how to modify the fstab entry and remount
[17:05] <shrooman> user option?
[17:05] <transhumanist> shrooman:  https://help.ubuntu.com/community/InstallingANewHardDrive I think this may help youi the rw, nosuid, no dev lines...
[17:06] <transhumanist> been a very long time since i had this issue so i am very vague on the solution details... sory
[17:07] <shrooman> currently just using noatime options, Ill try some of these out
[17:08] <shrooman> usually works in Gentoo
[17:08] <leftyfb> shrooman: fstab is going to work exactly the same across all linux distributions
[17:14] <shrooman> still have to be root to modify the mounted partition's files noatime,rw,nosuid,nodev    are my opts in my fstab.
[17:17] <transhumanist> shrooman:   /dev/sda5 on /media/mynewdrive type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)
[17:18] <transhumanist> I think its the uid and umask that allow it but sorry Its been way too long , I dont remember
[17:18] <transhumanist> shrooman: https://askubuntu.com/questions/43570/change-owner-of-internal-hard-drive-partition-from-root-to-user
[17:18] <shrooman> Thank you, transhumanist I will try those out
[17:25] <nshirelaptop> I don't know what happened between 20.04 and 22.04, but wow 22 is so snappy and responsive
[17:25] <nshirelaptop> compliments to the chef
[17:25] <shrooman> still cant modify that filesystem
[17:25] <Elliria> I noticed that, too, nshirelaptop, and the colors are WAY more vivid.
[17:26] <Crucifyy> im loving it too
[17:26] <Crucifyy> althought im still getting weird hangs when i launch some apps
[17:26] <shrooman> I think I belong in gentoo... idk this kinda sucks
[17:27] <nshirelaptop> ^lo
[17:27] <nshirelaptop> lol
[17:27] <Crucifyy> *waves*
[17:58] <h1pot> i've switched the stable track of firefox snap to beta, but once i reverted to stable, i am unable to use my old profile, how can i restore my data?
[17:59] <enigma9o7[m]> copy it from the old profile into the new profile, overwriting.
[17:59] <enigma9o7[m]> but using it on an older version is not always safe
[18:08] <h1pot> enigma9o7[m]: firefox prompt me to create a new profile whenever i try to do this
[18:28] <cambrian_invader> why does this code give a warning with godbolt's gcc 9.4 but not mine (9.4.0-1ubuntu1~20.04.1)? https://godbolt.org/z/fnaGKvTMr
[18:29] <cambrian_invader> echo "int f(void) { int x = x; return x; }" > test.c && gcc -Wall -c test.c # no warning
[18:39] <EriC^^> cambrian_invader: different version or the compiler was compiled with different options for ubuntu
[18:40] <cambrian_invader> if the "source package"
[18:40] <cambrian_invader> link goes to salsa does that mean ubuntu is using debian's sources directly?
[18:41] <EriC^^> no idea
[18:41] <EriC^^> what link?
[18:41] <cambrian_invader> the source package repo at the bottom of https://packages.ubuntu.com/source/focal/gcc-defaults
[18:43] <cambrian_invader> although I guess the source package is actually gcc-9
[19:09] <Elon_Satoshi> Can Ubuntu be installed so that the user has to set up their own username and password on the first startup?
[19:09] <EriC^^> Elon_Satoshi: yeah, i think that's what the OEM install option does
[19:11] <leftyfb> Elon_Satoshi: https://help.ubuntu.com/community/Ubuntu_OEM_Installer_Overview
[19:11] <Elon_Satoshi> Ah cool thanks
[19:32] <bertieb> Hi, how would I figure out why grub seems to have installed itself in legacy mode (looking for a missing 'i386-pc/normal.mod' when x86_64-efi dir is present in /boot/grub) ? Context is an install from live mode on a wyse7020 in UEFI boot mode. Cheers!
[19:33] <bertieb> (22.04)
[19:33] <EriC^^> bertieb: grub lately has been installing ive noticed in both modes since 20.04 or so, remove 'grub-pc' package and it should remove the legacy mode
[19:35] <bertieb> EriC^^: ah, thanks for the clue! can that be done by booting 22.04 live and chrooting into the existing install to remove the package?
[19:35] <EriC^^> bertieb: install grub-efi-amd64 , seems grub-pc 'conflicts' with that package
[19:35] <EriC^^> bertieb: yes sure
[19:35] <bertieb> fab, thank you :) will give that a go just now
[19:36] <EriC^^> no problem :)
[19:38] <bertieb> (it'll take a wee bit to redownlaod the live image via PXE netboot, will report back to close the loop when done)
[19:39] <EriC^^> alright
[19:40] <EriC^^> bertieb: it sounds like it's booting in legacy mode? the actual bios?
[19:50] <bertieb> EriC^^: the actual BIOS has 3 modes- legacy, mixed and UEFI; it was (and is) set to UEFI
[19:50] <EriC^^> bertieb: interesting
[19:51] <bertieb> EriC^^: I had to futz around with modes and recompile pixiecore (due to this bug: https://github.com/danderson/netboot/issues/131) to get netboot.xyz to boot in UEFI mode
[19:52] <bertieb> I mention this as figuring that out -- again, I came across that bug last year -- took more time than I am proud to admit ;-P
[19:52] <EriC^^> i find it very odd how it would look for normal.mod, i think it should load grub.efi from there it should be hard-coded to search for the efi/normal.mod
[19:52] <jhutchins> Just like a BIOS, UEFI can be implemented over a pretty broad range of standards,
[19:52] <EriC^^> when are you getting the i386/normal.mod error? grub booting or the apt/grub stuff?
[19:53] <bertieb> EriC^^: I get a grub rescue mode screen with the i386-pc error
[19:53] <EriC^^> bertieb: when you're in the chroot and have the efi partition mounted, look at /boot/efi/efi/ubuntu/grub.cfg and please paste the prefix part
[19:54] <EriC^^> that is what tells it where normal and the modules are
[19:54] <bertieb> sure thing
[19:54] <soloslinger> Is there a more powerful version of holding a package?  I'm usking dpkg --set-selections, but apt still wants to do minor upgrades.
[19:55] <bertieb> as for what jhutchins says about UEFI, it's possible there's an issue with the implementation; I also have a wyse 3040 which uses the fallback location
[19:56] <EriC^^> soloslinger: maybe apt-mark hold <package> ?
[19:58] <EriC^^> !pin | soloslinger there's also this
[20:00] <bertieb> EriC^^: in the EFI partition, EFI/ubuntu/grub.cfg: set prefix=($root)'/boot/grub'
[20:00] <jhutchins> Shades of the 20th century!
[20:00] <soloslinger> EriC^^: Both commands seem to do the same thing.
[20:01] <soloslinger> ubottu: Pinning as per that article is trying to bring packages in from, for example, I have an 18.04 system but I want packages from 20.04.  Or am I reading that wrong?
[20:02] <soloslinger> Basically, I don't want apt to touch my postgresql install, including  minor versions.  I would be surprised if I'm the only person who has this desire.
[20:02] <murmel> soloslinger you can do that with pinning but it's really not recommended. you can just set the priority to a negative number so it never gets installed/upgraded
[20:02] <bertieb> (also, the install seems to already have grub-efi-amd64-bin installed already -_-)
[20:03] <EriC^^> bertieb: i think it's booting in legacy mode still, somehow
[20:03] <murmel> soloslinger why don't you want security updates oO
[20:03] <EriC^^> bertieb: anyways when you chroot, run 'grub-install && update-grub' just to reinstall everything
[20:03] <bertieb> EriC^^: there's a way to check that, right? ISTR something along the lines of being able to check efivars if booted in non-legacy mode
[20:04] <EriC^^> yeah, "ls /sys/firmware/efi" should show it
[20:05] <bertieb> thanks :)
[20:05] <bertieb> yeah that's populated !
[20:05] <EriC^^> sounds good
[20:06] <bertieb> I'll give grub a reinstall and see what happens
[20:08] <soloslinger> murmel: I don't want my automation to haphazardly update by databases in production?  I would be very surprised to learn if the bulk of the Linux community just "YOLO! SHIP IT!" when it comes to their database instances?
[20:08] <bertieb> it, er, wants to install for i386-pc platform (?!) so I've specified --target=x86_64-efi
[20:08] <EriC^^> bertieb: ah
[20:08] <EriC^^> bertieb: did you remove grub-pc and grub-pc-bin?
[20:09] <murmel> soloslinger idk, but i have always at least 1 mirror db, or backup before upgrading security updates
[20:09] <bertieb> EriC^^: I... did not! Give me a mo, apt's complaining that doing so will cause unmet dependencies
[20:09] <EriC^^> try apt-get install grub-efi-amd64 grub-pc- -grub-pc-bin-
[20:09] <EriC^^> er
[20:10] <EriC^^> try apt-get install grub-efi-amd64 grub-pc- grub-pc-bin-
[20:10] <bertieb> EriC^^: will give that a try, thanks
[20:11] <EriC^^> np
[20:12] <bertieb> before I do tho I may have forgotten to do the ancillary mounts (sys, proc etc) for a chroot, so Ill back out and mount those
[20:12] <soloslinger> murmel: Sure.  The devops practice is to have the automation run regularly, as to guarantee state.  If I run that 20 times a day, or add other things into this application stack, I'm either going to update the mirror at the same time causing the same problem, or I'm still risking data loss between the backup time and the upgrade.
[20:12] <bertieb> (I'm wondernig if grub-install couldn't 'see' the EFI stuff in sys so figured it was in legacy mode)
[20:13] <EriC^^> bertieb: nah, grub will get confused if both grub-pc and grub-efi are there, afai noticed
[20:13] <murmel66> soloslinger why would you ever upgrade them at the same time oO
[20:13] <EriC^^> bertieb: try 'ls /sys /proc /dev' in the chroot
[20:14] <bertieb> EriC^^: that should work... now that I've actually mounted them :D
[20:14] <soloslinger> murmel66: I'm getting the impression your use cases don't involve as much automation as mine do.
[20:14] <EriC^^> bertieb: ah ok :D
[20:14] <murmel66> it does? i just have it set up that those upgrades run at different times
[20:14] <murmel66> soloslinger ^
[20:16] <bertieb> EriC^^: er, it's complaining about causing an an unmet dep with shim-signed; which appears to be Secure Boot-related
[20:16] <bertieb> I don't think I want Secure Boot (?)
[20:17] <bertieb> it = apt, when told to remove grub-pc grub-pc-bin
[20:17] <EriC^^> bertieb: try 'mokutil --sb-state'
[20:18] <bertieb> reports disabled
[20:18] <Jeremy31> Must be booted in EFI mode
[20:18] <bertieb> can I remove the SB shim in that case?
[20:18] <EriC^^> bertieb: yeah, im not sure what that package is really
[20:19] <Jeremy31> It is the signed element of grub IIRC
[20:19] <bertieb> lol, "E: removing essential system-critical packages is not permitted. This might break the system."
[20:20] <sarnold> "I'm sorry Linus, I can't let you do that"
[20:20] <Jeremy31> Likely a dependency of grub
[20:20] <EriC^^> bertieb: hmm, what does 'apt-get install grub-efi-amd64' do?
[20:20] <alkisg> bertieb: remember to mount the efi partition in the chroot/boot/efi as well
[20:20] <bertieb> alkisg: good shout, but it already is
[20:20] <alkisg> Also, apt install shim-signed will install grub efi and work with or without secure boot, so it's usually a good idea
[20:20] <EriC^^> bertieb: actually i have the same situation on my own pc i just noticed, both grub-pc and efi, going to remove here as well
[20:21] <bertieb> EriC^^: sure, good luck :)
[20:21] <jhutchins> Jeremy31: Signed files are related to "Secure Boot".
[20:21] <alkisg> I have grub-pc and grub-efi on purpose, because I want to be able to boot the disk in either mode
[20:21] <alkisg> It's been working fine since 18.04 when I first did that
[20:22] <bertieb> I might give this a quick try at booting since I was able to grub-install with  --target x86_64-efi
[20:22] <EriC^^> bertieb: got it removed, it did kind of almost trip
[20:22] <bertieb> can always come back and try removing grub-pc* if that still tries to load i386-pc stuff
[20:23] <bertieb> (when I first installed 22.04, it was booting straight to memtest86+, so a grub rescue shell is kinda sorta an improvement..?)
[20:23] <EriC^^> bertieb: i installed grub-efi-amd64 and it removed by itself grub-pc but whined abit, then i removed grub-pc-bin
[20:24] <bertieb> EriC^^: see, it just complains about not having an installation candidate for me
[20:24] <EriC^^> bertieb: hmm if it was booting memtest then you were using legacy not uefi
[20:25] <bertieb> EriC^^: yup, that was before I switched it over to UEFI
[20:25] <EriC^^> oh ok
[20:25] <alkisg> It's gpt, not mbr, right?
[20:26] <bertieb> alkisg: ohhh
[20:26] <bertieb> partition table: msdos
[20:26] <EriC^^> not a problem
[20:26] <Jeremy31> If it is GPT you would need a bios_grub partition to run BIOS/CSM/Legacy
[20:27] <bertieb> ah
[20:27] <EriC^^> bertieb: what's it looking when you do 'efibootmgr -v' ?
[20:28] <EriC^^> bertieb: btw you can upload output easily by doing "command here..... | nc termbin.com 9999"
[20:28] <EriC^^> it'll paste it for you and give a link back
[20:28] <bertieb> EriC^^: reasonably sane, I can paste
[20:28] <bertieb> ah nice
[20:29] <bertieb> ubuntu is in there as the default
[20:29] <EriC^^> ok sounds good
[20:29] <bertieb> I think, it has an asterisk by its entry
[20:29] <EriC^^> well as long as it's there, asterisk means its active
[20:29] <bertieb> ah right, right
[20:30] <EriC^^> honestly i'd try to reinstall grub, and boot, btw if you get a rescue shell again, try to continue booting the thing
[20:31] <EriC^^> do "set prefix=(hdx,msdosY)/boot/grub"
[20:31] <bertieb> EriC^^: good suggestion- I did try to insmod normal, but it would prepent the i386-pc dir, regardless of what I set the prefix to
[20:31] <EriC^^> where hdx,msdosY is your root partition if you dont have a /boot partition
[20:31] <bertieb> yup! rescue mode shell is painful to use without tab completion and scrollback/history
[20:31] <EriC^^> then do "insmod normal"
[20:32] <EriC^^> it should load the menu, "configfile $prefix/grub.cfg" loads the menu if it doesnt by itself
[20:32] <bertieb> yeah, as before- trying to get normal.mod from i386-pc/
[20:32] <EriC^^> bertieb: in grub did you try "ls -l" ?
[20:33] <EriC^^> i think ls -l only works in uefi grub
[20:33] <bertieb> ls works, ls -l does not
[20:33] <EriC^^> not sure though
[20:33] <EriC^^> aha
[20:33] <EriC^^> i think it has to be booted in legacy mode
[20:33] <bertieb> but why is it loading legacy grub, if it's been given x86_64-efi as a target?!
[20:34] <bertieb> sure, will try
[20:34] <EriC^^> no
[20:34] <EriC^^> i mean it's currently being booted in legacy mode
[20:34] <alkisg> Try F12 while your computer boots, to invoke the boot manager
[20:34] <EriC^^> good idea alkisg
[20:34] <EriC^^> choose the ubuntu entry
[20:34] <alkisg> You should see your disk twice; once for uefi and once for legacy mode
[20:34] <alkisg> Right, ubuntu is the uefi one
[20:35] <bertieb> that entry appears to do nothing
[20:35] <bertieb> I'll need to disable other options to see why
[20:35] <bertieb> as it goes straight to PXE otherwise
[20:35] <EriC^^> hmm i think there's an issue with it somehow
[20:36] <bertieb> oh yeah!
[20:36] <bertieb> yeah, it doesn't seem to print anything
[20:36] <alkisg> Is this a newly formatted disk/OS? If so, wouldn't it be a lot easier and better to switch to GPT and have grub properly installed from the installer etc etc?
[20:36] <bertieb> just immediately returns to boot menu
[20:36] <EriC^^> bertieb: boot the live usb to troubleshoot
[20:37] <bertieb> alkisg: funnily enough, this disk had ubuntu (20/21.x) on it beforehand, which I blew away to install 22.04 :D
[20:37] <alkisg> And the MBR+UEFI combination confused the installer and possibly even some grub packages, not just ubiquity; so why not make things easier...
[20:38] <bertieb> alkisg: to be honest, I was happy to let the installer do whatever it wanted to the disk
[20:38] <alkisg> It was preformatted in mbr mode though, right?
[20:38] <bertieb> possibly! I didn't check before I blew away the previous ubuntu
[20:39] <EriC^^> alkisg: i think ubiquity is just stupid these days
[20:39] <EriC^^> i installed 20.04 recently, gpt partition, i also had grub-pc with grub-efi installed
[20:39] <EriC^^> i noticed so many people recently who came had both packages
[20:40] <alkisg> I completely agree with that; I can't make 22.04 NOT complain about a missing EFI partition when I'm installing in the usual ancient MBR+BIOS mode :/
[20:40] <bertieb> I didn't get a complaint, fwiw
[20:40] <alkisg> But for teachers here, I advice them to avoid the weird combinations (MBR+UEFI or GPT+BIOS), so that they avoid the worse bugs/issues
[20:41] <alkisg> bertieb: because it created an efi partition while in mbr more :D
[20:41] <bertieb> I'm happy to reinstall, doing <whatever> to the disk
[20:42] <bertieb> heck, I'll format with reiserfs if it makes grub happy ;-P
[20:42] <alkisg> bertieb: suppose that you want to dual-boot windows later on; you won't be able to do that with MBR+UEFI. So personally I'd go for live cd => gparted => create gpt partition table => then run the installer once more
[20:42] <alkisg> Either that, or I'd actually switch to MBR+BIOS, not MBR+UEFI
[20:42] <bertieb> alkisg: fair dos- I'll format as gtp
[20:43] <alkisg> 👍️
[20:43] <bertieb> this is going to be a glorified thin client anyway, and I'm not letting Windows anywher near it
[20:44] <EriC^^> bertieb: it might help to also copy over the grub files to the standard locations for windows, some uefi need to be tricked
[20:44] <EriC^^> basically you cp /boot/efi/efi/ubuntu/grubx64.efi /boot/efi/efi/microsoft/boot/bootmgfw.efi
[20:45] <EriC^^> also so cp grubx64.efi to /boot/efi/efi/boot/bootx64.efi
[20:45] <bertieb> EriC^^: ah, the fallback location?
[20:45] <EriC^^> yeah
[20:46] <bertieb> I think --removable flag to grub-install installs it to the fallback dir
[20:46] <EriC^^> yup that's true
[20:47] <bertieb> I'll be irked and amused if that's the issue here
[20:47] <EriC^^> could be, maybe it's not liking that entry and just saying no
[20:47] <bertieb> given I ran into that very issue with it's younger brother, a Wyse 3040 (https://blog.roberthallam.org/2020/05/psa-dell-wyse-3040-uses-fallback-efi-location/)
[20:47] <EriC^^> if grub.efi is there, and the ptuuid is right and its in the partition it should load it
[20:47] <bertieb> (disclosre, that me)
[20:48] <EriC^^> aha
[20:48] <bertieb> if it is that, I'll be doing another PSA
[20:48] <EriC^^> my money's on that, it's unlikely grub-install messed up the entry or something
[20:48] <bertieb> right, I'll test that before I blow away this install for GTP
[20:48] <bertieb> *GPT
[20:50] <EriC^^> bertieb: my laptop also does it, need to disable the microsoft entry in efibootmgr to get it to work
[20:50] <EriC^^> did you see one in yours btw?
[20:50] <EriC^^> called 'windows boot manager'
[20:50] <bertieb> EriC^^: aye there was something similar but I have it disabled
[20:50] <EriC^^> oh
[20:51] <murmel> EriC^^ which brand is it? so I can avoid it :)
[20:51] <alkisg> My lenovo laptop forgets that ubuntu is my default uefi entry, whenever I insert a bootable usb stick. So when I remove the stick, it's booting the windows boot manager instead of grub :/
[20:52] <EriC^^> murmel: heh it's like almost all laptops :D this is an hp though
[20:52] <murmel> alkisg did you try to disable the windows boot manager entry?
[20:52] <murmel> EriC^^ great :)  didn't like them either way
[20:52] <bertieb> HP does seem to be a marmite brand
[20:53] <alkisg> murmel: good thought, no I didn't try that, I'll try it next time (I've given it to my wife because I also didn't like that I had to press Fn to activate the Fx keys)
[20:53] <EriC^^> alkisg: you can change the fn thing in the bios i think
[20:54] <bertieb> --removable is all I need for fallback path, rigght?
[20:54] <murmel> alkisg i had to do it that way on my asrock board (though that was on a board from 2010)
[20:54] <EriC^^> bertieb: yeah, i'd also cp to /boot/efi/efi/microsoft/boot/bootmgfw.efi just in case
[20:55] <bertieb> EriC^^: I didn't try that but using fallback was to no avail
[20:55] <alkisg> EriC^^: unfortunately this lenovo bios doesn't have that option; i've seen it in other laptops though
[20:55] <EriC^^> ah
[20:55] <bertieb> I'll just do the gpt dance alkisg suggested, the reinstall time will give me the chance to quickly grab a bite of dinner :)
[20:56] <EriC^^> sounds good
[20:56] <Jeremy31> Sounds like my cheap gateway, I have to press FN + F5 to refresh
[20:56] <murmel> bertieb how fast are you with your dinner then? xD
[20:57] <bertieb> murmel: hehe, probably unhealthily so :D
[20:57] <bertieb> inhale the food, optionally pause to chew
[20:57] <bertieb> you know
[20:58] <murmel> ahh, sounds like something soft to eat then
[20:58] <bertieb> pasta, so yes! 10 points to murmel
[21:00] <bertieb> at this rate I'll be done before the livecd redownloads (again)... I should have just made a USB
[21:17] <execci> hi
[21:21] <bertieb> Well, after formatting to gpt and reinstalling, it's now... booting straight into bios setup screen
[21:21] <bertieb> I'm not sure how that's even possible
[21:22] <EriC^^> why not use the pc in legacy mode btw?
[21:22] <bertieb> that would only boot memtest86+
[21:22] <EriC^^> hmm what would happen when you tried booting ubuntu?
[21:23] <bertieb> how do you mean?
[21:23] <bertieb> it booted straight to memtest
[21:23] <bertieb> no grub, nothing else
[21:23] <EriC^^> odd
[21:23] <bertieb> extremely!
[21:23] <Jeremy31> bertieb: any BIOS option to boot an EFI file?
[21:23] <bertieb> Jeremy31: not that I saw but will double check
[21:24] <EriC^^> bertieb: long shot but sometimes some bios give extra options when you set an admin password
[21:24] <bertieb> EriC^^: this has an admin password by default :)
[21:24] <bertieb> Jeremy31: I don't see anything about booting an EFI file
[21:24] <Jeremy31> bertieb: What machine?
[21:25] <bertieb> Jeremy31: Wyse 7020
[21:25] <bertieb> I have another Wyse that doesn't honour EFI boot 'suggestions'
[21:25] <EriC^^> bertieb: when it was booting straight to memtest, by any chance did you see if you had a bootflag option on any partition?
[21:25] <EriC^^> it might have just ignored booting the disk if it didnt see any bootflag
[21:26] <murmel> hm, sounds like it's locked to windows boot manager?
[21:26] <bertieb> I think my next plan of attack now is to try fallback + windows efi boot location (that EriC^^  suggested)
[21:26] <bertieb> No idea- if I select PXE it boots; if I try ubuntu or anything else it chucks me to BIOS password
[21:26] <EriC^^> i find it very odd it didnt boot grub in the mbr even and went to its own memtest
[21:26] <bertieb> *BIOS setup (password prompt)
[21:27] <bertieb> yup, there's something very strange going on here; would love to be able to peer under the hood as to what its doing
[21:27] <EriC^^> bertieb: this makes me think that earlier it was booting in legacy mode, and now since you have gpt+efi only it's doing this
[21:28] <bertieb> EriC^^: it would  complain about the miissing normal.mod in mixed mode
[21:28] <EriC^^> bertieb: although, the fact that you got grub is nice, about not finding normal it could be that it somehow wasnt being able to read the disk and find normal.mod cause i assume you did have the i386-pc/normal.mod in /boot/grub/... right?
[21:29] <bertieb> no, that wasn't in the directory tree; just the x86_64-efi/ dir
[21:29] <EriC^^> aha
[21:29] <EriC^^> well that's good then
[21:30] <EriC^^> try i guess to boot a live usb, copy the fallback dir and microsoft, and also share the output of efibootmgr
[21:31] <bertieb> Sure, I'll give that a try in a bit; need to hit my head against something else for a little bit
[21:31] <bertieb> I'll report back when I do
[21:31] <bertieb> regardless of how it all turns out I want to say thanks for the help so far, it's much appreciated and y'all are real friendly :)
[21:31] <EriC^^> no problem :)
[21:32] <memphisto> is the BIOS password "Fireport" ?
[21:34] <soloslinger> I don't suppose anyone can decipher Held packages were changed and -y was used without --allow-change-held-packages for me?
[21:44] <enigma9o7[m]> just repeat the commadn without -y and see what its asking about
[22:03] <Maximalist> is there a channel for icecat?
[22:15] <leftyfb> !alis | Maximalist
[22:16] <leftyfb> maccam94[m]: https://www.omgubuntu.co.uk/2022/05/firefox-100-available-to-download
[22:58] <corba> Hi, I'm having issues with kodi crashing on 22.04
[22:59] <corba> context.c:56: warning: mpd_setminalloc: ignoring request to set MPD_MINALLOC a second time
[23:00] <corba> anyone can help? already tried searching online
[23:02] <sarnold> corba: that one line in isolation feels unlikely to be the actual problem
[23:02] <sarnold> corba: did you get a core dump or similar from it?
[23:03] <corba> yes
[23:03] <corba> libva info: VA-API version 1.14.0
[23:03] <corba> libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
[23:03] <corba> libva info: Found init function __vaDriverInit_1_14
[23:03] <corba> libva info: va_openDriver() returns 0
[23:03] <corba> context.c:56: warning: mpd_setminalloc: ignoring request to set MPD_MINALLOC a second time
[23:03] <corba> Segmentation fault (core dumped)
[23:06] <sarnold> drone *always* beats me by a few secvonds.. heh
[23:06] <sarnold> corba: I suggest running gdb on the core file, run 'bt', see if you can get a stack trace..
[23:09] <corba> Thank you
[23:13] <corba> This is the crashlog: https://pastebin.com/88kVuHs6
[23:14] <sarnold> woot
[23:14] <wez> .o/
[23:18] <sarnold> corba: dang :( it's all deep magic or normal-enough looking stuff..
[23:18] <sarnold> corba: the only thing I could see was: 2022-05-05 17:08:48.437 T:26522   ERROR <CSettingInt>: unknown options filler "libinputkeyboardlayout" of "input.libinputkeyboardlayout"
[23:19] <sarnold> corba: it feels pretty unlikely that this was related, too, but checking your configuration to see if there's anything like this that ought to be different..
[23:20] <sarnold> corba: if that doesn't sound right, then probably best to 'ubuntu-bug kodi' (or whatever the package name is) and get a bug filed..
[23:20] <corba> okay thank you
[23:57] <noarb> Is there a place to look at how the defaults are chosen when installing ubuntu on an LVM drive? I think it allocates 50% initially. I want to use the whole disk while keeping enough space for snapshots