Redshift: add delay on startup due to latest geoclue2 update

[mattia-b89]

latest geoclue2 update makes redshift-gtk autostart to fail.
adding a delay solve the issue.

just add X-GNOME-Autostart-Delay=10 to the .desktop file to fix the issue

[jonls]

Which version of Redshift?

[mattia-b89]

1.12-2

On Sun, 12 Aug 2018, 23:01 Jon Lund Steffensen, [e-mail]
wrote:

Which version of Redshift?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jonls/redshift/issues/645#issuecomment-412371430, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAhSt4ggcg0qdISr0eHsC1DMc3LREaCbks5uQJeQgaJpZM4V5g4G
.

[jonls]

Thanks. What is the failure you see with autostart? What are the error messages?

[mattia-b89]

this is the error:

unfortunately my fix doesn't seem to work always... but now I don't have any idea on how to fix it...

EDIT: this issue looks like https://github.com/jonls/redshift/issues/636 and https://github.com/jonls/redshift/issues/318
EDIT2: redshift autostart-ed using the check on the systray applet

[mattia-b89]

UPDATE: sometimes I get the window-error above, sometimes I get this one else:

I think this bug report it's the same as https://github.com/jonls/redshift/issues/657

[mattia-b89]

I confirm workaround of adding a time.sleep(5) in redshift-gtk.in, fix the issue

[feluxe]

I have the same issue since the last dist upgrade.

[trinaldi]

Tried the change, nothing.

[jonls]

@mattia-b89 Since you posted an AccessDenied message above from GeoClue it's likely that you're seeing some issues that are due to GeoClue being misconfigured in your distribution or you may be seeing a known issue where GeoClue is crashing. Please see the summary here: https://github.com/jonls/redshift/issues/636#issuecomment-412295941 for workarounds and take a look at the comments by zeenix in that issue.

[mattia-b89]

@jonls Unfortunately shared previous experience do not help me: I already have geoclue2-2.4.11 and tried with and without geoclue.conf permission.
As I stated above: a time.sleep(5) in redshift-gtk.in, fix the issue.
For this reason I think it's a daemon/service priority problem, that could be related to GNOME since also downgrading to geoclue2-2.4.8 didn't fix the issue ???

[jonls]

Could be related to this: https://gitlab.freedesktop.org/geoclue/geoclue/issues/84 and this: https://bugzilla.redhat.com/show_bug.cgi?id=1537319 maybe? It looks like Geoclue may not be waiting long enough for the agent to start when it starts up. That would explain why Redshift fails to autostart and why adding a delay works.

[mattia-b89]

Yes, that's true.
As conservative action we can do is to add this five seconds delay.
Yes, this is a dirty workaround of an issue outside Redshift itself but it works...

[jonls]

This was fixed in Geoclue (https://gitlab.freedesktop.org/geoclue/geoclue/issues/84). Should be in Geoclue 2.5.0, I think. Please reopen if it's still an issue.

[mattia-b89]

this is the error:

same error