[00:09] <yuesbeez> keys created with kleopatra work. keys greated with gpg tool do not
[00:34] <mmikowski> yuesbeez: This sounds like a case of dearmored versus not-dearmored keys. If you inspect them, do they look different? One might be ascii text and the other binary or competedly different format.
[00:34] <mmikowski> just a guess, but I have seen this before. Some tools use ascii encoded (armored, iirc) by default, whereas other do not.
[00:36] <yuesbeez> mmikowski: I actually just figured it out. KDE wallet service is not compatible with keys that have a passphase. So when prompted for a passphrase if you just press enter it will create a private-key, as opposed to a protected-private-key
[00:36] <mmikowski> ah, so there it is. Thanks yuesbeez,  I'll keep that in mind.
[00:37] <yuesbeez> This should be in the documentation. no reason using the gpg tool that ships with kubuntu shouldnt be supported
[00:41] <mmikowski> Well, you've got it sorted. You might want to file a bug after checking for dups. My guess is there probably is already something out there. FWIW, you might check out KeePassXC which might work better for some use cases.
[03:55] <hamdani> hi
[04:59] <user|91> hello
 hi all, I can't see any output on my external monitor. I do get the popup what do to when I plug in the HDMI cable but nothing happens. I can't see this monitor in the monitor setup.
 any fix?
[08:17] <StyXman> hi all. I'm trying to upgrade to kinetic and I'm getting issues with libqt5webenginecore5 which stays at 5.15.9+dfsg-1 while other siblings are going up to 5.15.10+dfsg-6. also, is there a transition for libevent-core? 2.1-7 and 2.1-7a clonflict each other and seems like some packages want one and others want the other one
[12:50] <StyXman> I lost connection, so I'll ask again
[12:50] <StyXman> hi all. I'm trying to upgrade to kinetic and I'm getting issues with libqt5webenginecore5 which stays at 5.15.9+dfsg-1 while other siblings are going up to 5.15.10+dfsg-6. also, is there a transition for libevent-core? 2.1-7 and 2.1-7a clonflict each other and seems like some packages want one and others want the other one
[13:03] <BluesKaj> Hi all
 Hi
 is realtek open source or closed source?
 Are Realtek drivers open or closed source?
[13:12] <BluesKaj> both
[14:32] <guruprasad> I have the discover snap backend installed and enabled, but it never shows any updates for snaps. I installed a flatpak a few days ago and today I got a notification for its update.
[14:33] <guruprasad> Has anyone experienced the same issue?
[14:33] <guruprasad> This computer was running Kubuntu 22.04, Kubuntu 22.04 + 5.25 via the backports-extra PPA and now runs Kubuntu 22.10 + 5.26 via the backports PPA.
[14:34] <guruprasad> I have seen the same issue in all these setups
[14:34] <non> guruprasad: normal, snap are automatically refresh in the backgrounds
 Hi, where can i learn bash scripting from?
