[00:30] <valorie> fravialis: it might help to clear klipper's settings
[00:30] <valorie> it works really well, but I've had issues in the past as well
[00:45] <fravialis> valorie: tx
=== Lord_of_Life_ is now known as Lord_of_Life
[04:31] <user|69> Hi All
[04:33] <user|69> I'm having tech problems with 18:04LTS and it won't allow me to update to 22.04LTS am I doing something wrong
[05:34] <alkisg> user|69: as I said yesterday, what's the output of this command? dpkg --print-architecture
[06:06] <IrcsomeBot> <milesdredd08> https://i.imgur.com/YVrBiHB.png
[06:06] <IrcsomeBot> <milesdredd08> 😅love it !
[08:32] <IrcsomeBot> <Omar> Any help (re @Omar: Hi, i wanna remove all snaps, and I have riseup vpn i need it is there a similar alternative?)
=== mkv is now known as m4v
[10:14] <mint> hi
=== ls is now known as rax
=== rax is now known as r9
[12:08] <BluesKaj> Hi all
[15:16] <TiZ[m]> Hello there. Will Kubuntu 22.04 be getting Plasma 5.26 via the backports-extra PPA?
[15:20] <RikMills> TiZ[m]: not while there is a direct upgrade path to kinetic 22.10. installing plasma 5.26 on 22.04 would break later upgrades to 22.10
[15:21] <TiZ[m]> I gotcha. Is 22.10 gonna have 5.26? And is there a direct upgrade path for 22.04 with the backports-extra PPA?
[15:23] <RikMills> TiZ[m]: everything in the backports-extra ppa for 22.04 will be a lower version than in 22.10, so upgrades to 22.10 should go smoothly there
[15:26] <TiZ[m]> And 5.26 will be in the backports-extra or backports PPA?
[16:03] <RikMills> TiZ[m]: backports. -extra was a compromise to make 5.25 available on the LTS, because it wasn't stable enough for the Kubuntu Focus people who use the normal backports
[16:03] <RikMills> that will not be needed on 22.10
[16:04] <TiZ[m]> Okay, so I'm guessing that the upgrade path will leave -extra as a blank PPA that you can just remove afterward.
[16:05] <TiZ[m]> Thanks for your time today :)
[16:06] <RikMills> TiZ[m]: yes, it will, and no problem :)
[16:30] <IrcsomeBot> <CrustyCrab55> What should I do? : https://irc-attachments.kde.org/a429e896/file_60694.jpg
[16:31] <IrcsomeBot> <Eickmeyer> Probably start by not asking for help with openSUSE in a Kubuntu Support place.
[16:31] <IrcsomeBot> <CrustyCrab55> oh sorry I posted in wrong group
[16:32] <IrcsomeBot> <CrustyCrab55> I was posting to somewhere lol
[16:32] <IrcsomeBot> <Eickmeyer> All good.
[16:34] <IrcsomeBot> <Eickmeyer> It just mirrors to IRC so despite you deleting I had to answer.
[16:34] <IrcsomeBot> <Eickmeyer> (posts to IRC are permanent)
[16:34] <IrcsomeBot> <CrustyCrab55> All fine
[18:08] <Kangarooo> RikMills: "18:20 <RikMills> TiZ[m]: not while there is a direct upgrade path to kinetic 22.10. installing plasma 5.26 on 22.04 would break later upgrades to 22.10" how is Linux updates working? Can you give some manual link about that? Logical would be to make updates installing packages with working dependencies, not any version dependency. No?
[18:52] <RikMills> Kangarooo: several parts of plasma hard depend on the ABI of the Qt version they were compiled against. i.e. 5.15.3 in jammy. so those packages will not work or install with the Qt version in kinetic. apt will not find an upgrade path due to that hard dep
[18:56] <RikMills> same for dependencies on some other libraries that have had their library package name bumped due to binary incompatible changes
[18:57] <RikMills> this is not a weakness of the debian/ubuntu automatically determined dependencies, but a strength
[18:58] <RikMills> the determined dependencies make sure that the correct library versions each package needs are in their dependencies
[18:59] <RikMills> if that was not so, programs would crash due to not finding the right library they were compiled against
[19:00] <RikMills> hope that makes sense. it is quite as technical thing, but 100% required so that things do not break
[19:56] <miley> I've got the best of both!
[20:03] <valorie> right, those who want the very latest can run the alpha of the next release
[22:52] <keithzg> mmikowski: Days later, finally getting back to my i/o error when running `/usr/bin/env python3`, insanely the error occurs not only when using something like XTerm, but even an outright VT (ex. ctrl-alt-f3)!
[22:55] <mmikowski> keithzg: wow! It sounds like it has to be an environment variable.
[22:58] <mmikowski> keithzg: Have you tried to diff the environment?
[23:57] <IrcsomeBot> <Anarchotaoist> What kernel should 22.04 be on? uname -r
[23:57] <IrcsomeBot> <Anarchotaoist> 5.17.0-1019-oem
[23:57] <IrcsomeBot> <Anarchotaoist> How do I change the kernel? Thanks.
[23:59] <genii> !info linux-image-generic jammy
[23:59] <ubottu> linux-image-generic (5.15.0.50.50, jammy): Generic Linux kernel image. In component main, is optional. Built by linux-meta. Size 3 kB / 20 kB. (Only available for amd64, armhf, arm64, powerpc, ppc64el, s390x.)