Monday, 2021-08-02

T42<max_simon7> :
T42<edp_17> mal: When trying to build firejail for aarch64, getting this error:
T42<edp_17> It has built fine for armv7hl. Do you know what to fix? Thanks.10:08
T42<edp_17> Should I remove *.o from hybris/mw/firejail/upstream/src/fseccom?10:12
T42<birdzhang> git clean -x -f -d10:16
T42<edp_17> Oh, I forgot that. Thanks!10:18
rinigusAre we supposed to build firejail for ported devices?10:19
piggzrinigus: not as far as i know11:16
piggzat least i havnt had to11:17
piggzthough, i have had to add to the rules11:17
riniguspiggz: great! haven't adjusted rules for tama either - so far so good...12:23
T42<edp_17> I am getting erros when building packages for aarch64. Tried to install automake but didn't help:
mal@edp_17 why are you building that? run git clean again in the sources to remove any old built stuff, many packages could have issues if you have built those for other arch and git clean could be needed12:41
mal@edp_17 have you verified target has correct local repo?12:42
T42<edp_17> mal: I did git clean but got the same issue. Then I deleted and cloned the package and tried to build. It failed with the same error.12:53
T42<edp_17> mal: Yes, I have downloaded target aarch64. (Now I have both targets samsung-treltexx-aarch64 and samsung-treltexx-armv7hl in mer/targets)12:54
T42<edp_17> I have did a 'git clean -x -f -d' in each folder within hybris/mw then tried to rebuild all packages with 'rpm/dhd/helpers/ -o -n' but it didn't do anything.13:01
T42<edp_17> Is it not possible to rebuild all packages offiline while keeping the existing .rpms with the -n switch?13:01
T42<edp_17> I have started to build all packages with 'rpm/dhd/helpers/ -o' and got this error:
T42<edp_17> mal: ^^ Any idea about this?13:17
mal@edp_17 did you reclone libhybris repo? or run git clean -x -f -d in the submodule folder?13:53
T42<edp_17> mal: I just run the 'git clean -x -f -d' in the submodule folder.13:55
T42<edp_17> mal: I just deleted libhybris, re-cloned and it built successfully.14:21
T42<edp_17> @elros34 , mal: I am getting a weird issue on the device. Here is the log:
T42<edp_17> How it happened:14:36
T42<edp_17> 1. I backed up an existing, working sfos4.014:36
T42<edp_17> 2. in TWRP, I wiped then installed sfos4.1 that had the yamuisplash included.14:37
mal@edp_17 have you installed any custom packages?14:37
T42<edp_17> mal: No. I just restored a backup.14:38
T42<edp_17> 3. booted into 4.1, then went back to TWRP, wiped, then restored the saved 4.014:38
T42<edp_17> 4. when 4.0 is booting up, it still displays the yamui splash screen, and only gives me a white screen and that error is in the log: HomeApplication: Errors while loading compositor from "file:///usr/share/lipstick-jolla-home-qt5/compositor.qml"14:39
T42<edp_17> It is odd because thought at restoring a backup it would overwrite all stuff.14:40
T42<edp_17> mal: Regarding your question about any custom packages. I installed Elros' compositor that displays a cursor when I attach a mouse. Could that be the problem?14:42
T42<edp_17> That package is called mousetracker.14:44
malhmm, what is that compositor?14:44
malyou can see the messages about symbol HwcImage in the error log which suggest some package version mismatch14:45
T42<edp_17> This is the package I was referring to:
T42<edp_17> mal: How is it posible that I have a package missmatch if this is a restored backup?14:47
malno idea14:48
T42<edp_17> I thought would re-install lipstick, but there is no internet on the device and I cannot turn wifi on as it displays a white screen only. 😔14:50
maldoes just rfkill unblock for the wifi enable it?14:53
T42<edp_17> mal: Nope, because the wifi probably requires to enter the password.14:56
malyeah, if you have screen lock enabled14:58
T42<edp_17> mal: yep. What is interesting that I restored and booted into this backup successfully before I tried the latest 4.1 build.15:01
T42<edp_17> I only included this yamui thing into the latest one.15:01
malso you did some changes compared to the backup?15:08
T42<edp_17> mal: Yes, the backup is a sfos 4.0 and the other one I tried on the device was 4.1.15:11
T42<edp_17> Is this how you meant changes?15:12
malI really am confused what you are saying15:12
malwhat did you mean by this "I only included this yamui thing into the latest one"15:13
T42<edp_17> mal: I built sfos4.1 with that yamui thing in it. This is how I meant.15:21
malyou are saying the same backup worked before? or other backups worked before?15:22
T42<edp_17> Yes, this backup workd before.15:22
T42<edp_17> I've built a few sfos 4.1 version, and before the latest one, that yamui was not included into any builds. When I tried those 4.1 builds on the device and then restored the saved 4.0 from the same backup, it always booted up and worked.15:25
malhave you tried restoring the backup again15:31
T42<edp_17> mal: Do you mean, wipe and restore, or just restore over the existing system?15:33
T42<edp_17> When building droid-hal-version-$DEVICE (aarch64) it is complaining about missing:
T42<edp_17> How can I get it? (I didn't have this issue when building armv7hl.) Thanks.15:36
maldo you have some binary stuff in config repo15:39
T42<edp_17> mal: Oh, yes. I've compiled evtest and put it into sparse/usr/bin/droid. I remove it and retry. Thanks!15:47
T42<edp_17> mal: I needed to remove those bynaries and now droid-hal-version-$DEVICE (aarch64) has built successfully. Thanks!15:55
T42<elros34> @edp_17 I have removed that qxcompositor package you linked so you do not use old outdated package build for 3.3.0 sfos.16:20
T42<edp_17> @elros34 : I am not even sure that is even installed on the device. If that was not built for 4.0, then it is definitely not installed on there. I just remembered that played with that in the past and thought that could be the reason of that behaviour.16:29
T42<elros34> remember that whatever package you installed, everything else was also updated!16:31
T42<elros34> assuming you used gui/pkcon16:32
T42<elros34> so if you use devel repo on 4.0 then you could easily upgrade droid, libhybris and other packages without noticing it16:44
T42<edp_17> Thanks.16:58
T42<edp_17> I've got this error again:
T42<edp_17> I thought when I removed the armv7hl binaries from sparse, this error would be gone.16:59
mal@edp_17 that is in broadcom-bluetooth-bluez5 package, i.e.
maldid you clean that also18:01
T42<edp_17> mal: Yes I did. And then manually rebuilt for aarch64. I'll try to clone it then retry.18:36
T42<edp_17> mal: I've managed to restore that backup. Needed to format /sysyem, data and all partitions except external sd. But finally it works.18:37

Generated by 2.17.1 by Marius Gedminas - find it at!