[12:49] <BluesKaj> Hi all
 Hello, I have a short question. I cannot seem to find a 22.04 BETA iso...is it not released yet?
[13:14] <BluesKaj> @Niggolas, https://cdimage.ubuntu.com/kubuntu/releases/22.04/beta/
 Τηανκ υοθ! (re @IrcsomeBot: <BluesKaj> @Niggolas, https://cdimage.ubuntu.com/kubuntu/releases/22.04/beta/)
 Thank you! (re @IrcsomeBot: <BluesKaj> @Niggolas, https://cdimage.ubuntu.com/kubuntu/releases/22.04/beta/)
[13:39] <BluesKaj> @Niggolas, :-)
[14:43] <tmlk> hi! Which is the default Python version in Kubuntu 21.10?
[15:27] <oerheks> python3 -v
[15:45] <sigma__> hi why i get this massage ? cannot increment value of type 'std::map<char, Counter>' (aka 'map<char, unsigned long long>')     i just try Analyzer_list[alphabet]++; Analyze is map pointer!?
[15:47] <sigma__> sorry wrong massage :)
[16:13] <tmlk> oerheks: Hi rephrase. I have both python3 and python2 in my Kubuntu installation. Python2 is the default version used by the system. "which python" resolves to a symlink to python2 binary. Is this the default or I messed somehow with my system?
[16:13] <tmlk> s/Hi/I
[16:27] <oerheks> only python3 is default, you must have installed a programm that depends on it, or cruft from upgrade
[18:54] <woenx> Hi. Maybe someone could lend me a hand. I'm new to Kubuntu (used the regular ubuntu until now) and I want to configure autofs to automatically mount a sshfs share
[18:54] <woenx> But I don't know if it's compatible. I copied my config files from my previous installation but doesn't seem to work. Maybe because KDE uses kio-fuse instead of fuse?
[18:55] <woenx> btw, I can mount the share normally by using the sshfs command, but not when using automount / autofs
[19:01] <Guest69> I'm using a library with custom allocateObj and freeObj functions. I want to wrap these in some sort of RAII unique_ptr thing (or, at least the freeObj part). What's the easiest way to to that?
[19:21] <Guest69> Oops, wrong channel.
[19:21] <woenx> I was confused xD
[19:22] <woenx> Anyway, I created a thread on the forum, with all the details
[19:22] <woenx> https://www.kubuntuforums.net/forum/currently-supported-releases/kubuntu-22-04-jammy-jellyfish/software-support-be/662079-autofs-with-sshfs-in-kubuntu-22-04
[20:27] <orca4> Hi there.
[20:29] <orca4> After a Kubuntu 21.04 reboot, my keyboard is not enabled in any graphical environment, but it sure is recognized in a plain (Ctl+Alt+F2) terminal. It used to work seamlessly before.
[20:30] <valorie> hmmm
[20:30] <valorie> that sounds like possibly a hardware issue
[20:31] <valorie> oh, except that it works in term
[20:31] <orca4> It is a USB Logitech keyboard, in a Dell desktop machine. I have rebooted several times, tried different USB ports and even another keyboard, with no success at all
[20:31] <valorie> orca4: the other day I was having a problem with my laptop cam would was not detected
[20:32] <orca4> Right now, I am in the plain (text) terminal and am able to issue any commands...
[20:32] <valorie> I figured out that there is an fn key which turns it on and off!
[20:32] <valorie> try `lsusb` -- is it listed?
[20:32] <oerheks> are you sure you are on 21.04? it is EOL, dead. But i read some more 21.10 issues with keyboard and mouse not working after reboot.
[20:32] <genii> Machiavellian designers
[20:33] <valorie> oh right, 21.04, sorry for not noticing that
[20:33] <orca4> @valorie: in fact, after the mentioned reboot, my USB mouse was not enabled either. However, after unpluggin and replugging it did start work again...
[20:34] <valorie> lsusb will list all logged in usb devices
[20:34] <valorie> so try your fn keys and see if some appear and disappear
[20:34] <valorie> and then gosh, upgrade
[20:34] <valorie> !eol
[20:37] <orca4> lsusb furnishes 3 Logitech devices: the keyboard, the mouse, the headset, 1 generic webcam and some "root hubs"...
[20:40] <valorie> so it is not the USB that is the issue
[20:40] <valorie> however, we can't support an EOL release
[20:41] <oerheks> i find no recent bugreports, but users mention this on 21.10.
[20:41] <orca4> oerheks, @ubottu: at any rate, you mean I should upgrade to which exact release? To 21.10? As far as I know 22.04 is still beta; would it be worth trying?
[20:42] <oerheks> upgrading now brings you 21.10. only if you select -d = development, you get jammy 22.04 .. out in 14 days or so
[20:43] <valorie> personally I would go for jammy, but I'm planning to do that on this machine today anyway
[20:44] <oerheks> it will be appreciated, if you find glitches/bugs.
[20:44] <orca4> If that matters, I have tried booting from older kernels, withour any success either
[20:44] <oerheks> 22.04 is LTS, stable and long term support
[20:45] <oerheks> orca4, oke, that is valuable info. you might want to file a bugerport, not sure if you can without keyboard..
[20:46] <orca4> oerheks : if I try 22.04 right now, you think this issue might get solved?
[20:46] <oerheks> if you install fresh, maybe yes
[20:48] <orca4> Hmm, in fact, I would like to preserve, by upgrading (not fresh installation) my already installed and configured packages and /home directory (which is in a separate partition)
[20:50] <orca4> So you guess upgrading to 21.10 or even 22.04 (beta), instead of a fresh install, is less likely to solve the issue?
[20:53] <orca4> The fact that in the plain terminal, the keyboard does work, but not in the login screen or (after using the virtual terminal) inside KDE, is not suggestive of just something related to perhaps some xserver-xorg-* package?
[20:55] <valorie> easiest way to file a bug is `ubuntu-bug $packagename` but as oerheks says, that will require a keyboard at some point
[20:57] <orca4> I might be able to report a bug, because I have another fully operational Ubuntu 18.04 desktop as well, physically close/next to the 21.04 problematic one. Would that work? Which package should I associated the bug with?
[21:01] <oerheks> orca4, that is the problem; ubuntu-bug collects proper info from the running system.
[21:02] <orca4> When I issue (in the 18.04 machine) the command: ubuntu-bug, the first thing it asks is the kind of problem I wanna report. Should it be: (1) Other probelm, or (2) Display (Xorg)?
[21:02] <orca4> oerheks, I see
[21:03] <oerheks> and not sure what to file the bugrepost against, what package i mean
[21:03] <orca4> Isn't there a bug reporting plain text app?
[21:03] <oerheks> no, AFAIK
[21:05] <orca4> Perhaps I am being too naive, but, after entering KDE in the problematic 21.04 machine, or by using a live cd, I have the sheer impression that everything, apart from this keyboard issue, seems to be fine...
[21:06] <oerheks> problem is; if one encounters this keyboard issue, one cannot go online to seek help or file a bugreport... so it might be a serious one, still no clue/bugreports appearing
[21:07] <orca4> Then, since I am able to run plain text commands, given sufficient expertise, should I not be able to fix everything, without having to dist-upgrade at all?
[21:10] <orca4> One last piece of info which might be relevant: when I boot from a 21.04 live usb stick, the keyboard DOES work... Does that mean something?
[21:11] <oerheks> No. you have not the update that caused this.
[21:12] <oerheks> but please, drop 21.04 .. and go for 21.10 /  22.04
[21:13] <valorie> If you want to be cautious, orca4, then burn a thumbdrive with 22.04 beta and try it out
[21:13] <valorie> if it works, you are golden
[21:14] <valorie> then you can either upgrade (twice) or just do a fresh install
[21:15] <valorie> using an eol is dangerous, because you are not getting even security updates
[21:16] <oerheks> updates would mention there is a new version available.
[21:18] <orca4> Ok I see. I guess I have nothing to lose, by then trying to upgrade twice, as valorie says: 21.04 -> 21.10 and then 21.10 -> 22.04 beta. Is it just a matter of changing the sources.list file and issuing apt upgrade, then apt dist-upgrade?
[21:23] <orca4> Should I be able to do the twice upgrade in a plain text terminal?
[21:37] <orca4> Thank you all!!