My screen is flickering in Leap 15.5/GNOME. It lasts one or two seconds and doesn’t seem to happen when the mouse and keyboard are active. Other than that, it seems random. Happens using both Wayland and X. I have an Intel CometLake-S GT2 graphics card and an HP Pavilion 27xw monitor. The screen resolution and refresh rate are set to the defaults: 1920, 16:9 and 60%. This has been going on for awhile, maybe since installing 15.5. It doesn’t happen when I log into the Ice WM for a few hours, so I’m pretty sure the problem is in GNOME. Any suggestions to help me troubleshoot this? Thanks.
Welcome to the forums 
Off the top of my head:
- Check if issue persists after disabling all extensions and logging out and back in.
- Check if the system is suspending and being un-suspended during these events:
sudo journalctl -k -g suspend
Edit: additionally would be nice to have the outputs of the following:
sudo coredumpctl list
sudo journalctl -p3 -b
Maybe an obvious thing to check, but I’d make sure the physical connections are secure, and the contacts are free of dust. Hard to diagnose if that might be the issue without actually seeing it, but definitely something I’d look to eliminate as a cause of the issue here.
Not sure what you mean by “extensions.” From the terminal,
$ sudo journalctl -k -g suspend
.
Apr 02 07:03:21 jclinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 02 07:03:21 jclinux kernel: PM: suspend exit
Apr 02 21:33:37 jclinux kernel: PM: suspend entry (deep)
Apr 02 22:03:07 jclinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 02 22:03:07 jclinux kernel: PM: suspend exit
Apr 02 22:33:12 jclinux kernel: PM: suspend entry (deep)
Apr 02 22:44:40 jclinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 02 22:44:40 jclinux kernel: PM: suspend exit
Apr 02 23:14:45 jclinux kernel: PM: suspend entry (deep)
Apr 03 06:40:50 jclinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 03 06:40:50 jclinux kernel: PM: suspend exit
$ sudo coredumpctl list
If 'coredumpctl' is not a typo you can use command-not-found to lookup the package that contains it, like this:
cnf coredumpctl
$ sudo journalctl -p3 -b
Apr 03 06:40:50 jclinux kernel: usb 1-5: PM: dpm_run_callback(): usb_dev_resume+0x0/0x10 [usbcore] returns -5
Apr 03 06:40:50 jclinux kernel: usb 1-5: PM: failed to resume async: error -5
Apr 03 06:46:18 jclinux smartd[889]: Device: /dev/nvme0, number of Error Log entries increased from 936 to 937
Apr 03 08:15:27 jclinux gnomesu-pam-backend[22918]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Apr 03 08:15:27 jclinux gnomesu-pam-backend[22918]: gkr-pam: couldn't unlock the login keyring.
Apr 03 09:51:11 jclinux sudo[29420]: gkr-pam: unable to locate daemon control file
Apr 03 09:57:02 jclinux sudo[29626]: gkr-pam: unable to locate daemon control file
Apr 03 09:57:06 jclinux sudo[29626]: gkr-pam: unable to locate daemon control file
Apr 03 09:57:07 jclinux sudo[29626]: gkr-pam: unable to locate daemon control file
Apr 03 09:57:10 jclinux sudo[29626]: tipper : 3 incorrect password attempts ; TTY=pts/0 ; PWD=/home/tipper ; USER=root ; COMMAND=coredumpctl list
Apr 03 09:57:23 jclinux su[29641]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Apr 03 09:57:23 jclinux su[29641]: gkr-pam: couldn't unlock the login keyring.
Apr 03 12:51:42 jclinux su[8431]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control
Apr 03 12:51:42 jclinux su[8431]: gkr-pam: couldn't unlock the login keyring.
Very good idea, it’s getting dusty back there. I need to take some time to clean everything up.
I did some dusting yesterday, the kernel didn’t seem to appreciate my efforts saying something about EMI…
Apr 03 14:52:44 suse-pc kernel: usb 3-1-port2: disabled by hub (EMI?), re-enabling...
Apr 03 14:52:44 suse-pc kernel: usb 3-1.2: USB disconnect, device number 5
It added the USB device back though, so no complaints 
In your case the IceWM session working for a few hours would preclude dust or such other h/w issues, that was my initial thinking at least 
Do these suspend entry/exit entries correspond to the screen flickering by any chance?
You appear to be missing systemd-coredump package. Docs on configuring it:
Do these suspend entry/exit entries correspond to the screen flickering by any chance?
Could be. I’ll have to log them to be sure. Thing is, it’s not locking as it seems it would. It turns blank for a couple of seconds, then returns. I have it set to suspend after 30 minutes of inactivity, no screensaver. The flickering can happen several times in that interval.
Probably not it then, try searching for Extensions from the app list (Super+A) and disable everything, logout and then log back in to see if the issue persists.
Post
inxi -aFz
Disabling the extensions seems to reduce the flickering, but doesn’t quite eliminate it. My log:
04/04/24 04:34:00 PM
04/04/24 06:35:00 PM
04/04/24 06:54:00 PM
04/04/24 07:31:00 PM
04/04/24 08:05:00 PM
04/04/24 08:21:00 PM
04/05/24 07:27:00 AM
04/05/24 08:05:00 AM
04/05/24 08:09:00 AM
04/05/24 08:40:00 AM 2
04/05/24 09:43:00 AM
04/05/24 09:50:00 AM Disabled extensions
04/05/24 10:46:00 AM
$ journalctl -k -g suspend
.
Apr 04 06:40:56 jclinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 04 06:40:56 jclinux kernel: PM: suspend exit
Apr 04 21:15:05 jclinux kernel: PM: suspend entry (deep)
Apr 05 07:02:45 jclinux kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 05 07:02:45 jclinux kernel: PM: suspend exit
$ inxi -aFz
System:
Kernel: 5.14.21-150500.55.52-default arch: x86_64 bits: 64 compiler: gcc
v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.52-default
root=UUID=d2e1e764-5db2-4593-828b-284da44eca1d splash=silent
resume=/dev/disk/by-uuid/a5dc2422-26d6-475c-891b-67dc3149a87f
preempt=full mitigations=auto quiet security=apparmor
Desktop: GNOME v: 41.9 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM v: 41.3
Distro: openSUSE Leap 15.5
Machine:
Type: Desktop Mobo: Acer model: Aspire TC-895 v: V:1.0
serial: <superuser required> UEFI: American Megatrends v: R01-A0
date: 05/19/2020
CPU:
Info: model: Intel Core i5-10400 bits: 64 type: MT MCP arch: Comet Lake
gen: core 10 level: v3 note: check built: 2020 process: Intel 14nm family: 6
model-id: 0xA5 (165) stepping: 3 microcode: 0xF8
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 800 min/max: 800/4300 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 9: 800 10: 800 11: 800 12: 800 bogomips: 69597
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: Enhanced IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB:
conditional, RSB filling, PBRSB-eIBRS: SW sequence
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel CometLake-S GT2 [UHD Graphics 630]
vendor: Acer Incorporated ALI driver: i915 v: kernel arch: Gen-9.5
process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1
empty: DP-1,HDMI-A-2,HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:9bc8
class-ID: 0300
Display: wayland server: X.org v: 1.21.1.4 with: Xwayland v: 22.1.5
compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
alternate: intel dri: iris gpu: i915 display-ID: 0
Monitor-1: HDMI-A-1 model: HP 27xw serial: <filter> built: 2018
res: 1920x1080 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23")
diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel UHD Graphics 630 (CML
GT2) direct render: Yes
Audio:
Device-1: Intel Comet Lake PCH-V cAVS vendor: Acer Incorporated ALI
driver: snd_hda_intel bus-ID: 1-2.1:18 v: kernel chip-ID: 0a67:d090
alternate: snd_sof_pci_intel_cnl class-ID: 0300 bus-ID: 00:1f.3
chip-ID: 8086:a3f0 serial: <filter> class-ID: 0403
Device-2: Medeli AudioPro X5 Microphone type: USB
driver: hid-generic,snd-usb-audio,usbhid
Device-3: Creative Sound BlasterX Kratos S5 type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-5:24 chip-ID: 041e:30ca
class-ID: 0300 serial: <filter>
Sound API: ALSA v: k5.14.21-150500.55.52-default running: yes
Sound Server-1: PulseAudio v: 15.0 running: yes
Sound Server-2: PipeWire v: 0.3.64 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Acer Incorporated ALI driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-3:4
chip-ID: 8087:0029 class-ID: e001
Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Drives:
Local Storage: total: 1.38 TiB used: 562.15 GiB (39.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVLQ512HALU-00000 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: FXV7000Q temp: 12.8 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM003-1SB102
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: HPH4 scheme: GPT
Partition:
ID-1: / raw-size: 35 GiB size: 35 GiB (100.00%) used: 12.48 GiB (35.7%)
fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-2: /boot/efi raw-size: 500 MiB size: 499.7 MiB (99.95%)
used: 5.2 MiB (1.0%) fs: vfat dev: /dev/nvme0n1p5 maj-min: 259:5
ID-3: /home raw-size: 40 GiB size: 39.98 GiB (99.95%)
used: 3.16 GiB (7.9%) fs: xfs dev: /dev/nvme0n1p7 maj-min: 259:7
ID-4: /opt raw-size: 35 GiB size: 35 GiB (100.00%) used: 12.48 GiB (35.7%)
fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-5: /tmp raw-size: 35 GiB size: 35 GiB (100.00%) used: 12.48 GiB (35.7%)
fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
ID-6: /var raw-size: 35 GiB size: 35 GiB (100.00%) used: 12.48 GiB (35.7%)
fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:6
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 16 GiB used: 40.1 MiB (0.2%)
priority: -2 dev: /dev/nvme0n1p9 maj-min: 259:9
Sensors:
System Temperatures: cpu: 27.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 371 Uptime: 6d 6h 4m wakeups: 75 Memory: 15.5 GiB
used: 3.41 GiB (22.0%) Init: systemd v: 249 target: graphical (5)
default: graphical tool: systemctl Compilers: gcc: 7.5.0 alt: 7 Packages:
pm: rpm pkgs: N/A note: see --rpm tools: gnome-software,yast,zypper
pm: flatpak pkgs: 0 Shell: Bash v: 4.4.23 running-in: gnome-terminal
inxi: 3.3.23
Check graphics-related logging…
sudo journalctl -b | egrep "i915|drm"
Another idea: You could try using a recent stable kernel to see if this helps…
https://en.opensuse.org/SDB:InstallNewerKernel
I don’t see anything corresponding to the flickering but something interesting:
What’s this about? I’ll try upgrading the kernel.
Upgrade BIOS - v. R01-A3 2021/08/03 is available.
Post
zypper se -si egl
Wayland uses EGL, but I don’t see its presence.
Also where is Vulkan?
It’s an issue in X, too, not just Wayland.
$ zypper se -si egl
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-----------------------------+---------+-----------------------+--------+--------------------------------------------------
i+ | gegl-0_4 | package | 0.4.34-150400.3.5.2 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i+ | gegl-0_4-lang | package | 0.4.34-150400.3.5.2 | noarch | Update repository with updates from SUSE Linux Enterprise 15
i+ | libgegl-0_4-0 | package | 0.4.34-150400.3.5.2 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
i+ | libwayland-egl1 | package | 99~1.21.0-150500.1.1 | x86_64 | openSUSE:Leap:15.5
i+ | libwayland-egl1 | package | 99~1.21.0-150500.1.1 | x86_64 | Main Repository
i+ | Mesa-libEGL1 | package | 22.3.5-150500.76.pm.4 | x86_64 | (System Packages)
i+ | typelib-1_0-GeocodeGlib-1_0 | package | 3.26.4-150400.3.5.2 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
zypper se -si vulkan
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+---------------------------+---------+-----------------------+--------+-----------------------
i+ | libgstvulkan-1_0-0 | package | 1.22.0-lp155.3.7.1 | x86_64 | Main Update Repository
i+ | libvulkan1 | package | 1.2.133-1.26 | x86_64 | openSUSE:Leap:15.5
i+ | libvulkan1 | package | 1.2.133-1.26 | x86_64 | Main Repository
i+ | libvulkan_intel | package | 22.3.5-150500.76.pm.4 | x86_64 | (System Packages)
i+ | Mesa-vulkan-device-select | package | 22.3.5-150500.76.pm.4 | x86_64 | (System Packages)
Mesa 3D from Packman?
Try to use Mesa 3D from Main repo.
Post
zypper se -si WaylandEgl
My inxi info:
:~> inxi -aFz
...
Graphics:
...
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: egl: 1.4 drv: kms_swrast surfaceless:
drv: radeonsi x11: drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 22.3.5 glx-v: 1.4
direct-render: yes renderer: AMD Radeon Graphics (raven LLVM 15.0.7 DRM
3.49 5.14.21-150500.55.52-default) device-ID: 1002:15d8 memory: 1.95 GiB
unified: no
API: Vulkan v: 1.2.133 layers: 3 device: 0 type: integrated-gpu name: AMD
Radeon Graphics (RADV RAVEN) driver: mesa radv v: 22.3.5
device-ID: 1002:15d8 surfaces: xcb,xlib
...
inxi: 3.3.34
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.