[kwin] [Bug 474730] Window placement "Centered" doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=474730 --- Comment #2 from Matthias Heinz --- (In reply to Nate Graham from comment #1) > This is indeed intentional. If you open two of the same size windows when > using Centered mode, they'll overlap 100% and that's not exactly helpful and > it's very confusing for non-experts. We're not planning to offer an opt-out > for this. I know. And you added it, because your wife got used to it from using MacOS and that's why you are personally attached to this feature. (This is meant as a non-emotional statement of the current situation and not as an insult. Don't get me wrong here.) Still the name is missleading. I would expect the name to open all windows centered. And minimized windows aren't taken into account at all (this could be intentional, but defeats the logic of cascading windows with the same size). And it fights with some applications that set their own window position, but could be a bug on their side not kwin. (Like konsole apparently). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 343475] webdavs: allow for multiple credentials
https://bugs.kde.org/show_bug.cgi?id=343475 Matthias Heinz changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #6 from Matthias Heinz --- Hi. Sorry for the late reply, but this bug is still present in 5.27.7. In the syntax webdavs://username@ the username just gets ignored. Best regards Matthias -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474730] New: Window placement "Centered" doesn't work correctly
https://bugs.kde.org/show_bug.cgi?id=474730 Bug ID: 474730 Summary: Window placement "Centered" doesn't work correctly Classification: Plasma Product: kwin Version: 5.27.7 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m...@familie-heinz.name Target Milestone: --- SUMMARY When having window placement set to "Centered" new windows should be always centered. This doesn't work correctly. Newly starting e.g. konsole puts it centered on the screen, but when opening another window of konsole the new window is not centered, but cascade slightly right-down below. This is either an undocumented feature (that should be configurable) or a bug. This was tested with a new user on a clean session with window placement set to "Centered" (which was the default) and allowing applications to handle the window placement on their own switched off. STEPS TO REPRODUCE 1. Set window placement to "Centered" 2. Start konsole 3. Use e.g. the shortcut in konsole to open more windows. OBSERVED RESULT The first konsole window will get centered, the second maybe, but then they get cascaded. EXPECTED RESULT All windows get centered, when window placement is set to "Centered". (And if the application itself is not allowed to control their own positioning on the screen). --- Yes, I have seen https://bugs.kde.org/show_bug.cgi?id=58063 and other reports that this might be intentional. But it is not documented. And I find it very VERY annoying to have something named "Centered", which doesn't actually center. So either call it "smart center" or document it somewhere, where it is obvious what will happen. And add an option where new windows are always centered. (Yes I like my windows centered. All of them.) Many thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472441] Manually sorted windows are resetted when opening the launcher, but just once
https://bugs.kde.org/show_bug.cgi?id=472441 --- Comment #1 from Matthias Heinz --- > 4. Open the launcher (I do this with the Meta key) This only happens when opening the launcher with the hotkey. Clicking on it will not reset the order in the task manager bar. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472441] New: Manually sorted windows are resetted when opening the launcher, but just once
https://bugs.kde.org/show_bug.cgi?id=472441 Bug ID: 472441 Summary: Manually sorted windows are resetted when opening the launcher, but just once Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: m...@familie-heinz.name Target Milestone: 1.0 SUMMARY When starting plasma there are a few programs that are started automatically, like Firefox with several windows. Then I drag those windows around in the task manager bar. If I then open the launcher the window order in the task manager will get resetted to what it was like before. I can then rearrange them again. Opening the launcher now will not change the order anymore. The sorting of the windows is set to manual. STEPS TO REPRODUCE 1. Start plasma 2. Have some windows opened by some programs 3. Move the windows around in the task bar 4. Open the launcher (I do this with the Meta key) OBSERVED RESULT The windows should be resetted to their initial order. EXPECTED RESULT The window order doesn't change. 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-kidletime] [Bug 328987] Power saving should not trigger if joystick/controller/gamepad is in use
https://bugs.kde.org/show_bug.cgi?id=328987 Matthias Heinz changed: What|Removed |Added CC||m.he...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423189] Cannot make default script active
https://bugs.kde.org/show_bug.cgi?id=423189 --- Comment #5 from Matthias Heinz --- After digging around in the code a bit I think I found the problem. In ksieveui/managescriptsjob/generateglobalscriptjob.cpp is the function GenerateGlobalScriptJob::writeUserScript(), which is called by the start() function. In the writeUserScript() function a put() is called to kmanagesieve/sievejob.cpp SieveJob *SieveJob::put. And if you look closely it has two booleans as input. One to set a script active, one to deactivate it. And in writeUserScript() both bools are "false", which is wrong. The first one should "true". -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423189] Cannot make default script active
https://bugs.kde.org/show_bug.cgi?id=423189 Matthias Heinz changed: What|Removed |Added CC||m.he...@gmx.net --- Comment #4 from Matthias Heinz --- Hi, I just stumbled about that problem as well. Since sieve is a relatively simple protocol I first thought this would be dovecots fault. But no, the problem seems to be kmails sieve editor here. I could just activate the script with SETACTIVE "USER" over an openssl s_client connection and now it works. Easiest fix would probably be to run SETACTIVE "USER" on every connection or so... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427840] Minimizing a window doesn't move it to the bottom of the Task Switcher (alt+tab) list anymore
https://bugs.kde.org/show_bug.cgi?id=427840 Matthias Heinz changed: What|Removed |Added CC||m.he...@gmx.net --- Comment #16 from Matthias Heinz --- Hi, I recently updated to Plasma 5.20.5 and at first I thought I was going insane and then I gladly found this bug report. Why has it changed? There was no necessity to do this and it doesn't make any sense at all. If a user minimizes a window there is a reason for it: To get it away and have it running in the background and not care about it for some time. As a very very long term developer who does ui stuff: You don't change behavior like this. Never. You make a new option if you think the other behavior is better, but never make it a default until you have verified it is really better (which is it not). I hope you consider this answer as not too rude, but this is annoying me for some days now. And I have the feeling that when Plasma 5.20 starts trickeling down into all the distributions that don't ship every release this bugreport might blow up a bit. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 412900] Mouse wheel scrolling over a slider doesn't change the volume anymore.
https://bugs.kde.org/show_bug.cgi?id=412900 Matthias Heinz changed: What|Removed |Added CC||m.he...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 412900] New: Mouse wheel scrolling over a slider doesn't change the volume anymore.
https://bugs.kde.org/show_bug.cgi?id=412900 Bug ID: 412900 Summary: Mouse wheel scrolling over a slider doesn't change the volume anymore. Product: kmix Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: es...@kde.org Reporter: m.he...@gmx.net Target Milestone: --- SUMMARY I've updated kmix to version 4.6 and since then scrolling with the mouse wheel over a slider doesn't work anymore. I'm aware of https://bugs.kde.org/show_bug.cgi?id=409325 and see it as advantage, not as a bug and I fear someone removed the functionality completely, while trying to fix this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 196303] KDE needs it's own Print Dialogue
https://bugs.kde.org/show_bug.cgi?id=196303 Matthias Heinz <m.he...@gmx.net> changed: What|Removed |Added CC||m.he...@gmx.net --- Comment #16 from Matthias Heinz <m.he...@gmx.net> --- Hello alltogether, the printing dialog right now does its job. It's ok. But afair the old dialog had more features. But it's not that I'm missing much. Back in 2009 I did some manual duplex printing, which was annoying, but can be pretty easy with a good gui. Now almost every printer has a duplex unit built in, so it doesn't matter anymore. Also I don't print much anymore, too. Paper got somewhat obsolete for me. -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 343475] webdavs: allow for multiple credentials
https://bugs.kde.org/show_bug.cgi?id=343475 Matthias Heinz <m.he...@gmx.net> changed: What|Removed |Added CC||m.he...@gmx.net --- Comment #2 from Matthias Heinz <m.he...@gmx.net> --- Hi, I've got the same behaviour here. I have multiple webdav accounts on a cloud service, but I only have access to one. I have tried the webdavs://username@ syntax but the username gets ignored. When I try with a username I have never used before, I get the password dialog. Then I can enter the password and store it. From now on I have only access to that webdav resource, even when I change the username in the URL I always land on this resource and there's no way to get access to any other. I've tested this with dolphin now and also with the file open dialog in okular. I can access one resource in dolphin and a different one in okular. But there's no way to change the username if entered once in a context. I have tried to logout and login. And then I can access the webdav resource with a different username, but that name is then again locked for the whole session. This seems to be a caching problem per context and session so far to me. Either the cache is not cleared, when the same resource is accessed with a different username or there gets no new session started, when the URL is the same, but the username changes. Best Matthias -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 355441] DAV Resource 16.12.0: Broken state, The item was not deleted on the server.
https://bugs.kde.org/show_bug.cgi?id=355441 Matthias Heinz <m.he...@gmx.net> changed: What|Removed |Added CC||m.he...@gmx.net --- Comment #17 from Matthias Heinz <m.he...@gmx.net> --- Hey, I've got the same bug with kdepim 16.04 and it would be great if this could be solved somehow. For now I guess I'll try the rewrite rules. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 179504] Global shortcuts doesn't work with Ctrl+Alt+Shift+...
https://bugs.kde.org/show_bug.cgi?id=179504 --- Comment #35 from Matthias Heinz <m.he...@gmx.net> --- Dear Sasha, I tried with "Ctrl+Alt+Shift+1" and "Ctrl+Alt+Shift+2" for switchting desktops and it worked. Also I use Meta+Tab and Meta+Shift+Tab for switchting through my desktops. In earlier versions the "Shift" got always ignored, now it is interpreted and the shortcuts work as expected. You will have to wait for KDE framework 5.28 then. Best Matthias -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 179504] Global shortcuts doesn't work with Ctrl+Alt+Shift+...
https://bugs.kde.org/show_bug.cgi?id=179504 --- Comment #33 from Matthias Heinz <m.he...@gmx.net> --- (In reply to Sasha Unspecified from comment #32) > Matthias Heinz, in KDE 5.18 it still doesn't. > What shortcut did you try in 5.28. Hi, yes, I assigend it through the systemsettings. Please check the version of your KDE framework (it's called plasma-framework in Debian and recently got updated to 5.28.0 there). Best Matthias -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 179504] Global shortcuts doesn't work with Ctrl+Alt+Shift+...
https://bugs.kde.org/show_bug.cgi?id=179504 Matthias Heinz <m.he...@gmx.net> changed: What|Removed |Added CC||m.he...@gmx.net --- Comment #31 from Matthias Heinz <m.he...@gmx.net> --- Hi, this works with plasma-framework 5.28.0 for me. Since this is a very old bug, I suggest closing it, if nobody has any objections. Matthias -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 355899] Control+Shift+Meta+Tab shortcut does not work
https://bugs.kde.org/show_bug.cgi?id=355899 Matthias Heinz <m.he...@gmx.net> changed: What|Removed |Added CC||m.he...@gmx.net --- Comment #3 from Matthias Heinz <m.he...@gmx.net> --- Hi, this works with plasma-framework 5.28.0 for me now. Matthias -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 296879] Global Shortcuts: Cannot input Backtab
https://bugs.kde.org/show_bug.cgi?id=296879 Matthias Heinz <m.he...@gmx.net> changed: What|Removed |Added CC||m.he...@gmx.net --- Comment #1 from Matthias Heinz <m.he...@gmx.net> --- Hi, this works with plasma-framework 5.28.0 for me. Since this is a very old bug, I suggest closing it, if nobody has any objections. Matthias -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 159063] some keyboard shortcuts don't work
https://bugs.kde.org/show_bug.cgi?id=159063 --- Comment #8 from Matthias Heinz <m.he...@gmx.net> --- Hi, this works with plasma-framework 5.28.0 for me. Since this is a very old bug, I suggest closing it, if nobody has any objections. Matthias -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 284000] Shift+Tab / Backtab issues on global shortcuts
https://bugs.kde.org/show_bug.cgi?id=284000 Matthias Heinz <m.he...@gmx.net> changed: What|Removed |Added CC||m.he...@gmx.net --- Comment #3 from Matthias Heinz <m.he...@gmx.net> --- Hi, I recently figured out that this seems to be fixed in plasma-framework 5.28.0. So I'm suggesting to close this bug. Matthias -- You are receiving this mail because: You are watching all bug changes.
