search

baduhai / Koi

Koi - Theme scheduling for the KDE Plasma Desktop
GNU Lesser General Public License v3.0
263 stars 19 forks source link

[BUG] Doesn't switch theme after waking from sleep/hibernate. #11

Open baduhai opened 4 years ago

baduhai commented 4 years ago

Describe the bug If the computer was sleeping/hibernating during the time it had to switch themes, when it wakes Koi doesn't switch themes.

To Reproduce

  1. Put computer to sleep/hibernate before the time to switch theme.
  2. Let time go past when the theme should switch.
  3. Wake the computer.
  4. See that themes don't change.

Expected behavior Themes should change after the computer is waken.

Desktop (please complete the following information):

baduhai commented 4 years ago

Possible solution: nativeEvent. Awfully intrusive solution: writing a trivial driver to detect sleep changes. Will probably work, but it's insanely intrusive for such a simple task.

Wtark02 commented 1 year ago

have another problem, use sunset/sunrise to change the theme.

If sun set or rise when PC has sleeping, nothing changed, or (if sun sets AND rise) change to wrong theme.

By the way, on my laptop is work OK, but it always poweroff, not sleep/hibernate.

Arch Linux, Koi 0.2.3

Wtark02 commented 1 year ago

I found a solution: systemd unit that restart koi after suspend:

[Unit]
Description=Restart koi after suspend
After=suspend.target
After=hibernate.target
After=hybrid-sleep.target
After=syslog.target
After=multi-user.target

[Service]
Type=simple
ExecStart=/usr/bin/koi
ExecReload=/bin/kill -HUP $MAINPID
Restart=always

[Install]
WantedBy=suspend.target
WantedBy=hibernate.target
WantedBy=hybrid-sleep.target
WantedBy=multi-user.target
WantedBy=syslog.target

It may not be the most ingenious solution, but it works

major-mayer commented 6 months ago

Unfortunately, this workaround isn't valid for me. First I was wondering where to put this systemd unit file. Since it's regarding a GUI application, I thought placing it it in~/.config/systemd/user/ and starting it as a user service should be appropriate. But then i realized that this is not an option, since the suspend-, hibernate-, etc. targets are not available for user unit files, only "default.target" (reference).

So I moved the file to /etc/systemd/system/ and enabled it using systemctl start koi.service (I named my unit file "koi.service"). I also removed the "syslog" target, because it doesn't seem to be available. It was successfully enabled (and started) but showed no effect on suspend.

I found the following logs: 

Apr 25 16:34:27 laurenz-ManjaroKDE systemd[1]: Started Restart koi after suspend.
░░ Subject: A start job for unit koi.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit koi.service has finished successfully.
░░ 
░░ The job identifier is 13001.
Apr 25 16:34:27 laurenz-ManjaroKDE koi[188194]: qt.qpa.xcb: could not connect to display
Apr 25 16:34:27 laurenz-ManjaroKDE koi[188194]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Apr 25 16:34:27 laurenz-ManjaroKDE koi[188194]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

                                                Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Apr 25 16:34:27 laurenz-ManjaroKDE systemd[1]: koi.service: Main process exited, code=dumped, status=6/ABRT
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ An ExecStart= process belonging to unit koi.service has exited.
░░ 
░░ The process' exit code is 'dumped' and its exit status is 6.
Apr 25 16:34:27 laurenz-ManjaroKDE systemd[1]: koi.service: Failed with result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ The unit koi.service has entered the 'failed' state with result 'core-dump'.
Apr 25 16:34:28 laurenz-ManjaroKDE systemd[1]: koi.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ Automatic restarting of the unit koi.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.

Seems like when you add this as system unit file, it tries to start Koi as root, which I think can be problematic. But even when I add User=laurenz, it doesn't work and throws the same error message. Somehow, it can't connect to the display.

@Wtark02 Can you explain a bit more in depth how you installed and activated this unit file?

Edit: I think in general, it would be much more convenient if this could be implemented in Koi itself, especially if QT provides suitable event handlers. Most of the users probably don't know how to create and activate a unit file.

Voultapher commented 6 months ago

Having the same problem on Arch as well.

