[09:07] <kubuntu> Helloworld
[09:07] <kubuntu> howsworld
 Pls? (re @trevantee: Am I the only one that gets random crashes on kde 22.04 what is that all about?)
 ? (re @trevantee: And is it advisable to move to 22.10)
 I think the 22.04 LTS is more stable (re @trevantee: ?)
 Yiu have to provide more info so you can get help (re @trevantee: Pls?)
[09:43] <guruprasad> I have my locale set to `en_IN.UTF-8` in `/etc/default/locale` on my Kubuntu 22.10 (with the latest Plasma version from the backports PPA). This works as expected in tty sessions. But when I log in to Plasma, the Regional settings complained about there not being a language en_IN or something like that
[09:43] <guruprasad> I searched for it in the dropdown but as I couldn't find it, I set it to American English.
[09:44] <guruprasad> Now when logged into Plasma, if I open Konsole and run the `locale` command, it shows `LANG=en_US.UTF-8` and a few other locale related variables are set to it as well, while the rest of them are en_IN without the .UTF-8 suffix.
[09:45] <guruprasad> I do not understand what is happening here and how to fix it to use en_IN.UTF-8 everywhere uniformly.
[09:45] <guruprasad> Any ideas/suggestions to figure out this issue?
[12:54] <BluesKaj> Hi all
 Okay, while using my kubuntu 22.04, sometimes it just gets to a point where it just freezes completely (re @Omar: Yiu have to provide more info so you can get help)
 Sort of like a crash….and I won’t be able to take anything out of the screen nor do anything till I log out
[13:00] <BluesKaj> @trevantee, I have to ask. Have you updated and upgraded your packages lately ?
 😇 for all with iGPU's the friendly reminder to set the videomem to a fixed value within the bios settings..
 Yes I did (re @IrcsomeBot: <BluesKaj> @trevantee, I have to ask. Have you updated and upgraded your packages lately ?)
 Yes I have (re @IrcsomeBot: <BluesKaj> @trevantee, I have to ask. Have you updated and upgraded your packages lately ?)
[18:20] <massimo> yoooooooo
 Plasma shell crash? (re @trevantee: Sort of like a crash….and I won’t be able to take anything out of the screen nor do anything till I log out)
 Not even a terminal? (re @trevantee: Sort of like a crash….and I won’t be able to take anything out of the screen nor do anything till I log out)
[20:25] <TomTom> Hmm is there a reason (or can it be changed) why the audio devices show the pipewire node-description instead of the node-nick? The nick contains the more useful information, e.g. the name of the monitor connected, otherwise its just the enumerated long name of the graphics card audio sink
[20:26] <TomTom> you can check it with `wpctl status` and `wpctl inspect $ID||grep "node"`
[20:26] <TomTom> single pipe of course...
 Why? There's no such option on laptops (re @JoDoGo42: 😇 for all with iGPU's the friendly reminder to set the videomem to a fixed value within the bios settings..)
 the chipset itself has that option, the question is if the provider gave you a bios frontend which has a button where you could change that.
 Patching bioses with different (full featured) bios interfaces isnt really complicated but needs very specific knowledge to not brick your device by changing the biosversion.
 Nowadays unfortunately many oem's tend to opt those settings out presuming the users, all willing to have just windoze shards in bios and on disk anyways, wont need such anyways as the oem iGPU drivers have perfect auto capabilities.
 For un*x thats unfortunately not always true and kernels tend to hang, stall or at least pause when memory they expect at place a isnt there anymore or somewhere else randomly. Most un*x drivers dont come from the oems but from the community devs doing remarkable jobs in understanding the vastly different and divers ideas of oem's to wire chipsets with mem and gpu's or other subparts which are building the specific machine you bought. Apart 
 Oems are getting win low lvl libs with workarounds just when they order off the shelf and usually dont know those details as well - how can community devs then?
 So in short, win machines sold as win machines will run (at least the first some days, weeks or even months flawlessly, no matter how buggy the used hardware is - as most oems have contracts with ms the drivers will stay compatible and sound as long those contract periods are active. Luckily over time the un*x devs follow up and older hardware usually works pretty well then.
 usually chk your bios within advanced, igpu assigned (video memory) Its defaulted to auto. When you dont play heavy 3D stuff set it to a somewhat low possible fixed value, when you game with it, set it to the bigger values - but in general, just set it to a fixed value - a real huge number of completely strange problems can be broken down to this random memory occupation under auto mode
 ps, even if you dont encounter issues give it a try as randomly moving mem areas around takes time as well - you may even gain a slightly better resposiveness of your system 😁
[22:15] <fsflp23> Does anyone know if the ISO image includes KDE Skanlite or GNOME Document Scanner/Simple Scan apps?
[22:34] <arraybolt3> fsflp23: I'll check real quick.
[22:34] <arraybolt3> fsflp23: Skanlite is included, according to https://cdimage.ubuntu.com/kubuntu/releases/22.04.2/release/kubuntu-22.04.2-desktop-amd64.manifest.
[22:38] <fsflp23> Thanks so much!!  I didnt know about that link you gave, good to know about it.  I was hoping for Skanlite......
 Note for self to remember to do in. Someone else has advised me about this too! (re @JoDoGo42: 😇 for all with iGPU's the friendly reminder to set the videomem to a fixed value within the bios settings..)
 Sometimes my PC reaches 100% CPU load and stay there for some minutes (I am a patient boy! I wait, I wait and I wait) and it recovers itself. (re @trevantee: Sort of like a crash….and I won’t be able to take anything out of the screen nor do anything till I log out)
 It can take up to 10 min, but I'd rather wait than to restart everything to get up my work flow setup and running again.
 I have never found any obvious cause.