Control: reassign -1 geoclue-2.0 Control: affects -1 redshift Hi Gabriel, Mike, and Nicolas,
On Thu, Jan 07, 2021 at 09:14:46PM +0000, Mike Gabriel wrote:
> On Do 07 Jan 2021 22:03:11 CET, Debian Bug Tracking System wrote:
>
> > Package: redshift-gtk
> > Version: 1.12-4
> > Followup-For: Bug #892275
> >
> > Dear Maintainer,
> >
> > It seems that I have the same bug since today's reboot.
> > See the attached screenshot.
> > Moreover, I can't stop redshift. I close the window and it comes back.
> > I can't stop it, even killing it makes the fatal window come back again.
> > redshift uses 100% of a processor.
> >
> > Yours,
> > n.
>
> I can confirm this. After upgrading geoclue-2.0 from 2.5.6-1 to 2.5.7-2,
> gtk-redshift is broken (again).
Urg. I'm really sorry you all were affected by this issue.
Could you check the following two things for me?
1. Does redshift work in “manual” mode, i.e. providing it with latitude and
longitude? That could be a workaround, as you can pass it `-l LAT:LON` on
the command line, or set it in ~/.config/redshift.conf like so:
[redshift]
location-provider=manual
[manual]
lat=12.34
lon=56.78
2. Is the AppArmor profile denying any actions from redshift?
You should be able to find the relevant logs in /var/log/audit.log
if you install/enable auditd.
> For some days now, redshift is unusable, thus bumping severity to grave
> again. Also, the upstream activity of redshift is suboptimal. Many open PRs,
> last activity dates back to summer 2020. :-(
Yes. I'm also pretty unimpressed with the size of d/patches by now. >_>'
I'm hopeful, though, as upstream mentionned resuming maintaining maintainance
of it, so there might be an upswing in activity.
Best,
nicoo
signature.asc
Description: PGP signature
