[01:40] <lexandrop> Hi. In Kubuntu 20.04, when I plugged in my wired headset, microphone automatically changed to that wired one. In Kubuntu 22.04 it doesn't happen anymore (not sure, from the very beginning or after some update).
[01:41] <lexandrop> Before trying to dig into details myself, I have a question: did anyone else face the same problem? Is it an intended change, or is it a bug, etc.? Any advices maybe?
[01:42] <lexandrop> P.S. I can manually select headset microphone both via pavucontrol and via KDE audio settings, the problem is only about "automatically".
[01:46] <lexandrop> P.P.S. Output automatically switches to headset correctly. Only input doesn't.
=== chris is now known as Guest9720
[09:23] <karsten_> Hello! Ive installed kernels 5.15.0-56-generic and a custom one that wont start, but compiled with same .config as the generic one. Why the custom kernel is more than seven times bigger than the generic one?
[09:24] <karsten_> source for the custom is 5.15.85
=== Lord_of_Life_ is now known as Lord_of_Life
[12:06] <IrcsomeBot> <pu7n1k> bjuw
[12:12] <IrcsomeBot> <pu7n1k> anyone else with Telegram (webz) screen sharing (group -> video chat -> share screen - window/tab) issue on Kubuntu 22.04.1 LTS x86_64 ?
[12:21] <Kangarooo> Hello! Bug here maybe computer slow because he is indexing all files that are copied to it and its 100gb of files? its old computer also. But it has ubuntu sticker so it was for ubuntu so i put kubuntu
[12:21] <Kangarooo> very unresposive
[12:21] <Kangarooo> how to know if some process is doing there something? system monitor seems not showing that
[13:34] <cbreak> Kangarooo: it should show something
[13:34] <cbreak> if it's indexing, it's probably that baloo thing
[14:16] <BluesKaj> Hi all
=== adi_ is now known as adi__
[16:00] <DreadKnight> heya! had problems logging in for some reason, had to run a fsck from that openbox thingy; now my plasmashell won't start. I'm getting this stuff... plasmashell: error while loading shared libraries: libKUserFeedbackCore.so.1: cannot open shared object file: No such file or directory
[16:03] <genii> DreadKnight: You might try: sudo apt-get update && sudo apt-get install --reinstall libkuserfeedbackcore1
[16:04] <DreadKnight> genii that did the job, woot! I was thinking earlier to go for some "reinstall" command, since removing and adding again is a bit more scary. Thanks! :-)
[16:05] <genii> Glad to be of assistance
[16:06] <DreadKnight> learned something useful. Time to properly log into session now. Laters!
[17:29] <user|92> Hello. I need upgrade ubuntu 21.10 to lastest version, but i dont know how
[17:30] <cbreak> user|92: 21.10 is out of support :/ the updates aren't available the normal way I think
[17:31] <cbreak> https://help.ubuntu.com/community/EOLUpgrades
[17:31] <oerheks> !eolupgrade
[17:31] <ubottu> End-Of-Life is when security updates and support for an Ubuntu release stop. Make sure to update Ubuntu before it goes EOL so you get updates promptly for newly-discovered security vulnerabilities. See https://help.ubuntu.com/community/EOL and https://wiki.ubuntu.com/Releases for more info. Looking to upgrade from an EOL release? See https://help.ubuntu.com/community/EOLUpgrades
[17:31] <cbreak> you should decide whether you want to go to 22.04 or 22.10
[17:32] <oerheks> i would stick to LTS
[17:32] <user|92> thanks
=== Hi is now known as Guest4063
[20:35] <user|48> Hi all.  I just completed the update from 20.4 to 22.4 and now when I log in, it boots to kodi....
[20:41] <oerheks> logout, and login with the correct user?
[20:44] <user|48> Yup.
[20:45] <user|48> I restarted and logged back in.  Now kodi seems to be my "windows" manager.
[20:50] <user|48> I did 3 machines at once and they all have this problem.
[20:54] <user|48> So, I logged out and ran
[20:54] <user|48> sudo apt-get remove koki* -y
[20:54] <user|48> sudo apt-get purge kodi* -y
[20:54] <user|48> and it STILL boots to kodi!  WTH?
[20:56] <oerheks> maybe it is a snap? https://snapcraft.io/mir-kiosk-kodi
[20:56] <oerheks> but then you would see nothing gets removed in konsole..
[21:00] <user|48> The remove command had a type-o....  I'm rerunning it now.
[21:04] <user|48> It looks like if I type the command correctly, it seems to work.... LOL.
[21:12] <user|48> But I'd still like to know how to not have been in this situation in the first place.  Am I REALLY going to have to uninstall kodi in order to update kubuntu?
[21:16] <oerheks> kodi runs as its own user?
[21:17] <oerheks> snap package does not have this issue, AFAIK
[21:22] <user|48> I don't know.  I was just expecting to have the regular windows manager.
=== guiverc2 is now known as guiverc
[21:32] <cbreak> user|48: on your login manager, can you select a different desktopo environment?
[21:32] <user|48> I didn't think to look....  I've uninstalled kodi.  I've got 8 of these to do today.
[21:35] <lexandrop> user|48: do you even have the ability to open terminal somehow? I think, search should start from looking at processes tree, to see how exactly kodi is launched (and where does it have it's binary).
[21:37] <cbreak> update-alternatives --display x-session-manager
[21:37] <cbreak> and / or update-alternatives --list x-session-manager
[21:50] <user|48> I didn't have the ability to open anything else.  Kodi launched in full screen mode and when I made it a window, the background was black.
[21:51] <user|48> Well, the 3 machines that I've done so far are working.  I'll install kodi on a test machine and see if it breaks anything.
[21:52] <lexandrop> well, you can always use Ctrl+Alt+F[1-7] to switch to another TTY, terminal should be available there at least
[21:52] <lexandrop> just in case
[21:58] <user|48> Yup.  Fortunately, I was able to ssh in and fix all the things.
[22:23] <user|48> Thanks for your time; I guess I just needed to vent.