Voultapher commented 6 months ago

Would be awesome if it can be fixed, as it is it makes automatic switching useless to me, and I'm better of manually switching.

MartinVonReichenberg commented 4 months ago

Would be awesome if it can be fixed, as it is it makes automatic switching useless to me, and I'm better of manually switching.

Could you check it again and test it with the latest version of Koi if the problem still occurs ??

major-mayer commented 4 months ago

I can test it, as soon as the AUR package is updated.

MartinVonReichenberg commented 4 months ago

I can test it, as soon as the AUR package is updated.

DONE, Check AUR. Thanks!

Voultapher commented 4 months ago

Same here, was waiting for AUR, will try to test the next days. Thanks for fixing.

Voultapher commented 4 months ago

Initial test with manually set light- and dark-mode times looks good. I will keep an eye on it and report issues here should they crop up. Thanks for the fix.

MartinVonReichenberg commented 4 months ago

@Voultapher

Most likely a former incompatibility with operating system internals.

Another thing which should help on this matter is using DBus interface, but for that, a separate *.XML file would needed to be created and integrated into build process along with with DBusActivatable=true instead of false inside the Koi.DESKTOP file.

Any "improvements" welcomed . . .

Voultapher commented 4 months ago

Not sure it's related, if not I can create a separate bug ticket, this morning the theme didn't switch after waking it up from sleep, tracing it back I saw it wasn't running anymore, and I found this error log in the autostart dialog: image

major-mayer commented 4 months ago

I'm not able to find those Koi errors in the journal logs, but interestingly enough, this morning the automatic theme switch after standby also didn't work for me.

MartinVonReichenberg commented 4 months ago

Not sure it's related, if not I can create a separate bug ticket, this morning the theme didn't switch after waking it up from sleep, tracing it back I saw it wasn't running anymore, and I found this error log in the autostart dialog: image

Not sure if I can reference this, but will try it out on four Linux distributions and will let you know later . . .

major-mayer commented 4 months ago

In my case I am using Manjaro Linux KDE Edition if that's helping.

MartinVonReichenberg commented 4 months ago

In my case I am using Manjaro Linux KDE Edition if that's helping.

In my quad-boot, I have Manjaro installed too, but with X-ForCE . . .

Voultapher commented 4 months ago

I'm on Arch + KDE

MartinVonReichenberg commented 4 months ago

Still nothing ?_?

Voultapher commented 4 months ago

It's a mixed bag, I'd say most days I wake my machine from sleep, based on the time it should be in light mode but it's in dark mode. I'm not sure but it may happen more often when the transition to dark mode should have happened while the machine was asleep. So it goes from light mode -> sleep -> dark mode, but it should go light mode -> sleep -> light mode. Over the last couple days koi was running without issues after wakeup, so that can't explain it.

major-mayer commented 4 months ago

At least when setting the schedule manually to time a few minutes away, the dark theme is correctly applied. I have to observe it for a longer time to be able to say if it's completely fixed in a real-world scenario.

major-mayer commented 4 months ago

I think I found a way to crash Koi and maybe also to reproduce the automatic theme switching not working.

Assuming that it's now 13:30 and i've set the schedule like this: grafik I would guess that the theme should be light atm, then switch to dark at 13:40 and back to light at 13:50. Actually Koi sets the current theme to dark, when applying those settings, so I've manually set the theme to light.

