Tuesday, 2021-09-14

rinigusmal: thank you very much for looking into it!03:48
riniguspiggz: fingers crossed03:49
T42_<adampigg> https://irc.thaodan.de/.imgstore/2b0bc74c/file_2651.jpg09:05
T42_<adampigg> https://irc.thaodan.de/.imgstore/27ac09fe/file_2652.jpg09:06
piggzrinigus: guess i have some debugging to do09:09
T42_<b100dian> You do have telnet hopefully:)09:09
piggznope, not on lvm volume09:09
piggzSep 14 12:24:27 VollaPhone sailfish-device-encryption-community-wizard[883]: DevEnc::Dev:227: Failed to activate device. Device: /dev/sailfish/home_open09:25
piggzSep 14 12:24:27 VollaPhone sailfish-device-encryption-community-wizard[883]: DevEnc::Dev:132: Failed to encrypt and format device. Device: /dev/sailfish/home_open09:25
T42_<edp_17> Hi all! Can I build with tooling&target or there will be available version for both?10:10
piggzim sue lbt will have 4.2 targets avaialble by lunch time ;)10:11
T42_<edp_17> @adampigg : Good news! I'll wait then. Thanks! 👍10:13
T42_<edp_17> Another question. 😊 Building 4.1 I needed to use a specific commit of droidmedia, gst-droid and gmp-droid. Do I need to use the same for building 4.2 or I can use the latest from each?10:15
piggzim sure there should be a voting process where the community can dictate jolla's immediate priorities10:19
riniguspiggz: sorry for delay - was afk. have you checked that you have device /dev/sailfish/home_open?10:55
piggzrinigus: yes, also found this....10:55
riniguspiggz: can you check /etc/fstab on whether you have /home mount there?10:57
rinigusI wonder if it was mounted when accessed by wizard10:58
piggzrinigus: i dont10:58
riniguspiggz: `df -h` ?10:58
rinigusls -l /dev/sailfish10:59
rinigusand let's check also home_open size with lvm. maybe it was not resized10:59
riniguslvdisplay, I think10:59
rinigusI have a meeting in 0 minutes, will be back as soon as I can - maybe 1h? sorry11:00
riniguspiggz: ^11:00
piggzrinigus: np :)11:01
T42_<elros34> @edp_17 most likely you can use IIRC gmp-droid should be 0.2 and other packages also can't be latest. For gst-droid I used https://github.com/sailfishos/gst-droid/commits/upgrade-4.2.0 without latest commit which breaks video recording for me11:59
T42_<elros34> for droidmedia I think 9450a66a133ffa4df4af5f1d2af5b09ff794606d12:01
T42_<edp_17> I have used these:12:01
T42_<edp_17> droidmedia -  9450a66a133ffa4df4af5f1d2af5b09ff794606d12:01
T42_<edp_17> gst-droid -  364c13e3f6b3d99a87b58beb526bd13f377ce6f412:01
T42_<edp_17> gmp-droid -  b61b740987a9880fccf5401220644c7dcf184be212:01
T42_<edp_17> for building 4.112:02
T42_<adampigg> i think for 4.2, you dont need to package gst-droid/gmp-droid because there is a new common repo which contains droidmedia-devel .... however, there was an issue with aarch64, so i think for that arch you have to wait until 4.3 for the benefit ... mal can confirm12:02
T42_<elros34> @adampigg where do you see such a repo, I have and I do not see droidmedia-devel when searching via zypper12:08
mal@adampigg what issue?12:10
T42_<adampigg> mal: no issue ... was just mentioning the new common repo for the media stuff12:11
mal@adampigg not sure what you meant with "there was an issue with aarch64"12:13
T42_<adampigg> mal: you gave me the link, where aarch64 didnt make it to 4.212:13
T42_<adampigg> i think!12:13
malno idea what you are talking about :)12:14
T42_<adampigg> *sigh* searching logs! :D12:14
T42_<adampigg> mal: https://github.com/mer-hybris/community-adaptation/pull/4/files12:15
T42_<edp_17> Does somebody know when we can start building 4.2 on OBS?12:21
piggz@edp_17 keep calm an wait on lbt :)12:23
T42_<edp_17> Okay 😊12:23
T42_<edp_17> I didn't mean to urge, just asked. 😊12:24
T42_<elros34> usually after particular sfos version is released, 4.2.0. is still in EA12:27
T42_<edp_17> Oh, I though with the the EA is over. I though the EA is always the first version of of an upgrade (like and thought the following update is the final (like
malI have the new adaptation-common repo in
T42_<adampigg> mal: i just searched that repo, and it doesnt have the media stuff in it ... is that correct? is that changing?12:37
T42_<XAP2P> When ban? (re @💝💝💝 ГPUППA_ZНAК0MCTV_18+: )12:41
mal@adampigg then what does it have?12:42
T42_<adampigg> https://irc.thaodan.de/.imgstore/95ce9f73/file_2658.jpg12:42
T42_<adampigg> mal: ^^12:43
mal@adampigg now I remember, droidmedia and friends only appear there after next release12:53
T42_<adampigg> ok12:53
malother stuff is there already12:53
T42_<adampigg> so, @elros34 i was a release early :)12:54
riniguspiggz: this all looks as it should be. can you paste devices.ini?13:01
rinigusthis one is fine as well. hmm13:03
riniguspiggz: if you reboot, I expect that you will be asked to setup the device again. would you mind testing without encryption?13:05
rinigusI presume you exited wizard through development Quit button13:06
rinigusI start to wonder whether cryptsetup is installed ... but let's see if it works without encryption13:07
piggzrinigus: also found this Sep 14 16:05:51 VollaPhone sailfish-device-encryption-community-wizard[916]: device-mapper: reload ioctl on   failed: Operation not permitted13:07
riniguspiggz: that I will have to check at home and see whether I have something like it on dev device13:08
piggzSep 14 16:05:51 VollaPhone kernel:  (7)[916:sailfish-device][dm-crypt] dev path: /dev/sailfish/home_open, type: -113:08
piggzSep 14 16:05:51 VollaPhone kernel:  (7)[916:sailfish-device][dm-crypt] dev path: /dev/sailfish/home_open, type: -113:08
piggzSep 14 16:05:51 VollaPhone kernel:  (7)[916:sailfish-device]device-mapper: table: 253:2: crypt: Unknown error13:08
piggzSep 14 16:05:51 VollaPhone kernel:  (7)[916:sailfish-device]device-mapper: ioctl: error adding target to table13:08
piggzrinigus: i should point out, i was also unable to get stock encryption working on  this device :)13:10
piggzmaybe some weird kernel bug?13:10
riniguspiggz: you have this strange error in the beginning of https://paste.mozilla.org/8AsNyksA13:10
rinigusmaybe there is some delay before LVM volumes get recognized properly?13:10
riniguspiggz: cryptsetup should be there though - its required by the main package13:12
riniguslet's see if non-encrypted version will work13:12
piggzrinigus:  i posted to dm-crypt ML ages ago about cryptsetup nt working on this device13:13
piggzdidnt get very far ... you can imiagine how much sympathy a vendor kernel gets13:13
riniguspiggz: you mean that cryptsetup command doesn't work at all on volla?13:14
piggzrinigus: one moment, the ML wesite is down, searching mail13:14
piggzrinigus: this is the post ... it was using the older android 9 port , this is 10 https://paste.mozilla.org/sZYr5VWs13:16
piggzrinigus: non-encrypt worked ok13:16
riniguspiggz: ... reading your email ...13:17
T42_<TheVancedGamer> Now but my client doesn't support bans (re @XAP2P: When ban?)13:19
riniguspiggz: looks like the same we have in our case.13:20
piggzit does13:20
riniguson device, if you now unmount /home and try to run that cryptsetup luksFormat /dev/sailfish/home_open - would that fail the same way?13:21
T42_<adampigg> i suppose i should stop user session if i can!13:22
rinigusthen you can reset settings by removing /etc/sailfish-device-encryption/config.ini and removing home.mount from /etc/systems/system.13:22
rinigusif you remove or rename devices.ini it will boot without /home mounted and wizard bothering you13:23
riniguspiggz: ^13:23
piggzrinigus: errr, no, it seeme to work!13:23
riniguspiggz: "it"?13:24
piggzwhats command to mount?13:25
riniguspiggz: luksOpen makes it available as device via mapper13:26
rinigusnice that it works, btw!13:26
rinigusafter luksOpen your would have to format it as ext4 and then mount13:26
piggzrinigus: ah, but the open failed13:27
piggz[root@VollaPhone ]# cryptsetup luksOpen /dev/sailfish/home_open home_open13:28
piggzEnter passphrase for /dev/sailfish/home_open:13:28
piggzNo key available with this passphrase.13:28
piggzEnter passphrase for /dev/sailfish/home_open:13:28
piggzdevice-mapper: reload ioctl on   failed: Operation not permitted13:28
piggzwrong passwd first13:28
riniguspiggz: but have you had home unmounted?13:28
piggzyes, it was unmounted13:28
riniguscommand is cryptsetup luksOpen /dev/sailfish/home_open home_encrypted13:29
rinigusyou need to have different mapper name13:29
piggzin other terminal it shows13:30
piggz[  815.026278]  (7)[3901:cryptsetup][dm-crypt] dev path: /dev/sailfish/home_open, type: -113:30
piggz[  815.026326]  (7)[3901:cryptsetup][dm-crypt] dev path: /dev/sailfish/home_open, type: -113:31
piggz[  815.026346]  (7)[3901:cryptsetup]device-mapper: table: 253:2: crypt: Unknown error13:31
piggz[  815.026363]  (7)[3901:cryptsetup]device-mapper: ioctl: error adding target to table13:31
riniguspiggz: this is quite bad. no idea and indeed, looks like something is wrong on kernel/driver side13:32
rinigusI wonder what this error type: -1 means13:32
rinigusor that next line. with type: -1 I guess I can check at home and see if I get the same13:37
piggzrinigus: does android use basically the same method for its encryption?13:39
piggzalso, what encryption method is used?13:39
riniguspiggz: https://source.android.com/security/encryption/full-disk#how_android_encryption_works13:40
riniguspiggz: does encryption work on volla android?13:42
piggzrinigus: i dont know .... i presume so, as i have to format /data to install on it13:43
T42_<eriki73> piggz: are you using the same encryption algorithm on SFOS compared to Android?13:44
riniguspiggz: do you have recovery working on volla? so, if you install and encrypt on android, would you be able to check out what is /data?13:44
T42_<adampigg> @eriki73 algo is https://paste.mozilla.org/s8LiBsP213:45
T42_<eriki73> @adampigg , try aes-cbc-essiv:sha25613:46
T42_<eriki73> That is what Android claims to be using...13:47
T42_<eriki73> In Android docs...13:47
piggzsame https://paste.mozilla.org/JPanLah013:50
piggz@eriki73 do you have a working v10 install to check there?13:50
T42_<eriki73> piggz: No, I am daily-driving my Volla on Droidian.13:51
piggznot sfos 4.1???13:51
rinigus@eriki73: with cryptsetup?13:51
T42_<eriki73> rinigus: it is not encrypted.13:52
piggz@eriki73 you could try creating a file though13:52
T42_<eriki73> piggz: a file?13:53
rinigusyes, file would work fine for testing13:53
riniguscreate sparse file and then format that with luksFormat13:53
piggzmake it big enough to be your ~, then mount it and secure your data :D13:54
riniguspiggz: I guess for you file fails the same way, right?13:55
piggzrinigus: yes, same error13:57
riniguspiggz: android it is then :) . assuming that you can somehow pull android encrypted data from the phone... is there some kind of dump that let's you copy it as an image?13:59
riniguspiggz: any other device where encryption is known to work?14:01
piggzrinigus: pro1 works using stock....14:01
piggznot sure I want to force everyone to reflash for communitty14:01
riniguspiggz: https://forums.ubports.com/topic/6076/device-mapper-crypto-not-working-on-volla-phone/214:12
piggznice find14:14
rinigussounds like you need to patch kernel and add "sailfish" to the list... or try to get rid of these "acceleration" hacks14:14
T42_<adampigg> @NotKit ^^^ as ubports maintainer, thoughts?14:15
piggzrinigus: at least maintainer is here :)14:16
T42_<NotKit> first time I see this myself, so no idea, but could just modify it to treat unrecognized storage as external storage14:20
T42_<NotKit> so int type = 1; by default14:20
piggzyeah, i see a kernel mod coming :)14:22
T42_<eriki73> When I saw the error, I was thinking that it looks like there is some MediaTek coding quality in the kernel. I think I was correct...14:29
T42_<adampigg> rinigus: @NotKit @eriki73 https://paste.mozilla.org/RZ9YYujZ15:28
piggzrinigus: can i reset everything so the wizard starts again?15:30
riniguspiggz: yes. remove config.ini in /etc/sailfish-device-encryption . I think that is sufficient16:04
rinigusif something fails, let's remove /etc/systemd/system/home.mount . but it should be done automatically by wizard16:05
piggzit worked16:07
riniguspiggz: regarding reset - we can later discuss whether it should be in GUI. I have a scenario where it can happen by accident with a kid holding your phone16:07
piggzrinigus: should we offer different algorithms?16:10
riniguspiggz: for encryption? not sure. gentoo howto had a statement similar to don't touch algos unless you really know what you do16:21
piggzrinigus: ok, lets leave that idea for now16:41
piggzrinigus: anything i can test for you?17:10
piggzrinigus: found an odd bug17:12
riniguspiggz : impossible! Should be no bugs...17:16
piggzi set password to qwertyuiop17:17
piggzi can see on the keyboard that it is detecting all the keypresses17:17
piggzbut, it nearly always misses off the last p17:17
piggzbut i can see on the keyboard it is pressed17:17
riniguspiggz that's this keyboard on device boot, right? I wonder whether some other signal has to be used.. currently it's onclicked17:20
piggzrinigus: yes, the password entry keyboard17:21
piggzrinigus: i think its all the edge keys17:22
piggzeg, 1q0p that are worst17:22
riniguspiggz  as we can see them fine, would probably handle onpressed then...17:27
piggzrinigus: you want a PR or have you got it covered?17:36
riniguspiggz: PR would be wonderful. especially a tested one - then I can continue with hwcrypt :)17:37
rinigusits the same keyboard in wizard and ask password - 2 PRs?17:38
itexhello guys, I am still struggling to get the local manifest file working, I have used the right version of cm like written on the lineage wiki and used the right depo but it fails to find them when i try to repo sync https://www.3hg.fr/CHATONS/Pastebin/?21ade830ab9f9cd2#55GuKvdHfCrSjWrHCwfAS5omYsBUhtzgMWSWSxUirmoM17:41
itexI don't know where my problem is17:41
piggzrinigus: something weird on my device tooo....17:51
piggzafter unlock, boot continues17:51
piggzlipstick shows up, but seems to stutter at start...17:52
piggzbut, main thing17:52
piggzbacklight doesnt turn off when i press power to off the screen17:52
riniguspiggz: if you can - check whether systemd-ask-password-gui is running. service should be OK, but process should be killed17:53
rinigusand anything else odd in systemctl status? any odd services hanging?17:53
riniguspiggz: I also had to add https://github.com/sailfishos-sony-tama/droid-config-sony-tama-pie/blob/hybris-10/sparse/etc/systemd/system/systemd-ask-password-gui-stop.service.d/50-vendor-hwcomposer-2-3.conf17:54
T42_<A_T_R> Your branch is cm-14.117:55
T42_<A_T_R> not "stable/cm-14.1" (re @SailfishFreenodeIRCBridgeBot: <itex>hello guys, I ...)17:55
piggzrinigus: only the tty ask passwd is running17:56
T42_<A_T_R> @itex - set revision="cm-14.1"17:56
riniguspiggz: good. now question is whether that hwcomposer restart is needed for you as well17:57
rinigusI can see in your github sources that one is missing17:58
itexI think it worked thanks A_T_R18:01
piggzrinigus: grrrr, i cant get the backlight off!18:33
riniguspiggz: even after that hwcomposer restart?18:34
piggzrinigus: found something18:37
riniguspiggz: was just going to type that I have no idea18:37
piggzrinigus: /sys/class/leds/18:37
piggzcontains lcd-backlight/brightness18:38
piggzechoinf 0/255 into that does nothing18:38
piggzalso has mt6370_pmu_bled/brightness18:38
piggzechoing into that works as expected18:38
piggzso, must be a config problem18:38
piggzbut, i dont know whyu ive just noticed it18:38
riniguspiggz: but has it worked before?18:38
piggzim _sure_ it worke before18:39
piggzthought, the lvm build, which is new, does have that brighness config in it, which is wrong in my case18:39
riniguspiggz: it could be that the boot sequence is somewhat altered as well. as encryption depends on some android bits (in getting ready to hwcrypt as well as hwcomposer). so, in theory, some services could start earlier than before now18:40
rinigusbut it could be error in config that got triggered somehow now18:41
piggzrinigus: i think its a config issue, added 99-backlight.ini with correct path, it seems fine19:06
piggznow, back to fixing keyboard19:06
piggzrinigus: what line endings do you have on that file?19:22
riniguspiggz: ******** no idea why crlf sneaked in. feel free to change to unix19:23
piggzmy git diff was showing ^M ... which got me wondering :)19:24
riniguspiggz: thanks!19:39
rinigusdid it help?19:39
piggzrinigus: yes, it fixed it for me19:41
riniguspiggz: excellent! now same for wizard?19:43
riniguspiggz: updates required for hwcrypt are all in. we can now create hw backed key from settings GUI and use it during a boot19:56
rinigusyou would have to update hwcrypt and 3 other packages (see what's landed today). assuming that systemd-ask-password is updated already with your fix19:58
rinigusclosing hwcrypt issue - open a new one if it fails for you :)19:59
piggzok ...20:00
piggzbug confirmed in wizard20:00
riniguspiggz: new bug? or something with keyboard?20:02
rinigusI'll be off till tomorrow (+2h) ... if new, maybe should get that at github20:03
piggzrinigus: same kb bug20:03
riniguspiggz: great - then you have the fix :)20:04
itexif i use lineage os manifets I cannot use others from non lineage os? "breakfast $DEVICE" asks me for some repos but the ones from lineageos don't seem to work https://www.3hg.fr/CHATONS/Pastebin/?041c15af56f887ce#3U51HzRWgUaEne2NTUuim85XX2JK9AV6o5epxHLospi420:30
Ketoand seems it came back online...20:54
T42_<XAP2P> Google translator xD (re @SailfishFreenodeIRCBridgeBot: <Keto>PSA: the sailb...)21:28
T42_<edp_17> Good evening all! I need a little help. SFOS, treltexx, CM14.1 base, device stays on the yamui splash screen because lipstick doesn't start. Journal: https://paste.ubuntu.com/p/sPBVXNMqND/21:54
T42_<edp_17> I've updated tooling&target to and all three submodules.21:55
T42_<edp_17> Can you help to find out what is causing the issue, please?21:56
T42_<edp_17> Oh, the initial setup couldn't run, therefore the device is only accessible with telnet.21:57

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!