First of all, I have really no idea where to post this issue. I filed it under kwin/compositing because it appears when there is, in fact, NO compositing. Feel free to move it to any other category or to plasmashell. Now for the issue itself: when suspending compositing (either via window rule or Alt+Shift+F12) my Plasma panel and the icons in the systray applet flicker shortly. After that they are virtually unusable because what is rendered on the screen doesn't necessarily correspond to what is actually there. Certain icons simply vanish (although they're actually still there), other icons that have long gone, suddenly appear again. Sometimes the same happens for the Task Manager applet (i.e. certain windows are not listed although they're actually there). So when I click a tray icon, I cannot be sure what happens before I actually click. This is because at the position where I click, I see, e.g. a Clipboard icon. But in reality it is the KMix icon, so KMix opens. Or I click, e.g., the network applet and nothing happens because in reality I clicked an icon that does nothing on click (e.g. Steam). I think this issue gets worse when some icons are rendered by sni-qt, but I am not sure. As soon as I turn compositing back on, everything's fine again. This might be related to "The window taskbar gets out of sync with the application windows" described in yesterday's blog post on PlanetKDE: https://btux1984.wordpress.com/2015/10/15/is-the-kde-5-desktop-stable-enough-for-normal-users-or/ Reproducible: Always Steps to Reproduce: 1. Make sure you have some icons in your systray and probably some windows open 2. Suspend compositing 3. Try to interact with systray icons 4. If you get (un)lucky, wonder why certain windows disappeared from your panel
Oh, I forgot to mention: I'm on proprietary NVIDIA drivers (v352.30) using OpenGL 3.1 rendering backend (GLX).
Also see https://forum.kde.org/viewtopic.php?f=289&t=128544 The bug is somewhere likely between libplasma, qtquick and plasmashell - and the nvidia driver. Can you please attach the output of "qdbus org.kde.KWin /KWin supportInformation"?
PS, wild guess: is it an autohiding panel?
No, I hate auto-hiding panels. ;-) Here's the qdbus output you requested: KWin Support Information: The following information should be used when requesting support on e.g. http://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 http://paste.kde.org instead of pasting into support threads. ========================== Version ======= KWin version: 5.4.1 Qt Version: 5.5.0 Qt compile version: 5.5.0 XCB compile version: 1.11 Operation Mode: X11 only Build Options ============= KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_WAYLAND: yes HAVE_WAYLAND_EGL: yes HAVE_WAYLAND_CURSOR: yes HAVE_XKB: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11604000 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: Blur: 0 onAllDesktopsAvailable: true alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 9 decorationButtonsRight: 6, 3, 4, 5 borderSize: 3 gridUnit: 12 font: Oxygen-Sans,11,-1,5,50,0,0,0,0,0 smallSpacing: 3 largeSpacing: 12 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 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 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 inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 unredirectFullscreen: false glSmoothScale: 2 colorCorrected: false xrenderSmoothScale: false maxFpsInterval: 16666666 refreshRate: 0 vBlankTime: 6000000 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 99 glPlatformInterface: 1 Screen Edges ============ desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 2 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: 2 Screen 0: --------- Name: DVI-I-1 Geometry: 0,0,2560x1440 Refresh Rate: 59.9506 Screen 1: --------- Name: DVI-D-0 Geometry: 2560,0,2560x1440 Refresh Rate: 59.9506 Compositing =========== Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 960/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 352.30 OpenGL platform interface: GLX OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 352.30 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.16.4 Linux kernel version: 4.1.4 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --------------- zoom dimscreen slidingpopups kwin4_effect_login wobblywindows slide screenshot magiclamp kwin4_effect_windowaperture glide desktopgrid kwin4_effect_translucency kwin4_effect_fade kwin4_effect_maximize presentwindows kwin4_effect_dialogparent highlightwindow blur contrast logout dashboard startupfeedback screenedge kscreen Currently Active Effects: ------------------------- blur contrast Effect Settings: ---------------- zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 dimscreen: slidingpopups: fadeInTime: 150 fadeOutTime: 250 kwin4_effect_login: wobblywindows: stiffness: 0.14999999999999999 drag: 0.55000000000000004 moveFactor: 0.10000000000000001 xTesselation: 20 yTesselation: 20 minVelocity: 0 maxVelocity: 1000 stopVelocity: 0.5 minAcceleration: 0 maxAcceleration: 1000 stopAcceleration: 0.5 moveEffectEnabled: true openEffectEnabled: false closeEffectEnabled: false moveWobble: true resizeWobble: true slide: screenshot: magiclamp: animationDuration: 250 kwin4_effect_windowaperture: glide: duration: 350 effect: 0 angle: 1 desktopgrid: zoomDuration: 300 border: 10 desktopNameAlignment: 0 layoutMode: 0 customLayoutRows: 2 usePresentWindows: true kwin4_effect_translucency: kwin4_effect_fade: kwin4_effect_maximize: presentwindows: layoutMode: 0 showCaptions: true showIcons: true doNotCloseWindows: false ignoreMinimized: false accuracy: 20 fillGaps: true fadeDuration: 150 showPanel: false leftButtonWindow: 1 rightButtonWindow: 2 middleButtonWindow: 0 leftButtonDesktop: 2 middleButtonDesktop: 0 rightButtonDesktop: 0 kwin4_effect_dialogparent: highlightwindow: blur: blurRadius: 12 cacheTexture: true contrast: logout: useBlur: true dashboard: brightness: 0.5 saturation: 0.5 blur: false startupfeedback: type: 0 screenedge: kscreen:
do you use what is known as "davetray" - the xembed-sni-proxy?
Whoops, didn't realize how long that is. Should have posted it to a paste service. Sorry about that. ;-) I use some apps that only have tray icons through sni-qt as described above (i.e. ownCloud and presumably KeePassX2).
I reported a similar problem in the forums (mentioned above): https://forum.kde.org/viewtopic.php?f=289&t=128544 Here is my system information: $ qdbus org.kde.KWin /KWin supportInformation KWin Support Information: The following information should be used when requesting support on e.g. http://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 http://paste.kde.org instead of pasting into support threads. ========================== Version ======= KWin version: 5.4.2 Qt Version: 5.5.0 Qt compile version: 5.5.0 XCB compile version: 1.11.1 Operation Mode: X11 only Build Options ============= KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_WAYLAND: yes HAVE_WAYLAND_EGL: yes HAVE_WAYLAND_CURSOR: yes HAVE_XKB: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11702000 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: Blur: 0 onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 5, 3 decorationButtonsRight: borderSize: 1 gridUnit: 12 font: Terminus,9,-1,5,50,0,0,0,0,0 smallSpacing: 3 largeSpacing: 12 Options ======= focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 6 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 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 inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: false compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 unredirectFullscreen: false glSmoothScale: 1 colorCorrected: false xrenderSmoothScale: false maxFpsInterval: 16666666 refreshRate: 0 vBlankTime: 6000000 glStrictBinding: false glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 0 glPlatformInterface: 1 Screen Edges ============ desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens ======= Multi-Head: no Active screen follows mouse: yes Number of Screens: 2 Screen 0: --------- Name: DVI-I-3 Geometry: 0,0,1920x1080 Refresh Rate: 60 Screen 1: --------- Name: DVI-I-2 Geometry: 1920,0,1280x1024 Refresh Rate: 60.0197 Compositing =========== Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 275/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 340.93 OpenGL platform interface: GLX OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 340.93 GPU class: G80/G90 OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.17.2 Linux kernel version: 4.1.10 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --------------- dimscreen slidingpopups kwin4_effect_login slide screenshot magiclamp kwin4_effect_windowaperture glide desktopgrid kwin4_effect_translucency kwin4_effect_maximize kwin4_effect_fade presentwindows highlightwindow kwin4_effect_dialogparent blur contrast logout dashboard startupfeedback screenedge kscreen Currently Active Effects: ------------------------- blur contrast Effect Settings: ---------------- dimscreen: slidingpopups: fadeInTime: 150 fadeOutTime: 250 kwin4_effect_login: slide: screenshot: magiclamp: animationDuration: 250 kwin4_effect_windowaperture: glide: duration: 350 effect: 0 angle: 0 desktopgrid: zoomDuration: 300 border: 10 desktopNameAlignment: 0 layoutMode: 0 customLayoutRows: 2 usePresentWindows: true kwin4_effect_translucency: kwin4_effect_maximize: kwin4_effect_fade: presentwindows: layoutMode: 0 showCaptions: true showIcons: true doNotCloseWindows: false ignoreMinimized: false accuracy: 20 fillGaps: true fadeDuration: 150 showPanel: false leftButtonWindow: 1 rightButtonWindow: 2 middleButtonWindow: 0 leftButtonDesktop: 2 middleButtonDesktop: 0 rightButtonDesktop: 0 highlightwindow: kwin4_effect_dialogparent: blur: blurRadius: 12 cacheTexture: true contrast: logout: useBlur: true dashboard: brightness: 0.5 saturation: 0.5 blur: false startupfeedback: type: 1 screenedge: kscreen: Regards
a) is it a multiscreen issue? ie. does it also happen if you disable the second screen and/or stop + deactivate the kscreen daemon in "kcmshell5 kded"? b) I noticed that when suspending the compositor, the panel briefly "sets off", not sure whether shrinks and also re-grows or just shifts out of screen - does this happen for either of you? c) is the panel position relevant?
a) Happens to me with one and two screens. b) I made a video how it looks on my system: https://vid.me/2D1I . I pressed Alt+Shift+F12 twice, starting with effects enabled. https://vid.me/2D1I c) Tried it in different positions, no difference. I noticed something else. It does not happen in the beginning. Directly after booting my system it works for a while but after using the system for a bit it always comes back. When it happened once it never goes back to normal again. A similar thing. After testing c) i noticed that directly after moving the panel it works for 2 - 3 switches. Every time i moved the panel. Hope that helps. Greetings
I can confirm those observations. I can also confirm that it sometimes works after a fresh boot. Right now, for instance, I can't reproduce it, but I know that it'll come back as it has always come back since I'm using Plasma5. Another thing I noticed is a bug specifically with KeepassX2. This might be unrelated, but maybe it's not. When I turn off compositing I can't restore the minimized window from the system tray anymore. I only see a flicker where the window is supposed to be but that's it. This condition stays even when I turn compositing back on until I restart KeePassX2 (except for that I don't see the flicker anymore, instead I see nothing).
Hmm. Forget the KeePassX2 thing. It's a bug with the program itself I guess. I just realized that the problem occurs when I re-minimize it using the tray icon instead of the window titlebar button. It happens with both compositing turned on and off. I just never clicked the tray icon to minimize the window under normal conditions.
Btw. a workaround we figured on the forum is to resize the panel (and I assume restarting the plasmashell process should do as well) Does either of you use triple buffering? ("grep -i triple /var/log/Xorg.0.log")
Yes, I'm using Triple Buffering to get rid of tearing issues.
No triple buffering.
ie. "insignificant". *sigh*
The same problem here, works after restart then starts this after some time. $ qdbus org.kde.KWin /KWin supportInformation KWin Support Information: The following information should be used when requesting support on e.g. http://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 http://paste.kde.org instead of pasting into support threads. ========================== Version ======= KWin version: 5.4.3 Qt Version: 5.4.2 Qt compile version: 5.4.2 XCB compile version: 1.11 Operation Mode: X11 only Build Options ============= KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_WAYLAND: yes HAVE_WAYLAND_EGL: yes HAVE_WAYLAND_CURSOR: yes HAVE_XKB: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11702000 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: Blur: 0 onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 0, 2 decorationButtonsRight: 6, 3, 4, 5 borderSize: 2 gridUnit: 12 font: Roboto Condensed,12,-1,5,50,0,0,0,0,0 smallSpacing: 3 largeSpacing: 12 Options ======= focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 8 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777250 showGeometryTip: false condensedTitle: false electricBorderMaximize: true electricBorderTiling: true electricBorderCornerRatio: 0.25 borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 2 useCompositing: true compositingInitialized: true hiddenPreviews: 1 unredirectFullscreen: false glSmoothScale: 1 colorCorrected: false xrenderSmoothScale: false maxFpsInterval: 16666666 refreshRate: 0 vBlankTime: 6000000 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: false glPreferBufferSwap: 97 glPlatformInterface: 2 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: eDP1 Geometry: 0,0,1920x1080 Refresh Rate: 60.001 Compositing =========== Compositing is active Compositing Type: XRender Loaded Effects: --------------- dimscreen slidingpopups kwin4_effect_login slide screenshot minimizeanimation kwin4_effect_windowaperture desktopgrid kwin4_effect_translucency kwin4_effect_maximize presentwindows highlightwindow kwin4_effect_dialogparent logout dashboard screenedge kscreen Currently Active Effects: ------------------------- Effect Settings: ---------------- dimscreen: slidingpopups: fadeInTime: 150 fadeOutTime: 250 kwin4_effect_login: slide: screenshot: minimizeanimation: kwin4_effect_windowaperture: desktopgrid: zoomDuration: 300 border: 10 desktopNameAlignment: 0 layoutMode: 0 customLayoutRows: 2 usePresentWindows: true kwin4_effect_translucency: kwin4_effect_maximize: presentwindows: layoutMode: 0 showCaptions: true showIcons: true doNotCloseWindows: false ignoreMinimized: false accuracy: 20 fillGaps: true fadeDuration: 150 showPanel: false leftButtonWindow: 1 rightButtonWindow: 2 middleButtonWindow: 0 leftButtonDesktop: 2 middleButtonDesktop: 0 rightButtonDesktop: 0 highlightwindow: kwin4_effect_dialogparent: logout: useBlur: true dashboard: brightness: 0.5 saturation: 0.5 blur: false screenedge: kscreen:
(In reply to Victor Varvaryuk from comment #16) > Compositing is active > Compositing Type: XRender Do you generally use XRender compositing? Do you use the nvidia driver as well? (see glxinfo)
> Do you generally use XRender compositing? I am experiencing freezes up to 1 minute when I launch some applications (KWrite -- it opens, the mouse cursor moves and changes when over other windows, but otherwise cannot anything else). I thought it might be related to OpenGL -- so I selected XRender. > Do you use the nvidia driver as well? (see glxinfo) I am not sure. I am supposed to be using Intel drives (I've installed bbswitch): $ glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.0.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend, GL_AMD_performance_monitor, GL_AMD_seamless_cubemap_per_texture, GL_AMD_shader_trinary_minmax, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_base_instance, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, GL_ARB_compressed_texture_pixel_storage, GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_derivative_control, GL_ARB_direct_state_access, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_indirect, GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, GL_ARB_explicit_uniform_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_shader, GL_ARB_framebuffer_no_attachments, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, GL_ARB_get_texture_sub_image, GL_ARB_gpu_shader5, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multi_draw_indirect, GL_ARB_occlusion_query2, GL_ARB_pipeline_statistics_query, GL_ARB_pixel_buffer_object, GL_ARB_point_sprite, GL_ARB_program_interface_query, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sample_shading, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_seamless_cubemap_per_texture, GL_ARB_separate_shader_objects, GL_ARB_shader_atomic_counters, GL_ARB_shader_bit_encoding, GL_ARB_shader_image_load_store, GL_ARB_shader_image_size, GL_ARB_shader_objects, GL_ARB_shader_subroutine, GL_ARB_shader_texture_lod, GL_ARB_shading_language_420pack, GL_ARB_shading_language_packing, GL_ARB_sync, GL_ARB_texture_buffer_object, GL_ARB_texture_buffer_object_rgb32, GL_ARB_texture_buffer_range, GL_ARB_texture_compression_bptc, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map_array, GL_ARB_texture_float, GL_ARB_texture_gather, GL_ARB_texture_mirror_clamp_to_edge, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_levels, GL_ARB_texture_query_lod, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_texture_view, GL_ARB_timer_query, GL_ARB_transform_feedback2, GL_ARB_transform_feedback3, GL_ARB_transform_feedback_instanced, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_attrib_binding, GL_ARB_vertex_shader, GL_ARB_vertex_type_10f_11f_11f_rev, GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_viewport_array, GL_ATI_blend_equation_separate, GL_ATI_texture_float, GL_EXT_abgr, GL_EXT_blend_equation_separate, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_sRGB, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, GL_EXT_pixel_buffer_object, GL_EXT_polygon_offset_clamp, GL_EXT_provoking_vertex, GL_EXT_shader_integer_mix, GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, GL_EXT_texture_compression_s3tc, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, GL_INTEL_performance_query, GL_KHR_context_flush_control, GL_KHR_debug, GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_packed_depth_stencil, GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc OpenGL version string: 3.0 Mesa 11.0.2 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend, GL_AMD_performance_monitor, GL_AMD_seamless_cubemap_per_texture, GL_AMD_shader_trinary_minmax, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, GL_ARB_color_buffer_float, GL_ARB_compressed_texture_pixel_storage, GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_derivative_control, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, GL_ARB_explicit_uniform_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_framebuffer_no_attachments, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, GL_ARB_get_texture_sub_image, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, GL_ARB_pipeline_statistics_query, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_program_interface_query, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sample_shading, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_seamless_cubemap_per_texture, GL_ARB_separate_shader_objects, GL_ARB_shader_atomic_counters, GL_ARB_shader_bit_encoding, GL_ARB_shader_image_load_store, GL_ARB_shader_image_size, GL_ARB_shader_objects, GL_ARB_shader_texture_lod, GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_compression_bptc, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, GL_ARB_texture_cube_map_array, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_float, GL_ARB_texture_gather, GL_ARB_texture_mirror_clamp_to_edge, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_query_levels, GL_ARB_texture_query_lod, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_texture_view, GL_ARB_timer_query, GL_ARB_transform_feedback2, GL_ARB_transform_feedback3, GL_ARB_transform_feedback_instanced, GL_ARB_transpose_matrix, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_attrib_binding, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_vertex_type_10f_11f_11f_rev, GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, GL_ATI_separate_stencil, GL_ATI_texture_env_combine3, GL_ATI_texture_float, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, GL_EXT_draw_buffers2, GL_EXT_draw_instanced, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_multisample_blit_scaled, GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB, GL_EXT_gpu_program_parameters, GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, GL_EXT_packed_float, GL_EXT_packed_pixels, GL_EXT_pixel_buffer_object, GL_EXT_point_parameters, GL_EXT_polygon_offset, GL_EXT_polygon_offset_clamp, GL_EXT_provoking_vertex, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_shader_integer_mix, GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_array, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_rgtc, GL_EXT_texture_compression_s3tc, GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_integer, GL_EXT_texture_lod_bias, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, GL_EXT_texture_shared_exponent, GL_EXT_texture_snorm, GL_EXT_texture_swizzle, GL_EXT_timer_query, GL_EXT_transform_feedback, GL_EXT_vertex_array, GL_EXT_vertex_array_bgra, GL_IBM_multimode_draw_arrays, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, GL_INTEL_performance_query, GL_KHR_context_flush_control, GL_KHR_debug, GL_MESA_pack_invert, GL_MESA_texture_signed_rgba, GL_MESA_window_pos, GL_NV_blend_square, GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_light_max_exponent, GL_NV_packed_depth_stencil, GL_NV_primitive_restart, GL_NV_texgen_reflection, GL_NV_texture_env_combine4, GL_NV_texture_rectangle, GL_OES_EGL_image, GL_OES_read_format, GL_S3_s3tc, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.0.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_texture_max_level, GL_EXT_blend_minmax, GL_EXT_color_buffer_float, GL_EXT_discard_framebuffer, GL_EXT_draw_buffers, GL_EXT_map_buffer_range, GL_EXT_multi_draw_arrays, GL_EXT_read_format_bgra, GL_EXT_separate_shader_objects, GL_EXT_shader_integer_mix, GL_EXT_texture_compression_dxt1, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_format_BGRA8888, GL_EXT_texture_rg, GL_EXT_texture_type_2_10_10_10_REV, GL_EXT_unpack_subimage, GL_INTEL_performance_query, GL_KHR_context_flush_control, GL_NV_draw_buffers, GL_NV_fbo_color_attachments, GL_NV_read_buffer, GL_NV_read_depth, GL_NV_read_depth_stencil, GL_NV_read_stencil, GL_OES_EGL_image, GL_OES_EGL_image_external, GL_OES_EGL_sync, GL_OES_compressed_ETC1_RGB8_texture, GL_OES_depth24, GL_OES_depth_texture, GL_OES_depth_texture_cube_map, GL_OES_element_index_uint, GL_OES_fbo_render_mipmap, GL_OES_get_program_binary, GL_OES_mapbuffer, GL_OES_packed_depth_stencil, GL_OES_rgb8_rgba8, GL_OES_standard_derivatives, GL_OES_stencil8, GL_OES_surfaceless_context, GL_OES_texture_3D, GL_OES_texture_float, GL_OES_texture_float_linear, GL_OES_texture_half_float, GL_OES_texture_half_float_linear, GL_OES_texture_npot, GL_OES_vertex_array_object 40 GLX Visuals visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat ---------------------------------------------------------------------------- 0x020 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x021 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0af 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0b0 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0b1 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0b2 24 tc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 0 0 None 0x0b3 24 tc 0 24 0 r . . 8 8 8 0 . . 0 0 0 0 0 0 0 0 0 None 0x0b4 24 tc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x0b5 24 tc 0 24 0 r . . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x0b6 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0b7 24 tc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x0b8 24 tc 0 24 0 r y . 8 8 8 0 . . 0 24 8 16 16 16 0 0 0 Slow 0x0b9 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0ba 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0bb 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0bc 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x0bd 24 tc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 4 1 None 0x0be 24 tc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 8 1 None 0x0bf 24 tc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 4 1 None 0x0c0 24 tc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 8 1 None 0x0c1 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0c2 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x0c3 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0c4 24 dc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 0 0 None 0x0c5 24 dc 0 24 0 r . . 8 8 8 0 . . 0 0 0 0 0 0 0 0 0 None 0x0c6 24 dc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x0c7 24 dc 0 24 0 r . . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x0c8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0c9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0ca 24 dc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x0cb 24 dc 0 24 0 r y . 8 8 8 0 . . 0 24 8 16 16 16 0 0 0 Slow 0x0cc 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0cd 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0ce 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0cf 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x0d0 24 dc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 4 1 None 0x0d1 24 dc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 8 1 None 0x0d2 24 dc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 4 1 None 0x0d3 24 dc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 8 1 None 0x06e 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 64 GLXFBConfigs: visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat ---------------------------------------------------------------------------- 0x06f 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x070 0 tc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x071 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x072 0 tc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x073 0 tc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x074 0 tc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x075 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x076 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x077 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x078 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x079 24 tc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 0 0 None 0x07a 24 tc 0 24 0 r . . 8 8 8 0 . . 0 0 0 0 0 0 0 0 0 None 0x07b 24 tc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x07c 24 tc 0 24 0 r . . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x07d 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x07e 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 0 Slow 0x07f 32 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x080 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x081 24 tc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x082 24 tc 0 24 0 r y . 8 8 8 0 . . 0 24 8 16 16 16 0 0 0 Slow 0x083 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 1 None 0x084 0 tc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 1 None 0x085 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 1 None 0x086 0 tc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 1 None 0x087 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x088 24 tc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x089 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x08a 24 tc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x08b 24 tc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 4 1 None 0x08c 24 tc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 8 1 None 0x08d 24 tc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 4 1 None 0x08e 24 tc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 8 1 None 0x08f 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x090 0 dc 0 16 0 r . . 5 6 5 0 . . 0 0 0 0 0 0 0 0 0 None 0x091 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x092 0 dc 0 16 0 r . . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x093 0 dc 0 16 0 r y . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x094 0 dc 0 16 0 r . . 5 6 5 0 . . 0 24 8 0 0 0 0 0 0 None 0x095 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x096 24 dc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x097 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x098 24 dc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x099 24 dc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 0 0 None 0x09a 24 dc 0 24 0 r . . 8 8 8 0 . . 0 0 0 0 0 0 0 0 0 None 0x09b 24 dc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x09c 24 dc 0 24 0 r . . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x09d 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 0 0 None 0x09e 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 16 16 16 0 0 0 Slow 0x09f 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None 0x0a0 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 16 16 16 16 0 0 Slow 0x0a1 24 dc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 0 0 None 0x0a2 24 dc 0 24 0 r y . 8 8 8 0 . . 0 24 8 16 16 16 0 0 0 Slow 0x0a3 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 4 1 None 0x0a4 0 dc 0 16 0 r y . 5 6 5 0 . . 0 0 0 0 0 0 0 8 1 None 0x0a5 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 4 1 None 0x0a6 0 dc 0 16 0 r y . 5 6 5 0 . . 0 16 0 0 0 0 0 8 1 None 0x0a7 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 4 1 None 0x0a8 24 dc 0 32 0 r y . 8 8 8 8 . . 0 0 0 0 0 0 0 8 1 None 0x0a9 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 4 1 None 0x0aa 24 dc 0 32 0 r y . 8 8 8 8 . . 0 24 8 0 0 0 0 8 1 None 0x0ab 24 dc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 4 1 None 0x0ac 24 dc 0 24 0 r y . 8 8 8 0 . . 0 0 0 0 0 0 0 8 1 None 0x0ad 24 dc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 4 1 None 0x0ae 24 dc 0 24 0 r y . 8 8 8 0 . . 0 24 8 0 0 0 0 8 1 None
(In reply to Victor Varvaryuk from comment #18) > I am not sure. It's intel. > I've installed bbswitch: => Anybody here *not* on an optimus system??
I have the same issue. i also would like to say that for me problem also includs desktop. I have a folder view as my desktop with clock on it and after using some opengl apps for 1-2 minutes while compositing is off dektop seems frozen ( all folders, clock, panel dont update). qdbus org.kde.KWin /KWin -> https://paste.kde.org/pswpovk46
(In reply to Sebastian Kuźlak from comment #20) > OpenGL vendor string: NVIDIA Corporation > OpenGL renderer string: GeForce GT 240/PCIe/SSE2 > OpenGL version string: 3.1.0 NVIDIA 340.96 > OpenGL platform interface: GLX > OpenGL shading language version string: 1.40 NVIDIA via Cg compiler > Driver: NVIDIA > Driver version: 340.96 > GPU class: G80/G90 ---- > includs desktop. I have a folder view as my desktop with clock on it and > after using some opengl apps for 1-2 minutes while compositing is off > dektop seems frozen ( all folders, clock, panel dont update). This would seem like a mere conflict of/between QtQuick (and other "opengl apps" (which?)) on apparently the nvidia driver (w/o any relation towards redirection state changes) => Is this an optimus system (ie. a notebook with an intel IGP *and* an nvidia GPU)?
Its a desktop pc with one main nvidia graphics card. Any opengl game, kodi also makes this bug happen (ill try to see if its happening without hardware accelerated kodi)
There goes jos' hope for any implicit fix, i fear :-P do you have env | grep QSG_RENDER_LOOP if not, what if you run: kquitapp plasmashell # desktop gone QSG_RENDER_LOOP=basic plasmashell & # desktop back in konsole? Do you maybe override swapcontrol in nvidia-settings (or by exporting __GL_SYNC_TO_VBLANK=0) Did you configure the system for triple buffering ("grep -i triple /var/log/Xorg.0.log")?
One note. Ive noticed now that it is always the first time i start kodi (didnt checked other apps) that freezes the uncomposited desktop immediately (i have a rule to disable compositing for kodi and some apps) . If i close kodi, quit plasmshell and restart it and kodi bug isn't present any more, at least its not occurring instantaneously like with fresh start. > do you have > env | grep QSG_RENDER_LOOP nope > if not, what if you run: > kquitapp plasmashell # desktop gone > QSG_RENDER_LOOP=basic plasmashell & # desktop back > > in konsole? nothing changes i can still get that bug on first run > Do you maybe override swapcontrol in nvidia-settings (or by exporting > __GL_SYNC_TO_VBLANK=0) .nvidia-settings-rc -> https://paste.kde.org/phop9x2ij no i dont ( at least i dont think i did ). Kodi is set up to use vblank however every game i have i set up to vblank=0 in their settings. > Did you configure the system for triple buffering ("grep -i triple > /var/log/Xorg.0.log")? with or without triple buffering bug is still visible on frist run
However after 5-10 minutes bug returns if i run kodi again :/
What is the status on this? I have this problem on three different systems with three completely different hardware configurations. All proprietary nvidia gpus tho.
See comment #22 The problem is in plasmashell, though the bug will ultimately be in QtQuick and/or the nvidia driver. Apparently whenever some ("fullscreen"?) GL context (kodi, in that case) is closed, plasmashell/QtQuick stops updating (on nvidia, at least) unless it's redirected and until the QtQuick context is resized. It's for pretty sure not in KWin - suspending the compositor is just one way to close a gl context and unredirect all windows (by the nature of the feature)
Hi there, i just installed KDE, QT 5.6 and the latest nvidia drivers and this bug is still present.
I am having this problem as well as of the latest update from Opensuse repos. The main trouble for me is the task manager, which doesn't update with compositing off, making me have to guess where the app I want to interact with is if I need to. This has been going for a while and happens every time compositing is turned off. My video card is an Nvidia 750 ti. My CPU is AMD.
Since 5.5 (or 5.6?) I also have the issue that not all windows are shown on the task manager when compositing is turned off (mostly those which were opened after turning it off) and the clock isn't updating. Everything seems to be in the state at which it was when disabling compositing for the first time. So enabling and disabling it again doesn't help. If my clock was at 3:45 when I turned it off, it stays at 3:45 until I turn compositing back on. And when I disable compositing a second time, it's again shows 3:45, even though it was, e.g., 5:32 when I re-enabled compositing temporarily. Using nvidia-358.16 on a GTX 650.
I'm also affected by this bug and also have an nvidia graphics card (Driver version: 361.42) > qdbus org.kde.KWin /KWin supportInformation https://paste.kde.org/pbjfhgnx4/acqpfg System: Neon User Edition
Still present in KDE 5.7, this is getting ridiculous.
Created attachment 100010 [details] qdbus output Can confirm this with Plasma/QT 4.7, Kernel 4.6 and 4.7rc. qdbus info attached. Panel freezes. Moving / resizing it resolves the issue for a while.
typo: Qt/Plasma 5.7
(In reply to Thomas Lübking from comment #27) Considering this post, it looks like the bug description is misleading or two different bugs are discussed here.
Another "me too". https://paste.kde.org/ptwwwkems I think something dies in the background and the non-composited panel stops rendering. For instance, my current local time is 1:23PM but if I alt+shift+f12 I see 3:28PM, which is presumably yesterday, and presumably when it got suck as I've watched it for an hour or so and it hasn't moved from 3:28PM. I'm running 3 displays on 2x GTX 580s in SLI (Propreitary drivers) Resizing it caused an immediate update here as well.
*** Bug 359661 has been marked as a duplicate of this bug. ***
I am encountering the same bug, with Debian unstable on x64, using proprietary nvidia drivers, so this is still not fixed. It is triggered by any full-screen app, which I guess turns off compositing. Quite an annoing bug, not good that something like this stays around for more than 12 months over several releases. A permanent fix would be much appreciated.
This still happens in 5.8.0 and is super annoying. Now I don't know if this is a bug specifically in Chrome or indeed a general NVIDIA issue, but when I started an application that disables compositing, not only the Plasma panels showed this bug, but also the Chrome UI froze until I minimized and restored the window. Anyhow, this bug is a super show stopper and deserves a fix. Any more insight on what exactly may be causing it?
Yes, this bug is still present with 5.8 but no one seems to care.
Confirm that the bug is still present in 5.8. You can prevent it by turning off compositing completely, so the bug title is actually wrong. I also noticed that the bug goes away temporarily if I switch composting from GL 2.0 to 3.1 and vice versa.
(In reply to Moritz Moeller-Herrmann from comment #41) > Confirm that the bug is still present in 5.8. You can prevent it by turning > off compositing completely, so the bug title is actually wrong. I also > noticed that the bug goes away temporarily if I switch composting from GL > 2.0 to 3.1 and vice versa. "kwin --replace" also works.
*** Bug 378043 has been marked as a duplicate of this bug. ***
Same here with Plasma 5.10, nvidia proprietary driver. I disable compositing automatically for Mplayer, so when I'm watching videos, my clock displays a time in the past (the first time the compositer went off, I think), the system tray icons don't correspond to the actual icons (you click one and trigger the other), the taskbar is wrong, etc... Resizing the panel "fixes" it temporarily.
Eheh, I've been late enough times to learn to not trust the plasma panel clock while i'm playing games :)
*** Bug 375742 has been marked as a duplicate of this bug. ***
Still affected in Plasma 5.8.7 (Frameworks 5.35.0 / Qt 5.6.1), using Nvidia GTX 970 with propietary drivers 381.22 When I start a game, compositing get off automatically, and if I alt+tab to the desktop, the task manager doesn't update anymore, although I change between virtual desktops, the same apps are shown. After I close the game, and compositing auto enables again, if I alt+shift+f12 to disable, the same apps appear in the panel, confirming the past freeze state of other comments. qdbus Kwin information https://goo.gl/VoMD8n
Beside the panel itself, I've seen the same with any other windows. Plasma Framework 5.28.0/Qt 5.7.1 (Debian 9.1 Stretch) with Nvidia Quadro K2200 proprietary drivers 375.66. This workstation runs OpenGL code for visualizing data, and after a while I see this bug kicking in. What's most annoying is that it can show up even a few hours after a fresh reboot. One thing that I've noticed is that it seems to be loosely correlated with the use of the X11vnc server. Another possible suspect could be the VirtualBox driver, but, again, loose correlation here. I've checked the .xsession-errors log, but there isn't anything related to the issue (just the usual 220Mb of Kmix errors) Given the two years anniversary around the corner, it would be nice to see some good news.
*** Bug 383810 has been marked as a duplicate of this bug. ***
*** Bug 371219 has been marked as a duplicate of this bug. ***
Created attachment 108776 [details] qdbus org.kde.KWin /KWin supportInformation Same issue here on Fedora 26 KDE Spin with NVIDIA GeForce GTX 650 (proprietary driver v387.22)
*** Bug 386717 has been marked as a duplicate of this bug. ***
*** Bug 361692 has been marked as a duplicate of this bug. ***
*** Bug 386327 has been marked as a duplicate of this bug. ***
If it can be useful for debugging, i just noticed that even switching from opengl to xrender compositing triggers the bug (panel stops to update while compositing is switched to xrender from opengl, and starts updating again as soon as compositing is switchet to opengl again)
Same bug still present in 5.11. What can we do to get the fixed? Is there more information needed? This has been open for 2 years, it is a bug which people experience every day breaking one of the main functions of Plasma. It affects latte dock the same as the default panel. Please let us know how we can help or give us an update. Thank you.
From some guy on Reddit: Make sure Systemsettings > Display & Monitor > Compositor > "Allow Applications to block compositing" is checked. (This is not absolutely necessary but it makes the bug appear faster on my system.) Make sure compositing is actually active (You have shadows under your plasma panel) Download this game: https://12amstatic.itch.io/wishcraft > ""Download Now" > Enter 0$ > Download "Wishcraft PC version". (90MB) Extract the game and change into the folder Start the game with "Wishcraft.sh" (Now this is the tricky part. It does not happen all the time, but if you start the game multiple times, sooner or later my panel freezes in "non compositing" mode. I have to restart kwin then to get it back to work until it freezes again) ----- Also apparently my NV robustness support patch doesn't make a difference to this.
(In reply to David Edmundson from comment #57) > From some guy on Reddit: > > > Make sure Systemsettings > Display & Monitor > Compositor > "Allow > Applications to block compositing" is checked. (This is not absolutely > necessary but it makes the bug appear faster on my system.) > > Make sure compositing is actually active (You have shadows under your > plasma panel) > > Download this game: https://12amstatic.itch.io/wishcraft > ""Download > Now" > Enter 0$ > Download "Wishcraft PC version". (90MB) > > Extract the game and change into the folder > > Start the game with "Wishcraft.sh" (Now this is the tricky part. It does > not happen all the time, but if you start the game multiple times, sooner or > later my panel freezes in "non compositing" mode. I have to restart kwin > then to get it back to work until it freezes again) > > > > > > ----- > > Also apparently my NV robustness support patch doesn't make a difference to > this. For this bug to occur you can use any opengl app. Blender will be enough to trigger it. Turn off composigint (via ctrl+alt+f12 or using "Allow Applications to block compositing" option ) and after few minutes panel stop redrawing.
*** Bug 363647 has been marked as a duplicate of this bug. ***
Same issue on 5.11.5 with nvidia drivers. Is a fix in the works?
No, we didn't find a developer yet who understands the cause for this issue and is able to propse a patch. It is not clear if the bug is in kwin, the plasmashell, or anywhere in graphics subsystem.
I recently stopped using kwin for my window manager in favor of i3wm and compton for compositing. I am no longer able to reproduce this bug, even if compton is not running. Since the nvidia driver and plasmashell remain the same, this lends some support to the problem being kwin related. > cat ~/.config/plasma-workspace/env/wm.sh export KDEWM=/usr/bin/i3 compton --daemon --config ~/.config/compton.conf
Well, i just noticed that panels/plasma keeps updating again by just restarting kwin, even with compositing disabled. I mean, kwin restarts without compositing.
Just wanted to add that it seems to be still present in 5.12.0. Let me know if there is anything else needed to help debug.
Not sure if I have done anything but it seems to be gone for me with plasma 5.12 on the 384 latest drivers and a 1060. Will let you know if it comes back.
This problem isn't solved by using the "Allow applications to block compositing" for me. For me the panel will freeze when launching Unity 3D "games", or other games. Also after closing the game the font turns blurry. For my work this is debilitating. I cannot restart every single time I want to run this software which I need for work. The only thing that works for me is using XRender instead of OpenGL. I am using the Nvidia driver 390. This really sucks because it also disables all the nice visual effects.
Yes indeed sorry it has since some back...
Hi ! I get a random issue that seems related. Sometimes, (it occurs quite regularly, like once every few days) the panel "freezes". Well, not really, as it remains clickable, but it is not updated "visually" anymore. I can still raise / lower windows, switch desktops... but the panel doesn't reflect what I do. Disabling / re-enabling desktop effects makes no difference. I didn't think of restarting KWin. I will, next time. I remember that several minutes earlier, I started Steam and got a notification according to which desktop effects had to be reinitialized. It didn't seem to have any consequence, but that might be related. Then I pinned some apps to my panel, and this is when it occurred. Apps running : Thunderbird, Firefox, Steam. Also, I'm using NVIDIA drivers 390.x (but it occurred before) and Plasma 5.12.1 (KDE Neon). I don't know how to make it reproducible. But it's quite frequent.
BTW, as you people all seem to encounter it when using NVIDIA proprietary drivers + some openGL apps that suspend compositing automatically, can you tell what specific tweak you applied ? Here I force the composition pipeline (otherwise my desktop animations are too jerky) but I'm pretty sure it also occurred when using "export __GL_YIELD=USLEEP"
I believe I have enabled "export __GL_YIELD=USLEEP" and I still get it.
More often than not, using Steam cause kwin to perform a "graphics reset". Plasma doesn't get that and tries to render to the old addresses. You can monitor the kwin output and react to the reset, with a: kquitapp5 plasmashell && kstart plasmashell /Allan
Since this bug breaks basic desktop functionality, many hours daily for some users and there is not solution in sight. Is there a way to add a dirty fix for NVIDIA users? Instead of just disabling compositor run: disable compositor kwin_x11 --replace disable compositor How could we add this our self so it is automated?
So this is a corner case with nvidia i suppose? I haven't head this issue in a while even though i still have the same hardware as when i reported this issue (under a different bug). I have to admit though, that was at a time when i played a steam game almost daily, something that hasn't happened since. But i'm curious. Nvidia was once the card you should have for linux. Any desktop would work best on that. Then it was Intel which was - till a few years ago - putting out driver updates fairly regularly. AMD was always a big no-go due to it's massive unstable behavior and always lacking behind in kernel support. Where are we now? Which GPU is recommended? As i get from the comments that nvidia is apparently not recommended anymore. I wouldn't be surprised if "AMD" would be the answer now. As they have become really good (in terms of open source drivers).
*** Bug 354492 has been marked as a duplicate of this bug. ***
(In reply to Mark from comment #73) > Where are we now? Which GPU is recommended? > As i get from the comments that nvidia is apparently not recommended anymore. > I wouldn't be surprised if "AMD" would be the answer now. As they have > become really good (in terms of open source drivers). Oh absolutely, if I get get asked which ditro someone should try, my first question is what GPU they use because I just cant recommend Plasma in combination with an NVIDIA GPU. Not just the panel breaking, but also the generally poor desktop performance. If I resize a windows quickly I can get the desktop FPS down to 20FPS with a 970 GTX, where an old iGPU runs smoothly at 60fps.
(In reply to evea from comment #75) > (In reply to Mark from comment #73) > > Where are we now? Which GPU is recommended? > > As i get from the comments that nvidia is apparently not recommended anymore. > > I wouldn't be surprised if "AMD" would be the answer now. As they have > > become really good (in terms of open source drivers). > > Oh absolutely, if I get get asked which ditro someone should try, my first > question is what GPU they use because I just cant recommend Plasma in > combination with an NVIDIA GPU. > > Not just the panel breaking, but also the generally poor desktop > performance. If I resize a windows quickly I can get the desktop FPS down to > 20FPS with a 970 GTX, where an old iGPU runs smoothly at 60fps. :( I still have a GPU from the times when they seemed to recommend either nvidia or intel. Mine still is a GTX 670. But is that perormance issue really an issue of KWin or just Qt (QML more specifically)?
I managed to fix my issue. I have an Nvidia 1070 and the latest Nvidia drivers. If you run into this issue follow these steps and report back. Scale Method : Smooth Rendering backend : OpenGL 3.1 Tearing prevention("vsync") : Full screen repaints Keep window thumbnails : Only for Shown Windows Experimental : Enable color correction : false(unchecked) Allow applications to block compositing : false(unchecked) The key is really not allowing applications to block compositing for me. After I stop letting applications to disable it, after it reverting when the application was closed never gave me any issues. I think compositing isn't re-starting properly after an application disables it.
Just to add my tuppence worth. I also had this problem where the panel stops rendering ie appears frozen, but remains clickable along with widgets such as the simple monitor also not rendering. In my case I was also using the Docky launchpad application. Interestingly Docky remained working after the panel had frozen. However after removing Docky the panel is now working reliably which is great because I don't really need Docky. It does sound like any 3rd part app that requires compositing causes an issue in Plasma rendering.
I don't have any third party apps (or widgets even), and I get this issue on both my Laptop and Desktop, so I would doubt they are the issue. And, yes, the panel stops rendering but remains "clickable", although the text/position of things gets pretty far off as its not repainting.
Panel rendering freeze still happens in Plasma 5.12.3 (KDE Neon). I'd been running KDE Neon for probably 6 hours (laptop), I was only using Chrome, Gimp, Kmail, Dolphin, no games or apps that require compositing as far as I'm aware. On the desktop I'm using the 'simple monitor widget'. I noticed the seconds on the clock on the panel had froze, panel was still clickable ie you could close apps but the rendering then no longer matches what actaully running. The simple monitor also freezes. To restart rendering I switch panel to autohide or alternatively CNTRL_ALT-F1 followed by CNTRL-ALT-F7 restarts the panel & widget rendering.
Test
Just had the panel rendering freeze again, was using with kmail at the time, so did a bit of detective work. As I had enabled seconds on the panel clock it gives me a time to look for in the logs. So the panel froze at 00:13:35. Looking at /var/log/syslog, the following entry exists at 00:13:33 that's relevant to the GPU. There was nothing else around that time that was unusual. Sorry post this in sections as bugs.kde.org seems to think my post contains spam ! ;-/
I can't post the actual error bugs.kde.org keeps telling me its spam ! Anyway ... Just had the panel rendering freeze again, was using with kmail at the time, so did a bit of detective work. As I had enabled seconds on the panel clock it gives me a time to look for in the logs. So the panel froze at 00:13:35. Looking at /var/log/syslog, the following entry exists at 00:13:33 that's relevant to the GPU. There was nothing else around that time that was unusual. This URL explains the error I'm getting http://docs.nvidia.com/deploy/xid-errors/index.html#topic_5_2 This error is inserted into /var/log/syslog by the Nvidia driver and indicates an error. If I've understood this correctly, this is XID error 31. So I looked up the NVidia documentation which states: XID 31: Fifo: MMU Error This event is logged when a fault is reported by the MMU, such as when an illegal address access is made by an applicable unit on the chip Typically these are application-level bugs, but can also be driver bugs or hardware bugs. When this event is logged, NVIDIA recommends the following: Run the application in cuda-gdb or cuda-memcheck , or Run the application with CUDA_DEVICE_WAITS_ON_EXCEPTION=1 and then attach later with cuda-gdb, or File a bug if the previous two come back inconclusive to eliminate potential NVIDIA driver or hardware bug. Note: The cuda-memcheck tool instruments the running application and reports which line of code performed the illegal read. The cuda-memcheck tool sounds like it might be very useful for tracking down this bug. Has anybody tried running cuda-memcheck with plasma ? Is it even possible ?
I don't think this is just an NVIDIA issue. The log messages from their driver are useful, but I've been experiencing this exact bug with Intel graphics for years. The system I've encountered it on is a late 3013 MacBook Pro (the 13" one with Intel-only graphics).
Apologies for the typo - I don't really own a laptop from the future. Although if I did, I imagine sourcing drivers for it might be a little tricky ;-). 'Late 3013' in my previous message should actually read 'late 2013'.
(In reply to Steven Gilberd from comment #84) > I don't think this is just an NVIDIA issue. The log messages from their > driver are useful, but I've been experiencing this exact bug with Intel > graphics for years. > > The system I've encountered it on is a late 3013 MacBook Pro (the 13" one > with Intel-only graphics). I agree, I'm hoping that somebody that knows this code could work on it if we can find a 100% reliable way of triggering the bug so at least it's easier to track it down. Although I code mainly in C and a tiny amount in C++ I'm tempted to start delving into this. KDE & Plasma is a great platform but it needs to be stable. My windows colleagues would laugh if I told them I had to CNTRL-F1 & CNTRL-F7 periodically because the panel & desktop rendering had frozen !
(In reply to Steven Gilberd from comment #85) > Apologies for the typo - I don't really own a laptop from the future. > Although if I did, I imagine sourcing drivers for it might be a little > tricky ;-). > > > 'Late 3013' in my previous message should actually read 'late 2013'. I sure hope this bug has been fixed by 3013 :-D, not to mention Wayland working with Nvidia hardware !
KWin forgot to inform Plasma about new render memory location, Plasma renders to a bad location and NVidia MMU says Xid 31. Triggered easily with Steam. Restarting plasma causes correct rendering again: kquitapp5 plasmashell && kstart plasmashell
>KWin forgot to inform Plasma about new render memory location, Plasma renders to a bad location and NVidia MMU says Xid 31. That doesn't sound right at all. What makes you say it's that?
The complete process goes: Steam (or others) triggers KWin to reset graphics subsystem -> Plasma is now rendering to a bad address -> NVidia throw Xid 31. Speculation that fit all the facts. :)
Just wanted to clarify that the problem is not random an easy to reproduce, it happens every day to me if I have steam running and launch CS:GO.
>Speculation that fit all the facts. :) Not really. Kwin doesn't allocate memory for plasma to render into. We're on GLX here. Can someone paste the error they have in pastebin that mentions XID error 31.
Sure I'm travelling at the moment but I'll send it in about 4 hours
I think XID error 31 is unrelated to this bug. I get xid error only when launching steam, then kwin restarts with "Desktop effects were restarted due to a graphics reset" notification. I made a video with panel bug where I didn't get any xid errors: https://streamable.com/3czun Also, someone stated that this bug occur with intel gpu, so it has to be problem either with kwin or plasmashell.
My desktop effects just reset and the compositing has switched to XRender instead of returning to OpenGL 3.1. I don't know if it is a separate bug or is still related to this. Anyway the plasma panel doesn't update anymore (either by enabling or disabling compositing with the shortcut). NVIDIA GTX 970 (driver 390.48) Plasma 5.12.3 ArchLinux with linux 4.15.13-1 Compositing =========== Compositing is active Compositing Type: XRender
(In reply to David Edmundson from comment #92) > >Speculation that fit all the facts. :) > > Not really. Kwin doesn't allocate memory for plasma to render into. We're on > GLX here. > > Can someone paste the error they have in pastebin that mentions XID error > 31. So here's the error. https://pastebin.com/HDtNJn5t As mentioned in an earlier post this occurred 2 seconds before the panel froze. I would have had the following programs open, Filezilla, Dolphin, kdevelop, Chrome, Discover, kmail. KDE Neon, Plasma 5.12.3, GTX570M, Nvidia driver 384.111, I7 2670QM CPU.
*** Bug 362955 has been marked as a duplicate of this bug. ***
I've just added the following bug https://bugs.kde.org/show_bug.cgi?id=393748 which also is a plasma shell freeze but caused by Dolphin and is 100% reproducible. Thought if your following this thread you may want to take a look as maybe it's all related.
Created attachment 112396 [details] Backtrace of plasmashell Attached plasmashell backtrace, captured while the panel was frozen, the only programs I was running at the time were kmail, dolphin, filezilla, chrome, kate, okular and system activity monitor. Is there any other processes I should be getting a backtrace or other data on ?
Just out of curiosity, if anybody has a working knowledge of ThreadWeaver what's going on here and is this bad?. It looks bad to me but then I know diddly squat about thread programming. This is one of the plasmashell backtrace threads captured during a plasma panel freeze. For all the other associated threads see the attachment. Thread 34 (Thread 0x7ff24a7fc700 (LWP 6695)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007ff3908ac65b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x00007ff2b754d80f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #3 0x00007ff2b75518e8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #4 0x00007ff2b754c9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x00007ff2b7551942 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x00007ff2b754c9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x00007ff2b7551942 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x00007ff2b754c9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x00007ff2b7551942 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x00007ff2b754c9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x00007ff2b7551942 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x00007ff2b754c9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x00007ff2b7551942 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x00007ff2b754c9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x00007ff2b7551942 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x00007ff2b754c9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #17 0x00007ff2b7551942 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #18 0x00007ff2b754c9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #19 0x00007ff2b7551942 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #20 0x00007ff2b754c9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #21 0x00007ff2b7551942 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #22 0x00007ff2b754c9ed in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #23 0x00007ff2b754f460 in ThreadWeaver::Thread::run() () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #24 0x00007ff3908ab709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x00007ff38fe9d6ba in start_thread (arg=0x7ff24a7fc700) at pthread_create.c:333 #26 0x00007ff3901ba41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
> is this bad?. No. It shows an krunner thread is sittling idling. Plasma isn't frozen, if you run with gammaray attached whilst the panel is froze the panel in gammaray's view is updated fine.
Thanks, I've killed plasmashell & restarted using the command gammaray plasmashell but I can't see any view ? Am I starting it correctly ? I've had a quick look online but can't find any info on starting a view. I've seen some of the gammaray docs that show more options in the left hand column like quick scenes, state machines which I seem to be missing. Are there KDE docs that describe using gammaray, or am I going to have to read the manual & figure it out.
It's the same with me. Once the problem starts, the desktop effects are lost, the time is frozen, the taskbar icons are ghosts and many times I can't shut down the system from the "start" button, as another process breaks down, having to shut down the system from the terminal. But the problem does not end there.... now the computer does not shut down because there is a process that does not close -A start job is running... -. I have to wait 90 seconds for it to finish closing, and when the PC is finally turned off, it starts again automatically. When that happens, the computer turns on correctly, but whenever I turn it off, it starts automatically. It reminds me a lot of a problem I had with the wake on lan, that whenever I activated it, the computer would only turn on when I turned it off. The only way to get it to shut down again is to force the button to shut it down.
*** Bug 393175 has been marked as a duplicate of this bug. ***
Something I noticed last night: when the panel gets stuck like this even after exiting the OpenGL/Vulkan application/game, switching to a virtual terminal and then back to X restores the panel to working again.
(In reply to Joe from comment #105) > Something I noticed last night: when the panel gets stuck like this even > after exiting the OpenGL/Vulkan application/game, switching to a virtual > terminal and then back to X restores the panel to working again. That's the trick I use too. :-) Interestingly that trick does not work when plasma hangs when you move (cut & paste) a large number of files using Dolphin. Plasma stays frozen until the freeze ends, the time period of the froze being depending on the number of files moved. Try moving 1000 files and see how long plasma freezes for..
Speak of the devil, just glanced at the clock and the seconds (along with hours/minutes and the rest of the desktop is frozen. Froze an hour and ten minutes ago (uptime 2:18) and all I've been using is kmail, Dolphin & Chrome with 8 tabs open. And of course CNTRL-ALT-F1 followed by CNTRL-ALT-F7 starts it working again.
*** Bug 394146 has been marked as a duplicate of this bug. ***
Having the same issue on an NVIDIA + Ryzen Desktop build... Sometimes I workaround this by killing plasmashell and kwin_x11, glad to see I'm not alone.
Created attachment 112596 [details] sleep mode to ram busting ingame opengl aswell sleep mode to ram busting ingame opengl aswell
Today happened again, with no game opened, just DaVinci resolve and chromium browser.
Yeah, I have seen it now on my desktop atleast twice recently where it happened outside of full screen games.
I'll be a happy camper when this bug gets fixed, I can tell you. I've just realised the plasma panel clock has froze at 17:13 and it's now 18:26, I should have left work 45 minutes ago ! Again no full screen games just chrome, dolphin and kmail and libreoffice. I've got nothing to prove this but it feels like it's whenever I'm using Dolphin or kmail this thing kicks off. Certainly if I leave the computer running without those programs running I've never seen the panel freeze. The more I'm playing with kmail & Dolphin the more this is likely to happen.
So it happened to me last night again with only Chrome open. Seemed to kick in when I opened up roll20, so I would guess whatever graphics api they are using (maybe webGl or something?) can trigger the bug without fullscreen.
*** Bug 394445 has been marked as a duplicate of this bug. ***
*** Bug 356035 has been marked as a duplicate of this bug. ***
*** Bug 394950 has been marked as a duplicate of this bug. ***
May be fixed my new nvidia driver (https://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-390.67-Linux-Released) > Fixed a bug that caused kwin OpenGL compositing to crash when launching certain OpenGL applications
see comment 84, it is present even with intel drivers.
(In reply to Antonio Orefice from comment #119) > see comment 84, it is present even with intel drivers. Well, that's interesting. In my experience (many different machines over the years), it never occurred on Intel or AMD hardware but did occur several times a day with Nvidia GPUs. I'm sorry that's not very helpful, but there is definitely something making the issue more prominent with Nvidia drivers. (I do get other unrelated trouble with all those, like kwin crashing on in a while and not restarting or getting a black desktop)
*** Bug 395076 has been marked as a duplicate of this bug. ***
Still a bug after many years. Anyone have advice for a rookie to fix this problem?
(In reply to mdjones325 from comment #122) > Still a bug after many years. > > Anyone have advice for a rookie to fix this problem? Disable compositing.
(In reply to Andrey Rahmatullin from comment #123) > (In reply to mdjones325 from comment #122) > > Still a bug after many years. > > > > Anyone have advice for a rookie to fix this problem? > > Disable compositing. would appreciate rookie-level advice
Personally I prefer compositing to be enabled. So to recover from a plasma freeze which may happen once or twice a day depending on what I'm doing, I just CNTRL-ALT-F1 to bring up the full screen terminal and then CNTRL-ALT-F7 to return to the GUI. I then find the plasmashell is now working again. Alternatively enable auto-hide on the task bar. (Click the three bar menu on the extreme right of the task bar, click on 'more settings' then click auto hide in the visibility section'. If there is not a three bar menu on the extreme right of the task bar, click right on background of the desktop and make sure there is a menu entry that says 'lock widgets', if it says 'unlock widgets' then click it. The three bar menu will appear. Autohide seems to have the same affect as CNTRL-ALT-F1 & CNTRL-ALT-F7. The taskbar also seems to freeze for me when I'm using Dolphin more than any other program.
Thanks Nick. Switching between the full screen terminal and the DE fixes the problem.
Still affects me, and always has. Maybe I'll give this a try on my machine with amdgpu to see if it happens just to see if it is an nvidia only thing and report back. Arch Linux nvidia 396.24-1 kernel 4.16.9-1-ARCH 1080ti For me, the taskbar does not update at all when in non-composited mode. When I switch back to composited with Alt+shift+F12, it works. I like to use non-composited when gaming because I am sure the compositing is not interfering, and I get less stuttering and weird behavior when I alt-tab during a game. The ability to do this is why I like Plasma.
Same here, with the compositor disabled the task manager never updates correctly. I'm using an nvidia quadro card.
I believe the new Nvidia drivers fixed the issue. Please confirm you have the newest drivers, or if you get this bug and end up here try them and report back.
(In reply to Ryein Goddard from comment #130) > I believe the new Nvidia drivers fixed the issue. I cannot confirm this observation. Still an issue with the newest driver.
The plasma freezing on compositing enable/disable is definitely NOT fixed with the (currently latest) 390.67 nvidia drivers (GeForce 1050). It might have fixed a frequent kwin freeze though.
*** Bug 395971 has been marked as a duplicate of this bug. ***
*** Bug 394583 has been marked as a duplicate of this bug. ***
Coming here from (it was duped by someone) https://bugs.kde.org/show_bug.cgi?id=394583 For me at least, the task bar freezing is gone when I disable the compositor. I've been running with the compositor disabled for weeks now and I don't experience the issue.
Hi ! I don't want to get you people excited over nothing but here's an excerpt of the new Nvidia drivers update : "Fixed a bug that caused kwin OpenGL compositing to crash when launching certain OpenGL applications." (fixed in the 390.77 and 396.45 Nvidia drivers)
(In reply to Mahendra Tallur from comment #136) > Hi ! I don't want to get you people excited over nothing but here's an <cut> It's a partial excitement. It doesn't solve the other cases that break plasma rendering, like Lockscreen and many OpenGL apps (including browsers occasionally).
I don't understand; the case specific to the issue this bug is reporting (Turning off compositing breaks Plasma panel rendering) is fixed?
Latest 390.xx drivers don't fix this for me - was able to just easily reproduce it by alt-tabbing out of thrones of Britannia (Vulkan). Panel was frozen as always.
(In reply to Joe from comment #139) > Latest 390.xx drivers don't fix this for me - was able to just easily > reproduce it by alt-tabbing out of thrones of Britannia (Vulkan). Panel was > frozen as always. Hmm, I encounter the same phenomenon, but is the panel restored when the game is exited and compositing resumed ? Here the panel is often frozen when compo is disabled but it used to ALSO remain frozen when compo is re-enabled ; didn't witness it so far.
Actually, yes, the panel appears to be only broken now when the vulkan/opengl app is running, the panel seems to go back to normal when things are exited. I guess thats... something.
For me the panel always has worked well after the openGL app exited.
@Alex : actually, in the past, the panel would sometimes remain stuck even after resuming compositing on my machine, so that's a significant yet partial improvement (as one doesn't have to kill plasmashell anymore). The current situation is "only" annoying if you alt-tab away from games...
@Mahendra Tallur Exactly. Although I would also say that I have triggered this just in Chrome and not full screen (on roll20), so it still can be a bit more annoying that just alt-tabbing from full screen games.
*** Bug 397552 has been marked as a duplicate of this bug. ***
*** Bug 400176 has been marked as a duplicate of this bug. ***
KUBUNTU 18.10 - nouveau driver OK, nvidia - dead stick @https://bugs.kde.org/show_bug.cgi?id=395781 as guru said NVIDIA _I_ U DISPERSE ALL bug isnt related to KDE or even kernel
Created attachment 116933 [details] przejebane https://www.youtube.com/watch?v=2AJm4mlylzw&feature=youtu.be Pure installation new kubuntu 18.10 sleep mode using nouveau driver gives normal behaviour. Change to nvidia 390, or go back to nouveau keeps bug alive ---- but has been a litle fixed since >2 last years since drawing is more close than before
I spent some time today on this, I wrote an app to block compositing every few seconds. I also tried to reproduce the panel in a separate app of rendering multiple QQuickViews and adding the same shadows/blur that panel does. I have some relevant notes: - It doesn't break consistently - When it does break, toggling compositing back on and then off again will always give you the first broken frame (i.e if I toggle every 10 seconds, if I have a stuck frame with the clock saying 12:00:00 when it breaks and I toggle compositing back on it'll resume 12:00:10, 12:00:11, blah blah, when it toggles off again it goes back to showing 12:00:00) - Even if the app is frozen you still get that broken frame when you toggle compositing, so it's a breakage once, not a breakage each toggle event. I also built libxcb with this. https://cgit.freedesktop.org/xcb/libxcb/commit/?id=bbda345a718ff73086437e51f03fcbb73e4365b9 The description vaguely matches a setup behaviour that we see in Plasma. We have nvidia-glx rendering one thread, whilst our panel is making a tonne of X calls directly to adjust the panel shadow. The commit is trying to fix a crash, but a missed reply could have other consequences. print statements showed we end up in the "fix" code a lot. So far I haven't reproduced afterwards.
I recently switched from an AMD GPU to an nvidia GPU. I think I might have a useful observation. When my panel freezes, it turns more of a dark black, as apposed to the default breeze look. This same thing -- at least cosmetically -- happened on my AMD card before I switched. However, with the AMD card it would within a few seconds correct itself. I suspect if the cause of this graphical glitch can be found and fixed for mesa, it would also take care of the issue for nvidia cards which recover less gracefully. I think it's also worth noting, you can kill plasmashell and restart it to fix this issue. The issue only occurs during the transition from composited to non-composited.
(In reply to Ryein Goddard from comment #66) > This problem isn't solved by using the "Allow applications to block > compositing" for me. > > For me the panel will freeze when launching Unity 3D "games", or other > games. Also after closing the game the font turns blurry. For my work this > is debilitating. I cannot restart every single time I want to run this > software which I need for work. > > The only thing that works for me is using XRender instead of OpenGL. > > I am using the Nvidia driver 390. > > This really sucks because it also disables all the nice visual effects. Setting the compositor to XRender instead of OpenGL does seem to fix this issue for me, I've been well over a week without seeing this issue.
Is that an NVIDIA driver issue? In that case has someone got in contact with them? Because I recently found they have a mailing list for linux bugs and it looks like they answer unlike their forum, just to let you know
Came here to say this happens to me also. This is 100% reproducible on my system every time I launch Counter-Strike: Global Offensive through steam. Entire desktop freezes when compositing is off (Background, widgets, task manager, system tray area, etc). KWin version: 5.15.5 Qt Version: 5.12.1 Qt compile version: 5.12.1 XCB compile version: 1.13.1 Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 1070/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 418.74 OpenGL platform interface: GLX OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 418.74 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 Linux kernel version: 5.0.17 Direct rendering: Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: yes
Created attachment 120476 [details] kwin info
*** Bug 409172 has been marked as a duplicate of this bug. ***
*** Bug 410216 has been marked as a duplicate of this bug. ***
*** Bug 381197 has been marked as a duplicate of this bug. ***
Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-19-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 31.2 GiB of RAM same panel freezes. even if 1. you disable compositor manually - panel is working 2. start any(?) opengl application, even not a game, krita did the trick for me 3. panel freezes!
I have the same problem
*** Bug 373797 has been marked as a duplicate of this bug. ***
I have the same problem. I do not need to play a game or have any application open, the panel simply stops working when I disable the compositor. Happens consistently. I use KDE Plasma 5.17.5 on Manjaro with NVIDIA GeForce GTX 1060, 440.44 drivers. How has this been problem been around for 5 years?
My krita program keeps crashing. Can someone help me? Thanks From David
I would kindly suggest you read this first and resubmit your question under the right thread, else you probably won't get much of a response. http://www.catb.org/esr/faqs/smart-questions.html
If you are like me then I simply switched to xrender as my compositor. This solved the issues. On 3/23/20 6:02 PM, Nick wrote: > https://bugs.kde.org/show_bug.cgi?id=353983 > > --- Comment #165 from Nick <nick.craig.law@gmail.com> --- > I would kindly suggest you read this first and resubmit your question under the > right thread, else you probably won't get much of a response. > > http://www.catb.org/esr/faqs/smart-questions.html >
Can confirm on Arch Linux with OpenGL 2.0 backend and proprietary Nvidia graphics driver. KDE plasma version: 5.18.3
What can we say... let's hope plasma 6 will be free or maybe a vulkan back end will magically fix it?
Took a look at this from the NVIDIA side and determined that it is a bug in our X driver. KWin / plasmashell aren't doing anything wrong. Should be able to get a fix out in an upcoming driver release. I'll include an entry in the change log mentioning the issue.
That's great news! Once there's a fix, can you include a link to it in the URL field of this bug, and put the version of the driver that includes the fix in the Version fixed in field? Thanks! I'll keep this open since some people are saying that they experience this with Intel drivers too; perhaps they will require a driver fix as well.
Finally!! Thanks for the fix!
Finally!! Thanks for the fix! Edit: BTW, can Nvidia guys check on this? Another annoying bug related to propietary driver. https://bugs.kde.org/show_bug.cgi?id=364593
That is fantastic. I hope to test the fix soon. Let me know if I can buy you a beer Eric. I will send some cash your way.. This has been so annoying for awhile now.
*** Bug 421071 has been marked as a duplicate of this bug. ***
(In reply to Steven Gilberd from comment #84) > I don't think this is just an NVIDIA issue. The log messages from their > driver are useful, but I've been experiencing this exact bug with Intel > graphics for years. > > The system I've encountered it on is a late 3013 MacBook Pro (the 13" one > with Intel-only graphics). Are you still getting this? Nvidia devs claim the problem was in their driver, that's a bit odd.
(In reply to Antonio Orefice from comment #175) > Are you still getting this? > Nvidia devs claim the problem was in their driver, that's a bit odd. This was fixed on my laptop about a year ago. So perhaps this was two independent driver bugs, and Intel just happened to fix theirs first?
nvidia 450.51 beta claims to fix this issue.
(In reply to Sebastian Kuźlak from comment #177) > nvidia 450.51 beta claims to fix this issue. Yes. Here's the changelog: https://www.nvidia.com/download/driverResults.aspx/160555/en-us > Fixed a bug causing the Plasma desktop panel to freeze when compositing is > disabled (https://bugs.kde.org/show_bug.cgi?id=353983) > Fixed a bug that could cause a KDE Plasma session to crash > when running under Wayland.
(In reply to Sebastian Kuźlak from comment #177) > nvidia 450.51 beta claims to fix this issue. Yes, 450.51 should contain the fix. I would appreciate it if anyone who has been affected by this bug would be able to verify.
(In reply to Erik Kurzinger from comment #179) > (In reply to Sebastian Kuźlak from comment #177) > > nvidia 450.51 beta claims to fix this issue. > > Yes, 450.51 should contain the fix. I would appreciate it if anyone who has > been affected by this bug would be able to verify. I had this issue and 450.51 did indeed fix it for me. Compositing is off but the system tray/widgets/etc all function properly.
Hooray!
Fixed for me too! (nvidia 450.57-1 on Arch) When disabling compositing with Alt+Shift+F12 there is a brief moment where the panel gets a dark color (like before the fix), but that color disappears after 2s and everything works! :)
*** Bug 421033 has been marked as a duplicate of this bug. ***