[kwin] [Bug 478496] With NVIDIA GPU, kwin_wayland crashes upon start when `XwaylandClientsScale=false` in set in kdeglobals
https://bugs.kde.org/show_bug.cgi?id=478496 --- Comment #4 from Xu Zhao --- (In reply to Nate Graham from comment #3) > Ah, I'm not using an NVIDIA GPU. That could indeed be related. Re-opening. > > Are you able to test the Plasma 6 beta release? I just tried Plasma 6. Plasma 6 does not have this issue (I tried 8 reboots or so). I guess Plasma6 has fixed this issue, so I am okay closing it if we don't plan a backward fix on 5.27.9. However sidenote that there is pretty bad flickering issue across the plasma desktop/wayland applications/X11 applications on NVIDIA card (suspect duplicate of https://bugs.kde.org/show_bug.cgi?id=478563). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478496] kwin_wayland crashes upon start when KSCreen `XwaylandClientsScale=false` in kdeglobals
https://bugs.kde.org/show_bug.cgi?id=478496 --- Comment #2 from Xu Zhao --- (In reply to Nate Graham from comment #1) > I haven't been able to reproduce this on Fedora 39 with Plasma 6 stuff built > on top of it after 3 reboots. So maybe it's already fixed in Plasma 6. Let's > close it for now until we get any reports of it from people on Plasma 6. > Thanks anyway for reporting it! Plasma6 hasn't landed on tumbleweed repo, so I cannot test it. BTW, do you use NVIDIA GPU? This seems to be only reproducible on NVIDIA GPU. I am using NVIDIA Driver version 545.29.02. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478496] kwin_wayland crashes upon start when KSCreen `XwaylandClientsScale=false` in kdeglobals
https://bugs.kde.org/show_bug.cgi?id=478496 Xu Zhao changed: What|Removed |Added Component|general |wayland-generic -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478496] kwin_wayland crashes upon start when KSCreen `XwaylandClientsScale=false` in kdeglobals
https://bugs.kde.org/show_bug.cgi?id=478496 Xu Zhao changed: What|Removed |Added Version|5.27.0 |5.27.9 Target Milestone|--- |5 Product|frameworks-kwindowsystem|kwin Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 478496] New: kwin_wayland crashes upon start when KSCreen `XwaylandClientsScale=false` in kdeglobals
https://bugs.kde.org/show_bug.cgi?id=478496 Bug ID: 478496 Summary: kwin_wayland crashes upon start when KSCreen `XwaylandClientsScale=false` in kdeglobals Classification: Frameworks and Libraries Product: frameworks-kwindowsystem Version: 5.27.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: i...@xuzhao.net Target Milestone: --- SUMMARY Upon system start, kwin_wayland crashes with the following stacktrace: ``` Nov 27 22:33:54 arch-desktop systemd-coredump[1460]: [?] Process 1202 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 1202: #0 0x7ffb2e4ac83c n/a (libc.so.6 + 0x8e83c) #1 0x7ffb2e45c668 raise (libc.so.6 + 0x3e668) #2 0x7ffb2eb8 abort (libc.so.6 + 0x264b8) #3 0x7ffb3058afee n/a (libepoxy.so.0 + 0xbbfee) #4 0x7ffb3058e9d2 n/a (libepoxy.so.0 + 0xbf9d2) #5 0x7ffb31030d97 n/a (libkwin.so.5 + 0x430d97) #6 0x7ffb31032bc9 _ZN4KWin9EglDmabufD1Ev (libkwin.so.5 +> #7 0x7ffb31034121 _ZN4KWin18AbstractEglBackendD2Ev (libk> #8 0x7ffb30f75f7d n/a (libkwin.so.5 + 0x375f7d) #9 0x7ffb30dc058b _ZN4KWin10Compositor4stopEv (libkwin.s> #10 0x7ffb30db9108 _ZN4KWin10Compositor12reinitializeEv (> #11 0x7ffb2f4d1097 n/a (libQt5Core.so.5 + 0x2d1097) #12 0x7ffb30f11dba _ZN4KWin9Workspace15slotReconfigureEv > #13 0x7ffb2f4d1097 n/a (libQt5Core.so.5 + 0x2d1097) #14 0x7ffb2f4d2bcf _ZN6QTimer7timeoutENS_14QPrivateSignal> #15 0x7ffb2f4c3b4e _ZN7QObject5eventEP6QEvent (libQt5Core> #16 0x7ffb2eb788ff _ZN19QApplicationPrivate13notify_helpe> #17 0x7ffb2f49c168 _ZN16QCoreApplication15notifyInternal2> #18 0x7ffb2f4ea7cb _ZN14QTimerInfoList14activateTimersEv > #19 0x7ffb2f4eacb1 _ZN20QEventDispatcherUNIX13processEven> #20 0x5557facd7ce2 n/a (kwin_wayland + 0x137ce2) #21 0x7ffb2f49ae74 _ZN10QEventLoop4execE6QFlagsINS_17Proc> #22 0x7ffb2f49c313 _ZN16QCoreApplication4execEv (libQt5Co> #23 0x5557fabf340b n/a (kwin_wayland + 0x5340b) #24 0x7ffb2e445cd0 n/a (libc.so.6 + 0x27cd0) #25 0x7ffb2e445d8a __libc_start_main (libc.so.6 + 0x27d8a) #26 0x5557fabf5015 n/a (kwin_wayland + 0x55015) Stack trace of thread 1215: #0 0x7ffb2e520f6f __poll (libc.so.6 + 0x102f6f) #1 0x7ffb2d16c276 n/a (libglib-2.0.so.0 + 0xb8276) #2 0x7ffb2d10c162 g_main_context_iteration (libglib-2.0.> #3 0x7ffb2f4eaf7c _ZN20QEventDispatcherGlib13processEven> #4 0x7ffb2f49ae74 _ZN10QEventLoop4execE6QFlagsINS_17Proc> #5 0x7ffb2f2f74f6 _ZN7QThread4execEv (libQt5Core.so.5 + > #6 0x7ffb31354a9a n/a (libQt5DBus.so.5 + 0x18a9a) #7 0x7ffb2f2f371a n/a (libQt5Core.so.5 + 0xf371a) #8 0x7ffb2e4aa9eb n/a (libc.so.6 + 0x8c9eb) #9
[plasmashell] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #52 from Xu Zhao --- (In reply to Tony from comment #51) > (In reply to Zamundaaa from comment #49) > > There have been a few related changes in KWin, and while plasmashell still > > crashes, neither turning off the output nor having Screen Energy Savings > > kills the session for me with git master. Can you check again? > > Can confirm turning the monitor off and on does not crash the session on > master, it does F up plasmashell badly. Can I have the backtrace of plasmashell? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #47 from Xu Zhao --- Just wondering is there any update to this issue, given its VHI level? -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 440054] KDE Print Manager doesn't respect "US Letter" paper size
https://bugs.kde.org/show_bug.cgi?id=440054 Xu Zhao changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Xu Zhao --- After some analysis, this is identified as a QT bug: https://bugreports.qt.io/browse/QTBUG-95469. Therefore, I am closing this right now. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 440054] KDE Print Manager doesn't respect "US Letter" paper size
https://bugs.kde.org/show_bug.cgi?id=440054 --- Comment #1 from Xu Zhao --- More context information: My printer model is: EPSON Inkjet ET-2760 The driver version is epson-inkjet-printer-escpr 1.7.8-1.5. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 440054] New: KDE Print Manager doesn't respect "US Letter" paper size
https://bugs.kde.org/show_bug.cgi?id=440054 Bug ID: 440054 Summary: KDE Print Manager doesn't respect "US Letter" paper size Product: print-manager Version: 21.04.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: i...@xuzhao.net Target Milestone: --- SUMMARY KDE Print Manager doesn't respect the paper size to be "US Letter" in the configuration and still uses the default A4 size. The region and format set in KDE is "Canada - Canadian English (en_CA)", but I don't find anywhere to set the default paper size in the "Formats - System Settings". The only place to set paper size is in the KDE printer settings dialog. STEPS TO REPRODUCE 1. Set paper size to "US Letter" in the KDE printer setting 2. Print a PDF document in Okular OBSERVED RESULT The CUPS daemon prints the following log: D [19/Jul/2021:22:36:27 -0400] [Job 79] argv[5]="media=A4 sides=one-sided number-up=1 number-up-layout=lrtb job-billing= job-uuid=urn:uuid:e21dd7c7-e0c3-361f-7c2e-18a71efa315a job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1626748580 time-at-processing=1626748587 document-name-supplied=0242c61005404 Duplex=None PageSize=A4" EXPECTED RESULT The CUPS should respect the paper size set to "US Letter". SOFTWARE/OS VERSIONS openSUSE Tumbleweed 20210716 Linux: 5.13.1 (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 --- Comment #39 from Xu Zhao --- (In reply to Nate Graham from comment #37) > Is this affected by the fix for Bug 438789? No, I tested with patched kwin, and the problem still exists. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420160] Session crashes when monitor goes into standby
https://bugs.kde.org/show_bug.cgi?id=420160 Xu Zhao changed: What|Removed |Added CC||i...@xuzhao.net --- Comment #36 from Xu Zhao --- Can confirm this issue on openSUSE Tumbleweed 20210701, KDE Plasma 5.22.2, KDE Frameworks 5.83.0 on Wayland, AMD 6800 XT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419937] Krunner does not get focus when the "Focus stealing prevention" is set to "Extreme"
https://bugs.kde.org/show_bug.cgi?id=419937 Xu Zhao changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Xu Zhao --- (In reply to Patrick Silva from comment #3) > Tested with Plasma 5.22 on Arch Linux. > krunner is focused, but konsole launched with it opens in background. Thanks for the test. I have tried again in 5.22, and the behavior is the same as yours. The original bug has disappeared. I think now this is the correct behavior (new application open in background) because the option specifies to prevent the new application from stealing the focus. Therefore, I am closing this bug report. Please feel free to reopen the bug if you disagree. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 370726] Text selection tool highlight unintelligible
https://bugs.kde.org/show_bug.cgi?id=370726 --- Comment #5 from Xu Zhao --- I submitted a tentative merge request to address this issue: https://invent.kde.org/graphics/okular/-/merge_requests/440 Maybe someone here could help review it? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 436223] Krunner incorrectly sets "GDK_SCALE" and "GDK_DPI_SCALE" under wayland and HiDPI
https://bugs.kde.org/show_bug.cgi?id=436223 --- Comment #2 from Xu Zhao --- This is because when I start my computer, I first login X11 session. After I logout X session and login Wayland session, this bug will appear, because in the wayland session, krunner still uses startplasma-x11.cpp to start an application (not startplasma-wayland.cpp). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 436223] Krunner incorrectly sets "GDK_SCALE" and "GDK_DPI_SCALE" under wayland and HiDPI
https://bugs.kde.org/show_bug.cgi?id=436223 --- Comment #1 from Xu Zhao --- Created attachment 137931 --> https://bugs.kde.org/attachment.cgi?id=137931=edit Result of incorrect scaling -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 436223] New: Krunner incorrectly sets "GDK_SCALE" and "GDK_DPI_SCALE" under wayland and HiDPI
https://bugs.kde.org/show_bug.cgi?id=436223 Bug ID: 436223 Summary: Krunner incorrectly sets "GDK_SCALE" and "GDK_DPI_SCALE" under wayland and HiDPI Product: krunner Version: 5.21.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: i...@xuzhao.net CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Krunner doesn't scale correctly for Firefox and other GTK applications. Qt applications work well. I am using KDE with Wayland, 4K resolution with 2x scale factor. The application scales correctly when started from commandline or plasma application launcher, but it starts with incorrect scale with krunner. STEPS TO REPRODUCE 1. Start krunner and type "firefox" 2. Start firefox 3. The result application window text looks small (doesn't scale correctly) OBSERVED RESULT The result application window text looks small (doesn't scale correctly) EXPECTED RESULT The result application window should scale correctly. SOFTWARE/OS VERSIONS openSUSE Tumbleweed 20210423 Linux: 5.11.15 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Inspecting into the process's environment variable, I find "GDK_SCALE=2" and "GDK_DPI_SCALE=0.5", which leads to incorrect scaling. The process UI scale correctly if started from commandline or from Plasma Application Launcher. And it doesnot have the above two environment variables set when I start it from there. Therefore, it must be krunner incorrectly set the above two environment variables somewhere. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431525] KScreenlocker crops screen on hidpi after monitor connection
https://bugs.kde.org/show_bug.cgi?id=431525 Xu Zhao changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #4 from Xu Zhao --- The problem disappears after I switch from HDMI to DisplayPort. Closed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431525] KScreenlocker crops screen on hidpi after monitor connection
https://bugs.kde.org/show_bug.cgi?id=431525 --- Comment #2 from Xu Zhao --- (In reply to Nate Graham from comment #1) > Seems like a graphics issue. Wayland or X11? Thanks for the reply! I am using X11. I have tried adding 90-monitor.conf in /etc/X11/xorg.conf.d: Section "Monitor" Identifier "" DisplaySize 345 194 # in millimeters EndSection But it doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 431525] New: KScreenlocker crops screen on hidpi after monitor connection
https://bugs.kde.org/show_bug.cgi?id=431525 Bug ID: 431525 Summary: KScreenlocker crops screen on hidpi after monitor connection Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: i...@xuzhao.net CC: bhus...@gmail.com Target Milestone: --- Created attachment 134798 --> https://bugs.kde.org/attachment.cgi?id=134798=edit The monitor shows only the top left quarter of the entire lock screen. SUMMARY I am using kscreenlocker 5.20.5 on 4K monitor (DELL U2720Q). Scaling Factor is 2.0. Kernel 5.10.5, Display Card Radeon 6800XT, Driver amdgpu. STEPS TO REPRODUCE 1. Lock the screen 2. Disconnect monitor 3. Reconnect monitor OBSERVED RESULT The monitor only shows top left quarter of the screen. The rest part is chopped. EXPECTED RESULT Show the entire screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.20.5 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 openSUSE Tumbleweed 20210105 ADDITIONAL INFORMATION After pressing Ctrl-Alt-F1 to switch to TTY, then press Ctrl-Alt-F7 to switch back to lockscreen, the problem is fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419937] Krunner does not get focus when the "Focus stealing prevention" is set to "Extreme"
https://bugs.kde.org/show_bug.cgi?id=419937 --- Comment #2 from Xu Zhao --- Can anyone please check if they could reproduce this bug? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 370726] Text selection tool highlight unintelligible
https://bugs.kde.org/show_bug.cgi?id=370726 --- Comment #3 from Xu Zhao --- The problem persists on Okular 1.9.3. Any progress on this issue? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 416319] forceActiveWindow() function raises window but may not give it focus.
https://bugs.kde.org/show_bug.cgi?id=416319 Xu Zhao changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Xu Zhao --- Superseded by bug 419937. *** This bug has been marked as a duplicate of bug 419937 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419937] New: Krunner does not get focus when the "Focus stealing prevention" is set to "Extreme"
https://bugs.kde.org/show_bug.cgi?id=419937 Bug ID: 419937 Summary: Krunner does not get focus when the "Focus stealing prevention" is set to "Extreme" Product: kwin Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: i...@xuzhao.net Target Milestone: --- SUMMARY KRunner or the window launched by krunner does not correctly get focus when the "Focus Stealing Prevention" setting is set to "Extreme" or "High" STEPS TO REPRODUCE 1. Open Window Focus Behavior, set "Focus Stealing Prevention" to "Extreme". Click Apply. (Now the focus is on the "Window Focus Behavior" window) 2. Use Alt-F2 to call out krunner 3. Krunner doesn't get focus. If you start an application using krunner (e.g., konsole), the new application window doesn't get focus, either. OBSERVED RESULT KRunner, or the application started by the krunner should get the focus. EXPECTED RESULT The focus remains to be on the old application. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20200408 KDE Plasma Version: Plasma 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Not sure whether this is desired behavior or a bug. Please let me know what you think. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419937] Krunner does not get focus when the "Focus stealing prevention" is set to "Extreme"
https://bugs.kde.org/show_bug.cgi?id=419937 --- Comment #1 from Xu Zhao --- *** Bug 416319 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419080] Window doesn't have correct size when using themes with Aurorae theme engine
https://bugs.kde.org/show_bug.cgi?id=419080 --- Comment #3 from Xu Zhao --- Created attachment 126932 --> https://bugs.kde.org/attachment.cgi?id=126932=edit The screenshot when the compositing is turned off. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419080] Window doesn't have correct size when using themes with Aurorae theme engine
https://bugs.kde.org/show_bug.cgi?id=419080 --- Comment #2 from Xu Zhao --- (In reply to David Edmundson from comment #1) > >This bug does not exist when using Intel/Nouveau drivers. > > That sounds unlikely. > > Is it the same machine? > Does it affect every window when the bug exhibits itself? > For the whole session? Yes, it affects every window for the whole session. I can reproduce the bug on at least three machines using Nvidia display driver. However, they are all in openSUSE Tumbleweed. > > >Window Decoration Theme: McMojave-Light, or Breezemite > > And all Aurorae themes are affected? I have tested a few Aurorae themes. It seems all of them are affected. - Breezemite - Breezemite_dark - McMojave - McMojave-light - Qogir-light - Sweet-Dark > > Does toggling compositing (alt+shift+f12) make a difference? The bug persists. You can find the screenshot after toggling the compositing in the new attachment. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 419080] New: Window doesn't have correct size when using themes with Aurorae theme engine together with Nvidia driver
https://bugs.kde.org/show_bug.cgi?id=419080 Bug ID: 419080 Summary: Window doesn't have correct size when using themes with Aurorae theme engine together with Nvidia driver Product: frameworks-kwindowsystem Version: 5.67.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: i...@xuzhao.net Target Milestone: --- Created attachment 126931 --> https://bugs.kde.org/attachment.cgi?id=126931=edit The window overflows the title bar SUMMARY The window overflows when using Aurorae theme engine together with Nvidia proprietary display driver. STEPS TO REPRODUCE 1. Change the window decoration theme to McMojave Light 2. Start any application OBSERVED RESULT The window overflows the title bar EXPECTED RESULT The window should be within the title bar SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20200318 KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Display Driver: Nvidia 440.64 Window Decoration Theme: McMojave-Light, or Breezemite ADDITIONAL INFORMATION This bug does not exist when using Intel/Nouveau drivers. See the screenshot for details. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 416319] New: forceActiveWindow() function raises window but may not give it focus.
https://bugs.kde.org/show_bug.cgi?id=416319 Bug ID: 416319 Summary: forceActiveWindow() function raises window but may not give it focus. Product: frameworks-kwindowsystem Version: 5.65.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: i...@xuzhao.net Target Milestone: --- Created attachment 125159 --> https://bugs.kde.org/attachment.cgi?id=125159=edit The screenshot showing the specified window is not getting focus SUMMARY I discover this bug when developing a simple KRunner extension that switches windows on Plasma. In this extension, I use forceActiveWindow(Wid w) call to raise and focus a window, see https://github.com/xuzhao9/krunner-switcher/blob/master/src/switcher.cpp#L135 This function call successfully returns, the window specified in argument always raises, but may not get focus (non-deterministic). STEPS TO REPRODUCE 1. Install the krunner-switcher plugin of KRunner 2. Use KRunner to activate a window OBSERVED RESULT The specified window is activated and gets focus. EXPECTED RESULT The specified window is raised to the front, but may not get focus (the old window keeps focus). If you call activeWindow() at this moment, it returns the new window, i.e., the one specified in the argument of forceActiveWindow(). SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20200113 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION This bug is non-deterministic. You may need to try it multiple times to reproduce it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 370726] Text selection tool highlight unintelligible
https://bugs.kde.org/show_bug.cgi?id=370726 Xu Zhao changed: What|Removed |Added CC||i...@xuzhao.net --- Comment #2 from Xu Zhao --- Can confirm this on Okular 1.9.0. Any progress on this bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410827] Wayland clients are not exposed to scripting api
https://bugs.kde.org/show_bug.cgi?id=410827 --- Comment #3 from Xu Zhao --- (In reply to Vlad Zahorodnii from comment #2) > > Wayland windows are currently excluded from scripting due to security > > constraints. > > Um, actually that's no longer the case. Wayland clients are exposed to > scripts. Then why the KWin script doesn't return the correct result? It should. Is it working-in-progress to support KWin scripts on Wayland? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 376658] Customized tabbox does not work and makes kwin stuck and slow
https://bugs.kde.org/show_bug.cgi?id=376658 Xu Zhao changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Xu Zhao --- Fixed on Plasma 5.16.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410827] New: Neither KWinscript nor wmctrl show all the windows on Wayland
https://bugs.kde.org/show_bug.cgi?id=410827
Bug ID: 410827
Summary: Neither KWinscript nor wmctrl show all the windows on
Wayland
Product: kwin
Version: 5.16.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: platform-wayland
Assignee: kwin-bugs-n...@kde.org
Reporter: i...@xuzhao.net
Target Milestone: ---
Created attachment 122072
--> https://bugs.kde.org/attachment.cgi?id=122072=edit
Only one window being recognized by the kwinscript
SUMMARY
Neither KWinscript nor wmctrl correctly show all the open windows on KWin
Wayland.
STEPS TO REPRODUCE
1. Open a few applications in KWin 5.16.4: Firefox, Emacs, Alacritty, Okular
2. Run "wmctrl -l" or the following KWinscript:
var clist = workspace.clientList();
print(clist.length);
for(var i = 0; i < clist.length; i ++) {
print(clist[i]);
}
3. Should print all the windows, but only one of them got printed. See
screenshot: https://ibb.co/YpFF7xG
OBSERVED RESULT
Only one window got printed
EXPECTED RESULT
All the windows are printed with their names.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Linux 5.2.0 , openSUSE Tumbleweed latest
(available in About System)
KDE Plasma Version: Plasma 5.16.4
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0
ADDITIONAL INFORMATION
See the attachment
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 392677] "Pointer motion confined to the current window. To release pointer hold Escape for 3 seconds." notification upon trying to move XWayland app window
https://bugs.kde.org/show_bug.cgi?id=392677 --- Comment #4 from Xu Zhao <i...@xuzhao.net> --- (In reply to Martin Flöser from comment #3) > (In reply to Xu Zhao from comment #2) > > Is there a way to disable the notification in kwin? > > No Here is a workaround that I found today. Change the /usr/share/kwin/onscreennotification/plasma/main.qml: visible: osd.visible to: visible: osd.invisible can hide this and all osd notifications. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392677] "Pointer motion confined to the current window. To release pointer hold Escape for 3 seconds." notification upon trying to move XWayland app window
https://bugs.kde.org/show_bug.cgi?id=392677 Xu Zhao <i...@xuzhao.net> changed: What|Removed |Added CC||i...@xuzhao.net --- Comment #2 from Xu Zhao <i...@xuzhao.net> --- Is there a way to disable the notification in kwin? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394153] New: Tabbox incorrect positioning under wayland
https://bugs.kde.org/show_bug.cgi?id=394153 Bug ID: 394153 Summary: Tabbox incorrect positioning under wayland Product: kwin Version: 5.12.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: i...@xuzhao.net Target Milestone: --- Created attachment 112592 --> https://bugs.kde.org/attachment.cgi?id=112592=edit Incorrect positioning of tabbox using Wayland The tabbox always appears on the top-left corner of the screen. It should appear in the center. I am using the large icons tabbox theme. My environment: openSUSE Tumbleweed 20180502 kwin: 5.12.4-1.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379868] Window decorations KCM shows apply/discard dialog even when no change is done
https://bugs.kde.org/show_bug.cgi?id=379868 --- Comment #6 from Xu Zhao <i...@xuzhao.net> --- Here is the replicated bug report: https://bugs.kde.org/show_bug.cgi?id=381806 I believe this is because of kde is fetching the themes from the network, since I saw a flash in the kcm window then the "Apply" button becomes clickable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379868] Window decorations KCM shows apply/discard dialog even when no change is done
https://bugs.kde.org/show_bug.cgi?id=379868 Xu Zhao <i...@xuzhao.net> changed: What|Removed |Added CC||i...@xuzhao.net --- Comment #4 from Xu Zhao <i...@xuzhao.net> --- Reproducible on openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381806] New: Window Decorations KCM pop up even there is no change
https://bugs.kde.org/show_bug.cgi?id=381806 Bug ID: 381806 Summary: Window Decorations KCM pop up even there is no change Product: kwin Version: 5.10.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: i...@xuzhao.net Target Milestone: --- Created attachment 106375 --> https://bugs.kde.org/attachment.cgi?id=106375=edit Popup window even nothing is changed in Window Decoration How to reproduce it: 1. Open system settings -> Application Style 2. Open tab: Window Decorations 3. Do nothing, wait ~1sec 4. Click "Widget Style" tab 5. Popup window appear: "The settings of current module have changed. Do you want to apply the changes or discard them?" Desired behavior: There is no popup window. This is because I am not changing the window decoration, it does not need to inform me to apply/discard changes, since there is no change at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377670] Background shadow remains after quick tile window to the right
https://bugs.kde.org/show_bug.cgi?id=377670 --- Comment #14 from Xu Zhao <i...@xuzhao.net> --- (In reply to Martin Gräßlin from comment #13) > > The problem remains in kwin 5.9.4, in which the fix should be contained. > > The patch got only pushed to master branch. It is not in a bug fix branch. I am sorry I don't get it... From Github page: https://github.com/KDE/kwin/compare/v5.9.4...master, commit 948ff63 should have been included in the kwin 5.9.4. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377670] Background shadow remains after quick tile window to the right
https://bugs.kde.org/show_bug.cgi?id=377670 --- Comment #12 from Xu Zhao <i...@xuzhao.net> --- (In reply to Marco Martin from comment #11) > Git commit 948ff63d65d2e645eeb023387600bee52ef4d684 by Marco Martin. > Committed on 17/03/2017 at 16:47. > Pushed by mart into branch 'master'. > > when the padding aroun the window changes, update > > Summary: > update m_visibleRectBeforeGeometryUpdate when the padding > change signal gets emitted: aurorae updates its shadow > and postentially shadow size asynchronously after repainting. > that would make the first addRepaintDuringGeometryUpdates > when the winow is moved *for the first time* have a wrong > m_visibleRectBeforeGeometryUpdate that doesn't take into > account the shadow, leaving some leftover shadow on screen > > Test Plan: > shadow leftover not reproducible anymore with maui's kwinrc > replaces D4989 > tested both on master and together D4990, which should go in as well > > Reviewers: #plasma, davidedmundson, graesslin > > Reviewed By: #plasma, graesslin > > Subscribers: plasma-devel, kwin, #kwin > > Tags: #kwin > > Differential Revision: https://phabricator.kde.org/D5078 > > M +4-0abstract_client.cpp > > https://commits.kde.org/kwin/948ff63d65d2e645eeb023387600bee52ef4d684 The problem remains in kwin 5.9.4, in which the fix should be contained. See the screenshot:http://imgur.com/a/zhTJT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377757] KWin window decoration incorrect rendering
https://bugs.kde.org/show_bug.cgi?id=377757 --- Comment #2 from Xu Zhao <i...@xuzhao.net> --- Created attachment 104623 --> https://bugs.kde.org/attachment.cgi?id=104623=edit Another screenshot This may related to window rendering, not only decorations. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377757] KWin window decoration incorrect rendering
https://bugs.kde.org/show_bug.cgi?id=377757 --- Comment #1 from Xu Zhao <i...@xuzhao.net> --- This maybe related to https://bugs.kde.org/show_bug.cgi?id=375369 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377757] New: KWin window decoration incorrect rendering
https://bugs.kde.org/show_bug.cgi?id=377757 Bug ID: 377757 Summary: KWin window decoration incorrect rendering Product: kwin Version: 5.9.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: i...@xuzhao.net Target Milestone: --- Created attachment 104622 --> https://bugs.kde.org/attachment.cgi?id=104622=edit Incorrectly rendering the window decoration I am using Breezemite decoration theme on KWin 5.9.3. Breezemite is a theme powered by Aurorae engine. Today I meet this problem that KWin incorrectly renders the window decoration, as in screenshot. Unfortunately, this bug happens non-deterministically and I could not find a way to deterministically reproduce it. My OS: openSUSE Tumbleweed. KWin version: 5.9.3 This is my result of running `qdbus org.kde.KWin /KWin supportInformation`:https://paste.kde.org/pqielzg2x This is content of my kwinrc: https://paste.kde.org/par8izyqh -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377670] Background shadow remains after quick tile window to the right
https://bugs.kde.org/show_bug.cgi?id=377670 --- Comment #8 from Xu Zhao <i...@xuzhao.net> --- (In reply to Martin Gräßlin from comment #6) > Could you try whether the steps to reproduce also work with the default > window decoration breeze? Sorry, Breeze decoration do have the window background shadow and it works fine. However, Breezemite window decoration will have the problem in my screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377670] Background shadow remains after quick tile window to the right
https://bugs.kde.org/show_bug.cgi?id=377670 --- Comment #7 from Xu Zhao <i...@xuzhao.net> --- (In reply to Martin Gräßlin from comment #6) > Could you try whether the steps to reproduce also work with the default > window decoration breeze? Yes I can. Breeze does not have this problem (but breeze seems don't have window background shadow either) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377670] Background shadow remains after quick tile window to the right
https://bugs.kde.org/show_bug.cgi?id=377670 --- Comment #3 from Xu Zhao <i...@xuzhao.net> --- Hello, here is my result of running `qdbus org.kde.KWin /KWin supportInformation` https://paste.kde.org/pzugou75m Below is my kwinrc: https://paste.kde.org/pkaj3tpiu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377670] New: Background shadow remains after quick tile window to the right
https://bugs.kde.org/show_bug.cgi?id=377670 Bug ID: 377670 Summary: Background shadow remains after quick tile window to the right Product: kwin Version: 5.9.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: i...@xuzhao.net Target Milestone: --- Created attachment 104591 --> https://bugs.kde.org/attachment.cgi?id=104591=edit Screenshot Steps to reproduce: 1. Open a window 2. Press shortcut to quick tile the window to the right 3. Show symptom: window shadow remains in the previous position. See screenshot. My OS is openSUSE Tumbleweed 20170314, KWin 5.9.3. I am using window decoration theme Breezemite. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376658] Customized tabbox does not work and makes kwin stuck and slow
https://bugs.kde.org/show_bug.cgi?id=376658 --- Comment #1 from Xu Zhao <i...@xuzhao.net> --- This bug seems nondeterministic. I tried 10 times and can reproduce it 8 times. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376658] New: Customized tabbox does not work and makes kwin stuck and slow
https://bugs.kde.org/show_bug.cgi?id=376658 Bug ID: 376658 Summary: Customized tabbox does not work and makes kwin stuck and slow Product: kwin Version: 5.9.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: i...@xuzhao.net Target Milestone: --- I am trying to customize the Large Icons theme for kwin tabbox. The only line I modified is add the following line into PlasmaCore.Dialog block: backgroundHints: PlasmaCore.Dialog.NoBackground Without this line, everything is good. However after having this line and restart kwin, the large icon tabbar does not work and kwin becomes very slow on my machine (i7-6700K, 16G RAM). I use openSUSE Tumbleweed any my kwin version is 5.9.1, I use kwin on X11. Here is the full main.qml file I am using for the slowed tabbox: https://pastebin.com/kdz3QisG -- You are receiving this mail because: You are watching all bug changes.
