You are not logged in.

Pages: 1

#1 2023-02-15 17:04:23

maboleth
Member
Registered: 2020-01-03
Posts: 230

[SOLVED] Redshift not firing after logoff/on

I have set Redshift to start with Systemd.

[Unit]
Description=Redshift display colour temperature adjustment (GUI)
Documentation=http://jonls.dk/redshift/
After=display-manager.service

[Service]
ExecStart=/usr/bin/redshift-gtk
Restart=always

[Install]
WantedBy=default.target

And it works. Except when Languages menu is clicked during logging on (LightDM for Xfce4).

If Languages is just clicked, without changing anything, after logging on Redshift won't start. Message in journal is:

The job identifier is 2220 and the job result is done.
Feb 15 17:42:34 ivan-desktop systemd[611]: redshift-gtk.service: Start request repeated too quickly.
Feb 15 17:42:34 ivan-desktop systemd[611]: redshift-gtk.service: Failed with result 'core-dump'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit UNIT has entered the 'failed' state with result 'core-dump'.
Feb 15 17:42:34 ivan-desktop systemd[611]: Failed to start Redshift display colour temperature adjustment (GUI).
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has finished with a failure.
░░ 
░░ The job identifier is 2220 and the job result is failed.

Last edited by maboleth (2023-02-16 09:28:54)

Offline

#2 2023-02-15 17:25:18

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,096

Re: [SOLVED] Redshift not firing after logoff/on

Feb 15 17:42:34 ivan-desktop systemd[611]: redshift-gtk.service: Failed with result 'core-dump'.

https://wiki.archlinux.org/title/Core_d … _core_dump

Also please post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Never use "-x" w/ journalctl, it's just spam.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2023-02-15 17:47:31

maboleth
Member
Registered: 2020-01-03
Posts: 230

Re: [SOLVED] Redshift not firing after logoff/on

seth wrote:
Feb 15 17:42:34 ivan-desktop systemd[611]: redshift-gtk.service: Failed with result 'core-dump'.

https://wiki.archlinux.org/title/Core_d … _core_dump

Also please post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Never use "-x" w/ journalctl, it's just spam.

