| xes | hi freemangordon! | 00:36 |
|---|---|---|
| joerg | s/ check what you're missing/ check IF you're missing anything/ | 02:33 |
| joerg | I mean, it "works", e.g. https://web.archive.org/web/20210615112444/https://garage.maemo.org/projects/aic34-eq/ https://web.archive.org/web/20200927194100/https://garage.maemo.org/frs/?group_id=1843&release_id=4028 but no idea how to *search* and *find* those | 03:56 |
| freemangordon | uvos__: at least in the VM the issue is fixed | 08:49 |
| freemangordon | nela: please try to upgrade when you have a chance | 08:49 |
| uvos | freemangordon: great | 10:35 |
| Wizzup | uvos: ping | 11:09 |
| 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 | 11:09 |
| Wizzup | where can we find that work? I know there are packges I built for -experimental | 11:09 |
| Wizzup | iirc there were two approaches, one is just having elogind run xsession | 11:11 |
| Wizzup | the other is to port things to more elogind-specific startup things | 11:11 |
| 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 | 11:24 |
| uvos | theres nothing to useing elogind besides createing a session with pam_open_session | 11:25 |
| uvos | this autologin dose for you | 11:25 |
| uvos | the problem is that starting af-services breaks everything pretty mutch, elogind becomes unresponsive and you cant log out etc | 11:25 |
| 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 | 11:26 |
| freemangordon | uvos: what does this mean - joins session? | 11:26 |
| freemangordon | *sessions | 11:27 |
| freemangordon | it just starts user dbus session (iirc) and export the path in /tmp file | 11:27 |
| uvos | on leste the session bus is seemingly the same no matter if you are root or user | 11:27 |
| uvos | this is how mce can modify users gconf keys for instance | 11:28 |
| freemangordon | umm, not sure, lemme check | 11:28 |
| uvos | this seams very broken as it exposes all of roots interfaces to user | 11:28 |
| freemangordon | no | 11:28 |
| freemangordon | sec | 11:28 |
| freemangordon | see https://pastebin.com/LWHhY5Xf | 11:29 |
| uvos | so? | 11:29 |
| freemangordon | ah, you mean there is no separate session bus for root? | 11:29 |
| uvos | yes | 11:29 |
| uvos | and root users of the session bus end up on users bus | 11:30 |
| freemangordon | but, isn;t root supported to work on system bus? | 11:30 |
| uvos | no | 11:30 |
| freemangordon | ok | 11:30 |
| uvos | the system bus is global yes | 11:30 |
| uvos | but root should have its own bus | 11:30 |
| freemangordon | I see | 11:30 |
| freemangordon | so, besides mce, what else is accessing user session bus? | 11:30 |
| uvos | anything that needs gconf | 11:31 |
| uvos | and is root | 11:31 |
| uvos | nothing uses it directly afaik | 11:31 |
| uvos | (mce dosent) | 11:31 |
| freemangordon | I see | 11:31 |
| freemangordon | but then again, I think back in fremantle days this was not broken | 11:31 |
| uvos | this is also what breaks gsettings | 11:31 |
| freemangordon | because gconf was not using dbus, adaik | 11:31 |
| freemangordon | *afaik | 11:31 |
| uvos | since gsettings will use dbus to send signals to write to the store | 11:32 |
| uvos | but will read directly | 11:32 |
| freemangordon | ok, so, to sum it up - this seems the same or similar issue we have with gconf in general, no? | 11:32 |
| uvos | this means that root gsettings clients on leste read from roots gsettings but write to users gesettings | 11:32 |
| Wizzup | as I understand it, and you might be at this point already, is that a certain dbus user sesssion is forced for 'user' user and root on leste | 11:33 |
| uvos | wich is quite problematic | 11:33 |
| freemangordon | maybe it is time to get back to the drawing board and decide what to replace gconf with | 11:33 |
| Wizzup | which elogind disallows | 11:33 |
| freemangordon | maybe not 'disallows' but rather 'never tested and not working' | 11:33 |
| Wizzup | I really hope we can separate gsettings/gconf and elogind | 11:33 |
| Wizzup | freemangordon: no, probably very explicitly disallows | 11:33 |
| freemangordon | right, in the context of systemd tracking user processes | 11:34 |
| uvos | it also feals like a huge security risk to me | 11:34 |
| Wizzup | ever since I have elogind on my laptop many things are all weird | 11:34 |
| uvos | imo | 11:34 |
| freemangordon | uvos: kinda agree | 11:34 |
| Wizzup | what, because root can do what user does? | 11:34 |
| freemangordon | though rott is allowed to do many things anyways | 11:34 |
| freemangordon | *root | 11:35 |
| Wizzup | we might want to check what actually blocks things | 11:35 |
| freemangordon | right | 11:35 |
| Wizzup | since currently we have uvos' educated guess | 11:35 |
| freemangordon | I will install elogind in my vm | 11:35 |
| Wizzup | in any case we will probably want to change af-services to use the dbus set up by elogind | 11:35 |
| Wizzup | so no longer should it make its own thing in /tmp | 11:36 |
| Wizzup | the path should be predictable given a username, too | 11:36 |
| Wizzup | so that way root could just access it all the same | 11:36 |
| Wizzup | if that makes sense | 11:36 |
| freemangordon | umm... | 11:36 |
| freemangordon | IIUC, this will allow 2 users to log in, no? | 11:36 |
| Wizzup | huh? | 11:36 |
| freemangordon | how is root supposed to know which exactly user to use dbus of? | 11:37 |
| Wizzup | well, it's 'user' | 11:37 |
| uvos | witch session | 11:37 |
| freemangordon | mhm | 11:37 |
| Wizzup | do you mean user vs system dbus? | 11:37 |
| freemangordon | this is simply not meant to be used on mobile IMO | 11:37 |
| freemangordon | if use 'user' have more than one session | 11:37 |
| freemangordon | is that allowed? | 11:37 |
| freemangordon | *user 'user' | 11:38 |
| Wizzup | I am not sure if I follow why this matters | 11:38 |
| uvos | you should be able to restict user to one session via pam | 11:38 |
| uvos | not sure if has side effects | 11:38 |
| uvos | ssh maybe | 11:38 |
| Wizzup | yes, ssh for sure | 11:38 |
| freemangordon | ssh should not start its own dbus, no? | 11:38 |
| Wizzup | I don't think so | 11:39 |
| freemangordon | that's why run-standalone.sh | 11:39 |
| Wizzup | I don't think that if we use elogind we will have trouble with dbus | 11:39 |
| Wizzup | the only thing we should fix is whatever overrides the session for root to be the user sesssion | 11:39 |
| Wizzup | that needs updating | 11:39 |
| Wizzup | (just my educated guess anyway) | 11:39 |
| freemangordon | but that, how is root going to access user's gconf settings? | 11:39 |
| uvos | or we kcik the can down the road | 11:39 |
| uvos | and just have elgoind installed | 11:39 |
| freemangordon | not time now | 11:39 |
| freemangordon | ah | 11:40 |
| uvos | and try to figure out how to disable it | 11:40 |
| freemangordon | yes, I will do that in few minutes | 11:40 |
| uvos | so it dosent interfeer | 11:40 |
| freemangordon | just want to have some background | 11:40 |
| Wizzup | the issue here is I think that it conflicts with ck and the other stuff | 11:40 |
| Wizzup | ok | 11:40 |
| freemangordon | ck? | 11:40 |
| Wizzup | ConsoleKit | 11:40 |
| freemangordon | it replaces it actually | 11:40 |
| freemangordon | so, going to remove hildon-meta and install elogind | 11:40 |
| freemangordon | do you want me to create some shared ssh session for you to watch? | 11:41 |
| freemangordon | or jit.si meeting? | 11:42 |
| Wizzup | that's fine, in 15 mins or so if you can wait | 11:42 |
| freemangordon | sure | 11:42 |
| Wizzup | ok | 11:42 |
| Wizzup | brb then | 11:42 |
| freemangordon | I will create jit.si meeting and will wait for both of you to join | 11:43 |
| freemangordon | https://meet.jit.si/elogind | 11:43 |
| freemangordon | uvos: ^^^ | 11:44 |
| freemangordon | brb lunch | 11:49 |
| Wizzup | freemangordon: i'm back, but will make a coffee and wait for you to return :D | 11:59 |
| freemangordon | I am back as well | 12:02 |
| Wizzup | ok | 12:02 |
| Wizzup | 2 mins and I will join | 12:02 |
| freemangordon | so, I made a snapshot of the vm and installed elogind | 12:02 |
| * Wizzup joins | 12:06 | |
| freemangordon | do you see VM screen? | 12:08 |
| Wizzup | yes | 12:08 |
| freemangordon | ok | 12:08 |
| freemangordon | ok, seems this is what uvos is talking about | 12:10 |
| freemangordon | but it is not logind that nags IIUC | 12:10 |
| freemangordon | *hangs | 12:10 |
| Wizzup | what hangs? | 12:10 |
| freemangordon | it was sitting on "starting dbus" | 12:11 |
| Wizzup | for me hangs = no progress | 12:11 |
| freemangordon | right | 12:11 |
| freemangordon | it progressed while I was swithing between windows | 12:11 |
| freemangordon | lemme open ssh session | 12:11 |
| freemangordon | what now? | 12:12 |
| freemangordon | we have both h-d and elogind running | 12:12 |
| Wizzup | I missed if you installed the pkgs from extras | 12:12 |
| freemangordon | I did not | 12:13 |
| Wizzup | is elogind running, or just installed? | 12:13 |
| freemangordon | I just installed modified hildon-base that does not conflict with elogind | 12:13 |
| freemangordon | see what I share on jitsi | 12:13 |
| Wizzup | yeah, I see | 12:13 |
| freemangordon | to me elogind seems running | 12:13 |
| Wizzup | ps xua | grep logind | 12:14 |
| freemangordon | and we still have the same dbus sessions | 12:14 |
| Wizzup | hmm | 12:14 |
| freemangordon | what now? | 12:14 |
| Wizzup | type 'loginctl' | 12:14 |
| Wizzup | well, this -seems- fine | 12:15 |
| freemangordon | I mean - what issues do we expect | 12:15 |
| freemangordon | lemme try to reboot | 12:15 |
| Wizzup | black screen, no h-d | 12:15 |
| freemangordon | hmm? | 12:15 |
| Wizzup | that's the issue I experienced when I installed elogind | 12:15 |
| Wizzup | (arguably a bit ago now) | 12:15 |
| freemangordon | lemme poweroff first | 12:16 |
| Wizzup | ok | 12:16 |
| freemangordon | seems I cannot open power button meny | 12:17 |
| freemangordon | *menu | 12:17 |
| Wizzup | that's probably dbus related | 12:17 |
| Wizzup | you can check /proc/<pid>/environ | grep -a DBUS | 12:17 |
| Wizzup | to see what certain programs run as | 12:17 |
| freemangordon | it powered down | 12:17 |
| Wizzup | ok | 12:17 |
| freemangordon | probably by elogind | 12:17 |
| Wizzup | ah, yes. | 12:17 |
| Wizzup | this is a config option | 12:17 |
| freemangordon | lemme check how to disable elognd power button attach | 12:17 |
| Wizzup | https://www.reddit.com/r/voidlinux/comments/n66ira/power_button_ignores_all_config_and_forcibly/ | 12:18 |
| Wizzup | HandlePowerKey=ignore | 12:18 |
| freemangordon | k | 12:18 |
| Wizzup | under [Login] | 12:18 |
| freemangordon | k | 12:18 |
| Wizzup | from https://forums.gentoo.org/viewtopic-p-8590155.html?sid=f7ed4c0f8ad04da6b20966c82220ee07 | 12:19 |
| Wizzup | I am kind of dumbfounded that it would just work though, I think this is because we have my patched X | 12:19 |
| Wizzup | maybe we should check if X runs as root or not | 12:20 |
| freemangordon | root | 12:21 |
| Wizzup | right, that's nor normal under elogind | 12:21 |
| Wizzup | so I wonder if we are started by elogind, or just /etc/init.d/xorg and /etc/init.d/xsession | 12:21 |
| freemangordon | it is because our scripts start it | 12:21 |
| Wizzup | I think the latter | 12:21 |
| Wizzup | yes | 12:21 |
| freemangordon | sure | 12:21 |
| Wizzup | but I am not sure if it even counts as elogind session then | 12:22 |
| freemangordon | but, do we *want* it started by logind *now* | 12:22 |
| Wizzup | I agree | 12:22 |
| uvos | sorry, im currently indisposed | 12:22 |
| freemangordon | or, we want to release chimaera | 12:22 |
| uvos | if you h | 12:22 |
| Wizzup | I'm just surprised it 'works' | 12:22 |
| Wizzup | uvos: np, this is kind of impromptu :) | 12:22 |
| uvos | if you start x via autologin/no-dm it will run as user | 12:22 |
| uvos | but you have to have it build with logind support | 12:22 |
| Wizzup | freemangordon: maybe we shall try the same on a d4 and see what happens | 12:23 |
| Wizzup | uvos: right, that is my understanding too, but that is only true of X in chimaera-experimental | 12:23 |
| uvos | its true on beowulf too | 12:23 |
| uvos | if you rebuild it | 12:23 |
| uvos | unless thats what you mean | 12:23 |
| freemangordon | ok, but lets set our goals, ok? | 12:24 |
| Wizzup | right, what I mean is that I build a X without logind for normal chimaera and beowulf, but for chimaera-experimental I built one with logind | 12:24 |
| freemangordon | what do we want? | 12:24 |
| Wizzup | freemangordon: IMO, to release chimaera, regardless of elogind integration | 12:24 |
| freemangordon | agree | 12:24 |
| Wizzup | but it might make sense to see if the apps that 'require' elogind work | 12:24 |
| Wizzup | was it gparted? or something? | 12:25 |
| freemangordon | then, we want to remove conflict from hildon-base and provide elogind config that is appropriate with current setup | 12:25 |
| freemangordon | lemme see | 12:25 |
| Wizzup | for me the confusing part is that I am pretty sure I did this for chimaera-experimental (hildon-base changes) | 12:25 |
| Wizzup | maybe the problem is that it was combined with my X changes, and this caused issues | 12:26 |
| Wizzup | looks like gparted didn't start, I am assuming you're checking via ssh? | 12:27 |
| Wizzup | oh I see it now | 12:27 |
| freemangordon | yes, started from command line with sudo gparted | 12:27 |
| Wizzup | what are the errors without sudo | 12:27 |
| freemangordon | otherwise it fails with "Error executing command as another user: No authentication agent found." | 12:27 |
| Wizzup | because it wants to become super user for some things | 12:27 |
| Wizzup | right | 12:27 |
| freemangordon | maybe we lack some other package | 12:28 |
| Wizzup | either that or something is on the wrong bus | 12:28 |
| Wizzup | can you inspect ps again and see if there is any other dbus | 12:28 |
| Wizzup | I think I saw three | 12:28 |
| freemangordon | https://bbs.archlinux.org/viewtopic.php?id=175895 | 12:28 |
| Wizzup | this predates elogind | 12:28 |
| freemangordon | yes, 3, but we have the same before logind as well | 12:29 |
| Wizzup | hmm | 12:29 |
| Wizzup | can you show them in terminal again? | 12:29 |
| freemangordon | ops, sorry | 12:29 |
| Wizzup | can also be vm terminal :D | 12:29 |
| freemangordon | no idea | 12:30 |
| freemangordon | but yeah | 12:30 |
| freemangordon | could be ssh session | 12:30 |
| Wizzup | no, I mean, you could type in vm terminal instead of share this one | 12:30 |
| freemangordon | ah | 12:30 |
| Wizzup | the third one seems like one we probably didn't want to start | 12:30 |
| freemangordon | no, that one is ssh one I guess | 12:30 |
| freemangordon | but that's normal | 12:31 |
| freemangordon | lemme exit ssh session | 12:31 |
| freemangordon | and check from xterm | 12:31 |
| freemangordon | no idea what it is then | 12:32 |
| Wizzup | pstree? | 12:32 |
| freemangordon | but it is there even on beowulf | 12:32 |
| Wizzup | oh, ok | 12:32 |
| Wizzup | maybe some auto start | 12:32 |
| freemangordon | mhm | 12:32 |
| freemangordon | anywayt, this is not new | 12:32 |
| Wizzup | ok | 12:32 |
| freemangordon | IIRC it was there even back in ...umm... | 12:32 |
| freemangordon | what was before beowulf? ascii? | 12:32 |
| freemangordon | yeah, it iwas there in ascii as well | 12:33 |
| Wizzup | ok | 12:33 |
| freemangordon | see | 12:33 |
| 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 | 12:33 |
| freemangordon | the same on beowulf | 12:34 |
| freemangordon | we lack auth agent | 12:34 |
| freemangordon | this is not lack of integration IIUC | 12:34 |
| 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 | 12:34 |
| Wizzup | like some gtk sudo thing | 12:34 |
| Wizzup | right, I see what you show, but I think polkit is replaced by elogind | 12:34 |
| Wizzup | maybe gparted isn't the best test program in any case :) | 12:35 |
| freemangordon | I understand what you mean, but, I don;t hink that shall stop us from releaseing chimaera | 12:35 |
| Wizzup | yes | 12:35 |
| freemangordon | you can always start with sudo | 12:36 |
| Wizzup | shall I try it on my d4? | 12:36 |
| freemangordon | lemme see power button config first | 12:36 |
| Wizzup | right | 12:36 |
| Wizzup | I saw the key was already set, did you set it earlier? | 12:37 |
| freemangordon | hmm | 12:37 |
| freemangordon | no | 12:37 |
| freemangordon | this is the first boot with that key set | 12:38 |
| freemangordon | hmm, maybe there was some oops | 12:38 |
| freemangordon | now, why it waits there? | 12:38 |
| Wizzup | is this any different from beowulf? | 12:39 |
| freemangordon | lemme check | 12:39 |
| freemangordon | hmm | 12:40 |
| freemangordon | pressing power button does nothing | 12:40 |
| Wizzup | might take a bit | 12:40 |
| Wizzup | btw, maybe also worth checking if acpid is somehow pulled for your amd64 machine | 12:40 |
| Wizzup | that can also mess with the power button | 12:41 |
| freemangordon | see beowulf VM | 12:41 |
| freemangordon | it started in 20 seconds | 12:41 |
| Wizzup | ah | 12:42 |
| Wizzup | maybe it's blocking on elogind starting or something? | 12:42 |
| Wizzup | is elogind in any runlevel? | 12:42 |
| freemangordon | will have to enable boot log to see what it waits for | 12:42 |
| freemangordon | no idea | 12:43 |
| freemangordon | now it does nothing as well | 12:43 |
| Wizzup | what if you wait a bit longer | 12:43 |
| freemangordon | it boots | 12:43 |
| Wizzup | hmm | 12:43 |
| freemangordon | but waits twice for about 20 seconds doing nothing | 12:43 |
| Wizzup | smells like some dbus timeout | 12:44 |
| freemangordon | anyway, lemme see if power button is active | 12:44 |
| freemangordon | cool :) | 12:44 |
| Wizzup | :) | 12:44 |
| Wizzup | so why did it not work before? | 12:44 |
| freemangordon | ok, what else? | 12:44 |
| freemangordon | why do you ask me? | 12:44 |
| Wizzup | hehe | 12:44 |
| freemangordon | I never tried that :p | 12:44 |
| freemangordon | well, I have a theory | 12:44 |
| freemangordon | it works because it is *me* trying it :p | 12:45 |
| freemangordon | this happens 95% of the time :D | 12:45 |
| Wizzup | hehe | 12:45 |
| Wizzup | maybe it is polkit then | 12:46 |
| freemangordon | lemme install polkit | 12:46 |
| freemangordon | do you know tha package name? | 12:46 |
| Wizzup | apt-cache search polkit | 12:47 |
| Wizzup | ? | 12:47 |
| freemangordon | any idea what ukui-polkit is? | 12:47 |
| Wizzup | no | 12:48 |
| Wizzup | I don't think ukui is relevant | 12:48 |
| Wizzup | https://packages.debian.org/search?suite=bullseye&searchon=names&keywords=polkit | 12:48 |
| Wizzup | maybe try libpolkit-agent-1-0 | 12:49 |
| Wizzup | is it running? | 12:49 |
| freemangordon | no, I will have to start it it seems | 12:49 |
| freemangordon | hmmm | 12:51 |
| Wizzup | compare dbus addrs maybe | 12:51 |
| Wizzup | although you did run standalone for both | 12:51 |
| Wizzup | maybe dbus-monitor or something? | 12:51 |
| freemangordon | right | 12:52 |
| Wizzup | I mean, this might not be very important | 12:52 |
| freemangordon | yeah, but I want to spend few more minutes | 12:52 |
| Wizzup | :) | 12:52 |
| Wizzup | should the agent run as user? I mean, probably, but? | 12:53 |
| Wizzup | and is polkitd running? | 12:54 |
| freemangordon | polkitd? | 12:54 |
| Wizzup | https://packages.debian.org/sid/polkitd | 12:54 |
| Wizzup | oh, it's not in bullseye | 12:54 |
| Wizzup | nevermind then I guess | 12:54 |
| Wizzup | I think the agent still needs a handler so that there is user interaction | 12:57 |
| freemangordon | what do you mean? | 12:57 |
| Wizzup | something that shows a dialog | 12:57 |
| Wizzup | like gtk-pinentry or something (analogous?) | 12:57 |
| uvos | https://uvos.xyz/maserati/screenshots/2020-06-30-205758_960x540_scrot.png | 12:58 |
| Wizzup | https://en.wikipedia.org/wiki/UKUI_(desktop_environment) | 12:58 |
| Wizzup | freemangordon: ^ | 12:58 |
| freemangordon | how did you do that? | 12:59 |
| uvos | gtk askpass implementation | 12:59 |
| Wizzup | but this is not polkit, this is gksudo | 12:59 |
| freemangordon | ok, but what is the package? | 12:59 |
| Wizzup | right? | 12:59 |
| uvos | Wizzup: no idea it just installed it and it worked in most places | 13:00 |
| Wizzup | uvos: what about gparted? | 13:00 |
| freemangordon | uvos: I am getting "Error executing command as another user: No authentication agent found." despite I installed ukui-polkit | 13:00 |
| uvos | good question about pacakge | 13:00 |
| freemangordon | ok, lets sum up | 13:01 |
| freemangordon | the only issue with logind so far is power button handling, from leste POV | 13:02 |
| uvos | ssh-askpass-fullscreen | 13:02 |
| uvos | if you have that installed and remove the ssh all all thing it will pop up in ham etc | 13:03 |
| Wizzup | freemangordon: I would like to check that it is also ok on phones | 13:03 |
| uvos | ill check gparted in a bit | 13:03 |
| freemangordon | I will do now | 13:03 |
| uvos | *sudo all all thing | 13:03 |
| uvos | not ssh | 13:03 |
| uvos | ie nopasswd sudo | 13:03 |
| freemangordon | "Could not open a connection to your authentication agent." | 13:06 |
| freemangordon | this is from ssh-add | 13:06 |
| freemangordon | in the meanwhile I have run-standalone.sh /usr/lib/x86_64-linux-gnu/ukui-polkit/polkit-ukui-authentication-agent-1 running | 13:06 |
| Wizzup | freemangordon: ukui is a desktop environment like MATE and gnome | 13:10 |
| freemangordon | right | 13:10 |
| Wizzup | so maybe it needs it's own session before any of this will work | 13:10 |
| freemangordon | ok | 13:10 |
| Wizzup | are you doing as d4 elogind instal or shall I try it? | 13:10 |
| freemangordon | anyway, shall we sum up and decide what next? | 13:11 |
| freemangordon | yes, will do | 13:11 |
| freemangordon | Wizzup: how to start virtual ssh or whatever? | 13:12 |
| Wizzup | I don't understand the questionb | 13:13 |
| freemangordon | anyway | 13:13 |
| freemangordon | shared ssh session | 13:13 |
| freemangordon | but not important | 13:13 |
| freemangordon | Wizzup: see jitsi | 13:14 |
| Wizzup | ok | 13:14 |
| Wizzup | if you git fetch you can checkout experimental branch | 13:15 |
| Wizzup | that works too | 13:16 |
| Wizzup | does this device have ck installed? | 13:17 |
| freemangordon | lemme check | 13:18 |
| freemangordon | yes, removing | 13:18 |
| freemangordon | that's it, right? | 13:20 |
| freemangordon | Wizzup: ^^^ | 13:20 |
| freemangordon | shall I reboot and see | 13:20 |
| Wizzup | yes | 13:23 |
| Wizzup | I think so | 13:23 |
| freemangordon | it is up and running | 13:24 |
| Wizzup | ok | 13:24 |
| Wizzup | shall I make a hildon-base for chimaera-devel? | 13:24 |
| Wizzup | and maybe have it conflict with consolekit | 13:24 |
| freemangordon | what about logind.conf? | 13:25 |
| freemangordon | we have to divert. or, does it support run-parts/ | 13:26 |
| freemangordon | ? | 13:26 |
| freemangordon | yes, it does | 13:26 |
| freemangordon | so we need /etc/elogind/logind.conf.d/maemo-leste.conf | 13:26 |
| Wizzup | right | 13:26 |
| freemangordon | are you going to do it? | 13:26 |
| freemangordon | BTW, why chimaera-devel? | 13:27 |
| Wizzup | ok, but let's try it on your phone | 13:27 |
| freemangordon | lets push that to chimaera and call it a day | 13:27 |
| freemangordon | sure, NP | 13:27 |
| Wizzup | -devel because then we don't accidentilly break the users who are already on chimaera | 13:27 |
| Wizzup | we can move it over an hour later | 13:27 |
| freemangordon | me and you I guess :D | 13:27 |
| Wizzup | I think more | 13:27 |
| Wizzup | rafael too for sure, maybe some users | 13:27 |
| freemangordon | oh, ok | 13:27 |
| Wizzup | so do we place the =ignore stuff there? | 13:28 |
| Wizzup | (teh file) | 13:28 |
| freemangordon | lemme test it gere | 13:28 |
| freemangordon | /etc/elogind/logind.conf.d/maemo-leste.conf thingie | 13:28 |
| freemangordon | *here | 13:28 |
| Wizzup | I doubt that is can restart, but maybe :D | 13:29 |
| Wizzup | try | 13:29 |
| Wizzup | sudo loginctl reload | 13:29 |
| Wizzup | freemangordon: ^ | 13:30 |
| freemangordon | ummm | 13:30 |
| freemangordon | /etc/init.d/elogind restart | 13:30 |
| freemangordon | but ok | 13:30 |
| Wizzup | System Commands | 13:30 |
| Wizzup | reload | 13:30 |
| Wizzup | Reload the elogind configuration. While the daemon is being reloaded, all sockets elogind listens on behalf of user configuration will stay accessible. | 13:30 |
| Wizzup | ok, feel free to try | 13:30 |
| freemangordon | already did | 13:30 |
| Wizzup | :) | 13:30 |
| freemangordon | it works | 13:30 |
| Wizzup | ok, maybe try restart | 13:30 |
| Wizzup | I will prepare packages | 13:30 |
| freemangordon | Wizzup: https://pastebin.com/hLRp8wJp | 13:31 |
| freemangordon | so, once we have that released, I guess we can come-up with our own auth agent | 13:32 |
| freemangordon | should;t be that hard. | 13:32 |
| freemangordon | assuming we know how to properly register it | 13:32 |
| Wizzup | right | 13:32 |
| freemangordon | blueman is running | 13:34 |
| freemangordon | I guess I have to review uvos' PR about hildon-status-menu | 13:34 |
| Wizzup | hildon-base is building | 13:35 |
| Wizzup | now leste-config | 13:35 |
| freemangordon | cool | 13:35 |
| freemangordon | Wizzup: why the conflict with consolekit? | 13:37 |
| maemish_ | Following this at my friends summer cottage having my birthday party. | 13:37 |
| freemangordon | cheers and happy birthday | 13:38 |
| * freemangordon is afk for 5 minutes | 13:39 | |
| Wizzup | I left the jitsi, I'm going to upgrade from -devel | 13:40 |
| Wizzup | oh, -devel has the xorg with elgoind changed | 13:41 |
| Wizzup | I will remove it from there and move it to experimental | 13:42 |
| freemangordon | on my d4 I have 1:7.7+22 | 13:47 |
| 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. | 13:48 |
| Wizzup | E: Reverse conflicts early remove for package 'elogind:armhf' failed | 13:48 |
| Wizzup | freemangordon: huh, xorg? | 13:48 |
| freemangordon | yes | 13:48 |
| Wizzup | it should be 1.20.11.1 | 13:48 |
| Wizzup | you might be checking some other version | 13:48 |
| freemangordon | oh, wait | 13:48 |
| freemangordon | this is xserver-xorg | 13:48 |
| freemangordon | xserver-xorg-core is 2:1.20.11.1-1+m7 | 13:48 |
| Wizzup | right | 13:49 |
| freemangordon | is this the "correct" version | 13:49 |
| freemangordon | ? | 13:49 |
| Wizzup | yes | 13:49 |
| freemangordon | ok | 13:49 |
| freemangordon | Wizzup: ok, why do we conflict consolekit and require alogind? | 13:50 |
| freemangordon | *elogind | 13:50 |
| Wizzup | why not? | 13:51 |
| Wizzup | do we want users to 'choose' which they want? | 13:51 |
| Wizzup | (that sounds funny out of context) | 13:51 |
| freemangordon | right now we do not *require* any of those | 13:51 |
| Wizzup | I think it is better to have a consistent base | 13:51 |
| freemangordon | when we have proper integration, well, that's another story | 13:51 |
| Wizzup | otherwise when we get reports we have to ask | 13:51 |
| freemangordon | ok, we can only conflict with ck without requiring elogind | 13:52 |
| Wizzup | that will still make it inconsistent | 13:52 |
| freemangordon | so if one wants to install blueman or something, elogind will be installed | 13:52 |
| Wizzup | I am fine if you want to go this way btw | 13:52 |
| Wizzup | just wasn't my first thought | 13:52 |
| freemangordon | as you wish, but I think this is more sane | 13:53 |
| freemangordon | Wizzup: do you want me to do anything else now? | 13:58 |
| freemangordon | uvos: could you help with investigating how to properly register auth agent when you have some spare time? | 13:59 |
| Wizzup | ok, my droid dist-upgraded to devel also boots | 14:00 |
| freemangordon | also, do we really need elogind for anything but that one? | 14:00 |
| freemangordon | sorry my ignorance | 14:01 |
| Wizzup | eventually if we can use it, it won't be bad for us I think | 14:01 |
| Wizzup | like we can run X as user | 14:01 |
| Wizzup | and streamline the dbus setup | 14:01 |
| Wizzup | I don | 14:01 |
| Wizzup | I don't know what -requires- it | 14:01 |
| Wizzup | hm, my device just rebooted | 14:01 |
| Wizzup | let's see if it's power button related | 14:01 |
| Wizzup | very much like what happened to you | 14:02 |
| freemangordon | maybe config didn;t make it | 14:02 |
| Wizzup | mhm | 14:02 |
| freemangordon | ugh | 14:02 |
| freemangordon | got sms while powering off :) | 14:02 |
| Wizzup | heh | 14:02 |
| Wizzup | telephony is *hard* :) | 14:03 |
| freemangordon | and that seems to hung the device | 14:04 |
| Wizzup | for me the power button worked just once | 14:04 |
| Wizzup | and now it's rebooting | 14:04 |
| Wizzup | the config seemed to be there though | 14:04 |
| freemangordon | hmm | 14:04 |
| freemangordon | thats why I powered down | 14:04 |
| Wizzup | hm? | 14:04 |
| freemangordon | to see if after power-up the config will still work | 14:04 |
| Wizzup | I don't follow | 14:05 |
| freemangordon | after I created the run-parts file, I didn't reboot | 14:05 |
| freemangordon | just restarted the service | 14:05 |
| Wizzup | I rebooted after installing elogind | 14:05 |
| Wizzup | first thing | 14:05 |
| Wizzup | and it doesn't seem to work as expected yet | 14:05 |
| freemangordon | and did sudo loginctl reload | 14:05 |
| Wizzup | let me check the mainconfig file | 14:05 |
| freemangordon | works here after reboot as well | 14:06 |
| freemangordon | maybe you have a typo or missing new line or dunno | 14:06 |
| Wizzup | and double press lock works too? | 14:07 |
| freemangordon | yes | 14:07 |
| freemangordon | single-press opens the menu | 14:07 |
| freemangordon | it is as it should be | 14:07 |
| freemangordon | *is it | 14:07 |
| freemangordon | do you have \n at the end of /etc/elogind/logind.conf.d/maemo-leste.conf ? | 14:08 |
| Wizzup | will check | 14:10 |
| Wizzup | after that I have go to for a bit | 14:10 |
| freemangordon | me too | 14:10 |
| Wizzup | wait | 14:10 |
| Wizzup | ok | 14:11 |
| Wizzup | I messed up the config place | 14:11 |
| freemangordon | hmm? | 14:11 |
| freemangordon | ah :) | 14:11 |
| Wizzup | ok | 14:11 |
| freemangordon | check for the right placehttps://pastebin.com/hLRp8wJp | 14:11 |
| Wizzup | yeah I did | 14:12 |
| Wizzup | I will fix when I get back | 14:12 |
| freemangordon | ok | 14:12 |
| freemangordon | ttyl | 14:12 |
| freemangordon | oh, ok, got it | 17:26 |
| freemangordon | we have to run auth agent in the same session as gparted, for example | 17:26 |
| buZz | uvos: what changed in the latest sphone release? could i already add new contacts from it now? | 17:26 |
| buZz | i tried longclicking or maemo context menus , but nothing seemed to do anything | 17:27 |
| uvos | nothing changed | 18:05 |
| uvos | the rebuild was nesscary because of the bug in ci | 18:06 |
| buZz | ahh ok | 18:06 |
| buZz | uvos: so just refactoring? | 18:07 |
| buZz | i mean the rebuild was just of a refactoring build? | 18:07 |
| uvos | no there was a bug in ci that caused beowulf to get the chimaera package | 18:07 |
| uvos | i had to bump the version and rebuild the pacakge | 18:07 |
| uvos | thats it | 18:07 |
| uvos | there are no code changes | 18:07 |
| buZz | ah ok | 18:07 |
| freemangordon | uvos: why don;t we use autologin to start maemo-launcher process? | 18:08 |
| uvos | why would we | 18:08 |
| uvos | and we do | 18:08 |
| uvos | in my system | 18:08 |
| uvos | the vm | 18:08 |
| freemangordon | because hildon-desktop is runs in maemo-launcer process env | 18:08 |
| freemangordon | we don;t need tinydm, IIUC | 18:09 |
| uvos | well tinydm is just a script that execs something in a .desktop file | 18:09 |
| freemangordon | mhm | 18:09 |
| uvos | in our case hildon-session | 18:09 |
| freemangordon | but it relies on autologin | 18:09 |
| uvos | we do want tinydm however | 18:09 |
| uvos | yes i know | 18:10 |
| uvos | hildon-session then runs scripts in a dir | 18:10 |
| uvos | thats all | 18:10 |
| freemangordon | and it is maemo-launcher that must be started as session parent | 18:10 |
| buZz | Wizzup: what was that application called, which you use to hookup droid4 to car media system? | 18:10 |
| uvos | i have a script there that starts the stuff in xsession | 18:10 |
| uvos | as well as m-l and some other sutff | 18:10 |
| freemangordon | ah | 18:10 |
| uvos | this is best | 18:10 |
| uvos | because this way hildon-sesson can be started by other dms too | 18:10 |
| uvos | like gdm or whatever | 18:11 |
| freemangordon | because what I did here: | 18:11 |
| freemangordon | start Xorg as root (no session) | 18:11 |
| freemangordon | start maemo-launcer via auto-login | 18:11 |
| uvos | why would you want to do that? | 18:11 |
| freemangordon | start hildon-desktop as normal | 18:11 |
| uvos | start x as root instead of in the session (by the dm) | 18:11 |
| freemangordon | because I don;t want to put even more packages just to fulfull some desktop-style boot/login process | 18:12 |
| freemangordon | *pull | 18:12 |
| uvos | but this is just worse | 18:12 |
| freemangordon | why it is better to start X as user? | 18:12 |
| uvos | for a 100 script? really? | 18:12 |
| uvos | because its often the target of cves? | 18:12 |
| uvos | not useing the desktop style session startup to spare 100 lines of bash is silly | 18:13 |
| freemangordon | ok, ok | 18:13 |
| uvos | the mapphones allso have a extreamly good case to want this system too | 18:13 |
| uvos | since they transform into laptops | 18:13 |
| freemangordon | am still trying to figure out how it is coupled | 18:13 |
| uvos | where you might wan to start another session | 18:13 |
| freemangordon | ok, so we start tinydm through autologin and the? | 18:14 |
| freemangordon | *then? | 18:14 |
| uvos | tinydm looks for a file in the xdg sessions dir | 18:14 |
| uvos | there is a file that points to hildon-session | 18:14 |
| uvos | then it starts x | 18:14 |
| freemangordon | 'it'? | 18:15 |
| uvos | and execs the hildon-sessoin script | 18:15 |
| uvos | tinydm | 18:15 |
| freemangordon | ok | 18:15 |
| uvos | the hildon-session script runs the stuff in xsession | 18:15 |
| freemangordon | and our hildon-session file start everything that is neeed | 18:15 |
| uvos | all of this works fine | 18:15 |
| uvos | if you avoid starting af-services | 18:15 |
| freemangordon | so, maemo-launcher shall be started by session script as well, right? | 18:15 |
| uvos | yes | 18:16 |
| freemangordon | I still don;t see why af-services is an issue | 18:16 |
| freemangordon | like, you explained... | 18:16 |
| uvos | https://github.com/maemo-leste/hildon-session/blob/master/hildon-session/usr/bin/hildon-session | 18:16 |
| freemangordon | but I don;t get the problem | 18:16 |
| uvos | its just a script that runs a .d | 18:16 |
| freemangordon | sure | 18:16 |
| freemangordon | I am talking about dbus user session | 18:17 |
| freemangordon | anyway, I need to think about that for a while | 18:18 |
| freemangordon | ttyl | 18:18 |
| buZz | 1668604753 <Wizzup> bt+mpris works in my car | 19:13 |
| buZz | ah, was that it? | 19:13 |
| buZz | i think so! | 19:14 |
| Wizzup | will catch up later tonight | 19:36 |
| joerg | you can tell buZz is a geek, from the timestamps they use ;-) | 23:01 |
| joerg | hmm | 23:07 |
| joerg | cmd: date -d @1668604753 >Wed Nov 16 14:19:13 CET 2022 | 23:07 |
| buZz | joerg: its from the irc.txt in topic ;) | 23:24 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
