[00:36] <rjft197> I had to boot my dual boot laptop into windows to recover my sons iPad the other day.  When I tried to reboot back to ubuntu grub didn't appear instead it went to a grub minimal recovery screen or something.  I've done a bit of searching around google and have tried some things but I'm way out of my comfort zone would this be a good place to ask?
[00:36] <rjft197> I have managed to boot it with a live USB drive, but I haven't been able to use any of the things i've found on Google to help out.
[00:36] <signofzeta> not sure about that one.  When you reboot into Linux, have you done a `sudo update-grub`?
[00:36] <rjft197> GNU BRUB version 2.06
[00:36] <rjft197> Minimal BASH-like line editing is supported....
[00:37] <rjft197> that's what i see on  boot up.  Just booting it into ubuntu now to retry the update-grub command.  I have tried it can't recall what it said
[00:39] <signofzeta> cool, let us know what it says:  sudo update-grub | nc termbin.com 9999
[00:40] <signofzeta> I bet Windows overrode your UEFI boot selections or something
[00:42] <rjft197> \/usr\/sbin\/grub-probe: error: failed to get canconical path of '\/cow'.
[00:43] <rjft197> hmmm had to add the \s in there to make it show
[00:43] <signofzeta>  /cow? That's a new path.
[00:43] <rjft197> I don't recall that error searching for that one now.
[00:43] <signofzeta> (yeah, IRC commands start with a slash)
[00:43] <rjft197> yup that's what it says
[00:44] <sarnold> /cow sounds a bit like the live boot environment
[00:44] <signofzeta> Oh, you're booted from a different Linux system, that's why.
[00:44] <signofzeta> (cow = copy-on-write, aka, your rootfs is read only)
[00:45] <rjft197> That sounds right.  I can only booth the live environment
[00:45] <signofzeta> Can you mount your /boot partition?
[00:46] <signofzeta> Also, is this UEFI or BIOS/CSM?
[00:46] <rjft197> UEFI (I think)
[00:46] <signofzeta> Try this: https://www.ubuntupit.com/how-to-repair-the-grub-bootloader-using-a-ubuntu-live-usb-drive/
[00:46] <signofzeta> Use the flash drive's rescue mode
[00:49] <waltman> Hi. I just ran `sudo apt update; sudo apt upgrade`. There were a bunch of xorg and nvidia driver updates. It seemed to be fine, but a few minutes later my desktop froze. I can still move the mouse, but the desktop is unresponsive. The Xorg app is taking 100% of my CPU. Is there any way I can restart X without rebooting?
[00:49] <waltman> I'm ssh'd in from my laptop.
[00:50] <signofzeta> waltman: can you tell if apt is still running in the background?  Killing X or Wayland would likely take out apt as well.
[00:51] <oerheks> after tose updates you would need to reboot, IIRC
[00:51] <waltman> Xorg is still running
[00:51] <waltman> apt finished maybe 10-15 minutes before this happened.
[00:52] <signofzeta> oh, okay, then try: sudo systemctl restart gdm
[00:52] <signofzeta> that's the nice-ish way to do it
[00:52] <waltman> No response.
[00:52] <sarnold> waltman: maybe systemctl restart display-manager   would do it, that's probably very similar to signofzeta's command; but imho restarting X11 isn't all that different from the reboot :( so you might as well go all the way down and back..
[00:53] <oerheks> .. as you supposed to..
[00:53] <rjft197> I don't get an expert mode or rescue broken system just - Try or install ubuntu - ubuntu (safe graphics) - OEM install - Boot from next volume - UEFI Firmware settings
[00:54] <waltman> That didn't help either.
[00:54] <oerheks> windows might have switched on Fastboot in uefi..
[00:54] <signofzeta> rjft197: try Method 2 on that web site.  I admit I've never had to do this.
[00:54] <waltman> This has happened to me before after an nvidia update. It should really force a reboot after that.
[00:55] <waltman> OK, I'm just going to reboot it. I'm be back in a few minutes.
[00:58] <rjft197> signofzeta Oops i didn't scroll down to see method 2.  I have tried boot-repair it doesn't have any suggestions.  I will get the output from it though.
[01:06] <rjft197-lv> https://paste.ubuntu.com/p/RV7KrXz7hY/
[01:09] <signofzeta> everything seems normal.  let me look.
[01:11] <signofzeta> can you mount your Linux partition? /dev/nvme0n1p7
[01:11] <rjft197-lv> Also I discovered that a bit of the fdisk -l output looks like this
[01:11] <rjft197-lv> Device              Start        End    Sectors   Size Type
[01:11] <rjft197-lv> Where as parted -l reports
[01:11] <rjft197-lv> Number  Start   End     Size    File system  Name                          Flags
[01:11] <rjft197-lv>  1      1049kB  263MB   262MB   fat32        EFI system partition          boot, esp
[01:11] <rjft197-lv>  2      263MB   397MB   134MB                Microsoft reserved partition  msftres
[01:12] <waltman> I'm back. Rebooting seems to have fixed things.
[01:12] <signofzeta> I'm guessing your /boot is on either partition 7 with your other Linux files, or on the ESP.
[01:12] <signofzeta> waltman: excellent!
[01:13] <arraybolt3> rjft197-lv: You might try mounting your system's disk to /mnt using "sudo mount /dev/<disk ID here> /mnt", then bind-mount critical paths ("sudo mount --bind /dev /mnt/dev". repeat for at least /proc and /sys, maybe more than those). Then "chroot /mnt", and "update-grub".
[01:13] <signofzeta> basically, GRUB is starting up but it can't find your grub.cfg file.
[01:14] <arraybolt3> rjft197-lv: Oh, you might also need to mount the EFI system partition with "sudo mount /dev/<efiPartiionIDHere> /mnt/boot/efi".
[01:15] <rjft197-lv> > sudo mount /dev/nvme0n1p7 /mnt
[01:15] <rjft197-lv> NTFS signature is missing.
[01:15] <rjft197-lv> Failed to mount '/dev/nvme0n1p7': Invalid argument
[01:15] <rjft197-lv> The device '/dev/nvme0n1p7' doesn't seem to have a valid NTFS.
[01:15] <rjft197-lv> Maybe the wrong device is used? Or the whole disk instead of a
[01:15] <rjft197-lv> partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
[01:15] <rjft197-lv> NTFS signature is missing.
[01:15] <rjft197-lv> Have I tried to mount the wrong thing there?
[01:15] <arraybolt3> rjft197-lv: That's the wrong partition - that's where Windows is.
[01:16] <signofzeta> no, looking at his partition table, p7 is the only one marked as Linux Data
[01:17] <arraybolt3> Oh, I can't see the pastebin, so... Weird. Try "sudo mount -t ext4 /dev/nvme0n1p7 /mnt".
[01:17] <arraybolt3> Replace "ext4" with whatever filesystem you're using (if you're using BTRFS, use "btrfs" instead of "ext4", for instance).
[01:18] <arraybolt3> signofzeta: Any clue why on planet earth "mount" would be trying to mount NTFS when it's a Linux fs? That's so weird.
[01:18] <rjft197-lv> I think that's the issue.
[01:18] <signofzeta> arraybolt3: I don't know. It's guessing wrong?
[01:18] <arraybolt3> (And I'm realizing "NTFS signature is missing" doesn't mean it's a Windows partition necessarily - sorry.)
[01:19] <rjft197-lv> fd... seems to think it's linux
[01:19] <rjft197-lv> but par... seems to think it's unknown
[01:19] <arraybolt3> Are you able to get into your files with the file manager?
[01:19] <rjft197-lv> I can't mount the drive
[01:19] <rjft197-lv> I've just tried those options.  I'd assume it was ext4 but I've tried ext2 too.
[01:19] <rjft197-lv> ext3 I mean
[01:20] <signofzeta> Ubuntu defaults to ext4 these days.  Do you remember what file system it was?
[01:21] <rjft197-lv> Device              Start        End    Sectors   Size Type
[01:21] <rjft197-lv> ...
[01:21] <rjft197-lv> \/dev\/nvme0n1p7  389177344 1961932799 1572755456 749.9G Linux filesystem
[01:21] <rjft197-lv> that's from fdi
[01:21] <rjft197-lv> sk
[01:22] <arraybolt3> rjft197-lv: I wonder if maybe Windows pulled a fast one on the partition table, so that the partition table has the partition marked NTFS when it's actually ext4? TestDisk might be able to do the trick here, but that could be somewhat risky, and I've never used it, so...
[01:22] <signofzeta> your partition table looks normal:  EFI System Partition, bunch of Windows partitions, then one Linux one.
[01:22] <signofzeta> I'd say to try running fsck, but now I'm getting uncomfortable
[01:23] <rjft197-lv> Most of my data is backed up.  I was just hoping that windows had managed to do something iffy without losing all the data to negate the need to reinstall the OS and all the software
[01:23] <signofzeta> what the heck happened while you were in Windows?  Feature update?
[01:24] <arraybolt3> And trying to mount it with the "-t ext4" option in there didn't do the trick?
[01:24] <rjft197-lv> Happy to try anything one last time.  Probably I hadn't booted into windows for a long time.  I don't use it anymore.  It's only because my sons iPad was set to unavailable so needed a restore
[01:24] <rjft197-lv> I tried -t ext4
[01:24] <rjft197-lv> ext3
[01:24] <rjft197-lv> ext2
[01:24] <rjft197-lv> and the other one you suggested
[01:24] <arraybolt3> Bah. Try popping open GParted and see what partition type it thinks it is. That should tell you the filesystem.
[01:25] <rjft197-lv> How can you write that.
[01:25] <rjft197-lv> GParted
[01:25] <rjft197-lv> ha, parted -l
[01:25] <rjft197-lv> It wasn't letting me write that earlier.  I was trying to provide the output from parted -l
[01:25] <arraybolt3> It's not a terminal command, it's a GUI app. If you're in a live Ubuntu desktop, you should have it in the Application Menu.
[01:25] <signofzeta> Try this: fsck.ext4 -n /dev/nvme0n1p7
[01:25] <signofzeta> The -n switch will make no changes
[01:26] <rjft197-lv> gparted and fdisk have differing opinions
[01:26] <signofzeta> And yes, you were muted for spamming.  Use a paste bin site like paste.ubuntu.com, termbin.com, etc. for multi-line stuff
[01:26] <arraybolt3> Whatever FS gparted thinks, put that after the -t and see what happens.
[01:28] <rjft197-lv> fdisk -l https://termbin.com/b2x2
[01:29] <rjft197-lv> parted -l https://termbin.com/tc7bd
[01:29] <rjft197-lv> gparted has some red exclamation marks next to p1, p2, p3 and p7
[01:30] <rjft197-lv> p7 has an unknown file system in gparted
[01:30] <signofzeta> yeah, that filesystem is hosed.  You can try fsck -n on it to see what can be done, but damn -- what did Windows do?
[01:32] <rjft197-lv> fsck.ext4 ..... command https://termbin.com/y58s
[01:33] <arraybolt3> So weird. Best I can figure at this point would be to run the commands suggested by the fsck, but that could end in disaster. Guess now I know to NEVER dual-boot Windows and Linux...
[01:34] <signofzeta> yeah, I don't even know, man.  Something happened while you were in Windows, and that's definitely not normal.  Dual-booting should be fairly painless.
[01:35] <arraybolt3> If you're not comfortable causing worse damage, I'd take a full disk image of the NVME device with dd before trying anything fancy with fsck. But if you're fine with losing everything on the drive (including Windows possibly), then I'd try the suggested fsck commands and maybe TestDisk and see what happens. Might work, might blow up.
[01:36] <signofzeta> fsck can't even find an ext2/3/4 superblock on that volume, so it's more than hosed.  Unless it's something else like ZFS or btrfs.
[01:37] <rjft197-lv> I would have thought I'd gone with the default system when installing.
[01:37] <signofzeta> yeah, nothing wrong with ext4.  I picked ZFS for auto-snapshots and stuff -- not that that would have helped you here.
[01:37] <rjft197-lv> and the laptop is only a year old or so.
[01:38] <arraybolt3> Wipe it, reinstall Linux giving it the whole entire disk, then plop Windows in a virtual machine.
[01:38] <signofzeta> I don't know what happened to the contents of that partition, but it's gone.  You can try booting into Windows to see what it thinks, but it'll probably just say "RAW"
[01:40] <rjft197-lv> At this point I'll try anything  I did try the commands that fsck suggested they just gave the same output
[01:40] <rjft197-lv> I can't boot into windows.  I don't have a boot screen to do so.
[01:41] <rjft197-lv> ideally I'd keep the dual boot.  I don't have instalation media for windows to create a virtual machine.  And I do have one project that I'm working on that would need me to use windows.
[01:41] <signofzeta> Since it's UEFI, you might be able to use your firmware's boot menu to select Windows Boot Manager instead of ubuntu.  Or is that also broken?
[01:43] <rjft197> your device ran into a problem and needs a restart. we'll restart for you
[01:43] <rjft197> and it doesn't
[01:43] <signofzeta> ah, damn
[01:44] <signofzeta> Well, I'm not sure about this one.  Startup Repair (if you can get that far) might be able to get Windows working, but your Linux partition seems to be toast.
[01:45] <signofzeta> I've heard of Win10 breaking GRUB when it updates, but that's usually a quick fix.  I've never seen it hose a partition like that.
[01:45] <rjft197> There's a dell supportassist os recovery.  I wonder if that will allow it to reinstall.
[01:46] <signofzeta> can't speak for that, but do you have a backup of your Windows data (if you care about that)?
[01:46] <rjft197> thanks anyway.  Yeah I don't have the best luck with computers.  I had a nas for a bit of a better chance of not losing data.  Two hard drives died within 10 minutes of each other :(
[01:47] <signofzeta> that happened to me, too!  RAID 5 with faulty Seagates.
[01:47] <rjft197> I have a backup of anything that is important.  Just no ability to install windows i don't think.
[01:47] <signofzeta> can you borrow another computer?  Grab a flash drive and download Microsoft's Windows 10 (or 11) Media Creation Tool.
[01:47] <signofzeta> Then get that working and make an Ubuntu install disk.
[01:50] <signofzeta> I haven't tried this since the Win7 days, but supposedly, the way to dual-boot natively is to do Windows first, then Linux.
[01:51] <rjft197> I have another computer that's not the issue.  And I have an ubuntu live usb key that I can install ubuntu from.
[01:51] <rjft197> Yes I've only ever done windows first then linux.
[01:51] <signofzeta> at least you have a backup.  I commend you for that!
[01:52] <rjft197> (my backup wasn't working at the time my laptop broke, had to swap motherboards but i managed to get that working.
[01:52] <rjft197> just need to get my laptop back. I just don't know how to get windows onto the laptop now.
[01:53] <signofzeta> the easiest way would be to make a Windows installer, clean the disk, then start from scratch.
[01:53] <signofzeta> I'd use the Windows Media Creation Tool.  I'm not familiar with SupportAssist.
[01:53] <signofzeta> If it lets you partition the disk, just save some space for Ubuntu
[01:56] <signofzeta> I'm heading to bed.  Good luck, rjft197!
[01:57] <rjft197> Thanks, Just don't know how I'm going to install it.  It came preinstalled so i don't have a certificate.  I don't know how that works these days
[01:58] <signofzeta> oh, it's automatically activated.  Your Windows key is burned into the ACPI tables.
[01:59] <signofzeta> just install the right edition (Home, Pro, or other) and it takes care of itself
[01:59] <rjft197> Oh cool.  there is a download and install the factory operating system.  So time to start the reinstall.  Thanks very much
[01:59] <signofzeta> anytime!
[02:40] <jwash> hi guys, i just turned on my laptop and now have no sound devices in pavucontrol
[02:40] <jwash> any ideas on how to fix?
[02:41] <arraybolt3> jwash: Did you just finish rebooting after an update?
[02:42] <jwash> yes
[02:42] <jwash> this is my soundcard: Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
[02:43] <jwash> owner@Latitude:~$ alsamixer
[02:43] <jwash> cannot open mixer: No such file or directory
[02:43] <arraybolt3> jwash: Almost certainly the result of a broken kernel update. Try these instructions: https://askubuntu.com/questions/945403/how-to-downgrade-kernel-after-bad-update-16-04
[02:47] <jwash> installing a new kernel, will see if that fixes
[02:48] <arraybolt3> jwash: Pretty much any time you reboot and then something doesn't work, it's a kernel problem and a kernel downgrade (or maybe a kernel upgrade) will do the trick. Just keep trying new kernels as they come out to see if they work yet, and if not, fall back to the old one.
[02:51] <jwash> whole computer is lagging now
[02:52] <jwash> startup took 2 min before login screen appeared, usually 5 secs
[02:52] <jwash> had to use onboard to login, then it took 2 more min before it connected to wifi and keyboard started working....
[02:53] <arraybolt3> jwash: That's... weird. That shouldn't happen. How did you install the kernel?
[03:02] <Rockwood> hi
[03:03] <Rockwood> how to install ubuntu lts without gui on my VM ?
[03:03] <lotuspsychje> !server
[03:03] <Rockwood> i have iso file of ubuntu 20.4
[03:03] <oerheks> what vm exactly?
[03:04] <Rockwood> oracle VM
[03:04] <Rockwood> Virtual Box
[03:04] <enigma9o7[m]> If you use the iso for ubuntu server, it won't install a GUI by default.
[03:05] <Rockwood> but installation looks gui
[03:05] <enigma9o7[m]> But if you're trying to use the regular iso to install w/o dekstop, dunno if thats possible...
[03:05] <oerheks> you can see virtualbox, right?
[03:05] <Rockwood> enigma9o7[m], yes
[03:06] <Rockwood> oerheks, yes
[03:06] <Rockwood> enigma9o7[m], which the correct link for it?
[03:06] <enigma9o7[m]> Yes?  I dont recall asking a question....
[03:06] <oerheks> indeed server needs no gui or monitor
[03:06] <Rockwood> means
[03:06] <oerheks> downloads on ubuntu.com?
[03:07] <Rockwood> i downloaded from ubuntu.com
[03:07] <Rockwood> yes
[03:07] <enigma9o7[m]> https://ubuntu.com/download/server
[03:08] <enigma9o7[m]> https://mirror.ette.biz/ubuntu-releases/22.04/ubuntu-22.04-live-server-amd64.iso for example
[03:09] <enigma9o7[m]> From untu.com/download/server select option #2 for a direct download of the iso.
[03:09] <enigma9o7[m]> (ubuntu)
[03:10] <Rockwood> enigma9o7[m], i am downloading your suggested version
[03:24] <descent1> what does [m] mean on peoples name
[03:25] <arraybolt3> descent1: Pretty sure it means they're on Matrix chat bridged to IRC. Don't know that for sure, but I know Matrix is bridged, and I've seen users who have both a normal nick and a [m] nick, so that's my best guess. Anyone want to confirm?
[03:26] <descent1> ah ok
[03:26] <Unit193> Usually, yeah.  Some people see that and think it means mobile, so use it for that.  But typically it's Matrix.
[03:49] <enigma9o7[m]> yes confirmed it means I'm using a matrix client, not real irc client.
[05:07] <tgoyen> I need help with apt policy if someone has a minute
[05:08] <tgoyen> when I am installing chromium there is another policy
[05:08] <tgoyen>      101.0.4951.64-1~deb11u1 500
[05:08] <tgoyen>         500 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages
[05:08] <tgoyen>  *** 99.0.4844.74-1~deb11u1 700
[05:08] <tgoyen>         300 http://ftp.debian.org/debian stable/main amd64 Packages
[05:08] <tgoyen> after the version.... the 700. Not sure where that comes from, but it blocks the upgrade to a newer version
[05:10] <luna> tgoyen, #debian
[05:10] <enigma9o7[m]> /etc/apt/preferences.d
[05:13] <tgoyen> @enigma9o7[m], Thanks!
[05:24] <tgoyen> yeah there was a special preferences file in there someone had left me....
[05:36] <nightBulb> Greetings people, My Dell Inspiron 7000 series laptop does not wakeup with touchpad interaction...
[05:36] <nightBulb>  It used to wakeup in Ubuntu 21.10
[05:36] <nightBulb>  But no longer works in Ubuntu 22.04 Linux Kernel 5.15
[05:36] <nightBulb>  Just to clarify,
[05:36] <nightBulb>  suspend and wakeup IS working
[05:36] <nightBulb>  touchpad after wakeup IS working
[05:39] <nightBulb> anyone ?
[06:45] <nightBulb> is anyone there ?
[06:45] <luna> yeah
[06:45] <nightBulb> Hi
[06:45] <luna> hi
[06:46] <nightBulb> I have some problem with Ubuntu 22.04
[06:46] <nightBulb> I have "a" problem
[06:47] <arraybolt3> I'm here too!
[06:47] <arraybolt3> What's gone wrong?
[06:48] <nightBulb> my laptop does not wakeup on touchpad interaction
[06:48] <nightBulb> power button for wake up works
[06:48] <nightBulb> but not touchpad trigger ...
[06:48] <nightBulb> also, does anyone know how to contact Kai-Heng Feng ?
[06:48] <nightBulb> I found this https://patchwork.kernel.org/project/linux-input/patch/20200618145515.5055-1-kai.heng.feng@canonical.com/
[06:49] <nightBulb> which is the closest I think i have come to identify problem.
[06:49] <nightBulb> The touchpad used to wakeup laptop from suspend up till Ubuntu 21.10
[06:49] <nightBulb> in 22.04 its not working
[06:50] <guiverc> nightBulb, I know how I'd contact (Canonical/Ubuntu) people, but I can't see other passing on that detail (if it's not publically available)
[06:50] <arraybolt3> Hmm. Not sure how to fix the touchpad, if it's not working anymore, but it used to work, then it's quite possible it's a kernel problem. You can fall back to 20.04 for the time being.
[06:50] <arraybolt3> As far as contacting a Canonical employee, that's not how this sort of stuff is usually done. You file a bug report.
[06:51] <nightBulb> It appears the issue is with Linux Kernel 5.15 ..
[06:51] <nightBulb> I filed a bug report
[06:51] <guiverc> s/other/others ^  , but I agree completely with arraybolt3
[06:51] <nightBulb> guiverc, can you ask ?
[06:51] <nightBulb> https://patchwork.kernel.org/project/linux-input/patch/20200618145515.5055-1-kai.heng.feng@canonical.com/
[06:51] <nightBulb> what happened to that patch ?
[06:51] <guiverc> in that case I'd file a bug report too
[06:51] <arraybolt3> Then just wait, and check your email daily. Contacting people directly is not a good way to get a problem fixed, it's a good way to make people annoyed.
[06:52] <nightBulb> guiverc, arraybolt3 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971933
[06:52] <nightBulb> I was hoping Kai was here on IRC ...
[06:52] <arraybolt3> Looks like a good report to me. Just give it time.
[06:52] <nightBulb> no-one is responding in #ubunuu-kernel
[06:52] <guiverc> to get bugs noticed; test to see if it occurs in the current development release... that tends to get a developers attention more than a released product that requires SRU; they'll backport if possible (ie. kinetic fixes will reach jammy in time via HWE at minimum)
[06:53] <arraybolt3> I've been doing bug reporting stuff, it takes some time, but I've witnessed a bug get fixed (actually, two bugs), so the reports don't go unnoticed. These people just have gobs of work to do (me included, though I'm not a Canonical employee).
[06:53] <nightBulb> Yup
[06:54] <nightBulb> I saw the buglist was quite big
[06:54] <nightBulb> that's why I was trying to get it fixed as soon as possible, by identifying which version caused trouble ..
[06:54] <nightBulb> 5.13 -> 5.15
[06:55] <nightBulb> Ubuntu 21.10 -> Ubuntu 22.04
[06:55] <arraybolt3> nightBulb: Like guiverc said, try using the latest development release (Kinetic) and see if it happens there, too. The way Ubuntu works is, new changes get merged into the development release most easily. That's the one everyone works on.
[06:55] <arraybolt3> Here's Ubuntu Kinetic downloads: http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248206/downloads
[06:55] <nightBulb> arraybolt3, thanks :)
[06:56] <arraybolt3> Note, don't use development releases as your daily drivers - they may have bugs that the devs are still sorting out. Use them for testing (like seeing if the trackpad issue happens).
[06:56] <nightBulb> arraybolt3, it boots off of USB ?
[06:56] <nightBulb> of off
[06:56] <nightBulb> of of ?
[06:57] <arraybolt3> Depends on how you want to do it. You can burn it to a DVD, flash it to a USB with Startup Disk Creator, dd, or balenaEtcher.
[06:57] <arraybolt3> But yeah, should work off a USB no problem if that's what your asking.
[06:58] <nightBulb> Yup, I test it (of of) USB first...
[06:58] <nightBulb> then report on bugreport ?
[06:59] <arraybolt3> Yep. If you can reproduce the problem on the bug, stick a comment on the bug report indicating that it happens in the latest Kinetic.
[06:59] <nightBulb> okey-doke
[06:59] <arraybolt3> (You can also add a "Kinetic" tag once you've verified it still happens, but I'm happy to do that for you.)
[06:59] <nightBulb> sure ..
[07:00] <nightBulb> off I go ...
[07:00] <nightBulb> thanks arraybolt3 guiverc
[07:00] <nightBulb> :)
[07:01] <arraybolt3> You bet. I'll also do some testing on my end, and pitch in some help. I've already subscribed to bug notifications for the touchpad bug.
[07:01] <nightBulb> :) :) :)
[07:14] <de-facto> wow will pulseaudio ever be fixed? it is extremely buggy since years, unable to output analog audio and now it seems even fails over hdmi. killing it sometimes cures it, but thats not really a solution
[07:14] <i-garrison> de-facto: hdmi is a bit problematic, especially with displayport; which pulseaudio version do you have?
[07:14] <de-facto> with analog audio it makes the volume slider wildly wiggle on itself sometimes, other times it works
[07:15] <de-facto> the one from 22.04
[07:15] <i-garrison> de-facto: please share 'fuser -v /dev/snd/*'
[07:16] <de-facto> its listing /dev/snd/controlC0 and /dev/snd/controlC1
[07:17] <i-garrison> pastebin it please
[07:17] <de-facto> nothing really interesting in there but ok
[07:18] <de-facto> https://paste.debian.net/1241248/
[07:18] <de-facto> i replaced username
[07:19] <i-garrison> de-facto: np, looks good; pulseaudio does not 'wiggle' volumes unless you have flat-volumes enabled in /etc/pulse/daemon.conf, but that setting is disabled by default for ages
[07:20] <Unode> hi all, is there any way to specify for a package to be installed from the main channel and not the -updates channel?
[07:20] <Unode> I'm having issues installing libssl3-dev in a jammy docker container
[07:20] <i-garrison> de-facto: so if that is still 'wiggling' it is either firefox operating output volumes (it is a known issue) or you have some other app changing volumes on alsa devices
[07:20] <Unode> Keep getting 'libssl-dev : Depends: libssl3 (= 3.0.2-0ubuntu1.1) but 3.0.2-0ubuntu1.2 is to be installed'
[07:21] <de-facto> i-garrison, how can i disable any app to control volume?
[07:21] <Unode> (sorry i mean libssl-dev not libssl3-dev)
[07:23] <de-facto> i dont want any volume changes by any app, its too buggy
[07:23] <de-facto> can i disable that interface completely?
[07:23] <i-garrison> de-facto: there is no option to "disable" that for all apps, but here is a described workaround specifically for firefox https://bugzilla.mozilla.org/show_bug.cgi?id=1422637#c19
[07:24] <i-garrison> de-facto: also if you have something changing volumes on alsa level there is nothing pulseaudio can do with that
[07:24] <de-facto> i dont know what is causing this, but i dont need any program to change volume at all, hence my desire to get rid of this annoyance
[07:25] <i-garrison> de-facto: and please check if you are no affected by this 22.04 bug https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1953052
[07:26] <i-garrison> de-facto: well disabling volume controls on alsa level is separate topic; on pulseaudio level you can use that firefox workaround but set the virtual sink as "default" which will isolate pulseaudio apps from device volume controls
[07:26] <de-facto> this bug affecting me already exists for many years
[07:26] <de-facto> its not new in the current ubuntu or such
[07:27] <de-facto> probably more like a decade old or such
[07:27] <i-garrison> de-facto: maybe yours is different, but 22.04 bug I linked is new and it looks like it could apply for you
[07:27] <i-garrison> de-facto: still check if you do not have flat-volumes enabled in /etc/pulse/daemon.conf
[07:29] <arraybolt3> Unode: Try setting the version you want manually, like so: "sudo apt install libssl3=3.0.2-0ubuntu1.1"
[07:29] <de-facto> idk if that has anything to do with the sound slider wildly wiggling around, e.g. many times a second
[07:29] <de-facto> ; flat-volumes = no
[07:29] <de-facto> all defaults
[07:30] <Unode> arraybolt3: thanks, that works. Switching the order of packages installed on the system also seems to work. If libssl-dev is the first thing I install then apt is happy. Didn't yet check what is the final result but at least no build failures.
[07:30] <arraybolt3> Unode: Awesome!
[07:30] <Unode> arraybolt3: thanks for the suggestion. I was trying to avoid pinning the version as that will limit future uses.
[07:31] <de-facto> also killing pulseaudio fixes it sometimes, hence i blame pulseaudio itself
[07:32] <arraybolt3> Unode: Glad you got a working solution.
[07:33] <arraybolt3> Unode: Does using "=" pin a package version? I didn't know that, and the info I'm finding doesn't tell me that, so that's important to know.
[07:33] <i-garrison> de-facto: ok if you can reproduce the issue at will and have some time to debug this in detail, hop onto #pulseaudio on OFTC and we will check what exactly is causing volume jumps on pulseaudio side
[07:34] <de-facto> thats the problem i did not find out what triggers this yet
[07:34] <de-facto> sometimes it just ends in that state, other times it works without any sign of problem
[07:34] <Unode> arraybolt3: sorry by pinning I meant writing a fixed version in the recipe. I misused the word pinning there as it has a different meaning under apt.
[07:34] <i-garrison> de-facto: if that happens e.g. daily you can set up debug logging and we will catch it
[07:35] <arraybolt3> Unode: Oh, ok, that makes sense.
[07:39] <sweb> ubuntu server 22.04 has not netinstall/minimal iso. installation on HP servers via ILO is really hard, even with USB stick take long time to boot for first installation any idea?
[07:39] <sweb> mini iso on older version is about 50-100 MB, instead full ubuntu server is about 1.5 GB.
[07:40] <arraybolt3> sweb: You could try using a preinstalled server image.
[07:40] <arraybolt3> http://cdimage.ubuntu.com/ubuntu-server/jammy/daily-preinstalled/current/
[07:41] <sweb> how can i confugure, network, apt-proxy and etc using this method ?
[07:42] <arraybolt3> The image is still beefy, but it's not as large as what you're using currently. You can boot your server from a lightweight OS like Alpine, and then use xzcat and dd to flash the image to your server.
[07:42] <arraybolt3> sweb: You'd probably need to configure the server manually after installation. Once you've figured out exactly what all config files to change, you can make a Bash script that does it automatically, then be able to deploy the server image to multiple servers.
[07:42] <arraybolt3> sweb: Once the script is built, just boot, flash, reboot, run script.
[07:43] <sweb> it's really bad decision  to deprecate mini iso, it's very usefull and fast
[07:44] <arraybolt3> sweb: (If you need mass deployment, you could also try using DRBL and Clonezilla. Once you've got one master image built (which you can probably do in a VM), you can then use Clonezilla to mass-deploy the image over the network.
[07:51] <baviano> ok so the latest ubuntu 22.04 desktop update screwed up my nvidia drivers again
[07:52] <baviano> the last time it was in the proposed-repo, I couldn't find a way out so I reverted with timeshift
[07:53] <baviano> now it's in the main repo and it completely screws up the works as it did when it was in proposed, so "great"
[07:53] <baviano> I'm exactly in the spot where I was at when the proposed-repo killed my nvidia drivers
[07:53] <baviano> got a 30-series nvidia
[07:53] <baviano> all my work's stuck
[07:54] <baviano> I spent a day trying to troubleshoot this when the proposed-repo screwed things up, the only thing I concluded that would fix it in the end was to revert to my daily timeshift backups
[07:56] <guiverc> baviano, whilst in proposed did you file a bug report?   that's part of why it sits in proposed; so people can test & report issues... if none are reported & it proves successfuly in testing it'll go to main repositories.
[07:57] <baviano> nvidia-smi says no driver installed, back when this happened when this was still in the proposed-branch; which was somewhere last week, I suppose, the problem was that there was no corresponding nvidia kernel whatevers to the version
[07:57] <baviano> can't fucking remember, pardon the french
[07:58] <baviano> guiverc: lol so the previous guy gave me a ton of crap for using anything from the proposed-repo altogether and said I shouldn't have used that (as in: "you shouldn't have worn that dress")
[07:59] <guiverc> proposed can help... but if you didn't have problems before; and the problems only occurred when you enabled proposed - that's not a good thing & needs reporting generally.. It maybe I'm mising something in your history & prior advice sorry
[07:59] <baviano> so ... the last time (= last week) when this happened with the proposed repo, I did manage to get some "life" back into my nvidia card, i.e. I could get it to show up on nvidia-smi, but the graphics would still be forced on to my internal gpu's output
[07:59] <baviano> atm it's the same square one as it was with the proposed-repo's update
[08:00] <baviano> sorry for being a bit salty but that's a production machine that I run neural network training on and I'm ... yeah
[08:00] <baviano> I try to do the right thing, not clutter up things too much, ... could it be that I have Nvidia's developer repo enabled?
[08:01] <baviano> I mean am I barking at the wrong tree here ... let's see
[08:02] <baviano> /var/log/dpkg.log:2022-05-18 06:43:13 install nvidia-dkms-510:amd64 510.60.02-0ubuntu1 510.73.05-0ubuntu0.22.04.1
[08:02] <baviano> ok so that was the latest thing that's been installed according to '/var/log/dpkg.log'
[08:03] <baviano> which is odd, since I _swear_ I saw a bunch of packages on ubuntu's software updater nagging me about how they need to be installed ... but /var/log/dpkg.log says that's the only thing that's been installed in the past few days
[08:04] <baviano> let's see, running
[08:04] <baviano> 'sudo apt install nvidia-dkms-510:amd64 --reinstall' just to see what the hell,
[08:04] <baviano> oh yep it couldn't probably figure out a way to handle the UEFI secure boot
[08:06] <baviano> okay ... alright.
[08:06] <baviano> so the auto-update screwed it up because the dkms package needs you to set up the UEFI secure boot, and it got compeltely omitted, so ...
[08:06] <baviano> *blood pressure maybe returning back to normal*
[08:09] <baviano> WORKS!
[08:09] <baviano> guiverc: works, when I reinstalled the dkms package that had been installed last night and re-entered a new password and validated it on boot ...
[08:09] <baviano> the auto-update process on dkms drivers, woo-hee....
[08:09] <baviano> thanks for the help and sorry about the gun
[08:09] <baviano> ;::D
[08:11] <turganti> hiii
[08:15] <turganti> hii
[08:15] <turganti> soy turganti
[08:22] <baviano> guiverc: ok, so to recap; the dkms driver package got auto-updated last night via ubuntu's software updater (the gui one); obviously since I have secure boot enabled, it needed me to set a password for the new driver and whatnot, which was completely omitted by the software updater (that only wanted me to reboot)
[08:22] <Kharec> hello !
[08:23] <baviano> guiverc: so yeah, reinstalling the package via apt like I said over there solved the issue, but that's overall a bit of a... let's say, if you're not much into package handling, well, sure glad I don't do end-customer endpoints.
[08:24] <baviano> you might want to see if it could be possible to i.e. open up the terminal prompt for dkms driver installation via software updater whenever it's required, or somehow pipe the output through the software updater.
[08:24] <baviano> because otherwise you'll just end up with a black screen with no video output on reboot. I'm glad this workstation has a built-in GPU as well
[08:24] <baviano> others might not be that lucky.
[08:24] <baviano> k thnx bye
[08:25] <nightBulb> arraybolt3, I just checked on Kinetic
[08:25] <nightBulb> bug exists
[08:25] <nightBulb> on Kinetic "current" build
[08:28] <nightBulb> How to mark ?
[08:47] <Laci69> Hello, When I start the system the desktop looks like this: https://i.ibb.co/fQdLdvg/j.jpg How can I make the wallpaper "full screen" by default?
[08:48] <Laci69> The system starts like when the 'super key' is pushed.
[08:54] <multi8> exit
[09:24] <arraybolt3> nightBulb: You should see an area marked "tags" underneath your bug report (before the comments, I believe). You should be able to edit that - add the word "kinetic" to the line of tags, separate from the other tags.
[09:24] <arraybolt3> I'll do it in a bit (if I remember, which I hopefully will)
[09:26] <arraybolt3> nightBulb: Got it tagged, will comment once I get it tested. You may want to comment as well.
[09:29] <nightBulb> arraybolt3, thanks, (The long bug report kind-of / somehow threw me off, and couldn't see the tags option at the bottom) Just saw it ...
[09:29] <nightBulb> Thanks for tagging
[09:31] <arraybolt3> 👍
[09:34] <dreamon> hello. question: I want to know, using a raid-1 on Ubuntu on a server. how can I get knowledge if there`s a failure on some hdd drives? maybe get an email if so.
[09:35] <dreamon> or see if there is a prefail condition?
[09:37] <waveform> dreamon, depends how you're implementing raid-1 -- in software via mdadm?
[09:40] <waveform> (my hardware raid knowledge is likely massively out of date at this point so I can't help with that, but I can provide some hints on monitoring with mdadm and smartmontools)
[09:40] <dreamon> waveform, want to use a brand new mainboard. so think its hardware designed? never used a raid befrore
[09:41] <waveform> okay, if it's hardware raid, and if hardware raid still operates like it did about 10+ years ago, then basically monitoring is up to your raid hardware and whatever management tools it provides because the OS won't "see" the underlying drives anyway -- just the device the raid hardware provides. But as I say, that's how it *used* to be and I've no idea if that's still relevant (I'd heard rumours it's all soft-raid these days anyway, but what that
[09:41] <waveform> means in practice I don't know)
[09:44] <dreamon> waveform, how does software raid work? is this a OS thing to do? so using mdadm its a linux management software?
[09:44] <dreamon> maybe lower performance?
[09:47] <waveform> yes, mdadm is the OS doing software raid; with the spare capacity on modern processors (and the vast disparity between the speed of processors and the speed of mass storage) I'd be extremely surprised if there was any performance difference there, even with lower-end CPUs. The main worries are (or used to be?) things like corruption in the case of power loss (hardware raid used to have battery/capacitor backup systems for that, software raid can rely
[09:47] <waveform> on journalling-esque systems which does indeed lower performance but is optional -- if you have a decent UPS setup you *might* consider it unnecessary for example)
[09:49] <waveform> obviously in the case of the OS managing the raid setup, it *can* see the individual drives, so in this case I strongly recommend installing smartmontools and setting that up to do periodic self-tests on each drive in the array (staggered so you don't go hitting 'em all at once), with e-mail sent in the case of errors. Further, mdadm should be configured to performance periodic "scrubs" of the array (I *think* that's actually the default in ubuntu/
[09:49] <waveform> debian's packaging of mdadm, but worth confirming)
[09:51] <dreamon> cool. Thank you for your help. now its getting clear.
[10:21] <pagios> can i ask curl to follow 302 redirection and auomatically request the new location?
[10:27] <waveform> pagios, I thought it did already, no?
[10:27] <pagios> no
[10:27] <pagios> -L
[10:27] <waveform> oh, I'm confusing it with wget's behaviour
[10:46] <Itay> I installed ubuntu-desktop on clean ubuntu-server 20.04.4 using apt install ubuntu-desktop
[10:46] <Itay> But after install, taskbar is not attached, it can only be seen with winkey - any way to fix it?
[11:07] <Bugies> Hello I have a problem with Doom 3 BFG steam version, I cannot get rid of the white screen in the game menu. I have an amd rx 5500 xt graphics card and ubuntu 22.04. Did someone have a similar problem with this card?
[11:34] <kmikita> Is available ureadahead patch for latest kernel 5.17?
[11:48] <lotuspsychje> kmikita: for deeper kernel questions you might wanna ask in #ubuntu-kernel
[11:56] <kmikita> lotuspsychje, thank you fo advice
[11:58] <lotuspsychje> Bugies: would it be possible to share your dmesg in a !paste maybe the volunteers can check your graphics there
[12:01] <Bugies> lotuspsychje, https://termbin.com/9ea3
[12:02] <Guest9061> hello, i'm running ubuntu 20.0.4 and i get this error: Package 'chrome-gnome-shell' has no installation candidate. any way i can get around this without like reinstalling everything? what i'm actually trying to do is to remove the "Window is ready" message
[12:03] <lotuspsychje> Bugies: did you update your system to latest, aka 5.15.0-30-generic ?
[12:04] <Bugies> i have 5.15.0-27-generic
[12:04] <lotuspsychje> !uptodate | Bugies lets try this first
[12:06] <Guest9061> (sorry, nevermind my question, found a workaround)
[12:11] <gtahc> Was the ubuntu-software-center replaced by gnome-software?
[12:11] <lotuspsychje> Bugies: i also see you added a kernel parameter; quiet splash amdgpu.ppfeaturemask=0xffffffff amdgpu.vm_fragment_size=9
[12:12] <Bugies> yes amdgpu.vm_fragment_size=9 is for amdgpu-pro but not using it
[12:12] <Guest9061> (actually do mind my question, the workaround only worked halfway)
[12:13] <Bugies> lotuspsychje , i found Video memory: 142MB in glxinfo
[12:13] <lotuspsychje> Bugies: your dmesg shows that parameter is added
[12:14] <Bugies> ok i will remove it leter
[12:28] <Bugies> lotuspsychje, thank you, cya
[12:33] <k0fein> hi, how could I find which apps (even better packages, apps came from) handles drawing desktop icons? I have ubuntu budgie 22.04 and there are 3 overlapped sets of icons for everything on the desktop. When I turn off 'show desktop icon' only 2 remain. I need to know what packages are responsible, so I can keep just one.
[13:10] <unixbsd> wheere to find the wabbitemu for ubuntu, or ... debian or devuan linux amd64, already built ? (calc emulator)
[13:13] <lotuspsychje> !info tilem | unixbsd can this help ?
[13:15] <unixbsd> tilem 2 cannot emulator the TI 84 PC SE colors ! so sadly
[13:15] <unixbsd>    ==> The file ti84pcse.rom is not a recognized calculator ROM file.
[13:16] <unixbsd> we need wabbitemu for ubuntu
[13:16] <leftyfb> unixbsd: then ask wabbitemu
[13:16] <unixbsd> ther eis no one on #wabbitemu
[13:16] <lotuspsychje> !info tiemu | unixbsd and this?
[13:17] <leftyfb> unixbsd: https://github.com/sputt/wabbitemu/issues
[13:17] <unixbsd>   TiEmu 3 - Version 3.03    : tiemu ti84pcse.rom   crashes.
[13:18] <unixbsd> tiemu ti92p.rom   works but :(  sadly tiemu ti84pcse.rom   crashes
[13:19] <ravage> unixbsd, https://i.imgur.com/XzmiI19.png maybe this helps?
[13:23] <unixbsd> you did that with WINE ?
[13:23] <unixbsd> ah ok. but then, I cannot do tht on my armhf Raspberr ypi 4 ??
[13:24] <unixbsd> can you built a wabbitemu built package for ubuntu armhf for raspberry pi ?
[13:24] <ravage> you need something like box86 then
[13:25] <unixbsd> what about hte github infos? they said that it was compiled on linux, but they dont commeent on that.
[13:25] <ravage> https://github.com/ptitSeb/box86/blob/master/docs/X86WINE.md
[13:32] <iomari891> is there a repo for iptables 1.8.8?
[13:35] <lotuspsychje> iomari891: the volunteers cant advice on external ppa's, only reccomend/support the ubuntu repo packages
[13:38] <lotuspsychje> !backports | iomari891 another route could be
[14:04] <BluesKaj> Hi all
[16:33] <Sven_vB> hi :)
[16:36] <Sven_vB> in focal, is there a way to disable a certain key for just one program? in most programs I want to be able to type "=" but not into my graphics program, because I often press that accidentially and it messes with my selection.
[16:41] <Furna> Hi ... I would need some help on Ubuntu22-04 fresh install. I have a Realtek ALC1220 on a Z490 chipset motherboard; everything seems to work but I miss a GUI to make "room corrections" to my 5.1 (adjust volume levels of front, center, sub and rear)
[16:42] <Furna> I know I can use alsamixer in terminal with ncurses anyway I am just wondering if there is a GUI
[16:48] <Sven_vB> Furna, in pavucontrol, in the output tab, right of the device name, is there a lock icon? unlocking it should split the volume slider into one per channel.
[16:56] <Furna> Seven_vB: pavcontrol was not installed ... that's a huge step forward! Thanks
[17:53] <vertebrate3> Hey,
[17:53] <lotuspsychje> welcome vertebrate3
[18:10] <MrFantastik> how big is the apt package index?
[18:10] <MrFantastik> like if i installed every single package from apt, how much space woould that take up?
[18:10] <MrFantastik> or how can i answer this myself without actually doing that
[18:11] <sarnold> those are different questions..
[18:11] <sarnold> MrFantastik: the package indexes are stored in http://archive.ubuntu.com/ubuntu/dists/
[18:12] <MrFantastik> the second one is what I really want to know
[18:12] <sarnold> MrFantastik: the repo structure isn't exactly *easy* to follow if you're not familiar with it, but different files in there have the details on the binary packages, or the source packages, in the various releases and pockets and components
[18:13] <sarnold> *installing* all the packages would be quite difficult, as there are conflicts among some packages, and there's something like twenty different types of kernels you could install, but you'd realistically only want one type of kernel..
[18:14] <Jeremy31> Wh0: try the command>  rg
[18:15] <MrFantastik> sarnold, right that makes sense
[18:15] <Wh0> ok
[18:16] <sarnold> MrFantastik: hopefully helpful https://termbin.com/7yfs
[18:16] <Wh0> rg: command not found
[18:16] <Wh0> Jeremy31,
[18:16] <MrFantastik> but lets say I wanted to install as many as possible, would that me like, 100s of gbs, tbs, pbs?
[18:17] <MrFantastik> oh very nice!
[18:17] <Wh0> rg worked on debian, but not on ubuntu (i am in wsl on windows)
[18:17] <sarnold> Wh0: the ripgrep package is only in focal and newer https://launchpad.net/ubuntu/+source/rust-ripgrep
[18:18] <MrFantastik> okay so ths output is in bytes?
[18:18] <sarnold> MrFantastik: I think kilobytes https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-installed-size
[18:18] <MrFantastik> and each line is for main, universe, restricted, and multiverse?
[18:19] <sarnold> MrFantastik: yeah; and this is just focal, not including -security or -updates; doing a good job with those would be way harder
[18:25] <MrFantastik> ty sarnold I was answering a question for someone about along the lines  "why isn't every C libary installed by default" in ubuntu
[18:34] <sarnold> MrFantastik: oh my :) that'd be a *lot* of stuff installed :)
[19:02] <ternee> I came across a curiosity. I installed Aether from the snap store, but the launcher wouldn't run it. Saying it couldn't activate something I think. So I ran it from the terminal to see what was going wrong. But then it ran from the terminal perfectly well. What's going on?
[19:04] <oerheks> Now you run it from terminal, does the normal launcher work too?
[19:04] <ternee> No
[19:04] <oerheks> this P2P network might need to be activated something, i have no clue
[19:05] <ternee> You mean something that can't be initialised from the launcher?
[19:06] <ternee> amyway it needs looking at. I'm a returnee to Linux, so I remembered what to try, but to new users this will just look like a dead programme
[19:06] <oerheks> testing it now ..
[19:07] <ternee> Thank you
[19:07] <oerheks> well, latest version is from 2020 ...
[19:07] <ternee> So why is the snap still in the store i suppose is the next question
[19:08] <oerheks> and i never heard or read about it before, it looks like
[19:08] <ternee> It's works frine from the terminal, but maybe I should look for a later version
[19:08] <ternee> If there is one
[19:08] <oerheks> "Failed to launch  bla bla desktop file did not specify <something>"
[19:08] <ternee> That's it
[19:08] <oerheks>  file a bugreport to the maintainer?
[19:09] <oerheks> sudo snap remove aetherp2p
[19:09] <ternee> but if you run it from aetherp2p in cli it will bootstrap
[19:09] <oerheks> not that in your bugreport?
[19:09] <oerheks> c/note
[19:10] <douglasfir> hey! so i cant change what wifi I'm connected to, the auth thing pops up and instantly goes away
[19:10] <ternee> I will do once I remember how to report bugs. I've spent two years using a Chromebook and a phone. So I'm rusty but I'll het to it
[19:11] <oerheks> !bug
[19:11] <ternee> Thanks
[19:11] <oerheks> start with registering on launchpad, else we cannot answer back
[19:11] <ternee> ok
[19:14] <ternee> As I know this channel is logged I just want to say I can usually spell program and I don't usually make quite so many typos :) :)
[19:14] <ternee> Right lets have a look at launchpad
[19:14] <oerheks> No worries :-D
[19:15] <oerheks> brb reboot after ssl3 updates
[20:17] <bancroft_> how can I downgrade to a kernel I don't have installed anymore?
[20:19] <alkisg> bancroft_: to a specific kernel, or to any one available? Which Ubuntu version?
[20:20] <bancroft_> alkisg: I was on 22 but then problems started so I went back down to 20.04 and now what's installed is lower (5.17 -> 5.16) but i'm still getting problems
[20:20] <sarnold> try this: dpkg -l 'linux*' | grep '^ii'   -- it'll show you the packages you've got installed now. follow the patterns of what you've got installed, but replace the numbers as you need to
[20:20] <alkisg> bancroft_: 22.04 has kernel 5.4 and 5.13 available
[20:21] <alkisg> 5.16 and 5.17 aren't in ubuntu repositories
[20:22] <bancroft_> then I have no idea how I got 5.16.15 :/ or whatever 5.17 I had
[20:22] <alkisg> If you have stock Ubuntu and not some derivative, then installing 5.16 or 5.17 is a manual process
[20:23] <alkisg> E.g. from https://kernel.ubuntu.com/~kernel-ppa/mainline/ => but they are not officially supported
[20:24] <bancroft_> can I swap somehow? start over without loosing things I installed (k3s, ssh config, other apps)
[20:24] <alkisg> sudo apt install linux-generic-hwe-20.04
[20:24] <alkisg> This will give you 5.13; then reboot to that and uninstall the other ones
[20:25] <bancroft_> ok I'll give that a shot
[20:26] <bancroft_> will it mess with zfs-dkms ? do I reinstall it? that's really where all my problems are, after upgrading I've had nothing but kernel panics `VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed`
[20:28] <sarnold> if you use the ubuntu-provided kernels you should use the zfs userspace that matches the pre-built kernels
[20:28] <sarnold> if you're building your own zfs kernel modules then you should use the zfs userspace that matches the modules you're building
[20:31] <bancroft_> i'm not smart enough or confident enough to compile zfs the right way lol!!
[20:31] <bancroft_> packages, please helm me hahaha
[20:45] <coraxx> hi ..I'm having problems with xserver (ubuntu 20.04) ...when I start the computer, I only get the terminal login prompt, not the "graphic" one ...
[20:45] <coraxx> ...and if I log in as a user I can't start the xserver with "startx" ... unless I start as root ("sudo startx")
[20:46] <coraxx> ...does someone outthere know a fix ...just happened today when I ran an update of my packages ?
[20:48] <Bugies> coraxx, try 'sudo dpkg-reconfigure xdm' or gmd3
[20:49] <Bugies> gdm3
[20:49] <coraxx> trying it now ...(thnax :-) )
[20:51] <coraxx> tried all three variations ... I get "'XXX' is not installed and no information is available"
[20:51] <coraxx> I wonder what my login software is ???
[20:51] <coraxx> anyone know how I can find out ?
[20:52] <ravage> if you installed Ubuntu 20.04 desktop then it is gdm
[20:52] <oerheks> run updates again. or fix with apt install -f
[20:53] <coraxx> ravage: I installed ubuntu server 20.04 ... the xserver and related packages was installed with "zentyal"-package
[20:53] <coraxx> oerheks: already did a "fix" install  ...didn't work.
[20:54] <oerheks> oh zentyal issues.. they will support you, commercial blob
[20:56] <coraxx> anyone know which login software "zentyal 7.0" (Developer Edition) uses ?
[20:57] <oerheks> depends what desktop zentyal pull in.. we don't know, it is not from our repositories
[20:58] <sarnold> I thought zentyal was a server thing, I wouldn't have expected it to bring in any desktop stuff
[20:58] <ogra> yeah
[20:58] <leftyfb> coraxx: zentyal is not a supported application. You'll need to seek support from the vendor
[20:58] <oerheks> this guide shows it askss for a graphical environment.. https://zentyal.com/news/install-zentyal-quickly-on-top-of-ubuntu-20-04-server-or-desktop/
[20:59] <leftyfb> coraxx: ubuntu server does not have a desktop by default
[20:59] <coraxx> zentyal gives the option of also installing a graphic layer on top of ubuntu server 20.04
[20:59] <oerheks> good luck!
[21:00] <oerheks> (zentyal has no channel on Libera, afaik)
[21:00] <sarnold> https://zentyal.com/zentyal_installer.sh
[21:00] <sarnold>   echo 'lxdm shared/default-x-display-manager select lxdm' | debconf-set-selections
[21:01] <ogra> by default it oly installs a web UI i think
[21:01] <ogra> *only
[21:01] <m4tt4ew> window last
[21:01] <ogra> should be listening on port 8443
[21:02] <sarnold> heh their install script is *involved*. I wonder why.
[21:02] <ogra> https://doc.zentyal.org/en/installation.html#initial-configuration
[21:02] <coraxx> sarnold: thank you ...just discovered it 2 seconds before you wrote ...after running a dpkg-reconfigure lightdm
[21:02] <coraxx> :-)
[21:02] <sarnold> this whole gui install function just feels like stomping over things for no good reason
[22:08] <bobdobbs> Is there a channel for KDE/Plasma?
[22:10] <matsaman> bobdobbs: yeah, #kde
[22:10] <bobdobbs> thanks
[22:10] <matsaman> bobdobbs: /msg alis list *kde*
[22:25] <blahboybaz> I've been running Ubuntu 20.04 for about a year on this machine. I run update/upgrade on a VERY regular basis (several times a week on average) and I have never seen what I am looking at now.. pacakage manager is telling me there are 163 packages that can be upgraded. That seems like an alarmingly large number (like what you would see after a fresh instlal). Is that normal? I've been having an-other
[22:25] <blahboybaz> problem for a few weeks now too. Could this be a clue?
[22:29] <blahboybaz> https://pastebin.com/0xbxcqfH
[22:29] <blahboybaz> It looks like a TON of internal system packages listed in the upgrade
[22:31] <blahboybaz> Bunch of libmono stuff
[22:34] <sarnold> blahboybaz: try running 'apt policy libmono-system-web-razor2.0-cil' to figure out which repository it came from
[22:34] <sarnold> blahboybaz: (my guess is MS, but you never know..)
[22:34] <Bashing-om> blahboybaz: I too update very regularly - I have not seen more than say 6 or 7 packages requiring updates at any time :(
[22:40] <blahboybaz> sarnold: the only ms thing on here is code (visual studio code)
[22:42] <sarnold> hah
[22:43] <blahboybaz> I get https://pastebin.com/fgr9F57k
[22:43] <blahboybaz> I'm guessing this is the repos its coming from tho..
[22:43] <blahboybaz> 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
[22:43] <blahboybaz> 500 http://us.archive.ubuntu.com/ubuntu focal/universe i386 Packages
[22:43] <blahboybaz> Bashing-om: yep
[22:44] <sarnold> libmono-system-web-razor2.0-cil comes from the mono source package on ubuntu .. https://launchpad.net/ubuntu/+source/mono .. only one of the seven currently supported releases has had a mono update, and that was seven years ago
[22:44] <sarnold> aha, mono-project :)
[22:46] <blahboybaz> Just for the sake of putting it out there (don't know if it's related or not)..  so for the last few weeks the computer will not display the login screen after lifing the lid. What I mean is if I just close the lid on the laptop then come back later maybe a few hours later or whatever then when I lift the lid the screen just stays blank and does not change to the login screen. I end up having to hard
[22:46] <blahboybaz> boot to get the login screen again
[22:46] <oerheks> after your last update run, did you reboot?
[22:46] <blahboybaz> sarnold: I see. Must be a major release then
[22:47] <oerheks> if /var/run/reboot-required  exists, reboot, and you can continue updating
[22:47] <blahboybaz> oerheks: probably.. I think? but have not run the upgrade we are talking about here now though
[22:47] <oerheks> so, why are you afraid of updates?
[22:48] <blahboybaz> oerheks: I investigate anything the seems odd as a matter of prectice
[22:48] <sarnold> so strange that they haven't posted release notes on https://www.mono-project.com/docs/about-mono/releases/
[22:48] <sarnold> maybe they'll get to it
[22:49] <blahboybaz> this all sounds normal so I'll run my upgrades, reboot, and return here. I'd like to ask about my other issue then if anyone would be so kind  :)
[22:49] <blahboybaz> peace out for a minut
[23:16] <blahboybaz> Well the thing didn't blow up yet
[23:16] <blahboybaz> Ubuntu 20.04.. After I close the lid on my laptop and then return later I want the login screen to appear after I open the lid again. Instead all I get is a black screen and it doesn't matter if a press a key or move the mouse - nothing makes it show the login screen again. What do I do?
[23:17] <blahboybaz> correction the pointer is visible above the black screen and can be moved around but it doens't change the login screen not appearing
[23:18] <sarnold> blahboybaz: is it suspending or hibernating or something at the same time?
[23:19] <sarnold> blahboybaz: maybe try loginctl lock-session or systemctl suspend, systemctl hibernate, systemctl hybrid-sleep, etc, and see if running some of these commands replicate the same problems or not
[23:19] <blahboybaz> sarnold: I have no idea but I do have some kind of (tty?) output that I took a picture of. It can be seen after pushing F5 when this happens. Pressing F5 again returns to the aformentioned condition. I'll paste a link to that pic
[23:24] <blahboybaz> I have this..
[23:24] <blahboybaz> https://imgur.com/xMUhfYW
[23:24] <sarnold> those are probably just holdovers from bootup
[23:26] <blahboybaz> sarnold: I see
[23:27] <blahboybaz> sarnold: fwiw I have added a pic of settings (the only settings secsion I know of that may have something that could cause the sitch)
[23:27] <blahboybaz> secsion\section
[23:28] <sarnold> blahboybaz: do you have to do something to share that other picture? https://imgur.com/xMUhfYW still looks like one photo to me, not a gallery
[23:28] <blahboybaz> https://imgur.com/R7Wt1oE
[23:29] <blahboybaz> sorry I didn't realize till now
[23:29] <sarnold> heh dang, not a ton of info there :(
[23:29] <sarnold> try those different commands ^^ and see if any of them cause similar problems?
[23:30] <blahboybaz> oh sorry I didn't see that. I'll try that out
[23:34] <blahboybaz> sarnold: Those seem to be commands to configure something. Is that right? Do you think there is any way to diagnose what is going on?
[23:34] <blahboybaz> Some way to investigate?
[23:34] <sarnold> blahboybaz: all those commands execute something immediately
[23:35] <sarnold> blahboybaz: I'm hoping the consequences of executing them will give some hints
[23:35] <blahboybaz> sarnold: so it is not persistent for any of them?
[23:35] <sarnold> blahboybaz: right
[23:36] <sarnold> blahboybaz: to make them persistent you'd fiddle witrh the HandleLidSwitch= and similar keys in https://www.freedesktop.org/software/systemd/man/logind.conf.html#HandlePowerKey=
[23:36] <blahboybaz> Ok. It may cause me to have to reboot (which is fine). I'll lose my connection to irc if that happens so I'll return if any of them replicate the condition and let it be known
[23:37] <sarnold> yeah, it might not be *fun* :)
[23:43] <blahboybaz> sarnold: what do you call the screen prior to the login screen? The first one that comes up before you hit a key to make the login field appear?
[23:43] <blahboybaz> splash screen?
[23:53] <sarnold> blahboybaz: perhaps plymouth?
[23:56] <cluelessperson> How can I disable a very specific media key?
[23:56] <cluelessperson> specifically the "favorites" media key
[23:58] <matsaman> cluelessperson: and do what instead?
[23:59] <cluelessperson> matsaman, I want to map that key within another application
[23:59] <cluelessperson> so I want to disable the favorite media key function, but know still that it was pressed.