Package: redshift
Version: 1.12-4.1
Followup-For: Bug #808571
Let's not overcomplicate things. All that redshift needs to do is
regularly obtain the current timezone from the system, and get an
updated position from the location provider. Shouldn't be that hard
to do, and would beat regularly k
On Tue, 2015-12-22 at 06:58 +1300, martin f krafft wrote:
> > The current redshift now has support for geoclue2, which should
> > give it the information initially. But, like you have reported,
> > I need to check on how it behaves/honors changes in those events.
>
> Thank you!
I'm thinking how
also sprach Ritesh Raj Sarraf [2015-12-21 20:37 +1300]:
> What desktop framework are you using ?
None.
> And how exactly are you using
> redshift ?
I run redshift-gtk from .xsession.
> The current redshift now has support for geoclue2, which should
> give it the information initially. But, lik
Hello Martin,
On Mon, 2015-12-21 at 16:53 +1300, martin f krafft wrote:
> Travelling through several timezones, I found that redshift neither
> updates its understanding of what nighttime is (based on the
> timezone), nor does it make any efforts to re-acquire its position.
> Maybe it could instea
Package: redshift
Version: 1.10-5
Severity: normal
Travelling through several timezones, I found that redshift neither
updates its understanding of what nighttime is (based on the
timezone), nor does it make any efforts to re-acquire its position.
Maybe it could instead listen to appropriate event
5 matches
Mail list logo