Then I put my PC to standby and wake it up after 13:50. The result is that the dark theme is active and Koi crashed with the following backtrace:

           PID: 65756 (koi)
           UID: 1000 (laurenz)
           GID: 1000 (laurenz)
        Signal: 6 (ABRT)
     Timestamp: Fri 2024-06-28 14:52:56 CEST (45s ago)
  Command Line: /usr/bin/koi
    Executable: /usr/bin/koi
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-koi@autostart.service
          Unit: user@1000.service
     User Unit: app-koi@autostart.service
         Slice: user-1000.slice
     Owner UID: 1000 (laurenz)
       Boot ID: f167bc9e813445529ace415695928ecd
    Machine ID: e012fd79f36849318967b28a1dd79047
      Hostname: laurenz-ManjaroKDE
       Storage: /var/lib/systemd/coredump/core.koi.1000.f167bc9e813445529ace415695928ecd.65756.1719579176000000.zst (present)
  Size on Disk: 3.0M
       Message: Process 65756 (koi) of user 1000 dumped core.

                Stack trace of thread 65766:
                #0  0x00007f24634a8e44 n/a (libc.so.6 + 0x94e44)
                #1  0x00007f2463450a30 raise (libc.so.6 + 0x3ca30)
                #2  0x00007f24634384c3 abort (libc.so.6 + 0x244c3)
                #3  0x00007f2463439354 n/a (libc.so.6 + 0x25354)
                #4  0x00007f24634b3085 n/a (libc.so.6 + 0x9f085)
                #5  0x00007f24634b5240 n/a (libc.so.6 + 0xa1240)
                #6  0x00007f24634b554a n/a (libc.so.6 + 0xa154a)
                #7  0x00007f24634b7dae __libc_free (libc.so.6 + 0xa3dae)
                #8  0x00007f246313cddd n/a (libQt6Core.so.6 + 0x33cddd)
                #9  0x00007f246313ce89 _ZNK9QSettings5valueE14QAnyStringView (libQt6Core.so.6 + 0x33ce89)
                #10 0x0000555aa3147fdb n/a (koi + 0x2cfdb)
                #11 0x0000555aa314dcce n/a (koi + 0x32cce)
                #12 0x0000555aa313a7d9 n/a (koi + 0x1f7d9)
                #13 0x0000555aa313accd n/a (koi + 0x1fccd)
                #14 0x00007f24634ac34b n/a (libc.so.6 + 0x9834b)
                #15 0x00007f24634ac3c9 pthread_once (libc.so.6 + 0x983c9)
                #16 0x0000555aa313b2d1 n/a (koi + 0x202d1)
                #17 0x0000555aa313ab8a n/a (koi + 0x1fb8a)
                #18 0x0000555aa3143299 n/a (koi + 0x28299)
                #19 0x00007f2462ae0c84 execute_native_thread_routine (libstdc++.so.6 + 0xe0c84)
                #20 0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #21 0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65771:
                #0  0x00007f246351c39d __poll (libc.so.6 + 0x10839d)
                #1  0x00007f245d374277 n/a (libQt6WaylandClient.so.6 + 0x60277)
                #2  0x00007f24630c96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
                #3  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #4  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65932:
                #0  0x00007f24634a34e9 n/a (libc.so.6 + 0x8f4e9)
                #1  0x00007f24634a6242 pthread_cond_timedwait (libc.so.6 + 0x92242)
                #2  0x00007f24630ce058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2ce058)
                #3  0x00007f24630c7d52 n/a (libQt6Core.so.6 + 0x2c7d52)
                #4  0x00007f24630c96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
                #5  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #6  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65774:
                #0  0x00007f24634a34e9 n/a (libc.so.6 + 0x8f4e9)
                #1  0x00007f24634a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
                #2  0x00007f244de975ae n/a (radeonsi_dri.so + 0x975ae)
                #3  0x00007f244de7535c n/a (radeonsi_dri.so + 0x7535c)
                #4  0x00007f244de974dd n/a (radeonsi_dri.so + 0x974dd)
                #5  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #6  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65770:
                #0  0x00007f246351c39d __poll (libc.so.6 + 0x10839d)
                #1  0x00007f245d374277 n/a (libQt6WaylandClient.so.6 + 0x60277)
                #2  0x00007f24630c96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
                #3  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #4  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65768:
                #0  0x00007f246351c39d __poll (libc.so.6 + 0x10839d)
                #1  0x00007f24622328fd n/a (libglib-2.0.so.0 + 0xbe8fd)
                #2  0x00007f24621cff95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
                #3  0x00007f24631a28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
                #4  0x00007f2462f4f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
                #5  0x00007f246303a4e0 _ZN7QThread4execEv (libQt6Core.so.6 + 0x23a4e0)
                #6  0x00007f2464975dfe n/a (libQt6DBus.so.6 + 0x2ddfe)
                #7  0x00007f24630c96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
                #8  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #9  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65930:
                #0  0x00007f24634a34e9 n/a (libc.so.6 + 0x8f4e9)
                #1  0x00007f24634a6242 pthread_cond_timedwait (libc.so.6 + 0x92242)
                #2  0x00007f24630ce058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2ce058)
                #3  0x00007f24630c7d52 n/a (libQt6Core.so.6 + 0x2c7d52)
                #4  0x00007f24630c96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
                #5  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #6  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65765:
                #0  0x00007f24634a34e9 n/a (libc.so.6 + 0x8f4e9)
                #1  0x00007f24634a6242 pthread_cond_timedwait (libc.so.6 + 0x92242)
                #2  0x0000555aa3139e9c n/a (koi + 0x1ee9c)
                #3  0x0000555aa31474b0 n/a (koi + 0x2c4b0)
                #4  0x0000555aa313accd n/a (koi + 0x1fccd)
                #5  0x00007f24634ac34b n/a (libc.so.6 + 0x9834b)
                #6  0x00007f24634ac3c9 pthread_once (libc.so.6 + 0x983c9)
                #7  0x0000555aa313b6d1 n/a (koi + 0x206d1)
                #8  0x0000555aa313a46a n/a (koi + 0x1f46a)
                #9  0x0000555aa3143299 n/a (koi + 0x28299)
                #10 0x00007f2462ae0c84 execute_native_thread_routine (libstdc++.so.6 + 0xe0c84)
                #11 0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #12 0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65775:
                #0  0x00007f24634a34e9 n/a (libc.so.6 + 0x8f4e9)
                #1  0x00007f24634a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
                #2  0x00007f244de975ae n/a (radeonsi_dri.so + 0x975ae)
                #3  0x00007f244de7535c n/a (radeonsi_dri.so + 0x7535c)
                #4  0x00007f244de974dd n/a (radeonsi_dri.so + 0x974dd)
                #5  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #6  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 66036:
                #0  0x00007f24634a34e9 n/a (libc.so.6 + 0x8f4e9)
                #1  0x00007f24634a6242 pthread_cond_timedwait (libc.so.6 + 0x92242)
                #2  0x00007f24630ce058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2ce058)
                #3  0x00007f24630c7d52 n/a (libQt6Core.so.6 + 0x2c7d52)
                #4  0x00007f24630c96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
                #5  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #6  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65931:
                #0  0x00007f24634a34e9 n/a (libc.so.6 + 0x8f4e9)
                #1  0x00007f24634a6242 pthread_cond_timedwait (libc.so.6 + 0x92242)
                #2  0x00007f24630ce058 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x2ce058)
                #3  0x00007f24630c7d52 n/a (libQt6Core.so.6 + 0x2c7d52)
                #4  0x00007f24630c96e7 n/a (libQt6Core.so.6 + 0x2c96e7)
                #5  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #6  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65772:
                #0  0x00007f24634a34e9 n/a (libc.so.6 + 0x8f4e9)
                #1  0x00007f24634a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
                #2  0x00007f244de975ae n/a (radeonsi_dri.so + 0x975ae)
                #3  0x00007f244de7535c n/a (radeonsi_dri.so + 0x7535c)
                #4  0x00007f244de974dd n/a (radeonsi_dri.so + 0x974dd)
                #5  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #6  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65767:
                #0  0x00007f2463529ed6 __clone (libc.so.6 + 0x115ed6)
                #1  0x00007f24631290c3 n/a (libQt6Core.so.6 + 0x3290c3)
                #2  0x0000555aa3130879 n/a (koi + 0x15879)
                #3  0x0000555aa3147e48 n/a (koi + 0x2ce48)
                #4  0x0000555aa314d87e n/a (koi + 0x3287e)
                #5  0x0000555aa313a7d9 n/a (koi + 0x1f7d9)
                #6  0x0000555aa313accd n/a (koi + 0x1fccd)
                #7  0x00007f24634ac34b n/a (libc.so.6 + 0x9834b)
                #8  0x00007f24634ac3c9 pthread_once (libc.so.6 + 0x983c9)
                #9  0x0000555aa313b2d1 n/a (koi + 0x202d1)
                #10 0x0000555aa313ab8a n/a (koi + 0x1fb8a)
                #11 0x0000555aa3143299 n/a (koi + 0x28299)
                #12 0x00007f2462ae0c84 execute_native_thread_routine (libstdc++.so.6 + 0xe0c84)
                #13 0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #14 0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65773:
                #0  0x00007f24634a34e9 n/a (libc.so.6 + 0x8f4e9)
                #1  0x00007f24634a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
                #2  0x00007f244de975ae n/a (radeonsi_dri.so + 0x975ae)
                #3  0x00007f244de7535c n/a (radeonsi_dri.so + 0x7535c)
                #4  0x00007f244de974dd n/a (radeonsi_dri.so + 0x974dd)
                #5  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #6  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65777:
                #0  0x00007f24634a34e9 n/a (libc.so.6 + 0x8f4e9)
                #1  0x00007f24634a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
                #2  0x00007f244de975ae n/a (radeonsi_dri.so + 0x975ae)
                #3  0x00007f244de7535c n/a (radeonsi_dri.so + 0x7535c)
                #4  0x00007f244de974dd n/a (radeonsi_dri.so + 0x974dd)
                #5  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #6  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65776:
                #0  0x00007f24634a34e9 n/a (libc.so.6 + 0x8f4e9)
                #1  0x00007f24634a5ed9 pthread_cond_wait (libc.so.6 + 0x91ed9)
                #2  0x00007f244de975ae n/a (radeonsi_dri.so + 0x975ae)
                #3  0x00007f244de7535c n/a (radeonsi_dri.so + 0x7535c)
                #4  0x00007f244de974dd n/a (radeonsi_dri.so + 0x974dd)
                #5  0x00007f24634a6ded n/a (libc.so.6 + 0x92ded)
                #6  0x00007f246352a0dc n/a (libc.so.6 + 0x1160dc)

                Stack trace of thread 65756:
                #0  0x00007f246351c39d __poll (libc.so.6 + 0x10839d)
                #1  0x00007f24622328fd n/a (libglib-2.0.so.0 + 0xbe8fd)
                #2  0x00007f24621cff95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95)
                #3  0x00007f24631a28dd _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3a28dd)
                #4  0x00007f2462f4f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e)
                #5  0x00007f2462f4945d _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x14945d)
                #6  0x0000555aa312c8cc n/a (koi + 0x118cc)
                #7  0x00007f2463439c88 n/a (libc.so.6 + 0x25c88)
                #8  0x00007f2463439d4c __libc_start_main (libc.so.6 + 0x25d4c)
                #9  0x0000555aa312ca05 n/a (koi + 0x11a05)
                ELF object binary architecture: AMD x86-64
