Friday, 2022-04-22

T42<elros34> "execv('/system/bin/logd') -> no such file or directory" should give you some idea06:31
T42<leha155> @elros34 But i have this files. What is causing this error?08:31
T42<leha155> ls -al /system/bin
T42<leha155> I add minimum config
T42<leha155> `maybe i'm missing something?` (re @SailfishFreenodeIRCBridgeBot: <mal>do you have pro...)08:34
voidanix[m]@leha155: try setting SELINUX=disabled instead of permissive in /etc/selinux/config and see if it gets any further09:56
T42<leha155> it doesn't change for me. (re @SailfishFreenodeIRCBridgeBot: <voidanix[m]>@leha15...)11:27
T42<leha155> I also tried disabling selinux via cmdline, but that also didn't work.11:32
piggzmal: reminder to log bug against lipstick for currentl mesa version :)12:28
T42<RoseJGresham> Forwarded from Rose J. Gresham: *Hey!! I'm still in shock and so happy over withdrawal of $36,000 Bitcoins I came across a testimony referring me to Mr Mark Hutchinson and I must admit, I was skeptical at first, but now, withdrawing this much profit is something I couldn't imagine. I'm grateful to be testifying of the good work of Mr Mark Hutchinson he's truly a God sent. He's the real deal guys! Connect with him via the link be14:42
T42<RoseJGresham> 👇👇👇👇👇👇👇14:42
T42<RoseJGresham> ***14:42
T42<elros34> @leha155 so that should lead you to check what linker is used via: 'file /system/bin/logd'17:52
T42<nephros> CONFIG_SECURITY_SELINUX_BOOTPARAM=y is set righz?20:37
T42<nephros> Just to rule ouz the more or less obvious. (re @leha155: I also tried disabli...)20:37
T42<leha155> @nephros Yes I have21:14
T42<elros34> value=1 is pointless, you use it to disable selinux =0. Usually it's enabled unless you change something21:16
T42<leha155> Ok, I del this paramert. And i use selinux =1 in my cmdline21:19
T42<elros34> it's also irrelevant:) I think that advice was added to faq only because on older hybris bases selinux was supposed to be disabled selinux=021:22
T42<leha155> @elros34 `and can you elaborate on"`what linker is used via: file /system (tg://bot_command?command=system)/bin (tg://bot_command?command=bin)/logd (tg://bot_command?command=logd)`" ?`21:51
T42<elros34> did you run that command?21:52
T42<leha155> / # file /system/bin/logd21:57
T42<leha155> /system/bin/logd: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /system/bin/linker64, BuildID[md5/uuid]=cb8696687552ad7b45e1914202d4b11c, stripped21:57
T42<elros34> so you can see its "/system/bin/linker64" now check whether it is valid (it's symlink)21:58
T42<leha155> / # ls -al /system/bin/linker*21:59
T42<leha155> lrwxr-xr-x    1 root     shell           36 Jan  1  2009 /system/bin/linker -> /apex/
T42<leha155> lrwxr-xr-x    1 root     shell           38 Jan  1  2009 /system/bin/linker64 -> /apex/
T42<leha155> lrwxr-xr-x    1 root     shell           36 Jan  1  2009 /system/bin/linker_asan -> /apex/
T42<leha155> lrwxr-xr-x    1 root     shell           38 Jan  1  2009 /system/bin/linker_asan64 -> /apex/
T42<elros34> you showed it already previously, check whether symlinks are valid (/apex/ really is exits)22:00
T42<leha155> /apex in empy now, becouse droid-hal-init is masked and apexd dont run22:05
T42<leha155> `it turns out that apex is not mounted at startup `droid-hal-init` time and `linker (tg://bot_command?command=linker) `is a reference to empty space`22:07
T42<leha155> ?22:07
T42<elros34> how do you know it's not mounted?22:09
T42<leha155> these are my guesses, `and plus I don't see this information in the log`22:21
T42<leha155> is there a way to check this?22:21
T42<elros34> good question. For now you have few services in *.rc with "reboot_on_failure" which cause yours device reboot (and starting some unwanted services). So maybe one way could be get rid of this reboot on failure. Other idea could be adding some 'wait <path> [ <timeout> ]' after apex starts?22:25
T42<elros34> just to be sure: are you sure that you used correct android_version_major before building packages?22:29
T42<leha155> yes
T42<leha155> I comented all "reboot_on_failure" in my rc file and `loading is a bit slower now`22:44
T42<elros34> so you do not have starting ueventd now? If it's starts then either there are still some services with it or something else cause shutdown. You could also get rid of  "shutdown critical"22:47
T42<leha155> `unfortunately`22:50
T42<leha155>  "ueventd: ueventd started!"22:50
T42<elros34> If I uderstand docs correctly it's started when shutdown  starts and because it contains "shutdown critical"22:51

Generated by 2.17.1 by Marius Gedminas - find it at!