[16:13] The mapping from my Windows-key to the "open launcher"-function disappeared again. I tried setting it to Alt-F1 as that fixed the problem last time [16:13] .. but that did not fix it this time. [16:16] In 'System Settings -> Shortcuts -> Plasma' there are 5 entries for "Activate Application Launcher Widget", 4 of these say "No active shortcuts" and one says "Alt+F1" [16:17] this doesn't sound very rational to have 5 entries for one thing, if people want to map many key combos to one thing that should be implemented in an another way [16:18] I cannot delete the 4 inactive ones. If someone knows how to get the application launcher not activatable by "Windows"-key problem, please help [16:27] Iamthehuman12: just looking at the system settings -> shortcuts -> and I am confused :P there are so many options but most are for applications [16:27] Ah, I guess the plasma settings are what you want. [16:31] Oh, I don't have a windows key on my keyboard.... I do have an xt/at switch on it though :) [16:37] Anyway, there does seem to be a trash icon next to the alt-F1 entry. Do the empty entries not have one? or does it not remove them? [16:38] If I add a "custom shortcut" and then trash it that line goes away [19:13] OvenWerks: the trash icon just removes the Alt+F1 binding, not the 5 pcs same setting [19:15] I cannot delete the five instances of the launcher in the settings. And setting just one of them does not fix it. Should I set all of them and see if anything makes sense after that? [19:16] no can do, cannot map same key combo to more than one at a time [19:17] OvenWerks: The system should be clear of malware, unless there is this https://securelist.com/moonbounce-the-dark-side-of-uefi-firmware/105468/ on my EFI FW. I should be getting a non-messed up dock from Lenovo next week. The current dock's firmware being messed up may possibly be a source of problems due to the DMA it has. Maybe [19:19] OvenWerks: Eickmeyer told me there is some weird hardcoding of the Windows-key to Alt+F1 in some KDE thing and it sometimes disappears and he doesn't know why or how [19:21] once I got it fixed by reassigning Alt+F1 again in the system settings like he suggested, but now doing it does not help any more [19:57] Iamthehuman12: in ~/.config/kglobalshortcutsrc I have one line: activate widget 36=Alt+F1,none,Activate Application Menu Widget [19:57] do you have more lines similar? [20:00] I wonder if wiget number (36) might get changed if the top bar (or bottom) gets edited. Like if more than one application menu is added/removed [20:28] OvenWerks: I see no line similar to that. What does that number after 'activate widget' represent? I see some entries with "none,none" [20:30] If there is no desktop file in /usr/share/applications/ for the application, the panel makes one up on the spot and gic=ves it a number.. so 36.desktop would be a file I am guessing. [20:32] but I don't know where that file would be located [20:33] Also, you may not have it if you have never changed your application menu style with alternatives [20:33] OvenWerks: Here are the 5 entries I found searching for "activate widget" and none of them contain Alt+F1 even contrary to what my system settings tell me [20:33] OvenWerks: https://paste.debian.net/1240906/ [20:34] * OvenWerks always changes his to "Application Menu" from the default. [20:34] yeah, you do not have a Windows key [20:35] I remap ctrl-alt-L to first lock the system, wait 6 seconds and then put the displays to sleep, but right now I'd like to get the Windows-key to do the same thing it does in every OS [20:35] The one in line 5 looks borked [20:36] (widget 3=,none,Activa) it is missing whatever should be ahead of the , [20:36] it looks just the same as lines 1, 2 and 4 except the number is different. I'm more looking at the empty space before the comma in line 3 [20:37] :) ok line3 which is line5 in the paste [20:37] ah, ok sorry [20:38] so... add something there, or maybe put copy of the file aside, remove the other lines and add Alt+F1 before the comma and reboot and see if anything interesting happened? [20:39] (the other with "Activate Application Launcher Widget") [20:40] I'm thinking those lines are why I'm seeing the same exact shortcut target 5x, when there should be only one. [20:41] yeah that wouold make sense [20:44] My question would be: how did they all get there? [20:47] I do not know why all distros and OS drift into inconsistent states in unexplainable ways. I hope the Lenovo really brings a working dock. I had a malware streak from 2018, because I didn't realize that the criminals will corrupt the microsoft account which will enable reinfecting all OS after the Windows has been started. I cleared that one out, nuked the EFI-partition and installed clean Windows 11 and US 22.04 [20:48] I thought that getting a laptop with the security seals would render me free of the malware, but these corporations make more parameters than they make systems to keep the parameters in check [20:48] Windows? Isn't that the demo OS computers come with that everyone replaces with a real OS before they use it? [20:50] OvenWerks: Yes, just as soon as I can get FW updates to my dock via fwupdate, I will boot only one Windows 10, in VirtulBox, to run one program Xenu's Link Sleuth, which is the only truly free-of-charge and non-crippled link checker tool for webadmins (a private spider) [20:51] or someone forces Microsoft to allow Windows to boot from USB-encasings, in which case none will need Windows inside of their machine [20:53] ok, done, reboot, what is Australia doing in the ESC? Fine time to reboot [20:57] some progress, now there is only one entry for "Activate Application Launcher Widget", but windows key doesn't work to launch it. Alt+F1 is set as I wrote it to the config file [20:58] but pressing Alt+F1 does nothing, like pressing Windows-key does nothing [20:58] So wrong widget number :P [20:58] should I randomly try all 5 till I strike lucky? [20:59] I would but It may be something else too. [20:59] so try those five first [21:00] I'd need to reboot 4 more times [21:03] so there are no ways of finding out where lines into the config files come from and where the numbers come from or what they are pointing to, so best shot is try numbers if maybe one of them is right and pray hard that the system will not do it again and again and again [21:04] I would guess there is a place where it is... but not where [21:05] I cannot decipher that [21:09] I should just accept that the criminal's synthesis product is sweeter in people's ears than my real life, so I'm just going to be bullied, robbed and mislead by people, companies and organizations for as long as I live. This is so rife that I cannot tell bonafide incompetence apart from the malafide pretense [21:11] if you kickban me for that sigh, you'll just expedite me learning to install Arch, because there at least someone, incl. the users are supposed to understand how stuff works and why it broke and how to unbreak, instead of cryptic references that don't help in getting basic GUI feature to work after it was shipped broken, once fixed and now it broke again and cannot be fixed [21:12] I am looking to see if I can find out where it should be. [21:13] Thank you for your kind help and all the work you put in [21:33] Iamthehuman12: I don't know where to look. If you take that file and remove it (actually rename it) and restart, I would think plasma would recreate the file [21:33] I don't know how much you have in there though [21:33] but at least it may give you the right line to use [21:35] It would seem that kglobalshortcutsrc is just short cuts so just rename it to oldkglobalshortcutsrc.bac or something [23:23] OvenWerks: thanks for your help, I'll try the config recreation [23:31] OvenWerks: removing the config file and rebooting resulted in that nor System Settings nor kglobalshortcutrc no longer has any entry for "Activate Application Launcher Widget" [23:37] no good.