MartinVonReichenberg commented 4 months ago

Cannot really help on this . . .

Voultapher commented 4 months ago

@baduhai can you repro?

BinaryInk commented 4 months ago

I've been watching this thread, thinking I had little to contribute despite having the problem myself...but, unfortunately, I just observed this problem occurring without S3 suspend:

1.) Koi successfully changed from Light to Dark at specified time -- I observed it. 2.) I was actively using my computer throughout the night and did not sleep, hibernate, etc. 3.) An hour or two after it was supposed to change to light, I noticed the themes had not changed.

So...I'm not saying that there isn't a problem with S3 sleep and Koi...but, there either is a separate issue with the same symptom, or the issue everyone here is experiencing may not be related to sleep at all. I can open up a separate issue if needed.

I have got the journalctl output below. I'm not sure if that's what you're looking for, however; the data on its face seems to be useless in this regard... Let me know if there's anything else I can provide.

journalctl output (computer name removed, time in UTC).

 > journalctl -u app-koi@autostart --user -b
Jun 29 05:20:32 systemd[1879]: Starting Koi...
Jun 29 05:20:32 systemd[1879]: Started Koi.
Jun 29 05:20:32 koi[2496]: QSocketNotifier: Can only be used with threads started with QThread
Jun 29 05:20:34 plasma-changeicons[3531]: org.kde.plasma.changeicons: Icon theme is already used
Jun 29 05:20:34 krunner[3534]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Jun 29 05:20:34 krunner[3534]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Jun 29 05:20:34 krunner[3534]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Jun 29 05:20:34 krunner[3534]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Jun 29 05:57:18 krunner[3534]: The cached device pixel ratio value was stale on window expose.  Please file a QTBUG which explains how to reproduce.
Jun 29 06:57:28 krunner[3534]: The cached device pixel ratio value was stale on window expose.  Please file a QTBUG which explains how to reproduce.
Jun 29 08:24:02 krunner[3534]: The cached device pixel ratio value was stale on window expose.  Please file a QTBUG which explains how to reproduce.
Jun 29 10:41:18 plasma-changeicons[17984]: org.kde.plasma.changeicons: Icon theme is already used
Jun 29 10:41:18 krunner[3534]: qrc:/krunner/RunCommand.qml:309: TypeError: Cannot read property 'pinned' of null
Jun 29 10:41:18 krunner[3534]: qrc:/krunner/RunCommand.qml:295: TypeError: Cannot read property 'helpEnabled' of null
Jun 29 10:41:18 krunner[3534]: QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread
Jun 29 10:41:18 krunner[17986]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Jun 29 10:41:18 krunner[17986]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Jun 29 10:41:18 krunner[17986]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Jun 29 10:41:18 krunner[17986]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Jun 29 21:09:06 krunner[17986]: The cached device pixel ratio value was stale on window expose.  Please file a QTBUG which explains how to reproduce.
Jun 30 01:40:57 plasma-changeicons[57786]: org.kde.plasma.changeicons: Icon theme is already used
Jun 30 01:40:57 krunner[17986]: qrc:/krunner/RunCommand.qml:309: TypeError: Cannot read property 'pinned' of null
Jun 30 01:40:57 krunner[17986]: qrc:/krunner/RunCommand.qml:305: TypeError: Cannot read property 'helpEnabled' of null
Jun 30 01:40:57 krunner[57787]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Jun 30 01:40:57 krunner[57787]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Jun 30 01:40:57 krunner[57787]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Jun 30 01:40:57 krunner[57787]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Jun 30 10:56:20 krunner[57787]: The cached device pixel ratio value was stale on window expose.  Please file a QTBUG which explains how to reproduce.
Jun 30 10:56:20 krunner[57787]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Jun 30 10:56:20 krunner[57787]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Jun 30 12:35:35 plasma-changeicons[92549]: org.kde.plasma.changeicons: Icon theme is already used
Jun 30 12:35:35 krunner[57787]: qrc:/krunner/RunCommand.qml:309: TypeError: Cannot read property 'pinned' of null
Jun 30 12:35:35 krunner[57787]: qrc:/krunner/RunCommand.qml:295: TypeError: Cannot read property 'helpEnabled' of null
Jun 30 12:35:35 krunner[57787]: QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread
Jun 30 12:35:35 krunner[92550]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Jun 30 12:35:35 krunner[92550]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Jun 30 12:35:35 krunner[92550]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairRequested(QString)
Jun 30 12:35:35 krunner[92550]: qt.core.qobject.connect: QObject::connect: No such signal Solid::Backends::Fstab::FstabStorageAccess::repairDone(Solid::ErrorType, QVariant, QString)
Jun 30 12:38:23 krunner[92550]: The cached device pixel ratio value was stale on window expose.  Please file a QTBUG which explains how to reproduce.

Manjaro 24.0.2 Linux 6.9.3-3-MANJARO KDE Plasma 6.0.5 Koi 0.3 Uptime: 1d 7h (EDIT: not suspended between working state and failure...I can't say for certain I never suspended in this whole period of time)

MartinVonReichenberg commented 4 months ago

For me it works - 50:50 . . .

MartinVonReichenberg commented 3 months ago

@baduhai can you repro?

He obviously cannot . . . 🤭

Voultapher commented 3 months ago

I guess I'm missing some context here.On 18. Jul 2024, at 11:05, Martin von Reichenberg @.***> wrote:

@baduhai can you repro?

He obviously cannot . . . 🤭

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

MartinVonReichenberg commented 1 week ago

I shall try it out again ...