<freemangordon>
I wonder why upower ignores POWER_SUPPLY_CAPACITY_LEVEL=High
<sicelo>
when upower decides that shutdown should happen, it sends a request to logind for that. so a quick hack would be to request a shutdown inhibit lock through logind
<freemangordon>
but we alredy do
<freemangordon>
*already
<freemangordon>
or, I thought so
<sicelo>
freemangordon: they say CAPACITY_LEVEL only matters for peripherals (they're wrong, and wouldn't budge)
<freemangordon>
bbiab
<sicelo>
but, upower maintainership seems to have changed since then, so we could have a go at this conversation with them
halftux_ has joined #maemo-leste
halftux has quit [Ping timeout: 252 seconds]
<Wizzup>
we shouldhave logind ignore all of this
<Wizzup>
the key names changed perhaps
<freemangordon>
Wizzup: seems not
<freemangordon>
bbl, dinner
<Wizzup>
they changed on my gentoo laptop recently
<Wizzup>
ttyl
<sicelo>
i'm also not in a position to check atm, but under normal circumstances (upower aside), i think we do want logind to respond to shutdown requests. e.g. users should be able to `loginctl shutdown` (which is basically the same request upower makes). leste currently works fine with this
<sicelo>
what i would need to confirm is - who actually makes the request to shut down the system (Leste) atm - is it MCE, after receiving appropriate signal from upower, or the shutdown request goes directly from upower to logind
<sicelo>
most stacks simply let logind (and upower) handle this stuff on their own. in our case, afaiui, we want mce to control system shutdown, etc., so it would seem mce needs to start holding inhibitor lock against shutdown operation
<sicelo>
i use that config under pmos with an udev rule that initiates shutdown when kernel sends uevent to say CAPACITY_LEVEL = Low/Critical, thus completely bypassing upower for making shutdown decisions
<freemangordon>
cool
<freemangordon>
hmm
<freemangordon>
upower 0.99.20-2
<freemangordon>
won't fly
<freemangordon>
maybe we shal jump to upstream upoerw anyways
<sicelo>
what glib2 is in daedalus? this upower needs at least 2.66
<sicelo>
then upower will never try to shutdown the system. obviously, that needs the shutting down decision to move somewhere else. i went with udev, but we can do it in mce perhaps
<sicelo>
sure, no rush :-)
Anasko has joined #maemo-leste
<freemangordon>
ugh, will have to build mesa on device :(
<sicelo>
i wonder how long that'd take on N900 ... a week? :-D
<Wizzup>
freemangordon: why not on the armhf vm?
<freemangordon>
I'll directly build in ci
<freemangordon>
the bug is abvious
<freemangordon>
*obvious
<Wizzup>
ok
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
Livio has joined #maemo-leste
arno11 has joined #maemo-leste
<freemangordon>
Wizzup: BTW, we will have to set DPI
<freemangordon>
RN everything is tiny on d4 :)
<Wizzup>
that's new
halftux_ has quit [Quit: leaving]
<freemangordon>
I think we were doing something about DPI?
<Wizzup>
don't remember, now in leste-config I don't think
<freemangordon>
yes, but here it seems dpi is taken into account
<Wizzup>
by who? gtk? h-d?
<freemangordon>
xorg
<freemangordon>
*everything* is tiny
<Wizzup>
looks like xorg changes more than we think :)
<Wizzup>
254mm = 2.5cm - that seems wrong, no?
<Wizzup>
wait, 25cm
<Wizzup>
that's also wron
<freemangordon>
yes, it is
<freemangordon>
but that's reported by xdpyinfo
<Wizzup>
it this in dts?
<Wizzup>
is this*
<freemangordon>
that means dpi 96
<freemangordon>
I think it is nowhere
<freemangordon>
and xorg assumes dpi of 96 by default
<freemangordon>
and then simply multiplies the resolution
<freemangordon>
a wild guess
<Wizzup>
you can set it with xrandr --dpi I think
<freemangordon>
no efffect
<Wizzup>
or when starting X, or in config, or setting in dts I guess
<freemangordon>
config?
<Wizzup>
xorg.conf
<freemangordon>
ok, but how?
<freemangordon>
hmm
<Wizzup>
By default, Xorg always sets DPI to 96 since 2009-01-30. A change was made with version 21.1 to provide proper DPI auto-detection, but reverted.
<Wizzup>
and this is X app,not some wayland stuff right?
<freemangordon>
yes
<Wizzup>
ok
<freemangordon>
oh, wait
<freemangordon>
lemme test something
<Wizzup>
but other than this, if I build an image now, will h-d and icons and osso-xterm look ok?
<freemangordon>
yes
<Wizzup>
ok
<Wizzup>
I will do that tomorrow then
<freemangordon>
ok
<Wizzup>
I got up at 4am so it's bed time for me :)
<freemangordon>
ugh
<freemangordon>
night!
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
akossh has quit [Quit: Leaving.]
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
Livio has quit [Remote host closed the connection]
Livio has joined #maemo-leste
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
Pali has quit [Quit: Pali]
<inky>
> they changed on my gentoo laptop recently
<inky>
>
<inky>
> ttyl
<inky>
wow fellow gentoo folk. (:
xmn has joined #maemo-leste
<gnarface>
afaik 96dpi is hardcoded default; no auto-detection took place
<gnarface>
(i've had to set it manually for some time now, but i don't know if it's always been wrong or it's just recently that my available displays have had extreme enough native dpi to notice a problem)
<gnarface>
basically for years i just happened to be using a 96dpi display
<gnarface>
then more recently i got my hands on a couple pine64 devices with really super high dpi, and a projector with a really super low dpi, and that's when it became apparent no auto-detection was taking place and i would have to specify it manually
<gnarface>
but it's possible that sometime before that it was also off but i just didn't notice because my older display's native dpi at the time wasn't that far off the default 96dpi value
<gnarface>
...but when your display is pushing 300dpi you're gonna have issues rendering fonts right in gtk
<gnarface>
(i think some of this complication may have also stemmed from changes to fontconfig)