[kwin] [Bug 465158] line glitches with 125% and 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=465158 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] line glitches with 125% and 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #10 from Mathias Tillman --- This also seems to happen on the recently released Plasma 5.27. Weirdly, for me, it doesn't appear on 150% scaling, but it does on 125%. If I change to 140% I get a horizontal line instead which appears at roughly the same place as the vertical bar when using 125%. Here's my output of the support info: == Version === KWin version: 5.27.0 Qt Version: 5.15.8 Qt compile version: 5.15.8 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 X11 === Vendor: The X.Org Foundation Vendor Release: 12201001 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__Canta-light Plugin recommends border size: No onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0 decorationButtonsRight: 3, 4, 5 borderSize: 3 gridUnit: 12 font: Google Sans,10,-1,5,50,0,0,0,0,0,Regular smallSpacing: 3 largeSpacing: 12 Output backend == Name: DRM Active: true Atomic Mode Setting on GPU 0: true Cursor == themeName: breeze_cursors themeSize: 24 Options === focusPolicy: 1 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: true clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 300 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: true activeMouseScreen: true placement: activationDesktopPolicy: 0 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false 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: 16777251 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: allowTearing: 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 === Active screen follows mouse: yes Number of Screens: 2 Screen 0: - Name: DP-1 Enabled: 1 Geometry: 0,0,2048x1152 Scale: 1.25 Refresh Rate: 143998 Adaptive Sync: incapable Screen 1: - Name: DP-2 Enabled: 1 Geometry: 2047,0,1766x994 Scale: 1.44922 Refresh Rate: 143998 Adaptive Sync: incapable Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.7, DRM 3.49, 6.1.11-x64v1-xanmod1) OpenGL version string: 4.6 (Core Profile) Mesa 22.3.5 - kisak-mesa PPA OpenGL platform interface: EGL OpenGL shading language version string: 4.60 Driver: Unknown GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 22.3.5 X server version: 1.22.1 Linux kernel version: 6.1.11 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Loaded Effects: --- colorpicker outputlocator screenshot zoom blur contrast kwin4_effect_logout kwin4_effect_sessionquit kwin4_effect_login slidingpopups kwin4_effect_translucency kwin4_effect_windowaperture slide kwin4_effect_squash kwin4_effect_maximize kwin4_effect_morphingpopups kwin4_effect_frozenapp kwin4_effect_fadingpopups kwin4_effect_fullscreen kwin4_effect_scale kwin4_effect_dialogparent desktopgrid highlightwindow overview tileseditor windowview blendchanges startupfeedback kscreen screentransform Currently Active Effects: - blur contrast Effect Settings: colorpicker: outputlocator: screenshot: zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 focusTrackingEnabled: false textCaretTrackingEnabled: false focus
[kwin] [Bug 438401] [Wayland] 3rd-party window decoration pixelatex/badly rendered when fractional display scaling is used
https://bugs.kde.org/show_bug.cgi?id=438401 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] line glitches with 125% and 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #12 from Mathias Tillman --- Update: I think it may be related to the Blur effect, because I just tried turning that off and that seems to have made the lines disappear. Interestingly the lines also only appear when there's a semi-translucent window behind eg chrome or firefox. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] line glitches with 125% and 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #13 from Mathias Tillman --- Running a bisect the issue seems to be with https://invent.kde.org/plasma/kwin/-/commit/64e42bbd04e10e8b0c32bec444864ce7c64bbfc5 and that whole MR in fact. Maybe the blur code doesn't like the rounding ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] line glitches with 125% and 150% scale on Wayland
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #15 from Mathias Tillman --- @JonnyRobbie Do the lines go away of you disable the Blur effect? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466186] New: Closing VLC when a video is playing causes kwin wayland assert error crash/restart
https://bugs.kde.org/show_bug.cgi?id=466186 Bug ID: 466186 Summary: Closing VLC when a video is playing causes kwin wayland assert error crash/restart Classification: Plasma Product: kwin Version: 5.27.0 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: master.ho...@gmail.com Target Milestone: --- SUMMARY I'm experiencing a crash whenever I close VLC when a video is playing running kwin v5.27.0 (though I haven't tested earlier versions) on wayland. STEPS TO REPRODUCE 1. Play video through VLC 2. Close VLC 3. kwin wayland restarts OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Version === KWin version: 5.27.0 Qt Version: 5.15.8 Qt compile version: 5.15.8 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 X11 === Vendor: The X.Org Foundation Vendor Release: 12201001 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__Canta-light Plugin recommends border size: No onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0 decorationButtonsRight: 3, 4, 5 borderSize: 3 gridUnit: 10 font: Google Sans,10,-1,5,50,0,0,0,0,0,Regular smallSpacing: 2 largeSpacing: 10 Output backend == Name: DRM Active: true Atomic Mode Setting on GPU 0: true Cursor == themeName: breeze_cursors themeSize: 24 Options === focusPolicy: 1 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: true clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 300 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: true activeMouseScreen: true placement: activationDesktopPolicy: 0 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false 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: 16777251 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: allowTearing: 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 === Active screen follows mouse: yes Number of Screens: 2 Screen 0: - Name: DP-1 Enabled: 1 Geometry: 0,0,2048x1152 Scale: 1.25 Refresh Rate: 143998 Adaptive Sync: incapable Screen 1: - Name: DP-2 Enabled: 1 Geometry: 2048,0,2048x1152 Scale: 1.25 Refresh Rate: 143998 Adaptive Sync: incapable Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.7, DRM 3.49, 6.1.12-x64v1-xanmod1) OpenGL version string: 4.6 (Core Profile) Mesa 22.3.5 - kisak-mesa PPA OpenGL platform interface: EGL OpenGL shading language version string: 4.60 Driver: Unknown GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 22.3.5 Linux kernel version: 6.1.12 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Loaded Effects: --- colorpicker outputlocator screenshot zoom kwin4_effect_logout kwin4_effect_sessionquit kwin4_effect_login slidingpopups kwin4_effect_translucency kwin4_effect_windowaperture slide kwin4_effect_squash kwin4_effect_maximize kwin4_effect_morphingpopups kwin4_effect_frozenapp kwin4_effect_fadingpopups kwin4_effect_fullscreen kwin4_effect_scale kwin4_effect_dialogparent desktopgr
[kwin] [Bug 466186] Closing VLC when a video is playing causes kwin wayland assert error crash/restart
https://bugs.kde.org/show_bug.cgi?id=466186 --- Comment #1 from Mathias Tillman --- Seems the crash also happens under X11, so it's not limited to just Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465158] Line glitches with 125% and 150% scale on Wayland with either Both Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #21 from Mathias Tillman --- See https://invent.kde.org/plasma/kwin/-/merge_requests/3236 for a discussion about a potential fix for this issue. It does work for me, but there are some uncertainties about how to best approach it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466186] Closing VLC when a video is playing causes kwin assert error crash/restart
https://bugs.kde.org/show_bug.cgi?id=466186 Mathias Tillman changed: What|Removed |Added Summary|Closing VLC when a video is |Closing VLC when a video is |playing causes kwin wayland |playing causes kwin assert |assert error crash/restart |error crash/restart -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438401] [Wayland] 3rd-party window decoration pixelatex/badly rendered when fractional display scaling is used
https://bugs.kde.org/show_bug.cgi?id=438401 --- Comment #16 from Mathias Tillman --- Was this fixed in one of the 5.27.X releases? It seems to work fine for me now on 5.27.2 anyhow. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 459755] 5.26 Wayland windows go below Latte when "always visible" is chosen
https://bugs.kde.org/show_bug.cgi?id=459755 --- Comment #20 from Mathias Tillman --- (In reply to Archisman Panigrahi from comment #18) > (In reply to Mathias Tillman from comment #13) > > Slight update: Seems that it doesn't like it when the width is smaller than > > the height (for a top or bottom panel) or vice-versa. The "magic" 88 pixels > > width in my previous comment was actually the same as the height - that's > > why it started working when I changed it to that. > > So I guess a simple solution would be to change the 1 pixel width/height to > > the height/width counterpart. > > How do you change this height? I could not find a file named > waylandinterface.cpp You can see what needs to be changed in the MR above: https://invent.kde.org/plasma/latte-dock/-/merge_requests/44 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 459755] 5.26 Wayland windows go below Latte when "always visible" is chosen
https://bugs.kde.org/show_bug.cgi?id=459755 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 459755] 5.26 Wayland windows go below Latte when "always visible" is chosen
https://bugs.kde.org/show_bug.cgi?id=459755 --- Comment #12 from Mathias Tillman --- I have the same issue and I've managed to narrow the issue down to WaylandInterface::setViewStruts in app/wm/waylandinterface.cpp. The issue seems to be that the ghost window has a width (or height) of 1 pixel, and that causes it to be (I'm guessing) ignored by the wm. If I change the w->setGeometry call to use the full rect it works properly. I did some further testing, and for me the "magic" value that causes it to work is if I set the width to 88 pixels - any less than that and it won't work. Anyone know the reason for it not using the full rect for the ghost window? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 459755] 5.26 Wayland windows go below Latte when "always visible" is chosen
https://bugs.kde.org/show_bug.cgi?id=459755 --- Comment #13 from Mathias Tillman --- Slight update: Seems that it doesn't like it when the width is smaller than the height (for a top or bottom panel) or vice-versa. The "magic" 88 pixels width in my previous comment was actually the same as the height - that's why it started working when I changed it to that. So I guess a simple solution would be to change the 1 pixel width/height to the height/width counterpart. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483172] Free Disk Space button margin too wide and cuts off fonts
https://bugs.kde.org/show_bug.cgi?id=483172 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com --- Comment #20 from Mathias Tillman --- Can confirm this when upgrading to 6.0 on the user branch. Looks like the whole /usr/share/dbus-1 directory is missing in the build66 package of plasma-workspace. It does exist in build65, however, so something must have happened in-between build66 and build65 that has caused it to not be included anymore. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 457006] Unable to install Calligra
https://bugs.kde.org/show_bug.cgi?id=457006 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com --- Comment #5 from Mathias Tillman --- (In reply to Doug from comment #4) > I'm having this issue now with Testing. Getting a dependency resolution > fail error in Discover. > > when installing from the terminal: > > doug@testing:~$ sudo apt install calligra > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Starting pkgProblemResolver with broken count: 1 > Starting 2 pkgProblemResolver with broken count: 1 > Investigating (0) calligra-libs:amd64 < none -> > 1:3.2.1+p22.04+tstable+git20221007.0143-0 @un puN Ib > > Broken calligra-libs:amd64 Depends on calligra-data:amd64 < none | > 1:3.2.1+p22.04+tstable+git20221007.0143-0 @un uH > (>= > 1:3.2.1+p22.04+tstable+git20221007.0143-0) > Considering calligra-data:amd64 0 as a solution to calligra-libs:amd64 7 > Re-Instated calligra-data:amd64 > Broken calligra-libs:amd64 Depends on libkchart2:amd64 < none | 2.8.0-1 @un > uH > (>= 2.8.0+p22.04+tstable+git20220908.1010) > Broken calligra-libs:amd64 Depends on libm2mml0.0v5:amd64 < none | > 0.9.0-0ubuntu4 @un uH > > Considering libm2mml0.0v5:amd64 1 as a solution to calligra-libs:amd64 7 > Re-Instated libcauchy0.0v5:amd64 > Re-Instated libm2mml0.0v5:amd64 > Broken calligra-libs:amd64 Depends on libphonon4qt5experimental4:amd64 < > none | 4:4.12.0+p22.04+vstable+git20240117.0713-0 @un uH > (>= > 4:4.11.1+p22.04+tunstable+git20220919.0138) > Considering libphonon4qt5experimental4:amd64 0 as a solution to > calligra-libs:amd64 7 > Re-Instated libphonon4qt5experimental4:amd64 > Broken calligra-libs:amd64 Depends on libspnav0:amd64 < none | 0.2.3-1 @un > uH > (>= 0.2.2) > Considering libspnav0:amd64 0 as a solution to calligra-libs:amd64 7 > Re-Instated libspnav0:amd64 > Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > calligra-libs : Depends: libkchart2 (>= > 2.8.0+p22.04+tstable+git20220908.1010) but it is not going to be installed > Recommends: fonts-lyx but it is not going to be installed > Recommends: libqca2-plugins but it is not installable > Recommends: python but it is not installable > E: Unable to correct problems, you have held broken packages. Same here running the latest testing branch of Neon. It seems like on the unstable branch calligra-libs has changed the libkchart2 dependency to libkchart5-2, but on testing it's still libkchart2. This causes a dependency error since libkchart2 isn't updated by neon, whereas libkchart5-2 is. TLDR: The calligra-libs dependencies have to be changed to reference libkchart5-2 instead of libkchart2 on testing. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 457006] Unable to install Calligra
https://bugs.kde.org/show_bug.cgi?id=457006 --- Comment #7 from Mathias Tillman --- (In reply to Jonathan Riddell from comment #6) > Calligra is not well maintained alas. However try now. Can confirm that it's fixed now - thanks for the quick resolution! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com --- Comment #4 from Mathias Tillman --- So I've been experiencing this myself lately, but I believe the original bug is actually a separate issue, it just happens to have the same or similar results. I've done some testing myself, and it seems to have been introduced in v5.24.2. Running a bisect the faulty commit looks to be 00a8de6c011954f379fe6f0542bdc9c502de45f3 (https://invent.kde.org/plasma/kwin/-/commit/00a8de6c011954f379fe6f0542bdc9c502de45f3). I'm not sure why this would cause flickering though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 Mathias Tillman changed: What|Removed |Added CC||vlad.zahorod...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 --- Comment #5 from Mathias Tillman --- Created attachment 147548 --> https://bugs.kde.org/attachment.cgi?id=147548&action=edit Patch to fix window flickering -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421135] Flickering Issue with Blur enabled
https://bugs.kde.org/show_bug.cgi?id=421135 --- Comment #10 from Mathias Tillman --- (In reply to Matt from comment #8) > (In reply to David Edmundson from comment #7) > > Git commit 140c2fb20efa547cda1ff74880a7cdbcab8b5943 by David Edmundson, on > > behalf of Mathias Tillman. > > Committed on 17/03/2022 at 22:19. > > Pushed by davidedmundson into branch 'master'. > > > > effects/blur: Fix window flickering when the clip intersected with the > > current blur region. > > > > This fixes a bug introduced in > > https://invent.kde.org/plasma/kwin/-/merge_requests/2045 where it would no > > longer check if it should redraw the whole region unless the data clip > > intersected. This would lead to flickering in certain cases > > > > M +7-6src/effects/blur/blur.cpp > > > > https://invent.kde.org/plasma/kwin/commit/ > > 140c2fb20efa547cda1ff74880a7cdbcab8b5943 > > Wondering if this bug should really be resolved as fixed? > Matthias says this is a fix for something introduced in 5.24, but the issue > that was reported has been around since at least 5.18. Agreed, it probably shouldn't be marked as fixed. In hindsight I should have opened a separate issue, but since I wasn't sure of what the actual issue was, and it basically matched the flickering of the original issue, I decided to post my findings here. Perhaps this latest conversation should be split into a separate issue (that would be marked as resolved) for archiving purposes? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405016] Dock stays visible when moving mouse in and out quickly
https://bugs.kde.org/show_bug.cgi?id=405016 --- Comment #10 from Mathias Tillman --- I'm going to attempt to compile qt to see if I can find out what's causing this over the coming days. I will report back what I find! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405016] Dock stays visible when moving mouse in and out quickly
https://bugs.kde.org/show_bug.cgi?id=405016 --- Comment #12 from Mathias Tillman --- Do you mean git master? Unfortunately I haven't been able to get that working on my system due to the task manager widget not loading at all. It shows a bunch of errors on startup, so I'm guessing it's not working because of some incompatibility issue. Does it depend on some later plasma framework version? I'm on KDE neon testing which has 5.15.4. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406818] New: Wrong QtGraphicalEffects dependency in CMake
https://bugs.kde.org/show_bug.cgi?id=406818 Bug ID: 406818 Summary: Wrong QtGraphicalEffects dependency in CMake Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: master.ho...@gmail.com Target Milestone: --- SUMMARY The CMakeLists file adds a dependency on QtGraphicalEffects 1.0, but two of the qml files use QtGraphicalEffects 1.2, which causes the shell plasmoid to fail to load on systems that only have 1.0 installed. STEPS TO REPRODUCE 1. Compile git master on a system that only has QtGraphicalEffects 1.0 2. Run it OBSERVED RESULT The shell plasmoid fails to load, which causes problems with the task manager and probably other things. EXPECTED RESULT The shell plasmoid should load properly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: - (available in About System) KDE Plasma Version: - KDE Frameworks Version: - Qt Version: 5.12.0 ADDITIONAL INFORMATION Seems to me like either the CMakeLists.txt file should update the dependency on 1.2, or downgrade the two qml files that depend on 1.2. I manually changed them to import 1.0 instead of 1.2, and it seems to work fine now. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406818] Wrong QtGraphicalEffects dependency in CMake
https://bugs.kde.org/show_bug.cgi?id=406818 --- Comment #2 from Mathias Tillman --- Which solution do you think is best? I've been trying to find QtGraphicalEffects 1.2, but the latest I can find seems to be 1.12 - is 1.2 a part of some unreleased Qt version? I can definitely do a PR, just need to know what solution you want. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405016] Dock stays visible when moving mouse in and out quickly
https://bugs.kde.org/show_bug.cgi?id=405016 --- Comment #14 from Mathias Tillman --- Running git master now, and things are looking good so far. Will report back in a few days after testing it more. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406818] Wrong QtGraphicalEffects dependency in CMake
https://bugs.kde.org/show_bug.cgi?id=406818 Mathias Tillman changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/lat ||te-dock/99454c0b15ba7afbeed ||ea69b0ceb0a7a1f44783a Status|REPORTED|RESOLVED --- Comment #4 from Mathias Tillman --- Git commit 99454c0b15ba7afbeedea69b0ceb0a7a1f44783a by Mathias Tillman. Committed on 23/04/2019 at 20:32. Pushed by mathiastillman into branch 'master'. Import QtGraphicalEffects 1.0 instead of 1.2 to fix dependency issue. Summary: Fixes an issue where the shell plasmoid fails to load when QtGraphicalEffects 1.2 is missing from the system. This causes various issues like the task manager applet failing to load. Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D20774 M +1-1plasmoid/package/contents/ui/taskslayout/ScrollEdgeShadows.qml M +1-1plasmoid/package/contents/ui/taskslayout/ScrollOpacityMask.qml https://commits.kde.org/latte-dock/99454c0b15ba7afbeedea69b0ceb0a7a1f44783a -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405016] Dock stays visible when moving mouse in and out quickly
https://bugs.kde.org/show_bug.cgi?id=405016 --- Comment #15 from Mathias Tillman --- Done some more testing, and it is definitely fixed in git master. To test I checked out 77f7d27c83b2be01a6ad49c09df3f58c489790c1 and the issue is back again, then checked out 834b6477ac53a81541207b9ade8d58051fb4e6d2 and it's fixed. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405016] Dock stays visible when moving mouse in and out quickly
https://bugs.kde.org/show_bug.cgi?id=405016 --- Comment #17 from Mathias Tillman --- Yeah, feels nice when a simple refactor actually fixes something! I backported 834b6477ac53a81541207b9ade8d58051fb4e6d2 to the v0.8 branch, and it looks to be working there as well. Any chance you could push out a new 0.8 release with it fixed? Prefer to stay on the official distro version since I get automatic updates and such that way. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405016] Dock stays visible when moving mouse in and out quickly
https://bugs.kde.org/show_bug.cgi?id=405016 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com --- Comment #4 from Mathias Tillman --- Having the same problem here. I have a theory that it's caused by the user leaving the MouseArea (for the window preview) before it's active, meaning the onContainsMouseChanged signal is never sent. However, I haven't done enough testing to verify this is the case. Unfortunately, it also happens quite rarely for me, so I haven't been able to find a way to reproduce it reliably. I will do some testing and report back what I find. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 405016] Dock stays visible when moving mouse in and out quickly
https://bugs.kde.org/show_bug.cgi?id=405016 --- Comment #5 from Mathias Tillman --- Done some debugging, and I believe this may be a Qt bug. Basically, when this happens, containsMouse is still true for the ToolTipWindowMouseArea component, even though my cursor is clearly outside the window preview. To make this even more clear I tested it by starting a timer that would trigger 1 second after the window preview was shown, and made it output containsMouse. And sure enough, it was true even if my cursor was in the middle of the screen. Looking at the qt code, containsMouse only returns a value that's set when leaving, entering or moving the cursor. If I were to guess, the hoverLeaveEvent is never triggered, causing the internal value to never be updated. I still haven't found a reproducible way to trigger this bug yet, but I am working on it. It just happens randomly when you quickly move the mouse cursor over the window preview, just as it appears. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379524] Fontsettings crashes/stalls when installing/deleting multiple system fonts
https://bugs.kde.org/show_bug.cgi?id=379524 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #7 from Mathias Tillman --- I have sent a review request that should fix this issue here: https://phabricator.kde.org/D14493 Please try the patch if you can and report back. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379324] Deleting System-Fonts causes a freeze of systemsettings
https://bugs.kde.org/show_bug.cgi?id=379324 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #6 from Mathias Tillman --- I have sent a review request that should fix this issue here: https://phabricator.kde.org/D14493 Please try the patch if you can and report back. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392267] Font Installer hangs at 100% when installing a system font
https://bugs.kde.org/show_bug.cgi?id=392267 Mathias Tillman changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/60c895758f20bd2 ||cb17ab12e57cf34cc37197098 Resolution|--- |FIXED --- Comment #1 from Mathias Tillman --- Git commit 60c895758f20bd2cb17ab12e57cf34cc37197098 by Mathias Tillman. Committed on 31/07/2018 at 10:40. Pushed by mathiastillman into branch 'master'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379524, bug 379324, bug 349673, bug 361960 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 M +4-0kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/60c895758f20bd2cb17ab12e57cf34cc37197098 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379524] Fontsettings crashes/stalls when installing/deleting multiple system fonts
https://bugs.kde.org/show_bug.cgi?id=379524 Mathias Tillman changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/60c895758f20bd2 ||cb17ab12e57cf34cc37197098 --- Comment #8 from Mathias Tillman --- Git commit 60c895758f20bd2cb17ab12e57cf34cc37197098 by Mathias Tillman. Committed on 31/07/2018 at 10:40. Pushed by mathiastillman into branch 'master'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379324, bug 349673, bug 361960, bug 392267 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 M +4-0kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/60c895758f20bd2cb17ab12e57cf34cc37197098 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 349673] kcm_fontinst: Backend crashes on systemwide fonts installations
https://bugs.kde.org/show_bug.cgi?id=349673 Mathias Tillman changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/60c895758f20bd2 ||cb17ab12e57cf34cc37197098 Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #14 from Mathias Tillman --- Git commit 60c895758f20bd2cb17ab12e57cf34cc37197098 by Mathias Tillman. Committed on 31/07/2018 at 10:40. Pushed by mathiastillman into branch 'master'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379524, bug 379324, bug 361960, bug 392267 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 M +4-0kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/60c895758f20bd2cb17ab12e57cf34cc37197098 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379324] Deleting System-Fonts causes a freeze of systemsettings
https://bugs.kde.org/show_bug.cgi?id=379324 Mathias Tillman changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-desktop/60c895758f20bd2 ||cb17ab12e57cf34cc37197098 --- Comment #7 from Mathias Tillman --- Git commit 60c895758f20bd2cb17ab12e57cf34cc37197098 by Mathias Tillman. Committed on 31/07/2018 at 10:40. Pushed by mathiastillman into branch 'master'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379524, bug 349673, bug 361960, bug 392267 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 M +4-0kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/60c895758f20bd2cb17ab12e57cf34cc37197098 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 361960] kfontinst freezes adding fonts to system
https://bugs.kde.org/show_bug.cgi?id=361960 Mathias Tillman changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/60c895758f20bd2 ||cb17ab12e57cf34cc37197098 --- Comment #12 from Mathias Tillman --- Git commit 60c895758f20bd2cb17ab12e57cf34cc37197098 by Mathias Tillman. Committed on 31/07/2018 at 10:40. Pushed by mathiastillman into branch 'master'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379524, bug 379324, bug 349673, bug 392267 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 M +4-0kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/60c895758f20bd2cb17ab12e57cf34cc37197098 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379524] Fontsettings crashes/stalls when installing/deleting multiple system fonts
https://bugs.kde.org/show_bug.cgi?id=379524 Mathias Tillman changed: What|Removed |Added Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla |sma-desktop/60c895758f20bd2 |sma-desktop/690570a4cefd786 |cb17ab12e57cf34cc37197098 |db5113ca237e9bdb48cd50812 --- Comment #9 from Mathias Tillman --- Git commit 690570a4cefd786db5113ca237e9bdb48cd50812 by Mathias Tillman. Committed on 02/08/2018 at 07:33. Pushed by mathiastillman into branch 'Plasma/5.12'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379324, bug 349673, bug 361960, bug 392267 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 (cherry picked from commit 60c895758f20bd2cb17ab12e57cf34cc37197098) M +4-0kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/690570a4cefd786db5113ca237e9bdb48cd50812 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 361960] kfontinst freezes adding fonts to system
https://bugs.kde.org/show_bug.cgi?id=361960 Mathias Tillman changed: What|Removed |Added Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla |sma-desktop/60c895758f20bd2 |sma-desktop/690570a4cefd786 |cb17ab12e57cf34cc37197098 |db5113ca237e9bdb48cd50812 --- Comment #13 from Mathias Tillman --- Git commit 690570a4cefd786db5113ca237e9bdb48cd50812 by Mathias Tillman. Committed on 02/08/2018 at 07:33. Pushed by mathiastillman into branch 'Plasma/5.12'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379524, bug 379324, bug 349673, bug 392267 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 (cherry picked from commit 60c895758f20bd2cb17ab12e57cf34cc37197098) M +4-0kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/690570a4cefd786db5113ca237e9bdb48cd50812 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 349673] kcm_fontinst: Backend crashes on systemwide fonts installations
https://bugs.kde.org/show_bug.cgi?id=349673 Mathias Tillman changed: What|Removed |Added Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla |sma-desktop/60c895758f20bd2 |sma-desktop/690570a4cefd786 |cb17ab12e57cf34cc37197098 |db5113ca237e9bdb48cd50812 --- Comment #16 from Mathias Tillman --- Git commit 690570a4cefd786db5113ca237e9bdb48cd50812 by Mathias Tillman. Committed on 02/08/2018 at 07:33. Pushed by mathiastillman into branch 'Plasma/5.12'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379524, bug 379324, bug 361960, bug 392267 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 (cherry picked from commit 60c895758f20bd2cb17ab12e57cf34cc37197098) M +4-0kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/690570a4cefd786db5113ca237e9bdb48cd50812 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392267] Font Installer hangs at 100% when installing a system font
https://bugs.kde.org/show_bug.cgi?id=392267 Mathias Tillman changed: What|Removed |Added Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla |sma-desktop/60c895758f20bd2 |sma-desktop/690570a4cefd786 |cb17ab12e57cf34cc37197098 |db5113ca237e9bdb48cd50812 --- Comment #2 from Mathias Tillman --- Git commit 690570a4cefd786db5113ca237e9bdb48cd50812 by Mathias Tillman. Committed on 02/08/2018 at 07:33. Pushed by mathiastillman into branch 'Plasma/5.12'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379524, bug 379324, bug 349673, bug 361960 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 (cherry picked from commit 60c895758f20bd2cb17ab12e57cf34cc37197098) M +4-0kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/690570a4cefd786db5113ca237e9bdb48cd50812 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 379324] Deleting System-Fonts causes a freeze of systemsettings
https://bugs.kde.org/show_bug.cgi?id=379324 Mathias Tillman changed: What|Removed |Added Latest Commit|https://commits.kde.org/pla |https://commits.kde.org/pla |sma-desktop/60c895758f20bd2 |sma-desktop/690570a4cefd786 |cb17ab12e57cf34cc37197098 |db5113ca237e9bdb48cd50812 --- Comment #8 from Mathias Tillman --- Git commit 690570a4cefd786db5113ca237e9bdb48cd50812 by Mathias Tillman. Committed on 02/08/2018 at 07:33. Pushed by mathiastillman into branch 'Plasma/5.12'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379524, bug 349673, bug 361960, bug 392267 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 (cherry picked from commit 60c895758f20bd2cb17ab12e57cf34cc37197098) M +4-0kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/690570a4cefd786db5113ca237e9bdb48cd50812 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404234] plasmoid previews not working
https://bugs.kde.org/show_bug.cgi?id=404234 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com --- Comment #6 from Mathias Tillman --- Just wanted to chime in that I'm having the same problem since updating to plasma 5.15. Any ETA on when 0.8.6 will be available? I'll have a go at compiling the latest code from git and see if it's fixed there. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404234] plasmoid previews not working with plasma 5.15
https://bugs.kde.org/show_bug.cgi?id=404234 --- Comment #11 from Mathias Tillman --- I've posted a patch here which should fix this issue: https://phabricator.kde.org/D19002 Feel free to give it a try. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404234] plasmoid previews not working with plasma 5.15
https://bugs.kde.org/show_bug.cgi?id=404234 Mathias Tillman changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/lat ||te-dock/ddb941d4656cf54eec4 ||8d0cec7c9569d34a409d1 --- Comment #14 from Mathias Tillman --- Git commit ddb941d4656cf54eec48d0cec7c9569d34a409d1 by Mathias Tillman. Committed on 14/02/2019 at 13:01. Pushed by mathiastillman into branch 'master'. Fix window thumbnails not working since frameworks 5.55 Summary: This fixes a problem where window thumbnails are no longer visible since KDE Frameworks 5.55. This is caused by https://cgit.kde.org/plasma-framework.git/commit/?id=b257029afc3bfcd6366d2c2b910b8d91403ab8a which no longer automatically updates the visibility of mainItem of PlasmaCore.Dialog. Test Plan: Ensure window thumbnails are working correctly now Reviewers: mvourlakos Reviewed By: mvourlakos Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D19002 M +2-0plasmoid/package/contents/ui/main.qml https://commits.kde.org/latte-dock/ddb941d4656cf54eec48d0cec7c9569d34a409d1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499871] Changing months too fast leads to a re-triggered animation but no month change
https://bugs.kde.org/show_bug.cgi?id=499871 Mathias Tillman changed: What|Removed |Added Resolution|FIXED |--- CC||master.ho...@gmail.com Status|RESOLVED|REOPENED --- Comment #2 from Mathias Tillman --- Accidentally pushed the commit with the fix to the master branch (sorry!). Have created an MR here: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5275 so reopening until it's been approved. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 474981] Searching for "shutdown", "restart" or "sleep" brings up the "Desktop Session" KCM instead of performing the actions themselves
https://bugs.kde.org/show_bug.cgi?id=474981 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com --- Comment #5 from Mathias Tillman --- I'm not able to reproduce this on 6.3.1. Searching for 'shutdown', 'restart' etc both on the application dashboard and regular krunner brings up the relevant option, and clicking it performs the action (with the usual countdown). Maybe it's been resolved? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 474981] Searching for "shutdown", "restart" or "sleep" brings up the "Desktop Session" KCM instead of performing the actions themselves
https://bugs.kde.org/show_bug.cgi?id=474981 --- Comment #7 from Mathias Tillman --- (In reply to Nate Graham from comment #6) > I can still reproduce it on git masterA theory: this is caused by the fact > that by default, we make Applications and System Settings "favorite" > runners. Because the item for the Desktop Session KCM matches, and it's a > System Settings page, it gets put first even though it's not the best match. > > That would make this "intentional, though not ideal". Worth thinking about. You're right, I see it now. And yes, this does seem like it will be because of the favourites list. I don't know if there's an easy solution that would please everyone, but I feel like search matches that match text in the display title of the result should be prioritised higher than ones that don't. But that might lead to some confusion as well since it won't always match the ordering of the favourites list. See, eg, https://bugs.kde.org/show_bug.cgi?id=489866 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 489866] Krunner doesn't order search results based on my preferred order
https://bugs.kde.org/show_bug.cgi?id=489866 Mathias Tillman changed: What|Removed |Added CC||master.ho...@gmail.com --- Comment #13 from Mathias Tillman --- Can confirm that the ordering seems to be a bit off, and that reverting the commit above (d02e1c13a9ee92a90218a4584a3642f39da4e28a) restores the old behaviour. It was introduced in the MR https://invent.kde.org/frameworks/krunner/-/merge_requests/168. I will ask the maintainer about the intended behaviour there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 499871] Changing months too fast leads to a re-triggered animation but no month change
https://bugs.kde.org/show_bug.cgi?id=499871 Mathias Tillman changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/aba4911be4fdd8c3bf2084655 ||5f4512700727f4f Resolution|--- |FIXED --- Comment #1 from Mathias Tillman --- Git commit aba4911be4fdd8c3bf20846555f4512700727f4f by Mathias Tillman. Committed on 01/03/2025 at 12:39. Pushed by mathiastillman into branch 'master'. components/calendar: Fix previous/next buttons not always working When you pressed the next or previous button in quick succession it wouldn't always change the view since it waited for the animation to end before actually changing the backend value. Fix this by checking if we are moving through the velocity value, and if so, trigger the next/previous in the backend. M +26 -18 components/calendar/qml/InfiniteList.qml M +2-0components/calendar/qml/MonthView.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/aba4911be4fdd8c3bf20846555f4512700727f4f -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 358159] New: ktraderclient5 returns the wrong order for x-scheme-handler/magnet
https://bugs.kde.org/show_bug.cgi?id=358159 Bug ID: 358159 Summary: ktraderclient5 returns the wrong order for x-scheme-handler/magnet Product: frameworks-kservice Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: master.ho...@gmail.com CC: kdelibs-b...@kde.org I've noticed that magnet links are always opened in ktorrent, when I want them to open in qBittorrent. I have x-scheme-handler/magnet=qBittorrent.desktop set under Default Applications in mimeapps.list, and yet they still open in ktorrent. I did some digging and found that xdg-open uses ktraderclient5 (when using kde frameworks 5) to find what program it should open, and calling ktraderclient5 --mimetype x-scheme-handler/magnet --servicetype Application does indeed return the wrong order, with ktorrent being offer 0 and qbittorrent being offer 1. I tried calling ktraderclient (the kde 4 version), and that returns the correct order. If I run xdg-mime default qBittorrent.desktop x-scheme-handler/magnet it works for a little while, but then seems to reset itself. I'm not sure why or how. Reproducible: Always Steps to Reproduce: 1. Try to open a magnet link using xdg-open 2. 3. Actual Results: ktorrent opens even though I have qBittorrent set as the default. Expected Results: qBittorrent should open. Running Kubuntu 15.10 with kde framework 5.15.0 and plasma 5.4.3. -- You are receiving this mail because: You are watching all bug changes.
