The entire screens freeze for some 5 seconds when notifications from the tray are about to scroll down or disappear. This only affects drawing of screen content, it doesn't affect sound or cursor motion. If relevant, the particular tray notifications are about bluetooth devices. The particular order is like this: -two messages (M1 - connection deactivated, M2 - connection timed out) appear one above the other -2-3 seconds pass -freeze for 5 seconds -M1 disappears, M2 animates going down -messages reappear and animate again, but without freezes. When the freeze ends, the first image drawn on the displays is actually a "frame" before the one seen during the freeze. Suppose we have a sequence of frames: f0, f1, f2 (freeze here, f2 shown for 5 seconds), f1, f3, f4, etc. If plasmashell is stopped, this bug does not happen and the notifications are shown in small windows at the top of the main screen. Reproducible: Always Original bug here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840141
Forgotten details: Computer: ThinkPad Edge E540: Graphics: 4th Gen Core Processor Integrated Graphics Controller [8086:416] video module: i915
Created attachment 101726 [details] attachment-28171-0.html Please provide output of: qdbus org.kde.KWin /KWin supportInformation
Version ======= KWin version: 5.8.2 Qt Version: 5.6.1 Qt compile version: 5.6.1 XCB compile version: 1.12 Operation Mode: X11 only Build Options ============= KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_INPUT: yes HAVE_DRM: yes HAVE_GBM: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes HAVE_WAYLAND_EGL: yes X11 === Vendor: The X.Org Foundation Vendor Release: 11804000 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: 0 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Options ======= focusPolicy: 1 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 100 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: true focusStealingPreventionLevel: 2 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 glSmoothScale: 2 colorCorrected: false xrenderSmoothScale: false maxFpsInterval: 16666666 refreshRate: 0 vBlankTime: 6000000 glStrictBinding: true glStrictBindingFollowsDriver: true glCoreProfile: true glPreferBufferSwap: 101 glPlatformInterface: 1 windowsBlockCompositing: true Screen Edges ============ desktopSwitching: false desktopSwitchingMovingClients: false cursorPushBackDistance: 1x1 timeThreshold: 150 reActivateThreshold: 350 actionTopLeft: 0 actionTop: 0 actionTopRight: 0 actionRight: 0 actionBottomRight: 0 actionBottom: 0 actionBottomLeft: 0 actionLeft: 0 Screens ======= Multi-Head: no Active screen follows mouse: yes Number of Screens: 2 Screen 0: --------- Name: VGA-1 Geometry: 0,0,2048x1152 Refresh Rate: 59.9087 Screen 1: --------- Name: eDP-1 Geometry: 2048,0,1920x1080 Refresh Rate: 60.0073 Compositing =========== Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL version string: 3.3 (Core Profile) Mesa 12.0.3 OpenGL platform interface: GLX OpenGL shading language version string: 3.30 Driver: Intel GPU class: Haswell OpenGL version: 3.3 GLSL version: 3.30 Mesa version: 12.0.3 X server version: 1.18.4 Linux kernel version: 4.3 Direct rendering: Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no Loaded Effects: --------------- zoom slidingpopups slide screenshot flipswitch kwin4_effect_windowaperture desktopgrid coverswitch kwin4_effect_morphingpopups presentwindows highlightwindow kwin4_effect_dialogparent contrast startupfeedback screenedge kscreen Currently Active Effects: ------------------------- contrast Effect Settings: ---------------- zoom: zoomFactor: 1.2 mousePointer: 0 mouseTracking: 0 enableFocusTracking: false followFocus: true focusDelay: 350 moveFactor: 20 targetZoom: 1 slidingpopups: fadeInTime: 150 fadeOutTime: 250 slide: screenshot: flipswitch: tabBox: false tabBoxAlternative: false duration: 200 angle: 30 xPosition: 0.33000001311302185 yPosition: 1 windowTitle: true kwin4_effect_windowaperture: desktopgrid: zoomDuration: 300 border: 10 desktopNameAlignment: 0 layoutMode: 0 customLayoutRows: 2 usePresentWindows: true coverswitch: animationDuration: 200 animateSwitch: true animateStart: true animateStop: true reflection: true windowTitle: true zPosition: 1353 primaryTabBox: true secondaryTabBox: false kwin4_effect_morphingpopups: 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: contrast: startupfeedback: type: 0 screenedge: kscreen: On 23/10/16 21:57, Martin Gräßlin via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=371537 > > --- Comment #2 from Martin Gräßlin <mgraesslin@kde.org> --- > Please provide output of: > qdbus org.kde.KWin /KWin supportInformation >
What I don't really understand from your bug report: is plasma freezing or KWin? Is it a problem of just the rendering of the notifications or is e.g. glxgears no longer updated as well? Can you still move the mouse cursor while the freeze happens?
KWin. Everything that is displayed, on both displays, follows that "frame sequence": f0, f1, f2 (freeze here, f2 shown for 5 seconds), f1, f3, f4 . The cursor which is still movable. On 24/10/16 08:31, Martin Gräßlin via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=371537 > > --- Comment #4 from Martin Gräßlin <mgraesslin@kde.org> --- > What I don't really understand from your bug report: is plasma freezing or > KWin? Is it a problem of just the rendering of the notifications or is e.g. > glxgears no longer updated as well? Can you still move the mouse cursor while > the freeze happens? >
Correction: the cursor _is_ still movable.
are you using the intel xorg driver or the modesettings xorg driver? Can you check in dmesg whether you see anything related to the freeze (e.g. hung gpu)? Can you check in /var/log/Xorg.0.log for any errors which might be related.
Hi, Unfortunately Xorg.0.log says nothing about possible errors. Dmesg says at random times things such as: [ 9.404406] [drm:cpt_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun [ 9.417934] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B [ 9.417950] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun [ 9.468543] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 9.473467] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device But it has been saying it for years. Unfortunately, even after looking on the internet I don't know how to determine if this is the modesetting driver or not. One more detail is that if I run optirun kwin --replace &, this bug will disappear until the next restart. On 24/10/16 09:03, Martin Gräßlin via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=371537 > > --- Comment #7 from Martin Gräßlin <mgraesslin@kde.org> --- > are you using the intel xorg driver or the modesettings xorg driver? Can you > check in dmesg whether you see anything related to the freeze (e.g. hung gpu)? > Can you check in /var/log/Xorg.0.log for any errors which might be related. >
xorg.0.log should tell you which driver you are using. If it says something like "LoadModule: intel" then you are on intel.
Created attachment 101751 [details] Xorg.0.log
Hi, there doesn't seem to be any Intel driver loading. I've attached the entire file, as it doesn't seem to containing anything private.
Yeah it's using the modesettings driver. Good. If you have the possibility, please ssh into your system and attach gdb to kwin and try to get a backtrace from when the system freezes.
After upgrading Debian to latest Testing (new kernel, KDE and Qt stuff) I don't see this anymore. Also, doing ssh precisely during those 5 seconds of freeze looks pretty difficult. Should this reproduce, I would need an easier method to debug.
In case it happens again, please reopen.
I confirm this continues to happen. Only twice in some 8 hours, so it's intruding a lot less. If there's a way to get some debug information, other than ssh in the precise seconds this happens, I'll gladly do.
Really difficult. The problem could be anywhere and thus asking for specific debug info is tricky. I'm kind of lacking ideas where the problem is and what could cause it. A reliable way to reproduce would be good, but we don't have that as even for you it only happens from time to time.
I got this happening quite often again with 5.8.6 of Debian. The freezes are shorter this time, and the „frame back” only stays for very short instant. I think this _may_ have to do something with the i915 driver. If I run plasmashell on the discrete Nvidia card ("optirun plasmashell &" details at https://wiki.debian.org/Bumblebee ), this problem doesn't happen any more. However, when running with Nvidia plasma has a strange colour tint notifications have unpainted areas, so I might be comparing apples to oranges.
This issue report is quite old. Can you please confirm, that it still persists with KDE 5.23?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!