[kwin] [Bug 477124] cursor is able to escape a fullscreen, window, borderless in apex legends under plasma 5.92.0/rc1 wayland
https://bugs.kde.org/show_bug.cgi?id=477124 --- Comment #19 from Ashcon Mohseninia --- Done. Filed bug 484835 for this -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484835] New: Proton games do not lock onto game window on a multi-monitor setup since 6.0.x
https://bugs.kde.org/show_bug.cgi?id=484835 Bug ID: 484835 Summary: Proton games do not lock onto game window on a multi-monitor setup since 6.0.x Classification: Plasma Product: kwin Version: 6.0.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ashco...@gmail.com Target Milestone: --- Created attachment 167998 --> https://bugs.kde.org/attachment.cgi?id=167998=edit Demo showing the bug SUMMARY When playing a game on a multi-monitor setup, the mouse can escape the main monitor (Where the game is being played), but is teleported back to the window fairly quickly. The issue is that when it is outside the window, clicking (IE: Firing a weapon), instead causes the focus of the game to be lost, and the other monitors become the focus. What is interesting, is since 6.0.3, the game still looks around as if the mouse is still present in the game window. Pre 6.0.3, the mouse would move outside the window and the game would stop looking around. STEPS TO REPRODUCE 1. Play a proton Game on any version of plasma 6.0.x on a multi-monitor setup 2. Try to look around 3. Notice that the mouse is escaping the main game window. I've attached a video here to show the bug in action SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477124] cursor is able to escape a fullscreen, window, borderless in apex legends under plasma 5.92.0/rc1 wayland
https://bugs.kde.org/show_bug.cgi?id=477124 Ashcon Mohseninia changed: What|Removed |Added CC||ashco...@gmail.com --- Comment #17 from Ashcon Mohseninia --- KWIN 6.0.3 on wayland, playing Fallout 4 on a multi-screen setup, still experiencing this issue. However, it appears a little different. when looking around, the mouse appears for a split second on my other monitors, but then goes back into the game window. The issue here is that when clicking (Example when shooting), if the house has escaped the window at this exact moment, then the click is registered in another open window, and the game minimises itself. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481554] New: Wayland + Nvidia - Extreme stuttering doing anything
https://bugs.kde.org/show_bug.cgi?id=481554 Bug ID: 481554 Summary: Wayland + Nvidia - Extreme stuttering doing anything Classification: Plasma Product: kwin Version: 5.93.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ashco...@gmail.com Target Milestone: --- SUMMARY *** On a hybrid setup (External monitors connected to NVIDIA GPU, laptop display connected to internal intel GPU), there is extreme stuttering of the UI, GLXGears will run at 1/2 the refresh rate of the displays. *** (Note, on plasma 5.x, using `KWIN_DRM_USE_MODIFIERS=0` would resolve this issue, but in 6.x, either this env. variable is ignored, or does nothing) I've attached a video showing this issue, both my external monitors are 120Hz, and the laptops own display is 144Hz, so theoretically, the minimum framerate I should get is 120Hz, but, you can see when doing anything like moving windows around, the glxgear window stutters and framerate drops significantly1. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457359] New: Present windows takes too long to display itself and will close itself immediately when hotcorner is activated more than once
https://bugs.kde.org/show_bug.cgi?id=457359 Bug ID: 457359 Summary: Present windows takes too long to display itself and will close itself immediately when hotcorner is activated more than once Product: kwin Version: 5.25.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: ashco...@gmail.com Target Milestone: --- SUMMARY When using the present windows effect via the mouse hot corner (Mainly on a multi-monitor setup), it can take up to 2-3 seconds for it to actually show itself. This makes the effect appear unresponsive, so naturally you will end up trying to activate the hot corner more than onces. Issue with doing that is once you have tapped the corner more than once, and the present windows effect finally does display itself, it will immediately close itself due to the double activation of the hot corner STEPS TO REPRODUCE (Scenario A) 1. Open 10-20 windows on a multi monitor setup 2. Activate the present windows via the hotcorner 3. Observe a long lag time between hot corner activation and the effect starting STEPS TO REPRODUCE (Scenario B) 1. Open 10-20 windows on a multi monitor setup 2. Activate the present windows via the hotcorner, then activate the hot corner again whilst the effect still hasn't shown yet 3. Observe after some time, the present windows effect will show, then immediately close itself OBSERVED RESULT The long lag time with showing present windows combined with multiple hot corner activation will result in the effect lagging out, then immediately closing itself EXPECTED RESULT Hot corner activation should be disabled once the effect was first called, so erroneous double tapping of it would not trigger the effect to immediately close itself before the effect has actually shown. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439329] New: Launching source engine games causes compositor to slow to a crawl after game exits
https://bugs.kde.org/show_bug.cgi?id=439329 Bug ID: 439329 Summary: Launching source engine games causes compositor to slow to a crawl after game exits Product: kwin Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ashco...@gmail.com Target Milestone: --- SUMMARY I've tried this with multiple source engine 1 games (TF2, HL2, Portal 2), and all exhibit the same behavior, however this is not observed with other games such as cities skylines or KSP (Unity engine). After launching one of the effected games and playing for a bit, all is smooth. However as soon as the game exits, window dragging and animations are at around 5-10fps. This problem gets worse and worse the more you open and close the effected games. Halting the compositor (ALT+SHIFT+F12) makes the problem go away, however re-enabling the compositor makes everything sluggish once again. Unticking "Allow applications to block compositing" has no effect on this. Weather its enabled or not, as soon as the game exists a noticeable slow-down is observed. It should be noted however that during these slow-downs, 3D applications are unaffected (I can re-launch a game whilst having slowdowns and the games are unaffected). STEPS TO REPRODUCE 1. Open a source engine game 2. Play for a bit, then close it 3. Drag some windows around, it will be far more sluggish than before OBSERVED RESULT After the game is closed, the compositor is noticeably slower than prior to launching the game. Repeating steps 1-3 keeps making the compositor slower until the entire system is unusable. EXPECTED RESULT Compositor should not drastically slow down after closing a game. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (5.12.13 kernel) KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 SYSTEM INFO: Razer blade 2018 (i78750HQ + GTX1060) NVIDIA driver version: 470.42.01 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429142] New: Dolphin crashes on startup
https://bugs.kde.org/show_bug.cgi?id=429142 Bug ID: 429142 Summary: Dolphin crashes on startup Product: dolphin Version: 20.11.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ashco...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 133353 --> https://bugs.kde.org/attachment.cgi?id=133353=edit Crash log from journalctl SUMMARY Since updating to 20.11.80, Dolphin always crashes on launch STEPS TO REPRODUCE 1. Launch dolphin OBSERVED RESULT Dolphin crashes on startup, regardless of the target directory asked to start in with the following stack trace seen in the attachment EXPECTED RESULT Dolphin doesn't crash on startup SOFTWARE/OS VERSIONS Arch Linux (KDE-Unstable) KDE Plasma version: 5.20.3 KDE Frameworks version: 5.75.0 QT Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426260] Plasma boots a black desktop on multi-screen setup; wallpaper returns after changing display setup
https://bugs.kde.org/show_bug.cgi?id=426260 Ashcon Mohseninia changed: What|Removed |Added CC||ashco...@gmail.com --- Comment #5 from Ashcon Mohseninia --- I filed a similar bug report here: https://bugs.kde.org/show_bug.cgi?id=426764 Seems that with more than 2 monitors on optimus laptops the black screen happens on every boot. Im using optimus manager set to NVIDIA mode -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426764] New: Optimus laptop internal display no wallpaper or menu
https://bugs.kde.org/show_bug.cgi?id=426764 Bug ID: 426764 Summary: Optimus laptop internal display no wallpaper or menu Product: plasmashell Version: 5.19.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: ashco...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When using multiple monitors with my Optimus enabled laptop (Using the NVIDIA GPU to drive the external displays with PRIME), the internal laptop display no longer has a wallpaper, the option to right-click on it for a menu, or any desktop icons. But i can still drag windows to it and view them on there perfectly fine STEPS TO REPRODUCE 1. Enable NVIDIA mode with Optimus manager / set NVIDIA GPU as primary 2. Plug in external monitor(s) 3. Set plugged in monitor as a primary display 4. Reboot Laptop OBSERVED RESULT Laptop display no longer has wallpaper or any right-click menu EXPECTED RESULT Laptop display should still function as a desktop display SOFTWARE/OS VERSIONS Linux: Arch Linux (kernel 5.8.10-arch1) KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION Laptop being used here is a Razer blade 2018. It has a GTX 1060 which drives the DP and HDMI external outputs. The laptops own display is driven by the intel IGPU -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418898] Plasmashell crashes when "Edit Panel" is selected
https://bugs.kde.org/show_bug.cgi?id=418898 Ashcon Mohseninia changed: What|Removed |Added CC||ashco...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 417986] OpenGL Section in Graphical info shows wrong kernel module with NVIDIA + Intel optimus
https://bugs.kde.org/show_bug.cgi?id=417986 Ashcon Mohseninia changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Ashcon Mohseninia --- I forgot to change the bug status last time i posted the info. Sorry -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 417986] OpenGL Section in Graphical info shows wrong kernel module with NVIDIA + Intel optimus
https://bugs.kde.org/show_bug.cgi?id=417986 --- Comment #2 from Ashcon Mohseninia --- --GLXINFO-- [ashcon@RB-2018 ~]$ glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 6144 MB Total available memory: 6144 MB Currently available dedicated video memory: 5660 MB OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 440.59 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6.0 NVIDIA 440.59 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 440.59 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 --QDBUS-- [ashcon@RB-2018 ~]$ qdbus org.kde.KWin /KWin org.kde.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.1 Qt Version: 5.14.1 Qt compile version: 5.14.1 XCB compile version: 1.13.1 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: 12007000 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 Blur: 0 onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 0 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: 4 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 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true compositingMode: 1 useCompositing: true hiddenPreviews: 1 unredirectFullscreen: false glSmoothScale: 2 xrenderSmoothScale: false maxFpsInterval: 694 refreshRate: 0 vBlankTime: 600 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 99 glPlatformInterface: 1 windowsBlockCompositing: false 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: eDP-1-1 Geometry: 0,0,1920x1080 Scale: 1 Refresh Rate: 143.998 Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 440.59 OpenGL platform interface: GLX OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 440.59 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.20.7 Linux kernel version: 5.5.5 Direct rendering: Requires strict binding: no GLSL shaders
[kinfocenter] [Bug 417986] New: OpenGL Section in Graphical info shows wrong kernel module with NVIDIA + Intel optimus
https://bugs.kde.org/show_bug.cgi?id=417986 Bug ID: 417986 Summary: OpenGL Section in Graphical info shows wrong kernel module with NVIDIA + Intel optimus Product: kinfocenter Version: 5.18.1 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: OpenGL Assignee: hubn...@gmail.com Reporter: ashco...@gmail.com Target Milestone: --- Created attachment 126256 --> https://bugs.kde.org/attachment.cgi?id=126256=edit Image showing mix up of openGL attributes SUMMARY When using the NVIDIA GPU through optimus-manager as the primary GPU, Kinfocenter displays a mix up of Nvidia and Intel attributes in the OpenGL section. Example in attached image shows 3D accelerator device as UHD Graphics 630 but shows the Driver as being NVIDIA, the OpenGL Version being 4.6.0 NVIDIA 440.59 and the Kernel module being i915 STEPS TO REPRODUCE 1. Use optimus manager on a supported laptop and switch to nvidia 2. Launch Kinfocenter 3. Observe mixed vendors in the OpenGL Section as shown in attachment OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