[14:35] <guruprasad> non, but if there is an update and the next refresh hasn't yet run, shouldn't discover show it? If not, what is even the purpose of the snap discover backend?
[14:35] <guruprasad> I am not sure I understand
[14:37] <non> guruprasad: yeah I think it should be that way too,but unfortunately someone hasn't implemented it yet
[14:37] <guruprasad> Oh, okay. What does the backend do in its current form any way?
[14:38] <Gorenoise_> hello all
[14:38] <non> guruprasad: configure permission, and display some apps that installable
[14:38] <Gorenoise_> is kubuntu related issues on installing on virtual machines?
[14:39] <Gorenoise_> im trying since 2 days and it just stay in a black screen... ;///
[14:39] <non> guruprasad: that's to my understanding only, i'm not a kde developer tho
[14:39] <kksilvery> SAD bhai!
[14:40] <non> Gorenoise_: what do you use for virtual machine is it "virtualbox"?
[14:40] <Gorenoise_> yes non
[14:40] <Gorenoise_> virtualbox :D
[14:40] <Gorenoise_> its bad?
[14:41] <non> nah, it's fine really, i'm just trying to do the samething on my computer so i can help :)
[14:42] <Gorenoise_> non: u installed there?
[14:42] <Gorenoise_> i just got a black screen lol
[14:42] <guruprasad> non, I haven't been able to find installable snap apps via this backend, afai
[14:42] <guruprasad> *afaik
[14:42] <non> Gorenoise_: trying to at the moment
[14:43] <non> guruprasad: try searching for firefox in discover does firefox appear?
[14:44] <guruprasad> non, from what I can see, it only lists snaps that are installed. So yes, it shows firefox
[14:44] <arraybolt3> Gorenoise_: When you launch the VirtualBox machine, do you see the words "Press F12 to see boot options" (or something like that) show up in the lower-right corner of the VM screen for a second just after starting the VM?
[14:45] <Gorenoise_> arraybolt3: no. it goes to the boot options in auto
[14:45] <Gorenoise_> but yes... is posible to see the options with f12
[14:46] <non> guruprasad: on my machine there are apps that aren't install showing,can I ask what apps are you searching for?
[14:46] <arraybolt3> Gorenoise_: Hmm, OK. If those words weren't popping up it would mean that VirtualBox wasn't starting the VM *at all*, but if they are showing up, then that's not the problem.
[14:47] <arraybolt3> And VBox works perfectly for me so :P Guess I'll let others with more experience try to help with this.
[14:47] <Gorenoise_> arraybolt3: vm starts but after kubuntu logo, just a black screen and nothing happens hehe
[14:47] <arraybolt3> Wait a sec... what host OS are you using? Windows?
[14:47] <Gorenoise_> arraybolt3: i will try more times... im dumb as f** so...
[14:48] <guruprasad> non, I searched for emacs, pycharm, yt-dlp and nothing in the search results.
[14:48] <arraybolt3> If so, can you upgrade your version of VirtualBox to the latest version? Sometimes older versions have strange incompatibilities with newer operating systems.
[14:48] <arraybolt3> Gorenoise_: ^
[14:48] <Gorenoise_> arraybolt3: unfortunattly yes.... ruinwodws
[14:48] <Gorenoise_> lol
[14:48] <guruprasad> Oh wait, I was trying to search when the `Updates` section was open and I think it searches there and obviously doesn't find anything.
[14:48] <Gorenoise_> arraybolt3: VM is updated
[14:48] <guruprasad> Searching from the home section seems to work.
[14:49] <arraybolt3> Gorenoise_: Shoot. Um... and just to be sure, you are setting the VM type to Ubuntu (64-bit) when you're first setting up the virtual machine, and you're providing at least 2 GB of RAM, right?
[14:49] <arraybolt3> (The default 1 GB may not be enough, and if you're setting the VM type to something other than Ubuntu (64-bit), that may not work.)
[14:49] <non> guruprasad: lol ,updates I do that sometime too
[14:49] <arraybolt3> (Also you'll want at least 20 GB disk space, the default 10 GB may not be enough.)
[14:49] <Gorenoise_> arraybolt3: exactly bro
[14:50] <guruprasad> non, I'd say that it is poor UX.
[14:50] <arraybolt3> Gorenoise_: Maybe it's just loading really slowly? How old is your computer?
[14:50] <guruprasad> If the search box is outside a page in a location that appears global like it does on discover, it is misleading and confusing.
[14:51] <Gorenoise_> arraybolt3[m]: Intel(R) Core(TM) i5-2400S CPU @ 2.50GHz   2.50 GHz
[14:51] <Gorenoise_> its not so old but its a S**i know
[14:51] <Gorenoise_> lol
[14:52] <Gorenoise_> arraybolt3: yes really slowly and so just the black screen of death
[14:52] <arraybolt3> Yeah that shouldn't just drop you to a black screen.
[14:52] <Gorenoise_> haha
[14:52] <arraybolt3> Gorenoise_: Maybe while you see the Kubuntu logo, you can press Esc. That should show you a whole bunch of geeky info about what's happening in the background, and may show what's failing or getting hung up.
[14:52] <Gorenoise_> i run tails here too.
[14:53] <Gorenoise_> parrot...
[14:53] <arraybolt3> If you can see a failure like that somewhere in there, screenshot it, upload it to Imgur, and send the link here.
[14:53] <Gorenoise_> arraybolt3: hmm good tip bro
[14:53] <Gorenoise_> i will try rn arraybolt3
[14:53] <Gorenoise_> lets see
[14:53] <Gorenoise_> if it works i wil pay u a beer ok haha
[14:54] <arraybolt3> LOL I don't drink alcohol but thanks for the thought. (And we don't take payment for offering help here.)
[14:54] <Gorenoise_> arraybolt3 im kidding
[14:55] <Gorenoise_> :D
[14:55] <arraybolt3> :P
[14:55] <Gorenoise_> arraybolt3: im on it Kubuntu 22.04.1 LTS
[15:10] <Gorenoise_> arraybolt3: the tip of doing ESC on booting is great haha
[15:10] <Gorenoise_> im seeing now
[15:11] <Gorenoise_> but now goes to the black screen again ://
[15:12] <Gorenoise_> started!
[15:12] <Gorenoise_> urruuuuuuuuuuuuu
[15:15] <Gorenoise_> well started but nothing happens ://
[15:18] <non> Gorenoise_: did you take a screenshot?
[15:19] <Gorenoise_> no ;//
[15:19] <Gorenoise_> i will re-run  and take one of whats happens on bground ok
[15:22] <non> Gorenoise_: I just try installing it on virtualbox it so slow on my athlon cpu lmao
[15:24] <Gorenoise_> non and arraybolt3: see https://imgur.com/a/UJOG2La
[15:24] <Gorenoise_> and i see now that it started to install :D
[15:26] <non> Gorenoise_: does it change or it just the stuck in the same screen as the above
[15:29] <Gorenoise_> non: i changed some configs on VM so it goes to the black screen but goes out really fast
[15:29] <Gorenoise_> im installing right now
[15:29] <Gorenoise_> :D
[15:29] <Gorenoise_> really thanx for your time and patience guys
 Hi !! New Kubuntu user!!
 Really very very very nice distro
 Far better than main Ubuntu with Gnome
 I saw one little graphic issue let's say 😜 If you choose LVM and encryption as I did on my system when you out the encryption password the message that the partition was unencrypted it falls over the Kubuntu logo on the login
 That was fixed in an update. (re @Thanos: I saw one little graphic issue let's say 😜 If you choose LVM and encryption as I did on my system when you out the encryption password the message that the partition was unencrypted it falls over the Kubuntu logo on the login)
 Are you sure?? I have done all the updates on Kubuntu 22.04.1 LTS...I saw only that the message appearing and disappearing a little more fast...but again it's on the Kubuntu logo (re @Eickmeyer: That was fixed in an update.)
 Considering I'm the one who fixed it, yes. (re @Thanos: Are you sure?? I have done all the updates on Kubuntu 22.04.1 LTS...I saw only that the message appearing and disappearing a little more fast...but again it's on the Kubuntu logo)
 So, it might be your screen size/specific to your machine.
 My screen size is at 1920x1080
 I might take another look, but it's such a minor bug that it would get "wishlist" priority.
 I can send you also video to check!! The fix was to move the message down on the Kubuntu logo or just puting it appearing faster?
 Yes yes I know!!! (re @Eickmeyer: I might take another look, but it's such a minor bug that it would get "wishlist" priority.)
 I am just saying that this is the only let's say graphic issue that I have noticed
 It's possible it was fixed but never actually done in an SRU, so it's awaiting some kind of backport.
 I worked on that months ago.
 Ok 👌
 I have the Kubuntu LTS 22.04.1 with the main repos nothing more enabled
 Right. You get faster bugfixes by enabling the Kubuntu Backports PPA.
[16:22] <genii> !backports
 Do you think that I have to do it?? I  mean because I would like to upgrade directly from 22.04 to next 24.04 LTS Do you think that I will face problem on the upgrade of the next LTS release of I have the backports enabled? (re @Eickmeyer: Right. You get faster bugfixes by enabling the Kubuntu Backports PPA.)
 It shouldn't cause a problem. When you upgrade, it disables the PPA and the backports are versioned to prevent any versioning issues.
 This automatically? (re @Eickmeyer: It shouldn't cause a problem. When you upgrade, it disables the PPA and the backports are versioned to prevent any versioning issues.)
 Additionally, the versions in the next LTS are always going to be greater than what's in the backports, so you're not going to have a problem.
 Yes. (re @Thanos: This automatically?)
 What is mean with the term "versioned" (re @Eickmeyer: It shouldn't cause a problem. When you upgrade, it disables the PPA and the backports are versioned to prevent any versioning issues.)
 So, right now you have a package (say Plasma) that is plasma-desktop 5.24.2. In backports is 5.24.7, but in 24.04 LTS would be 5.27. The package management system always takes what is the greatest version. (re @Thanos: What is mean with the term "versioned")
 So, the idea is that you're not left with incompatible versions of packages.
 Aaaaa ok!! And when you click upgrade let's say from 22.04 to next 24.04 in the future it will mange to disable the backports repos itself the upgrade procedure and do the rest!?
 Yes, exactly.
 Are you in the lead of Kubuntu project? (re @Eickmeyer: Yes, exactly.)
 No, I'm the lead of Ubuntu Studio and am part of the Kubuntu Focus team (kfocus.org). (re @Thanos: Are you in the lead of Kubuntu project?)
 Anyway 😉 again congrats for this amazing flavor (re @Eickmeyer: No, I'm the lead of Ubuntu Studio and am part of the Kubuntu Focus team (kfocus.org).)
 I haven't try the studio version
 Hehe, thanks. I'll pass it on. @RikMills (re @Thanos: Anyway 😉 again congrats for this amazing flavor)
 Wow Kfocus I see is a Kubuntu version? (re @Eickmeyer: No, I'm the lead of Ubuntu Studio and am part of the Kubuntu Focus team (kfocus.org).)
 Only for dedicated laptops?
 No, it's computer hardware that uses Kubuntu as its OS. (re @Thanos: Wow Kfocus I see is a Kubuntu version?)
 When you mean hardware you mean dedicated PCs? (re @Eickmeyer: No, it's computer hardware that uses Kubuntu as its OS.)
 That you sell with Kubuntu?
 Yes.
 Nice project!!! Ok for me KDE yes I think is the most complete DE for Linux so is a great choice for someone who needs a Linux laptop
[16:54] <Eickmeyer> ^ mmikowski
 Well, if you're in the market for one, you know where to go!
 I think if someone knows Linux it's a great choice (re @Eickmeyer: Well, if you're in the market for one, you know where to go!)
 Hello, I am installing a fresh 22.10 on my desktop and I'm facing an issue at the end of the installation, this is my second try and the system is not bootable after reset, let me upload some screenshots
 https://irc-attachments.kde.org/7a363b4c/file_61102.jpg
 https://irc-attachments.kde.org/abe831a6/file_61103.jpg
 running grub-install manually: https://pastebin.com/raw/Du0Tey1q
 I was getting an alert regarding the missing EFI partition at the disk setup screen, but I proceeded. as I also did not have an EFI partition in 22.04 and it was working fine ...
 https://irc-attachments.kde.org/b8453b41/file_61104.jpg
 is this something new on 22.10 ?
 These backports are different from the backports extra? (re @Eickmeyer: Right. You get faster bugfixes by enabling the Kubuntu Backports PPA.)
 Backports extra has a later Plasma version (5.25) and is intended to be used on top of regular backports if you want newer features. But the regular backports contains the LTS version of Plasma (5.24) which has two-year support from KDE. (re @Thanos: These backports are different from the backports extra?)
 So better to use the regular backports (re @Eickmeyer: Backports extra has a later Plasma version (5.25) and is intended to be used on top of regular backports if you want newer features. But the regular backports contains the LTS version of Plasma (5.24) which has two-year support from KDE.)
 In my opinion (and considering you wish to stick to LTS releases), yes. (re @Thanos: So better to use the regular backports)
 So it's Kubuntu LTS version carry also a KDE LTS versu? (re @Eickmeyer: In my opinion (and considering you wish to stick to LTS releases), yes.)
 So it's Kubuntu LTS version carry also a KDE LTS version? (re @Eickmeyer: In my opinion (and considering you wish to stick to LTS releases), yes.)
 Coincidentally, yes. Plasma 5.24 is an LTS version of Plasma. However, KDE only supports it for 2 years as opposed to 3 years for Kubuntu. (re @Thanos: So it's Kubuntu LTS version carry also a KDE LTS version?)
 Understood
[19:37] <mmikowski> Thanos: I agree with Eickmeyer. The Kfocus project actively (and extensively) tests and tracks key proposed updates to the backports repo; then then reports the results back to Kubuntu and KDE. This helps encourage more stable releases. The other backport repos are more bleeding edge - or for testing - and do not get the same scrutiny from KFocus.
[19:41] <mmikowski> Of course there are many other people and CI systems that test the software, but if you are looking for usable and stable, regular backports is probably a good choice.
 So backports-extra are more for testing let's say
 Now how about the apps like gimp blender inkscape vscode discord etc..are you using Debs from main repos or snaps?
[20:03] <valorie> @thanos look at flatpaks too
[20:03] <valorie> I find them easier than snaps
[20:56] <mmikowski> thanos: I use repos unless the app is unavailable there, or if I need a newer version that's only available in snap/flatpack/appimage. I think that's a pretty safe strategy in 22.04 LTS.
 Still getting this message, fixed the EFI issue but grub fails to install still
 https://pastebin.com/raw/f7KArHRb (re @ykruH: )
 I'm getting out of ideas :/
[22:21] <mmikowski> ykruH: It appears you may have a disk with a RAID signature on it.
 yes, all is on mdadm
[22:23] <mmikowski> ok, so RAID is what you want and is set up...
[22:23] <mmikowski> And I was hoping for an easy win here ...
 I think I will download the 22.04 iso again and install it, that version was just installing normal
[22:25] <mmikowski> FWIW, before you go forward, are you sure you want to boot to RAID?
 I am doing so since 2010 or so .. never an issue
[22:26] <mmikowski> I've done that before using the Ubuntu server disk and then adding kubuntu-desktop on top of that, and it's worked well (you need to also add the kubuntu-backports repo).
 something must have changed in the latest 22.10 that affects how grub is installed or how mdadm is being detected
[22:27] <mmikowski> Ah, so this worked on 22.04?
 sure
 I am just trying to upgrade
[22:27] <mmikowski> Ugh. I haven't seen this before, so just a few friendly thoughts ...
 I took a backup of root but not from /boot so I can not roll back easily :/
[22:29] <mmikowski> Yeah, we were looking at a BTRFS default setup for kfocus 22.04, but the fact we had to snapshot /boot too (at least for encrypted disks), was part of the challenge on system failure. TL;DR: I feel your pain :)
[22:30] <mmikowski> This smells of potentially an initramfs issue. Have you rebuilt after making sure dkms is updated?
[22:31] <mmikowski> If you use dkms and it is broken, then that can cause failures in some cases (nvidia drivers and tuxedo keyboard are obvious examples, but there are certainly others).
[22:32] <arraybolt3> Hold on. Is this a DKMS + Secure Boot issue on Ubuntu 22.10?
[22:32] <mmikowski> I was writing about fixing these issues, but realized that you need to boot into the system first.
[22:33] <mmikowski> Hi arraybolt3. Say, are you going to say this is possibly the broadcom issue?
[22:33] <arraybolt3> mmikowski: Yep.
[22:33] <mmikowski> bwahaha
[22:33] <mmikowski> not sure it is. I was just spit-balling on what might be going on here.
[22:34] <mmikowski> https://pastebin.com/raw/f7KArHRb <= from ykruH
 no secure boot, just plain non-uefi
 it's a fresh install, boot and root partitions formatted
[22:34] <arraybolt3> Ah, then it's not what I suspected. Carry on.
[22:35] <mmikowski> ykruH: ok, so *very* unlikely to be the broadcom issue.
[22:35] <mmikowski> On test: can you boot into a rescue disk and mount the system disks? That might tell you something.
[22:36] <mmikowski> https://kfocus.org/wf/recovery.html#bkm_use_a_live
[22:36] <mmikowski> ^ in case you need it (although it sounds like you don't).
[22:36] <arraybolt3> According to your pastebin earlier (https://pastebin.com/raw/Du0Tey1q), you are indeed booted into UEFI, if I'm understanding correctly. Either that or else something's gone haywire.
 is there official docu on how to chroot correctly in the live-usb mode to retry configuring grub ? Not sure if that is the only think missing as the installer exited after the grub-install error
 yeah, that was before I realized I booted incorrectly, changed the bios setting, now it's back to legacy (re @IrcsomeBot: <arraybolt3> According to your pastebin earlier (https://pastebin.com/raw/Du0Tey1q), you are indeed booted into UEFI, if I'm understanding correctly. Either that or else something's gone haywire.)
[22:38] <mmikowski> ykruH: That link I gave gets you in the chroot position where you can run sudo update-grub. It works with the stock kubuntu USB image. The model-specific stuff is about the disk topology.
[22:38] <arraybolt3> I don't know of any official docs on that process, however it's not that tricky to do either. TL;DR: Mount root to /mnt, then mount /boot and /boot/efi into their appropriate folders within /mnt, then bind-mount /sys, /proc, /dev, and /dev/pts into the right spots in /mnt, then chroot and try to do something. If it fails, add some more bind-mounts.
[22:38] <arraybolt3> Actually, scratch all that, mmikowski has it figured out.
[22:38] <mmikowski> arraybolt3: Yeah, it's documented :)
[22:39] <arraybolt3> mmikowski: Heh, your documentation is better than the stuff I've seen elsewhere.
[22:40] <mmikowski> thanks arraybolt3. Our goal is to fill in the gaps and always be current.
 root@kubuntu:/# update-grub
 /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
[22:46] <arraybolt3> Exit chroot, then "sudo mount --bind /dev /mnt/dev", then re-enter chroot.
 done that, I think I found something, hold on ..
 so, mdadm was not installed, I did it in chroot and now I can access the data in initramfs but still not boot completely.  I think it may be related to the @ subvolume in btrfs...
 https://irc-attachments.kde.org/73fbddcf/file_61110.jpg
 https://irc-attachments.kde.org/389895ca/file_61111.jpg
[23:26] <NoCreativity> Hello everyone! I'm trying to figure out why I'm getting sometimes some additional keystrokes when typing fast. I notice this problem started happening after I upugraded to Kubuntu 22.04.
[23:26] <NoCreativity> Some examples of how my wording ends up being are:
[23:26] <NoCreativity>  - suppoprt  - support
[23:26] <NoCreativity>  - issueu    - issueu
[23:26] <NoCreativity>  - upugraded - upgraded
[23:26] <NoCreativity>  - persisits - persists
 Thats it man, with the subvolume flag in grub it booted up !!! Finally
 https://irc-attachments.kde.org/cc4f26be/file_61112.jpg
[23:28] <NoCreativity> Hello
[23:30] <bprompt> allo
[23:30] <NoCreativity> Hello everyone! I'm trying to figure out why I'm getting sometimes some additional keystrokes when typing fast. I notice this problem started happening after I upugraded to Kubuntu 22.04. Some examples of how my wording ends up being are: suppoprt(support), issueu (issueu), upugraded (upgraded), persisits (persists) and clcueu (clue). I tried
[23:30] <NoCreativity> turning of keyboard repeats but the problem still persisits. Would anyone have a clcueu where I can search for a solution?
[23:34] <bprompt> NoCreativity: checked stuff in Accessibility settings maybe that shouldn't be turned on?
[23:39] <NoCreativity> Checking
[23:41] <NoCreativity> Nothing is enabled. Sticky key is disabled as well as keyboard filters.
[23:42] <bprompt> NoCreativity:  do you run autokey? maybe some "phrase"?
[23:44] <NoCreativity> I'm not famililar with that. Let me verify.
[23:45] <bprompt> I use autokey quite a lot =), but I know what I write there :)
[23:49] <NoCreativity> Yeah. I can't find if I have any autokey tools installed. I checked a list but coculdn't find any.
[23:55] <bprompt> NoCreativity: some websites recommend "sudo apt-get install xserver-xorg-input-all"   <--- namely, reinstalling the keyboard drivers
[23:55] <NoCreativity> Hmmmm. Let me try that! :)
[23:56] <NoCreativity> It's already installed.
[23:57] <NoCreativity> I'm forcefully reinstalling.
[23:59] <bprompt> right, I was about to say that