joerg has quit [Killed (tantalum.libera.chat (Nickname regained by services))]
joerg has joined #maemo-leste
rafael2k_ has joined #maemo-leste
elastic_dog has quit [Ping timeout: 252 seconds]
elastic_dog has joined #maemo-leste
rafael2k_ has quit [Ping timeout: 248 seconds]
<freemangordon>
uvos__: at least in the VM the issue is fixed
<freemangordon>
nela: please try to upgrade when you have a chance
mro has joined #maemo-leste
uvos__ has quit [Ping timeout: 248 seconds]
mro has quit [Quit: Leaving...]
maemish_ has joined #maemo-leste
uvos has joined #maemo-leste
<uvos>
freemangordon: great
Twig has joined #maemo-leste
<Wizzup>
uvos: ping
<Wizzup>
uvos: fmg and I planned to do elogind work today, there is the summary of where you are at in the logs ~1-2 days ago
<Wizzup>
where can we find that work? I know there are packges I built for -experimental
<Wizzup>
iirc there were two approaches, one is just having elogind run xsession
<Wizzup>
the other is to port things to more elogind-specific startup things
<uvos>
you install those 2 packages, h-s starts xsession scripts. but you have to remove all the init scripts that eventualy depend on the xsession one
<uvos>
theres nothing to useing elogind besides createing a session with pam_open_session
<uvos>
this autologin dose for you
<uvos>
the problem is that starting af-services breaks everything pretty mutch, elogind becomes unresponsive and you cant log out etc
<uvos>
educated guess is that because af-services joins user and roots session dbus bus, and elogind works via dbus, elogind gets very confused by the broken session cookies
<freemangordon>
uvos: what does this mean - joins session?
<freemangordon>
*sessions
<freemangordon>
it just starts user dbus session (iirc) and export the path in /tmp file
<uvos>
on leste the session bus is seemingly the same no matter if you are root or user
<uvos>
this is how mce can modify users gconf keys for instance
<freemangordon>
umm, not sure, lemme check
<uvos>
this seams very broken as it exposes all of roots interfaces to user
<freemangordon>
yes, 3, but we have the same before logind as well
<Wizzup>
hmm
<Wizzup>
can you show them in terminal again?
<freemangordon>
ops, sorry
<Wizzup>
can also be vm terminal :D
<freemangordon>
no idea
<freemangordon>
but yeah
<freemangordon>
could be ssh session
<Wizzup>
no, I mean, you could type in vm terminal instead of share this one
<freemangordon>
ah
<Wizzup>
the third one seems like one we probably didn't want to start
<freemangordon>
no, that one is ssh one I guess
<freemangordon>
but that's normal
<freemangordon>
lemme exit ssh session
<freemangordon>
and check from xterm
<freemangordon>
no idea what it is then
<Wizzup>
pstree?
<freemangordon>
but it is there even on beowulf
<Wizzup>
oh, ok
<Wizzup>
maybe some auto start
<freemangordon>
mhm
<freemangordon>
anywayt, this is not new
<Wizzup>
ok
<freemangordon>
IIRC it was there even back in ...umm...
<freemangordon>
what was before beowulf? ascii?
<freemangordon>
yeah, it iwas there in ascii as well
<Wizzup>
ok
<freemangordon>
see
<Wizzup>
the only reason I asked about gparted was to check if our potential solution, just running elogind without any integration would cause unexpected issues
<freemangordon>
the same on beowulf
<freemangordon>
we lack auth agent
<freemangordon>
this is not lack of integration IIUC
<Wizzup>
I understand, but I am not sure even sure what this would be on gnome / kde, I assume it is just a way to become root
<Wizzup>
like some gtk sudo thing
Blikje has joined #maemo-leste
<Wizzup>
right, I see what you show, but I think polkit is replaced by elogind
<Wizzup>
maybe gparted isn't the best test program in any case :)
<freemangordon>
I understand what you mean, but, I don;t hink that shall stop us from releaseing chimaera
<Wizzup>
yes
<freemangordon>
you can always start with sudo
<Wizzup>
shall I try it on my d4?
<freemangordon>
lemme see power button config first
<Wizzup>
right
<Wizzup>
I saw the key was already set, did you set it earlier?
<freemangordon>
hmm
<freemangordon>
no
<freemangordon>
this is the first boot with that key set
<freemangordon>
hmm, maybe there was some oops
<freemangordon>
now, why it waits there?
<Wizzup>
is this any different from beowulf?
<freemangordon>
lemme check
<freemangordon>
hmm
<freemangordon>
pressing power button does nothing
<Wizzup>
might take a bit
<Wizzup>
btw, maybe also worth checking if acpid is somehow pulled for your amd64 machine
<Wizzup>
that can also mess with the power button
<freemangordon>
see beowulf VM
<freemangordon>
it started in 20 seconds
<Wizzup>
ah
<Wizzup>
maybe it's blocking on elogind starting or something?
<Wizzup>
is elogind in any runlevel?
<freemangordon>
will have to enable boot log to see what it waits for
<freemangordon>
no idea
<freemangordon>
now it does nothing as well
<Wizzup>
what if you wait a bit longer
<freemangordon>
it boots
<Wizzup>
hmm
<freemangordon>
but waits twice for about 20 seconds doing nothing
<Wizzup>
smells like some dbus timeout
<freemangordon>
anyway, lemme see if power button is active
<freemangordon>
cool :)
<Wizzup>
:)
<Wizzup>
so why did it not work before?
<freemangordon>
ok, what else?
<freemangordon>
why do you ask me?
<Wizzup>
hehe
<freemangordon>
I never tried that :p
<freemangordon>
well, I have a theory
<freemangordon>
it works because it is *me* trying it :p
<freemangordon>
this happens 95% of the time :D
<Wizzup>
hehe
<Wizzup>
maybe it is polkit then
<freemangordon>
lemme install polkit
<freemangordon>
do you know tha package name?
<Wizzup>
apt-cache search polkit
<Wizzup>
?
<freemangordon>
any idea what ukui-polkit is?
<Wizzup>
no
maemish_ has quit [Quit: Connection closed for inactivity]
<Wizzup>
I doubt that is can restart, but maybe :D
<Wizzup>
try
<Wizzup>
sudo loginctl reload
<Wizzup>
freemangordon: ^
<freemangordon>
ummm
<freemangordon>
/etc/init.d/elogind restart
<freemangordon>
but ok
<Wizzup>
System Commands
<Wizzup>
reload
<Wizzup>
Reload the elogind configuration. While the daemon is being reloaded, all sockets elogind listens on behalf of user configuration will stay accessible.
<freemangordon>
so, once we have that released, I guess we can come-up with our own auth agent
<freemangordon>
should;t be that hard.
<freemangordon>
assuming we know how to properly register it
<Wizzup>
right
nmdv has joined #maemo-leste
<freemangordon>
blueman is running
<freemangordon>
I guess I have to review uvos' PR about hildon-status-menu
<Wizzup>
hildon-base is building
<Wizzup>
now leste-config
<freemangordon>
cool
<freemangordon>
Wizzup: why the conflict with consolekit?
<maemish_>
Following this at my friends summer cottage having my birthday party.
<freemangordon>
cheers and happy birthday
* freemangordon
is afk for 5 minutes
<Wizzup>
I left the jitsi, I'm going to upgrade from -devel
<Wizzup>
oh, -devel has the xorg with elgoind changed
<Wizzup>
I will remove it from there and move it to experimental
<freemangordon>
on my d4 I have 1:7.7+22
<Wizzup>
E: This installation run will require temporarily removing the essential package hildon-base:armhf due to a Conflicts/Pre-Depends loop. This is often bad, but if you really want to do it, activate the APT::Force-LoopBreak option.
<Wizzup>
E: Reverse conflicts early remove for package 'elogind:armhf' failed
<Wizzup>
freemangordon: huh, xorg?
<freemangordon>
yes
<Wizzup>
it should be 1.20.11.1
<Wizzup>
you might be checking some other version
<freemangordon>
oh, wait
<freemangordon>
this is xserver-xorg
<freemangordon>
xserver-xorg-core is 2:1.20.11.1-1+m7
<Wizzup>
right
<freemangordon>
is this the "correct" version
<freemangordon>
?
<Wizzup>
yes
<freemangordon>
ok
<freemangordon>
Wizzup: ok, why do we conflict consolekit and require alogind?
<freemangordon>
*elogind
<Wizzup>
why not?
<Wizzup>
do we want users to 'choose' which they want?
<Wizzup>
(that sounds funny out of context)
elastic_dog has quit [Quit: elastic_dog]
<freemangordon>
right now we do not *require* any of those
<Wizzup>
I think it is better to have a consistent base
<Wizzup>
otherwise when we get reports we have to ask
<freemangordon>
when we have proper integration, well, that's another story
<freemangordon>
ok, we can only conflict with ck without requiring elogind
<Wizzup>
that will still make it inconsistent
<freemangordon>
so if one wants to install blueman or something, elogind will be installed
<Wizzup>
I am fine if you want to go this way btw
<Wizzup>
just wasn't my first thought
<freemangordon>
as you wish, but I think this is more sane
<freemangordon>
Wizzup: do you want me to do anything else now?
<freemangordon>
uvos: could you help with investigating how to properly register auth agent when you have some spare time?
<Wizzup>
ok, my droid dist-upgraded to devel also boots
<freemangordon>
also, do we really need elogind for anything but that one?
<freemangordon>
sorry my ignorance
<Wizzup>
eventually if we can use it, it won't be bad for us I think
<Wizzup>
like we can run X as user
<Wizzup>
and streamline the dbus setup
<Wizzup>
I don
<Wizzup>
I don't know what -requires- it
<Wizzup>
hm, my device just rebooted
<Wizzup>
let's see if it's power button related
<Wizzup>
very much like what happened to you
<freemangordon>
maybe config didn;t make it
<Wizzup>
mhm
<freemangordon>
ugh
<freemangordon>
got sms while powering off :)
<Wizzup>
heh
<Wizzup>
telephony is *hard* :)
<freemangordon>
and that seems to hung the device
<Wizzup>
for me the power button worked just once
<Wizzup>
and now it's rebooting
<Wizzup>
the config seemed to be there though
<freemangordon>
hmm
<freemangordon>
thats why I powered down
<Wizzup>
hm?
<freemangordon>
to see if after power-up the config will still work
<Wizzup>
I don't follow
<freemangordon>
after I created the run-parts file, I didn't reboot
<freemangordon>
just restarted the service
<Wizzup>
I rebooted after installing elogind
<Wizzup>
first thing
<Wizzup>
and it doesn't seem to work as expected yet
<freemangordon>
and did sudo loginctl reload
<Wizzup>
let me check the mainconfig file
<freemangordon>
works here after reboot as well
<freemangordon>
maybe you have a typo or missing new line or dunno
<Wizzup>
and double press lock works too?
<freemangordon>
yes
<freemangordon>
single-press opens the menu
<freemangordon>
it is as it should be
<freemangordon>
*is it
<freemangordon>
do you have \n at the end of /etc/elogind/logind.conf.d/maemo-leste.conf ?