=== javi404_ is now known as javi404 | ||
oerheks | yes | 01:11 |
---|---|---|
=== genii_ is now known as genii | ||
=== mrbutthead19587 is now known as mrbutthead1958 | ||
=== timj3 is now known as timj | ||
yogaum | Hello | 06:10 |
=== mrpond1 is now known as mrpond | ||
Guest83 | 😀 | 08:21 |
l0k1 | Hi, i have a question to hibernation and secure boot. My notebook can't enter the hibernation when i close the lid. I can see in the journal: "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7". Is there any workaround to get hibernation working? | 09:50 |
=== ramblebamble is now known as ramblebamble_afk | ||
yogaum | Hello | 11:38 |
yogaum | Anyone active? | 11:38 |
mgedmin | l0k1, please don't leave before you get a chance to hear an answer to your question | 11:52 |
=== ramblebamble_afk is now known as ramblebamble | ||
Elisa | hi | 12:42 |
BluesKaj | Hi all | 12:45 |
=== jimmyb5 is now known as jimmyb | ||
deadrom | what's ubuntu server's default retention policy for old kernels? | 14:12 |
mgedmin | same as ubuntu desktops, I think -- it tries to keep two of them, for every flavor (-generic etc) that you have installed | 14:13 |
oerheks | 2 | 14:15 |
oerheks | some reading , https://askubuntu.com/questions/620266/how-does-apt-decide-how-many-old-kernels-to-keep | 14:16 |
deadrom | 2 is what I had in mind, still I hear here that the colleagues had to clear up manually as a 2GB /boot was crammed with old kernels. Let me read up then.. | 14:24 |
pragmaticenigma | deadrom: creating a /boot partition is an old practice that is not necessary any more, unless you are doing full drive encryption which depending on configuration may still require it | 14:26 |
oerheks | deadrom, when you switch to HWE, the old kernel tree stays and gets updates too, IIRC | 14:27 |
pragmaticenigma | deadrom: if you accepted defaults during an Ubuntu install, there will not be a /boot partition on your machine, and thus no need to worry about sapce | 14:27 |
deadrom | deplyoment is configured like that | 14:27 |
deadrom | no hwe, vms | 14:27 |
pragmaticenigma | deadrom: they should stop doing that... it's not necassary on modern hardware | 14:28 |
deadrom | well, I'll rather have boot run full than / | 14:28 |
deadrom | ok, / is monitored, true, but whether the mechanism fails on /boot or / -- I'd like the system to only keep 2 kernels around at any rate | 14:29 |
deadrom | but technically: we hab /boot around for decades for a reason, what reason went away that "forget /boot" is the new gospel? | 14:30 |
deadrom | s/hab/had | 14:31 |
pragmaticenigma | With UEFI firmware, it is no longer needed. /boot is from a time when the computer would search a specific area of the harddrive for the boot strap code, after post | 14:31 |
LACERDA | OLA | 14:33 |
oerheks | :-) | 14:33 |
deadrom | the system would look at the boot drive's first secotrs and usually find a boot loader there. in case of grub that would hold the info where to search the kernel image | 14:34 |
deadrom | so technically, you didn't have to have /boot on legacy systems either, it was more of a "leave the essential stuff untouched" thing. Which I still think is a good idea. | 14:35 |
deadrom | I remember /boot on ext2 as no need for ext4 journals on it, for example, or to boot bare metal to raid from a usb thumb etc | 14:36 |
pragmaticenigma | that is wrong, but this isn't the place to debate it further | 14:39 |
deadrom | if not here where else? | 14:39 |
mgedmin | #ubuntu-discuss, probably | 14:40 |
mgedmin | or #ubuntu-offtopic | 14:40 |
deadrom | disagree. I have an issue at hand and need to solve long run. I get told my ways are deprecated but no why, I get told my statements are wrong but not how. | 14:41 |
pragmaticenigma | deadrom: you had no issue, your original inquery was for information which you received | 14:41 |
pragmaticenigma | you asked how many kernels are retained, the answer is 2, for each "class" or "flavor" of kernel on your machine. -general, -hwe, etc | 14:42 |
deadrom | and had you read up you would have seen that I have an issue at hand, which now on top of all you deny. you know what, let someone else. | 14:43 |
pragmaticenigma | I have read... the only "issue" you noted was that coleagues have had to do clean up. That doesn't say you are experiencing an issue. | 14:43 |
deadrom | this is ridiculous. | 14:44 |
pragmaticenigma | The fix, if it is a concerns is to stop installing with a dedicated /boot partition. Kernel is progressively getting larger and larger with each version. there is no way to know how large each kernel will be, so the solution is to stop making a /boot partition | 14:44 |
pragmaticenigma | deadrom: if you have a specific issue with your installation, then actually state the problem you want help with. If you're not experiencing a problem, there is nothing that can be offered to you to fix what isn't broken | 14:50 |
leftyfb | deadrom: all of my ubuntu servers have only 2 kernels installed as intended | 14:54 |
leftyfb | deadrom: what release of ubuntu are you running? | 14:54 |
deadrom | leftyfb, well, there's situations in which old kernel packages may get marked not to be auto-removed from what I gather. it's a 22.04 and I think it might have been upgraded from 20.04, something I don't recommend for production servers yet here we are. I'll try and see what was removed... | 14:55 |
leftyfb | deadrom: which kernels are installed? | 14:56 |
deadrom | sheesh... those gt purged now https://paste.debian.net/1348734/ and installed right now are... hang on | 14:58 |
leftyfb | deadrom: also, you know the only way the old kernels get automatically removed is by running "sudo apt autoremove" right? | 14:58 |
deadrom | vmlinuz-5.15.0-126-generic and -131-generic | 14:58 |
leftyfb | deadrom: also, 5.15 is not the ubuntu 22.04 HWE kernel | 14:59 |
deadrom | let's clarify HWE: for VM ops, would I want hwe? | 15:00 |
leftyfb | yes | 15:00 |
leftyfb | 5.15 was released almost 4 years ago | 15:00 |
deadrom | well yes, and it's the kernel that shipped with 22.04 isn't it? | 15:01 |
leftyfb | yes, and is outdated | 15:02 |
leftyfb | you're not even running the latest 5.15 available in ubuntu 22.04 | 15:02 |
leftyfb | oh wait, maybe you are | 15:03 |
leftyfb | still | 15:03 |
leftyfb | the HWE kernel is highly recommended | 15:03 |
leftyfb | which is currently at 6.8.0-52 | 15:03 |
deadrom | The 5.15 GA kernel is supported until April 2027. I don't see an issue. | 15:03 |
leftyfb | better hardware support, more efficiency, possibly bug fixes | 15:06 |
deadrom | java application servers, on-prem not exposed, they work, as long as nobody complains I'm not gonna install new kernels. more likely to intro new api issues with java than anything. never touch a running system. | 15:07 |
leftyfb | goodl uck | 15:07 |
leftyfb | good luck* | 15:07 |
deadrom | all fine. only need to figure why the old kernels don't get removed. I'll check the autoremove thing, that's solid to go after. not my deployment, so... | 15:09 |
deadrom | leftyfb, hang on, if default policy is to retain 2 kernels, why do I still need to setup autoremove? Wouldn't the 2 kernel policy be enforced by system defaults then? | 15:30 |
oerheks | no need for autoremove, next update run will remove them automaticly | 15:33 |
oerheks | you could do that in the same session | 15:33 |
deadrom | oerheks, please clarify: will invoking update automatically invoke autoremove as well? | 15:35 |
pragmaticenigma | if you perform update from GUI yes, if you perform update from command line, no | 15:36 |
oerheks | correct, the gui shows that | 15:41 |
oerheks | oh wait, you are on server. then no | 15:41 |
=== NDPZenB00k is now known as NDPZenBook | ||
deadrom | oerheks, that could be the explanation. I'll add it to /arr/spool/apt-mirror/var/postmirror.sh and observe | 15:56 |
Guest7 | what is more secure - ubuntu or debian? | 16:17 |
oerheks | both are | 16:18 |
oerheks | what answer would you expect in the ubuntu support channel? | 16:18 |
leftyfb | Guest7: feel free to discuss non-support topics in #ubuntu-offtopic | 16:18 |
oerheks | the only culprit is the user 🤠| 16:18 |
=== Guest5857 is now known as larkon | ||
ogra | Well, the answer here is clearly Ubuntu ... debian does not do security support for its whole archive while Ubuntu does now (with pro enabled) ... | 16:44 |
pragmaticenigma | ogra: Do you have a support question? | 16:45 |
ogra | heh, no :) | 16:45 |
=== richardla is now known as Bueford | ||
janskey | i connect my bluetooth speaker, but the volume keyboard control doesn't work the volume. any idea? | 17:10 |
pragmaticenigma | keyboard control will not control the speaker directly. the keyboard can only change the audio output of the computer's own sound output | 17:14 |
=== hjgkhgf6436f is now known as GSP | ||
janskey | @pragmaticenigma thats odd, why does it work with other linux distro? i've tested with Linux Mint and it works. | 17:23 |
pragmaticenigma | the way you phrased your question, it appears you expect the keyboard to directly control your speaker, which it cannot do. | 17:24 |
janskey | so is it possible or not? | 17:25 |
pragmaticenigma | as your question is phrased, no | 17:26 |
oerheks | did you select the right keyboard? settings>keyboard | 17:26 |
janskey | are you referring the layout? | 17:27 |
janskey | its English (US), default. | 17:28 |
ogra | and the right audio output in the settings ? pulseaudio did not always pick up output changes in the past so the volume control will keep controlling line out while BT or HDMI is ionm use | 17:28 |
ogra | (pipüewire should be better at that though) | 17:28 |
leftyfb | janskey: to be clear, the keyboard sound control will control the volume output of your computer, regardless if the output is hardwired speakers or bluetooth. The volume output to your bluetooth speaks will be adjusted accordingly. But The volume controls will not control any separate volume controls on the speaker itself | 17:29 |
ravage | Did not know there is a German fork :D | 17:29 |
pragmaticenigma | ogra: default sounds system is pipewire in newer editions of Ubuntu | 17:29 |
ogra | pragmaticenigma, i'm well aware | 17:29 |
ogra | pragmaticenigma, we switched it in 22.04 ... so 20.04 might have such issues ... | 17:31 |
janskey | fyi i'm using macbook, so is it possible to configure to control it via keyboard? | 17:32 |
leftyfb | janskey: open up your sound settings | 17:34 |
ogra | janskey, open the settings, go to audio and check what output your system uses | 17:34 |
pragmaticenigma | janskey: as already mentioned, the volume control only affects the system sound output. It cannot control the bluetooth speaker's onboard volume control. | 17:34 |
janskey | @ogra it uses bluetooth output | 17:35 |
leftyfb | janskey: when you press volume up or down, do you see an onscreen popup that shows the volume going up and down? | 17:35 |
janskey | @leftyfb yes, pop up shows. it also change the built-in volume but not the bluetooh. | 17:36 |
ogra | then it should also control the system output stream to that ... you could try switvching back and forth between outputs to see if that helps | 17:36 |
leftyfb | it will change the output going to the bluetooth device | 17:36 |
pragmaticenigma | janskey: you have to manually set the volume of the bluetooth speaker, then the output level from the computer can be adjusted by the keyboard/system controls | 17:37 |
janskey | if i press the keyboard volume up/down, it only change the built-in output in the PulseAudio. but when i press the belutooth speakers volume physically, thats where the PulseAudio audio controls also change. | 17:39 |
janskey | so maybe the keyboard needs to know if there is a speaker connect, it will map to the bluetooth device instead. | 17:40 |
leftyfb | that's not how this works | 17:41 |
janskey | probably this can be configured? | 17:41 |
pragmaticenigma | it will never work that way | 17:41 |
leftyfb | the keyboard doesn't know or care about bluetooth at all | 17:41 |
ogra | no, the keyboard only talks to pulseaudio (or pipewwire if you are on a more recent release) | 17:41 |
ogra | the sound server then controls the stream volume going to whatever device ... | 17:41 |
janskey | @ogra if thats true, then how did linux mint and mx linux made it work? i tested it on both distro. | 17:42 |
pragmaticenigma | They didn't | 17:42 |
ogra | no idea, you might have found a bug | 17:42 |
leftyfb | but not a bug in the way you think it is | 17:42 |
oerheks | on what desktop? .. | 17:42 |
pragmaticenigma | They 100% did not control your speaker in the manner you think they did | 17:42 |
oerheks | pulseaudio or pipewire? | 17:42 |
ogra | right, thesy will also do the exact same thing ubuntu does ... control the volume of the audio stream | 17:43 |
oerheks | gnome extention to control different output devices , up to gnome 44 https://extensions.gnome.org/extension/6036/advanced-volume-control/ | 17:43 |
leftyfb | janskey: when you go to settings -> bluetooth >- your bt device .... what does it say under "Type"? | 17:44 |
janskey | i'm not sure the type, i dont see. | 17:46 |
janskey | this one? | 17:46 |
janskey | /org/bluez/hci0 | 17:46 |
yetitwo | hello! i'm trying to install neovim on a new machine. i've done `sudo add-apt-repository ppa:neovim-ppa/unstable` and i've verified that the repo is being queried when i run `sudo apt update`. when i do `sudo apt info neovim`, it points at `oracular/universe` in the ubuntu archive, not the PPA that i just added. when i do `sudo apt-cache policy`, | 17:47 |
yetitwo | the new PPA isn't present at all. I tried adding an entry to `/etc/apt/preferences.d/`, but that doesn't seem to have helped. any idea on what to check next? | 17:47 |
leftyfb | janskey: open settings | 17:47 |
leftyfb | yetitwo: you'll need to contact the PPA owner for support with their package | 17:47 |
yetitwo | and to clarify: i want the PPA and not the one packaged by ubuntu because the ubuntu archive is behind a version and treesitter isn't compatible with the version | 17:47 |
pragmaticenigma | yetitwo: 3rd party software is not supported here, you will have to contact the mainter of the repository for suppotr | 17:47 |
janskey | yes, i'm the bluetooth settings already. | 17:47 |
yetitwo | ... it worked on my previous machine | 17:47 |
yetitwo | and this seems to be an issue with apt, not with the PPA | 17:48 |
pragmaticenigma | !latest yetitwo | 17:48 |
leftyfb | yetitwo: the issue is the PPA doesn't support the release you are running | 17:48 |
leftyfb | which is an issue with the PPA | 17:48 |
yetitwo | https://launchpad.net/~neovim-ppa/+archive/ubuntu/unstable shows 24.10, and that's what i'm running | 17:48 |
leftyfb | it got updated 6 hours ago, maybe it's not fully supported yet | 17:49 |
leftyfb | contact the PPA owner for support | 17:49 |
yetitwo | it's a nightly build | 17:49 |
yetitwo | it's going to be updated nightly | 17:50 |
oerheks | yetitwo, run update & upgrade, it would update to v10 | 17:50 |
yetitwo | again, this seems to be an apt issue, not an issue with the PPA | 17:50 |
yetitwo | or else please let me know what i can do as further troubleshooting steps | 17:50 |
pragmaticenigma | yetitwo: the problem is the PPA owner has something misconfigured... no support here | 17:50 |
oerheks | always run proper updates before adding a PPA | 17:50 |
yetitwo | i've run update multiple times | 17:51 |
pragmaticenigma | yetitwo: there is nothing more to the command to add a PPA... after that it is the PPA's owner's responsibility to make sure items are in their repository, which they don't appear to be in the right places. | 17:51 |
oerheks | https://launchpad.net/~neovim-ppa/+archive/ubuntu/unstable | 17:51 |
yetitwo | is there any way that i can figure out *what* is misconfigured on my side so that i know what to communicate to the ppa? | 17:51 |
yetitwo | ppa maintainer* | 17:51 |
oerheks | pastebin your update run? | 17:51 |
yetitwo | https://hastebin.com/share/papexajoze.less | 17:52 |
pragmaticenigma | yetitwo: as you said, it's not finding the package... so probably inform them that they're 24.10 release is not in the correct location for their PPA | 17:52 |
yetitwo | wouldn't that 404 in the update? | 17:52 |
yetitwo | that's the behavior i've seen in the past | 17:52 |
leftyfb | yetitwo: I just spun up an oracular machine and added the PPA. The package is not available for this release. Please contact the PPA owner for support | 17:53 |
oerheks | weird, it shows https://launchpad.net/~neovim-ppa/+archive/ubuntu/unstable?field.series_filter=oracular | 17:54 |
yetitwo | hmm yeah | 17:55 |
yetitwo | looks like a build failure | 17:55 |
yetitwo | https://launchpad.net/~neovim-ppa/+archive/ubuntu/unstable/+packages | 17:55 |
yetitwo | leftyfb: thank you | 17:55 |
oerheks | oh, Waiting to build | 17:58 |
leftyfb | [12:49:27] <leftyfb> it got updated 6 hours ago, maybe it's not fully supported yet | 17:58 |
ogra | FWIW you can as well just do "sudo snap install nvim --classic" the snap is well maintained and updated regulary | 18:19 |
ogra | (in fact i think it is maintained by upstream) | 18:20 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!