[Librem-5-dev] Power management issues

[Guido Günther]

Hi,
On Mon, Oct 22, 2018 at 10:29:58AM +0200, Benjamin Berg via Librem-5-dev wrote:
> Hi,
> 
> On Mon, 2018-10-22 at 09:20 +0200, Guido Günther wrote:
> > Hi Adrien,
> > On Mon, Oct 22, 2018 at 08:48:53AM +0200, Adrien Plazas via Librem-5-dev wrote:
> > >    Hi all,
> > >    Benjamin submitted the following issues to me, wondering if we (Purism
> > >    devs) would be interested in fixing some of them, here are they:
> > >    - [1]https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/88
> > >    - [2]https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/78
> > >    - [3]https://gitlab.gnome.org/GNOME/gnome-control-center/issues/232
> > >    - [4]https://gitlab.gnome.org/GNOME/gnome-control-center/issues/200
> > >    - [5]https://bugzilla.gnome.org/show_bug.cgi?id=657496
> > >    What do you think?
> > 
> > Thanks for collecting these! As mentioned on matrix I don't think these
> > hit us badly atm / can be worked around but as discussed during the
> > gnome-settings BoF we will need to put some work in here in the long
> > run.
> 
> Yeah, kind of expected that, and that is fair.
> 
> > On my mental roadmap this is somewhat past proper wwan panel integration
> > 
> >   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/132
> >   https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/70
> >   https://gitlab.gnome.org/GNOME/gcr/issues/8
> >   https://gitlab.gnome.org/GNOME/gcr/issues/7
> 
> Right, I should have a look at the WWAN module. Even though I don't
> really know what to look out for exactly :)
> 
> > and proper UI for the kill switches. I wonder if we should use a tag in
> > gitlab to track these? The "mobile apps initiative" tag doesn't seem
> > 100% right.
> 
> Hrm, kill switches. What about
>   https://bugzilla.gnome.org/show_bug.cgi?id=761051

Yeah I think we'll hit this and it even gets a bit more complex since
the hardware kill switches are (AFAIK) not known to the rfkill framework
in the kernel when switched off since they get "unplugged" so we might
need to teach g-s-d to read devices that might be there (switched on) or
not (switched off). This could be parsed from /sys though. I know better
how this all behaves in a couple of days and will then file bugs to move
the discussion over (this also affects laptops with hardware kill
switches).

Cheers,
 -- Guido