Summary: | KDE 5.18: window flickering and some system crashes | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Duns <web> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | major | CC: | nate, web |
Priority: | NOR | ||
Version: | 5.18.0 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Duns
2020-02-14 07:03:35 UTC
Not always this happens, I noticed I'm not sure that enabling virtual desktops is the cause of flickering, that happens sometimes. And today I have had two system crashes. What log should I check? This my configuration: inxi -SMGxxxz System: Host: duns-neon Kernel: 5.3.0-28-generic x86_64 bits: 64 gcc: 7.4.0 Desktop: KDE Plasma 5.18.0 (Qt 5.13.2) dm: sddm,sddm Distro: KDE neon User Edition 5.18 Machine: Device: desktop Mobo: MSI model: B250M PRO-VD (MS-7A74) v: 1.0 serial: N/A UEFI [Legacy]: American Megatrends v: 1.20 date: 12/02/2016 Graphics: Card-1: Intel HD Graphics 630 bus-ID: 00:02.0 chip-ID: 8086:5912 Card-2: NVIDIA GK208B [GeForce GT 710] bus-ID: 01:00.0 chip-ID: 10de:128b Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nouveau (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: NV106 version: 4.3 Mesa 19.2.8 Direct Render: Yes and this (neofecth --off) OS: KDE neon User Edition 5.18 x86_64 Host: MS-7A74 1.0 Kernel: 5.3.0-28-generic Uptime: 30 mins Packages: 1992 Shell: bash 4.4.20 Resolution: 1920x1080 DE: KDE WM: KWin Theme: Breeze [KDE], Breeze [GTK2/3] Icons: Humanity [KDE], Humanity [GTK2/3] Terminal: konsole CPU: Intel i3-7100 (2) @ 3.900GHz GPU: Intel Integrated Graphics GPU: NVIDIA GeForce GT 710 Memory: 2069MiB / 7854MiB btw I noticed another bug, reported here: https://bugs.kde.org/show_bug.cgi?id=417818 I don't know if it is related with this one, maybe... Today I installed ndvidia driver. Maybe this was the problem: I will see and tell you. so far it has worked: probably it was a driver problem. Thanks for the update; changing status. |