[dolphin] [Bug 406725] Allow folders to be excluded for thumbnail generation
https://bugs.kde.org/show_bug.cgi?id=406725 --- Comment #13 from Szczepan Hołyszewski --- Perhaps a system level solution could work. If we could somehow control the user/group under which the thumbnailer process runs, this would instantly make thumbnailing opt-in globally. By creating a group named "crawlers" and runing the thumbnailer as nobody:crawlers, one could allow thumbnails in selected directories by granting read access to crawlers with ACL. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #26 from Szczepan Hołyszewski --- kcachegrind is another program that I find myself unable to run 100% in English when the current user's locale is Polish. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482694] New: Dolphin won't show pixel sizes of images on Samba shares
https://bugs.kde.org/show_bug.cgi?id=482694 Bug ID: 482694 Summary: Dolphin won't show pixel sizes of images on Samba shares Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: rula...@wp.pl CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin won't show pixel size (or any baloo-ish data/metadata) for images on Samba shares. STEPS TO REPRODUCE 1. Place the attached file in a shared folder on a Windows machine 2. Open the folder as a Samba share in dolphin 3. Select the file, note what details are shown in the information panel 4. Copy the file to your home directory 5. Select the file in your home directory, note what details are shown in the information panel OBSERVED RESULT Fewer details are shown when the file is on a remote share than when it is in the home directory. EXPECTED RESULT Exactly the same details should be shown as when the file is in the home directory. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B24 System Version: 2.0 ADDITIONAL INFORMATION Windows machine: Windows 10 Pro -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481932] "Unable to create KIO worker. Unknown protocol 'appstream'." error when using "Get " feature
https://bugs.kde.org/show_bug.cgi?id=481932 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #12 from Szczepan Hołyszewski --- How can a user fix this for themselves without waiting for the fix to percolate through normal channels? -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 45191] Ability to exclude folders from search
https://bugs.kde.org/show_bug.cgi?id=45191 --- Comment #11 from Szczepan Hołyszewski --- > The last thing you want to do is adopt a Fischer-Price Gnome app interface > that you can only operate with your thumbs, your fists and your forehead. These days I only revisit lost cause bug reports for random pearls of UX humour like this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455913] [Wayland + Nvidia] Plasma popups (e.g. Kickoff and KRunner) sometimes stops showing after opening / closing them a few times
https://bugs.kde.org/show_bug.cgi?id=455913 --- Comment #32 from Szczepan Hołyszewski --- (In reply to Szczepan Hołyszewski from comment #31) > Notably there seems to be no krunner.desktop anywhere. There is /usr/share/kglobalaccel/org.kde.krunner.desktop, but copying it to ~/.local/share/applications and editing there has no effect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479163] New: $HOME/.local/share/applications/org.kde.krunner.desktop ignored on startup
https://bugs.kde.org/show_bug.cgi?id=479163 Bug ID: 479163 Summary: $HOME/.local/share/applications/org.kde.krunner.deskto p ignored on startup Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: rula...@wp.pl CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY The usual way to customize an application is to copy its .desktop file to ~/.local/share/applications and modify it there. It seems that Plasma doesn't check for a copy of org.kde.krunner.desktop in ~/.local/share/applications and always uses the "factory" copy in /usr/share/kglobalaccel. STEPS TO REPRODUCE 1. `cp /usr/share/kglobalaccel/org.kde.krunner.desktop ~/.local/share/applications` 2. Edit the override file to set `Exec=env QT_QUICK_BACKEND=software /usr/bin/krunner` in an attempt to work around #455913 3. Log out & in OBSERVED RESULT The symptom of #455913 manifests, indicating that the ~/.local copy of the desktop file was not taken into consideration when starting krunner. (It has been already experimentally determined that killing krunner and re-running it manually with the workaround applied _does_ alleviate the symptom on this system). EXPECTED RESULT The symptom of #455913 should not manifest, because the workaround should be in effect as a result of the ~/.local/share/applications/org.kde.krunner.desktop override file being used by Plasma to launch krunner, instead of the "factory" file. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B24 System Version: 2.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455913] [Wayland + Nvidia] Plasma popups (e.g. Kickoff and KRunner) sometimes stops showing after opening / closing them a few times
https://bugs.kde.org/show_bug.cgi?id=455913 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #31 from Szczepan Hołyszewski --- (In reply to Dmitrii Chermnykh from comment #30) > setting `QT_QUICK_BACKEND=software` works as a workaround Is there a way to apply this workaround permanently? Notably there seems to be no krunner.desktop anywhere. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing on Wayland with Basic render loop and Non-Intel GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #92 from Szczepan Hołyszewski --- (In reply to Nate Graham from comment #74) > (In reply to Konstantin from comment #73) > > Please explain what parameter needs to be changed and where it is. I don't > > understand. > Search for "plasma renderer" in KRunner or Kickoff and launch it. In that > window, switch to the "Threaded" option for the "Render Loop" combobox. No results from that search. There must be some "normal" way to launch whatever configuration UI it is that you have in mind - like a CLI command, a particular executable or something. -- You are receiving this mail because: You are watching all bug changes.
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #62 from Szczepan Hołyszewski --- (In reply to tagwerk19 from comment #61) > Still see this in KVM Fedora 36 guests, independent of the choice of QXL and > Virtio graphics and X11 or Wayland logon. > > Editing: > /etc/security/pam_env.conf > and adding: > QT_QUICK_BACKEND DEFAULT=software > is still needed This looks like something that instructs something to do something in software rather than using hardware. How does emulating hardware functionality in software make things faster / less CPU intensive? -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 473951] Filelight does not honor directory exclusion list or filesystem boundary option
https://bugs.kde.org/show_bug.cgi?id=473951 --- Comment #6 from Szczepan Hołyszewski --- (In reply to fanzhuyifan from comment #5) > Seems to be caused by this commit: > https://invent.kde.org/utilities/filelight/-/commit/ > 659a3e487cd1d1e5d573892d938233aa4f52202a I can understand how that commit breaks manual exclusions, but how does it break the filesystem boundary option? -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 473951] Filelight does not honor directory exclusion list or filesystem boundary option
https://bugs.kde.org/show_bug.cgi?id=473951 --- Comment #3 from Szczepan Hołyszewski --- While this bug is being fixed, please recommend an alternative utility that CAN, as opposed to CANNOT, help me find disk space hogs on a specific partition. Not having this functionality hurts me a lot: I have the root partition 95% filled and Filelight's report is useless without being able to limit the scan to the partition in question. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 473951] Filelight does not honor directory exclusion list or filesystem boundary option
https://bugs.kde.org/show_bug.cgi?id=473951 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #2 from Szczepan Hołyszewski --- *** Bug 474479 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 474479] Filelight scans across filesystem boundaries even though the setting is off
https://bugs.kde.org/show_bug.cgi?id=474479 Szczepan Hołyszewski changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Szczepan Hołyszewski --- *** This bug has been marked as a duplicate of bug 473951 *** -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 474479] Filelight scans across filesystem boundaries even though the setting is off
https://bugs.kde.org/show_bug.cgi?id=474479 Szczepan Hołyszewski changed: What|Removed |Added Platform|Other |Archlinux -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 474479] New: Filelight scans across filesystem boundaries even though the setting is off
https://bugs.kde.org/show_bug.cgi?id=474479 Bug ID: 474479 Summary: Filelight scans across filesystem boundaries even though the setting is off Classification: Applications Product: filelight Version: 23.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rula...@wp.pl CC: martin.sandsm...@kde.org Target Milestone: --- SUMMARY Turning "Scan across filesystem boundaries" has no effect. Filelight scans across filesystem boundaries anyway. STEPS TO REPRODUCE 1. Disable "Scan across filesystem boundaries" 2. Scan the root directory on a system with multiple partition OBSERVED RESULT Scanning takes a long time and results contain data scanned from various partitions mounted under `/mnt`. EXPECTED RESULT Scanning should be fast (only 1 partition on NVMe) and results should only contain data from the partition mounted at `/`. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409524] _KDE_NET_WM_BLUR_BEHIND_REGION=0 does not always cause window backgrounds to be blurred
https://bugs.kde.org/show_bug.cgi?id=409524 --- Comment #25 from Szczepan Hołyszewski --- To add a feedback data point 4 years later: I ended up no longer using any transparency or blurring. It is much more headache than wow, with all the quirks, inconsistencies and corner cutting described and analyzed in this report. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 474252] [feature][privacy] temporarily suspend outgoing communication to paired devices
https://bugs.kde.org/show_bug.cgi?id=474252 --- Comment #1 from Szczepan Hołyszewski --- 5. Obviously, the would-be outgoing messages blocked by the privacy mode must be dropped entirely. They must NOT be buffered and then replayed once the privacy mode is disabled. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 474252] New: [feature][privacy] temporarily suspend outgoing communication to paired devices
https://bugs.kde.org/show_bug.cgi?id=474252 Bug ID: 474252 Summary: [feature][privacy] temporarily suspend outgoing communication to paired devices Classification: Applications Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: rula...@wp.pl CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY I would like functionality in kdeconnect that would allow me to temporarily suspend all outgoing communication with paired devices. If this effect can be achieved simply by temporarily disabling all plugins, then I would like a convenient UI to do (and indicate) just that. If kdeconnect possesses any "core" (i.e. not plugin-supplied) functionality that involves sending any information to paired devices as a result of any actions I take on the PC, then I would like that communication to also be suspended while the privacy mode is active. Workarounds, and why they are unsatisfactory: 1. Unpair all devices and later re-pair them once you no longer need the "privacy mode". This is inconvenient because it requires action to be taken on both ends of the pairing. 2. Manually disable all plugins and later re-enable them once you no longer need the "privacy mode". This is O(n) in the number of plugins rather than O(1), thus rather cumbersome, and possibly insufficient if there is any "core" functionality that cannot be suspended by disabling plugins. Details of desired functionality: 1. A "Suspend communication" or "Privacy mode" command not too many levels deep from a click on the kdeconnect tray icon; preferably an icon button on the title bar of the popup, next to the settings and pin buttons. 2. An overlay icon on top of the kdeconnect tray icon to indicate the privacy mode (possibly the same that is used on the volume control icon when muted). 3. The suspension of communication should be unidirectional: it is only supposed to prevent the possibility that something (like showing a notification about a video I am playing) will accidentally "happen" on _other_ devices as a result of my actions on the _desktop_. It is not supposed to block any functionality that allows me to control or send information to the desktop from the other devices. 4. The suspension of communication must be genuine: the communication must really be prevented from being sent over the network, rather than merely marked as "pretend you didn't hear". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 471901] Clicking Compact View temporarily behaves like Icons View (text below icons)
https://bugs.kde.org/show_bug.cgi?id=471901 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #3 from Szczepan Hołyszewski --- While this bug doesn't cause any substantial denial of functionality, the sheer annoyance factor warrants classifying is as something bigger than "minor". -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449020] No way to elevate read permissions when opening a file, no error, blank document shown
https://bugs.kde.org/show_bug.cgi?id=449020 --- Comment #2 from Szczepan Hołyszewski --- As of 2023.04.3 there is an in-window notification about insufficient permissions to read the file. This is better than no warning at all, but I still think that proper permission elevation should be supported. -- You are receiving this mail because: You are watching all bug changes.
[kweather] [Bug 471377] Add a map widget to location search
https://bugs.kde.org/show_bug.cgi?id=471377 Szczepan Hołyszewski changed: What|Removed |Added Summary|Add an embedded map widget |Add a map widget to |to location search |location search -- You are receiving this mail because: You are watching all bug changes.
[kweather] [Bug 471377] New: Add an embedded map widget to location search
https://bugs.kde.org/show_bug.cgi?id=471377 Bug ID: 471377 Summary: Add an embedded map widget to location search Classification: Applications Product: kweather Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: usability Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rula...@wp.pl CC: espi...@gmail.com Target Milestone: --- SUMMARY There is no way to disambiguate among identically named towns/villages when adding locations to kweather. STEPS TO REPRODUCE 1. Try adding Zachełmie OBSERVED RESULT There are two entries for "Zachełmie | Poland", corresponding to two real villages with the same name hundreds of kilometers apart. There is no way to tell them apart in kweather. If you add one, the UI provides no information that could help to know whether you chose the right one. Basically the only way is to add one provisionally, then watch the weather outside, and if it's poorly correlated with what kweather says, it's probably the wrong one. EXPECTED RESULT There should be a map widget embedded in the location search dialog, showing the geographical vicinity of the chosen location. Additionally, the main UI should have a button to show the current location on a map. Displaying latitude and longitute somewhere wouldn't harm either. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #24 from Szczepan Hołyszewski --- (In reply to Nate Graham from comment #23) > I have not tried, as getting translations applied to my built-from-source > KDE code isn't trivial. If you currently lack the capability to reproduce l10n issues, wouldn't it be worthwile to step back and do something about that? Why are translations even "applied to (...) code"? As far as I understand, there's one locale-agnostic code, and there are message catalogs, and "applying" a locale should happen entirely at runtime. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468897] Settings pane does not size to fit content when a localization has longer strings
https://bugs.kde.org/show_bug.cgi?id=468897 --- Comment #6 from Szczepan Hołyszewski --- Created attachment 158381 --> https://bugs.kde.org/attachment.cgi?id=158381=edit Clipped buttons in the sidebar Used `spectacle --new-instance`. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468897] Settings pane does not size to fit content when a localization has longer strings
https://bugs.kde.org/show_bug.cgi?id=468897 --- Comment #4 from Szczepan Hołyszewski --- More specifically, the first tab of the sidebar has two sections (labels backtranslated, may differ from original): "Make a new screenshots" "Screenshot settings" The first section contains a number of command buttons, and it's those buttons that are clipped on the right. The second section appears OK, and the checkboxes' labels are wrapped to the sidebar's width. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468897] Settings pane does not size to fit content when a localization has longer strings
https://bugs.kde.org/show_bug.cgi?id=468897 --- Comment #3 from Szczepan Hołyszewski --- (In reply to Noah Davis from comment #2) > By "settings pane", do you mean the sidebar on the right with the checkboxes > for things like whether or not to include the mouse pointer? A picture would > help us find the part of the UI that needs to be fixed. Yes, that's what I mean. Please instruct me how to obtain a screenshot of the Spectacle window itself. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468897] Settings pane does not size to fit content when a localization has longer strings
https://bugs.kde.org/show_bug.cgi?id=468897 --- Comment #1 from Szczepan Hołyszewski --- ERRATA: OBSERVED RESULT: The UI in the first tab of the settings pane is clipped; the settings pane does * not * grow in width to fit content. (Please, PLEASE, upgrade to a bugtracker that allows fixing typos). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468897] New: Settings pane does not size to fit content when a localization has longer strings
https://bugs.kde.org/show_bug.cgi?id=468897 Bug ID: 468897 Summary: Settings pane does not size to fit content when a localization has longer strings Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: rula...@wp.pl CC: k...@david-redondo.de Target Milestone: --- SUMMARY Due to longer button labels in Polish localization, the UI in the first tab of the settings pane to the right of the screenshot area has larger content-determined minimum size than the settings pane can accomodate, and the settings pane fails to resize to fit contents, resulting in clipped UI. I failed to figure out how to make a screenshot of Spectacle itself, so no screenshot. STEPS TO REPRODUCE 1. Launch spectacle OBSERVED RESULT The UI in the first tab of the settings pane is clipped; the settings pane does grow in width to fit content. EXPECTED RESULT The UI in the first tab of the settings pane shouldn't be clipped; the settings pane should grow in width to fit content. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Couldn't figure out how to make a screenshot of the spectacle window itself, so no screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447717] plasmashell crashes when hovering or clicking items on the Panel due to "zwp_linux_buffer_params_v1.add" protocol error
https://bugs.kde.org/show_bug.cgi?id=447717 --- Comment #79 from Szczepan Hołyszewski --- (In reply to Fushan Wen from comment #77) > I think the bug has been mitigated in 5.27.0 due to some changes in the task > manager's tooltip. Nope, 5.27.0 here and writing this without plasmashell running because it crashed when I hovered over the panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465992] Multiple symptoms of possibly one underlying issue after upgrading to 5.27
https://bugs.kde.org/show_bug.cgi?id=465992 --- Comment #4 from Szczepan Hołyszewski --- I agreee that this is not a bug. It is a disaster. And this is not a bug report, it is a disaster report. Unfortunately there is no separate disasters tracker available at disasters.kde.org, so all I can do is report it here. There is also no official guideline document on reporting disasters, so the report is kind of free-form. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465992] Multiple symptoms of possibly one underlying issue after upgrading to 5.27
https://bugs.kde.org/show_bug.cgi?id=465992 Szczepan Hołyszewski changed: What|Removed |Added Resolution|NOT A BUG |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from Szczepan Hołyszewski --- [posted prematurely, because saving the edited title apparently submits the comment too] (In reply to Nicolas Fella from comment #1) > Please read https://community.kde.org/Get_Involved/Issue_Reporting before > reporting further bugs. TL;DR: This Is Different. Long version: I know how to report regular bugs, and I have a record on this bugtracker to prove it. This is not a regular bug, therefore this bug report is not a regular bug report. This is a situation where a user logs in to a newly updated desktop and is met with an avalanche of glitches, none of which were present before the update. Nothing remotely like this has happened in my 15+ years with KDE. This is a never before seen situation that the document you quoted doesn't cover? > https://community.kde.org/Get_Involved/Issue_Reporting#Remember_your_manners I fail to find in that document an interdiction against stating facts. > https://community.kde.org/Get_Involved/ > Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket I am reporting multiple _symptoms_ that manifested all at once as a result of a single update. When something like that happens, it is quite possible that all the symptoms are different manifestation of a single bug, but I am not able to ascertain whether that's the case, so the next best thing I can do is report the symptoms, and YES report them together, because their correlation and co-occurrence may actually be something that a programmer debugging the issue might want to know. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465992] Multiple symptoms of possibly one underlying issue after upgrading to 5.27
https://bugs.kde.org/show_bug.cgi?id=465992 Szczepan Hołyszewski changed: What|Removed |Added Summary|Multiple issues after |Multiple symptoms of |upgrading to 5.27 |possibly one underlying ||issue after upgrading to ||5.27 --- Comment #2 from Szczepan Hołyszewski --- (In reply to Nicolas Fella from comment #1) > Please read https://community.kde.org/Get_Involved/Issue_Reporting before > reporting further bugs. TL;DR: This Is Different. Long version: I know how to report regular bugs, and I have a record on this bugtracker to prove it. This is not a regular bug, therefore this bug report is not a regular bug report. This is a situation where a user logs in to a newly updated desktop and is met with an avalanche of glitches, none of which were present before the update. Nothing remotely like this has happened in my 15+ years with KDE. This is a never before seen situation that the document you quoted doesn't cover? > https://community.kde.org/Get_Involved/Issue_Reporting#Remember_your_manners I fail to find in that document an interdiction against stating facts. > https://community.kde.org/Get_Involved/ > Issue_Reporting#Multiple_issues_in_a_single_Bugzilla_ticket I am reporting multiple _symptoms_ that manifested all at once as a result of a single update. When something like that happens, it is quite possible that all the symptoms are different manifestation of a single bug, but I am not able to ascertain whether that's the case, so the next best thing I can do is report -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 463710] Volume control applet has no effect on Haruna volume
https://bugs.kde.org/show_bug.cgi?id=463710 --- Comment #7 from Szczepan Hołyszewski --- > Again no idea what you mean with bypassing the main volume control. > The only place where I can adjust the left/right balance is in the settings > and only for devices not applications (tried vlc and mpv). Yes, I do mean "adjust the left/right balance in the settings", and the settings can be opened from the RMB menu of the volume control applet in the system tray. The confusion was caused by lack of clear UI boundary: a user like me "does something" with the volume control applet and confusingly "ends up" in systemsettings. Yes, I do mean "only for devices not applications". Yes, I do mean that the following anomaly absolutely positively DOES manifest: I adjust main volume in the settings, and this has no effect on the volume of sound played by Haruna. I can literally mute everything else by dragging the volume slider all the way to the left, but Haruna is still happily playing sound, and the volume isn't reduced one bit. That's the main issue, that's the title of this bug report, and the whole balance thing is just a consequence of that: since the only control that allows adjusting the balance fails to control Haruna's volume, balance cannot be adjusted for Haruna. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465992] New: Multiple issues after upgrading to 5.27
https://bugs.kde.org/show_bug.cgi?id=465992 Bug ID: 465992 Summary: Multiple issues after upgrading to 5.27 Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rula...@wp.pl CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Looks like the buggiest Plasma release within living memory. STEPS TO REPRODUCE 1. Log in OBSERVED RESULT - KDE logo + spinning cog for 30s (everything on NVMe, and a definite regression, looks like something timing out) - Black desktop backgrounds - Wrong monitor selected as the default; can change in settings (and this restores desktop backgrounds too), but the change doesn't stick after logging out and back in - Icons Only Task Manager icons too small EXPECTED RESULT - Fast login - No change to desktop backgrounds - No change to which monitor is the default - No change to Icons Only Task Manager icon size SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B24 System Version: 2.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 --- Comment #47 from Szczepan Hołyszewski --- (In reply to Bharadwaj Raju from comment #35) > Better solution, using triangle mouse filtering > > https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/832 Could you please explain this idea? I don't understand what "triangle mouse filtering" _is_, but as a solution to a problem that could be solved with a simple debounce, it sure _sounds_ like Spaceballs teleportation. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 463710] Volume control applet has no effect on Haruna volume
https://bugs.kde.org/show_bug.cgi?id=463710 --- Comment #5 from Szczepan Hołyszewski --- (In reply to george fb from comment #4) > I have no idea what you mean. By "cannot be split" I mean that left and right channel cannot be adjusted separately, so even if Haruna appeared correctly on the programs tab in the volume control applet, it would still be impossible to adjust balance. However if Haruna didn't bypass the main volume control, then it would be possible, because the main volume contro DOES allow "splitting" and adjusting balance. -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 45191] Ability to exclude folders from search
https://bugs.kde.org/show_bug.cgi?id=45191 --- Comment #10 from Szczepan Hołyszewski --- I had an S3 remote mounted with rclone in ~/mnt/s3, and KFile just crawled the complete entirety of to find the one text file in which I emergency-saved an important bit of information half a year ago. And no, I did not save that file on S3. That's the kind of harm that happens when you can't exclude folders from search. -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 45191] Ability to exclude folders from search
https://bugs.kde.org/show_bug.cgi?id=45191 --- Comment #9 from Szczepan Hołyszewski --- (In reply to Dennis Schridde from comment #5) > Is this still relevant? Yes it is. -- You are receiving this mail because: You are watching all bug changes.
[kfind] [Bug 45191] Ability to exclude folders from search
https://bugs.kde.org/show_bug.cgi?id=45191 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #8 from Szczepan Hołyszewski --- Wow! A 20+ years old feature request, completely reasonable, absolutely needed, and completely ignored by devs. KDE at its finest! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447717] plasmashell crashes when hovering or clicking items on the Panel due to "zwp_linux_buffer_params_v1.add" protocol error
https://bugs.kde.org/show_bug.cgi?id=447717 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #65 from Szczepan Hołyszewski --- (In reply to Nate Graham from comment #55) > Well darn. :( > > At least the fix is in Qt 6.3, so I guess the worst-case scenatio is that > this is a Plasma 6 fix. Which, for an end user, means WHEN? Looks like again we will be falling victim to the bad policy, "if there is a fix upstream, do nothing, even if the fix is MONTHS up stream". -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 463710] Volume control applet has no effect on Haruna volume
https://bugs.kde.org/show_bug.cgi?id=463710 --- Comment #3 from Szczepan Hołyszewski --- Still, it somehow bypasses main volume control, and per-program controls cannot be split. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 463710] Volume control applet has no effect on Haruna volume
https://bugs.kde.org/show_bug.cgi?id=463710 --- Comment #1 from Szczepan Hołyszewski --- ERRATA: whenever I mention "KMix", I really mean the volume control applet. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 463710] New: Volume control applet has no effect on Haruna volume
https://bugs.kde.org/show_bug.cgi?id=463710 Bug ID: 463710 Summary: Volume control applet has no effect on Haruna volume Classification: Applications Product: Haruna Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: rula...@wp.pl Target Milestone: --- SUMMARY Changing volume in KMix has no effect on Haruna playback volume, and Haruna doesn't show in KMix as a program that plays sound while it is playing sound. More importantly, Haruna lacks the ability to adjust the volume of each channel separately, which - combined with its apparent "independence" from what _should_ be the system-wide volume control - renders that important adjustment effectively unavailable in Haruna. >From the POV of an end user who shouldn't be required to understand the gory internals of pipewire, pulseaudio, ALSA, and sound card drivers, KMix should be the one, only and always-working go-to place for changing the volume of anything whatsoever. No software should circumvent this. STEPS TO REPRODUCE 1. Play something with audio in Haruna 2. Try adjusting the volume of what Haruna plays using KMix OBSERVED RESULT Changing the volume in KMix has no effect on the volume of audio playback in Haruna. Haruna does not show on the Programs tab in KMix. EXPECTED RESULT Haruna audio volume should be controllable with KMix. Haruna should show on the Programs tab in KMix while playing sound. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.1-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B24 System Version: 2.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449020] No way to elevate read permissions when opening a file, no error, blank document shown
https://bugs.kde.org/show_bug.cgi?id=449020 --- Comment #1 from Szczepan Hołyszewski --- Bitten by this again. This issue is an Intercontinental Ballistic Footgun. There MUST be SOME indication of a problem when I try to OPEN a file to which I don't have read access and get a blank buffer. Current behavior is DANGEROUS. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 458716] Toolbar missing: Undo, Redo, Crop, Resize, Rotate etc.
https://bugs.kde.org/show_bug.cgi?id=458716 Szczepan Hołyszewski changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #3 from Szczepan Hołyszewski --- (In reply to Patrick Silva from comment #1) > is the required kimageannotator 0.6.0 installed on your system? Surprisingly it was not. I thought it would come with KDE Gear 2022.08. In the meantime I switched back to Arch and got 0.6.0 and the toolbar. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 458716] New: Toolbar missing: Undo, Redo, Crop, Resize, Rotate etc.
https://bugs.kde.org/show_bug.cgi?id=458716 Bug ID: 458716 Summary: Toolbar missing: Undo, Redo, Crop, Resize, Rotate etc. Product: Spectacle Version: 22.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: rula...@wp.pl CC: k...@david-redondo.de Target Milestone: --- SUMMARY The toolbar that should contain the Undo, Redo, Crop etc. buttons is not there. STEPS TO REPRODUCE 1. Launch Spectacle 2. Open the Annotate dialog OBSERVED RESULT The toolbar with the Undo, Redo, Crop, Resize etc. icons is nowhere to be found. There is no way to configure toolbar visibility in Spectacle in order to restore it. EXPECTED RESULT The toolbar should be present. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.3-051903-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B24 System Version: 2.0 ADDITIONAL INFORMATION Deleting spectaclerc doesn't help. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 458713] New: Spectacle cannot take a screenshot of its own Annotate dialog
https://bugs.kde.org/show_bug.cgi?id=458713 Bug ID: 458713 Summary: Spectacle cannot take a screenshot of its own Annotate dialog Product: Spectacle Version: 22.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: rula...@wp.pl CC: k...@david-redondo.de Target Milestone: --- SUMMARY Specctacle cannot take a screenshot of its own Annotate dialog, which is preventing me from creating a screenshot to demonstrate an unrelated UI issue with the Annotate dialog. STEPS TO REPRODUCE 1. Open Spectacle 2. Set up a delayed whole desktop screenshot with 15s delay 3. Press the button to take the screenshot and start the timer. Spectacle will minimize itself. 4. While the timer is running, unminimize Spectacle and open the Annotate dialog. 5. Wait for the screenshot to be taken. 6. Close the annotate dialog to return to Spectacle's main UI OBSERVED RESULT The image in the main UI does not update. EXPECTED RESULT The image in the main UI should be the updated with the new screenshot showing Spectacle's Annotate window that was active at the moment when the timer triggered. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.3-051903-generic (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8400 CPU @ 2.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B24 System Version: 2.0 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 445158] Yakuake does not open on the screen where the mouse pointer is
https://bugs.kde.org/show_bug.cgi?id=445158 --- Comment #13 from Szczepan Hołyszewski --- Sorry, I got confused because Thomas Brix Larsen above said that _downgrading_ to 2022.04.3 fixed this for him. But it seems that he was in fact reporting a regression on X caused by this fix? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 445158] Yakuake does not open on the screen where the mouse pointer is
https://bugs.kde.org/show_bug.cgi?id=445158 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #11 from Szczepan Hołyszewski --- Experiencing this with Yakuake 2022.04.3 as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #22 from Szczepan Hołyszewski --- Changing the status from "reported" to "confirmed" or something similar would be one way to proceed. Could you reproduce this? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 300784] Need more resilience against intermittent authentication failures
https://bugs.kde.org/show_bug.cgi?id=300784 --- Comment #2 from Szczepan Hołyszewski --- If the bug is still present, it WILL manifest in this scenario with 100% certainty, but setting up this scenario (i.e. setting up a dummy POP3 server that can be instructed to fail authentication attempts on demand, configuring the accounts etc.) is not something you should expect a bug reporter (and end user) to do. That's test team's job. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405551] plasmashell high CPU, panel unresponsive and not redrawing every few minutes for few seconds
https://bugs.kde.org/show_bug.cgi?id=405551 Szczepan Hołyszewski changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Szczepan Hołyszewski --- No longer happening. Closing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #20 from Szczepan Hołyszewski --- I removed en_US from the configuration: ``` $ echo $LANGUAGE pl $ echo $LANG pl_PL.UTF-8 $ cat ~/.config/plasma-localerc [Formats] LANG=pl_PL.UTF-8 LC_COLLATE=pl_PL.UTF-8 useDetailed=true [Translations] LANGUAGE=pl ``` No effect. Symptoms persist. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #19 from Szczepan Hołyszewski --- ERRATA (rewriting the above comment, because it is impossible to edit or delete comments) If putting "en_US" last is an invalid setting, then what is the VALID setting that expresses the intention "use Polish if available and fall back to English"? Because that is a perfectly valid intention, and if it is not possible to express it validly with configuration, then we have another issue. Also, exactly WHY does this cause mixed translations, and shouldn't this behavior be fixed instead of being warned against? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #18 from Szczepan Hołyszewski --- If putting "en_US" last is an invalid setting, then what is the VALID setting that expresses the intention "use Polish if available and fall back to en_US"? Because that is a perfectly valid intention, and if it is not possible to express it validly with configuration, then we have another issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #16 from Szczepan Hołyszewski --- (In reply to Nate Graham from comment #15) > What is the output of the following commands in a new fresh terminal window? > > echo $LANGUAGE > echo $LANG > cat ~/.config/plasma-localerc ``` $ echo $LANGUAGE pl:en_US $ echo $LANG pl_PL.UTF-8 $ cat ~/.config/plasma-localerc [Formats] LANG=pl_PL.UTF-8 LC_COLLATE=pl_PL.UTF-8 useDetailed=true [Translations] LANGUAGE=pl:en_US ``` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #14 from Szczepan Hołyszewski --- ... and with dolphin, LANGUAGE has exactly ZERO effect, as opposed to about 40% in the case of plasma-systemmonitor. I'm not even making a screenshot, because it shows no evidence that running it in English was even attempted. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #13 from Szczepan Hołyszewski --- Created attachment 150585 --> https://bugs.kde.org/attachment.cgi?id=150585=edit Thorough mix of English and Polish. `LANGUAGE=en plasma-systemmonitor` results in this. It fails to launch the program *completely* in English. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #12 from Szczepan Hołyszewski --- (In reply to Ahmad Samir from comment #11) > Looking around it looks like setting LANGUAGE env var would work[1] e.g. > from terminal: > LANGUAGE=en dolphin > > [1]https://invent.kde.org/frameworks/kxmlgui/-/blob/master/src/ > kswitchlanguagedialog_p.cpp#L69 Nope. Screenshot will follow. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 --- Comment #36 from Szczepan Hołyszewski --- (In reply to Bharadwaj Raju from comment #35) > Better solution, using triangle mouse filtering > > https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/832 Could you explain the idea? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 432372] FormLayout text gets elided too early when using a fractional font size
https://bugs.kde.org/show_bug.cgi?id=432372 Szczepan Hołyszewski changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UPSTREAM|--- --- Comment #14 from Szczepan Hołyszewski --- I believe that once it has been established that "upstream" has a bug that won't be fixed in foreseeable future, but "application" and its users continually suffer from the bug, then "application" should try to come up with a workaround instead of telling users that they will have to wait indefinitely for the bug to be fixed upstream. KDE is the "application" here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449894] wayland Plasma session - no window previews on pager
https://bugs.kde.org/show_bug.cgi?id=449894 --- Comment #1 from Szczepan Hołyszewski --- Confirming on: Operating System: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449894] wayland Plasma session - no window previews on pager
https://bugs.kde.org/show_bug.cgi?id=449894 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 449020] New: No way to elevate read permissions when opening a file, no error, blank document shown
https://bugs.kde.org/show_bug.cgi?id=449020 Bug ID: 449020 Summary: No way to elevate read permissions when opening a file, no error, blank document shown Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: rula...@wp.pl Target Milestone: --- SUMMARY KWrite refuses to run with sudo, and claims in the output that it is "not necessary", because the user will be prompted for elevated permissions when they want to save the file. But what if permissions prevent KWrite from opening the file in the first place? There is no prompt for elevated permissions in this case, nor is there an error message, and KWrite shows an untruth: a blank document. STEPS TO REPRODUCE 1. Try to open a file to which you HAVE the r permission, but DON'T have the x permission for its containing directory (e.g. another user's .ssh/id_rsa.pub) OBSERVED RESULT No prompt for elevated permissions, no error message, blank document. An attempt to save the document _does_ prompt for privilege elevation, resulting in a risk of overwriting the file without even having seen its contents first. EXPECTED RESULT The mechanism for permission elevation should be implemented for opening files too. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #94 from Szczepan Hołyszewski --- No, actually the problem is that the issue is 9 years old, the decision to implement the dimming was undisputedly and objectively wrong, and people responsible for it not being correctly fixed on DAY ONE have actively, maliciously harmed KDE and should be fired. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #90 from Szczepan Hołyszewski --- Plot twist: Plasma 5.23 is apparently a "prestige" anniversary release and they are going to chisel and polish it for further MONTHS before this fix is available to end users. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 432372] FormLayout text gets elided too early when using a fractional font size
https://bugs.kde.org/show_bug.cgi?id=432372 --- Comment #10 from Szczepan Hołyszewski --- Th.. Qt tea... shou... definit... alloc... mo... resou... to fixi... thi... bu... . -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 441571] New: IDE cannot resolve symbols that the toolchain itself has no problem resolving
https://bugs.kde.org/show_bug.cgi?id=441571 Bug ID: 441571 Summary: IDE cannot resolve symbols that the toolchain itself has no problem resolving Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Build tools: QMake Assignee: kdevelop-bugs-n...@kde.org Reporter: rula...@wp.pl Target Milestone: --- Created attachment 141065 --> https://bugs.kde.org/attachment.cgi?id=141065=edit Thoroughly confused IDE SUMMARY Can you guys sit down an intern for a week and tell her to actually test every last one of the project templates you ship with KDevelop? It's ridiculous that a project created using one of the templates builds and runs successfully, but the IDE shows a ton of undersquiggles in source files, being unable to resolve symbols and include files that the toolchain itself had no problem resolving, as evidenced by the binary being successfully produced. STEPS TO REPRODUCE 1. Project -> New from template... -> Qt -> Grahical (QMake-based) -> QtQuick 2 program 2. Build the project and run the executable to verify that it builds successfully 3. Open src/main.cpp in the IDE OBSERVED RESULT See attachment. EXPECTED RESULT The IDE should be able to figure out every symbol and include file that the toolchain itself was able to figure out. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.12-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410928] Don't Present Windows if each window in the group is on a different monitor
https://bugs.kde.org/show_bug.cgi?id=410928 --- Comment #3 from Szczepan Hołyszewski --- Curiously though, current behavior is different from the one against which the bug was reported. I no longer see the Present Windows effect when clicking on a group button. Instead clicking repeatedly on the group button activates the windows in a cycle. This is close enough to what I wanted that I'm inclined to consider this bug fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410928] Don't Present Windows if each window in the group is on a different monitor
https://bugs.kde.org/show_bug.cgi?id=410928 --- Comment #2 from Szczepan Hołyszewski --- The user's intention is not to "trigger the effect". Their intention is to "get to the desired window" as directly as possible. They may have *intentionally* arranged the windows on different monitors in order to be *able* to get to either of them as directly as possible. What is confusing (and annoying) is when the software introduces another interaction step to ask a completely redundant follow-up question, and *frustrates* user's intention to "get to" either window as quickly and directly as possible. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 Szczepan Hołyszewski changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #10 from Szczepan Hołyszewski --- > Couldn't you just change the in-app language using the existing > functionality (again, for apps that implement it) and then change it back > afterwards? No and no. No to treating the fact that some apps don't implement it as a minor point, and no to having to make and subsequently un-make a persistent configuration change. It is doable, but it is an insult to the principle which asserts that software should serve the user, not vice versa. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358930] moving the mouse over a different application icon immediately changes the window list
https://bugs.kde.org/show_bug.cgi?id=358930 --- Comment #29 from Szczepan Hołyszewski --- These hundred-times-a-day ergonomy-wrecking annoyances should be treated with WAY UP THE TOP priority. Like 99% issues are less important than a constantly, relentlessly annoying, focus-destroying glitch in the first-contact UI through which users interact with Basically Everything. If the team is overloaded fixing less important issues, then the solution is simple: STOP working on less important issues, FIX THIS ONE, and THEN resume working on less important issues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #82 from Szczepan Hołyszewski --- > Therefore you just need to stop posting comments. There is nothing to be > gained by more comments, really. Just stop posting comments. The change is > in progress, just be patient and stop posting comments. Did I mention to > stop posting more comments? Really. Be patient for another few weeks. It's > not that hard. C'mon guys. You can do it. I have faith in you. To mock is the job of a clown. -- You are receiving this mail because: You are watching all bug changes.
[kcachegrind] [Bug 420748] Excruciatingly slow loading of certain profiles
https://bugs.kde.org/show_bug.cgi?id=420748 --- Comment #5 from Szczepan Hołyszewski --- I'll look into this again, but I seem to remember the XDebug guy explaining those weren't costs per se, but memory usage changes, which can be negative if a call ends up freeing more memory than it allocates. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #81 from Szczepan Hołyszewski --- > There is absolutely nothing constructive or helpful in this bug report. This is a lie. > Closing. Retaliatory closing is a whole new low. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #72 from Szczepan Hołyszewski --- (In reply to Nate Graham from comment #69) > Heh, as it turns out, a QML-based replacement is actually in active > development over here: > https://invent.kde.org/plasma/kwin/-/merge_requests/1177. How long between "initial bits of QML-based present windows effect" and "final bits that will allow it to be merged"? My prediction: INFINITY. This project will be abandoned before the next fashionable technology of the day arrives to supplant QML, at which point it will be restarted with the new technology, and this will continue long after we all return to the ecosystem. COMMENT OUT THE OFFENDING LINE OF C++ CODE THAT DIMS THE WINDOWS. OR SET THE END VALUE OF THE OPACITY ANIMATION OF THE DIMMING OVERLAY TO 0 JUST LIKE THE START VALUE. OR WHATEVER, DEPENDING ON HOW IT IS CURRENTLY IMPLEMENTED AND WHICH NECESSARY CHANGE WILL BE TRULY MINIMAL. JUST STOP DIMMING THOSE WINDOWS. STOP. DO STRICTLY LESS THAT YOU CURRENTLY DO. DON'T START NEW A NEW PROJECT FOR THIS. DON'T DO ANYTHING NEW. JUST STOP DOING SOMETHING OLD AND TIRED AND UNIVERSALLY VISCERALLY HATED. JUST STOP. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #57 from Szczepan Hołyszewski --- > I understand that you're upset, but insulting the people with the power do do > what you're asking may not be the most effective technique. :) Do you really have that power though, or do you only have veto power, i.e. the power to prevent what we're asking to from being done? Because if the latter is the case, then maybe that power should be taken away from you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #56 from Szczepan Hołyszewski --- > Yes, that's the easy part, but then there's not enough of a visual highlight > for the hover or selected window Enlarging the window like it's currently done is super enough. I mean it's animation. It MOVES. Its BREATHES IN in frantic anticipation of being selected. > If we don't implement that, then the work is only half-finished > and we will get bug reports about *that*. :) Then you'll revert the commit and I will apologize profusely, but I'm 99.9% sure it won't happen. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 Szczepan Hołyszewski changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Szczepan Hołyszewski --- > So can I ask you why exactly you want to be able to override the system > language for specific KDE apps? I don't want to be able to override the system language for specific KDE apps. I want to be able to override the system language for a **single run** of **any** KDE app. The reason I want it is simple: for writing bug reports in English, and to be able to see the EXACT form of English UI strings to google for when looking for solutions/workarounds. Like this brilliant idea of the "Copy in English" button at the bottom of kinfocenter's summary page, but universal: "run this program in English". -- You are receiving this mail because: You are watching all bug changes.
[kcachegrind] [Bug 420748] Excruciatingly slow loading of certain profiles
https://bugs.kde.org/show_bug.cgi?id=420748 Szczepan Hołyszewski changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Szczepan Hołyszewski --- Profiles seem to be loading quickly now, so it seems to be fixed one way or another. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417823] Unknown fate of multiple files shared from device to desktop
https://bugs.kde.org/show_bug.cgi?id=417823 --- Comment #6 from Szczepan Hołyszewski --- At this point I am receiving NO notification at all when I share from phone to desktop. The phone says it shared (there's a notification), but the file falls into a bottomless pit and gets eaten by a grue. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 429418] Cannot paste text copied from GTK apps into Kate
https://bugs.kde.org/show_bug.cgi?id=429418 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #8 from Szczepan Hołyszewski --- Is there a Qt issue on their tracker that I can follow? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 234528] Yakuake appearence is slow and nonfluent
https://bugs.kde.org/show_bug.cgi?id=234528 Szczepan Hołyszewski changed: What|Removed |Added Resolution|WORKSFORME |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #31 from Szczepan Hołyszewski --- > There is every intention to change this, but it's simply not so simple. We literally want the code to STOP doing something that it currently ACTIVELY DOES. It is an extraordinary claim requiring extraordinary evidence to say that STOPPING doing something is any more complicated than, well, stopping. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 349678] Kickoff closes on delayed "Detect window properties"
https://bugs.kde.org/show_bug.cgi?id=349678 --- Comment #6 from Szczepan Hołyszewski --- 99% of the time bugs don't just fix themselves spontaneously and automagically. If a bug was there and no effort was made to fix it, it is probably still there unless the codebase was rewritten from scratch. It makes very, very, VERY little sense to have this bot configured to ask the original reporter after a few years to check if the bug magically fixed itself. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #3 from Szczepan Hołyszewski --- 3) Adding the missing configurability to plasma-systemmonitor will not solve the general issue. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 --- Comment #2 from Szczepan Hołyszewski --- 1) There is no "Configure" menu in plasma-systemmonitor. 2) Any workaround that involves making and subsequently un-making persistent configuration changes is not sufficiently simple. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ki18n] [Bug 438394] New: We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language
https://bugs.kde.org/show_bug.cgi?id=438394 Bug ID: 438394 Summary: We need a software utility that will SOLVE the problem of one-off running KDE programs in a different language Product: frameworks-ki18n Version: 5.82.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: caslav.i...@gmx.net Reporter: rula...@wp.pl CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY The layered accretion of different i18n mechanisms in the entirety of the KDE-over-Qt ecosystem has reached the level of complexity where the technical skill necessary for succeeding at a simple intention like "I want to run this program in a different language than configured in Systemsettings, one-off, without changing settings for the purpose and reverting them afterwards" is now beyond the ability of a regular human. We need software utilities for solving these problems. Specifically, I propose creating a `withlang` utility that could be used to launch a KDE program in a terminal, and will SUCCESSFULLY AND THOROUGHLY launch it in a specified localization, so that EVERY string displayed in that program's window (as opposed to ONLY SOME strings) will be displayed in the desired language: ``` withlang en plasma-systemmonitor ``` STEPS TO REPRODUCE 1. Using Systemsettings, set all localization-related settings to Polish. 2. Log out and back in for good measure. Dzień dobry-śmobry digidi bejbi! 3. In xterm, try to apply your best envvar-fu to SUCCESSFULLY launch plasma-systemmonitor in English, so that ALL UI strings within the program window's client area will be shown in English, as opposed to just SOME. You think it's easy? You've been living blissfully secure in your conviction that setting some environment variable(s) on the command line is all it takes? Well then, I DARE YOU TO TRY, and I welcome you to post your experience in comments. OBSERVED RESULT No matter what I try - LANG, KDE_LANG, KDELANG, LANGUAGE, LC_*, LC_ALL, en([_-]US)?(\.(utf|UTF)-?8)?, I can only get SOME of the strings in the program to show in English. Others are shown in Polish. EXPECTED RESULT A utility like `withlang` should exist and be part of the KDE distribution, so that I could just run `withlang en plasma-systemmonitor` and Get What I Want. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.9-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 960/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 385894] plasma-desktop-5.11.1/kcms/hardware/joystick/joydevice.cpp:188]: (error) Memory leak
https://bugs.kde.org/show_bug.cgi?id=385894 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #11 from Szczepan Hołyszewski --- > We were all waiting on you, since you got the go-ahead to make > the change. Open source is collaborative, with participation > encouraged. It turns out that factually, what he got was more of a "go ahead, or else (the bug won't be fixed for another few years)", rather than a sincere go-ahead. And here's the thing: if you are the author/maintainer, gitwork is essentially YOUR JOB, and there is NO JUSTIFICATION for demanding that the user who did 100% of debugging also do the gitwork. There is NO JUSTIFICATION for not applying an obvious known fix FOR YEARS just because you want to make the point about "encouraging participation". A community that does that is not a "super welcoming" community, it is a "we can't be bothered to spend 5 minutes to formally wrap up a 2-LOC, single file result of what could have been hours or days of somebody else's debugging work" community. "Collaborative"? "I spend hours debugging, you spend 5 minutes to push my result through the right channels" is fair collaboration. "I spend hours debugging, you spend 15 minutes tutoring me interactively about the knowables and the unknowables of this project's submission process a.k.a. teach the man to fish" would also be fair collaboration. But "I spend hours debugging and you ask me to spend further hours (possibly spread over days) pushing the result through a territory unknown to me" is not fair collaboration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #29 from Szczepan Hołyszewski --- There is no such thing as "great workaround". A workaround is at best passable, by definition. Please don't detract from the severity of this issue by suggesting workarounds. This issue **ABSOLUTELY MUST** be fixed "in core". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433094] No way to disable tearing prevention
https://bugs.kde.org/show_bug.cgi?id=433094 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #2 from Szczepan Hołyszewski --- It is completely irrelevant whether Wayland session is affected or not. I know you guys promote Wayland and would be inclined to answer "hey, if Wayland session isn't affected, switch to Wayland", but the reality for many nVidia users is that Wayland Does Not Work And Never Has. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 329223] Unselected windows are too dim in "Present Windows" effect
https://bugs.kde.org/show_bug.cgi?id=329223 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #16 from Szczepan Hołyszewski --- There should be NO DIMMING WHATSOEVER. The established meaning and use of dimming as a GUI idiom is to de-emphasize things that are outside of the scope of the task at hand. If the task is to examine multiple items in order to choose one, then ALL items are absolutely relevant, and NONE of them is even one promille less relevant than the others. DIMMING IN PRESENT WINDOWS IS HARMFUL AND MUST GO. This is not a matter of opinion. Those who believe it should stay are objectively wrong. Those who want it gone are objectively right. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #25 from Szczepan Hołyszewski --- At this point I think the devs are just trolling us. They read this comment thread and have a laugh. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406725] Allow folders to be excluded for thumbnail generation
https://bugs.kde.org/show_bug.cgi?id=406725 --- Comment #8 from Szczepan Hołyszewski --- Also what is REALLY desired here is the ability to completely and consistently DENY the thumbnailing subsystem ACCESS to certain files. This isn't what "Show thumbnails" checkbox does: it prevents thumbnails from being shown in the dolphin directory view, but when you hover on a file, Dolphin will still generate its thumbnail and show it in the properties pane. What is desired is the ability to **prevent the thumbnail file under the .cache directory from ever possibly being created**, and **this** should work per-directory. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406725] Allow folders to be excluded for thumbnail generation
https://bugs.kde.org/show_bug.cgi?id=406725 Szczepan Hołyszewski changed: What|Removed |Added CC||rula...@wp.pl --- Comment #7 from Szczepan Hołyszewski --- "Remember properties for each folder" remembers ALL properties for each folder: the view type (list / compact list / tree), icon size, etc. This is undesirable. I want to be able to use common properties for all folders, EXCEPT for thumbnailer settings which I DO want to be able to override per directory. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 303438] Don't dim the other windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=303438 --- Comment #9 from Szczepan Hołyszewski --- To whoever implemented this originally and still holds the implementation hostage: you were wrong to implement it in the first place, you shouldn't have done that, this misfeature is exactly 0% useful and exactly 100% harmful, it goes completely against the established UI semantic of dimming (you DON'T dim things that are SPECIFICALLY RELEVANT to user's current activity, you dim ALL THE OTHER THINGS), and it has no redeeming qualities. Those who want it to stay are objectively wrong. Those who want it gone are objectively right. This is not a matter of opinion. Do the right thing. REMOVE IT. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427958] Debounce hiding the window selector upon unhovering program group icon
https://bugs.kde.org/show_bug.cgi?id=427958 --- Comment #1 from Szczepan Hołyszewski --- In order to be certain to avoid "losing" the window selector, the user must Very Consciously move the pointer vertically upwards onto the window selector, and Only Then sideways to select the desired thumbnail. This turns an elementary action into a "minigame". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427958] New: Debounce hiding the window selector upon unhovering program group icon
https://bugs.kde.org/show_bug.cgi?id=427958 Bug ID: 427958 Summary: Debounce hiding the window selector upon unhovering program group icon Product: plasmashell Version: 5.20.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: rula...@wp.pl CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Hiding the window selection UI upon unhovering the program group icon on the Icons-Only Task Bar should be debounced to prevent the UI from being hidden as the user accidentally hovers an adjacent icon for a split second when moving the pointer towards one of the tumbnails in the window selection UI. STEPS TO REPRODUCE 1. Open two instances of a program, so that they get grouped under a single icon in the Icons-Only Task Bar 2. Hover over the group icon and wait for the window selection UI to appear 3. Try selecting one of the thumbnails. OBSERVED RESULT More often than not, as you move the pointer towards the thumbnail, you will accidentally hover an adjacent icon on the taskbar for a split second. This will cause the window selection UI to disappear. EXPECTED RESULT When the window selection UI for a taskbar group is shown, the "another taskbar icon was hovered" event should be debounced. Instead of immediately hiding the window selection UI when such an event occurs, a timer should be started that would hide the UI after e.g. 100ms, and would be cancelled if the window selection UI is hovered within that timeframe. Operating System: Arch Linux KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.1-zen2-1-zen OS Type: 64-bit Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 960/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 427954] "First, you must pick a product on which to enter a bug" is becoming a prohibitively difficult puzzle
https://bugs.kde.org/show_bug.cgi?id=427954 --- Comment #1 from Szczepan Hołyszewski --- Suggestion: write an utility that will allow the user to click anywhere on the screen, xkill-style, and if the window thus selected belongs to a KDE "product", the utility would disclose the correct "product" to the user. Another possibility: add the "product" information to the "About" page of the properties dialog of every "thing" that has a properties dialog accessible via a context menu. For example, right clicking on an icon of a program group in the Icon Task Bar shows a context menu with a "More actions >" submenu, which contains "Icon Task Bar settings..." item at the bottom, which shows the settings dialog, which contains an "About" page. That page should display a sentence to the effect of "When reporting bugs for this component, choose "" as the product in the first step of the procedure". -- You are receiving this mail because: You are watching all bug changes.
