[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #81 from Claudius Ellsel --- Alright! I'll have another look at it when I test again. Likely, it's not a bug in KWin, but not sure :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #79 from Claudius Ellsel --- (In reply to Nate Graham from comment #78) > Unfortunately I got confused and duped a bunch of X11 bugs to this, and that > issue has been fixed. Sorry for that. At this point it's confusing to > re-open the original issue given that it was (unfortunately incorrectly) > marked as the parent for 9 duplicate reports, so let's keep this one closed. > > Regardless, apps don't do their own positioning on Wayland, so your original > issue was purely a KWin problem. So for simplicity's sake, if you're still > experiencing it with Plasma 5.26 (which made improvements here) please > submit a bug report on KWin. Thanks! Works for me! As has asked before, it seems that https://bugs.kde.org/show_bug.cgi?id=15329 already might be about this exact problem? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #77 from Claudius Ellsel --- (In reply to Viktor Jägersküpper from comment #76) > (In reply to Nate Graham from comment #10) > > The feature to remember window sizes and positions using KXMLGui is not used > > on Wayland. > > > > Remembering window positions on Wayland requires implementing Bug 15329. > > There was some confusion here about Wayland vs X11, but I think this means > bug 15329 is for Wayland. Nate, can you confirm? Also fine. But If you read my original comment here, I specifically said that it happened on Wayland for me and that I haven't tested on X11. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 Claudius Ellsel changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #75 from Claudius Ellsel --- Reopening for now as this is still not fixed for Wayland. Also see https://invent.kde.org/frameworks/kconfig/-/merge_requests/129#note_527114 for details. Please let me know in case the Wayland problems should be treated in another report. Repurposing bugs that were for Wayland originally and then extended for X11 to be only about X11 probably can happen by accident, though is far from ideal, IMHO. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432350] Mouse cursor often does not change on Firefox in Wayland
https://bugs.kde.org/show_bug.cgi?id=432350 --- Comment #9 from Claudius Ellsel --- I cannot reproduce anymore, so might have gotten fixed somewhere in the meantime. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427805] Highlight changed settings has problems with localized places locations
https://bugs.kde.org/show_bug.cgi?id=427805 --- Comment #6 from Claudius Ellsel --- With German, this works for me. Is this still an issue with other locales? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup, KDE app windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #68 from Claudius Ellsel --- (In reply to evea from comment #65) > I do not understand why the title still mentions, and the bug is limited to > X11. The exact same symptoms happen with Wayland. It isn't. The X11 part is just an addition of what is needed to trigger this bug on X11, as far as I see it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427124] Window sizes are not correctly restored on Wayland
https://bugs.kde.org/show_bug.cgi?id=427124 --- Comment #8 from Claudius Ellsel --- (In reply to Vlad Zahorodnii from comment #7) > Should be fixed in 5.24 Hm, not sure. I think I didn't see improvement when I checked. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432350] Mouse cursor often does not change on Firefox in Wayland
https://bugs.kde.org/show_bug.cgi?id=432350 --- Comment #5 from Claudius Ellsel --- During further investigation, I made some interesting findings. I did not find a Wayland application with this problem (but I also don't know of one that has a text cursor apart from input fields). While testing with LibreOffice, I managed to reproduce the problem (but only when there was no cursor blinking). Also, I noticed that the problem doesn't happen in Firefox if I have systemsettings open focused with a blinking cursor in the text field. I assume that it doesn't have to be systemsettings. In LibreOffice when there was a blinking "cursor", I noticed that the mouse cursor changed from normal to text after moving from normal content over text content in the frequency of the "cursor" blinking in the text field (the same happens the other way around when moving the mouse from text over normal content). There is a delay for changing the mouse cursor that seems to "wait" for the "cursor" in the text field to blink. I thus assume that somehow the text field "cursor" blinking is interfering or limiting some function that checks for the mouse cursor position in order to change it matching the content. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432350] Mouse cursor often does not change on Firefox in Wayland
https://bugs.kde.org/show_bug.cgi?id=432350 --- Comment #4 from Claudius Ellsel --- I can also reproduce on other webpages like Wikipedia. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432350] Mouse cursor often does not change on Firefox in Wayland
https://bugs.kde.org/show_bug.cgi?id=432350 Claudius Ellsel changed: What|Removed |Added Status|NEEDSINFO |REPORTED Keywords||wayland Resolution|WAITINGFORINFO |--- --- Comment #3 from Claudius Ellsel --- Finally, I got around to test a bit further. I cannot reproduce it on Bugzilla with X11, so setting Wayland keyword. Not sure whether it happens on other webpages, I think I mostly noticed it on Bugzilla. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398440] plasmashell on wayland in DeclarativeMimeData::DeclarativeMimeData() when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 --- Comment #27 from Claudius Ellsel --- Sounds promising :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 --- Comment #13 from Claudius Ellsel --- Your use cases for the already existing options also apply to the ones I am suggesting, though. On a multi-user system, a user might want to restore his previous used state (and this cannot be done at login screen level). I understand now, though that apart from those use cases it might be better to have the functionality implemented somewhere else, although I am not sure whether it can be done at a central point, so all distributions can benefit, maybe SDDM? But that would be off-topic. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 --- Comment #11 from Claudius Ellsel --- (In reply to Wolfgang Bauer from comment #10) > (In reply to Claudius Ellsel from comment #9) > > Then this issue still remains relevant for KDE in my opinion. Basically I > > think it will be beneficial to for example have a fourth option that will > > use the BIOS setting (or/and another one that restores this setting from the > > previous session). > I'm not sure it's possible from the KDE/Plasma side, and I don't see why > Plasma should change it to be different than on the login screen. > > That's my opinion, of course. It already is possible to set the setting to "on" and "off", so "remember" or "use BIOS value" might also work. If Plasma shouldn't change it to be different from the login screen than even the already existing options are a bit pointless. But if it can be already done at login screen level, that would be even better, I guess. > > Ideally openSUSE would "upstream" the things they do for this and then use > > the setting from KDE instead of relying on a hidden service for this. > That has no relevance to KDE though. It's a service that runs on boot and > also affects text mode. I agree that the service itself has no relevance. But the NumLock features are something I'd really like to see in KDE as well. But I might be wrong here and getting that correct is up to every distribution, because it has to be done at a lower level (unfortunately both distros with KDE that I have used, Manjaro and Tumbleweed, currently don't seem to get this right, so I thought a more centralistic solution might help). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428594] Firefox window thumbnails are sometimes empty
https://bugs.kde.org/show_bug.cgi?id=428594 Claudius Ellsel changed: What|Removed |Added Keywords||wayland CC||claudius.ell...@live.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432350] New: Mouse cursor often does not change on Firefox in Wayland
https://bugs.kde.org/show_bug.cgi?id=432350 Bug ID: 432350 Summary: Mouse cursor often does not change on Firefox in Wayland Product: plasmashell Version: 5.20.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: claudius.ell...@live.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On Firefox (and possible other XWayland applications) the mouse cursor doesn't always change. Examples are when I am over text and the cursor should change to a "text" cursor. Or when I somehow get it to change to that cursor and move away from the text, but it still is a text cursor and doesn't change back to a normal one. STEPS TO REPRODUCE 1. A page where this happens is https://bugs.kde.org/enter_bug.cgi 2. Move the mouse around over the content SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210128 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 This might be unrelated to Wayland or Plasma, haven't thoroughly tested. Maybe this is a Firefox bug in general. Product and component might be wrong. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432349] Switching from Wayland to X11 changes or resets the primary screen there
https://bugs.kde.org/show_bug.cgi?id=432349 --- Comment #1 from Claudius Ellsel --- At some point in the past, but maybe only on a different distribution, this worked fine without this bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 432349] New: Switching from Wayland to X11 changes or resets the primary screen there
https://bugs.kde.org/show_bug.cgi?id=432349 Bug ID: 432349 Summary: Switching from Wayland to X11 changes or resets the primary screen there Product: KScreen Version: 5.20.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: claudius.ell...@live.de Target Milestone: --- SUMMARY When I switch from a Wayland to an X11 session the primary screen of X11 is not the one it used to be. STEPS TO REPRODUCE 1. Have a multi monitor setup (I have a vertical one on the left and a horizontal one on the right. The right monitor is set as primary on X11). 2. Configure the monitors in X11 to work as written in 1. 3. Logout and login to a Wayland session 4. Due to another bug the vertical screen will have the wrong orientation on Wayland. Change that in KScreen to look normal (might be completely unrelated, though) 5. Logout and login to an X11 session OBSERVED RESULT The left monitor is now the primary screen EXPECTED RESULT The primary screen should stay as it was (the right screen) SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210128 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432260] Spectacle fails to create rectangular screenshots
https://bugs.kde.org/show_bug.cgi?id=432260 --- Comment #7 from Claudius Ellsel --- (In reply to Méven Car from comment #6) > Could you run `kscreen-doctor -o` This gives: Output: 33 XWAYLAND0 enabled connected Unknown Modes: 36:2560x1440@60*! Geometry: 1080,240 2560x1440 Scale: 1 Rotation: 1 Output: 35 XWAYLAND1 enabled connected Unknown Modes: 37:1920x1080@60*! Geometry: 0,0 1080x1920 Scale: 1 Rotation: 8 > The issue is somehow KWin screens names are different from > QApplication::screens() Hm. That might have been caused by me running multiple screens. I also switch between X11 and Wayland sessions which might introduce further problems (for example when switching from Wayland to X11 I have to correct the screen orientation of my vertical screen due to a different issue and also X11 currently always makes that one primary). Might not be related at all, though. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 Claudius Ellsel changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Claudius Ellsel --- On a second test it worked for me, so most likely a false alarm. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 420310] drkonqi itself crashed while trying to submit another crash report
https://bugs.kde.org/show_bug.cgi?id=420310 --- Comment #7 from Claudius Ellsel --- (In reply to David Edmundson from comment #1) > Fixed recently > > b2ebd8f2ca332473f09e589d9e7ee0af0e1c7d98 in drkonqi For convenience: https://invent.kde.org/plasma/drkonqi/-/commit/b2ebd8f2ca332473f09e589d9e7ee0af0e1c7d98 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 420310] drkonqi itself crashed while trying to submit another crash report
https://bugs.kde.org/show_bug.cgi?id=420310 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de --- Comment #6 from Claudius Ellsel --- Any chance this is related to or the same as https://bugs.kde.org/show_bug.cgi?id=429136? -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 432319] Crash as soon as typing in the bug description box
https://bugs.kde.org/show_bug.cgi?id=432319 Claudius Ellsel changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Claudius Ellsel --- *** This bug has been marked as a duplicate of bug 429136 *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 429136] Crash reporting assistant crashes on Wayland when I type anything in "Information about the crash" text box
https://bugs.kde.org/show_bug.cgi?id=429136 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de --- Comment #2 from Claudius Ellsel --- *** Bug 432319 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 432319] New: Crash as soon as typing in the bug description box
https://bugs.kde.org/show_bug.cgi?id=432319 Bug ID: 432319 Summary: Crash as soon as typing in the bug description box Product: drkonqi Version: 5.20.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: claudius.ell...@live.de Target Milestone: --- SUMMARY When I want to create a bug report, the application crashes as soon as I type in the bug description. STEPS TO REPRODUCE 1. Have an application crash (like systemsettings) 2. A notification appears and offers to report that crash 3. Dr. Konqi opens and guides through the steps (I selected that I remember what I did when the application crashed) 4. Sign in to the Bugzilla account 5. Select to create a new bug 6. The page for entering the new bug's details opens OBSERVED RESULT Entering the title works but as soon as I type in the bug description box the application crashes. EXPECTED RESULT The application doesn't crash. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210128 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432260] Spectacle fails to create rectangular screenshots
https://bugs.kde.org/show_bug.cgi?id=432260 --- Comment #5 from Claudius Ellsel --- This seems to be unrelated to multiple screens (at least I got the same error in the terminal after deactivating my second monitor in KScreen). -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432260] Spectacle fails to create rectangular screenshots
https://bugs.kde.org/show_bug.cgi?id=432260 Claudius Ellsel changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Claudius Ellsel --- (In reply to Andrey from comment #2) > What's in the error message? > Also you could try to run in from terminal to see more prompt output. Basically it just says that it cannot take a screenshot. I did not find an easy way to screenshot that window, as it is Spectacle and usually not wanted on Screenshots. Running from terminal was a good idea. It gives the following error message when trying to create a rectangular screenshot: `Error calling KWin DBus interface: "org.kde.kwin.Screenshot.Error.ScreenMissing" "Screen not found"` (In reply to Méven Car from comment #3) > Where you using multiple screens ? > What is the version of spectacle used ? Yes, I am using multiple screens. Version of Spectacle used is 20.12.1 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 Claudius Ellsel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from Claudius Ellsel --- Alright. I am marking this as waitingforinfo, as everything might be working completely fine. The instance where the screen was still on after I was afk for about 30 Minutes might have been caused by my mouse slightly moving and thus turning the screen on again. I'll have to try again properly, and probably it will also work for me, so false alarm. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #17 from Claudius Ellsel --- Mh, looking at the videos here, the symptoms look different compared to https://bugs.kde.org/show_bug.cgi?id=427127 (and this here seems to also happen on X11). So I am not entirely sure whether that one is actually a duplicate of this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432255] Hovercard background is sometimes not correct
https://bugs.kde.org/show_bug.cgi?id=432255 --- Comment #4 from Claudius Ellsel --- *** This bug has been marked as a duplicate of bug 416048 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #16 from Claudius Ellsel --- *** Bug 432255 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #15 from Claudius Ellsel --- Just to confirm, this only happens on Wayland as on the duplicate, correct? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 --- Comment #14 from Claudius Ellsel --- *** Bug 427127 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 427127] Sometimes tooltips of systray applets and widgets placed on Plasma panel are corrupted on Wayland
https://bugs.kde.org/show_bug.cgi?id=427127 Claudius Ellsel changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Claudius Ellsel --- *** This bug has been marked as a duplicate of bug 416048 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416048] Morphing Popups effect: glitch when the size of a tooltip is reduced
https://bugs.kde.org/show_bug.cgi?id=416048 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- --- Comment #13 from Claudius Ellsel --- Since this bug is the older one and contains more information, I am reversing the duplicate direction. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432242] Visual glitch behind integrated terminals on Wayland session
https://bugs.kde.org/show_bug.cgi?id=432242 --- Comment #2 from Claudius Ellsel --- Related to https://bugs.kde.org/show_bug.cgi?id=429025? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432242] Visual glitch behind integrated terminals on Wayland session
https://bugs.kde.org/show_bug.cgi?id=432242 Claudius Ellsel changed: What|Removed |Added Keywords||wayland CC||claudius.ell...@live.de -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 --- Comment #2 from Claudius Ellsel --- Just tested on X11 and I have a similar experience there. Waited about a minute but nothing changed. However, I am not entirely sure anymore how long it used to take the screens to turn off after locking the screen. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432260] Spectacle fails to create rectangular screenshots
https://bugs.kde.org/show_bug.cgi?id=432260 Claudius Ellsel changed: What|Removed |Added Keywords||wayland --- Comment #1 from Claudius Ellsel --- Wayland only, X11 is fine. Setting keyword. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432260] New: Spectacle fails to create rectangular screenshots
https://bugs.kde.org/show_bug.cgi?id=432260 Bug ID: 432260 Summary: Spectacle fails to create rectangular screenshots Product: Spectacle Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: claudius.ell...@live.de CC: k...@david-redondo.de Target Milestone: --- SUMMARY When I want to create a rectangular screenshot I get an error message. STEPS TO REPRODUCE 1. Launch Spectacle 2. Select the "rectangular area" mode from the dropdown 3. Click the button to create a new screenshot OBSERVED RESULT An error message is displayed EXPECTED RESULT The mode for rectangular screenshots is launched Happens on Wayland, will also test on X11. This might be a regression. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210127 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 --- Comment #1 from Claudius Ellsel --- I am rather sure this is a regression (although I haven't used Tumbleweed Wayland that often). Setting the keyword. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 Claudius Ellsel changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 432259] New: Screen does not seem to turn off when locked
https://bugs.kde.org/show_bug.cgi?id=432259 Bug ID: 432259 Summary: Screen does not seem to turn off when locked Product: kscreenlocker Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: claudius.ell...@live.de CC: bhus...@gmail.com Target Milestone: --- SUMMARY On the current Plasma Beta (5.20.90) I noticed that the screen doesn't seem to turn off when I lock it (shortcut Meta + L). Currently only tested on Wayland. STEPS TO REPRODUCE 1. Start a session 2. Lock the screen 3. Wait a short amount of time for the displays to turn off OBSERVED RESULT The displays stay on EXPECTED RESULT The displays are turned off SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210127 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432256] Some applications including Konsole don't show resize handles for the lower three edges
https://bugs.kde.org/show_bug.cgi?id=432256 --- Comment #2 from Claudius Ellsel --- Another affected application is Dolphin, others like systemsettings work fine. Possibly the root cause is at a higher level, but I thought for the beginning I'd file this for a specific app. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432256] Some applications including Konsole don't show resize handles for the lower three edges
https://bugs.kde.org/show_bug.cgi?id=432256 --- Comment #1 from Claudius Ellsel --- I am pretty confident this is a regression, although I cannot say that for sure. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432256] Some applications including Konsole don't show resize handles for the lower three edges
https://bugs.kde.org/show_bug.cgi?id=432256 Claudius Ellsel changed: What|Removed |Added Keywords||regression, usability, ||wayland -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 432256] New: Some applications including Konsole don't show resize handles for the lower three edges
https://bugs.kde.org/show_bug.cgi?id=432256 Bug ID: 432256 Summary: Some applications including Konsole don't show resize handles for the lower three edges Product: konsole Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: claudius.ell...@live.de Target Milestone: --- SUMMARY On Wayland some applications don't show resize handles for me on their lower three edges. The top edge works. STEPS TO REPRODUCE 1. Open Konsole 2. Move the mouse to the lower edge OBSERVED RESULT No resize handle appears EXPECTED RESULT A resize handle should appear SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210127 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432255] Hovercard background is sometimes not correct
https://bugs.kde.org/show_bug.cgi?id=432255 --- Comment #2 from Claudius Ellsel --- The "black" or dark bar on the right is in fact not black, but the card turns semi transparent in that region apparently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432255] Hovercard background is sometimes not correct
https://bugs.kde.org/show_bug.cgi?id=432255 Claudius Ellsel changed: What|Removed |Added Keywords||wayland --- Comment #1 from Claudius Ellsel --- Only happens on Wayland, setting keyword. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432255] Hovercard background is sometimes not correct
https://bugs.kde.org/show_bug.cgi?id=432255 Claudius Ellsel changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432255] New: Hovercard background is sometimes not correct
https://bugs.kde.org/show_bug.cgi?id=432255 Bug ID: 432255 Summary: Hovercard background is sometimes not correct Product: plasmashell Version: 5.20.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: claudius.ell...@live.de CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 135270 --> https://bugs.kde.org/attachment.cgi?id=135270=edit Screenshot of the problem SUMMARY When hovering from right to left over the icons the background of the hovercards is not correct. I started at the Firefox icon and then moved over the Dolphin icon where you can see a black stripe on the right. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210121 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.7-1-default OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary one.
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #26 from Claudius Ellsel --- (In reply to Shawn from comment #25) > I have a dual monitor setup with both resolutions at 2560x14440. I can't do > any of the coding stuff that you guys do, but if there is something I can > test to help, let me know. I say this because most of the comments I see > are from ppl that have a laptop + some other screen, possibly with different > resolutions. A screenshot of your screen setup (and arrangement) from the systemsettings might be interesting. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425796] Screen rotation is applied the wrong orientation in KCM on Wayland
https://bugs.kde.org/show_bug.cgi?id=425796 Claudius Ellsel changed: What|Removed |Added Platform|Manjaro |openSUSE RPMs Version|5.20.0 |5.20.90 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425796] Screen rotation is applied the wrong orientation in KCM on Wayland
https://bugs.kde.org/show_bug.cgi?id=425796 Claudius Ellsel changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #12 from Claudius Ellsel --- Reopening here, as I ran into this bug again when testing the 5.20.90 Beta on openSUSE Tumbleweed. Not sure whether this is a regression or only ever was fixed for the compiled from master session I tested with. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432101] Screen rotation mixup bug on Wayland seems to have regressed with the Beta
https://bugs.kde.org/show_bug.cgi?id=432101 Claudius Ellsel changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #2 from Claudius Ellsel --- I will reopen and mark this a duplicate then. I wasn't sure whether reopening was the correct thing to do here, as the issue appeared to have been fixed in the past when I tested. But the symptoms are the same. The only difference is that I experience this on openSUSE Tumbleweed (in contrast to Manjaro or a compiled from master session there where it was no longer occurring). *** This bug has been marked as a duplicate of bug 425796 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425796] Screen rotation is applied the wrong orientation in KCM on Wayland
https://bugs.kde.org/show_bug.cgi?id=425796 --- Comment #11 from Claudius Ellsel --- *** Bug 432101 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 Claudius Ellsel changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Severity|normal |wishlist Resolution|INTENTIONAL |--- --- Comment #9 from Claudius Ellsel --- Ah, then I misunderstood your comment on the openSUSE tracker and thought that would generally apply to KDE in general. Then this issue still remains relevant for KDE in my opinion. Basically I think it will be beneficial to for example have a fourth option that will use the BIOS setting (or/and another one that restores this setting from the previous session). This is at least what I as a user would expect, not sure whether it makes sense from an architectural / distribution point of view. Ideally openSUSE would "upstream" the things they do for this and then use the setting from KDE instead of relying on a hidden service for this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #36 from Claudius Ellsel --- (In reply to Greg Lepore from comment #32) > See attachment. NumLock is set to "Turn on" and kreadconfig5 --file > kcminputrc --group Keyboard --key NumLock shows "0". These appear to be > incompatible settings. > > I think my screenshot is accurately portraying the submitters report, isn't > it? Hm, I am not an expert, but it seems as if changes of this preference are not transferred correctly to the settings file? Out of curiosity, does the output of that command change if you change the preference in the settings? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 --- Comment #7 from Claudius Ellsel --- (In reply to Wolfgang Bauer from comment #5) > (In reply to Claudius Ellsel from comment #0) > > Also, Ideally that would already work at either Kernel > > or SDDM level, not sure what causes the problems there. > In that case, it should be reported to the kernel or SDDM though. > > At least SDDM does have a setting for this: > Numlock= > Change numlock state when sddm-greeter starts. Valid values > are on, off > or none. If property is set to none, numlock won't be > changed. Default > value is "none". Yup, just wanted to make sure first that I get the scope of the problem correctly. As I wrote before, NumLock is already off for SDDM. Does the `none` value there also means that it is supposed to read the BIOS value or just that it doesn't touch NumLock at all meaning when the Kernel has turned it off it will just stay at that? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 --- Comment #6 from Claudius Ellsel --- (In reply to Wolfgang Bauer from comment #2) > "Don't change" means exactly that: don't change it. > > So I don't see how this can possibly be a KDE bug. Ah, I thought it meant don't change from the previous state (in the boot process), meaning if SDDM or some other previous applications changed it, it will remain unchanged. But apparently that is not what it means, instead it means that the value set in BIOS will be applied? In this case this is indeed intentional (apart from apparently downstream bugs where this does not work like on Tumbleweed or Manjaro). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 --- Comment #1 from Claudius Ellsel --- Copying over my comment from https://bugs.kde.org/show_bug.cgi?id=368063, since that was misplaced there: After witnessing the changes on the NumLock LED (before my keyboard did not have one), I am wondering whether this also has something to do with SDDM or Linux kernel options (at least when the option is set to "leave unchanged"). When booting, the NumLock LED is already off when SDDM shows up. If I remember correctly that is explicitly also the case when one has enabled NumLock to turn on when booting in the BIOS settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #28 from Claudius Ellsel --- Since this bug is (at least originally) about cases where the preference to always turn NumLock on is explicitly set, I created another one generally tracking the problem that this is not the default value: https://bugs.kde.org/show_bug.cgi?id=432107. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Claudius Ellsel changed: What|Removed |Added Summary|NumLock not turned on |NumLock not is not turned ||on at start, although the ||preference for it is set to ||`on` in kcm_keyboard -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432107] Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 Claudius Ellsel changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432107] New: Default NumLock settings to leave the state unchanged will result in NumLock turned off
https://bugs.kde.org/show_bug.cgi?id=432107 Bug ID: 432107 Summary: Default NumLock settings to leave the state unchanged will result in NumLock turned off Product: plasmashell Version: 5.20.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: claudius.ell...@live.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The default setting for NumLock is to leave the state unchanged, which makes sense to some degree. Unfortunately either Linux or SDDM turn NumLock always off, so the "leave unchanged" setting does not appear to be a good default value to me. What I'd expect would be "restore to last used setting" or something like that to be default. Also, Ideally that would already work at either Kernel or SDDM level, not sure what causes the problems there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428977] Dragging tabs from Firefox over the desktop results in a crash
https://bugs.kde.org/show_bug.cgi?id=428977 --- Comment #11 from Claudius Ellsel --- Still easily reproducible on my setup, currently tested on openSUSE Tumbleweed with 5.20.90. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427808] Some applications don't remember their maximized state (at least on Wayland)
https://bugs.kde.org/show_bug.cgi?id=427808 Claudius Ellsel changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas | |ma/kwin/-/commit/76a33c90fb | |3a8ebdb9a8049953d79f093927f | |250 | Version Fixed In|5.20.1 | --- Comment #11 from Claudius Ellsel --- Removing the referenced commit and version fixed in, as that commit seems to fix a different problem, if I understand it correctly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423161] Search results blink when updating
https://bugs.kde.org/show_bug.cgi?id=423161 Claudius Ellsel changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423161] Search results blink when updating
https://bugs.kde.org/show_bug.cgi?id=423161 Claudius Ellsel changed: What|Removed |Added Version|5.19.0 |5.20.90 --- Comment #2 from Claudius Ellsel --- Just wanted to confirm this is still happening with the new Kickoff. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary one.
https://bugs.kde.org/show_bug.cgi?id=427875 Claudius Ellsel changed: What|Removed |Added Version|5.75.0 |5.78.0 CC||aleix...@kde.org, ||k...@davidedmundson.co.uk, ||vlad.zahorod...@kde.org --- Comment #24 from Claudius Ellsel --- Adding some kwin people to CC as well, maybe they have a clue what is going on here. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary one.
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #23 from Claudius Ellsel --- *** Bug 427808 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427808] Some applications don't remember their maximized state (at least on Wayland)
https://bugs.kde.org/show_bug.cgi?id=427808 Claudius Ellsel changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |DUPLICATE --- Comment #10 from Claudius Ellsel --- Marking as duplicate, as I am rather confident they are the same. The symptoms are the same at least. *** This bug has been marked as a duplicate of bug 427875 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 429772] Creating a rectangular screenshot on Wayland does not hide the Spectacle window
https://bugs.kde.org/show_bug.cgi?id=429772 Claudius Ellsel changed: What|Removed |Added Keywords||regression, usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427826] Window thumbnails usually aren't displayed on Wayland
https://bugs.kde.org/show_bug.cgi?id=427826 Claudius Ellsel changed: What|Removed |Added Summary|Window thumbnails don't |Window thumbnails usually |work|aren't displayed on Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427826] Window thumbnails don't work
https://bugs.kde.org/show_bug.cgi?id=427826 Claudius Ellsel changed: What|Removed |Added Keywords||wayland --- Comment #10 from Claudius Ellsel --- Things seem to work fine on X11, so setting Wayland keyword. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427826] Window thumbnails don't work
https://bugs.kde.org/show_bug.cgi?id=427826 Claudius Ellsel changed: What|Removed |Added Version|5.20.3 |5.20.90 Platform|Manjaro |openSUSE RPMs --- Comment #9 from Claudius Ellsel --- Still happening on the current Plasma Beta. I think this is only happening on Wayland (on Tumbleweed). Sometimes it seems to work however after waiting a second or two. Also, I noticed an interesting detail: Thumbnails are often not displayed while the mouse is over the hover card. But as soon as it moves on top of the corresponding window, the thumbnail is displayed. This is a pretty weird behavior. Maybe some security thing where thumbnails can only be taken from an "active" window? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary one.
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #22 from Claudius Ellsel --- Still happens with the current Plasma Beta. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] On a multi screen setup windows do not remember size, position, or the screen they were last opened on. For X11 when the left-most display is not the primary one.
https://bugs.kde.org/show_bug.cgi?id=427875 Claudius Ellsel changed: What|Removed |Added Summary|Windows do not remember |On a multi screen setup |size, position, or the |windows do not remember |screen they were last |size, position, or the |opened on when the |screen they were last |left-most display is not|opened on. For X11 when the |the primary one |left-most display is not ||the primary one. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432101] Screen rotation mixup bug on Wayland seems to have regressed with the Beta
https://bugs.kde.org/show_bug.cgi?id=432101 Claudius Ellsel changed: What|Removed |Added Keywords||regression, wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432101] New: Screen rotation mixup bug on Wayland seems to have regressed with the Beta
https://bugs.kde.org/show_bug.cgi?id=432101 Bug ID: 432101 Summary: Screen rotation mixup bug on Wayland seems to have regressed with the Beta Product: systemsettings Version: 5.20.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: claudius.ell...@live.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY After installing the current Plasma Beta on Tumbleweed, it appears as if the screen rotation bug on Wayland has either regressed or was never really fixed entirely: https://bugs.kde.org/show_bug.cgi?id=425796. See the linked report for a more detailed description. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 298133] The Properties dialog considers non-files like 'proc' for the size calculation, causing an apparent root directory size of 128 TiB
https://bugs.kde.org/show_bug.cgi?id=298133 Claudius Ellsel changed: What|Removed |Added CC||a.samir...@gmail.com, ||fa...@kde.org --- Comment #8 from Claudius Ellsel --- Adding two devs to cc, I guess with the knowledge available a path to a solution can be found rather easy? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 298133] The Properties dialog considers non-files like 'proc' for the size calculation, causing an apparent root directory size of 128 TiB
https://bugs.kde.org/show_bug.cgi?id=298133 --- Comment #7 from Claudius Ellsel --- (In reply to Frank Reininghaus from comment #1) > I can confirm the 128 TiB in KDE 4.8.2. Most likely due to "files" in /proc > being included, see also > http://forum.kde.org/viewtopic.php?f=223=101330 This seems to be true, according to https://bugs.kde.org/show_bug.cgi?id=423057#c1 the file "to blame" is 'proc/kcore'. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 353391] wrong calculated size of direcories
https://bugs.kde.org/show_bug.cgi?id=353391 --- Comment #11 from Claudius Ellsel --- Thanks btw. for finding the duplicates and triaging them! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 298133] The Properties dialog considers non-files like 'proc' for the size calculation, causing an apparent root directory size of 128 TiB
https://bugs.kde.org/show_bug.cgi?id=298133 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 353391] wrong calculated size of direcories
https://bugs.kde.org/show_bug.cgi?id=353391 --- Comment #9 from Claudius Ellsel --- Hm, usually I'd expect the oldest bug to be the original one (in this case it seems https://bugs.kde.org/show_bug.cgi?id=298133 is the one) and then all newer bugs to be marked as duplicates of that one. Is there a reason not to handle it this way here? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411500] Add a contextual actions panel/toolbar
https://bugs.kde.org/show_bug.cgi?id=411500 --- Comment #5 from Claudius Ellsel --- With single click in mind, this might not work that nicely, though. At least it would be harder to open the side bar, since one cannot simply click a file or folder. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411500] Add a contextual actions panel/toolbar
https://bugs.kde.org/show_bug.cgi?id=411500 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de --- Comment #4 from Claudius Ellsel --- Adding two links for the macOS finder approach here for reference. - https://appleinsider.com/articles/18/10/05/how-to-add-your-own-quick-actions-to-the-new-macos-mojave-finder - https://support.apple.com/en-za/guide/mac-help/mchl97ff9142/mac -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 417162] Incorrect tooltip position when shown on the edge of second screen
https://bugs.kde.org/show_bug.cgi?id=417162 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de --- Comment #6 from Claudius Ellsel --- Since there are no screenshots of the problem, I don't know exactly what this does. I think I have noted unexpected tooltop behavior in other KDE applications as well, though. Basically when the tooltip is near the screen edge (the one where two screens meet), it will be displayed on the other screen instead of the current screen the application is on. So it might be worth to look whether other applications require similar fixes (or whether it is possible to unify their behavior somehow). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 411563] Need a way to visualize microphone's current recording volume
https://bugs.kde.org/show_bug.cgi?id=411563 Claudius Ellsel changed: What|Removed |Added CC||claudius.ell...@live.de --- Comment #7 from Claudius Ellsel --- The original scope of this issue was to also have this in the KCM. I agree that it would make sense to also have it there, which to my knowledge isn't the case currently. Do we want to reopen this or track that in a new report? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429779] gparted installed from Discover on Neon unstable VM lacks icons
https://bugs.kde.org/show_bug.cgi?id=429779 Claudius Ellsel changed: What|Removed |Added Ever confirmed|0 |1 Resolution|DOWNSTREAM |--- Status|RESOLVED|REOPENED --- Comment #7 from Claudius Ellsel --- Thanks for following up here! I guess I forgot or did not came around to update this issue with your findings. Since those show the problem most likely has something to do with some KDE Neon specific things, I will reopen this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431234] Dolphin does not remember its window size
https://bugs.kde.org/show_bug.cgi?id=431234 --- Comment #17 from Claudius Ellsel --- Thanks for confirming! I suggest you to follow up in the original bug then (linked above). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427803] Vertical wallpaper of 5.20 is rotated instead of cropped while maintaining its orientation
https://bugs.kde.org/show_bug.cgi?id=427803 Claudius Ellsel changed: What|Removed |Added Summary|Wallpaper size chooser |Vertical wallpaper of 5.20 |algorithm doesn't take into |is rotated instead of |account images rotated with |cropped while maintaining |a rotation tag |its orientation -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427803] Wallpaper size chooser algorithm doesn't take into account images rotated with a rotation tag
https://bugs.kde.org/show_bug.cgi?id=427803 --- Comment #22 from Claudius Ellsel --- (In reply to Nate Graham from comment #20) > I see. > > In that case there is no point to this discussion because we have already > changed the wallpaper in Plasma 5.21 to one that you do not find > objectionable, and there are no further Plasma 5.20 releases planned with > which we would have the opportunity to make any changes. Alright, makes sense. Pretty much what I guessed in comment #7. Sorry that there apparently was misunderstanding afterwards. (In reply to Nate Graham from comment #21) > FWIW, rotating the Shell wallpaper for the portrait version was indeed > intentional. Lol, did not anticipate that :) Maybe worth noting that such things might confuse *some* users of multimonitor setups ;) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427803] Wallpaper size chooser algorithm doesn't take into account images rotated with a rotation tag
https://bugs.kde.org/show_bug.cgi?id=427803 --- Comment #19 from Claudius Ellsel --- Yes, if you consider rotating it by 90 degrees a concious cosmetic choice. I don't think that was on purpose. Best read the description of this issue again and look at the first attachement. That sums it up pretty well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425190] Improve scaling of the desktop
https://bugs.kde.org/show_bug.cgi?id=425190 --- Comment #25 from Claudius Ellsel --- (In reply to Carlos from comment #24) > Cludius: I don't understand your second experiment quite well. When you > upscaled x2 you just took the small icons and duplicated everything? If > that's the case, it might be worth for comparative purposes but I don't > think as a scaling technique that would improve too much on plain upscaling, > since it's not adding any new information (like, say, a handcrafted version > or an upscaled svg version). You mean my first experiment? I upscaled in the first series and for the second series I downscaled (after learning that icons are at least in theory only downscaled), both times starting with (I think) a screenshot of a desktop with 1x or 2x scale factor respectively. The tray icons in the second approach's 2x source are just looking that small originally. Does that help? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427803] Wallpaper size chooser algorithm doesn't take into account images rotated with a rotation tag
https://bugs.kde.org/show_bug.cgi?id=427803 --- Comment #17 from Claudius Ellsel --- No, if the image would have been rotated by moving pixels around instead of adding a rotation tag the problem would be exactly the same. It should not have been rotated at all, but cropped instead while maintaining orientation of the content. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427803] Wallpaper size chooser algorithm doesn't take into account images rotated with a rotation tag
https://bugs.kde.org/show_bug.cgi?id=427803 --- Comment #15 from Claudius Ellsel --- Created attachment 134856 --> https://bugs.kde.org/attachment.cgi?id=134856=edit Correctly vertically cropped example To be completely clear and avoid misunderstanding: This attachement shows a quick example of how it *should* look like instead. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427803] Wallpaper size chooser algorithm doesn't take into account images rotated with a rotation tag
https://bugs.kde.org/show_bug.cgi?id=427803 --- Comment #14 from Claudius Ellsel --- They are rotated to the vertical aspect ration instead of cropped (which would retain their orientation). Look at https://invent.kde.org/plasma/breeze/-/blob/6c72bd648e6e97f52fb255e5c1d69d1e143a89ec/wallpapers/Next/contents/images/vertical_base_size.jpg - The content is rotated by 90 degrees clockwise there. The content should not be rotated to get a vertical aspect ratio (you can compare that to the new one for example, where it is correct: https://invent.kde.org/plasma/breeze/-/blob/51840ad0686cf1182ce0ee1810864a5725412e1b/wallpapers/Next/contents/images/vertical_base_size.png, alternatively the previous one, also correctly oriented: https://invent.kde.org/plasma/breeze/-/blob/9873c57ea38348636f82665d3f933948a94ba06e/wallpapers/Next/contents/images/720x1440.jpg). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427803] Wallpaper size chooser algorithm doesn't take into account images rotated with a rotation tag
https://bugs.kde.org/show_bug.cgi?id=427803 --- Comment #12 from Claudius Ellsel --- One more data point (which might only add confusion to this, but anyway): The orientation is correct on the lockscreen (not SDDM but the other one - Shortcut Meta + L). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] Windows do not remember size, position, or the screen they were last opened on when the left-most display is not the primary one
https://bugs.kde.org/show_bug.cgi?id=427875 --- Comment #21 from Claudius Ellsel --- I might have found an explanation to this, although this is just a theory without me having any proper knowledge of how this works internally. I noticed that when having a window spread across two screens before closing, it will get restored only on the left-most screen. So maybe the restoring process works like this: First restore window size (which will always happen on the left-most screen) and after that restore position (moving the window to the correct position. The problem with this is that restoring the window size before setting the correct position might fail, although I am not exactly sure why. I first thought maybe the resolution of the screen where the window size is attempted to restore is too low but that is not true for all my tests. Also one would need to explain the "fall back" to the old resolution set before, which seems to be stored somewhere. -- You are receiving this mail because: You are watching all bug changes.
