<freemangordon>
Wizzup: ok, got it. maemo-launcher does not get started from init.d script even now, but from XSession script, so I am going to remove init.d script for maemo launcher
Twig has quit [Remote host closed the connection]
xmn has joined #maemo-leste
xmn has quit [Ping timeout: 255 seconds]
ungeskriptet has quit [Quit: You have been kicked for being idle]
pere has quit [Ping timeout: 248 seconds]
akossh has joined #maemo-leste
pere has joined #maemo-leste
mro has joined #maemo-leste
<freemangordon>
Wizzup: the boot 25 seconds hang is because of 'su - user'
ungeskriptet has joined #maemo-leste
<freemangordon>
google suggests it is related to selinux
<freemangordon>
hmm:
<freemangordon>
Mar 6 10:36:43 localhost dbus-daemon[2090]: [system] Activating service name='org.freedesktop.login1' requested by ':1.0' (uid=0 pid=2227 comm="su - user /etc/osso-af-init/real-af-dbus start ") (using servicehelper)
<freemangordon>
this is it I guess
<freemangordon>
uvos: Any idea what is this? ^^^
<freemangordon>
oh, ok, adding elogind as a dependency of dbus-user fixes the boot delay
<freemangordon>
this fixes poweroff delay as well
maemish_ has quit [Quit: Connection closed for inactivity]
newbie has joined #maemo-leste
arno11 has joined #maemo-leste
newbie has quit [Client Quit]
<Wizzup>
freemangordon: good work
<arno11>
Hi guys. Hope things are going well with chimaera stuff
<arno11>
fyi N900 overclocking + undervolting works fine
<arno11>
battery +20 %
<arno11>
Removing 125 freq helps a lot
<Wizzup>
the real battery saver is working to enable ret and off modes
<Wizzup>
but that requires kernel work
<Wizzup>
then you'll get a week no problem I think
<arno11>
i know but indeed that's not an easy task
<Wizzup>
:)
<Wizzup>
you can get RET on leste with gui, but it will just reset eventually
<arno11>
ah ok good to know
<Wizzup>
I already made some pm fixes to make this possible, but yeah, I don't remember where it resets
<arno11>
i found your pm stuff on github and tried few things
<arno11>
but it seems that something still block sleep mode
<Wizzup>
yeah, you also need to block some modules from loading iirc
<Wizzup>
I can check next weekend if you're interested in helping out
<arno11>
sure
mro has quit [Remote host closed the connection]
<arno11>
just ping me when you have time to check
mro has joined #maemo-leste
<Wizzup>
cool
<Wizzup>
freemangordon: the fixes you made, shall we push them to chimaera-devel?
arno11 has left #maemo-leste [#maemo-leste]
uvos__ has joined #maemo-leste
macros_ has joined #maemo-leste
<freemangordon>
Wizzup: what fixes?
<Wizzup>
freemangordon: 11:46 < freemangordon> oh, ok, adding elogind as a dependency of dbus-user fixes the boot delay
<freemangordon>
I will fix the package later on
<freemangordon>
nothing is still on github
<uvos__>
sorry i wasent qutie following allong
<freemangordon>
uvos__: after installing elogind, there is 25 seconds boot (and shutdown) delay
<uvos__>
so our solution wrt elogind is "kick the can down the road" for now? ie you are disableing it as far as possible
<uvos__>
while haveing he pacakge installed
<freemangordon>
we disable nothing
<uvos__>
but are you creating a lognd session?
<uvos__>
and running in that?
<freemangordon>
trying to
<uvos__>
ok
<uvos__>
neat
<uvos__>
sorry for still being busy :(
<freemangordon>
but, initially (and for the purpose of chimaera being released), there will be no logind session leste will run in
<uvos__>
ok
<uvos__>
yeah this should work with no mofidications really
<freemangordon>
so, elogind is installed and running
<freemangordon>
not really
<uvos__>
ok
<freemangordon>
as it seems su wants elogind running
nmdv has quit [Remote host closed the connection]
<uvos__>
ok
<freemangordon>
otherwise it wait for 25 seconds :)
<freemangordon>
*waits
<uvos__>
ok
<freemangordon>
also, weem maemo-launcher already runs from xsession script
<freemangordon>
*seems
<uvos__>
ok
<uvos__>
so it has the user env
<freemangordon>
yes
<uvos__>
maybe i should implement maemo-launcher sending itself the env via dbus, so that eatch proc has the env from where it is launched
<uvos__>
(since this probubly causes other issues too)
<freemangordon>
iI don;t see maemo-launcher causing any issues
<uvos__>
for now
<uvos__>
but its suprizeing when you application suddenly runs in a random env
<uvos__>
different from where it was launched from
<uvos__>
(seemingly)
<freemangordon>
so, my plan is to start /etc/X11/Xsession from autologin
<freemangordon>
and all will start working automagically
<Wizzup>
well the env affects how things are loaded potentially
<uvos__>
through hidon-session i hope
<freemangordon>
this will be for the future
<uvos__>
ok
<uvos__>
not sure why
<uvos__>
since its just the same ting
<freemangordon>
if xsession init.d script launches login session, I think we can call it a day for now
<uvos__>
but redirected trough 2 shells
<uvos__>
er bash scripts
<uvos__>
but ok
<uvos__>
i gues launching x is different
<freemangordon>
right
<uvos__>
launching x as root is bad however
<uvos__>
so is pulse
<uvos__>
we can have regular pulse then too
<freemangordon>
ok, but as a stop-gap (until we have all this working) I guess we can do it like that
<uvos__>
yes
<uvos__>
i agree
<freemangordon>
also, that would mean we do it in smaller steps
<uvos__>
yes
<freemangordon>
so easier to track the issues
<uvos__>
total agreement
<freemangordon>
:deal: :)
<uvos__>
hopefull ill find the time to do the rest
<freemangordon>
right
<freemangordon>
also, we shall keep gconf for now
<uvos__>
sure
<uvos__>
thats a nightmare
<freemangordon>
right
<uvos__>
but we should maybe decide on where to move
<uvos__>
soonish
<freemangordon>
agree
<uvos__>
since we can then start implementing stuff like switchble backends
<freemangordon>
I proposed configfs, but not sure if it can be 100% replacement
<uvos__>
me neither
<uvos__>
i think gsettings can work
<uvos__>
eccept icd2
<uvos__>
exceppt
<freemangordon>
no, because of the dynamic creation of keys
<uvos__>
you can do that
<freemangordon>
can I?
<freemangordon>
:)
<uvos__>
yes, but its quite rigid
<freemangordon>
anyway, this is for the future
<uvos__>
you have a scheme that references another sheme, but the number instances of this scheme is dynamic
<uvos__>
so that works in most casses
<freemangordon>
I see
<uvos__>
icd2 is wierd because the keys it creates changes
<uvos__>
anyhow
<freemangordon>
that looks over-engineered to me
<uvos__>
we can also use something else
<freemangordon>
(gsettings)
<freemangordon>
yeah
<uvos__>
the benefit is that the api is the same
<uvos__>
so are the schemes
<uvos__>
it just enforces things that are optional in gconf
<uvos__>
so you can migrate easier
<freemangordon>
hmm
<uvos__>
than elsewhere (presumably)
<uvos__>
in simple cases
<uvos__>
(not dynamic keys)
<freemangordon>
so, there is nothing similar to windows registry now in linux, right?
<uvos__>
i mean gconf is pretty simmular to windows registry
<uvos__>
so not sure what you mean by that
<freemangordon>
yes, but it is no more ;)
<bencoh>
nothing replaces gconf?
<freemangordon>
that's why I said *now*
<freemangordon>
bencoh: do you know of a replacement?
<uvos__>
a "well behaved" (compleat scheme with all keys etc) gconf application needs minimal modfication
<bencoh>
freemangordon: I dont, I'm just surprised
<uvos__>
bencoh: by what?
<freemangordon>
they migrated everything to gsettings, but it lacks functionality compared to gconf
<bencoh>
ah, I see
<uvos__>
i mean thats not really true, its just way way more enforceing of structure
<freemangordon>
and why is that needed?
<uvos__>
like every key needs to be in a scheme so gsettings knows 100% that i can delete all the keys when a application is uninstalled
<uvos__>
for instance
<freemangordon>
aha
<uvos__>
ie so that the windows registry is huge effect dosent occure :)
<freemangordon>
so, it is like "yeah, screw the functionality as long as we don;t have to do anything complicated" :)
<uvos__>
i mean gnome people wrote this
<uvos__>
so yes
<freemangordon>
yeah
elastic_dog has joined #maemo-leste
ceene has quit [Remote host closed the connection]
uvos__ has quit [Ping timeout: 256 seconds]
uvos__ has joined #maemo-leste
uvos__ has quit [Ping timeout: 252 seconds]
merp has joined #maemo-leste
mro has quit [Remote host closed the connection]
mro has joined #maemo-leste
mro has quit [Remote host closed the connection]
mro has joined #maemo-leste
xmn has joined #maemo-leste
mro_ has joined #maemo-leste
mro has quit [Ping timeout: 268 seconds]
mro_ has quit [Quit: Leaving...]
ungeskriptet has quit [Quit: You have been kicked for being idle]
maemish_ has joined #maemo-leste
<maemish_>
Good job.
elastic_dog has quit [Remote host closed the connection]
elastic_dog has joined #maemo-leste
<Wizzup>
uvos: I am trying to remember why I got the mz615 - easier to reflash?
<Wizzup>
god my memory is terrible
<Wizzup>
iirc it had no modem so there was a microsd card slot?
elastic_dog has quit [Ping timeout: 248 seconds]
elastic_dog has joined #maemo-leste
uvos__ has joined #maemo-leste
elastic_dog has quit [Read error: Connection reset by peer]
<uvos__>
Wizzup: some mz61x variants other than mz617 have a sdcard slot, yes, im not sure if mz615 is one of those, but i think yes
<uvos__>
this allows you to have mainline linux installed with resonable space without breaking android
<uvos__>
without the sdcard slot you have to first install linux to a small partition via fastboot and then install it somewhere else useing that install
<uvos__>
still
<uvos__>
mz615 has the extreamly locked bootloader too
<uvos__>
so you need to use the spicy method of installing kexecboot
elastic_dog has joined #maemo-leste
pere has quit [Ping timeout: 255 seconds]
elastic_dog has quit [Ping timeout: 248 seconds]
elastic_dog has joined #maemo-leste
uvos__ has quit [Ping timeout: 248 seconds]
pere has joined #maemo-leste
uvos__ has joined #maemo-leste
mro has joined #maemo-leste
mro has quit [Remote host closed the connection]
<freemangordon>
Wizzup: building osso-af-startup for chimaera
<freemangordon>
feel free to push the other changes once it is ready
<freemangordon>
hmm, seems autobuilder has issues
<freemangordon>
Wizzup: please have a look once you are around
<Wizzup>
freemangordon: what is the issue
<Wizzup>
everything seems to have passed
<freemangordon>
there is nothing in the irc
<Wizzup>
freemangordon: yes, it doesn't update for 'all' archtres
<Wizzup>
it's silly
<Wizzup>
I need to fix it some time
<freemangordon>
ok, osso-af-startup is there
<freemangordon>
we need config and hildon-base now
<freemangordon>
and we should be ready
<freemangordon>
maybe upgrade and confirm boot delay is gone
<Wizzup>
ok, later tonight :)
arno11 has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
uvos has joined #maemo-leste
LIERO_ has joined #maemo-leste
Twig has joined #maemo-leste
RedM_ has joined #maemo-leste
mro has joined #maemo-leste
mro has quit [Remote host closed the connection]
M1peter10[m] has quit [Ping timeout: 248 seconds]
LIERO has quit [Ping timeout: 248 seconds]
mighty17[m] has quit [Ping timeout: 248 seconds]
dreamer has quit [Ping timeout: 248 seconds]
RedW has quit [Ping timeout: 248 seconds]
M1peter10[m] has joined #maemo-leste
mighty17[m] has joined #maemo-leste
<sicelo>
arno11: nice work!
<sicelo>
might be useful to document the O/C work in wiki
arno11 has joined #maemo-leste
<arno11>
sicelo: thank you :)
<arno11>
its on the road for the wiki
<arno11>
just testing few other things before
maemish_ has quit [Quit: Connection closed for inactivity]
mro has joined #maemo-leste
dreamer has joined #maemo-leste
mro has quit [Read error: Connection reset by peer]
mro has joined #maemo-leste
maemish_ has joined #maemo-leste
Twig has quit [Remote host closed the connection]
arno11 has left #maemo-leste [#maemo-leste]
xmn has quit [Quit: ZZZzzz…]
mro has quit [Remote host closed the connection]
mro has joined #maemo-leste
mro_ has joined #maemo-leste
mro has quit [*.net *.split]
akossh has quit [Ping timeout: 252 seconds]
mro_ has quit [Quit: Leaving...]
joerg has quit [Excess Flood]
maemish_ has quit [Quit: Connection closed for inactivity]