redshift-gtk crash

[John Doe]

Here are the systemd logs

● redshift-gtk.service - Redshift display colour temperature adjustment (GUI)
     Loaded: loaded (/usr/lib/systemd/user/redshift-gtk.service; enabled; vendor preset: enabled)
     Active: failed (Result: core-dump) since Wed 2021-05-05 13:48:06 CEST; 1h 55min ago
       Docs: http://jonls.dk/redshift/
   Main PID: 1800 (code=dumped, signal=SEGV)
        CPU: 100ms

mai 05 13:48:06 black systemd[1412]: redshift-gtk.service: Main process exited, code=dumped, status=11/SEGV
mai 05 13:48:06 black systemd[1412]: redshift-gtk.service: Failed with result 'core-dump'.
mai 05 13:48:06 black systemd[1412]: redshift-gtk.service: Scheduled restart job, restart counter is at 5.
mai 05 13:48:06 black systemd[1412]: Stopped Redshift display colour temperature adjustment (GUI).
mai 05 13:48:06 black systemd[1412]: redshift-gtk.service: Start request repeated too quickly.
mai 05 13:48:06 black systemd[1412]: redshift-gtk.service: Failed with result 'core-dump'.
mai 05 13:48:06 black systemd[1412]: Failed to start Redshift display colour temperature adjustment (GUI).

Here is the coredump backtrace

#0 0x00007f6e58f91690 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#1 0x00007f6e58e322c4 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#2 0x00007f6e58e53ad8 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#3 0x00007f6e58e3e21a in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#4 0x00007f6e58e539a8 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#5 0x00007f6e58e3eb62 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#6 0x00007f6e5ac99357 in g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7 0x00007f6e5ac7f615 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8 0x00007f6e5ac80b1d in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9 0x00007f6e5ac815f1 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007f6e58e5c47b in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#11 0x00007f6e59045819 in () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#12 0x00007f6e5ac99357 in g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x00007f6e5ac7f615 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x00007f6e5ac80b1d in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x00007f6e5ae2ce84 in () at /usr/lib/python3/dist-packages/gi/_gi.cpython-39-x86_64-linux-gnu.so
#16 0x00007f6e5ae4ad4f in () at /usr/lib/python3/dist-packages/gi/_gi.cpython-39-x86_64-linux-gnu.so
#17 0x000000000051d6f5 in _PyObject_MakeTpCall ()
#18 0x00000000005175ba in _PyEval_EvalFrameDefault ()
#19 0x0000000000528b63 in _PyFunction_Vectorcall ()
#20 0x0000000000537b80 in ()
#21 0x000000000051d6f5 in _PyObject_MakeTpCall ()
#22 0x00000000005170e4 in _PyEval_EvalFrameDefault ()
#23 0x0000000000510fe7 in ()
#24 0x0000000000528d21 in _PyFunction_Vectorcall ()
#25 0x0000000000511fb5 in _PyEval_EvalFrameDefault ()
#26 0x00000000005106ed in ()
#27 0x0000000000510497 in _PyEval_EvalCodeWithName ()
#28 0x00000000005f5be3 in PyEval_EvalCode ()
#29 0x0000000000619de7 in ()
#30 0x0000000000615610 in ()
#31 0x0000000000619d79 in ()
#32 0x0000000000619816 in PyRun_SimpleFileExFlags ()
#33 0x000000000060d4e3 in Py_RunMain ()
#34 0x00000000005ea6e9 in Py_BytesMain ()
#35 0x00007f6e5b542d0a in __libc_start_main (main=0x5ea6b0, argc=2, argv=0x7fff17c021a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff17c02198) at ../csu/libc-start.c:308
#36 0x00000000005ea5ea in _start ()

[John Doe (rba777)]

Explanation and possible solution here => https://github.com/jonls/redshift/issues/265

In a few words, that happens on systems which are not using systemd graphical-session.target (e.g. XFCE, OpenBox, etc.) so you have to disable redshift-gtk.service and start it manually in one of the autostart scripts.

That said, there could be a small delay defined in systemd service file in order to avoid a frenzy restart of redshift-gtk.service