Here it is, I hope it's ok.

        PID: 23604 (redshift-gtk)
           UID: 1000 (ivan)
           GID: 1000 (ivan)
        Signal: 11 (SEGV)
     Timestamp: Wed 2023-02-15 18:57:23 CET (3min 50s ago)
  Command Line: python3 /usr/bin/redshift-gtk
    Executable: /usr/bin/python3.10
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/redshift-gtk.service
          Unit: user@1000.service
     User Unit: redshift-gtk.service
         Slice: user-1000.slice
     Owner UID: 1000 (ivan)
       Boot ID: 1ff76dfd0b7d489db73e1c894f7f478d
    Machine ID: d6382c652c1f46518bb934abdc912ac9
      Hostname: ivan-desktop
       Storage: /var/lib/systemd/coredump/core.redshift-gtk.1000.1ff76dfd0b7d489db73e1c894f7f478d.23604.1676483>
  Size on Disk: 2.2M
       Message: Process 23604 (redshift-gtk) of user 1000 dumped core.
                
                Stack trace of thread 23604:
                #0  0x00007f41b3513f14 n/a (libgtk-3.so.0 + 0x113f14)
                #1  0x00007f41b3534526 n/a (libgtk-3.so.0 + 0x134526)
                #2  0x00007f41b351e5a5 n/a (libgtk-3.so.0 + 0x11e5a5)
                #3  0x00007f41b504976b g_type_create_instance (libgobject-2.0.so.0 + 0x3d76b)
                #4  0x00007f41b5030571 n/a (libgobject-2.0.so.0 + 0x24571)
                #5  0x00007f41b5031dd0 g_object_new_with_properties (libgobject-2.0.so.0 + 0x25dd0)
                #6  0x00007f41b5032bca g_object_new (libgobject-2.0.so.0 + 0x26bca)
                #7  0x00007f41b3732ffc n/a (libgtk-3.so.0 + 0x332ffc)
                #8  0x00007f41b504976b g_type_create_instance (libgobject-2.0.so.0 + 0x3d76b)
                #9  0x00007f41b5030571 n/a (libgobject-2.0.so.0 + 0x24571)
                #10 0x00007f41b5031dd0 g_object_new_with_properties (libgobject-2.0.so.0 + 0x25dd0)
                #11 0x00007f41b51bfa34 n/a (_gi.cpython-310-x86_64-linux-gnu.so + 0x13a34)
                #12 0x00007f41b5f4f4c3 _PyObject_MakeTpCall (libpython3.10.so.1.0 + 0x14f4c3)
                #13 0x00007f41b5f4a8ee _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x14a8ee)
                #14 0x00007f41b5f4e7cb _PyObject_FastCallDictTstate (libpython3.10.so.1.0 + 0x14e7cb)
                #15 0x00007f41b5f5e3cd n/a (libpython3.10.so.1.0 + 0x15e3cd)
                #16 0x00007f41b5f4f4c3 _PyObject_MakeTpCall (libpython3.10.so.1.0 + 0x14f4c3)
                #17 0x00007f41b5f4a2e4 _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x14a2e4)
                #18 0x00007f41b5f562d9 _PyFunction_Vectorcall (libpython3.10.so.1.0 + 0x1562d9)
                #19 0x00007f41b5f454d6 _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x1454d6)
                #20 0x00007f41b5f44120 n/a (libpython3.10.so.1.0 + 0x144120)
                #21 0x00007f41b5ff1b94 PyEval_EvalCode (libpython3.10.so.1.0 + 0x1f1b94)
                #22 0x00007f41b6002323 n/a (libpython3.10.so.1.0 + 0x202323)
                #23 0x00007f41b5ffda8a n/a (libpython3.10.so.1.0 + 0x1fda8a)
                #24 0x00007f41b5ea1979 n/a (libpython3.10.so.1.0 + 0xa1979)
                #25 0x00007f41b5ea162a _PyRun_SimpleFileObject (libpython3.10.so.1.0 + 0xa162a)
                #26 0x00007f41b5ea1fdd _PyRun_AnyFileObject (libpython3.10.so.1.0 + 0xa1fdd)
                #27 0x00007f41b600eb0d Py_RunMain (libpython3.10.so.1.0 + 0x20eb0d)
                #28 0x00007f41b5fe336b Py_BytesMain (libpython3.10.so.1.0 + 0x1e336b)
                #29 0x00007f41b5c3c790 n/a (libc.so.6 + 0x23790)
                #30 0x00007f41b5c3c84a __libc_start_main (libc.so.6 + 0x2384a)
                #31 0x00005568b8447045 _start (python3.10 + 0x1045)
                
                Stack trace of thread 23609:
                #0  0x00007f41b5d190dd syscall (libc.so.6 + 0x1000dd)
                #1  0x00007f41b51133e3 g_cond_wait_until (libglib-2.0.so.0 + 0xa63e3)
                #2  0x00007f41b5090893 n/a (libglib-2.0.so.0 + 0x23893)
                #3  0x00007f41b50f567b n/a (libglib-2.0.so.0 + 0x8867b)
                #4  0x00007f41b50efdb5 n/a (libglib-2.0.so.0 + 0x82db5)
                #5  0x00007f41b5c9ebb5 n/a (libc.so.6 + 0x85bb5)
                #6  0x00007f41b5d20d90 n/a (libc.so.6 + 0x107d90)
                
                Stack trace of thread 23610:
                #0  0x00007f41b5d139df __poll (libc.so.6 + 0xfa9df)
                #1  0x00007f41b5119c2f n/a (libglib-2.0.so.0 + 0xacc2f)
                #2  0x00007f41b50c1d8f g_main_loop_run (libglib-2.0.so.0 + 0x54d8f)
                #3  0x00007f41b4eadaec n/a (libgio-2.0.so.0 + 0x10aaec)
                #4  0x00007f41b50efdb5 n/a (libglib-2.0.so.0 + 0x82db5)
                #5  0x00007f41b5c9ebb5 n/a (libc.so.6 + 0x85bb5)
                #6  0x00007f41b5d20d90 n/a (libc.so.6 + 0x107d90)
                
                Stack trace of thread 23608:
                #0  0x00007f41b5d190dd syscall (libc.so.6 + 0x1000dd)
                #1  0x00007f41b51133e3 g_cond_wait_until (libglib-2.0.so.0 + 0xa63e3)
                #2  0x00007f41b5090893 n/a (libglib-2.0.so.0 + 0x23893)
                #3  0x00007f41b50f567b n/a (libglib-2.0.so.0 + 0x8867b)
                #4  0x00007f41b50efdb5 n/a (libglib-2.0.so.0 + 0x82db5)
                #5  0x00007f41b5c9ebb5 n/a (libc.so.6 + 0x85bb5)
                #6  0x00007f41b5d20d90 n/a (libc.so.6 + 0x107d90)
                
                Stack trace of thread 23607:
                #0  0x00007f41b5d139df __poll (libc.so.6 + 0xfa9df)
                #1  0x00007f41b5119c2f n/a (libglib-2.0.so.0 + 0xacc2f)
                #2  0x00007f41b50c10e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2)
                #3  0x00007f41b50c1132 n/a (libglib-2.0.so.0 + 0x54132)
                #4  0x00007f41b50efdb5 n/a (libglib-2.0.so.0 + 0x82db5)
                #5  0x00007f41b5c9ebb5 n/a (libc.so.6 + 0x85bb5)
                #6  0x00007f41b5d20d90 n/a (libc.so.6 + 0x107d90)
                ELF object binary architecture: AMD x86-64

