[Powerdevil] [Bug 482278] Screen remains dimmed after unlocking
https://bugs.kde.org/show_bug.cgi?id=482278 --- Comment #6 from David Warner --- Sorry, ignore all the above - it just happened on the DisplayPort monitors, too. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482278] Screen remains dimmed after unlocking
https://bugs.kde.org/show_bug.cgi?id=482278 --- Comment #5 from David Warner --- In case it's helpful: in my 2x DisplayPort, 1x HDMI setup, the issue seems to be occurring only on the monitor connected by HDMI - the other 2 monitors are correctly set at 100% brightness after resuming. The monitor connected by HDMI also takes longer to turn back on, so I wonder if it's a timing issue of some kind. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482278] Screen remains dimmed after unlocking
https://bugs.kde.org/show_bug.cgi?id=482278 --- Comment #3 from David Warner --- (In reply to Jakob Petsovits from comment #2) > Hi, could you confirm if this is still an issue with Plasma 6.0.1 or higher? > The original 6.0.0 release was missing this commit: > https://invent.kde.org/plasma/powerdevil/-/commit/ > 8681355217eb6ff121785572eaf4ef2ca21b464b which fixed restoring the old > brightness in some cases (see the link for more details in the commit > message). This is still an issue for me in 6.0.3. Same repro steps as above. My screens (2x DisplayPort, 1x HDMI) are set to 100% brightness; after the screens are turned off due to inactivity, they will be at some brightness <100% after being turned back on. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482278] Screen remains dimmed after unlocking
https://bugs.kde.org/show_bug.cgi?id=482278 David Warner changed: What|Removed |Added CC||david.p.war...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482064] Sluggish Desktop on Plasma 6, swap interval problem
https://bugs.kde.org/show_bug.cgi?id=482064 --- Comment #14 from David Warner --- Happy to confirm this is fixed for me in 6.0.1 with the above commit. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482064] Sluggish Desktop on Plasma 6, swap interval problem
https://bugs.kde.org/show_bug.cgi?id=482064 David Warner changed: What|Removed |Added CC||david.p.war...@gmail.com --- Comment #8 from David Warner --- I think I'm seeing the same issue on my desktop, but only when I set my display to 24 Hz (the glxgears FPS drops to 12 - for other refresh rates, the FPS matches the refresh rate). I noticed because I use mpv-kscreen-doctor to set the display refresh rate to match the video refresh rate in mpv, which is frequently 24 Hz: https://gitlab.com/smaniottonicola/mpv-kscreen-doctor Operating System: Fedora Linux 39 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7700X 8-Core Processor Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon RX 6800 XT Manufacturer: ASRock Product Name: 7667CB5 System Version: B650M PG Riptide -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476566] Wine drag & drop coordinates off with Wayland fractional scaling
https://bugs.kde.org/show_bug.cgi?id=476566 --- Comment #2 from David Warner --- (In reply to Akseli Lahtinen from comment #1) > Can confirm this issue, the coordinates are offset. It also seems that the > Wine application is not scaled at all, text wise. Thanks for confirming. Wine has its own DPI settings (winecfg -> Graphics -> Screen resolution > 144 dpi (for 150%)), which scales text and other elements, at least on my machine. This setting doesn't seem to change the drag & drop behaviour, however. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476566] Wine drag & drop coordinates off with Wayland fractional scaling
https://bugs.kde.org/show_bug.cgi?id=476566 David Warner changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476566] New: Wine drag & drop coordinates off with Wayland fractional scaling
https://bugs.kde.org/show_bug.cgi?id=476566 Bug ID: 476566 Summary: Wine drag & drop coordinates off with Wayland fractional scaling Classification: Plasma Product: kwin Version: 5.27.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: david.p.war...@gmail.com Target Milestone: --- Created attachment 162872 --> https://bugs.kde.org/attachment.cgi?id=162872=edit foobar2000 screenshot SUMMARY Drag & drop coordinates in Wine apps are wrong when Wayland fractional scaling is enabled. STEPS TO REPRODUCE 1. Set monitor to 150% scaling (Wayland session). 2. Install foobar2000, select Album List + Properties layout. 3. Drag file(s) from Dolphin to foobar2000 playlist area. OBSERVED RESULT The drop target area is off by a factor of 1.5. For example, if the playlist area top left corner is positioned at (640,360), the mouse needs to be moved to (960,540) for the drop reticle to appear. EXPECTED RESULT The mouse coordinates should match the drop target coordinates. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Wine DPI scaling doesn't make seem to make a difference (configured via winecfg). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433284] Shortcut for switching input method (Windows + Space) does not work when using kimpanel-ibus-panel
https://bugs.kde.org/show_bug.cgi?id=433284 David Warner changed: What|Removed |Added CC||david.p.war...@gmail.com --- Comment #16 from David Warner --- IBus 1.5.29 better integrates with Wayland, and the Super+Space shortcut works now in Wayland apps, though not XWayland apps. https://bugzilla.redhat.com/show_bug.cgi?id=2076596 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 476543] Wrong display sizes when Wayland fractional scaling enabled
https://bugs.kde.org/show_bug.cgi?id=476543 David Warner changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 476543] New: Wrong display sizes when Wayland fractional scaling enabled
https://bugs.kde.org/show_bug.cgi?id=476543 Bug ID: 476543 Summary: Wrong display sizes when Wayland fractional scaling enabled Classification: Applications Product: krdc Version: 23.08.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: VNC Assignee: uwol...@kde.org Reporter: david.p.war...@gmail.com CC: aa...@kde.org Target Milestone: --- SUMMARY When fractional scaling is enabled in the Wayland session, KRDC renders VNC connections in the wrong resolution. 100% or 200% scaling works correctly. STEPS TO REPRODUCE 1. Run a VNC server on host (e.g. x11vnc on a machine with a display resolution of 1280x800). 2. Set monitor scaling on client to 125% or 150%. 3. Connect to host with KRDC. OBSERVED RESULT At 125% client monitor scaling, the 1280x800 host screen is rendered as 800x500. At 150% client monitor scaling, the 1280x800 host screen is rendered as 960x600. EXPECTED RESULT The host screen should be rendered as 1280x800. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Remmina, which I understand uses the same libVNCClient backend, has the 'opposite' problem - at 150% scaling, the 1280x800 host screen is rendered as 1920x1200. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 433205] [Wayland] VNC cursor stuck until click
https://bugs.kde.org/show_bug.cgi?id=433205 David Warner changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from David Warner --- I'm not sure when this was fixed, but it's no longer happening in KRDC 23.08.1 under KDE 5.27.9. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 453534] kcalc process always takes nearly 100% of a CPU thread when it's running
https://bugs.kde.org/show_bug.cgi?id=453534 --- Comment #13 from David Warner --- I'm not seeing this on a fresh Fedora 38 install with KCalc 23.04.0 (Plasma 5.27.4, KDE Frameworks 5.105.0, Qt 5.15.9, X11), though I'm sure it was still happening on my previous Fedora 37 install with the same versions. I'm confused, but happy if it's fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461032] With 150% scale, when maximising a window, kwin_x11 fails to redraw the window content
https://bugs.kde.org/show_bug.cgi?id=461032 --- Comment #12 from David Warner --- @San Does your package manager let you downgrade KWin to 5.26.1? In Fedora I ran `dnf install kwin-5.26.1-1.fc36.x86_64` and things seemed to work. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 460344] [X11] Drag & drop crashes Wine apps (foobar2000, Mp3tag, etc.)
https://bugs.kde.org/show_bug.cgi?id=460344 David Warner changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from David Warner --- Sorry, spoke too soon - it's still occurring. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 460344] [X11] Drag & drop crashes Wine apps (foobar2000, Mp3tag, etc.)
https://bugs.kde.org/show_bug.cgi?id=460344 David Warner changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from David Warner --- This seems to be fixed in 22.08.2. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461032] With 150% scale, when maximising a window, kwin_x11 fails to redraw the window content
https://bugs.kde.org/show_bug.cgi?id=461032 --- Comment #7 from David Warner --- (In reply to kevinfocke1 from comment #6) > (In reply to David Warner from comment #5) > > Thanks for the quick fix. Will this be in 5.26.3 or is there a chance it > > will be pushed sooner? > > As a hint, changing the scaling to 143.75 % or 156.25 % is a workaround I am > using. Maybe that is close enough for you as well. Thanks for the suggestion. ZaWertun's COPR for Fedora now includes this patch in kwin 5.26.2.1-2. I also found no issues in downgrading only kwin to 5.26.1. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4 in Krita 4.0 Beta
https://bugs.kde.org/show_bug.cgi?id=388985 --- Comment #8 from David Warner <blen...@gmail.com> --- Sadly no, I'm sorry I didnt think to save it. David Sent from my T-Mobile 4G LTE Device Original message From: Alvin Wong <bugzilla_nore...@kde.org> Date: 1/15/18 8:42 AM (GMT-05:00) To: blen...@gmail.com Subject: [krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4 in Krita 4.0 Beta https://bugs.kde.org/show_bug.cgi?id=388985 --- Comment #7 from Alvin Wong <alvinhoc...@gmail.com> --- Glad you've made it works now though I have no idea what was the cause at all. Do you happen to still have a backup of your old kritarc file? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4 in Krita 4.0 Beta
https://bugs.kde.org/show_bug.cgi?id=388985 --- Comment #6 from David Warner <blen...@gmail.com> --- Greetings once more Alvin, I report success! Deleting the AppData and rc files in my AppData\Local then reloading the 4.0 Beta 1 (Decided to skip the nightly build) worked well!!! Very Happy, David W. Sent from Mail for Windows 10 From: David Warner Sent: Monday, January 15, 2018 8:22 AM To: bug-cont...@kde.org Subject: RE: [krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4inKrita 4.0 Beta No, it did not work and I tried both the exe and the portable zip Sent from Mail for Windows 10 From: Alvin Wong Sent: Monday, January 15, 2018 8:21 AM To: blen...@gmail.com Subject: [krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4 inKrita 4.0 Beta https://bugs.kde.org/show_bug.cgi?id=388985 Alvin Wong <alvinhoc...@gmail.com> changed: What |Removed |Added Version|4.0.0-beta.1 |git master Platform|Other |MS Windows --- Comment #3 from Alvin Wong <alvinhoc...@gmail.com> --- It would be very weird for it to work on 3.3.3 but not on the 4.0 nightly. Does it work on 4.0 beta 1? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4 in Krita 4.0 Beta
https://bugs.kde.org/show_bug.cgi?id=388985 --- Comment #5 from David Warner <blen...@gmail.com> --- No, it did not work and I tried both the exe and the portable zip Sent from Mail for Windows 10 From: Alvin Wong Sent: Monday, January 15, 2018 8:21 AM To: blen...@gmail.com Subject: [krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4 inKrita 4.0 Beta https://bugs.kde.org/show_bug.cgi?id=388985 Alvin Wong <alvinhoc...@gmail.com> changed: What|Removed |Added Version|4.0.0-beta.1|git master Platform|Other |MS Windows --- Comment #3 from Alvin Wong <alvinhoc...@gmail.com> --- It would be very weird for it to work on 3.3.3 but not on the 4.0 nightly. Does it work on 4.0 beta 1? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4 in Krita 4.0 Beta
https://bugs.kde.org/show_bug.cgi?id=388985 --- Comment #4 from David Warner <blen...@gmail.com> --- BTW also deleting the rc files that reside in AppData as well Sent from Mail for Windows 10 From: David Warner Sent: Monday, January 15, 2018 8:17 AM To: bug-cont...@kde.org Subject: RE: [krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4inKrita 4.0 Beta I did Alvin, I even restarted my SP4 a number of times between settings. I eventually reinstalled 3.3.3 and all was well again. I am in the process of uninstalling Krita and deleting my User\AppData for Krita. I will do a restart and instal a fresh download of 4.0 Build 36. Best regards, David Warner Sent from Mail for Windows 10 From: Alvin Wong Sent: Monday, January 15, 2018 7:30 AM To: blen...@gmail.com Subject: [krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4 inKrita 4.0 Beta https://bugs.kde.org/show_bug.cgi?id=388985 Alvin Wong <alvinhoc...@gmail.com> changed: What |Removed |Added CC| |alvinhoc...@gmail.com --- Comment #1 from Alvin Wong <alvinhoc...@gmail.com> --- Have you restarted Krita after switching to the Windows Ink option? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4 in Krita 4.0 Beta
https://bugs.kde.org/show_bug.cgi?id=388985 --- Comment #2 from David Warner <blen...@gmail.com> --- I did Alvin, I even restarted my SP4 a number of times between settings. I eventually reinstalled 3.3.3 and all was well again. I am in the process of uninstalling Krita and deleting my User\AppData for Krita. I will do a restart and instal a fresh download of 4.0 Build 36. Best regards, David Warner Sent from Mail for Windows 10 From: Alvin Wong Sent: Monday, January 15, 2018 7:30 AM To: blen...@gmail.com Subject: [krita] [Bug 388985] Pen Pressure not detected on Surface Pro 4 inKrita 4.0 Beta https://bugs.kde.org/show_bug.cgi?id=388985 Alvin Wong <alvinhoc...@gmail.com> changed: What|Removed |Added CC||alvinhoc...@gmail.com --- Comment #1 from Alvin Wong <alvinhoc...@gmail.com> --- Have you restarted Krita after switching to the Windows Ink option? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388985] New: Pen Pressure not detected on Surface Pro 4 in Krita 4.0 Beta
https://bugs.kde.org/show_bug.cgi?id=388985 Bug ID: 388985 Summary: Pen Pressure not detected on Surface Pro 4 in Krita 4.0 Beta Product: krita Version: 4.0.0-beta.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: blen...@gmail.com Target Milestone: --- I installed Krita 4, build 36 on my Surface Pro 4. So far I have no pressure variance with my pen. I have tried both the Win Tab and Windows Ink base setting in Krita with no success. All other apps like Sketchbook, Leonardo, and Ink work fine as did Krita 3.3.2 and 3.3.3 -- You are receiving this mail because: You are watching all bug changes.
