You are not logged in.
- Topics: Active | Unanswered
#1 2023-09-01 16:02:22
- pieterv
- Member
- Registered: 2014-08-24
- Posts: 28
[SOLVED] Screen goes suddenly to 1% brightness
Hello everyone,
I'm trying to figure out what is going on on my laptop. All of a sudden, the brightness goes to 1%. I think this happens more when the GPU or CPU are used intensly (Steam game, virtualbox), but it can also happen randomly while browsing. I think it only happens on battery power.
The thing is, the logs don't seem to show anything. For example, today, at 17:46:50 it happened, and here are the logs of around that period:
Sep 01 17:45:00 archt14 rtkit-daemon[1110]: Supervising 13 threads of 6 processes of 1 users.
Sep 01 17:45:00 archt14 rtkit-daemon[1110]: Supervising 13 threads of 6 processes of 1 users.
Sep 01 17:45:33 archt14 plasmashell[1154]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x5629f58661a0) QQmlContext(0x5629f63634b0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Sep 01 17:45:33 archt14 plasmashell[1154]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x5629f58661a0) QQmlContext(0x5629f63634b0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
Sep 01 17:46:03 archt14 rtkit-daemon[1110]: Supervising 13 threads of 6 processes of 1 users.
Sep 01 17:46:03 archt14 rtkit-daemon[1110]: Supervising 13 threads of 6 processes of 1 users.
Sep 01 17:46:05 archt14 rtkit-daemon[1110]: Supervising 13 threads of 6 processes of 1 users.
Sep 01 17:46:05 archt14 rtkit-daemon[1110]: Supervising 13 threads of 6 processes of 1 users.
Sep 01 17:46:32 archt14 rtkit-daemon[1110]: Supervising 13 threads of 6 processes of 1 users.
Sep 01 17:46:32 archt14 rtkit-daemon[1110]: Supervising 13 threads of 6 processes of 1 users.
Sep 01 17:46:58 archt14 wpa_supplicant[890]: wlan0: WPA: Group rekeying completed with e8:df:70...... [GTK=CCMP]
Sep 01 17:47:05 archt14 org_kde_powerdevil[1201]: QObject::disconnect: Unexpected nullptr parameter
Sep 01 17:47:05 archt14 kernel: input: M720 Triathlon Keyboard as /devices/virtual/misc/uhid/0005:046D:B015.0007/input/input37
Sep 01 17:47:05 archt14 kernel: input: M720 Triathlon Mouse as /devices/virtual/misc/uhid/0005:046D:B015.0007/input/input38
Sep 01 17:47:05 archt14 kernel: hid-generic 0005:046D:B015.0007: input,hidraw1: BLUETOOTH HID v0.13 Keyboard [M720 Triathlon] on 04:7b.........
Sep 01 17:47:05 archt14 org_kde_powerdevil[1201]: QObject::disconnect: Unexpected nullptr parameter
Sep 01 17:47:05 archt14 systemd-logind[796]: Watching system buttons on /dev/input/event18 (M720 Triathlon Keyboard)
Sep 01 17:47:05 archt14 kcminit[81655]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
Sep 01 17:47:05 archt14 kcminit[81655]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
Sep 01 17:47:05 archt14 kcminit[81655]: kcm_touchpad: Using X11 backend
Sep 01 17:47:10 archt14 kernel: input: M720 Triathlon Keyboard as /devices/virtual/misc/uhid/0005:046D:B015.0008/input/input40
Sep 01 17:47:10 archt14 kernel: input: M720 Triathlon Mouse as /devices/virtual/misc/uhid/0005:046D:B015.0008/input/input41
Sep 01 17:47:10 archt14 kernel: hid-generic 0005:046D:B015.0008: input,hidraw1: BLUETOOTH HID v0.13 Keyboard [M720 Triathlon] on 04:7b:cb:bc:f4:33
Sep 01 17:47:10 archt14 org_kde_powerdevil[1201]: QObject::disconnect: Unexpected nullptr parameter
Sep 01 17:47:10 archt14 org_kde_powerdevil[1201]: QObject::disconnect: Unexpected nullptr parameter
Sep 01 17:47:10 archt14 systemd-logind[796]: Watching system buttons on /dev/input/event18 (M720 Triathlon Keyboard)
Sep 01 17:47:10 archt14 kcminit[81676]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
Sep 01 17:47:10 archt14 kcminit[81676]: Initializing "/usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
Sep 01 17:47:10 archt14 kcminit[81676]: kcm_touchpad: Using X11 backend
Sep 01 17:47:11 archt14 wpa_supplicant[890]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-70 noise=-109 txrate=54000How could I debug it further?
Currently I'm using KDE Plasma 5.27.7 on X11. All software is up to date.
Hardware is a ThinkPad T14 Gen 3, with AMD Ryzen 7 PRO 6850U
First thing I'm going to try myself is using LXDE for a while, so I can rule out it's a KDE Plasma issue
My current solution is to patiently search the cursor on the screen and try to reboot. Or connect my second screen, go to display setting and turn off and on the main laptop screen.
Thanks for any hints.
Last edited by pieterv (2024-01-26 07:40:16)
Offline
#2 2023-10-28 16:54:57
- pieterv
- Member
- Registered: 2014-08-24
- Posts: 28
Re: [SOLVED] Screen goes suddenly to 1% brightness
Coming back to my own question. I have now tested both Plasma and Gnome and have the same issue.
I have also tested it on both Gnome Xorg and Gnome Wayland, and has same issue.
Still nothing in the logs though.
Next I could try is:
- Working with a different user, so I can rule out a user setting (probably not likely)
- Try multiboot in Windows, so I can rule out it's a Linux / Kernel issue (**shudder**)
I'm thinking it might turn out to be a hardware problem...
Last edited by pieterv (2023-10-28 17:41:55)
Offline
#3 2023-11-26 16:09:49
- pieterv
- Member
- Registered: 2014-08-24
- Posts: 28
Re: [SOLVED] Screen goes suddenly to 1% brightness
I'm 3 weeks on Windows 11, and have no issues at all. So it must be Linux specific. No ideas how to proceed now.
Offline
#4 2023-11-26 16:48:57
- Xyne
- Administrator/PM
- Registered: 2008-08-03
- Posts: 6,963
- Website
Re: [SOLVED] Screen goes suddenly to 1% brightness
I suspect that your system is detecting voltage dips under load while running on battery. Try to monitor the reported voltage to see if you can detect any while running both Linux and Windows. My hypothesis is that either Linux is erroneously detecting dips, or Windows simply doesn't visibly react to them. In the former case I don't know exactly where to begin debugging this but I would start with ACPI. In the latter case the battery should probably be replaced.
On Linux you can inspect the raw voltage values under /sys/class/power_supply/BAT0/voltage_now or using a package such as upower.
Your battery may be "BAT1" or another value on your system.
I'm sure that there are tools to easily monitor and graph the voltage over time but I'm not familiar with them. Here's a simple script to log the voltage at regular intervals:
#!/usr/bin/env bash
set -euo pipefail
while true
do
timestamp=$(date -Ins)
voltage=$(< /sys/class/power_supply/BAT0/voltage_now)
echo "$timestamp $voltage"
# Decrease this for shorter logging intervals.
sleep 0.5
doneRun that and stress the system on battery until the screen dims, then check if it detected a voltage dip.
How old is the battery?
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
#5 2023-11-26 16:56:10
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,578
Re: [SOLVED] Screen goes suddenly to 1% brightness
https://wiki.archlinux.org/title/Backli … interfaces
Inspect what the brightness levels are when the backlight is normal, when it's off and see whether you can fix the backlight by changing it to a sane value.
Do you use stuff like TLP etc?
Edit: F5!
tail /sys/class/power_supply/BAT0/*for the battery stats
Last edited by seth (2023-11-26 17:00:30)
Offline
#6 2023-12-13 14:41:58
- pieterv
- Member
- Registered: 2014-08-24
- Posts: 28
Re: [SOLVED] Screen goes suddenly to 1% brightness
Xyne wrote:
I suspect that your system is detecting voltage dips under load while running on battery. Try to monitor the reported voltage to see if you can detect any while running both Linux and Windows. My hypothesis is that either Linux is erroneously detecting dips, or
Thank you for taking the time to reply. I took me some time, but finally I have your script running and I had a few issues while it was running. There is nothing out of the ordinary to be see. I'm even running it every 0.1 seconds. This is my output (i adjusted the output a bit):
Wed Dec 13 03:35:56 PM CET 2023 voltage=13100000 brightness=199
Wed Dec 13 03:35:56 PM CET 2023 voltage=13100000 brightness=199
Wed Dec 13 03:35:57 PM CET 2023 voltage=13100000 brightness=199
Wed Dec 13 03:35:57 PM CET 2023 voltage=13100000 brightness=199
Wed Dec 13 03:35:57 PM CET 2023 voltage=13100000 brightness=199
Wed Dec 13 03:35:57 PM CET 2023 voltage=13100000 brightness=199This outpout repeats before and after the moment the issue happens. Voltage changes slightly every once in a while, but seemingly unrelated to the moment the issue happens.
The laptop and battery are about half a year old.
The issue is happening both on AC power as on battery.
Last edited by pieterv (2023-12-13 18:32:14)
Offline
#7 2023-12-13 14:53:20
- pieterv
- Member
- Registered: 2014-08-24
- Posts: 28
Re: [SOLVED] Screen goes suddenly to 1% brightness
seth wrote:
...
Thanks Seth for replying.
Using the script of Xyne, I have monitored the brightness value in /sys/class/backlight/amdgpu_bl0/brightness and it stays constantly the same at the moment the effective brightness drops.
I have tried pushing the keyboard buttons to change the brightness once the issue happens, but that doesn't do anything. I could try to write directly to /sys/class/backlight/amdgpu_bl0/brightness and see if it does anything.
The linux package tlp is not installed
Here is the output of tail /sys/class/power_supply/BAT0/*
==> /sys/class/power_supply/BAT0/alarm <==
0
==> /sys/class/power_supply/BAT0/capacity <==
100
==> /sys/class/power_supply/BAT0/capacity_level <==
Full
==> /sys/class/power_supply/BAT0/charge_behaviour <==
[auto] inhibit-charge force-discharge
==> /sys/class/power_supply/BAT0/charge_control_end_threshold <==
100
==> /sys/class/power_supply/BAT0/charge_control_start_threshold <==
0
==> /sys/class/power_supply/BAT0/charge_start_threshold <==
0
==> /sys/class/power_supply/BAT0/charge_stop_threshold <==
100
==> /sys/class/power_supply/BAT0/cycle_count <==
110
==> /sys/class/power_supply/BAT0/device <==
tail: error reading '/sys/class/power_supply/BAT0/device': Is a directory
==> /sys/class/power_supply/BAT0/energy_full <==
36700000
==> /sys/class/power_supply/BAT0/energy_full_design <==
39380000
==> /sys/class/power_supply/BAT0/energy_now <==
36700000
==> /sys/class/power_supply/BAT0/hwmon2 <==
tail: error reading '/sys/class/power_supply/BAT0/hwmon2': Is a directory
==> /sys/class/power_supply/BAT0/manufacturer <==
SMP
==> /sys/class/power_supply/BAT0/model_name <==
LNV-5B10W51861@
==> /sys/class/power_supply/BAT0/power <==
tail: error reading '/sys/class/power_supply/BAT0/power': Is a directory
==> /sys/class/power_supply/BAT0/power_now <==
0
==> /sys/class/power_supply/BAT0/present <==
1
==> /sys/class/power_supply/BAT0/serial_number <==
2220
==> /sys/class/power_supply/BAT0/status <==
Full
==> /sys/class/power_supply/BAT0/subsystem <==
tail: error reading '/sys/class/power_supply/BAT0/subsystem': Is a directory
==> /sys/class/power_supply/BAT0/technology <==
Li-poly
==> /sys/class/power_supply/BAT0/type <==
Battery
==> /sys/class/power_supply/BAT0/uevent <==
POWER_SUPPLY_VOLTAGE_NOW=13085000
POWER_SUPPLY_POWER_NOW=0
POWER_SUPPLY_ENERGY_FULL_DESIGN=39380000
POWER_SUPPLY_ENERGY_FULL=36700000
POWER_SUPPLY_ENERGY_NOW=36700000
POWER_SUPPLY_CAPACITY=100
POWER_SUPPLY_CAPACITY_LEVEL=Full
POWER_SUPPLY_MODEL_NAME=LNV-5B10W51861@
POWER_SUPPLY_MANUFACTURER=SMP
POWER_SUPPLY_SERIAL_NUMBER= 2220
==> /sys/class/power_supply/BAT0/voltage_min_design <==
11610000
==> /sys/class/power_supply/BAT0/voltage_now <==
13085000Last edited by pieterv (2023-12-13 18:32:53)
Offline
#8 2023-12-13 15:24:54
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,578
Re: [SOLVED] Screen goes suddenly to 1% brightness
Please don't fully quote previous posts, it just bloats the thread.
Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.
/sys/class/backlight/amdgpu_bl0/brightness […] stays constantly the same at the moment the effective brightness drops
Seems nothing that's exposed to the system then.
connect my second screen, go to display setting and turn off and on the main laptop screen
… at least not backlight-wise.
Make a script, bind that to some shortcut you can trigger when this happens.
#!/bin/bash
xrandr -q > ~/whatfucksupmydisplay
xset -q >> ~/whatfucksupmydisplay
# is it DPMS?
xset dpms force off; sleep 1; xset dpms force on
# determinable delay
sleep 10
# is it randr?
xrandr --output eDP --off # eDP is speculative!
xrandr --output eDP --auto # get the actual output name from "xrandr -q"
mpv /path/to/some/audible/ping.mp3and see whether any of the above revives the output, which and what ~/whatfucksupmydisplay reports.
(Don't forget to chmod +x the script)
Offline
#9 2023-12-20 08:48:18
- pieterv
- Member
- Registered: 2014-08-24
- Posts: 28
Re: [SOLVED] Screen goes suddenly to 1% brightness
Thanks, I have edited my messages accordingly.
In the mean time, I have been able to "catch" an issue using the script with shortcut you provided. This is the information written to the text file.
The screen comes back on with the first command "xset dpms force off; sleep 1; xset dpms force on"
Screen 0: minimum 320 x 200, current 3840 x 1200, maximum 16384 x 16384
eDP connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 302mm x 189mm
1920x1200 60.00*+ 50.00 48.02
1920x1080 60.00
1600x1200 60.00
1680x1050 60.00
1280x1024 60.00
1440x900 60.00
1280x800 60.00
1280x720 60.00
1024x768 60.00
800x600 60.00
640x480 60.00
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
DisplayPort-3 disconnected (normal left inverted right x axis y axis)
DisplayPort-4 disconnected (normal left inverted right x axis y axis)
DisplayPort-5 disconnected (normal left inverted right x axis y axis)
DVI-I-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 478mm x 260mm
1920x1080 60.00*+ 50.00 59.94
1600x900 60.00
1280x1024 75.02 60.02
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
800x600 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 60.00 59.94
720x400 70.08
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000002
XKB indicators:
00: Caps Lock: off 01: Num Lock: on 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 500 repeat rate: 33
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 2/1 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 0 cycle: 0
Colors:
default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
built-ins
DPMS (Display Power Management Signaling):
Standby: 0 Suspend: 0 Off: 0
DPMS is Enabled
Monitor is OnLast edited by pieterv (2023-12-20 08:48:46)
Offline
#10 2023-12-20 09:46:53
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,578
Re: [SOLVED] Screen goes suddenly to 1% brightness
The screen comes back on with the first command "xset dpms force off; sleep 1; xset dpms force on"
That's interesting because
DPMS (Display Power Management Signaling):
Standby: 0 Suspend: 0 Off: 0
DPMS is Enabled
Monitor is Ona) the DPMS extension is enabled
b) the DPMS timeouts are not (0/0/0 means "don't auto-activate") - neither is the screensaver
c) the monitor is considered "On"
So this is probably some session daemon (xscreensaver etc) triggering a DPMS and that somehow gets botched because of the invoked mode(?) and you therefore can't break it by wiggling the mouse.
Let's see whether there's a suspect (we just round up the entire village for inspection)
ps auxAs a workaround and if you don't care about DPMS, you can disable the extension
/etc/X11/xorg.conf.d/11-no_dpms.conf
Section "Extensions"
Option "DPMS" "Disable"
EndSectionor just keep a shortcut for "xset dpms force on"
Offline
#11 2023-12-20 10:07:09
- pieterv
- Member
- Registered: 2014-08-24
- Posts: 28
Re: [SOLVED] Screen goes suddenly to 1% brightness
Thanks for the reply seth. I'm grateful that you are taking the time to figure out this problem with me.
Just to be clear. Do you want the "ps aux", just after the issue happens, or right now?
I will now try first to disable DPMS. At this point, I don't really care about much, as long as my issue can be resolved.
Offline
#12 2023-12-20 10:45:41
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,578
Re: [SOLVED] Screen goes suddenly to 1% brightness
"right now" - it's more about "which daemon that looks like it will try to trigger DPMS" (screensaver, powermanagement) might screw this up.
Offline
#13 2023-12-20 11:12:14
- pieterv
- Member
- Registered: 2014-08-24
- Posts: 28
Re: [SOLVED] Screen goes suddenly to 1% brightness
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 22820 14804 ? Ss 07:30 0:01 /sbin/init
root 2 0.0 0.0 0 0 ? S 07:30 0:00 [kthreadd]
root 3 0.0 0.0 0 0 ? I< 07:30 0:00 [rcu_gp]
root 4 0.0 0.0 0 0 ? I< 07:30 0:00 [rcu_par_gp]
root 5 0.0 0.0 0 0 ? I< 07:30 0:00 [slub_flushwq]
root 6 0.0 0.0 0 0 ? I< 07:30 0:00 [netns]
root 8 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/0:0H-events_highpri]
root 10 0.0 0.0 0 0 ? I< 07:30 0:00 [mm_percpu_wq]
root 12 0.0 0.0 0 0 ? I 07:30 0:00 [rcu_tasks_kthread]
root 13 0.0 0.0 0 0 ? I 07:30 0:00 [rcu_tasks_rude_kthread]
root 14 0.0 0.0 0 0 ? I 07:30 0:00 [rcu_tasks_trace_kthread]
root 15 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/0]
root 16 0.0 0.0 0 0 ? I 07:30 0:08 [rcu_preempt]
root 17 0.0 0.0 0 0 ? S 07:30 0:00 [migration/0]
root 18 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/0]
root 20 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/0]
root 21 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/1]
root 22 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/1]
root 23 0.0 0.0 0 0 ? S 07:30 0:00 [migration/1]
root 24 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/1]
root 25 0.0 0.0 0 0 ? I 07:30 0:00 [kworker/1:0-mm_percpu_wq]
root 26 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/1:0H-events_highpri]
root 27 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/2]
root 28 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/2]
root 29 0.0 0.0 0 0 ? S 07:30 0:00 [migration/2]
root 30 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/2]
root 31 0.0 0.0 0 0 ? I 07:30 0:00 [kworker/2:0-events]
root 32 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/2:0H-events_highpri]
root 33 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/3]
root 34 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/3]
root 35 0.0 0.0 0 0 ? S 07:30 0:00 [migration/3]
root 36 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/3]
root 38 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/3:0H-events_highpri]
root 39 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/4]
root 40 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/4]
root 41 0.0 0.0 0 0 ? S 07:30 0:00 [migration/4]
root 42 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/4]
root 44 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/4:0H-events_highpri]
root 45 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/5]
root 46 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/5]
root 47 0.0 0.0 0 0 ? S 07:30 0:00 [migration/5]
root 48 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/5]
root 50 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/5:0H-events_highpri]
root 51 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/6]
root 52 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/6]
root 53 0.0 0.0 0 0 ? S 07:30 0:00 [migration/6]
root 54 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/6]
root 56 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/6:0H-events_highpri]
root 57 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/7]
root 58 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/7]
root 59 0.0 0.0 0 0 ? S 07:30 0:00 [migration/7]
root 60 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/7]
root 62 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/7:0H-events_highpri]
root 63 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/8]
root 64 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/8]
root 65 0.0 0.0 0 0 ? S 07:30 0:00 [migration/8]
root 66 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/8]
root 68 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/8:0H-events_highpri]
root 69 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/9]
root 70 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/9]
root 71 0.0 0.0 0 0 ? S 07:30 0:00 [migration/9]
root 72 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/9]
root 74 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/9:0H-events_highpri]
root 75 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/10]
root 76 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/10]
root 77 0.0 0.0 0 0 ? S 07:30 0:00 [migration/10]
root 78 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/10]
root 80 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/10:0H-events_highpri]
root 81 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/11]
root 82 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/11]
root 83 0.0 0.0 0 0 ? S 07:30 0:00 [migration/11]
root 84 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/11]
root 86 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/11:0H-events_highpri]
root 87 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/12]
root 88 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/12]
root 89 0.0 0.0 0 0 ? S 07:30 0:00 [migration/12]
root 90 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/12]
root 92 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/12:0H-events_highpri]
root 93 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/13]
root 94 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/13]
root 95 0.0 0.0 0 0 ? S 07:30 0:00 [migration/13]
root 96 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/13]
root 98 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/13:0H-events_highpri]
root 99 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/14]
root 100 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/14]
root 101 0.0 0.0 0 0 ? S 07:30 0:00 [migration/14]
root 102 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/14]
root 104 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/14:0H-events_highpri]
root 105 0.0 0.0 0 0 ? S 07:30 0:00 [cpuhp/15]
root 106 0.0 0.0 0 0 ? S 07:30 0:00 [idle_inject/15]
root 107 0.0 0.0 0 0 ? S 07:30 0:00 [migration/15]
root 108 0.0 0.0 0 0 ? S 07:30 0:00 [ksoftirqd/15]
root 110 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/15:0H-events_highpri]
root 111 0.0 0.0 0 0 ? S 07:30 0:00 [kdevtmpfs]
root 112 0.0 0.0 0 0 ? I< 07:30 0:00 [inet_frag_wq]
root 113 0.0 0.0 0 0 ? S 07:30 0:00 [kauditd]
root 114 0.0 0.0 0 0 ? S 07:30 0:00 [khungtaskd]
root 116 0.0 0.0 0 0 ? S 07:30 0:00 [oom_reaper]
root 117 0.0 0.0 0 0 ? I< 07:30 0:00 [writeback]
root 118 0.0 0.0 0 0 ? S 07:30 0:00 [kcompactd0]
root 119 0.0 0.0 0 0 ? SN 07:30 0:00 [ksmd]
root 120 0.0 0.0 0 0 ? I 07:30 0:00 [kworker/10:1-inet_frag_wq]
root 121 0.0 0.0 0 0 ? SN 07:30 0:00 [khugepaged]
root 122 0.0 0.0 0 0 ? I< 07:30 0:00 [kintegrityd]
root 123 0.0 0.0 0 0 ? I< 07:30 0:00 [kblockd]
root 124 0.0 0.0 0 0 ? I< 07:30 0:00 [blkcg_punt_bio]
root 127 0.0 0.0 0 0 ? I< 07:30 0:00 [tpm_dev_wq]
root 128 0.0 0.0 0 0 ? I< 07:30 0:00 [ata_sff]
root 131 0.0 0.0 0 0 ? I< 07:30 0:00 [edac-poller]
root 132 0.0 0.0 0 0 ? I< 07:30 0:00 [devfreq_wq]
root 133 0.0 0.0 0 0 ? S 07:30 0:00 [watchdogd]
root 134 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/8:1H-kblockd]
root 135 0.0 0.0 0 0 ? S 07:30 0:00 [irq/25-AMD-Vi]
root 136 0.0 0.0 0 0 ? S 07:30 0:00 [kswapd0]
root 142 0.0 0.0 0 0 ? I< 07:30 0:00 [kthrotld]
root 159 0.0 0.0 0 0 ? I< 07:30 0:00 [acpi_thermal_pm]
root 161 0.0 0.0 0 0 ? S 07:30 0:00 [hwrng]
root 162 0.0 0.0 0 0 ? I< 07:30 0:00 [amd_iommu_v2]
root 163 0.0 0.0 0 0 ? I< 07:30 0:00 [mld]
root 164 0.0 0.0 0 0 ? I< 07:30 0:00 [ipv6_addrconf]
root 169 0.0 0.0 0 0 ? I< 07:30 0:00 [kstrp]
root 173 0.0 0.0 0 0 ? I< 07:30 0:00 [zswap1]
root 174 0.0 0.0 0 0 ? I< 07:30 0:00 [zswap1]
root 175 0.0 0.0 0 0 ? I< 07:30 0:00 [zswap-shrink]
root 215 0.0 0.0 0 0 ? I< 07:30 0:00 [charger_manager]
root 216 0.0 0.0 0 0 ? S 07:30 0:00 [irq/26-ACPI:Event]
root 217 0.0 0.0 0 0 ? S 07:30 0:00 [irq/27-ACPI:Event]
root 218 0.0 0.0 0 0 ? S 07:30 0:00 [irq/28-ACPI:Event]
root 219 0.0 0.0 0 0 ? S 07:30 0:00 [irq/29-ACPI:Event]
root 220 0.0 0.0 0 0 ? S 07:30 0:00 [irq/30-ACPI:Event]
root 221 0.0 0.0 0 0 ? S 07:30 0:00 [irq/31-ACPI:Event]
root 222 0.0 0.0 0 0 ? S 07:30 0:00 [irq/32-ACPI:Event]
root 223 0.0 0.0 0 0 ? S 07:30 0:00 [irq/33-ACPI:Event]
root 240 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/10:1H-kblockd]
root 251 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/11:1H-kblockd]
root 267 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/3:1H-kblockd]
root 268 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/12:1H-kblockd]
root 269 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/7:1H-kblockd]
root 270 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/2:1H-kblockd]
root 271 0.0 0.0 0 0 ? I< 07:30 0:10 [kworker/5:1H-kblockd]
root 272 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/15:1H-kblockd]
root 273 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/4:1H-kblockd]
root 274 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/1:1H-kblockd]
root 275 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/6:1H-kblockd]
root 276 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/9:1H-kblockd]
root 278 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/0:1H-kblockd]
root 279 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/14:1H-kblockd]
root 280 0.0 0.0 0 0 ? I< 07:30 0:00 [kworker/13:1H-kblockd]
root 285 0.0 0.0 0 0 ? I< 07:30 0:00 [nvme-wq]
root 286 0.0 0.0 0 0 ? I< 07:30 0:00 [nvme-reset-wq]
root 287 0.0 0.0 0 0 ? I< 07:30 0:00 [nvme-delete-wq]
root 295 0.0 0.0 0 0 ? I< 07:30 0:00 [amdgpu-reset-de]
root 296 0.0 0.0 0 0 ? I< 07:30 0:00 [amdgpu_dm_hpd_r]
root 297 0.0 0.0 0 0 ? I< 07:30 0:00 [amdgpu_dm_hpd_r]
root 298 0.0 0.0 0 0 ? I< 07:30 0:00 [amdgpu_dm_hpd_r]
root 299 0.0 0.0 0 0 ? I< 07:30 0:00 [amdgpu_dm_hpd_r]
root 300 0.0 0.0 0 0 ? I< 07:30 0:00 [amdgpu_dm_hpd_r]
root 301 0.0 0.0 0 0 ? I< 07:30 0:00 [amdgpu_dm_hpd_r]
root 302 0.0 0.0 0 0 ? I< 07:30 0:00 [amdgpu_dm_hpd_r]
root 303 0.0 0.0 0 0 ? I< 07:30 0:00 [amdgpu_dm_hpd_r]
root 304 0.0 0.0 0 0 ? I< 07:30 0:00 [dm_vblank_contr]
root 305 0.0 0.0 0 0 ? I< 07:30 0:00 [amdgpu_dm_hpd_w]
root 306 0.0 0.0 0 0 ? S 07:30 0:00 [card0-crtc0]
root 307 0.0 0.0 0 0 ? S 07:30 0:00 [card0-crtc1]
root 308 0.0 0.0 0 0 ? S 07:30 0:00 [card0-crtc2]
root 309 0.0 0.0 0 0 ? S 07:30 0:00 [card0-crtc3]
root 310 0.2 0.0 0 0 ? S 07:30 0:36 [gfx_0.0.0]
root 311 0.0 0.0 0 0 ? S 07:30 0:00 [comp_1.0.0]
root 312 0.0 0.0 0 0 ? S 07:30 0:00 [comp_1.1.0]
root 313 0.0 0.0 0 0 ? S 07:30 0:00 [comp_1.2.0]
root 314 0.0 0.0 0 0 ? S 07:30 0:00 [comp_1.3.0]
root 315 0.0 0.0 0 0 ? S 07:30 0:00 [comp_1.0.1]
root 316 0.0 0.0 0 0 ? S 07:30 0:00 [comp_1.1.1]
root 317 0.0 0.0 0 0 ? S 07:30 0:00 [comp_1.2.1]
root 318 0.0 0.0 0 0 ? S 07:30 0:00 [comp_1.3.1]
root 319 0.0 0.0 0 0 ? S 07:30 0:00 [sdma0]
root 320 0.0 0.0 0 0 ? S 07:30 0:00 [vcn_dec_0]
root 321 0.0 0.0 0 0 ? S 07:30 0:00 [vcn_enc_0.0]
root 322 0.0 0.0 0 0 ? S 07:30 0:00 [vcn_enc_0.1]
root 323 0.0 0.0 0 0 ? S 07:30 0:00 [jpeg_dec]
root 357 0.0 0.0 0 0 ? S 07:30 0:01 [jbd2/nvme0n1p4-8]
root 358 0.0 0.0 0 0 ? I< 07:30 0:00 [ext4-rsv-conver]
root 398 0.0 0.0 67596 21580 ? Ss 07:30 0:00 /usr/lib/systemd/systemd-journald
root 403 0.0 0.0 0 0 ? I< 07:30 0:00 [iprt-VBoxWQueue]
root 404 0.0 0.0 0 0 ? S 07:30 0:00 [iprt-VBoxTscThread]
root 457 0.0 0.0 35800 11112 ? Ss 07:30 0:00 /usr/lib/systemd/systemd-udevd
root 469 0.0 0.0 0 0 ? S 07:30 0:00 [psimon]
root 543 0.0 0.0 0 0 ? S 07:30 0:00 [irq/68-SYNA8018:00]
root 718 0.0 0.0 0 0 ? I< 07:30 0:00 [cryptd]
root 724 0.0 0.0 0 0 ? I< 07:30 0:00 [ktpacpid]
root 747 0.0 0.0 0 0 ? I< 07:30 0:00 [cfg80211]
root 793 0.0 0.0 0 0 ? I< 07:30 0:00 [ath11k_wq]
root 794 0.0 0.0 0 0 ? I< 07:30 0:00 [ath11k_aux_wq]
root 795 0.0 0.0 0 0 ? S 07:30 0:00 [irq/76-bhi]
systemd+ 828 0.0 0.0 91620 9332 ? Ssl 07:30 0:00 /usr/lib/systemd/systemd-timesyncd
root 833 0.4 0.0 12848 6376 ? Ss 07:30 1:21 /usr/lib/bluetooth/bluetoothd
dbus 834 0.0 0.0 11244 6740 ? Ss 07:30 0:02 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root 835 0.0 0.0 18052 9280 ? Ss 07:30 0:00 /usr/lib/systemd/systemd-logind
root 859 0.0 0.0 415772 26672 ? Ssl 07:30 0:02 /usr/bin/NetworkManager --no-daemon
root 860 0.0 0.0 0 0 ? I< 07:30 0:02 [kworker/u33:3-hci0]
root 890 0.0 0.0 312392 9424 ? Ssl 07:31 0:00 /usr/bin/gdm
root 896 0.0 0.0 316692 15884 ? Ssl 07:31 0:00 /usr/lib/accounts-daemon
root 897 10.6 0.2 3575016 75300 ? Ssl 07:31 29:46 /usr/lib/displaylink/DisplayLinkManager
polkitd 927 0.0 0.0 384976 10756 ? Ssl 07:31 0:00 /usr/lib/polkit-1/polkitd --no-debug
root 928 0.0 0.0 0 0 ? S 07:31 0:01 [napi/-322]
root 929 0.0 0.0 0 0 ? S 07:31 0:00 [napi/-323]
root 930 0.0 0.0 0 0 ? S 07:31 0:00 [napi/-324]
root 931 0.0 0.0 0 0 ? S 07:31 0:00 [napi/-325]
root 932 0.0 0.0 0 0 ? S 07:31 0:00 [napi/-326]
root 933 0.0 0.0 0 0 ? S 07:31 0:00 [napi/-327]
root 934 0.0 0.0 0 0 ? S 07:31 0:00 [napi/-328]
root 935 0.0 0.0 0 0 ? S 07:31 0:02 [napi/-329]
root 936 0.0 0.0 0 0 ? S 07:31 0:00 [napi/-330]
root 937 0.0 0.0 0 0 ? S 07:31 0:00 [napi/-331]
root 938 0.0 0.0 0 0 ? S 07:31 0:01 [napi/-332]
root 992 0.0 0.0 18192 11304 ? Ss 07:31 0:00 /usr/bin/wpa_supplicant -u -s -O /run/wpa_supplicant
root 1014 0.0 0.0 0 0 ? S 07:31 0:00 [card1-crtc0]
colord 1122 0.0 0.0 318400 17616 ? Ssl 07:31 0:00 /usr/lib/colord
root 1158 0.0 0.0 317280 16424 ? Ssl 07:31 0:08 /usr/lib/upowerd
root 1263 0.0 0.0 28336 9904 ? Ss 07:31 0:00 /usr/bin/cupsd -l
root 1303 0.0 0.0 1110548 14536 ? Ssl 07:31 0:01 /usr/bin/pcscd --foreground --auto-exit
rtkit 1368 0.0 0.0 23068 3628 ? SNsl 07:31 0:00 /usr/lib/rtkit-daemon
root 1793 0.0 0.0 0 0 ? I< 09:13 0:02 [kworker/u33:1-hci0]
root 1825 0.0 0.0 389000 16188 ? Sl 09:13 0:00 gdm-session-worker [pam/gdm-password]
pieter 1836 0.0 0.0 21508 13140 ? Ss 09:13 0:00 /usr/lib/systemd/systemd --user
pieter 1837 0.0 0.0 23236 1728 ? S 09:13 0:00 (sd-pam)
pieter 1851 0.0 0.0 313064 14016 ? SLsl 09:13 0:00 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring
pieter 1864 0.0 0.0 10120 6184 ? Ss 09:13 0:02 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
pieter 1882 0.0 0.0 231972 7480 tty2 Ssl+ 09:13 0:00 /usr/lib/gdm-x-session --run-script /usr/bin/gnome-session
pieter 1884 3.6 0.6 1333680 207936 tty2 Sl+ 09:13 6:22 /usr/lib/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3
pieter 1944 0.0 0.0 372080 21180 tty2 Sl+ 09:13 0:00 /usr/lib/gnome-session-binary
pieter 1978 0.0 0.0 316700 13320 ? Ssl 09:13 0:00 /usr/lib/gvfsd
pieter 1987 0.0 0.0 455976 8376 ? Sl 09:13 0:00 /usr/lib/gvfsd-fuse /run/user/1000/gvfs -f
pieter 1999 0.0 0.0 381956 9480 ? Ssl 09:13 0:00 /usr/lib/at-spi-bus-launcher
pieter 2006 0.0 0.0 8660 4804 ? S 09:13 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/1000/at-spi/bus_0
pieter 2022 0.0 0.0 88020 6944 ? Ssl 09:13 0:00 /usr/lib/gnome-session-ctl --monitor
pieter 2026 0.0 0.0 594088 22828 ? Ssl 09:13 0:00 /usr/lib/gnome-session-binary --systemd-service --session=gnome
pieter 2053 5.1 1.0 5655864 340828 ? Rsl 09:13 9:09 /usr/bin/gnome-shell
pieter 2079 0.2 0.5 1386020 177424 ? Sl 09:13 0:23 /usr/lib/mutter-x11-frames
pieter 2093 0.0 0.0 235224 9916 ? Sl 09:13 0:01 /usr/lib/at-spi2-registryd --use-gnome-session
pieter 2119 0.0 0.0 661536 24536 ? Sl 09:13 0:00 /usr/lib/gnome-shell-calendar-server
pieter 2120 0.0 0.0 305584 6900 ? Ssl 09:13 0:00 /usr/lib/xdg-permission-store
pieter 2130 0.0 0.1 1417740 53372 ? Ssl 09:13 0:00 /usr/lib/evolution-source-registry
pieter 2139 0.0 0.0 2923624 28112 ? Sl 09:13 0:00 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.Shell.Notifications
pieter 2159 0.0 0.0 379776 10348 ? Ssl 09:13 0:00 /usr/lib/gsd-a11y-settings
pieter 2161 0.0 0.0 449720 28720 ? Ssl 09:13 0:00 /usr/lib/gsd-color
pieter 2163 0.0 0.0 429328 16352 ? Ssl 09:13 0:00 /usr/lib/gsd-datetime
pieter 2164 0.0 0.0 459976 11772 ? Ssl 09:13 0:00 /usr/lib/gsd-housekeeping
pieter 2165 0.0 0.0 448380 29484 ? Ssl 09:13 0:00 /usr/lib/gsd-keyboard
pieter 2166 0.0 0.1 1199800 33956 ? Ssl 09:13 0:00 /usr/lib/gsd-media-keys
pieter 2167 0.0 0.0 523300 29204 ? Ssl 09:13 0:00 /usr/lib/gsd-power
pieter 2169 0.0 0.0 321676 13032 ? Ssl 09:13 0:00 /usr/lib/gsd-print-notifications
pieter 2170 0.0 0.0 527376 10224 ? Ssl 09:13 0:00 /usr/lib/gsd-rfkill
pieter 2179 0.0 0.0 305832 8692 ? Ssl 09:13 0:00 /usr/lib/gsd-screensaver-proxy
pieter 2180 0.0 0.0 4292 1448 ? S 09:13 0:00 /opt/forticlient/fortitraylauncher
pieter 2182 0.0 0.0 531216 12408 ? Ssl 09:13 0:00 /usr/lib/gsd-sharing
pieter 2183 0.0 0.0 533572 16360 ? Ssl 09:13 0:03 /usr/lib/gsd-smartcard
pieter 2194 0.0 0.0 389328 10988 ? Ssl 09:13 0:00 /usr/lib/gsd-sound
pieter 2195 0.0 0.0 531152 9360 ? Ssl 09:13 0:00 /usr/lib/gsd-usb-protection
pieter 2196 0.0 0.2 1040056 68280 ? Sl 09:13 0:00 /usr/lib/evolution-data-server/evolution-alarm-notify
pieter 2199 0.0 0.0 449328 27792 ? Ssl 09:13 0:00 /usr/lib/gsd-wacom
pieter 2203 0.0 0.0 450216 31580 ? Ssl 09:13 0:00 /usr/lib/gsd-xsettings
pieter 2214 0.0 0.0 307088 6560 ? Sl 09:13 0:00 /usr/lib/gsd-disk-utility-notify
pieter 2234 0.0 0.7 1801480 241852 ? Sl 09:13 0:09 /usr/bin/gnome-software --gapplication-service
pieter 2242 0.1 0.9 2748776 291724 ? SLl 09:13 0:12 /usr/bin/nextcloud --background
root 2263 0.0 0.0 469348 17908 ? Ssl 09:13 0:00 /usr/lib/udisks2/udisksd
pieter 2305 0.0 0.0 452556 19628 ? Sl 09:13 0:00 /usr/lib/gsd-printer
pieter 2312 0.0 0.0 2923480 27700 ? Sl 09:13 0:00 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.ScreenSaver
pieter 2375 0.0 0.1 1865080 33308 ? S<sl 09:13 0:01 /usr/bin/pulseaudio --daemonize=no --log-target=journal
pieter 2381 0.0 0.1 805536 43048 ? Sl 09:13 0:00 /usr/lib/goa-daemon
pieter 2409 0.0 0.1 893264 31976 ? Ssl 09:13 0:00 /usr/lib/evolution-calendar-factory
pieter 2420 0.0 0.0 459156 10532 ? Sl 09:13 0:00 /usr/lib/goa-identity-service
pieter 2438 0.0 0.0 698596 20436 ? Ssl 09:13 0:00 /usr/lib/xdg-desktop-portal
pieter 2446 0.0 0.0 432660 16156 ? Ssl 09:13 0:00 /usr/lib/gvfs-udisks2-volume-monitor
pieter 2455 0.0 0.0 606784 11092 ? Ssl 09:13 0:00 /usr/lib/xdg-document-portal
pieter 2458 0.0 0.0 306584 8316 ? Ssl 09:13 0:00 /usr/lib/gvfs-mtp-volume-monitor
root 2466 0.0 0.0 2488 1012 ? Ss 09:13 0:00 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /run/user/1000/doc
pieter 2471 0.0 0.5 1440984 159028 ? Ssl 09:13 0:02 /usr/lib/xdg-desktop-portal-gnome
pieter 2483 0.0 0.0 308492 10608 ? Ssl 09:13 0:00 /usr/lib/gvfs-gphoto2-volume-monitor
pieter 2486 0.0 0.1 818812 32780 ? Ssl 09:13 0:00 /usr/lib/evolution-addressbook-factory
pieter 2504 0.0 0.0 305896 8092 ? Ssl 09:13 0:00 /usr/lib/gvfs-goa-volume-monitor
pieter 2515 0.0 0.0 386472 10708 ? Ssl 09:13 0:00 /usr/lib/gvfs-afc-volume-monitor
pieter 2563 0.0 0.0 193936 14848 ? S<sl 09:13 0:00 /usr/bin/pipewire
pieter 2571 0.0 0.0 485640 19520 ? S<sl 09:13 0:00 /usr/bin/wireplumber
pieter 2629 0.0 0.1 449544 34364 ? Ssl 09:13 0:00 /usr/lib/xdg-desktop-portal-gtk
pieter 2710 0.0 0.0 311752 9908 ? Sl 09:13 0:00 /usr/lib/pulse/gsettings-helper
root 2719 0.0 0.0 0 0 ? S< 09:13 0:00 [krfcommd]
avahi 2723 0.0 0.0 8776 4628 ? Ss 09:13 0:00 avahi-daemon: running [archt14.local]
pieter 2724 0.0 0.0 229232 5400 ? Ssl 09:13 0:00 /usr/lib/dconf-service
avahi 2725 0.0 0.0 8776 392 ? S 09:13 0:00 avahi-daemon: chroot helper
passim 2729 0.0 0.0 316580 9540 ? Ssl 09:13 0:00 /usr/lib/passimd
pieter 6325 0.0 0.0 233528 8844 ? Ssl 09:14 0:00 /usr/lib/gvfsd-metadata
pieter 6430 0.0 0.0 613680 18164 ? Sl 09:15 0:07 /usr/lib/gvfsd-trash --spawner :1.5 /org/gtk/gvfs/exec_spaw/0
pieter 6458 0.0 0.1 805824 33052 ? SNsl 09:15 0:00 /usr/lib/tracker-miner-fs-3
pieter 6489 0.0 0.0 392176 13188 ? Sl 09:15 0:00 /usr/lib/gvfsd-recent --spawner :1.5 /org/gtk/gvfs/exec_spaw/1
pieter 9488 0.0 0.0 464728 11924 ? Sl 09:24 0:00 /usr/lib/gvfsd-network --spawner :1.5 /org/gtk/gvfs/exec_spaw/2
pieter 9506 0.0 0.0 393280 12160 ? Sl 09:24 0:00 /usr/lib/gvfsd-dnssd --spawner :1.5 /org/gtk/gvfs/exec_spaw/4
pieter 10244 0.0 0.0 323600 12412 ? Sl 09:27 0:00 /usr/lib/gvfsd-http --spawner :1.5 /org/gtk/gvfs/exec_spaw/5
root 11637 0.0 0.0 0 0 ? I 09:29 0:00 [kworker/9:2-events]
cups 13271 0.0 0.0 16548 4980 ? S 09:31 0:00 /usr/lib/cups/notifier/dbus dbus://
root 13681 0.0 0.0 0 0 ? I 09:37 0:00 [kworker/11:1-events]
root 13818 0.0 0.0 0 0 ? I 09:37 0:00 [kworker/14:1-rcu_gp]
root 13834 0.0 0.0 0 0 ? I 09:37 0:00 [kworker/9:0-events]
root 13837 0.0 0.0 0 0 ? I 09:37 0:00 [kworker/0:2-events]
root 17121 0.0 0.0 0 0 ? I 09:52 0:00 [kworker/3:0-events]
root 18059 0.0 0.0 0 0 ? S 09:52 0:00 [psimon]
root 47184 0.0 0.0 0 0 ? I 10:13 0:00 [kworker/7:0-events]
root 51990 0.0 0.0 0 0 ? I 10:30 0:00 [kworker/13:0-events]
root 52006 0.0 0.0 0 0 ? I 10:30 0:00 [kworker/8:0-events]
root 57362 0.1 0.0 0 0 ? I 10:49 0:06 [kworker/u32:0-events_power_efficient]
root 57375 0.0 0.0 0 0 ? I 10:49 0:00 [kworker/5:2-inet_frag_wq]
root 58487 0.0 0.0 0 0 ? I 11:03 0:00 [kworker/15:1-pm]
root 58510 0.0 0.0 0 0 ? I 11:03 0:00 [kworker/13:2-events]
root 59711 0.0 0.0 0 0 ? I 11:08 0:00 [kworker/3:1-events]
root 62478 0.1 0.0 0 0 ? I 11:19 0:05 [kworker/u32:1-events_power_efficient]
root 62986 0.0 0.0 0 0 ? I 11:30 0:00 [kworker/6:1-events]
root 62987 0.0 0.0 0 0 ? I 11:30 0:00 [kworker/1:2-inet_frag_wq]
pieter 63217 0.1 0.7 2539816 240120 ? Sl 11:31 0:04 /usr/bin/nautilus --gapplication-service
root 63509 0.0 0.0 0 0 ? I 11:32 0:00 [kworker/2:2-events]
root 64317 0.0 0.0 0 0 ? I 11:44 0:00 [kworker/7:1-events]
root 64345 0.0 0.0 0 0 ? I 11:45 0:00 [kworker/12:2-events]
root 64409 0.0 0.0 0 0 ? I 11:45 0:00 [kworker/4:2-events]
root 64466 0.0 0.0 0 0 ? I 11:45 0:00 [kworker/8:1-inet_frag_wq]
root 66589 0.0 0.0 0 0 ? I 11:47 0:00 [kworker/0:0-events]
root 66863 0.2 0.0 0 0 ? I 11:54 0:01 [kworker/u32:2-events_unbound]
root 67044 0.0 0.0 0 0 ? I 11:59 0:00 [kworker/6:2-inet_frag_wq]
root 67048 0.0 0.0 0 0 ? I 11:59 0:00 [kworker/12:0-events]
root 67123 0.0 0.0 0 0 ? I 12:00 0:00 [kworker/4:0-events]
root 67124 0.1 0.0 0 0 ? I 12:00 0:00 [kworker/u32:3-events_unbound]
root 67281 0.0 0.0 0 0 ? I 12:03 0:00 [kworker/10:0-events]
root 67430 0.0 0.0 0 0 ? I 12:03 0:00 [kworker/5:1-events]
root 67449 0.0 0.0 0 0 ? I 12:03 0:00 [kworker/14:2-events]
root 67506 0.0 0.0 0 0 ? I 12:04 0:00 [kworker/15:0-mm_percpu_wq]
root 67508 0.0 0.0 0 0 ? I 12:04 0:00 [kworker/11:0-cgroup_destroy]
root 67572 0.0 0.0 0 0 ? I 12:05 0:00 [kworker/7:2-events]
root 67573 0.0 0.0 0 0 ? I 12:05 0:00 [kworker/6:0-events]
root 67800 0.0 0.0 0 0 ? I 12:05 0:00 [kworker/13:1-mm_percpu_wq]
root 68036 0.0 0.0 0 0 ? I 12:07 0:00 [kworker/u32:4-flush-259:0]
root 68037 0.0 0.0 0 0 ? I 12:07 0:00 [kworker/u32:5]
root 68100 0.0 0.0 0 0 ? I 12:08 0:00 [kworker/0:1-events]
root 68101 0.0 0.0 0 0 ? I 12:08 0:00 [kworker/8:2-events]
root 68121 0.0 0.0 0 0 ? I 12:08 0:00 [kworker/12:1-events]
root 68124 0.0 0.0 0 0 ? I 12:08 0:00 [kworker/10:2-events]
pieter 69639 5.4 0.6 2104476 218808 ? Sl 12:09 0:02 /usr/bin/kgx --gapplication-service
pieter 69662 0.0 0.0 7784 4556 pts/0 Ss 12:09 0:00 /bin/bash
root 69685 0.0 0.0 9912 4308 pts/0 S 12:09 0:00 su
root 69686 0.0 0.0 7784 4764 pts/0 S 12:09 0:00 bash
root 69692 0.0 0.0 0 0 ? I 12:09 0:00 [kworker/3:2-events]
root 69708 0.0 0.0 0 0 ? I 12:09 0:00 [kworker/5:0-mm_percpu_wq]
root 69709 0.0 0.0 0 0 ? I 12:09 0:00 [kworker/1:1-events]
root 69732 0.0 0.0 0 0 ? I 12:09 0:00 [kworker/11:2]
root 69757 0.0 0.0 11136 4696 pts/0 R+ 12:09 0:00 ps auxOffline
#14 2023-12-20 11:19:48
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,578
Re: [SOLVED] Screen goes suddenly to 1% brightness
upowerd, gdm (likely wayland?) and gsd-screensaver-proxy
My money is on GDM, if it runs on wayland and triggers its own DPMS bypassing the X11 server (or even just runs on a differen DISPLAY, as is common for GDM) you might end up w/ a situation where output and session X11 server disagree on the DPMS state.
Also you've experienced this w/ different sessions, right?
Try https://wiki.archlinux.org/title/GDM#Use_Xorg_backend or just to https://wiki.archlinux.org/title/GNOME#Xorg_sessions (and the last link before, the excerpt in the wiki would result in a degraded session, it's only the gnome relevant tail of an xinitrc)
Sidebar, most likely unrelated, but you seem to run pipewire and pulseaudio concurrently.
https://archlinux.org/packages/extra/x8 … ire-pulse/
Offline
#15 2023-12-24 18:52:15
- pieterv
- Member
- Registered: 2014-08-24
- Posts: 28
Re: [SOLVED] Screen goes suddenly to 1% brightness
Seth, I have first tried the above mentioned /etc/X11/xorg.conf.d/11-no_dpms.conf, but the issue happened again. Here's the "/whatfucksupmydisplay" output:
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 16384
eDP connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 302mm x 189mm
1920x1200 60.00*+ 50.00 48.02
1920x1080 60.00
1600x1200 60.00
1680x1050 60.00
1280x1024 60.00
1440x900 60.00
1280x800 60.00
1280x720 60.00
1024x768 60.00
800x600 60.00
640x480 60.00
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 disconnected (normal left inverted right x axis y axis)
DisplayPort-2 disconnected (normal left inverted right x axis y axis)
DisplayPort-3 disconnected (normal left inverted right x axis y axis)
DisplayPort-4 disconnected (normal left inverted right x axis y axis)
DisplayPort-5 disconnected (normal left inverted right x axis y axis)
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000002
XKB indicators:
00: Caps Lock: off 01: Num Lock: on 02: Scroll Lock: off
03: Compose: off 04: Kana: off 05: Sleep: off
06: Suspend: off 07: Mute: off 08: Misc: off
09: Mail: off 10: Charging: off 11: Shift Lock: off
12: Group 2: off 13: Mouse Keys: off
auto repeat delay: 500 repeat rate: 33
auto repeating keys: 00ffffffdffffbbf
fadfffefffedffff
9fffffffffffffff
fff7ffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 2/1 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 0 cycle: 0
Colors:
default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
built-ins
DPMS (Display Power Management Signaling):
Server does not have the DPMS ExtensionI will now proceed to try the other suggestions in your last post.
Thanks for your mentioning of pipewire and pulseaudio.
Offline
#16 2023-12-24 20:11:36
- seth
- Member
- Registered: 2012-09-03
- Posts: 51,578
Re: [SOLVED] Screen goes suddenly to 1% brightness
Fwwi, there was an amdgpu specific backlight bug in 6.6.7 that might have overlapped with your tests, make sure you're not using that kernel
Offline
#17 2024-01-26 07:45:17
- pieterv
- Member
- Registered: 2014-08-24
- Posts: 28
Re: [SOLVED] Screen goes suddenly to 1% brightness
After about one month, the issue has not appeared anymore. I'm slowly getting confident the issue has been solved.
How it's solved, is not clear yet to me. Either it's because of the "Option "DPMS" "Disable"" in my xorg.conf, or it was the bug in kernel 6.6.7. I have now turned DPMS back on and will see if the issue returns.
Seth, I would like to thank you for taking the time looking at my issue!
Offline