| [01:43] <lotuspsychje> good morning | |
| [01:44] <arraybolt3[m]> lotuspsychje: Good... well it's almost night here, but good morning! | |
| [01:44] <lotuspsychje> hey there arraybolt3[m] | |
| [01:44] <lotuspsychje> where are you located? | |
| [01:44] <lotuspsychje> here's belgium @ 3h44 | |
| [01:44] <arraybolt3[m]> lotuspsychje: Central USA | |
| [01:45] <lotuspsychje> cool | |
| [01:45] <arraybolt3[m]> 8:44 PM here | |
| [01:45] <lotuspsychje> oh you still got a few hours support left hehe | |
| [01:48] <arraybolt3[m]> Random conversation starter: The current mess around systemd-oomd could be solved by simply enabling the Magic SysRq OOM killer trigger (Alt+PrtScrn+F I believe). When the system is nearing low memory, Ubuntu could simply pop up a window stating "The system is reaching a dangerously low level of free memory, and may lock up soon. If this happens, hold down the Alt key, then press PrtScrn, followed by F." Even if the system did | |
| [01:48] <arraybolt3[m]> lock up, the user would be staring at the solution, and could instantly unlock their system with one key combo. This would solve the problem entirely, at least on desktop Ubuntu. | |
| [01:49] <arraybolt3[m]> https://unix.stackexchange.com/questions/127193/kill-the-biggest-process-button | |
| [01:50] <lotuspsychje> think i saw recent bug(s) about systemd-oomd | |
| [01:50] <lotuspsychje> cant recall their ID | |
| [01:51] <arraybolt3[m]> There's an entire discussion on the ubuntu-devel mailing list regarding this problem, I tried to mention this solution but it looks like it got overlooked. | |
| [01:52] <lotuspsychje> bug # 1969248 is one | |
| [01:52] <lotuspsychje> bug #1969248 | |
| [01:52] <ubottu> Bug 1969248 in systemd (Ubuntu) "Systemd-oomd frequently kills applications on 8GB RAM machine" [Undecided, New] https://launchpad.net/bugs/1969248 | |
| [01:53] <Bashing-om> arraybolt3[m]: Developer's discussion: systemd-oomd issues on desktop >> https://lists.ubuntu.com/archives/ubuntu-devel/2022-June/042116.html . | |
| [01:54] <lotuspsychje> nice Bashing-om +1 | |
| [01:55] <arraybolt3[m]> Bashing-om: Thanks. Looks like my messages never made it through. Guess they don't want non-devs interfering with the conversation, but I thought my solution was pretty good. | |
| [02:00] <Bashing-om> arraybolt3[m]: Lemme check - think was on Discouse the developers have a thread open for suggestions. | |
| [02:03] <Bashing-om> arraybolt3[m]: NO- guess I had my wires crossed :( | |
| [02:05] <arraybolt3[m]> Oh well. They'll figure something out, I'm sure. | |
| [02:09] <lotuspsychje> 22.04.1 surely will solve a lot of issues | |
| [06:52] <ducasse> good morning all | |
| [12:58] <lotuspsychje> in wich cycle would kernel 5.18 arrive on ubuntu? | |
| [14:11] <hggdh> probably will not be made available. 22.10 will use 5.20, or 6.0/6.1, or whatever | |
| [14:14] <lotuspsychje> tnx hggdh | |
| [14:15] <lotuspsychje> ill test a kinetic once it reaches 5.20 then | |
| [14:29] <hggdh> usually a new kernel comes late in the cycle | |
| [14:34] <lotuspsychje> !info linux-image-generic kinetic | |
| [14:34] <ubottu> linux-image-generic (5.15.0.27.30, kinetic): Generic Linux kernel image. In component main, is optional. Built by linux-meta. Size 3 kB / 19 kB. (Only available for amd64, armhf, arm64, powerpc, ppc64el, s390x.) | |
| [14:34] <lotuspsychje> a bit of waiting game then | |
| [14:41] <Eickmeyer> oem in jammy is 5.17 | |
| [14:42] <hggdh> yeah, OEM is... different | |
| [18:24] <arraybolt3[m]> Out of curiosity, what's the point of a newer kernel? Does it have any visible effect for the end user? | |
| [18:27] <arraybolt3[m]> (My Ubuntu experience with kernel 5.8 on Focal is pretty much identical to my experience with kernel 5.15 on Kinetic, except for if you install kernel 5.8 on Kinetic, it breaks Snaps.) | |
| [18:28] <arraybolt3[m]> (I guess new drivers and support for stuff like exFAT comes in newer kernels, so there's that.) | |
| [18:32] <tomreyn> exactly that - support for newer hardware and features | |