[systemsettings] [Bug 470926] Adopt "explicit apply" paradigm with Apply/Cancel buttons
https://bugs.kde.org/show_bug.cgi?id=470926 --- Comment #3 from Guido Schmidt --- I wouldn't call it plenty. Only 5 out of 70 dialogs in my system settings don't have an Apply button. - Two of them ask if you really want to apply the changes: Global Design and Online accounts. - Game controller asks you before you start a new calibration. I think a confirmation dialog would be appropriate for autostart, too. Good to know that the button issue has been addressed, though. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470926] New: Autostart has no apply/cancel buttons / changes take effect immediately
https://bugs.kde.org/show_bug.cgi?id=470926 Bug ID: 470926 Summary: Autostart has no apply/cancel buttons / changes take effect immediately Classification: Applications Product: systemsettings Version: 5.27.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_autostart Assignee: plasma-b...@kde.org Reporter: gu...@sanguepreto.de CC: nicolas.fe...@gmx.de Target Milestone: --- SUMMARY I wanted to inspect an autostart entry in my list that didn't have a name. Not sure what that horizontal line at the end meant, I clicked it, only to discover I just had removed the entry. (BTW: Who thinks it's a good idea to hide the button until you hover it?) Well, I didn't press the apply button yet, so nothing to worry, right? Wrong. Entry gone. STEPS TO REPRODUCE 1. Click the minus button of an entry. OBSERVED RESULT 2. See the entry disappear. 3. Find out there are no apply/cancel buttons. EXPECTED RESULT Find apply and cancel button like in the other settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse Tumbleweed KDE Plasma Version: 5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466528] Regression: "Switch to next desktop" shortcut doesn't cycle through the desktops anynmore
https://bugs.kde.org/show_bug.cgi?id=466528 --- Comment #2 from Guido Schmidt --- Thanks, that was it! I actullay saw this setting. But the German translation is so misleading that I didn't even try it: "Automatisch zur Gegenseite navigieren" which more or less translates to "Automatically navigate to the opposite side". I have to admit that I have a hard time finding a good and concise German wording. So can this be changed into a translation bug? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466528] New: Regression: "Switch to next desktop" shortcut doesn't cycle through the desktops anynmore
https://bugs.kde.org/show_bug.cgi?id=466528 Bug ID: 466528 Summary: Regression: "Switch to next desktop" shortcut doesn't cycle through the desktops anynmore Classification: Applications Product: systemsettings Version: 5.27.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: plasma-b...@kde.org Reporter: gu...@sanguepreto.de CC: k...@david-redondo.de Target Milestone: --- SUMMARY Some time in fall 2022 (maybe when 5.26 landed) the shortcut that allowed me to cycle between virtual desktops does not bring me from the last to first one anymore. Imagine having three Desktops A, B and C. I used to be able to go from C to A. STEPS TO REPRODUCE 1. Configure a shortcut for "Switch to next desktop", for instance Meta+Tab. 2. Configure 3 desktops A B C. 3. Go to desktop C. 4. Hit Meta+Tab OBSERVED RESULT Nothing happens. EXPECTED RESULT Switch to desktop A. SOFTWARE/OS VERSIONS Linux: Opensuse Tumbleweed KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION "Switch to next desktop" may not be the literal name, I translated it from the German localization: "Zur nächsten Arbeitsfläche umschalten". -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 361974] Power saving settings for monitor have no effect
https://bugs.kde.org/show_bug.cgi?id=361974 Guido Schmidt changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Guido Schmidt --- Barely remember this one. No, it's working now. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable, and if you force-resize them, they forget their size after the computer or plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=332512 --- Comment #99 from Guido Schmidt --- No Michael, this bug is not about kickoff only, it's about the plasmoids in general that are attached to the startmenu. For instance the folder view: It is ridiculously small, therefore shows only a few files, and only the first part of their names. And it cannot be resized. Guido 04.09.2021 23:25:22 Michael Hamilton : > https://bugs.kde.org/show_bug.cgi?id=332512 > > Michael Hamilton changed: > > What |Removed |Added > > CC| |mich...@actrix.gen.nz > > --- Comment #98 from Michael Hamilton --- > This seems to be an intractable issue (arguably showing an appalling lack of > sensibility to real-world usability in the age of 4K monitors). There is an > alternative which works quite well and the author appears focused on usability: > cupnoodle's Kickoff/Grid: https://store.kde.org/p/1317546 - I would suggest > those seeking a resizable kickoff vote with their feet, which was somewhat > officially suggested here https://forum.kde.org/viewtopic.php?f=83=170175 > > -- > You are receiving this mail because: > You voted for the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346895] Keboard repeat settings not applied at startup time
https://bugs.kde.org/show_bug.cgi?id=346895 Guido Schmidt changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Guido Schmidt --- Now on opensuse tumbleweed: I updated to the latest packages and tried to change the settings again: The behavior is now different, but still erroneous: 1. The preview field does not reflect any changes, neither rate nor delay. 2. When hitting the aoply button the settings do not get applied. 3. Only after a relogin do the new settings become active. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 258418] kcm session settings: excluded applications not recognized
https://bugs.kde.org/show_bug.cgi?id=258418 Guido Schmidt changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED --- Comment #6 from Guido Schmidt --- Using Plasma 5.19.5 (OpenSUSE Tumbleweed) it is still broken. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 378834] kdeconnect fails to send large files, desktop freezes
https://bugs.kde.org/show_bug.cgi?id=378834 --- Comment #1 from Guido Schmidt <gu...@sanguepreto.de> --- May be related to Bug #362685, but I did not have to click on anything to freeze the desktop. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 378834] New: kdeconnect fails to send large files, desktop freezes
https://bugs.kde.org/show_bug.cgi?id=378834 Bug ID: 378834 Summary: kdeconnect fails to send large files, desktop freezes Product: kdeconnect Version: 1.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: gu...@sanguepreto.de Target Milestone: --- Version is 1.0.3, but that is not available on the list. System has 4GB RAM, 4GB Swap I tried to send a 7.6GB sized file. After a couple of seconds the desktop became completely unresponsive to mouse-movements or keyboard-input, RAM-usage went up to 100%, significant SWAP-usage. First try: File got copied until about 400MB arrived on the phone, then terminated unexpectedly. CPU, RAM and SWAP went back to normal. Progress indicator on phone kept running. I thought: Maybe this means kdeconnect is able to resume the transfer. So I gave it a try. Second try: Same symptoms on the desktop as before. No resume of previous transfer of course, instead a second progress indicator showed up on the phone, filename got (1) added. This time transfer worked until file size reached almost 700MB. But this time excessive RAM-, CPU-, SWAP-usage and unresponsive desktop stay for several (maybe 10?) minutes. To get rid of the progress-indicators on the phone I had to kill kdeconnect. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 376638] KDE Connect 1.6 loosing file extension
https://bugs.kde.org/show_bug.cgi?id=376638 Guido Schmidt <gu...@sanguepreto.de> changed: What|Removed |Added CC||gu...@sanguepreto.de --- Comment #1 from Guido Schmidt <gu...@sanguepreto.de> --- Exactly the same thing happend to here an my tablet. Version on tablet is 1.6, on Desktop 1.0.1-1.4. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 361974] New: Power saving settings for monitor have no effect
https://bugs.kde.org/show_bug.cgi?id=361974 Bug ID: 361974 Summary: Power saving settings for monitor have no effect Product: systemsettings Version: 5.6.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gu...@sanguepreto.de This is a desktop PC with OpenSUSE 13.2 (x86_64). Since KDE 5.6 my monitor turns off (I guess an energy saving mode) after a couple of minutes even though I have this setting disabled in systemsettings5 like I always had. (I would give you the exact name of this setting but even though I set System Settings to run in english it shows most words in my german - maybe another bug. The german name is: Energiesparmodus - Bildschirm abdunkeln) This does not happen when I am logged into an XFCE session. BTW this is the only session on this machine. I tried changing the setting by enabling it and setting the time-out to 1 minute. This also does not have any effect. So it looks like KDE is not reading/finding the setting and using a default? Reproducible: Always Steps to Reproduce: 1. Login to a KDE 5 session. 2. Make sure the energy/power setting for turning off the moniter after a configurable time is turned off. 3. Wait a little, i.e. watch a movie in full screen mode. Actual Results: Screen turns black and monitor LED indicates a power saving mode. Expected Results: Screens stays on. -- You are receiving this mail because: You are watching all bug changes.
