Wednesday, 2022-03-23

T42<edp_17> @elros34 : Good morning. I've set persisten journaling and captured earlier dmesg. journal:
T42<edp_17> logcat:
T42<edp_17> dmesg:
T42<edp_17> Regarding the etc/selinux/ content. I've created the files and symlinks that hadk-faq example shows.07:00
T42<edp_17> So I have these two symlinks:07:01
T42<edp_17> selinux/minimum/contexts/files/file_contexts -> /vendor/etc/selinux/vendor_file_contexts07:02
T42<edp_17> selinux/minimum/policy/policy.30 -> /vendor/etc/selinux/precompiled_sepolicy07:02
T42<edp_17> The rest are a copy from the example (hadk-faq)07:02
T42<elros34> AFAIK they can be symlinks only if you package system otherwise you must copy actual files07:16
T42<edp_17> Okay, I copy them and reboot.07:20
T42<edp_17> Regarding the not found issue. I've found a few suggestions on the channel. I've created a folder /odm/lib and added a symlink to the actual file on device. The issue's gone.07:21
T42<edp_17> Is this related to the issue? : try adding this line to your ld.config.29.txt
T42<elros34> I do not think so07:27
T42<edp_17> @elros34 : On device, I've copied /vendor/etc/selinux/vendor_file_contexts to /etc/selinux/minimum/contexts/files/file_contexts and /vendor/etc/selinux/precompiled_sepolicy to /etc/selinux/minimum/policy/policy.30, but after the reboot it still on sailfish os logo.07:28
T42<elros34> but do you still have same error in logcat?07:29
T42<edp_17> Yes:
T42<elros34> so did you confirm that there is usual: selinux: started in permissive mode or something like that in early dmesg?07:42
T42<elros34> What about that libs which couldn't be copied when building droid-hal?07:50
ThaodanLibs aren't copied the issue is that services can't find the libs from droid-system (/system)07:51
T42<edp_17> I let the droid-hal building fail, then copied them manually, then commented out the copy bit in and re-run droid-hal building. (Then uncommented the copy bit in for the next run.) (re @elros34: What about that libs...)08:15
T42<elros34> are these libs really in rpm package?08:20
T42<edp_17> Unfortunately, I don't know because I couldn't get so early (earlier than what I posted) dmesg. However, I've contacted the developer of the los rom that I use as base and he's confirmed the selinux is set to be permissive. As I am using his rom and kernel, I think selinux is permissive. (Otherwise shouldn't I get the device constantly reboot?) (re @elros34: so did you confirm t...)08:20
T42<edp_17> @elros34 : Are you referring to lib{dl,c,m}.so files?08:21
T42<elros34> yes08:21
T42<edp_17> Which package is that?08:23
T42<edp_17> I have these on device:
T42<elros34> if droid-hal fails then it should be in droid-hal package08:24
T42<edp_17> Let me check.08:25
T42<edp_17> No, they are not in there. (I've checked all droid-hal-*.rpm)08:27
T42<edp_17> I think know why.08:27
T42<edp_17> When droid-hal build failed, I've seen those files were symlinks in the installroot/usr/libexec/droid-hybris/system/lib library.08:28
T42<edp_17> I've removed them and copied the files from /out/soong/.intermediates/art/build/apex/ and WITHOUT commenting out the copy bit in I re-run building droid-hal.08:29
T42<edp_17> It failed again and replaced the copied file with symlinks.08:29
T42<edp_17> So, what I think happened. When I copied the files in and commented out the copy bit and re-run droid-hal, these files were just stripped out and not included into the package.08:30
T42<edp_17> I need to find out why cannot copy these files.08:30
T42<elros34> definitely. See even mce (I guess some plugin from it) fails because of missing libc.so08:31
T42<edp_17> On device I have all those three files in /usr/libexec/droid-hybris/system/lib, but all of them symlinks:
T42<edp_17> I copy them over from pc to see whether it fixes the issue.08:33
T42<edp_17> I copied the files from pc to devive and rebooted. Same error in logcat but something's changed as the sailfish os logo gets dimmer after a few seconds :
T42<edp_17> "" not found08:41
T42<edp_17> Okay, seemingly I need to symlink these three ( into /odm/lib08:42
T42<edp_17> After symlinking these (, and into /odm/lib, they are not reporting errors anymore. However, the originial one 'SELinux: Failed to acquire service_manager context. Aborting.' is still there.09:10
*** phlixi is now known as Guest13712:33
T42<elros34> @edp_17 what is the output of getenforce command?18:14

Generated by 2.17.1 by Marius Gedminas - find it at!