-
Notifications
You must be signed in to change notification settings - Fork 424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
redshift-gtk segfault when using systemd enabled #265
Comments
It would definitely be great to have a backtrace from gdb. I'm not sure how to go about obtaining such a backtrace when the crash only happens as it is started from systemd. Perhaps somebody here knows a good way to debug this? Also, this issue is probably not specific to Redshift. Maybe ask the people at Arch Linux or GTK+ if they can help solving this? |
Thanks for the quick reply, I will take a look at getting gdb to spit out a backtrace when running from systemd. I'll come back on this in some time when I figure this out with help of Arch user forum! |
Same here: redshift version:
|
|
I still see the same behavior on my Arch Linux. I mean it's barely noticable because systemd restarts the service quite quickly, but something is wrong for sure ;) I have attached a stacktrace.
` |
The crash seems to happen because the systemd uses a special There is a special systemd target named
should be changed to
However, there needs to be support for
In such cases it may be possible to create a custom target unit that |
Another possible solution might be to keep redshift in the disabled state when |
I updated my comment above to include a clarified description of the problem and intended solution. Current workarounds are to either use @mwstobo If I understood what you meant, the environment is inherited from the user manager when the unit is started, and doesn't change later. |
I'm still running into this. Are there plans to offer a better fix? *Edit: Actually I think I might be running into something else. I get this same core dump even when starting redshift-gtk manually via systemctl. |
Night mode in GNOME 3 with GDM works pretty well. With LightDM or older versions of GNOME there were problems (I'm not sure what was the root). |
That's not super helpful, as I don't want to use GNOME. I want to use redshift. |
@andreyv Do you think this is still caused by the DISPLAY issue? I can run |
Exactly — see #265 (comment) for explanation. |
That only explains why it doesn't work when auto-started by systemd. It doesn't explain why it doesn't work when manually running |
That works for me. Probably in your case |
Aha! Looks like that script is not being run somehow. Do you what might cause this? I'm starting X with just a regular |
Your |
Thank you!!! |
just had a crash like this |
|
Hello,
I'm running redshift on arch linux and I want to use it by doing:
systemctl --user enable redshift-gtk
When I reboot and login (GDM+Gnome) redshift is not started. I look in logs:
(I believe this happens 5 time because of 4 retries that systemd does, but correct me if I'm wrong)
There seems to be a segfault in libgtk, but when I execute
systemctl --user start redshift-gtk
everything runs ok. I am also running arch' latest version of systemd that has the XAUTHORITY and DISPLAY set through a script. (https://wiki.archlinux.org/index.php/Systemd/User#DISPLAY_and_XAUTHORITY)Let me know how I can help resolve this.
The text was updated successfully, but these errors were encountered: