Not seeing anything blindingly obvious, I have to admit.
Some(all?) of the /dev/i2c* entries are not writeable, but then again so are half of mine and I don’t know how one would check if they have been created with the correct permissions as one would have to assume that they have been set up appropriately depending on whether they are writeable i2c devices and should be written to.
Can we assume that this used to work some kernels ago? If so you could try booting one of those earlier kernels and checking the /dev/i2c* entries against what you get from this specific kernel?
I’m also on F43 KDE with recent updates, and I don’t have this problem.
Your log has various “errors” that also appear in mine so presumably aren’t fatal. The bit that stands out that I don’t have is this:
Feb 22 08:13:12 org_kde_powerdevil[2837]: The Wayland connection broke. Did the Wayland compositor die?
Feb 22 08:13:12 org_kde_powerdevil[2837]: Attempting wayland reconnect
Feb 22 08:13:12 org_kde_powerdevil[2837]: Failed to write to the pipe: Bad file descriptor.
Feb 22 08:13:12 org_kde_powerdevil[2837]: There are no outputs - creating placeholder screen
Feb 22 08:13:12 org_kde_powerdevil[2837]: X connection to :0 broken (explicit kill or server shutdown).
Feb 22 08:13:12 org_kde_powerdevil[2837]: QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread
Feb 22 08:13:12 org_kde_powerdevil[2837]: QtDBus: cannot relay signals from parent QObject(0x55ce88a009c0 "") unless they are emitted in the object's thread QThread(0x55ce88986ab0 "Qt mainThread"). Current thread is QThread(0x55ce88a34ec0 "").
Feb 22 08:13:12 org_kde_powerdevil[2837]: [ 2997] Watch thread terminated.
Feb 22 08:13:12 systemd[2035]: plasma-powerdevil.service: Consumed 43.024s CPU time, 13.4M memory peak
If you look at entries just before that time in the full journal (i.e. without grep power), is there anything suggestive?
There is a lot of I2C permission related errors. AFAIK those might be related to DDC/CI (controlling brightness of external monitor).
Maybe try something like this: Lexruee's Blog
The following appears just before the section of the log you pointed out. This is obviously not the whole list but it shows "kwin_wayland crashing
I’ll back up to a previous kernel and see if that changes anything.
Feb 22 08:12:53 flatpak[2202]: 2026-02-22 08:12:53 INF Synced file (folder.label=Tbird folder.id=svx54-wtbfd folder.type=sendreceive file.name=qukficff.default-release/cookies.sqlite file.modified="2026-02-22 08:12:40.398365577 -0800 PST" file.permissions=0644 file.size=1048576 file.blocksize=131072 blocks.local=5 blocks.download=3 log.pkg=model)
Feb 22 08:13:11 kwin_wayland_wrapper[2465]: KCrash: Application 'kwin_wayland' crashing... crashRecursionCounter = 2
Feb 22 08:13:11 audit[2465]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=2465 comm="kwin_wayland" exe="/usr/bin/kwin_wayland" sig=11 res=1
Feb 22 08:13:11 systemd-coredump[12604]: Process 2465 (kwin_wayland) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Feb 22 08:13:11 audit: BPF prog-id=114 op=LOAD
Feb 22 08:13:11 audit: BPF prog-id=115 op=LOAD
Feb 22 08:13:11 audit: BPF prog-id=116 op=LOAD
Feb 22 08:13:11 systemd[1]: Started systemd-coredump@1-16385-12604_12605-0.service - Process Core Dump (PID 12604/UID 0).
Feb 22 08:13:11 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-16385-12604_12605-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 22 08:13:11 audit: BPF prog-id=117 op=LOAD
Feb 22 08:13:11 audit: BPF prog-id=118 op=LOAD
Feb 22 08:13:11 audit: BPF prog-id=119 op=LOAD
Feb 22 08:13:11 systemd[1]: Started drkonqi-coredump-processor@1-16385-12604_12605-0.service - Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Feb 22 08:13:11 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=drkonqi-coredump-processor@1-16385-12604_12605-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 22 08:13:12 abrt-dump-journal-core[1497]: Failed to obtain all required information from journald
Feb 22 08:13:12 systemd-coredump[12605]: Process 2465 (kwin_wayland) of user 1000 dumped core.
Module /usr/bin/kwin_wayland from rpm kwin-6.6.0-1.fc43.x86_64
Module libqsvg.so from rpm qt6-qtsvg-6.10.1-1.fc43.x86_64
Module libSPIRV-Tools-opt.so from rpm spirv-tools-2026.1-2.fc43.x86_64
Module libQt6ShaderTools.so.6 from rpm qt6-qtshadertools-6.10.1-1.fc43.x86_6
Note that I edited your post and converted your ... lines before and after the text to ``` so it is displayed as preformatted text. Note the scroll bar that now exists so the reader can parse along the long lines and it is easy to tell line by line what is displayed.
In the future please do that so your pasted text is formatted as seen on-screen and is much easier to read and parse.
How embarrassing.
I’ve rebooted several times in the process of trying to identify the issue. Since trying an older kernel and then rebooting to use the newest one,…both the “Power Management” menu works as well as all the Autostart items. I’ve reboot 3 times and all appears to be well.
Sorry for the noise and thank you to those who responded.
Do not be sorry, feedback is important. It is not noise, it just really shows the all over situation , everything is shaking
We are getting close to a beta release … alpha testing for beta
