[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 --- Comment #33 from JonnyRobbie --- Is there any investigation ongoing? Would the fix come in the next bug release or at least in 6.1? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 JonnyRobbie changed: What|Removed |Added CC||marc...@seznam.cz --- Comment #24 from JonnyRobbie --- I wanted to chime in with the reproduction. 1440p@150%, I have a glitch line on the right side of the monitor. It's most noticeable when there's a full screen app, like firefox video fullscreen, mpv fullscreen or a video game. I also do have a secondary 4k monitor/tv connected at 200% and I don't notice the scaling bug there. -- 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 Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #41 from JonnyRobbie --- One thing I don't understand - this seems like a regression. It was fine in 5.26, but appeared in 5.27. Now I know enough that asking "how hard could it be" is an unfortunate question, so I'll try to rephrase that: have we managed to bisect towards the offending commit that it would help us diagnose the issue and point towards a solution? -- 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 Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #29 from JonnyRobbie --- Still present in 5.27.3 -- 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 Blur or Background Contrast effects turned on
https://bugs.kde.org/show_bug.cgi?id=465158 --- Comment #28 from JonnyRobbie --- Can I ask what is the current status? Has it been reproduced by developers? Will it be fixed in .3? Is there something more we can do to help? -- 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 #24 from JonnyRobbie --- I have to say that 5.27.2 didn't fix this for me :( In fact, it might be even worse. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466247] Minimize and maximize shortcuts for window stopped working
https://bugs.kde.org/show_bug.cgi?id=466247 --- Comment #5 from JonnyRobbie --- Hm, yes, moving away the old global shortcuts config worked around the issue and all the default shortcuts are now working. It wouldn't be a massive issue for me to leave it as I didn't have that many custom shortcuts anyway, but what could be the cause? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466247] Minimize and maximize shortcuts for window stopped working
https://bugs.kde.org/show_bug.cgi?id=466247 JonnyRobbie changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from JonnyRobbie --- Yes, it's wayland. Thought it's interesting, because most of the kwin shortcuts doesn't work, but some of the shortcuts do work - so it's not like all of the global shortcuts stopped working completely. work move mouse to center: meta+f6 mouse to focus: meta+f5 show desk grid: ctrl+f8 toggle present all: alt+tab toggle present current desk/window: ctrl+f9/f7 toggle tiles: meta+t zoom in/out: meta+=/- don't work close window: alt+f4 kill window: ctrl+alt+esc maximize: meta+pgup minimize: meta+pgdn switch to desktop x: ctrl+fx quick tile u+b+l+r: meta+down/up/left/right swithc to window above, bellow, left, right: meta+alt+u/d/l/r toggle invert/on window: meta+ctrl+i/u toggle mouse click effect: meta+* walk through wins/reverse: ctrl+alt+tab/alt+shift+backtab (ok, hold on a minute - backtab?) walk through wins current app/reverse: alt+`/~ window operations menu: alt+f3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466247] Minimize and maximize shortcuts for window stopped working
https://bugs.kde.org/show_bug.cgi?id=466247 JonnyRobbie changed: What|Removed |Added CC||marc...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466247] New: Minimize and maximize shortcuts for window stopped working
https://bugs.kde.org/show_bug.cgi?id=466247 Bug ID: 466247 Summary: Minimize and maximize shortcuts for window stopped working Classification: Plasma Product: kwin Version: 5.27.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: marc...@seznam.cz Target Milestone: --- SUMMARY Window minimization and maximization stopped working with shortcuts STEPS TO REPRODUCE 1. Go to Settings-Shortcuts-KWin-Minimize Window 2. Add a shortcut (ie. Meta+PgDown) 3. Press meta+pgdown OBSERVED RESULT Nothing EXPECTED RESULT Minimized window SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103 Qt Version: 5.15.8 ADDITIONAL INFORMATION This seems like a regression in .1 - I think it worked in 5.27 -- 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 #22 from JonnyRobbie --- I have to say that upgrading to 5.27.1 did not help. Still seeing white flickering border and artifacts. -- 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 #16 from JonnyRobbie --- (In reply to Mathias Tillman from comment #15) > @JonnyRobbie Do the lines go away of you disable the Blur effect? Both Blur AND Background Contrast has to be turned off for the lines to disappear. If either one is on, the lines are there. Also, not sure if its a symptom of the same cause - the white highlight border around the window seems like it's a pixel away from the actual window. You can see it in the photo I've attached before. -- 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 JonnyRobbie changed: What|Removed |Added CC||marc...@seznam.cz --- Comment #14 from JonnyRobbie --- Created attachment 156441 --> https://bugs.kde.org/attachment.cgi?id=156441=edit photo of a monitor with white lines around windows I can also reproduce the issue. 150% scaling, wayland. Funny thing it stops being a problem when I try to screen capture it with spectacle. I have to take a photo of a monitor to demonstrate. 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.27.0 Qt Version: 5.15.8 Qt compile version: 5.15.8 XCB compile version: 1.15 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: 12201008 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: Breeze Plugin recommends border size: None onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 5, 3, 4 decorationButtonsRight: 1, 2 borderSize: 0 gridUnit: 10 font: Noto 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: false clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 100 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: activationDesktopPolicy: 0 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: 16777251 condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 2 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-2 Enabled: 0 Screen 1: - Name: DP-3 Enabled: 1 Geometry: 0,0,1707x960 Scale: 1.5 Refresh Rate: 143856 Adaptive Sync: never Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 580 Series (polaris10, LLVM 15.0.7, DRM 3.49, 6.1.12-arch1-1) OpenGL version string: 4.6 (Core Profile) Mesa 22.3.4 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.4 X server version: 1.22.1 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 screenedge zoom blur contrast kwin4_effect_login kwin4_effect_sessionquit kwin4_effect_logout slidingpopups kwin4_effect_windowaperture slide slideb
[konsole] [Bug 378610] Konsole fails to render bitmap fonts properly above codepoint 255
https://bugs.kde.org/show_bug.cgi?id=378610 --- Comment #6 from JonnyRobbie --- I now use 1.5 display scaling, so I hope this doesn't affect this, but it seems like it works fine now. The font does not get scaled, but it is expected from a bitmap font. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 162211] Copying to an external causes lots of missing files
https://bugs.kde.org/show_bug.cgi?id=162211 JonnyRobbie changed: What|Removed |Added CC||marc...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393610] Wish for Debugger console do be disabled
https://bugs.kde.org/show_bug.cgi?id=393610 --- Comment #2 from JonnyRobbie <marc...@seznam.cz> --- Thanks for the info. I just want to thank you for your work on RKWard. I really love it, way more then RStudio and I tend to get itchy when people act like there is no alternative leading to absurd notions like the misconception that RStudio *is* R. However there were couple of usecases I noticed from coworkers where rkward is slightly lacking behind rstudio and those are mainly those I tried to address in my bugreports/suggestions. I don't know how much time/will you have regarding those, but if I can so something to help (apart of the actual coding where I don't have the necessary experience), just tell me. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393612] Add an option to search for function declarations
https://bugs.kde.org/show_bug.cgi?id=393612 JonnyRobbie <marc...@seznam.cz> changed: What|Removed |Added CC||marc...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393611] Option to search in all opened script files
https://bugs.kde.org/show_bug.cgi?id=393611 JonnyRobbie <marc...@seznam.cz> changed: What|Removed |Added CC||marc...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393609] Debugger Console font and theme cannot be changed
https://bugs.kde.org/show_bug.cgi?id=393609 JonnyRobbie <marc...@seznam.cz> changed: What|Removed |Added CC||marc...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393610] Wish for Debugger console do be disabled
https://bugs.kde.org/show_bug.cgi?id=393610 JonnyRobbie <marc...@seznam.cz> changed: What|Removed |Added CC||marc...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393612] New: Add an option to search for function declarations
https://bugs.kde.org/show_bug.cgi?id=393612 Bug ID: 393612 Summary: Add an option to search for function declarations Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: marc...@seznam.cz Target Milestone: --- This wish is coupled with #393611. Please add an option to search for function declarations. Perhaps form the find bar accessible with a special shortcut. Perhaps utilizing some form of search regex alias like: [ \t]?%s[ \t]?((<\-)|(=))[ \t]?function[ \t]?\( -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393611] New: Option to search in all opened script files
https://bugs.kde.org/show_bug.cgi?id=393611 Bug ID: 393611 Summary: Option to search in all opened script files Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: marc...@seznam.cz Target Milestone: --- Perhaps this feature already exists, but simply couldn't find it. `Edit -> Find` or Ctrl+F gives you the option to search only in the current script file which is in focus. Please consider adding an option to search in all opened script files from one place. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393610] New: Wish for Debugger console do be disabled
https://bugs.kde.org/show_bug.cgi?id=393610 Bug ID: 393610 Summary: Wish for Debugger console do be disabled Product: rkward Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: marc...@seznam.cz Target Milestone: --- This is a wishlist coupled with #393609. Please add an option to disable the *Debugger Console* and redirect all of its functionality to plain *R Console*. Perhaps with optional sidebar with "Next", "Step out", "Continue" and "Cancel" buttons which shows up when the RKWard detects a debugger context (and whose should be complete according to `browser()` implementation - see `?browser`). I would like to know the historical reason behind the decoupling of R Console and Debugger Console, especially when there is also a Debugger Frames window. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393609] New: Debugger Console font and theme cannot be changed
https://bugs.kde.org/show_bug.cgi?id=393609 Bug ID: 393609 Summary: Debugger Console font and theme cannot be changed Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: marc...@seznam.cz Target Milestone: --- Debugger Console font and theme cannot be changed. The R Console tab/window (and the script editor) can be themed with Kate themes. However the debugger console is stuck with default theme. This causes several issues, for example not being able to have a dark theme and more annoyingly a non-changeable proportional font, instead of being able to use chosen monospaced one. ---Session Info--- -- Frontend -- RKWard version: 0.7.0z+0.7.1+devel1 KDE Frameworks version (runtime): 5.45.0 KDE Frameworks version (compile time): 5.45.0 Qt version (runtime): 5.10.1 Local config directory: /home/marek/.config RKWard storage directory: /home/marek/.rkward/ Backend version (as known to the frontend): 3.5.0 Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.frontend -- Backend -- Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.rbackend R version (compile time): 3.5.0 (2018-04-23 r74626) R runtime session info: R version 3.5.0 (2018-04-23) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Arch Linux Matrix products: default BLAS: /usr/lib/libblas.so.3.8.0 LAPACK: /usr/lib/liblapack.so.3.8.0 locale: [1] LC_CTYPE=en_GB.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_NG.UTF-8 LC_COLLATE=en_GB.UTF-8 [5] LC_MONETARY=cs_CZ.UTF-8 LC_MESSAGES=en_GB.UTF-8 [7] LC_PAPER=en_GB.UTF-8 LC_NAME=en_GB.UTF-8 [9] LC_ADDRESS=cs_CZ.UTF-8LC_TELEPHONE=en_GB.UTF-8 [11] LC_MEASUREMENT=en_GB.UTF-8LC_IDENTIFICATION=en_GB.UTF-8 attached base packages: [1] stats graphics grDevices utils datasets methods base other attached packages: [1] gridExtra_2.3 MASS_7.3-49 rkward_0.7.1 loaded via a namespace (and not attached): [1] compiler_3.5.0 tools_3.5.0gtable_0.2.0 grid_3.5.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391486] Epoxy 1.5 breaks OpenGL compositing
https://bugs.kde.org/show_bug.cgi?id=391486 --- Comment #22 from JonnyRobbie <marc...@seznam.cz> --- Arch is somewhat a hybrid between source based and binary based distros. The main repos are binary, but you can use it's ports-like system and build easily for yourself if you need some advanced compile-time options, like debug symbols etc. I managed to build 1.5.0 by skipping the check() routine. Will post trace as soon as possible. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391486] Epoxy 1.5 breaks OpenGL compositing
https://bugs.kde.org/show_bug.cgi?id=391486 --- Comment #19 from JonnyRobbie <marc...@seznam.cz> --- No, the 1.5.0 I'm getting the main trouble is a precompiled binary from arch repos, which I can get to install, but gives me trouble, but presumably without debug symbols. I'm not able to build 1.5.0 on my own to get debug symbols in. I could patch out the offending commit I found in the bisect, but that would bias this whole thing, I think. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391486] Epoxy 1.5 breaks OpenGL compositing
https://bugs.kde.org/show_bug.cgi?id=391486 --- Comment #17 from JonnyRobbie <marc...@seznam.cz> --- Do you want debugging symbols from epoxyinfo or libepoxy? Because it seems that I'm not able to build libepoxy-1.5.0. see https://github.com/anholt/libepoxy/issues/160#issuecomment-371422087 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391486] Epoxy 1.5 breaks OpenGL compositing
https://bugs.kde.org/show_bug.cgi?id=391486 --- Comment #15 from JonnyRobbie <marc...@seznam.cz> --- @ajax: See attachments. glxinfo and epoxyinfo @ libepoxy-1.4.3 and glxinfo @ libepoxy-1.5.0. Interestingly, epoxyinfo @ libepoxy 1.5.0 segfaults. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391486] Epoxy 1.5 breaks OpenGL compositing
https://bugs.kde.org/show_bug.cgi?id=391486 --- Comment #14 from JonnyRobbie <marc...@seznam.cz> --- Created attachment 111253 --> https://bugs.kde.org/attachment.cgi?id=111253=edit glxinfo-libepoxy150 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391486] Epoxy 1.5 breaks OpenGL compositing
https://bugs.kde.org/show_bug.cgi?id=391486 --- Comment #13 from JonnyRobbie <marc...@seznam.cz> --- Created attachment 111252 --> https://bugs.kde.org/attachment.cgi?id=111252=edit epoxyinfo-libepoxy143 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391486] Epoxy 1.5 breaks OpenGL compositing
https://bugs.kde.org/show_bug.cgi?id=391486 --- Comment #12 from JonnyRobbie <marc...@seznam.cz> --- Created attachment 111251 --> https://bugs.kde.org/attachment.cgi?id=111251=edit glxinfo-libepoxy143 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391486] Epoxy 1.5 breaks OpenGL compositing
https://bugs.kde.org/show_bug.cgi?id=391486 --- Comment #9 from JonnyRobbie <marc...@seznam.cz> --- While I agree that a distro update breaking the dependecy is most certainly not in the greatest of styles and in that regard, there is something left to be desired, it is worth noting that if the issue really is some interface change in libepoxy, then the solution certainly is not for KWin to keep at the mercy of old and depreciated dependencies forever. If the libepoxy change is not some unfortunate regression that will be solved in the nearest patch, but an intentional change, then we may be upset of libepoxy maintainer all we want for breaking some of the most basic principle not dissimilar to Linux's 'Don't break the userspace - ever', but that doesn't change the fact that it happened. Now, I don't know enough to realize where the real problem is, the worst outcome would be when the users are caught between tho hard heads. I just hope the issue gets solved quickly and for that I'm participating in a way I've been told is most helpful for a non-developer - bug reporting (or in this case just participating, I guess). I'm sorry for being slightly hotheaded and marking the issue as confirmed without much proof. I'll try to be more composed next time. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391486] Epoxy 1.5 breaks OpenGL compositing
https://bugs.kde.org/show_bug.cgi?id=391486 JonnyRobbie <marc...@seznam.cz> changed: What|Removed |Added CC||marc...@seznam.cz Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from JonnyRobbie <marc...@seznam.cz> --- I can confirm this bug. It happeneded after an update of libepoxy from 1.4.3 to 1.5.0. I don't know if this is a libepoxy or kwin issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375976] appmenu not shown for gtk apps
https://bugs.kde.org/show_bug.cgi?id=375976 --- Comment #10 from JonnyRobbie <marc...@seznam.cz> --- Yes: $ plasmashell --version plasmashell 5.11.1 Using local/plasma5-applets-active-window-control-git r147.341276f-1 with 'System Settings-Application Style-Widget Style-Menubar Style' set to 'Application Menu Widget'. Konsole (for example) has properly rendered menu: https://i.imgur.com/Vg7E3eZ.png LOcalc has missing menu: https://i.imgur.com/x6qs7AN.png it is worth noting, that the menu is missing with SAL_USE_VCLPLUGIN=gtk3, I'd understand that the gtk menu is not supported, I got it, but then it shouldn't touch the menu at all and leave it alone and not hide it without replacement. Using SAL_USE_VCLPLUGIN=kde4, the menu is still there, but LO is hideous: https://i.imgur.com/qXmY2Kl.png (not to mention, it still probably has that ugly gradient with dark theme) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375976] appmenu not shown for gtk apps
https://bugs.kde.org/show_bug.cgi?id=375976 --- Comment #8 from JonnyRobbie <marc...@seznam.cz> --- Certainly, but even gtk apps show the appmenu again if I restore 'Menubar Style: In application' setting. So there has to be something in plasma telling LibreOffice to hide the menu. I don't think it's the gtk app hiding it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375976] appmenu not shown for gtk apps
https://bugs.kde.org/show_bug.cgi?id=375976 JonnyRobbie <marc...@seznam.cz> changed: What|Removed |Added CC||marc...@seznam.cz --- Comment #6 from JonnyRobbie <marc...@seznam.cz> --- I understand that it may not be easy to move gtk appmenu to the global widget. However I don't understand the necessity to remove it altogether. Let Qt apps have its globalmenu and leave incapable gtk aps with its local menu. What I don't understand is why do the gtk apps need to lose their menu altogether? Clearly kwin (or whichever component is responsible) is capable and even acting on removing those menus from gtk apps, why not just leave it alone then? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344706] KMenu won't show sometimes (multi-monitor setup)
https://bugs.kde.org/show_bug.cgi?id=344706 JonnyRobbie <marc...@seznam.cz> changed: What|Removed |Added CC||marc...@seznam.cz --- Comment #40 from JonnyRobbie <marc...@seznam.cz> --- Yeah, coming here with the same problem. Multimonitor setup, KF 3.34.0, Qt 5.8.0, Plasma 5.10.0, 4.11.3-1-ARCH x86_64. The bug was there with high focus stealing prevention. Turning it down to medium seem to have fixed (or at least mitigated) the bug. -- You are receiving this mail because: You are watching all bug changes.
