<freemangordon>
Wizzup: tried to build locally on d4, ended up with:
<freemangordon>
dpkg-shlibdeps: warning: symbol __aeabi_atexit@CXXABI_ARM_1.3.3 used by debian/qt-platform-maemo/usr/lib/arm-linux-gnueabihf/libQt5XcbMaemoQpa.so.5.15.2 found in none of the libraries
<uvos__>
hmm but it got to the code there "%s platform not yet supported"
<uvos__>
on beowulf
<uvos__>
thats how i knew
<uvos__>
about this list
<freemangordon>
no idea how did you manage to do it
<uvos__>
hm
uvos__ has quit [Quit: Konversation terminated!]
uvos__ has joined #maemo-leste
Danct12 has quit [Remote host closed the connection]
<norayr>
I broke my xperia's screen in the late december so for days i only have droid4 and pinephone. I don't want another android phone and i dont want to spend money on such a thing, so i will exclusively live under these two - droid4 and pp.
<norayr>
On pp under maemo currently it is impossible to charge the kbd and phone. If left alone without load on charge it looses 2% per day.
<norayr>
I know there are kbd charging improvements in newer kernels on pmos, not sure about mainline.
k1r1t0_N900 has left #maemo-leste [#maemo-leste]
<sicelo>
2% per day? that's kbd or phone?
<Wizzup>
freemangordon: we can fork it but it will take days to compile iirc
<freemangordon>
Wizzup: so, what are the options?
<freemangordon>
there is some bug in chromium we shall fix either ways
<Wizzup>
ok
<Wizzup>
I just hope it will work on ci
<Wizzup>
we'll see
<freemangordon>
git does not
<freemangordon>
apt-get source did
<freemangordon>
(in VM)
<Wizzup>
right, we need to get it from salsa
<freemangordon>
yes, from salsa ;)
<Wizzup>
uvos__: btw, any info and code you can share on elogind is welcome, I can't even install blueman without it
<Wizzup>
or just a status so I can take a look and start helping out
<freemangordon>
udisks2 depends on it too
<uvos__>
Wizzup: theres not more than is packaged, besides some hacks to vaious init scipts i have on a local machine to avoid loading things that break in the xdg session, avoid loading the xsession etc
<uvos__>
so packaged here is autologin/h-s/tindm
<uvos__>
but as mentined before the session work is tangential, since you dont have to use elogind, jus have it installed
<uvos__>
so what we really need is expiramental packages that remove the conflicts with elogind and remvoe the forks that disable it (like in xorg)
<uvos__>
and then running the old xsession and seeing what breaks
<uvos__>
i can runn most everything via hildon-session in vm however with elogind with no issues
<uvos__>
that i have found anyhow
<uvos__>
(besides dependancy hell in the init scripts)
<Wizzup>
uvos__: ok, so I need to start with the packages you made and then check conflicts?
<Wizzup>
what will run the x session?
<uvos__>
h-s runs the scripts of the xsession itself
<uvos__>
well most of them, i have jus the basic ones in there on vm
<uvos__>
Wizzup: best thing for you to do
<uvos__>
would be first to remvoe elogind conflicts and the xorg logind disable and depends on the xsession/xorg/h-d init script in expiramental
<uvos__>
since setting up hildon-session with those in place is a pain
<uvos__>
(you have to build x + meta localy and edit alot of scripts to get anything to work)
<Wizzup>
uvos__: ok
<Wizzup>
uvos__: I will set up the chimaera -testing, -devel and -experimental parts