[00:01] whenever this happens forcing power off is the only way to restart [00:01] brb, doing so [00:01] hmm [00:02] earlier kernel sounds like a good first step [00:06] sorry, where do i look againg in the log? [00:07] See /var/log/syslog for most messages; tail -f /var/log/syslog [00:07] will show running messages === stuffandthings30 is now known as stuffandthings [00:14] test [00:14] hu weird didnt know my computer had this app [00:15] now you do 😉 [00:15] so we just hop servers cool [00:20] i get things like: 2023-12-03 7:19 P.M. kernel rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 4-...D } 153643 jiffies s: 785 root: 0x10/. [00:21] 2023-12-03 7:19 P.M. kernel NMI backtrace for cpu 4 skipped: idling at intel_idle_ibrs+0x94/0x130 [00:21] stuffandthings: Are you running on an earlier kernel now? [00:21] Or is this the default [00:21] ? [00:21] not yet, ill be downgrading in about 40min [00:21] Like the one that was running when the system stalled? [00:22] 6.5.0 [00:22] but even 6.5.11 was fine [00:22] You can boot into it an test before removing the latest; the kernel is just an easy test, but not necessarily the source of the issue. [00:22] or whatever it was [00:22] So you can revert back in grub [00:22] just press right-shift on boot, and then select the earlier kernel. [00:23] i just use the app called mainline to change it [00:23] ok [00:23] not familiar with that. [00:26] kk, bb [00:26] thanks for your time [00:27] no worries, best of luck. [01:16] mmikowski: it's a ATX motherboard personal computer hooked up to a monitor via HDMI (& have a ANKER bluetooth speaker) [01:50] Anybody knows when will Kubuntu get an update kernel to 6.6 ? [01:50] The problem below seems to be fixed in the new version mentioned above: [01:50] https://forum.manjaro.org/t/sound-not-working-in-asus-rog-strix-g16-2023-g614ju/147761 [01:50] https://forum.manjaro.org/t/missing-sound-on-asus-rog-strix-g713pv-after-update-from-kernel-6-6-0-to-6-6-1-and-6-6-2/152486 [01:50] Anybody knows when will Kubuntu get an update kernel to 6.6 ? [01:50] The problem below seems to be fixed in the new version mentioned above: === fusion1181_away is now known as fusion1181 [02:34] @ArsonSteam, I see 6.6 kernel in -proposed for my release currently; but it'll be some time before it floats to an older jammy via HWE for example (jammy soon to get 6.5 being next) [02:37] i am using kubuntu 23.10 and kernel 6.5 [02:37] Is it ok to download the .deb packages from https://kernel.ubuntu.com/ [02:37] and install them [02:38] i wanna follow this guide [02:38] https://itsfoss.com/upgrade-linux-kernel-ubuntu/ [02:38] is it safe to do so ? [02:39] what is this IrcsomeBot relaying from? [02:44] You mean my messages ? (re @IrcsomeBot: what is this IrcsomeBot relaying from?) [02:44] I am using Telegram [02:52] ArsonSteam, aaah ok and someody put in IrcsomeBot here which is relaying to/from (at least) telegram, apparently. [03:18] i'm getting soft lockups daily in plasma on 23.10. i can see in the syslog that i have a cpu that gets stuck. the process seems to be kwin_wayland. anyone know anything about this? would logs be useful to submit somewhere? [03:18] kernel: [908024.365819] watchdog: BUG: soft lockup - CPU#8 stuck for 2392s! [kwin_wayla:cs0:853215] [03:19] and stack trace or whatever follows [04:09] what vertion is the best === fusion1181 is now known as fusion1181_away === popey0 is now known as popey [05:41] imbezol Sorry for playing Captain Obvious, but is kwin_x11 an option? === guiverc2 is now known as guiverc === root is now known as Guest6506 [13:11] Hi all === fusion1181_away is now known as fusion1181 === vcxza is now known as p4aoo [15:23] Hi, i've a problem with kubuntu 22 LTS. It was added to an active directory but on the gui login page i can't see the user [15:23] It's uid is too high [15:23] How can i resolve? [15:41] bonjour  j ai t 420 et j ai installé kubuntu 22.4 comment maiter le lecture d'empreintes merci === fusion1181 is now known as fusion1181_away === fusion1181_away is now known as fusion1181 [17:52] so far its looking like it was the kernel, for me, old kernels doing okay === fusion1181 is now known as fusion1181_away === jcea1 is now known as jcea === Bluefoxicy_ is now known as Bluefoxicy === fusion1181_away is now known as fusion1181