[Systemd KCM] [Bug 401000] many colour schemes have poor contrast for SystemD log
https://bugs.kde.org/show_bug.cgi?id=401000 --- Comment #4 from fire f. --- I recompiled systemdgenie from sources in Sept. of 2021. It now does follow the system color scheme of KDE. The binary provided by Manjaro does, however, not follow the system colour scheme. As the compile goes pretty smoothly, this probably the quickest way to obtain usability of systemdgenie. Not sure about the KCM thingy. -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 401000] many colour schemes have poor contrast for SystemD log
https://bugs.kde.org/show_bug.cgi?id=401000 --- Comment #5 from fire f. --- Corrections of my above error report: The binary of systemdgenie version 0.99.0 actually does follow a users colour scheme, such as the one binary "systemdgenie" provided by the Manjaro distro in 2021. If launched as sudo /sbin/systemdgenie that user is root. The color scheme of user "root" is not accessible via non-root KDE-system-settings GUI. So it would be nice if the app would force a good, high-contrast color scheme for the user "root" or be otherwise user-friendly to resolve the issue of low contrast of root’s default colour scheme. -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 401000] many colour schemes have poor contrast for SystemD log
https://bugs.kde.org/show_bug.cgi?id=401000 --- Comment #6 from fire f. --- until such time, one can work around the poor contrast by copying manually 2 good "kdeglobals" with the scheme "elementary Luna" from GNHS activated to below the /root/ directory, namely as target files: file:///root/.kde4/share/config/kdeglobals as well as file:///root/.config/kdeglobals containg a line like this ColorScheme=elementaryLuna worked for me with ColorScheme=WhiteSur too while at Big Sur, CA -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426920] improve the help texts
https://bugs.kde.org/show_bug.cgi?id=426920 --- Comment #2 from fire f. --- khelpcenter could be more detailed when elucidating keditbookmarks ! There is quite some utility in using keditbookmarks features right while in khelpcenter and saving salient bookmarks from the khelpcenter itself. This custoization might be very helpful for memorizing workflow et cetera! -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 401000] many colour schemes have poor contrast for SystemD log
https://bugs.kde.org/show_bug.cgi?id=401000 --- Comment #7 from fire f. --- ideally, the systemdgenie binary would perform this "kdeglobals" customization to overcome the poor contrast default colorscheme preset. Would greatly improve usability! -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 426920] New: improve the help texts
https://bugs.kde.org/show_bug.cgi?id=426920 Bug ID: 426920 Summary: improve the help texts Product: khotkeys Version: 5.19.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@michael-jansen.biz Reporter: fire...@firemail.cc Target Milestone: --- SUMMARY some small improvements for clarity and usability of the help texts would be nice to have. STEPS TO REPRODUCE 1. kcmshell5 khotkeys 2. read the internal help text 3. be left wondering about the Macro-key functionality on special keys and characters such as € , @ , quotes , "SPACE-char" and such. Particularly after switching keyboard language-layout say from en-US to es-ES . OBSERVED RESULT not quite optimal help text, especially in translated German version. EXPECTED RESULT pretty good help texts. SOFTWARE/OS VERSIONS Linux/KDE Plasma:KDE neon distro KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION developing for khotkeys is not very hard. So the source code can be played around with rather easily: git clone https://invent.kde.org/plasma/khotkeys.git #install various developer libs in KDE neon such as: sudo apt install libqt5x11extras5-dev mkdir buildSubDir cdbuildSubDir cmake .. # it usually builds smoothly, if all libs are present. look for missing packages to install via apt or synaptic in error messages. then: qdbus org.kde.kded5 /kded org.kde.kded5.unloadModule khotkeys # true or false ./git/khotkeys/buildSubDir/bin/khotkeys_standalone" &# launch the homemade khotkeys daemon kcmshell5 khotkeys&# GUI start and bang, you run your modified khotkey. to mark your homemade Dämon, change the line file:///home//git/khotkeys/libkhotkeysprivate/settings.cpp line 485 or thereabouts accordingly: qDebug() << "Version 2 File!## My homemade khotkeys daemon is at play now. This line will be seen in the bash Konsole. ## "; also, one might want to look into coherently adapt LANG="en" /usr/bin/khelpcenter help:/kcontrol/khotkeys/index.html to launch english khotkeys, use this: LANG="en" kcmshell5khotkeys LANG="en" systemsettings5# or find it via system settings. -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 426920] improve the help texts
https://bugs.kde.org/show_bug.cgi?id=426920 fire f. changed: What|Removed |Added CC||fire...@firemail.cc -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 426920] improve the help texts
https://bugs.kde.org/show_bug.cgi?id=426920 --- Comment #1 from fire f. --- How does one produce a MAKRO key-sequence which contains the SPACE-character, for example: "is khotkey able to send these keys and not omit the SPACEs between the words?" and assign this MAKRO to the "F3" hotkey. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401317] Replace the search system with KFind
https://bugs.kde.org/show_bug.cgi?id=401317 --- Comment #2 from fire f. --- on the topic, Nate G. wrote: "As for the feature itself, for the past few years I'd been opposed to this, on the basis that people should just use the built-in Baloo-based search instead. But unfortunately the requests keep coming in, and there are use cases that Baloo doesn't work for (e.g. on external disks), so there does seem to be a need, or at least a desire. " So why is it that users like you oppose the view of the main guys? Why can you not accept the basis of decisions made for you by KDE, see above? I too suggested it and resigned to never see it implemented on these grounds. So its small wonder, users place the patches to Dolphin offsite and don't contribute via Phabricator. Just not worth to go against the opposition by superiors. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 401317] Replace the search system with KFind
https://bugs.kde.org/show_bug.cgi?id=401317 --- Comment #3 from fire f. --- https://phabricator.kde.org/D22594 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391677] Implement kfind as baloo alternative for main toolbar
https://bugs.kde.org/show_bug.cgi?id=391677 --- Comment #5 from fire f. --- opposition against such an obviously great feature has died down in 2020. finally, progress is on its march. more retarding impetus to come! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 384798] KFind launcher for the toolbar
https://bugs.kde.org/show_bug.cgi?id=384798 --- Comment #7 from fire f. --- adding KFind service menu in the right-click additionally won't hurt either. for those handy with the right button: https://bugs.kde.org/show_bug.cgi?id=395255 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 400949] Dolphin doesn't find linux hidden files & doesn't search if Baloo is deactivated
https://bugs.kde.org/show_bug.cgi?id=400949 --- Comment #2 from fire f. --- since 2020 , systemsettings "Search" has: "index hidden files and folders" i.e. those .files or dotfiles so new, its not even yet translated everywhere. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427465] Bookmarks: error if pdf-file was moved or renamed
https://bugs.kde.org/show_bug.cgi?id=427465 --- Comment #10 from fire f. --- A serious pdf reader should offer bookmark functionality like the OP and gazillions of users expect it. The "keditbookmarks" GUI standalone app has import / export functions. Some find/replace functinality for the document's path, e.g. using /home/bookmk ~/documents/ could tremendously enhance the power of Okular. For the moment, manual find/replace of the path does already allow users to maintain big bookmark-collections across machines and what not. 2 collaborating users would, however, use a standardized absolute path such as /home/bookies or make that a symbolic link (via: ln -s src targ ) into /~/documents in a particular language (such as: ~/Dokumente/ ) Worth repeating that without powerful portable bookmarks, which clearly are possible, Okular is not half the man it used to be in user's perception. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427465] Bookmarks: error if pdf-file was moved or renamed
https://bugs.kde.org/show_bug.cgi?id=427465 --- Comment #11 from fire f. --- but not even keditbookmark's own KHELP does point out the whole power of KDE bookmarks - like right there in KHELP ! But that will not deter power users from finding it out... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437747] New: KRunner item needs to remain in Dtop-right click menu for usability
https://bugs.kde.org/show_bug.cgi?id=437747 Bug ID: 437747 Summary: KRunner item needs to remain in Dtop-right click menu for usability Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: fire...@firemail.cc CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The latest Neon Developer has removed the ability to launch KRunner without taking the hand off the mouse, by no longer offering to place it in the core menu on the right mouse button. It used to be in that core place for decades. STEPS TO REPRODUCE 1. place cursor on empty spot of the desktop background. 2. click the right mouse button. 3. try to find the KRunner launch entry which use to be there since 1990. OBSERVED RESULT Usability and ergonomics suffer, as users are forced to move the right hand to and fro from mouse to keyboard without any good reason. It was much better before the item removal. EXPECTED RESULT People expect to operate KDE to a very large part with the mouse ONLY. They move the hand to the keyboard only if necessary. People expect to do this workflow: 1. right click, launch KRunner 2. click downArrow for history 3. launch the app from the history list this is the most convenient way to achieve it. All keyboard use is significantly more tedious. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon Developer live image as of today KDE Plasma Version: current today ADDITIONAL INFORMATION The reason given in Developer webchat was: The removal makes the choice list "less intimidating". Yet some bloat still still remains, such as the multiple wallpaper items, only 1 of which would be sufficient. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437747] KRunner item needs to remain in Dtop-right click menu for usability
https://bugs.kde.org/show_bug.cgi?id=437747 fire f. changed: What|Removed |Added CC||fire...@firemail.cc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437747] KRunner item needs to remain in Dtop-right click menu for usability
https://bugs.kde.org/show_bug.cgi?id=437747 --- Comment #1 from fire f. --- 3. launch the app from the history list without using the keyboard. Mouse-only usage as many users prefer it! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437747] KRunner item needs to remain in Dtop-right click menu for usability
https://bugs.kde.org/show_bug.cgi?id=437747 --- Comment #3 from fire f. --- steps 1. 2. 3. above are not "searching". these steps are just launching instead. Those are 2 separate usages. Obviously, searching something with the mouse ONLY is a trickier job. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437747] KRunner item needs to remain in Dtop-right click menu for usability
https://bugs.kde.org/show_bug.cgi?id=437747 --- Comment #4 from fire f. --- Putting a history list into Kickoff seems viable as long as it does not drive up the number of clicks required to launch an app, as compared to do it the KRunner way. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437747] KRunner item needs to remain in Dtop-right click menu for usability
https://bugs.kde.org/show_bug.cgi?id=437747 --- Comment #5 from fire f. --- sidenote: "GRun" is a gnome app similar to KRunner with good ergonomics, but there was package bitrot. Users must compile it themselves. GRun is a "minimum-number-of-clicks launcher", like KRunner and much UNLIKE Lancelot. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 410722] New: net profile editor messes up when VLAN is being used
https://bugs.kde.org/show_bug.cgi?id=410722 Bug ID: 410722 Summary: net profile editor messes up when VLAN is being used Product: plasma-nm Version: 5.16.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm Assignee: jgrul...@redhat.com Reporter: fire...@firemail.cc Target Milestone: --- SUMMARY while kcmshell5 kcm_networkmanagement works well with a "normal" pppoE-connection and ethernet-connections and so forth, it seems to support VLAN rather poorly. The nm-connection-editor from the Gnome NetworkManager suite works much better for VLAN, but cannot switch between ONLINE and OFFLINE. So currently while using this VLAN 7 profile, I do not utilize kcmshell5 kcm_networkmanagement at all because it just messes up everything in unpredictable ways and its display is not useful and is inconsistent. Since ISP Dt. Telekom has millions of customers, it is desirable for pppoE with VLAN frame-tagging to "7" to work as smoothly as a normal pppoE or as roaring-penguin-pppoE for that matter. STEPS TO REPRODUCE 1. follow https://gitlab.freedesktop.org/snippets/638 2. try to switch between ONLINE and OFFLINE 3. it won't work, so you must nmcli for that OBSERVED RESULT the kcmshell5 kcm_networkmanagement GUI is not much useable for controlling a VLAN profile, see also https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/222 EXPECTED RESULT I expected a VLAN 7 pppoE connection to work as smoothly as a non-VLAN connection SOFTWARE/OS VERSIONS Linux/KDE Plasma:current Manjaro rolling release KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.60.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION Kernel: 5.2.4-1-MANJARO -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 410722] net profile editor messes up when VLAN is being used
https://bugs.kde.org/show_bug.cgi?id=410722 fire f. changed: What|Removed |Added CC||fire...@firemail.cc -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 410722] net profile editor messes up when VLAN is being used
https://bugs.kde.org/show_bug.cgi?id=410722 fire f. changed: What|Removed |Added URL||https://gitlab.freedesktop. ||org/snippets/638 Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 410722] net profile editor messes up when VLAN is being used
https://bugs.kde.org/show_bug.cgi?id=410722 --- Comment #2 from fire f. --- I kinda presumed this after reading prior speculations in a Ubuntu forum which linked to the commit initially disabled VLAN completely in 2017 or so, before it was re-enabled. Maybe I can take a look at the sources myself. Let's see. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 410722] net profile editor messes up when VLAN is being used
https://bugs.kde.org/show_bug.cgi?id=410722 --- Comment #3 from fire f. --- To clarify, the package containing "kcmshell5 kcm_networkmanagement" is still installed and probably needs to be installed. But I don't click on it for editing the net profile to avoid trouble while using VLAN ID 7 frame-tagging. Instead, I use solely "nmcli" in a bash Konsole in order to set up the network and go online and offline. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 315636] vlan monitoring does not work. netdev.c in function processNetDev_(void) uses fixed position 7 parsing address when vlan names are longer
https://bugs.kde.org/show_bug.cgi?id=315636 fire f. changed: What|Removed |Added CC||fire...@firemail.cc -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 315636] vlan monitoring does not work. netdev.c in function processNetDev_(void) uses fixed position 7 parsing address when vlan names are longer
https://bugs.kde.org/show_bug.cgi?id=315636 --- Comment #3 from fire f. --- line 196 is still sscanf(strchr(buf, ':') + 1, "%llu . https://github.com/KDE/ksysguard/blob/master/ksysguardd/Linux/netdev.c while Gnome's NetworkManager can do VLAN fine, KDE's plasma-nm package is "untested" and indeed is not working with VLANs really neither BOND etc. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 387920] [RFE] Implement network priority using the main network list, via drag-and-drop
https://bugs.kde.org/show_bug.cgi?id=387920 --- Comment #8 from fire f. --- Created attachment 122033 --> https://bugs.kde.org/attachment.cgi?id=122033&action=edit priority connect may be implemeted already? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409774] Don't show "Network disconnected" notification after the disconnect button in the plasma-nm widget is clicked
https://bugs.kde.org/show_bug.cgi?id=409774 --- Comment #1 from fire f. --- always found that unnerving too, but luckily one can switch it off with 3 clicks. Cluttering the desktop with somewhat pointless notifications is being frowned upon. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 409774] Don't show "Network disconnected" notification after the disconnect button in the plasma-nm widget is clicked
https://bugs.kde.org/show_bug.cgi?id=409774 --- Comment #2 from fire f. --- at least we have a "do not disturb" mode by now, which I make use of heavily! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 378592] [RFE] SoftEther VPN Support
https://bugs.kde.org/show_bug.cgi?id=378592 --- Comment #2 from fire f. --- you can already use softether as a client very conveniently, just import the .ovpn config file and you're ready to go. I consider this case RESOLVED ! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 378592] [RFE] SoftEther VPN Support
https://bugs.kde.org/show_bug.cgi?id=378592 --- Comment #3 from fire f. --- do it via vpngate.net -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 350413] [RFE] [OpenVPN] ovpn file type should be recognized
https://bugs.kde.org/show_bug.cgi?id=350413 --- Comment #1 from fire f. --- since the Gnome surrogate is better than its KDE counterpart, why not associate .ovpn files in Dolphin using the command line : nm-connection-editor -i %f works like a charm and is like 3 clicks only! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 350413] [RFE] [OpenVPN] ovpn file type should be recognized
https://bugs.kde.org/show_bug.cgi?id=350413 --- Comment #2 from fire f. --- I don't think the kcmshell5 --args kcm_netw... GUI is scriptable. the above solution does not seem to have any disadvantages. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 350413] [RFE] [OpenVPN] ovpn file type should be recognized
https://bugs.kde.org/show_bug.cgi?id=350413 fire f. changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 350413] [RFE] [OpenVPN] ovpn file type should be recognized / filetype association [is poss!]
https://bugs.kde.org/show_bug.cgi?id=350413 fire f. changed: What|Removed |Added Summary|[RFE] [OpenVPN] ovpn file |[RFE] [OpenVPN] ovpn file |type should be recognized |type should be recognized / ||filetype association [is ||poss!] -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 398280] [RFE] Enhancement of plasma-nm for include proxy settings
https://bugs.kde.org/show_bug.cgi?id=398280 --- Comment #1 from fire f. --- nm-connection-editor does have proxy settings, just cannot establish conn or disconnect -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 393734] Plasmashell crashes, if plasma-nm is installed
https://bugs.kde.org/show_bug.cgi?id=393734 --- Comment #3 from fire f. --- some distros, e.g. Manjaro, have packages in their repo, which inevitably will crash other programs. Then they censor the crash reports about it and accuse the reporter. trademark Manjaro behaviour for many years, not kidding you. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 397489] MAC change not working via plasma-nm
https://bugs.kde.org/show_bug.cgi?id=397489 --- Comment #1 from fire f. --- plasma-nm has issues but I thought it was limited to "special" cases like VLAN. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 290989] [RFE] Make it possible to import FritzVPN-configuration files
https://bugs.kde.org/show_bug.cgi?id=290989 --- Comment #6 from fire f. --- This is a FritzBox proprietary format. nm-connection-editor -i vpngate.opvn will open the Open Format VPN however. Maybe its poss to transmogrify those Fritz files? nm-connection-editor -i %f as Dolphin file association is handy too. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 396530] [RFE][OpenVPN] Use nmcli importer
https://bugs.kde.org/show_bug.cgi?id=396530 --- Comment #2 from fire f. --- could someone please point out the filename or link to that shared library which plasma-nm could but does not use? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 407561] Delete applet config window and move its two options into the KCM
https://bugs.kde.org/show_bug.cgi?id=407561 --- Comment #2 from fire f. --- I confirm that the wording of the 2 options is not helpful, is has very little explanatory value. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410328] Open new instance of application with keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=410328 --- Comment #1 from fire f. --- see also https://forum.kde.org/viewtopic.php?f=66&t=160923#p420352 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410328] Open new instance of application with keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=410328 --- Comment #2 from fire f. --- it is "Icons-only task manager" , the plasmoid in the standard panel. while it is true that you cannot add any shortcut to Global Shortcuts , it might well serve your purpose to add somthing - namely a .khotkeys scheme - under Custom Shortcuts in the same KCM in systemsettings called "Shortcuts" granted, the whole thing may be a bit confusing. see also https://docs.kde.org/trunk5/en/kde-work ... otkeys.pdf with good explanations -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410328] Open new instance of application with keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=410328 --- Comment #3 from fire f. --- Created attachment 125026 --> https://bugs.kde.org/attachment.cgi?id=125026&action=edit explains all the confusing verbiage in KDE hotkeys https://docs.kde.org/trunk5/en/kde-workspace/kcontrol/khotkeys/khotkeys.pdf -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410328] Open new instance of application with keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=410328 fire f. changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |NOT A BUG --- Comment #4 from fire f. --- seems like a non-bug to me, reporter please confirm whether a custom shortcut fulfills your needs. global shortcuts are not there to do what you want, I presume. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 395255] improve usability by launching KFind from right-click (servicemenu) rather than the current file FIND toil & labour
https://bugs.kde.org/show_bug.cgi?id=395255 fire f. changed: What|Removed |Added Summary|improve usability by|improve usability by |launching KFind from|launching KFind from |right-click (servicemenu) |right-click (servicemenu) |rather than the current |rather than the current |file FIND ordain|file FIND toil & labour -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 226370] GUI for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=226370 --- Comment #6 from fire f. --- while we are at it... there are some very compact keyboard and touchpad combos out there, e.g. by Rapoo Inc., which require a way to disable the touchpad, which shows in xinput as a mouse, in order to be able to type without accidental touches on the pad being located right next to the enter-key. currently, a scheme.khotkeys file can be imported to use like F1 and F2 to do this. But when KDE drops the whole "KCM Shortcuts" due to lack of maintainers, a gaping usability problem will suddenly rip open! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 351646] let the user identify the KCM with baloo with adding the string "Baloo" somewhere.
https://bugs.kde.org/show_bug.cgi?id=351646 --- Comment #6 from fire f. --- that would be less of a concern if baloo did simply do its job rather than have the reputation of eating 90% of disk space and CPU cycles in many cases. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 351646] let the user identify the KCM with baloo with adding the string "Baloo" somewhere.
https://bugs.kde.org/show_bug.cgi?id=351646 --- Comment #7 from fire f. --- at leastK help centre refers to https://community.kde.org/Baloo/Configuration at one stage. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390177] Upgrade to 5.12 activated window decoration menu button, making in-app menu bars disappear
https://bugs.kde.org/show_bug.cgi?id=390177 fire f. changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #39 from fire f. --- (In reply to Michal from comment #36) > Finally found the solution but just for yourself! > System Settings -> Application Style -> Widget Style -> Applications > Widget Style: Choose GTK+ instead of Breeze. has zero effect here. > This solved the problem for me, > No idea what prompts the issue. so now we know. > Seems to me quite a serious bug, as it completely cripples > the affected programs. losing the main menu of all KDE apps effectively nukes the installation. This is even worse considering that those separated menus are 100% nonsensical and no one will ever use them in earnest. seems like a waste of time to me. usability and ergonomics are next to zero. separate main menu turn a good useable GUI into broken junk with just the click of a button. since this huge problem was "FIXED" as they say these days, where is the link to bug report of all people still suffering from this desaster? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390177] Upgrade to 5.12 activated window decoration menu button, making in-app menu bars disappear
https://bugs.kde.org/show_bug.cgi?id=390177 fire f. changed: What|Removed |Added CC||fire...@firemail.cc --- Comment #40 from fire f. --- while those separated menus work as expected in Manjaro KDE, they are broken in current Fedora wokstation 31. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390177] Upgrade to 5.12 activated window decoration menu button, making in-app menu bars disappear
https://bugs.kde.org/show_bug.cgi?id=390177 fire f. changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 415164] ctrl+alt+(left|right) conflict on yakuake
https://bugs.kde.org/show_bug.cgi?id=415164 --- Comment #1 from fire f. --- that so many distros force that yakuake nonsense down users' throats is quite outrageous. Serious people don't need a gamified console. Run with # konsole --background-mode # parameter, Konsole offers that popup feature already. Having said that, I did notice JWM (Joe's window manager as a replacement of kwin_x11) crashing when it tried to assign hotkeys which were in use already, say by Konsole. So one has to use non-occupied hotkeys. Its a bit quirky there. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 414880] add option for background mode windows to auto-hide on focus loss
https://bugs.kde.org/show_bug.cgi?id=414880 --- Comment #1 from fire f. --- like a bash -c konsole --background-mode to unhide / hide / unhide etc. with the same global shortcut might make sense. But let us not use gamified apps like yakuake as a role model in KDE. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 414879] After closing a window in background mode, background mode shortcut is disabled for any other background mode windows
https://bugs.kde.org/show_bug.cgi?id=414879 --- Comment #1 from fire f. --- might be intended behaviour: a closed window is a goner. you cannot bring it back up, since it closed and terminated. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407821] Terminal bell does not trigger system (visual) bell
https://bugs.kde.org/show_bug.cgi?id=407821 --- Comment #7 from fire f. --- I struggled with this as well. Very complicated! had to remove non-connected bluetooth audiodevices and reboot. finally it works as kinda expected. should be simpler so as to not be unaware of big issues because audio notifications kinda drop dead. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408458] The window icon is changing to BELL
https://bugs.kde.org/show_bug.cgi?id=408458 --- Comment #7 from fire f. --- (In reply to Juraj from comment #5) > When I change the icon in Profile settings to something else than default > the window icon is restored after the bell event is "gone". cool for you. I cannot get the icon changed at all on Fedora31. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408458] The window icon is changing to BELL
https://bugs.kde.org/show_bug.cgi?id=408458 --- Comment #8 from fire f. --- ah well... its just the TAB icon, not the window-icon. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412840] Konsole doesn't honour accessibility setting 'flash window'
https://bugs.kde.org/show_bug.cgi?id=412840 --- Comment #2 from fire f. --- noticed it on Fedora 31 too -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408498] "Shortcut Schemes" -> "Current Scheme" specified in custom Konsole profile has no effect
https://bugs.kde.org/show_bug.cgi?id=408498 --- Comment #2 from fire f. --- scheme.kksrc import & export has moved from "manage schemes" button on that page to "File" button. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408498] "Shortcut Schemes" -> "Current Scheme" specified in custom Konsole profile has no effect
https://bugs.kde.org/show_bug.cgi?id=408498 --- Comment #3 from fire f. --- (In reply to fire f. from comment #2) > scheme.kksrc import & export has moved from "manage schemes" button on that > page to "File" button. example content now: [konsole][Global Shortcuts] Konsole Background Mode=Meta+F -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408498] "Shortcut Schemes" -> "Current Scheme" specified in custom Konsole profile has no effect
https://bugs.kde.org/show_bug.cgi?id=408498 --- Comment #4 from fire f. --- ... with "Meta" being the Windows-Key. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357965] [Regression] Konsole does not allow its hotkey to show/hide Konsole (à la Yakuake, Kuake, Guake, Tilda, the "terminal emulator" present in Quake and other games, etc.)
https://bugs.kde.org/show_bug.cgi?id=357965 --- Comment #2 from fire f. --- works now after a recent commit. close this? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411579] GPU accelerated terminal
https://bugs.kde.org/show_bug.cgi?id=411579 --- Comment #3 from fire f. --- I installed kitty but I cannot see the point. KDE is well advised not to waste effort into such an endeavour like kitty. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 305162] Konsole notification "Bell in session" should have button to bring up that session
https://bugs.kde.org/show_bug.cgi?id=305162 --- Comment #9 from fire f. --- does systemd journal learn of BELL events ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414342] New: Why on Earth does "git remove" irrevocably destroy the file instead of ignore it?
https://bugs.kde.org/show_bug.cgi?id=414342 Bug ID: 414342 Summary: Why on Earth does "git remove" irrevocably destroy the file instead of ignore it? Product: dolphin Version: 19.07.80 Platform: Manjaro OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: plugins: git Assignee: sebast...@sebastian-doerner.de Reporter: fire...@firemail.cc CC: kfm-de...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. git init 2. touch aaa 3. git add aaa 4. in Dolphin, right click and click "git remove" while file "aaa" is marked OBSERVED RESULT file "aaa" is destroyed forever! Not in trashbin or anything! gone forever! EXPECTED RESULT file aaa should be ignored or booked out of git i.e. "unstaged", but of course REMAIN ON DISK ! SOFTWARE/OS VERSIONS: Linux/KDE Plasma, see above -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414342] Why on Earth does "git remove" irrevocably destroy the file instead of ignore it?
https://bugs.kde.org/show_bug.cgi?id=414342 fire f. changed: What|Removed |Added CC||fire...@firemail.cc -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414342] Why on Earth does "git remove" irrevocably destroy the file instead of ignore it?
https://bugs.kde.org/show_bug.cgi?id=414342 fire f. changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414342] Why on Earth does "git remove" irrevocably destroy the file instead of ignore it?
https://bugs.kde.org/show_bug.cgi?id=414342 --- Comment #2 from fire f. --- yes, since the instruction "git remove" does not even exist, just like the instruction "cheryypick" asf., I expected to definietly keep the file on disk, just book it out of git. It coulkd at least been trash-binned ! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414342] Why on Earth does "git remove" irrevocably destroy the file instead of ignore it?
https://bugs.kde.org/show_bug.cgi?id=414342 --- Comment #3 from fire f. --- meaning that "git remove" just reverses "git add" but not totally destroy it. That is what intuitively many would presume. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414342] Why on Earth does "git remove" irrevocably destroy the file instead of ignore it?
https://bugs.kde.org/show_bug.cgi?id=414342 --- Comment #4 from fire f. --- (In reply to Nate Graham from comment #1) > If you don't want files in your git repo removed on disk, don't use git's > remove operation. my file was not even "in the git repo" proper, since no commit was yet made. So the menu entry should change from "git remove" to "git destroy" to not let anyone believe the file can be gotten back from the git repo necessarily. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414342] Why on Earth does "git remove" irrevocably destroy the file instead of ignore it?
https://bugs.kde.org/show_bug.cgi?id=414342 --- Comment #8 from fire f. --- An icon "delete file" has been present forever, and people know hwt it means. For usability's sake, there should be a "git ignore" icon. "git remove" seems redundant, since it just does the same as "file delete". People do not expect to have their files destroyed forever in git. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414342] Why on Earth does "git remove" irrevocably destroy the file instead of ignore it?
https://bugs.kde.org/show_bug.cgi?id=414342 --- Comment #9 from fire f. --- Thanks, Nate, wonderful ! indeed, git fsck --name-objects git show 6809d…… will display the "lost file" to make a copy ! glad, I got the file back. Feels like bit of a rough edge initially! Again, thanks for your help! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414342] usability: "git remove" kills file into a dangling blob, recover it with git fsck; git show
https://bugs.kde.org/show_bug.cgi?id=414342 fire f. changed: What|Removed |Added Summary|Why on Earth does "git |usability: "git remove" |remove" irrevocably destroy |kills file into a dangling |the file instead of ignore |blob, recover it with git |it? |fsck; git show -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414342] usability: "git remove" kills file into a dangling blob, recover it with git fsck; git show
https://bugs.kde.org/show_bug.cgi?id=414342 fire f. changed: What|Removed |Added Version Fixed In||BUG: 414342 FIXED-IN: ||19.12.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414342] usability: "git remove" kills file into a dangling blob, recover it with git fsck; git show
https://bugs.kde.org/show_bug.cgi?id=414342 --- Comment #10 from fire f. --- Thanks David as well! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375207] bring back the historylist (downarrow) for better mouse (keyboardless) usability
https://bugs.kde.org/show_bug.cgi?id=375207 fire f. changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #14 from fire f. --- (In reply to Christoph Feck from comment #13) > This ticket is fixed in Plasma 5.13.0, which is not released yet. If you > want to test the change, try KDE neon dev unstable. Excactly as I predicted, in Plasma 5.14.3 , current in rolling rel. Manjaro, the down-arrow is gone away again. Back to the old bad unergonomic situation. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375207] bring back the historylist (downarrow) for better mouse (keyboardless) usability
https://bugs.kde.org/show_bug.cgi?id=375207 fire f. changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375207] bring back the historylist (downarrow) for better mouse (keyboardless) usability
https://bugs.kde.org/show_bug.cgi?id=375207 fire f. changed: What|Removed |Added CC||fire...@firemail.cc -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375207] bring back the historylist (downarrow) for better mouse (keyboardless) usability
https://bugs.kde.org/show_bug.cgi?id=375207 fire f. changed: What|Removed |Added Version Fixed In|5.13.0 reappeared in 5.14.3 |5.13.0 then reappeared in ||5.14.3 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375207] bring back the historylist (downarrow) for better mouse (keyboardless) usability
https://bugs.kde.org/show_bug.cgi?id=375207 fire f. changed: What|Removed |Added Version Fixed In|5.13.0 |5.13.0 reappeared in 5.14.3 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375207] bring back the historylist (downarrow) for better mouse (keyboardless) usability
https://bugs.kde.org/show_bug.cgi?id=375207 --- Comment #15 from fire f. --- (In reply to fire f. from comment #14) > (In reply to Christoph Feck from comment #13) file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/runcommand/RunCommand.qml these .qml files change over the vearous themes like "breeze" , "oxygen", etc. concerning history-list. Should they not be the same ? qmlviewer-qt4 .⁄RunCommand.qml to see a bunch of errors as usual. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375207] bring back the historylist (downarrow) for better mouse (keyboardless) usability
https://bugs.kde.org/show_bug.cgi?id=375207 --- Comment #16 from fire f. --- seemingly the current master/tree version works. I removed the .qml manually and put the master version in its place. relogin, verified Alt-F2 does nothing without the .qml , then copyied the right .qml, and the down-arrow was back like it should be. 6 changes were made, maybe some intermediate version is not well. this one works: https://cgit.kde.org/plasma-workspace.git/plain/lookandfeel/contents/runcommand/RunCommand.qml?id=8227e4e2b7f034166cbf5efb01e4e715028b4606 save in raw mode to /usr/ to have the arrow back in place. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 375207] bring back the historylist (downarrow) for better mouse (keyboardless) usability
https://bugs.kde.org/show_bug.cgi?id=375207 --- Comment #17 from fire f. --- assuming the distros will get a correct version anytime soon, the bug report may be closed again, I presume. Please recheck, though. Thx! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 393052] Download Krunner's Search Plugins from GHNS
https://bugs.kde.org/show_bug.cgi?id=393052 --- Comment #4 from fire f. --- (In reply to Kai Uwe Broulik from comment #2) > Is this even possible, given KRunner plugins are all binary and as such need > to be compiled before use? > > We could look into a KRunner JS/QML/Python API (also to ease 3rd party > plugin creation) but as of now we don't have that. I made a krunner plugin in a few lines of python and it worked. Like a mini demo. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 283738] krunner: support for aliases
https://bugs.kde.org/show_bug.cgi?id=283738 --- Comment #3 from fire f. --- there is a ca. 5 line python demo of a krunner-plugin, which could be adapted to perform such a task. easy to test. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 386510] Show help of the active plugins in krunner
https://bugs.kde.org/show_bug.cgi?id=386510 --- Comment #3 from fire f. --- (In reply to francisco_t from comment #0) > I think krunner is an underrated tool because for a new user it is extremely > difficult to know how it works. true! On top of that, if you try to ameliorate this dire situation in the wiki (by editing), you'll meet with a lot of hostility there so you drop that idea real quick. -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 401000] New: many colour schemes have poor contrast for SystemD log
https://bugs.kde.org/show_bug.cgi?id=401000 Bug ID: 401000 Summary: many colour schemes have poor contrast for SystemD log Product: Systemd KCM Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: rthoms...@gmail.com Reporter: fire...@firemail.cc Target Milestone: --- Created attachment 116279 --> https://bugs.kde.org/attachment.cgi?id=116279&action=edit most color schemes have poor contrast like this one hover the mouse over a KCM-systemd line so the log appears, say of a particular service. of the standard 10 colour schemes, most will have very poor contrast, the log is unreadable (light color on another light color). Only the "steel" scheme works OK. Do we need better schemes or better SystemD ? -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 401000] many colour schemes have poor contrast for SystemD log
https://bugs.kde.org/show_bug.cgi?id=401000 fire f. changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 401000] many colour schemes have poor contrast for SystemD log
https://bugs.kde.org/show_bug.cgi?id=401000 fire f. changed: What|Removed |Added CC||fire...@firemail.cc -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 401000] many colour schemes have poor contrast for SystemD log
https://bugs.kde.org/show_bug.cgi?id=401000 --- Comment #2 from fire f. --- scheme "elementary Luna" from GNHS works, most other schemes are very poor in contrast. -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 362554] systemd spelling
https://bugs.kde.org/show_bug.cgi?id=362554 --- Comment #2 from fire f. --- I feel the grammar nazis will have to eventually yield. systemd will not stand. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 138866] Change font face and size for GTK apps too
https://bugs.kde.org/show_bug.cgi?id=138866 --- Comment #3 from fire f. --- kcmshell5 kde-gtk-config does it via button font "choose" but it is highly unergonomic to have this separate, like 8 clicks away from the KDE font settings. They belong together in a single dialogue, from a user perspective. maybe for a while, the old gtk-button should navigate / link to the KDE-font dialog -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 138866] Change font face and size for GTK apps too
https://bugs.kde.org/show_bug.cgi?id=138866 --- Comment #4 from fire f. --- while we're at it, we could also link to the font settings of Konsole in the same dialogue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399961] Uncheck "Confirm logout" by default
https://bugs.kde.org/show_bug.cgi?id=399961 --- Comment #6 from fire f. --- I dislike the default settings as well. With them there just is too much "log out business". I simplified it a lot: right-click , leave , then I am immediately in the Greeter with the REBOOT button. Thankfully that one does NOT ask for yet another confirmation. All this stuff in the menus , Lancelot or who the heck knows wherever is just too complicated: way too much confirmation business. I used spend to half of the day entering the root password or clicking "Yes I really want to..." (e.g. reboot). Quite a nuisance. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 254560] Associate application as the default for all of its known compatible mimetypes
https://bugs.kde.org/show_bug.cgi?id=254560 --- Comment #5 from fire f. --- https://userbase.kde.org/Dolphin/File_Management#Change_a_File_Association_on-the-fly now describes how to associate in single / multiple mode. unfortunately, the crucial feature InitialPreference=2 X-KDE-InitialPreference=3 which would be needed to be no nuisance by kicking out the old apps did not work for me. Given that X-KDE-InitialPreference=3 can be made to work we're almost there. Of course, a little GUI handling the .desktop files as suggested (like windows) would be awesome! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 254560] Associate application as the default for all of its known compatible mimetypes
https://bugs.kde.org/show_bug.cgi?id=254560 fire f. changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 141946] easy way to enable/disable static word wrap
https://bugs.kde.org/show_bug.cgi?id=141946 --- Comment #8 from fire f. --- there is a toolbar button, only it must be placed as visible manually. -- You are receiving this mail because: You are watching all bug changes.
