[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #19 from Komorebi --- Ah, okay, got it. Changing window placement policy to "top left corner" moved my OSD (volume and brightness level popups) there, but everything else including notifications are still appear in the middle. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #17 from Komorebi --- No. I've tried to set custom location for notifications, but it takes no effect. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget pop-up and notification placement
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #15 from Komorebi --- Created attachment 152130 --> https://bugs.kde.org/attachment.cgi?id=152130=edit No kwin debug console I don't have it. Krunner is also placed in a wrong position. Maybe some packages are missing? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget popups alignment
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #12 from Komorebi --- If you're talking about "plasma-interactiveconsole --kwin", this tool has broken output for years, at least in Neon. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget popups alignment
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #11 from Komorebi --- I'm not sure how do I run it, the only thing I've found is: qdbus org.kde.KWin /KWin supportInformation KWin Support Information: The following information should be used when requesting support on e.g. https://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like https://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.25.5 Qt Version: 5.15.6 Qt compile version: 5.15.6 XCB compile version: 1.14 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12013000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Plugin recommends border size: None onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0 decorationButtonsRight: 9, 3, 4, 5 borderSize: 0 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Platform == Name: DRM Active: true Atomic Mode Setting on GPU 0: true Cursor == themeName: breeze_cursors themeSize: 24 Options === focusPolicy: 0 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: 6 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777250 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 2 glStrictBinding: false glStrictBindingFollowsDriver: true glPreferBufferSwap: 101 glPlatformInterface: 2 windowsBlockCompositing: true latencyPolicy: renderTimeEstimator: Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: yes Number of Screens: 1 Screen 0: - Name: eDP-1 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 144000 Adaptive Sync: automatic Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: AMD OpenGL renderer string: AMD RENOIR (DRM 3.42.0, 5.15.0-48-generic, LLVM 12.0.0) OpenGL version string: 4.6 (Core Profile) Mesa 21.2.6 OpenGL platform interface: EGL OpenGL shading language version string: 4.60 Driver: RadeonSI GPU class: Vega OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 21.2.6 Linux kernel version: 5.15 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Loaded Effects: --- colorpicker blendchanges screenshot screenedge zoom kwin4_effect_login kwin4_effect_sessionquit kwin4_effect_logout slidingpopups kwin4_effect_windowaperture slide kwin4_effect_fullscreen kwin4_effect_squash kwin4_effect_frozenapp kwin4_effect_morphingpopups kwin4_effect_maximize kwin4_effect_scale kwin4_effect_fadingpopups sheet kwin4_effect_dialogparent desktopgrid highlightwindow overview windowview blur contrast startupfeedback kscreen screentransform Currently Active Effects: - blur contrast Effect Settings: colorpicker: blendchanges: screenshot: screenedge: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 focusTrackingEnabled: false textCaretTrackingEnabled: false focusDelay: 350 moveFactor: 20 targetZoom: 1 kwin4_effect_login: pluginId: kwin4_effect_login
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget popups alignment
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #9 from Komorebi --- At the current moment rearrangement of widgets in panel is also not possible. OSD popups in wrong position and steals keyboard focus. Plasma menu, notifications and OSD appear in overview and present windows. Kwin definitely do not recognize them as system windows. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget popups alignment
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #8 from Komorebi --- If I can help to debug this please let me know. Unfortunately I'm not expert in Plasma architecture and cpp. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget popups alignment
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #5 from Komorebi --- But the issue doesn't exist under Xorg. It's Wayland specific. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget popups alignment
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #4 from Komorebi --- No special settings or tricks, this can be reproduced even with default configuration, i.e. under newly created user. I'm not the only person who's affected: https://twitter.com/eastretrogamer/status/1570531825050877952 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget popups alignment
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #2 from Komorebi --- All popups no longer have an animation (when they appear or closed) and also have a taskbar icon. Feels like a mess with window class id or something. Please let me know if I can provide any useful information. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] The last frameworks update breaks plasma widget popups alignment
https://bugs.kde.org/show_bug.cgi?id=459188 --- Comment #1 from Komorebi --- It also moved notifications to center as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 459188] New: The last frameworks update breaks plasma widget popups alignment
https://bugs.kde.org/show_bug.cgi?id=459188 Bug ID: 459188 Summary: The last frameworks update breaks plasma widget popups alignment Product: frameworks-plasma Version: 5.98.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: plasma-b...@kde.org Reporter: markovs.i.m...@gmail.com CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: --- Created attachment 152084 --> https://bugs.kde.org/attachment.cgi?id=152084=edit Screenshot STEPS TO REPRODUCE 1. Run plasma width frameworks 5.98 2. Click on any applet OBSERVED RESULT Popup is centered EXPECTED RESULT Popup opens above plasmoid Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800HS with Radeon Graphics Memory: 22,9 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G14 GA401QE_GA401QE System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457486] Windows opened in multiple desktops have wrong z-positioning when switching between desktops
https://bugs.kde.org/show_bug.cgi?id=457486 --- Comment #6 from Komorebi --- >the issue is already fixed in current git master for Present Windows and >Desktop Grid still present in 5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457486] Windows opened in multiple desktops have wrong z-positioning when switching between desktops
https://bugs.kde.org/show_bug.cgi?id=457486 Komorebi changed: What|Removed |Added Version|5.25.4 |5.25.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457486] Windows opened in multiple desktops have wrong z-positioning when switching between desktops
https://bugs.kde.org/show_bug.cgi?id=457486 --- Comment #1 from Komorebi --- Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.15.0-43-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800HS with Radeon Graphics Memory: 22,9 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G14 GA401QE_GA401QE System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457486] Windows opened in multiple desktops have wrong z-positioning when switching between desktops
https://bugs.kde.org/show_bug.cgi?id=457486 Komorebi changed: What|Removed |Added Summary|Windows opened in multiple |Windows opened in multiple |desktops have wrong |desktops have wrong |z-position in new effects |z-positioning when ||switching between desktops -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457486] New: Windows opened in multiple desktops have wrong z-position in new effects
https://bugs.kde.org/show_bug.cgi?id=457486 Bug ID: 457486 Summary: Windows opened in multiple desktops have wrong z-position in new effects Product: kwin Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: markovs.i.m...@gmail.com Target Milestone: --- Affected effects are: desktop grid, slide (switch desktop) and present windows. This bug is a 5.25 regression. STEPS TO REPRODUCE 1. Make kwin rule "force window appear on all desktops" 2. Try to switch desktops or use swipe gesture to activate one of the effects affected OBSERVED RESULT In most cases window that is assigned to all desktops are painted on top, even if it's not active EXPECTED RESULT These windows should behave as any other window Here's the video demonstrating the issue: https://drive.google.com/file/d/1zBCaWDVhz48RSOoVooholAeHnj-LfmNn/view?usp=sharing On desktop 4 Spotify (which is an all-desktops window) is painted on top of the Chrome, but Chrome is treated as active by the effects and also by the panel (which is correct). Also the window overflows slide effect. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457049] Global hotkeys are not working when Chrome/Chromium PWA window is focused on wayland
https://bugs.kde.org/show_bug.cgi?id=457049 --- Comment #3 from Komorebi --- I think it must be possible because gnome wayland is not affected. The fix can probably lead to some side-effects like chrome apps won't be able to handle some shortcuts (global ones maybe), but to be honest - I don't see any difference in chrome behavior between X11 and Wayland on Gnome, everything just works. There's also a workaround for Sway that can be investigated and probably ported to Kwin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457049] Global hotkeys are not working when Chrome/Chromium PWA window is focused on wayland
https://bugs.kde.org/show_bug.cgi?id=457049 --- Comment #1 from Komorebi --- https://bugs.chromium.org/p/chromium/issues/detail?id=1338554#c16 - it seems like chromium team is not going to fix this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457049] Global hotkeys are not working when Chrome/Chromium PWA window is focused on wayland
https://bugs.kde.org/show_bug.cgi?id=457049 Komorebi changed: What|Removed |Added Summary|Global hotkeys are not |Global hotkeys are not |working when PWA window is |working when |focused on wayland |Chrome/Chromium PWA window ||is focused on wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457049] New: Global hotkeys are not working when PWA window is focused on wayland
https://bugs.kde.org/show_bug.cgi?id=457049 Bug ID: 457049 Summary: Global hotkeys are not working when PWA window is focused on wayland Product: plasmashell Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: markovs.i.m...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 I've already posted this bug to Chromium bug tracker, and some users confirm that it also applies to Sway. But it seems like in Gnome everything works as expected. Is there any way to fix it on the system level? STEPS TO REPRODUCE 1.Run wayland session 2.Enable Preferred Ozone platform = auto flag 3.Open some PWA on Wayland, YouTube as instance 4.See that meta key, media keys and other global keyboard hotkeys are no longer working when PWA is focused EXPECTED RESULT Global hotkeys work as usual SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.15.0-43-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800HS with Radeon Graphics Memory: 22,9 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G14 GA401QE_GA401QE System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454600] PWA on wayland don't get their own window icon in the taskbar
https://bugs.kde.org/show_bug.cgi?id=454600 Komorebi changed: What|Removed |Added CC||markovs.i.m...@gmail.com --- Comment #3 from Komorebi --- Well, I'm using 5.25.2 and the issue still persists. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455674] Unmoving cursor continually reselects the menu item it's hovering over
https://bugs.kde.org/show_bug.cgi?id=455674 --- Comment #13 from Komorebi --- Created attachment 150271 --> https://bugs.kde.org/attachment.cgi?id=150271=edit Settings icon is focused without cursor I see the same behavior in other widgets, see the settings button is focused without mouse pointer. Shall I create a separate bug report? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455674] Unmoving cursor continually reselects the menu item it's hovering over
https://bugs.kde.org/show_bug.cgi?id=455674 --- Comment #12 from Komorebi --- I've forked kickoff in order to implement https://bugs.kde.org/show_bug.cgi?id=455724 (test version is here: https://github.com/komorebithrowsatable/org.kde.plasma.kickoff.fixed), and it seems like this behavior is a result of 2 bugs. I seems like when you run one of you favorite apps (which are located in grid view) with mouse click, MouseArea don't emit exited() event and behaves like the mouse pointer is still there even after Kickoff is closed. But it looks like it's a deeper Qt bug that causes "phantom" mouse pointer to stay on the last position until you hover Kickoff with a real pointer once again. In combination with this bug this leads to the behavior shown in the video - "phantom" cursor selects an element from the bottom during the animation. So fixing this bug probably may also resolve bug from the video, at least for the current Kickoff version. But it also effects my version of Kickoff and probably some other alternative solutions, which means it can cause some issues with Plasma in future. To reproduce: 1. Run wayland session 2. Run app from the "favorites" grid 3. Try to search In this video you can see how item remains highlighted till I move mouse to Kickoff: https://drive.google.com/file/d/141mVx-tELYUwNykA1Z7lop9wXPOPo1EV/view?usp=sharing I'm attaching demo with my kickoff just because it illustrates the issue a way better. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455674] Unmoving cursor continually reselects the menu item it's hovering over
https://bugs.kde.org/show_bug.cgi?id=455674 --- Comment #9 from Komorebi --- Attaching a video showing similar issue: wrong menu item got selected even without hovering mouse cursor. Please let me know if it's a separate issue and I have to create a new bug report. I'm not sure. Vid: https://drive.google.com/file/d/12VCAvgZ33gvDQHbvVApflJvhHa5WLwKq/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455724] Kickoff should have 2 separate cursor items for mouse and keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=455724 --- Comment #7 from Komorebi --- Created attachment 150074 --> https://bugs.kde.org/attachment.cgi?id=150074=edit How it looks in dolphin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455724] Kickoff should have 2 separate cursor items for mouse and keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=455724 --- Comment #6 from Komorebi --- Again, that's not an idea, it's a pretty standard UX thing. When you tab with keyboard over the elements, you know which one is going to be activated with enter. All apps are actually work the same way, see dolphin screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455724] Kickoff should have 2 separate cursor items for mouse and keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=455724 --- Comment #4 from Komorebi --- Created attachment 150028 --> https://bugs.kde.org/attachment.cgi?id=150028=edit How it looks in Gnome -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455724] Kickoff should have 2 separate cursor items for mouse and keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=455724 --- Comment #3 from Komorebi --- Maybe I wasn't correct enough with my explanation. KDE is actually the only DE that acts this way. most of DEs and operating systems just highlight item on hover and keep keyboard cursor completely separated from mouse actions. There's no 2 different cursors, there's acrually only a keyboard one and cursor hover animation. See the Gnome screenshot attached. This it pretty standard behavior and gold standard from UX perspective. In Windows it works the same way, but I can't demonstrate it, Gnome boxes don't run windows 11 unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455724] New: Kickoff should have 2 separate cursor items for mouse and keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=455724 Bug ID: 455724 Summary: Kickoff should have 2 separate cursor items for mouse and keyboard navigation Product: plasmashell Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: markovs.i.m...@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 >From the UX perspective, navigation with keyboard and mouse are 2 different type of things. Sharing the same cursor item between 2 different types of input makes bugs like https://bugs.kde.org/show_bug.cgi?id=455674 possible. But even if it get fixed, there's still a situation when user hits meta, performs a search and hits enter to run the first entry without paying attention to mouse cursor and item selected. But if mouse cursor is placed in menu area and hovers another search result, the enter buttons opens it instead of the first entry. What I'm trying to say is there's no situation in real life when it's helpful to hover search result with the mouse, but select it with enter, so hovering search result with a mouse should never select it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455284] Swipe left/right gestures got inverted in 5.25
https://bugs.kde.org/show_bug.cgi?id=455284 Komorebi changed: What|Removed |Added Component|libinput|effects-various -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455284] New: Swipe left/right gestures got inverted in 5.25
https://bugs.kde.org/show_bug.cgi?id=455284 Bug ID: 455284 Summary: Swipe left/right gestures got inverted in 5.25 Product: kwin Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: markovs.i.m...@gmail.com Target Milestone: --- Desktop switching gestures got inverted in 5.25 which is pretty uncomfortable to use STEPS TO REPRODUCE 1. Swipe with 4 fingers to the right to switch to the next desktop OBSERVED RESULT Kwin switches to the previous desktop EXPECTED RESULT Kwin switches to the next desktop Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.15.0-33-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800HS with Radeon Graphics Memory: 22,9 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G14 GA401QE_GA401QE System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449915] Script settings are broken
https://bugs.kde.org/show_bug.cgi?id=449915 Komorebi changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #4 from Komorebi --- Moving to resolved, but probably yes, community needs some kind of notification about this change. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449915] Script settings are broken
https://bugs.kde.org/show_bug.cgi?id=449915 --- Comment #3 from Komorebi --- Thanks, it helped. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449915] New: Script settings are broken
https://bugs.kde.org/show_bug.cgi?id=449915 Bug ID: 449915 Summary: Script settings are broken Product: kwin Version: 5.24.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripts Assignee: kwin-bugs-n...@kde.org Reporter: markovs.i.m...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Install kwin script like https://github.com/esjeon/krohnkite 2. Register is as service: mkdir -p ~/.local/share/kservices5/ ln -s ~/.local/share/kwin/scripts/krohnkite/metadata.desktop ~/.local/share/kservices5/krohnkite.desktop OBSERVED RESULT "Plugin does not provide configuration file in expected location" window EXPECTED RESULT Settings work as in previous KDE versions. Even if it's not a bug, it's a least a backwards compatibility issue. Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-28-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,4 GiB of RAM Graphics Processor: Radeon RX550/550 Series -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 445804] kiconthemes 5.88.0 inconsistent icon changes
https://bugs.kde.org/show_bug.cgi?id=445804 --- Comment #20 from Komorebi --- I just want to mention that bug https://bugs.kde.org/show_bug.cgi?id=447092 is marked as duplicate of this one, but I'm not sure if they're really related. Anyway I want to highlight that google chrome web application icons are still broken -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 447092] Google chrome application icons are shown as Google Chrome icon after upgrading frameworks
https://bugs.kde.org/show_bug.cgi?id=447092 --- Comment #5 from Komorebi --- I've found that the issue persists only if I use some icon theme. With breeze icon theme everything looks good. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 447092] Google chrome application icons are shown as Google Chrome icon after upgrading frameworks
https://bugs.kde.org/show_bug.cgi?id=447092 Komorebi changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 447092] Google chrome application icons are shown as Google Chrome icon after upgrading frameworks
https://bugs.kde.org/show_bug.cgi?id=447092 --- Comment #3 from Komorebi --- No, it's broken everywhere except one place in KMenuEdit app. Please see the app menu screenshot. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 447092] Google chrome application icons are shown as Google Chrome icon after upgrading frameworks
https://bugs.kde.org/show_bug.cgi?id=447092 --- Comment #1 from Komorebi --- Created attachment 144612 --> https://bugs.kde.org/attachment.cgi?id=144612=edit App menu -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 447092] New: Google chrome application icons are shown as Google Chrome icon after upgrading frameworks
https://bugs.kde.org/show_bug.cgi?id=447092 Bug ID: 447092 Summary: Google chrome application icons are shown as Google Chrome icon after upgrading frameworks Product: frameworks-plasma Version: 5.89.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: markovs.i.m...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 144611 --> https://bugs.kde.org/attachment.cgi?id=144611=edit KDE Menu Editor SUMMARY After upgrading to 5.89 my Google Chrome application icons are shown as Google Chrome icon. I've checked .desktop files, and they remain the same, icons are set correctly, KDE Menu Editor icon selector is able to display them in icon change dialog, so they exist in system, however in the app tree they still displayed as Google Chrome. (see screenshot). This issue affects application menus and taskbar. Updating icons manually with menu editor does nothing. STEPS TO REPRODUCE 1. Upgrade frameworks to 5.89 2. See google chrome app icons are disappeared Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Kernel Version: 5.13.0-22-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,4 GiB of RAM Graphics Processor: Radeon RX550/550 Series -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443990] Kwin memory leak
https://bugs.kde.org/show_bug.cgi?id=443990 --- Comment #21 from Komorebi --- No longer happens to me. The system is up for 6 days and kwin consumes ~280MB of ram which is probably slightly more that before 5.23, but still less than in 5.23.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443990] Kwin memory leak
https://bugs.kde.org/show_bug.cgi?id=443990 --- Comment #15 from Komorebi --- >@Komorebi is memory leaked when using breeze window deco? Yes >I'm afraid it might have to do with the official nvidia driver. >I posted about the subject on Reddit. 3 people using Mesa/AMDGPU don't have >the issue, and I'm not able to replicate it either, as soon as I remove the >nvidia driver package. I have Radeon RX550/550 Series, so there might be 2 different issues. >alt-tab spam also raises the value by no more than 0.3 MB (which is also >de-allocated only seconds later) I'm not able to reproduce the issue by making some actions like alt+tabing, opening and closing windows, etc. Consumed memory grows over time by itself. The only way to reproduce the issue for me is just to wait for 2-3 days of uptime. I believe it's very important thing to take into account. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443990] Kwin memory leak
https://bugs.kde.org/show_bug.cgi?id=443990 --- Comment #7 from Komorebi --- + snapshot: https://drive.google.com/file/d/1E2ck3tYvGqR66EymOaUXyo8Y86Sk9uUk/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443990] Kwin memory leak
https://bugs.kde.org/show_bug.cgi?id=443990 --- Comment #5 from Komorebi --- ~1 day heaptrack https://drive.google.com/file/d/1fmY3vrwmtUeaAu34zql9NJmPJEWje5cX/view?usp=sharing I'm still running kwin with heaptrack and will upload one more snapshot later. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443990] Kwin memory leak
https://bugs.kde.org/show_bug.cgi?id=443990 --- Comment #4 from Komorebi --- I can't confirm alt+tabing increases memory usage. Will try heaptrack. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443990] Kwin memory leak
https://bugs.kde.org/show_bug.cgi?id=443990 --- Comment #1 from Komorebi --- Created attachment 142587 --> https://bugs.kde.org/attachment.cgi?id=142587=edit Kwin memory usage -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443990] New: Kwin memory leak
https://bugs.kde.org/show_bug.cgi?id=443990 Bug ID: 443990 Summary: Kwin memory leak Product: kwin Version: 5.23.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: markovs.i.m...@gmail.com Target Milestone: --- SUMMARY I've noticed kwin_x11 memory leak after updating plasma to the latest version (5.23.0) STEPS TO REPRODUCE 1. Update to 5.23.0 2. Wait 4 days OBSERVED RESULT After 4 days of uptime kwin uses 560MiB of ram. It was using ~200MiB (or less) before. Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-36-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,4 GiB of RAM Graphics Processor: Radeon RX550/550 Series -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 441792] Latte tasks are rendered with 1px height when dock/panel is positioned vertically and scrolling is enabled
https://bugs.kde.org/show_bug.cgi?id=441792 --- Comment #8 from Komorebi --- There's no special way to reproduce it. The bug only has a chance to occur on startup (very huge chance for me, but probably not for most of users). Probably you can try to overload your iowait, but for me it happens even without huge system load. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 441792] Latte tasks are rendered with 1px height when dock/panel is positioned vertically and scrolling is enabled
https://bugs.kde.org/show_bug.cgi?id=441792 --- Comment #4 from Komorebi --- Created attachment 141195 --> https://bugs.kde.org/attachment.cgi?id=141195=edit My layout -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 441792] Latte tasks are rendered with 1px height when dock/panel is positioned vertically and scrolling is enabled
https://bugs.kde.org/show_bug.cgi?id=441792 --- Comment #2 from Komorebi --- Created attachment 141172 --> https://bugs.kde.org/attachment.cgi?id=141172=edit Option I've disabled -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 441792] Latte tasks are rendered with 1px height when dock/panel is positioned vertically and scrolling is enabled
https://bugs.kde.org/show_bug.cgi?id=441792 Komorebi changed: What|Removed |Added Summary|Latte tasks sometimes |Latte tasks are rendered |displayed horizontally (1px |with 1px height when |height) when dock/panel is |dock/panel is positioned |positioned vertically |vertically and scrolling is ||enabled -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 441792] Latte tasks sometimes displayed horizontally (1px height) when dock/panel is positioned vertically
https://bugs.kde.org/show_bug.cgi?id=441792 --- Comment #1 from Komorebi --- Created attachment 141171 --> https://bugs.kde.org/attachment.cgi?id=141171=edit Correct layout -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 441792] New: Latte tasks sometimes displayed horizontally (1px height) when dock/panel is positioned vertically
https://bugs.kde.org/show_bug.cgi?id=441792 Bug ID: 441792 Summary: Latte tasks sometimes displayed horizontally (1px height) when dock/panel is positioned vertically Product: lattedock Version: 0.10.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: markovs.i.m...@gmail.com Target Milestone: --- Created attachment 141170 --> https://bugs.kde.org/attachment.cgi?id=141170=edit Broken layout SUMMARY Sometimes when dock is positioned vertically and scrolling option is enabled - latte tasks are rendered in a wrong way. Please see screenshots. As a temporary solution I've disabled scrolling. STEPS TO REPRODUCE 1. Launch latte 2. Sometimes layout is broken Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-27-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,4 GiB of RAM Graphics Processor: Radeon RX550/550 Series -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 423998] Weather widget tab captions are barely readable when Breeze global theme and Breeze Dark plasma style are used
https://bugs.kde.org/show_bug.cgi?id=423998 --- Comment #1 from Komorebi --- Created attachment 129977 --> https://bugs.kde.org/attachment.cgi?id=129977=edit Weather widget -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 423998] New: Weather widget tab captions are barely readable when Breeze global theme and Breeze Dark plasma style are used
https://bugs.kde.org/show_bug.cgi?id=423998 Bug ID: 423998 Summary: Weather widget tab captions are barely readable when Breeze global theme and Breeze Dark plasma style are used Product: kdeplasma-addons Version: 5.19.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Weather Assignee: plasma-b...@kde.org Reporter: markovs.i.m...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Set up you plasma to use breeze dark plasma style and breeze light window colors 2. Add weather widget to panel 3. Open full representation OBSERVED RESULT "3 days" and "details" tab captions use dark font color (screenshot is attached) EXPECTED RESULT Light font color SOFTWARE/OS VERSIONS Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-62-generic OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23.4 GiB of RAM Graphics Processor: Radeon RX550/550 Series -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 423747] Barely readable caption text when Breeze global theme and Breeze Dark plasma style are used
https://bugs.kde.org/show_bug.cgi?id=423747 --- Comment #11 from Komorebi --- Ok, thank you, will file a bug for weather and wait for 5.20 (I use neon). -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 423747] Barely readable caption text when Breeze global theme and Breeze Dark plasma style are used
https://bugs.kde.org/show_bug.cgi?id=423747 --- Comment #9 from Komorebi --- I don't feel like there's a reason to create multiple bug reports since most of widgets (at least weather, bluetooth, clipboard and notifications) are affected and the issue must be the same for all of them. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 423747] Barely readable caption text when Breeze global theme and Breeze Dark plasma style are used
https://bugs.kde.org/show_bug.cgi?id=423747 --- Comment #7 from Komorebi --- *I'm on. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 423747] Barely readable caption text when Breeze global theme and Breeze Dark plasma style are used
https://bugs.kde.org/show_bug.cgi?id=423747 --- Comment #6 from Komorebi --- Well, I'm not 5.19.3 and the issue is still here. Weather and notifications widgets are affected. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 423747] Barely readable caption text when Breeze global theme and Breeze Dark plasma style are used
https://bugs.kde.org/show_bug.cgi?id=423747 Komorebi changed: What|Removed |Added CC||markovs.i.m...@gmail.com --- Comment #5 from Komorebi --- Created attachment 129967 --> https://bugs.kde.org/attachment.cgi?id=129967=edit Weather widget on 5.19.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422899] Kwin crashed when using present window option via hot corners.
https://bugs.kde.org/show_bug.cgi?id=422899 Komorebi changed: What|Removed |Added CC||markovs.i.m...@gmail.com --- Comment #1 from Komorebi --- Same here Application: kwin_x11 (5.19.2) Qt Version: 5.14.2 Frameworks Version: 5.71.0 Operating System: Linux 5.3.0-59-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [KCrash Handler] #4 0x55ab026cdc00 in () #5 0x7fe0b115afca in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) (this=0x55ab0055e6e0, e=0x7fe0900749f0) at ./events.cpp:240 #6 0x7fe0ae7ca4df in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=, eventType=..., message=message@entry=0x7fe0900749f0, result=result@entry=0x7ffd33e0cc48) at kernel/qabstracteventdispatcher.cpp:488 #7 0x7fe099ea7bac in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0x55ab00458fd0, event=event@entry=0x7fe0900749f0) at qxcbconnection.cpp:550 #8 0x7fe099ea86d6 in QXcbConnection::processXcbEvents(QFlags) (this=0x55ab00458fd0, flags=...) at qxcbconnection.cpp:1029 #9 0x7fe099ecd32c in QXcbUnixEventDispatcher::processEvents(QFlags) (this=0x55ab004ab2a0, flags=...) at qxcbeventdispatcher.cpp:61 #10 0x7fe0ae7cbd2a in QEventLoop::exec(QFlags) (this=this@entry=0x7ffd33e0cda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #11 0x7fe0ae7d54a0 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1383 #12 0x55aafffcc3db in main(int, char**) (argc=, argv=0x7ffd33e0d018) at ./main_x11.cpp:479 Possible duplicates by query: bug 423319, bug 422899, bug 422558, bug 422275, bug 421762. Report to https://bugs.kde.org/ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 423268] New: Huge memory leak
https://bugs.kde.org/show_bug.cgi?id=423268 Bug ID: 423268 Summary: Huge memory leak Product: lattedock Version: 0.9.11 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: markovs.i.m...@gmail.com Target Milestone: --- SUMMARY Latte consumes more and more ram each time I navigate to dock settings or every time compositor gets restarted STEPS TO REPRODUCE 1. Navigate to dock settings 2. Settings window is appeared, latte consumes more ram 3. Close settings. Latte releases only ~half of ram consumed on 2nd step 4. Repeat 1-3 OBSERVED RESULT The process uses more and more ram (up to 2Gb) EXPECTED RESULT Amount of RAM used by the process shouldn't increase Similar problem is related to kwin restarts. I.e. ram is increased after kwin --replace or just running and closing Steam. Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-59-generic OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,4 GiB of RAM Graphics Processor: Radeon RX550/550 Series -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416219] Sometimes window stays visible after closing it
https://bugs.kde.org/show_bug.cgi?id=416219 --- Comment #15 from Komorebi --- Yep, I haven't faced it for 3 months or so. This is a really rare thing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416219] Sometimes window stays visible after closing it
https://bugs.kde.org/show_bug.cgi?id=416219 Komorebi changed: What|Removed |Added Version|5.17.5 |5.18.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416219] Sometimes window stays visible after closing it
https://bugs.kde.org/show_bug.cgi?id=416219 --- Comment #13 from Komorebi --- The window was still there after disabling fade effect, but disappeared after disabling squash. I was testing it on the fly without restarting kwin. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416219] Sometimes window stays visible after closing it
https://bugs.kde.org/show_bug.cgi?id=416219 --- Comment #10 from Komorebi --- Yep, already did that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416219] Sometimes window stays visible after closing it
https://bugs.kde.org/show_bug.cgi?id=416219 Komorebi changed: What|Removed |Added Attachment #128834|Discover window |Discover window is shown description||after closing it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416219] Sometimes window stays visible after closing it
https://bugs.kde.org/show_bug.cgi?id=416219 --- Comment #8 from Komorebi --- Hi, that happened again. Attaching screenshot and requested information. komorebi@komorebi-pc:~$ qdbus org.kde.KWin /KWin supportInformation KWin Support Information: The following information should be used when requesting support on e.g. https://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like https://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.18.5 Qt Version: 5.14.2 Qt compile version: 5.14.2 XCB compile version: 1.13 Operation Mode: X11 only Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_EGL_STREAMS: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12005000 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.kwin.aurorae Theme: __aurorae__svg__Breezemite Plugin recommends border size: No Blur: 1 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 5, 3, 4 decorationButtonsRight: borderSize: 3 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Platform == Name: KWin::X11StandalonePlatform Options === focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 6 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 0 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 28 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 28 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: true killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 1666 refreshRate: 0 vBlankTime: 600 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 101 glPlatformInterface: 1 windowsBlockCompositing: true Screen Edges desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens === Multi-Head: no Active screen follows mouse: no Number of Screens: 1 Screen 0: - Name: HDMI-A-0 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 60 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Radeon 550 Series (POLARIS12, DRM 3.33.0, 5.3.0-53-generic, LLVM 9.0.0) OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.2.8 OpenGL platform interface: GLX OpenGL shading language version string: 4.50 Driver: RadeonSI GPU class: Arctic Islands OpenGL version: 4.5 GLSL version: 4.50 Mesa version: 19.2.8 X server version: 1.20.5 Linux kernel version: 5.3 Direct rendering: Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --- zoom mouseclick slidingpopups kwin4_effect_login kwin4_effect_logout kwin4_effect_sessionquit kwin4_effect_windowaperture slide screenshot kwin4_effect_translucency flipswitch desktopgrid coverswitch colorpicker kwin4_effect_fadingpopups kwin4_effect_maximize kwin4_effect_squash kwin4_effect_fade kwin4_effect_frozenapp kwin4_effect_morphingpopups kwin4_effect_dialogparent presentwindows highlightwindow blur contrast startupfeedback screenedge kscreen Currently Active Effects: - kwin4_effect_squash blur contrast Effect Settings: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true
[kwin] [Bug 416219] Sometimes window stays visible after closing it
https://bugs.kde.org/show_bug.cgi?id=416219 --- Comment #7 from Komorebi --- Created attachment 128834 --> https://bugs.kde.org/attachment.cgi?id=128834=edit Discover window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419880] New: Chromium/electron app repainting bug
https://bugs.kde.org/show_bug.cgi?id=419880 Bug ID: 419880 Summary: Chromium/electron app repainting bug Product: kwin Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: glx Assignee: kwin-bugs-n...@kde.org Reporter: markovs.i.m...@gmail.com Target Milestone: --- SUMMARY I've created demo video with the bug: https://drive.google.com/file/d/1RxXezieDaVNh27wWU04lyTlA--BkRCPd/view?usp=sharing In most cases it happens after couple of days of uptime. Restarting kwin solves the problem. The bug affects not only video playback, but all application UI. i.e. on 0:21 I click "add tab" and it appears only after repaint on 0:22. Electron apps can also be affected in some rare cases. STEPS TO REPRODUCE I haven't found any stable way to reproduce this. In mosy cases you just need 1 week of uptime and chrome running all the time. Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 Kernel Version: 5.3.0-45-generic OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,4 GiB of RAM OpenGL vendor string: X.Org OpenGL renderer string: Radeon 550 Series (POLARIS12, DRM 3.33.0, 5.3.0-45-generic, LLVM 9.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.2.8 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.2.8 OpenGL shading language version string: 4.50 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.2.8 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 417933] Unable to update widget via discover or "get widgets" menu
https://bugs.kde.org/show_bug.cgi?id=417933 --- Comment #4 from Komorebi --- 1. No, discover UI just showed that widget is updated. 2. The worst issue is that widget is not updated even if update is successful. I mean I still have event calendar v63 on some of my devices, but plasma/discover is sure that it's v66. This could be really critical since a lot of users potentially are missing a lot of critical fixes like one that caused event calendar to consume a lot of cpu and spam google api requests when google calendar is down. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 417933] Unable to update widget via discover or "get widgets" menu
https://bugs.kde.org/show_bug.cgi?id=417933 --- Comment #2 from Komorebi --- Created attachment 126214 --> https://bugs.kde.org/attachment.cgi?id=126214=edit install widget menu that shows that event calendar is updated -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 417933] Unable to update widget via discover or "get widgets" menu
https://bugs.kde.org/show_bug.cgi?id=417933 --- Comment #1 from Komorebi --- Created attachment 126213 --> https://bugs.kde.org/attachment.cgi?id=126213=edit local plasmoid metadata -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 417933] New: Unable to update widget via discover or "get widgets" menu
https://bugs.kde.org/show_bug.cgi?id=417933 Bug ID: 417933 Summary: Unable to update widget via discover or "get widgets" menu Product: frameworks-knewstuff Version: 5.67.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jpwhit...@kde.org Reporter: markovs.i.m...@gmail.com CC: ad...@leinir.dk, kdelibs-b...@kde.org Target Milestone: --- Created attachment 126212 --> https://bugs.kde.org/attachment.cgi?id=126212=edit discover output SUMMARY Unable to update event calendar via discover. STEPS TO REPRODUCE 1. Have event calendar v65 installed 2. Find event calendar in discover, click "update all" OBSERVED RESULT Widget is not updated EXPECTED RESULT Widget is updated Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,4 GiB of RAM This also affects KDE widget installer. All my machines are affected. I've also found this when publishing my own extension (https://store.kde.org/p/1359965/) it also never get updated (however discover shows that update is installed, in fact ~/.local/share/plasma/plasmoid/ stuff remains old. I thought that i;m doing something wrong, but now it seems like it's an updater issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415155] Closing window from Present Windows effect sometimes causes the new frontmost window to lose focus and be unable to regain it
https://bugs.kde.org/show_bug.cgi?id=415155 --- Comment #2 from Komorebi --- Also affected Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.67.0 Qt Version: 5.13.2 Kernel Version: 5.3.0-28-generic OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,4 GiB of RAM Please let me know if you need some additional info. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416219] Sometimes window stays visible after closing it
https://bugs.kde.org/show_bug.cgi?id=416219 --- Comment #5 from Komorebi --- Hello, that never happened to me again, so I'm not able to share more details. Maybe it was something related to cache. Anyway, it looks like the issue is gone. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416219] Sometimes window stays visible after closing it
https://bugs.kde.org/show_bug.cgi?id=416219 --- Comment #1 from Komorebi --- Also never seen this before 5.17.5 upgrade -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416219] New: Sometimes window stays visible after closing it
https://bugs.kde.org/show_bug.cgi?id=416219 Bug ID: 416219 Summary: Sometimes window stays visible after closing it Product: kwin Version: 5.17.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: markovs.i.m...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Close any window (every window has a little random chance to be affected) 2. Sometimes it stays visible, but is not applicable, so it doesn't actually exist, but remains painted on the desktop Suspending kwin removes window's image from the desktop: qdbus org.kde.KWin /Compositor suspend qdbus org.kde.KWin /Compositor resume Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 Kernel Version: 5.0.0-37-generic OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,5 GiB of RAM Radeon 550 Series (POLARIS12, DRM 3.27.0, 5.0.0-37-generic, LLVM 8.0.0) 4.5 (Compatibility Profile) Mesa 19.0.8 Xsession, rendering backend - OpenGL 3.1 (will try 2.0) ADDITIONAL INFORMATION Close animation - Fade -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414337] New: I'm no longer able to apply night color settings
https://bugs.kde.org/show_bug.cgi?id=414337 Bug ID: 414337 Summary: I'm no longer able to apply night color settings Product: systemsettings Version: 5.17.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: markovs.i.m...@gmail.com Target Milestone: --- Since the feature was added for X.org sessions, I've enabled it when received 5.17.0 update. Today I've found that changing any night color settings doesn't active an "Apply" button, so I'm no longer able to apply any changes I've made. I got stuck on "Times" operation mode, and changing any values (including sunrise/sunset, operation mode, temperature, activate checkbox itself) does actually nothing. STEPS TO REPRODUCE 1. Open settings 2. Go to night color 3. Change any value OBSERVED RESULT Apply button is grayed out EXPECTED RESULT Apply to become active Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 Kernel Version: 5.0.0-36-generic OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413253] New: I'm no longer able to install flatpak packages
https://bugs.kde.org/show_bug.cgi?id=413253 Bug ID: 413253 Summary: I'm no longer able to install flatpak packages Product: Discover Version: 5.17.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: lei...@leinir.dk Reporter: markovs.i.m...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com Target Milestone: --- SUMMARY Since the last flatpak update (1.4.3) I'm not able to install or update flatpaks on my desktop (however everything works on my laptop). Installing/updating from konsole works well. STEPS TO REPRODUCE 1. Find some flathub package in discover (gnome boxes as instance) 2. Click "install" OBSERVED RESULT "Aborted due to failure" message will pop. EXPECTED RESULT App is installed SOFTWARE/OS VERSIONS Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.0.0-31-generic OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 V2 @ 3.20GHz Memory: 23,5 GiB of RAM Unfortunately, I have no idea how to debug it. Running discover in terminal gives nothing about the error. I can provide additional info if you help me find it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408888] Regression in 5.16: plasma process constantly consumes 10% CPU
https://bugs.kde.org/show_bug.cgi?id=40 Komorebi changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Komorebi --- I found that the problem is caused by event calendar, the agenda was constantly scrolling up and down without any reason which caused a lot of repaints and CPU usage as result. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408888] New: Regression in 5.16: plasma process constantly consumes 10% CPU
https://bugs.kde.org/show_bug.cgi?id=40 Bug ID: 40 Summary: Regression in 5.16: plasma process constantly consumes 10% CPU Product: plasmashell Version: 5.16.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: markovs.i.m...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 120988 --> https://bugs.kde.org/attachment.cgi?id=120988=edit Task manager screenshot SUMMARY STEPS TO REPRODUCE 1. Run plasma and wait for some time. I'm not sure what triggers it. OBSERVED RESULT 10% CPU load on plasmashell EXPECTED RESULT CPU is not used while idle SOFTWARE/OS VERSIONS Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.18.0-22-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i3-3225 CPU @ 3.30GHz Memory: 23,5 GiB of RAM Radeon RX 550 Series (POLARIS12, DRM 3.26.0, 4.18.0-22-generic, LLVM 7.0.0)s -- You are receiving this mail because: You are watching all bug changes.
