[kwin] [Bug 420039] [XWayland]: Windows are often invisible and unusable
https://bugs.kde.org/show_bug.cgi?id=420039 Yogesh Marwaha changed: What|Removed |Added CC||yogeshm@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #27 from Yogesh Marwaha --- It didn't work with Dolphin (Konsole too) for me also. Since other applications (which I use) seem to work fine, I tried some tricks. I manually resized application window and then closed it. Again started, maximised and closed. Afterwards it functioned as intended. PS: A bit unrelated, Firefox with custom title bar cannot determine that it's maximised. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #20 from Yogesh Marwaha --- It seems to work for KDE apps(In reply to Nate Graham from comment #19) > Scratch that. It's only working for XWayland apps. Full Wayland apps are > still broken in the way described here. Is xeyes method valid to check whether an app is wayland native? If not, how can one verify that? PS: xeyes doesn't move on KDE apps and firefox (under wayland) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #17 from Yogesh Marwaha --- Just updated my (Arch Linux) installation and the bug has disappeared (at least for all the KDE/non-KDE apps I use). A big thumbs-up for everyone involved! Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.4.45-1-lts OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 409919] [Wayland] KDE application don't remember maximization state after closing and re-opening
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #15 from Yogesh Marwaha --- I tried to look for the problem and it looks like kxmlgui (or any part of KDE) is not to be blamed here. Following are the few observations (while on plasma-wayland session): - #1: Applications correctly save window size/maximized state on close, but they somehow cannot restore maximized window state #2: Vanilla Qt5 applications also fail to set maximized window state on open #3: For example, with 'qdbusviewer --platform xcb', window is maximized on open with 'qdbusviewer --platform wayland', window is not maximized on open (but still has proportions of maximized window) So, either Qt(wayland) is not setting the window state properly or there is a communication gap between KWin and Qt5 (wayland) clients. I've tried to look into the qtwayland source, but that's probably too much for me. Thanks for your time. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 --- Comment #8 from Yogesh Marwaha --- This behavior is applicable for all KDE applications I have used/tried (dolphin, konsole, ksysguard, okular, gwenview, system settings, many KDE games (not tried all of them)) under wayland. Other non-KDE applications I use seem to work fine (e.g. Firefox, Gnu Cash, FileZilla, Chromium, Android Studio). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 Yogesh Marwaha changed: What|Removed |Added Attachment #121658|0 |1 is obsolete|| --- Comment #6 from Yogesh Marwaha --- Created attachment 121663 --> https://bugs.kde.org/attachment.cgi?id=121663=edit Screenshot 3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 Yogesh Marwaha changed: What|Removed |Added Attachment #121657|0 |1 is obsolete|| --- Comment #5 from Yogesh Marwaha --- Created attachment 121662 --> https://bugs.kde.org/attachment.cgi?id=121662=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #10 from Yogesh Marwaha --- I have filed a report against dolphin (https://bugs.kde.org/show_bug.cgi?id=410061). Can you have a look at screenshot 3 and confirm whether incorrect drawing along the right edge and bottom edge of the window is a fault of KWin or not? Judging from the mouse actions on that area, it is still part of the application window. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 --- Comment #3 from Yogesh Marwaha --- Created attachment 121658 --> https://bugs.kde.org/attachment.cgi?id=121658=edit Screenshot 3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 --- Comment #1 from Yogesh Marwaha --- Created attachment 121656 --> https://bugs.kde.org/attachment.cgi?id=121656=edit Screenshot 1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 --- Comment #2 from Yogesh Marwaha --- Created attachment 121657 --> https://bugs.kde.org/attachment.cgi?id=121657=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410061] New: Dolphin fails to restore window state (on restart) to maximized when running on wayland
https://bugs.kde.org/show_bug.cgi?id=410061 Bug ID: 410061 Summary: Dolphin fails to restore window state (on restart) to maximized when running on wayland Product: dolphin Version: 19.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: yogeshm@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY Dolphin fails to restore window state (on restart) to maximized when running on wayland STEPS TO REPRODUCE 1. Maximize dophin window (Ref. screenshot 1) 2. Close it 3. Reopen dolphin (Note: Now the application seems to be opened with a size which would be if it was started maximized, but it does not actually start maximized, as is evident from titlebar buttons' state) (Ref. screenshot 2) 4. Try to maximize window by clicking on relevant button in titlebar. Window is resized in a weird way (Ref. screenshot 3). If the window is resized (dragging from edges) before maximizing, it is maximized properly. EFFECTS OF BEHAVIOR MENTIONED ABOVE 1. Since the application window is started with a size of a maximized application (while not actually maximized; evident from buttons on the titlebar), it cannot be restored to a smaller size. 2. Since, to the window manager, the window is not maximized, shown window (i) has border around it and (ii) is shown with a titlebar even if showing titlebar for maximized windows is disabled. SOFTWARE/OS/HARDWARE VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel Version: 4.19.57-1-lts OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 14.6 GiB ADDITIONAL INFORMATION This report originates from: https://bugs.kde.org/show_bug.cgi?id=409919 Another related bug report: https://bugs.kde.org/show_bug.cgi?id=391621 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #7 from Yogesh Marwaha --- All right then. Since this bug affects multiple KDE applications (tested on dolphin, konsole, ksysguard, system settings, many KDE games) and needs to be worked on each one of them separately, does this bug needs to be reported separately for all those applications? If the answer is no, can you guide how can this be done. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #4 from Yogesh Marwaha --- Created attachment 121638 --> https://bugs.kde.org/attachment.cgi?id=121638=edit Screenshot 3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #5 from Yogesh Marwaha --- I'll try to rephrase (or may be explain better) the problem being faced by OP and me. Prerequisite info: - Operating System: Arch Linux KDE Plasma Version: 5.16.3 KDE Frameworks Version: 5.59.0 Qt Version: 5.13.0 Kernel Version: 4.19.57-1-lts OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 14.6 GiB Disclaimer: -- 1. Assuming that the OP wants to restore the application window (from maximized state) not minimize it; for me minimizing works fine. 2. This only seems to happen on KDE applications under wayland. Other non-KDE applications I use seem to work fine (e.g. Firefox, Gnu Cash, FileZilla, Chromium, Android Studio) Steps to reproduce: -- 1. Maximize a KDE application (Ref. screenshot 1) 2. Close it 3. Reopen the application (Note: Now the application seems to be opened with a size which would be if it was started maximized, but it does not actually start maximized, as is evident from titlebar buttons' state) (Ref. screenshot 2) 4. Try to maximize window by clicking on relevant button in titlebar. Window is resize in a weird way. (Ref. screenshot 3) If the window is resized (dragging from edges) before maximizing, it is maximized properly. Effects of behavior mentioned above: --- 1. Since the application window is started with a size of a maximized application (while not actually maximized as per KWin), it cannot be restored to a smaller size. 2. Since KWin thinks the window is not maximized, shown windows (i) have borders around them and (ii) are shown with a titlebar even if showing titlebars for maximized applications is disabled. Possible cause of problem: - Application indeed opens its window in maximized position but either KWin does not get the message or it forgets later that the window is maximized. I hope I'm clear enough. Regards. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 --- Comment #3 from Yogesh Marwaha --- Created attachment 121637 --> https://bugs.kde.org/attachment.cgi?id=121637=edit Screenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 409919] KDE application forgot their initial size after maximizing and closing them.
https://bugs.kde.org/show_bug.cgi?id=409919 Yogesh Marwaha changed: What|Removed |Added CC||yogeshm@gmail.com --- Comment #2 from Yogesh Marwaha --- Created attachment 121636 --> https://bugs.kde.org/attachment.cgi?id=121636=edit Screenshot 1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 405558] Breeze dark plasma theme shows dialog, tooltips etc. with light background
https://bugs.kde.org/show_bug.cgi?id=405558 Yogesh Marwaha changed: What|Removed |Added Summary|Breeze dark theme shows |Breeze dark plasma theme |dialog, tooltips etc. with |shows dialog, tooltips etc. |light background|with light background -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 405558] New: Breeze dark theme shows dialog, tooltips etc. with light background
https://bugs.kde.org/show_bug.cgi?id=405558 Bug ID: 405558 Summary: Breeze dark theme shows dialog, tooltips etc. with light background Product: Breeze Version: 5.15.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: yogeshm@gmail.com Target Milestone: --- Created attachment 118856 --> https://bugs.kde.org/attachment.cgi?id=118856=edit Screenshot showing the problem SUMMARY Breeze dark theme shows dialog, tooltips etc. with light background. It was looking fine before I upgraded (in a nutshell... qt5 from 5.12.1 to 5.12.2 and plasma 5.15.2 to 5.15.3) STEPS TO REPRODUCE 1. Go to System Settings -> Workspace Theme -> Plasma Theme 2. Select Breeze Dark 3. Click on Apply 4. Open application launcher OR click on any applet which would open a dialog OR move mouse so as to show tooltip on any plasma icon/applet OBSERVED RESULT Even though dark theme was selected, background of dialog opened in Step 4 is light. EXPECTED RESULT Background should have been dark. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION I've tried clearing cache (~/.cache). I've tried other user account. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting
https://bugs.kde.org/show_bug.cgi?id=385880 Yogesh Marwaha changed: What|Removed |Added CC||yogeshm@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[rekonq] [Bug 294129] Remove "rekonq" from main window of rekonq
https://bugs.kde.org/show_bug.cgi?id=294129 --- Comment #5 from Yogesh Marwaha --- Since this feature request is irrelevant in today's context, I'm taking taking liberty to close this as "RESOLVED > WORKSFORME". Thank you. -- You are receiving this mail because: You are watching all bug changes.
[rekonq] [Bug 294129] Remove "rekonq" from main window of rekonq
https://bugs.kde.org/show_bug.cgi?id=294129 Yogesh Marwaha changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 183458] Numpad (keypad) keys not mapped correctly when setting Global Shortcuts
https://bugs.kde.org/show_bug.cgi?id=183458 Yogesh Marwaha <yogeshm@gmail.com> changed: What|Removed |Added CC||yogeshm@gmail.com -- You are receiving this mail because: You are watching all bug changes.