http://0x0.st/HrYk.txt

Last edited by maboleth (2023-02-15 18:02:13)

Offline

#4 2023-02-15 18:05:54

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,096

Re: [SOLVED] Redshift not firing after logoff/on

Feb 15 17:34:00 ivan-desktop redshift-gtk[618]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Feb 15 17:34:00 ivan-desktop redshift-gtk[618]: /usr/lib/python3.10/site-packages/redshift_gtk/statusicon.py:58: Warning: invalid (NULL) pointer instance
Feb 15 17:34:00 ivan-desktop redshift-gtk[618]:   self.indicator = appindicator.Indicator.new(
Feb 15 17:34:00 ivan-desktop redshift-gtk[618]: /usr/lib/python3.10/site-packages/redshift_gtk/statusicon.py:58: Warning: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Feb 15 17:34:00 ivan-desktop redshift-gtk[618]:   self.indicator = appindicator.Indicator.new(
Feb 15 17:34:00 ivan-desktop redshift-gtk[618]: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
Feb 15 17:34:00 ivan-desktop redshift-gtk[618]: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
Feb 15 17:34:00 ivan-desktop audit[618]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=618 comm="redshift-gtk" exe="/usr/bin/python3.10" sig=11 res=1
Feb 15 17:34:00 ivan-desktop redshift-gtk[618]: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
…
Feb 15 17:34:00 ivan-desktop systemd-coredump[642]: Process 618 (redshift-gtk) of user 1000 dumped core.
                                                    
                                                    Stack trace of thread 618:
                                                    #0  0x00007f79fd513f14 n/a (libgtk-3.so.0 + 0x113f14)
                                                    #1  0x00007f79fd534526 n/a (libgtk-3.so.0 + 0x134526)
                                                    #2  0x00007f79fd51e5a5 n/a (libgtk-3.so.0 + 0x11e5a5)
                                                    #3  0x00007f79ff04976b g_type_create_instance (libgobject-2.0.so.0 + 0x3d76b)
                                                    #4  0x00007f79ff030571 n/a (libgobject-2.0.so.0 + 0x24571)
                                                    #5  0x00007f79ff031dd0 g_object_new_with_properties (libgobject-2.0.so.0 + 0x25dd0)
                                                    #6  0x00007f79ff032bca g_object_new (libgobject-2.0.so.0 + 0x26bca)
                                                    #7  0x00007f79fd732ffc n/a (libgtk-3.so.0 + 0x332ffc)
                                                    #8  0x00007f79ff04976b g_type_create_instance (libgobject-2.0.so.0 + 0x3d76b)
                                                    #9  0x00007f79ff030571 n/a (libgobject-2.0.so.0 + 0x24571)
                                                    #10 0x00007f79ff031dd0 g_object_new_with_properties (libgobject-2.0.so.0 + 0x25dd0)
                                                    #11 0x00007f79ff1bfa34 n/a (_gi.cpython-310-x86_64-linux-gnu.so + 0x13a34)
                                                    #12 0x00007f79fff4f4c3 _PyObject_MakeTpCall (libpython3.10.so.1.0 + 0x14f4c3)
                                                    #13 0x00007f79fff4a8ee _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x14a8ee)
                                                    #14 0x00007f79fff4e7cb _PyObject_FastCallDictTstate (libpython3.10.so.1.0 + 0x14e7cb)
                                                    #15 0x00007f79fff5e3cd n/a (libpython3.10.so.1.0 + 0x15e3cd)
                                                    #16 0x00007f79fff4f4c3 _PyObject_MakeTpCall (libpython3.10.so.1.0 + 0x14f4c3)
                                                    #17 0x00007f79fff4a2e4 _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x14a2e4)
                                                    #18 0x00007f79fff562d9 _PyFunction_Vectorcall (libpython3.10.so.1.0 + 0x1562d9)
                                                    #19 0x00007f79fff454d6 _PyEval_EvalFrameDefault (libpython3.10.so.1.0 + 0x1454d6)
                                                    #20 0x00007f79fff44120 n/a (libpython3.10.so.1.0 + 0x144120)
                                                    #21 0x00007f79ffff1b94 PyEval_EvalCode (libpython3.10.so.1.0 + 0x1f1b94)
                                                    #22 0x00007f7a00002323 n/a (libpython3.10.so.1.0 + 0x202323)
                                                    #23 0x00007f79ffffda8a n/a (libpython3.10.so.1.0 + 0x1fda8a)
                                                    #24 0x00007f79ffea1979 n/a (libpython3.10.so.1.0 + 0xa1979)
                                                    #25 0x00007f79ffea162a _PyRun_SimpleFileObject (libpython3.10.so.1.0 + 0xa162a)
                                                    #26 0x00007f79ffea1fdd _PyRun_AnyFileObject (libpython3.10.so.1.0 + 0xa1fdd)
                                                    #27 0x00007f7a0000eb0d Py_RunMain (libpython3.10.so.1.0 + 0x20eb0d)
                                                    #28 0x00007f79fffe336b Py_BytesMain (libpython3.10.so.1.0 + 0x1e336b)
                                                    #29 0x00007f79ffc3c790 n/a (libc.so.6 + 0x23790)
                                                    #30 0x00007f79ffc3c84a __libc_start_main (libc.so.6 + 0x2384a)
                                                    #31 0x000055c5d2793045 _start (python3.10 + 0x1045)
                                                    
                                                    Stack trace of thread 636:
                                                    #0  0x00007f79ffd139df __poll (libc.so.6 + 0xfa9df)
                                                    #1  0x00007f79ff119c2f n/a (libglib-2.0.so.0 + 0xacc2f)
                                                    #2  0x00007f79ff0c10e2 g_main_context_iteration (libglib-2.0.so.0 + 0x540e2)
                                                    #3  0x00007f79ff0c1132 n/a (libglib-2.0.so.0 + 0x54132)
                                                    #4  0x00007f79ff0efdb5 n/a (libglib-2.0.so.0 + 0x82db5)
                                                    #5  0x00007f79ffc9ebb5 n/a (libc.so.6 + 0x85bb5)
                                                    #6  0x00007f79ffd20d90 n/a (libc.so.6 + 0x107d90)
                                                    
                                                    Stack trace of thread 638:
                                                    #0  0x00007f79ffd190dd syscall (libc.so.6 + 0x1000dd)
                                                    #1  0x00007f79ff1133e3 g_cond_wait_until (libglib-2.0.so.0 + 0xa63e3)
                                                    #2  0x00007f79ff090893 n/a (libglib-2.0.so.0 + 0x23893)
                                                    #3  0x00007f79ff0f567b n/a (libglib-2.0.so.0 + 0x8867b)
                                                    #4  0x00007f79ff0efdb5 n/a (libglib-2.0.so.0 + 0x82db5)
                                                    #5  0x00007f79ffc9ebb5 n/a (libc.so.6 + 0x85bb5)
                                                    #6  0x00007f79ffd20d90 n/a (libc.so.6 + 0x107d90)
                                                    
                                                    Stack trace of thread 640:
                                                    #0  0x00007f79ffd139df __poll (libc.so.6 + 0xfa9df)
                                                    #1  0x00007f79ff119c2f n/a (libglib-2.0.so.0 + 0xacc2f)
                                                    #2  0x00007f79ff0c1d8f g_main_loop_run (libglib-2.0.so.0 + 0x54d8f)
                                                    #3  0x00007f79feeadaec n/a (libgio-2.0.so.0 + 0x10aaec)
                                                    #4  0x00007f79ff0efdb5 n/a (libglib-2.0.so.0 + 0x82db5)
                                                    #5  0x00007f79ffc9ebb5 n/a (libc.so.6 + 0x85bb5)
                                                    #6  0x00007f79ffd20d90 n/a (libc.so.6 + 0x107d90)
                                                    
                                                    Stack trace of thread 639:
                                                    #0  0x00007f79ffd190dd syscall (libc.so.6 + 0x1000dd)
                                                    #1  0x00007f79ff1133e3 g_cond_wait_until (libglib-2.0.so.0 + 0xa63e3)
                                                    #2  0x00007f79ff090893 n/a (libglib-2.0.so.0 + 0x23893)
                                                    #3  0x00007f79ff0f567b n/a (libglib-2.0.so.0 + 0x8867b)
                                                    #4  0x00007f79ff0efdb5 n/a (libglib-2.0.so.0 + 0x82db5)
                                                    #5  0x00007f79ffc9ebb5 n/a (libc.so.6 + 0x85bb5)
                                                    #6  0x00007f79ffd20d90 n/a (libc.so.6 + 0x107d90)
                                                    ELF object binary architecture: AMD x86-64

It's not redshift, but the systray icon (redshift-gtk specific)

Feb 15 17:34:00 ivan-desktop lightdm[606]: pam_unix(lightdm-autologin:session): session opened for user ivan(uid=1000) by (uid=0)

Can you please elaborate on

Except when Languages menu is clicked during logging on (LightDM for Xfce4).

This seems to be an autologin?

Try

ExecStart=/usr/bin/sleep 2; /usr/bin/redshift-gtk

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2023-02-15 18:16:14

maboleth
Member
Registered: 2020-01-03
Posts: 230

Re: [SOLVED] Redshift not firing after logoff/on

seth wrote:

It's not redshift, but the systray icon (redshift-gtk specific)

Yeah, I'm firing redshift-gtk alone. It's either one or the other.


seth wrote:

Can you please elaborate on Except when Languages menu is clicked during logging on (LightDM for Xfce4).
This seems to be an autologin?

Yes. There's autologin, but sometimes I need to logout. I have noticed under certain occasions Redshift icon/warmer light just isn't there.  After some troubleshooting I noticed it was happening when menu items in LightDM were interacted with before entering password. Language in this case.

If there is just logging off/on with just entering the password, Redshift-gtk will work.


seth wrote:

Try

ExecStart=/usr/bin/sleep 2; /usr/bin/redshift-gtk

it says "Bash: 2: command not found" but then it makes a second redshift-gtk icon with warmer light going on and off repeatedly.
If there was no Redshift-GTK before it just starts and remains (I have removed "2" from your ExecStart as I think that was a mistake)

Last edited by maboleth (2023-02-15 18:19:38)

Offline

#6 2023-02-15 18:17:41

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,096

Re: [SOLVED] Redshift not firing after logoff/on

ExecStartPre=/usr/bin/sleep 2
ExecStart=/usr/bin/redshift-gtk

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2023-02-15 18:20:38

maboleth
Member
Registered: 2020-01-03
Posts: 230

Re: [SOLVED] Redshift not firing after logoff/on

ExecStartPre=/usr/bin/sleep 2

doesn't work. Says bash: 2: command not found


ExecStart=/usr/bin/sleep2; /usr/bin/redshift-gtk

works though and it makes redshift-gtk appear and flash on and off.

What exactly are we trying to test?

Last edited by maboleth (2023-02-15 18:55:49)

Offline

#8 2023-02-15 21:23:07

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,096

Re: [SOLVED] Redshift not firing after logoff/on

Says bash: 2: command not found

Post your actual service file.

ExecStart=/usr/bin/sleep2; /usr/bin/redshift-gtk

I severely doubt that there's a "/usr/bin/sleep2" binary on your system.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2023-02-15 21:40:00

maboleth
Member
Registered: 2020-01-03
Posts: 230

Re: [SOLVED] Redshift not firing after logoff/on

Sorry I'm not sure I'm following you, which Service file?

Here's display-manager.service. The first user one for redlight-gtk is in the first post.

                    
[Unit]
Description=Light Display Manager
Documentation=man:lightdm(1)
Conflicts=getty@tty1.service
After=getty@tty1.service systemd-user-sessions.service plymouth-quit.service acpid.service

[Service]
ExecStart=/usr/bin/lightdm
Restart=always
IgnoreSIGPIPE=no
BusName=org.freedesktop.DisplayManager

[Install]
Alias=display-manager.service

There's no sleep.service though, only sleep.target.

Offline

#10 2023-02-15 22:00:52

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,096

Re: [SOLVED] Redshift not firing after logoff/on

D'ohhh…
Let me guess: you typed "ExecStartPre=/usr/bin/sleep 2" into an interactive shell?

The idea was to add that to your redshift service.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2023-02-15 22:06:00

maboleth
Member
Registered: 2020-01-03
Posts: 230

Re: [SOLVED] Redshift not firing after logoff/on

I have tested it further. I was wrong about clicking on any menu inside LightDM. The thing is, if you login fast enough, redshift-gtk will remain. But if you linger several more seconds (regardless of what you are doing at the login screen) redshift will shutoff.

Yeah, I was typing that in the terminal. Should try it now.

Offline

#12 2023-02-15 22:14:42

maboleth
Member
Registered: 2020-01-03
Posts: 230

Re: [SOLVED] Redshift not firing after logoff/on

It seems to be working now, there's a delay of 2sec as you pointed here.

However, I had 2 instances at once after logging in. I will test it further.

Offline

#13 2023-02-15 22:23:31

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,096

Re: [SOLVED] Redshift not firing after logoff/on

systemctl list-unit-files | grep -i red
systemctl --user list-unit-files | grep -i red

Edit: https://wiki.archlinux.org/title/Redshift#Autostart
You didn't use all methods there at once, did you?

Last edited by seth (2023-02-15 22:24:50)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2023-02-15 22:31:30

maboleth
Member
Registered: 2020-01-03
Posts: 230

Re: [SOLVED] Redshift not firing after logoff/on

seth wrote:
systemctl list-unit-files | grep -i red
systemctl --user list-unit-files | grep -i red

Edit: https://wiki.archlinux.org/title/Redshift#Autostart
You didn't use all methods there at once, did you?

No. I only have redshift listed under 

systemctl --user list-unit-files | grep -i red
redshift-gtk.service                                                          enabled   enabled
redshift.service                                                              disabled  enabled

However, even with sleep 2 ExecStartPre set, if redshift-gtk isn't started at the login, it won't appear regardless what systemctl says that it is enabled x2

Logging off and on again won't engage anything. The only way for redshift to reappear is to either Reload completely or do manual

 systemctl --user start redshift-gtk

Update: it says redshift.service is enabled too, shouldn't be. I will fix that.

Last edited by maboleth (2023-02-15 22:32:27)

Offline

#15 2023-02-15 22:45:11

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,096

Re: [SOLVED] Redshift not firing after logoff/on

No, the preset is enabled.
Can you succesfully enable only the non-gtk version, though?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#16 2023-02-15 23:07:42

maboleth
Member
Registered: 2020-01-03
Posts: 230

Re: [SOLVED] Redshift not firing after logoff/on

Yeah I finally managed it.
It seems I forgot that I also --globally enabled it, so it was sort of 'always enabled'. Still that wasn't causing the problem here.

Simply, after logging off and on, redshift failed to load sometimes, unless there is a delay with 

ExecStartPre=/usr/bin/sleep 2

I will test it a bit more then put [solved] if all works as should. Thanks.

Update: works!

For anyone having the same problem put this in your redshift service file:

ExecStartPre=/usr/bin/sleep 2
ExecStart=/usr/bin/redshift-gtk

Last edited by maboleth (2023-02-16 09:30:19)

Offline

Pages: 1

Board footer

Powered by FluxBB