Monday, 2020-06-01

T42<edp_17> @elros34: Thanks, I have seen this too but I am not sure how I can add the KEY_HOMEPAGE into it. I'll try to find out.00:05
T42<edp_17> @ankaos: Are you sure the wifi is not built in?00:05
T42<ankaos> now i am trying to fix00:06
T42<edp_17> @ankaos: This is not answer to the question. Are you sure that the wifi driver is compiled as module?00:11
T42<ankaos> I guess, no00:14
T42<edp_17> Check you defconfig, that will tell you for sure.00:15
r0kk3rzcheck your out folder00:24
T42<elros34> for this device wlan is wil6210 by default build as a module but he set it to builtin and enabled different wlan drivers which probably cause issues. So after reverting all wlan related changes modprobe wil6210 should be enough to get wifi working00:25
T42<elros34> I cannot communicate with him properly but maybe you will explain it to him00:26
T42<edp_17> @elros34: evdev.ini helped! Now the home button wakes the screen up! Thanks.00:29
T42<elros34> hmm or maybe this wilocity driver is only for 60Mhz00:41
T42<elros34> GHz*00:41
T42<edp_17> Now the S-Pen also wakes the screen up! 😊  Now I would like to be able to swipe with it. I may need to contact spiiroin as he done that evdev.ini.00:42
T42<edp_17> *he authored00:43
r0kk3rzthe spen is some kind of bluetooth device?00:51
T42<edp_17> Well, I am not sure. It works without bt on, so I guess it is not a bt device.00:55
r0kk3rzif its just a touchscreen stylus it should work already00:56
T42<edp_17> No, it is more than that.00:56
T42<edp_17> And it doesn't work.00:57
T42<edp_17> The evdev_trace shows its events when I put it close to the screen. It has multiple pressure levels, and the evdev_trace shows when I pull it out and put it back.00:58
r0kk3rz"S Pen remote function subject to Bluetooth connection quality."00:59
r0kk3rzsays samsung00:59
r0kk3rzso its some kind of bluetooth device00:59
T42<edp_17> It might be, but it doesn't at all require to turn the bt on.01:00
T42<edp_17> It works with bt off on android.01:00
r0kk3rz'it works' to do what?01:01
T42<edp_17> Many things. Write onto the screen, select something on the screen then cut/copy/paste it. It is like a stylus but has its own menu options in a menu which appears if the S-pen is pulled out.01:03
r0kk3rzsailfish wont be able to do things like that01:04
T42<edp_17> I would be happy if I could use it as a normal stylus. I don't need the other functionalities like copy/paste.01:04
r0kk3rzsounds like a fair amount of software integration work01:04
r0kk3rzim surprised it doesnt work as a normal stylus01:04
kaluber0kk3rz: @edp_17: it probably wouldn't be too bad to modify the kernel driver to emulate a mouse\01:05
T42<edp_17> Yeah, I don't want to develop for sailfish what Samsung has developed for years for android. 😊01:05
T42<edp_17> @kalube: That sounds very good to me. My original intention was to be able to use it as a mouse.01:06
T42<edp_17> However, I have no idea how and where to start, so if you could help me, that would be fantastic.01:06
r0kk3rzdigging into how the thing works is a start01:07
r0kk3rzit must be using some kind of wireless protocol01:07
kalube@edp_17 I have no idea to be honest, I'd start by tracking down the downstream driver (grep your kernel source for the name given in evdev_trace), then I'd find docs on mouse events and how to send them and just add function calls to the existing driver01:08
r0kk3rzif its touches are showing up in evdev then it shouldnt be too bad01:09
r0kk3rzprint logs of evdev trace for normal touching and stylus touching01:10
T42<edp_17> Yes, evdev_trace shows all events when I pull out, put back, take it close or touches the screen.01:10
T42<elros34> Have you tried removing hardcoded event node from droid-hal-device.conf? Maybe qt input will take care of it and listen on both events01:10
kalubeyeah, it probably has some function that takes an x/y value and the pressure or whatever, you could just call mouse function when it's touching etc, and probably implement something nice with the unused functionality01:10
T42<edp_17> How can I see evdev_trace in human readable format?01:10
T42<edp_17> Yes it has X/Y axis and pressure level.01:11
T42<edp_17> Like: ABS_X=0 [0,7056] ABS_Y=0 [0,12544] ABS_PRESSURE=0 [0,2047] ABS_DISTANCE=0 [0,1024] ABS_TILT_X=0 [-63,63]01:11
kalube@edp_17 EASY01:11
T42<edp_17> @kalube: Is it? Might be for you. :P01:12
T42<edp_17> However I am happy to learn.01:12
T42<edp_17> @elros34: No, I have not tried that.01:13
kalube@edp_17 what's the device called in evdev_trace? and link your kernel sources01:13
kalubeDefinitely try what @elros34 said first though01:13
T42<elros34> based on qt doc, maybe adding evdevtablet plugin01:14
T42<edp_17> @kalube:
kalubeWould be cool if it showed up as a drawing tablet or something like that01:15
kalubeoh it does01:15
kalubeYou can probably get it working without messing with kernel then01:16
T42<edp_17> Okay, I have removed the /dev/input/event2 from /var/lib/environment/compositor/droid-hal-device.conf.01:17
T42<edp_17> Should I reboot?01:17
T42<edp_17> Or just restart lipstick?01:17
T42<elros34> add evdevtablet also01:17
kaluberestarting lipstick isn't consistent is it?01:17
T42<edp_17> evdevtablet? How?01:18
T42<elros34> should be pretty obvious if you look in that file01:18
T42<edp_17> Okay, so as a plugin like : -plugin: evdevtablet?01:20
T42<edp_17> or just simply add to the end of: -plugin evdevkeyboard:keymap=/usr/share/qt5/keymaps/droid.qmap01:20
T42<edp_17> like: -plugin evdevkeyboard:keymap=/usr/share/qt5/keymaps/droid.qmap:evdevtablet01:20
T42<edp_17> Okay, to the end like -plugin evdevtablet01:21
T42<edp_17> Is there any parameters/arguments/whatever?01:21
T42<edp_17> I have added and rebooted but doesn't work.01:24
T42<edp_17> I have tried these:
T42<ankaos> @elros34 [for this device wlan is wil6210 by default bui …], Not work wil621001:38
T42<elros34> so modprobe wlan01:41
T42<elros34> @edp_17 without colon01:42
T42<edp_17> Only -plugin evdevtablet/dev/input/event3 ?01:43
T42<elros34> -plugin evdevtouch01:43
T42<edp_17> Okay, I am doing it.01:44
T42<elros34> QT_QPA_EVDEV_DEBUG could also be useful or/and QT_LOGGING_RULES="qt.qpa.input=true"01:45
T42<edp_17> I have realized that the s-pen also react for cat /dev/input/mice and /dev/input/mouse001:46
T42<edp_17> @elros34: where should I set these?01:47
T42<edp_17> Got that. In the same file.01:48
T42<edp_17> Okay, the droid-hal-device.conf on the device looks like:
T42<edp_17> Okay, I missed that I need to remove the : from the -plugin evdevtouch. Sorry.01:50
T42<edp_17> Okay, now the droid-hal-device.conf looks like:
T42<elros34> QT_QPA_EVDEV_DEBUG is missing value01:56
T42<edp_17> And what should that be?01:56
T42<elros34> 1?01:57
T42<edp_17> So like: QT_QPA_EVDEV_DEBUG="1" ?01:58
T42<edp_17> Or just: QT_QPA_EVDEV_DEBUG=1?01:58
T42<elros34> id doesnt matter, its env varable01:59
T42<edp_17> Okay, I set QT_QPA_EVDEV_DEBUG=1.02:00
T42<edp_17> And rebooted.02:00
T42<edp_17> How can I get those logs?02:00
T42<elros34> same as always: journalctl02:01
T42<edp_17> Here it is:
T42<edp_17> At one point I pulled out the s-pen and touched the screen a few times.02:03
T42<edp_17> Sorry guys, I need some sleep now. Can we continue tomorrow?02:05
T42<edp_17> Good night!02:06
T42<elros34> at least evdevtablet plugin is loaded. BTW you should disable TvoutService_C as it fails anyway02:14
*** ahjolinna_ is now known as ahjolinna02:45
T42<Verevka86> @adampigg Hello, its missing-04:21
T42<Verevka86> And missing include-05:12
spiiroinrinigus: fpd Verify = start dummy enroll, 1st progress report from below -> cancel enroll + report success upwards05:20
spiiroinrinigus: it is used only from csd app05:20
rinigusVerevka86: PR with Android packaging scripts is not need yet. Wait a bit and we should get it ready05:26
rinigusspiiroin: thank you very much! Will have to implement it05:27
rinigusspiiroin: from current API, it's not clear how to prevent manipulation with fingerprints without some Auth layer. Unless it's enforced by app somehow05:29
spiiroinrinigus: can you elaborate what you mean? (atm downstairs = user can add/remove fingerprints, if that is what you meant)05:33
spiiroin@edp_17: from mce pov that s-pen probably looks like single-touch device.. to verify do: systemctl mce stop; mce -Tq -levent-input.c:evin_iomon_device_add --auto-exit=005:40
spiiroin... lists evdev probing results, stte: /dev/input/event1: name='synaptics_dsx' type=TOUCHSCREEN05:40
spiirointhat type is used for mice etc also -> double click == double tap etc05:41
spiiroinfor actual interaction with ui also lipstick needs to grok what is going on05:41
rinigusspiiroin: sure. we can add/remove fingerprints without asking for PIN code or any other way of identification if the phone was unlocked. in settings app, you do ask for PIN/auth before operations on fingerprints, but that is not somehow enforced on dbus.05:43
rinigusunless we miss some challenge/response in FP DBUS api05:44
spiiroinrinigus: devicelock manages options that can be used for auth. fpd identify is used only when devicelock thinks it is possible and ok.05:47
spiiroinearlier fp use depended only on past attempt count.05:47
spiiroincurrently devel head state = lock code required after reboot / user switch05:48
spiiroinwhat fpd needs to do: when stateful op is started, lock on to client -> cancel etc is accepted only from client who initiated the op05:49
spiirointhe latter also allows "shared fp use" between mce (wakeup) and devicelock (auth)05:52
spiiroinmce parts are here:
spiiroinbehind the scene fpd also needs to deal with user session tracking, fp set switching, etc in a manner that is "invisible" to apps using/tracking dbus stuff05:54
rinigusspiiroin: interesting Todo, will be critical when we get to multiuser support.06:01
T42<adampigg> @Verevka86 [@adampigg Hello, its missing-06:21
T42<adampigg> https://github.c …], Its in a PR atm06:21
rinigusspiiroin: I filed the issues based on your comments, thank you! (cc @adampigg)06:29
spiiroinrinigus: I guess the important bits atm: that "lock-onto-client" + every op that starts should end with: aborted, failed, or appropriate success signal 1st, then fpd going idle06:47
spiiroinso that signaling that is related to operation happens while fpd is in state that indicates that operation06:47
T42<adampigg> Yeah,  i found that emitting idle too soon broke things06:49
spiiroin... clients still need to deal also with sun-spots like fpd restarts / out of state signaling06:49
T42<adampigg> So chanfed that a.few days ago06:49
rinigusspiiroin: that is not as it is now, as far as I know. I pushed the signaling for earlier as some ops also lead to recheck of the list of fingerprints to ensure android<->sfos maps consistency. will have to revise that06:50
spiiroinrinigus: getting list of fingerprints is exception, it is not stateful06:51
rinigusspiiroin: on dbus side it is not, so we have to keep a map ready06:51
spiiroinrinigus: yes. in some/many devices you can't even enumerate templates android side has -> have to have cache and hope it stays in sync06:52
rinigus... I probably overdid it as I did not trust recorded state. maybe should just init it once on start and then trust the changes as reported06:52
T42<adampigg> Rinigus, will merge all prs this morning,  got some meetings first tho06:54
rinigus@adampigg: I can work on that in the evening only, so that sounds fine06:54
rinigusspiiroin: we then will revise accordingly and make signaling work as expected06:55
T42<adampigg> We got any more porters trying yet?06:55
* spiiroin tries to recall if there has been any device where fp hal would have worked as-expected ...06:55
T42<birdzhang> @adampigg i tried on davinci, in-screen fp, when enrolling, Acquisition: FPACQUIRED_UNRECOGNIZED, and no progress, no light up on screen07:38
T42<birdzhang> dmesg and logcat logs when enroll
T42<edp_17> spiiroin and @elros34, thanks for the advice. I'll try that you suggested however I am not sure about the grok you mentioned for lipstick.07:44
rinigus@birdzhang: just in case, try to use -test app
rinigus... assuming that you used Settings07:52
T42<birdzhang> no, i use this test app07:52
rinigusthen please add journal log as well07:53
T42<birdzhang> no journal log at all07:53
T42<birdzhang> btw, it's not working on ubports too, @erfanoabdi07:54
rinigusstrange, the daemon should be rather chatty in the journal07:54
rinigusbirdzhang: no idea what's piggz position on it, but I would prefer us to get to the first release and then start testing on other devices. last night people were trying to follow README that was referring to things which are not merged. we will have to reorganize storage => mess with databases and there is no wish to start data migration support08:06
rinigusthere are probably more issues to be solved.08:06
riniguswe do have a decent speed in development, so it should be ready soon. just wait a bit.08:07
T42<birdzhang> Yeah, no hurry, and good job ;)08:08
rinigusbirdzhang: as you seem to have issues with UT as well, try to get android logcats corresponding to FP operations meanwhile. then you can later debug and see what is failing when you have good log to compare to08:08
T42<birdzhang> i will do it08:09
T42<edp_17> spiiroin: The result of 'mce -Tq -levent-input.c:evin_iomon_device_add --auto-exit=0':
T42<edp_17> event-input.c: evin_iomon_device_add(): /dev/input/event3: name='sec_e-pen' type=TOUCHSCREEN08:16
T42<edp_17> How do you mean: "lists evdev probing results, stte: /dev/input/event1: name='synaptics_dsx' type=TOUCHSCREEN"08:18
T42<edp_17> If you meant evdev_trace output, that is here:
T42archi_dagachs was added by: archi_dagachs08:21
spiiroin@edp_17: I meant that line with "name='sec_e-pen' type=TOUCHSCREEN" -> from mce pov the pen is mouse/touch kind device = good (in theory it could have been treated as sensor / whatnot)08:34
T42<edp_17> spiiroin: I see, thanks for confirming. Thought you advised me to run a command or something and it was not clear. 😊08:49
T42<edp_17> Last night I played with cat /dev/input/mice and cat /dev/input/mouse0 and cat /dev/input/event3. All three did the same when I touched the screen with the s-pen, so any of them can be used to interact with the s-pen. However I don't know how. 😁08:51
T42<KernelPanix> build/make/core/ error: FindEmulator: find: `tools/metalava/manual': No such file or directory08:55
T42<KernelPanix> @KernelPanix [build/make/core/ error: FindEm …], please help me this errors08:56
spiiroin@edp_17 "evdev_trace -t 3" -> prints events from /dev/input/event3 (in more human readable from than plain cat does)09:01
rinigusmal: ping regarding compass-related MRs to qtsensors and sensorfwd review.09:03
T42<edp_17> spiiroin: Thank you! It looks much better. I used the evdev_trace -t (without the event number) before but I thought there is something else as well. Anyway, for referece the output is here:
spiiroin@edp_17 looks like mix betweem single-touch device (ABS_X/Y + BTN_TOUCH) and mouse (reports also when not pressed down) with some extras09:20
spiiroindoes it report also when display is off?09:20
T42<edp_17> Yes it does report when the screen is off. All what you see in the last log recorded with screen off.09:23
zinstack625@KernelPanix hybris-16.0? If yes, then hybris-patches/ --mb09:24
T42<KernelPanix> @zinstack625 [@KernelPanix hybris-16.0? If yes, then hybris- …], okay thanks u09:24
T42<KernelPanix> (Sticker, 512x507)
spiiroin@edp_17 that sw_13 is interesting... 0x13 > 0x0f = SW_MAX when it possibly could/should be SW_PEN_INSERTED=0x0f?09:29
zinstack625Building rootfs or whatnot. rpm/dhd/helpers/ dies like this: Log has this: Tried reinstalling target to no avail. I did interrupt the building as it was stuck on something I can't recall. I could try deleting that file, but I'm not sure where it is. Any ideas?09:30
T42<edp_17> zinstack625: I got this before. You need to install droid-config in Platform. use this command: sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper install droid-config09:35
T42<edp_17> Then re-run the rpm/dhd/helpers/build_packages.sh09:35
T42<edp_17> spiiroin: Tbh, I don't know. The 0x013/SW_0013 does change its value to 1 or 0 depending on the s-pen is out or not.09:37
T42<edp_17> The other thing I do not understand is the home button. On the S2 port, the home button just works out of the box, while on this N4 port it doesn't.09:39
zinstack625@edp_17 Still fails. From what I see is it's trying to unpack initramfs to somewhere, but there this file already exists. In Platform, /boot is empty, so, perhaps there is rootfs getting ready somewhere and there it should be?09:52
T42<edp_17> zinstack625: what's the new error message?09:55
T42<edp_17> zinstack625: have you seen this?
zinstack625@edp_17 I have, but I forgot the url. Thanks09:59
T42<edp_17> zinstack625: No problem, your solution is on that link or here
T42<edp_17> For me on one of my ports it was enough to install droid-config, but on some others I needed to apply this fix.10:02
T42<adampigg> rinigus: @birdzhang Ive no issue with others trying it out, so long as they understand the rate of flux10:04
piggzspiiroin: rinigus: so, for Verify, state changes to enrolling, emits a progress update, csd calls Abort and state goes back to idle?  sounds like that can just use a timer to emit the progress?10:07
T42<adampigg> or, do you actually use the finger.10:10
T42<adampigg> just ran csd and thats what it looks like10:10
T42<adampigg> thats better actually10:10
T42<erfanoabdi> @birdzhang [btw, it's not working on ubports too, @erfanoa …], Sorry can't remember your device model10:32
T42<erfanoabdi> Is it fingerprint on screen?10:32
T42<birdzhang> Yeah, Redmi K2010:37
T42<erfanoabdi> @birdzhang [Yeah, Redmi K20], Fod still not supported10:39
T42<birdzhang> Okay10:40
rinigus@adampigg: I guess we need to file the issue to support Verify as well10:47
rinigusthnx for merging it all10:47
piggzrinigus: struggling with Verify ... its getting called, im emitting the progress, but its not Aborting like spiiroin suggested11:09
piggzmaybe it expects the daemon to abort after the progress?11:10
spiiroinpiggz: nope... a sec ;-)11:10
spiiroinpiggz: fpd does hal->enroll() ... hal->cancel; csd does fpd->verify() and waits for success/failure11:11
spiiroini.e. verify is implemented as enroll operation that is terminated when the info that is needed has been received11:11
spiiroinwhich is finger-on-sensor is detected = the 1st progress report fpd gets from hal11:12
piggzspiiroin: so, like i said, the fpd needs to terminate :#011:12
piggzone sec, lets try that11:12
piggzspiiroin: in normal enroll, success is indicated by the Added signal which contains the name supplied by the Enroll call..... what signal is expected for Verify, which doesnt take a string name parameter?11:18
T42<edp_17> @elros34: There are a few problems with the bt. 1,. After 3 minutes, it turns off itself (even if it is connected to another device). 2,. Not always can be paired (sometimes I need to turn the bt on and reboot) 3,. However it shows the device connected to a bluetooth loudspeaker, the speaker still blinking (waiting for the connection)11:43
T42and the sound is not routed.11:43
T42<edp_17> Is number 3 can be connected the incorrect scopcm value?11:44
T42<elros34> I have no idea but adding some random values for for hciattach can cause random issues.11:46
T42<elros34> BTW I am not bluetooth expert:)11:47
T42<edp_17> @elros34: Okay, I see. Now it does make sense what you told me last time. 😊12:02
T42<edp_17> This:
T42<edp_17> 😊12:05
piggzspiiroin: rinigus: Verify() implemented and passes csd test.12:48
riniguspiggz: great! I am still watching / will be able to join later tonight13:07
zinstackRootfs is built, it was not happy at hwservicemanager being unable to start (probably due to selinux being dead). I copied a sparce from sony-nile to deal with it and now it's not giving out ips over usb and bootloops after about a minute. From recovery I did ln -s /dev/null /data/.stowaways/sailfishos/etc/systemd/system/ofono.service, but it still bootloops. Here I am again, somebody knows what to do?13:43
zinstackAlso, I'd like to package rootfs as gzip, as twrp doesn't support bzip213:43
T42<edp_17> zinstack: Next to the bzip2, you should have got a normal zip image too. I am always installing that with twrp.14:05
T42<edp_17> If you don't have the zip image, the build is not complete. I think.14:05
zinstack@edp_17 There is a zip archive, but installing it is impossible, because inside it there is a rootfs tarball packed in bzip2. Installing it will copy that to /data, create a stowaway and extract it to the stowaway. That last part is bothersome, because there is no support for bzip2 in my twrp image (it's official btw)14:11
T42<edp_17> I am always installing the zip. It need to be flashed the android image first, then the sailfish image on top of it. Then, reboot. I have never heard of any other ways. It works the same way even on the officially supported Sony XA2.14:14
T42<edp_17> If your twrp doesn't support this, you should find an older one that does support.14:15
zinstack@edp_17 The eldest one is 3.3.1-0 and it uses toybox as well. Don't know much, but it still can't bunzip anything14:26
T42<edp_17> Oh, is that something very new device?14:27
zinstackPerhaps it's related to it being new, but I can remember sony amami had that same issue. Can't remember the twrp version though14:28
zinstack@edp_17 Found it, it had twrp 3.2.3-1 and no bzip214:36
T42<edp_17> What is this device?14:43
zinstackThe one that had twrp 3.2.3-1 was sony xperia z1 compact (amami), mine now is motorola moto g7 (river)14:44
T42<edp_17> I see, that really is a new one. :😄 So basically, you manually need to install the bzip2 from the image?14:49
riniguspiggz: pulling in your changes and starting to test14:49
T42<adampigg> rinigus: gr814:49
T42<edp_17> zinstack: And what about if you extract the zip on your pc and manually gzip it?14:50
zinstack@edp_17 I unpack bzip2 on pc and send over the unpacked tarball. It's manual but it works. At least to make it say init-debug in real rootfs for a minute14:51
rinigus@adampigg: meanwhile you could think what should I start  working on. #17 or #18?14:52
piggzrinigus: 18 is proabably a quick win? mainyl code removal?14:53
riniguspiggz: none of them is quick. in 18 we have to keep track on connected client14:54
zinstackInstalling is the least of my problems now. It started bootlooping and now I'm unable to telnet after I merged in hwservicemanager.rc from sony nile. That's a dead end for me, unless somebody knows what to do14:54
rinigusbut I can start there, no problem14:54
piggzrinigus: how do we do that, we dont get any info for that from qtdbus?14:54
T42<edp_17> zinstack: How quickly does it reboot?14:54
riniguspiggz: we should. just have to read the docs.14:55
zinstack@edp_17 it does take a minute, during which it shows up as init-debug in real rootfs. I can't telnet to it though, because it doesn't give out ips for some reason14:56
piggzzinstack: try a fixed ip on your host14:56
T42<elros34> @zinstack: first remove any changes you copied from different device then paste full journalctl. About gzip, maybe it's enough to amend pack_package-droid-updater in droid config, in hybris-boot, and use gzip when creating image with mic14:57
T42<edp_17> zinstack: try to assign an ip and bring up the usb manually. (Write a script that does it for you and at the end you can go in with telnet.) Some info is here:
T42<edp_17> Then once you are in: to stop the continuesly reboot: touch /init_enter_debug214:59
zinstackWell, bootloop stopped, but for what I can see, it's a regression. Systemd no longer starts after that merge, out it goes. After building, i'll report what it says. Thanks all15:07
zinstackSo, here's my journalctl: And dmesg: All I can see is that I need to fix hwservicemanage somehow. Message points to some selinux code, which may be a hint. In the code it obtains an selinux handle, successful, then checks the context and flops. I don't think I should touch that code, as that will be a pain to build and maintain, and, most likely, will15:56
zinstackbe extremely unstable15:56
riniguspiggz: how do you specify spec file when you build in sdk? or you use sb2 from terminal?15:59
riniguspiggz: I am on #1816:08
T42<adampigg> rinigus: i use terminal16:23
T42<adampigg> rinigus: gr8, i am going for icecream and chips while u work :D16:23
T42<kkk_sw> zinstack:
T42<elros34> you are missing hybris 16 specific changes from Also vendor-dsp.mount is incorrect. Do you have /usr/sbin/ohmd?16:48
T42<elros34> zinstack: did you even run
zinstack@elros yes, I did, it wouldn't compile without them, would it?16:53
zinstack@kkk_sw I knew it had something to do with that, but only thing I could find referencing that was an illiterate (both in language and in computers) gentelman being sworn at by another gentelman on this irc with broken links from ages ago. You are my reassurance and saviour16:55
zinstackgentleman* Wow, that's embarrasing16:56
T42<ot_kurva> "Could not run transaction" in buildpackages.sh16:59
T42<elros34> looks like too old submodules17:00
T42<ot_kurva> it hepls. thanks17:15
T42OwL_Is_NooB was added by: OwL_Is_NooB19:04
riniguspiggz: fix for #18 submitted. also PR for gui after I was looking while failed signal and error were not propagated...19:39
riniguspiggz: I think we have to fix #17 before release as well. at least decide how to store FPs and implement it.19:40
rinigusas we don't have multiuser yet, the rest of #17 will be hard to debug19:41
T42<adampigg> rinigus: yeah, im thinking how to even track user sessions .... does systemd emit such things?19:49
rinigus@adampigg: let's not bother with tracking until we get the functionality. its probably somewhere in SFOS beta/alpha codes and can maybe change as well19:50
rinigusbut we have to store FPs correctly already so we will not loose them when the update comes19:50
T42<adampigg> Ok, that should be easy enough19:51
rinigus@adampigg: then #17 is on you? :)19:56
riniguspiggz: I am off for tonight. gn20:25

Generated by 2.17.1 by Marius Gedminas - find it at!