Monday, 2026-06-01

malnightishaman: did you check which packages have been installed, zypper se droid-hal should also tell00:09
nightishamanim rebooting into system now00:11
nightishamanim gonna check00:11
nightishamanmal: okay droid-hal is updated00:37
nightishamanmal: MEMCG_V1 doesnt exist according to menuconfig00:48
malhmm01:11
malnightishaman: which kernel version does it have?01:11
T42<elros34> @the_hiktor stupid question how did you mount your vendor? It's on super partition. Can you paste all commands together with diff -s /etc/selinux/minimum/policy/policy.30 /vendor/etc/selinux/precompiled_sepolicy and similar for file_contexts. BTW have you tried previous suggestions: commandline chnages, yama in config?02:57
T42<the_hiktor> Yah... I Didn't bother to use commands I was on recovery so went to mount setting and clicked everything 😅03:29
T42<the_hiktor> Gimme sometime I'll try to run that03:30
T42<the_hiktor> Changes are made but i didn't build yet03:31
T42<adampigg> mal: for 5.1, does naything need updated for gps? csd is saying failed state07:19
T42<adampigg> Looks important: Jun 01 08:57:30 Quintus geoclue-hybris[40421]: [W] unknown:0 - GNSS set position mode failed08:04
T42<adampigg> from: https://github.com/mer-hybris/geoclue-providers-hybris/blame/8c18368c5580e6d6f8a243aa8ffedad4b716bec2/binder/binderlocationbackend_hidl.cpp#L93208:09
T42<adampigg> issue is this, needs setting toggled https://github.com/sailfishos/nemo-qml-plugin-systemsettings/pull/5410:37
T42<the_hiktor> @elros34 Files /etc/selinux/minimum/policy/policy.30 and /mnt/vendor/etc/selinux/precompiled_sepolicy are identical13:06
T42<the_hiktor> im gonna build and try with new changes13:07
T42<the_hiktor> oh and there's config file under selinux dir in droid-configs am i supposed to do an changes or leave it as is13:12
T42<the_hiktor> this what it contains13:12
T42<the_hiktor> SELINUX=permissive13:12
T42<the_hiktor> SELINUXTYPE=minimum13:12
T42<the_hiktor> AUTORELABEL=113:12
malthat should be always the same13:18
T42<the_hiktor> dbus_contexts under selinux/minimum/contexts should be also the same ?13:20
malwhat?13:23
malyes13:23
malonly the symlinks should be replaced13:23
T42<the_hiktor> ok ill build then13:24
T42<the_hiktor> dmesg14:56
T42<the_hiktor> https://paste.opensuse.org/pastes/2639a407ca7e14:56
T42<the_hiktor> nothing changed🙁14:56
T42<the_hiktor> i didnt get selinux policy from annother device🫤14:58
T42<the_hiktor> until someone confirm from where should i get it14:59
T42<elros34> did you change anything? Why don't you provide full dmesg so it's clear whether you have any changes or not15:38
T42<the_hiktor> Yeah disabled CONFIG_SECURITY_YAMA and added android boot.selinux=permissive to kernel commandline16:24
T42<the_hiktor> https://paste.opensuse.org/pastes/a0607edad71616:27
T42<the_hiktor> the same dmesg16:27
T42<the_hiktor> but full16:27
T42<elros34> what about removing audit=0?16:36
T42<the_hiktor> mal said not to but if I should I'll do it16:36
T42<nightishaman> mal: Kernel version is 6.117:31
malyeah, that doesn't have MEMCG_V1 option17:43
mal@elros_34 I wonder why that /sys/fs/cgroup/memory is missing17:44
T42<the_hiktor> full dmesg audit disabled18:31
T42<the_hiktor> https://paste.opensuse.org/pastes/55d80f39732e18:31
T42<elros34> do you use 18.1-20210114-UNOFFICIAL-surya? Have you tested it?19:06
T42<the_hiktor> Los ? (re @elros34: do you use 18.1-2021...)19:07
T42<elros34> yeah19:09
T42<the_hiktor> It's by the same maintainer afaik19:09
T42<the_hiktor> I'm using official19:09
T42<the_hiktor> But I remember trying an unofficial build maybe it's the one you're referring to19:11
T42<the_hiktor> It didn't boot at all19:11
T42<the_hiktor> Idk why though19:12
T42<elros34> you should try that 18.1-20210114-UNOFFICIAL-surya, it must be working because previous porter was using it and got different selinux policy file which works19:13
T42<the_hiktor> Can't we just get another selinux policy file and try it19:14
T42<the_hiktor> Instead of changing flash base19:14
T42<the_hiktor> It's the same dev anyways19:15
T42<elros34> you may try19:17
T42<elros34> but the fact 18.1-20210114-UNOFFICIAL-surya doesn't work for you suggest you have something wrong , maybe some other partition19:19
T42<the_hiktor> I remember it shows nothing wrong in logs or in recovery but it does bootloop at some point before boot animation19:20
T42<the_hiktor> At that time tried many recoveries19:20
T42<the_hiktor> And many firmwares but nothing changed19:21
T42<the_hiktor> Wdym by other partition ?19:23
T42<elros34> not sure, android use gazillion partitions but lineage flash only few, without log this is just guess game19:27
T42<the_hiktor> Can I try sepolicy file from stock ?19:31
T42<the_hiktor> Or it's a bad idea19:31
T42<elros34> try from "that lineage" version or from stock or.., what bad can happen?19:33
T42<elros34> why you don't want to use know to be working policy file tested by porter for excatly same device?19:34
T42<the_hiktor> Idk like some panic attack 😂19:34
T42<the_hiktor> Cuz I had that build19:35
T42<the_hiktor> And I removed it19:35
T42<the_hiktor> After making me go crazy19:35
T42<the_hiktor> It was asome kind of  hassle to get it19:35
T42<the_hiktor> Cuz it's old now19:35
T42<elros34> clone old droid-config-surya repo, adb push that policy, reboot don, it's really not hard19:35
T42<the_hiktor> https://paste.opensuse.org/pastes/bc31d8bac96520:00
T42<the_hiktor> dev-binderfs.mount now fails20:03
T42<elros34> nothing really changed, log from wokring port: https://pastebin.com/raw/KcFHBA2v20:10
T42<the_hiktor> Dude I'm down very deep 😭20:12
T42<the_hiktor> This is an absolute bs20:12
nightishamanmal: i think this is the problem: /sys/fs/cgroup # cat /proc/cmdline | tr ' ' '\n' | grep -iE 'cgroup'20:37
nightishamancgroup_disable=pressure20:37
nightishamancgroup_disable=memory20:37
nightishamancgroup.memory=nokmem20:37
T42<the_hiktor> @elros34 trying different vendor blobs helps in this case ?21:15
malnightishaman: where do those disable entries come from? some boardconfig, if so then remove the memory one21:17
nightishamanmal: It was in BoardConfig-common.mk where the boot command is. I removed it. Systemd-tmpfiles doesnt fail anymore, policies setup still fails21:26
malhow does policies setup fail?21:26
nightishamanhttps://paste.ubuntu.com/p/NhBzvP6Pqb/21:27
malok, so maybe because usb moded is masked, we can ignore that probably for now21:31
malhopefully21:31
nightishamanwell lipstick still doesnt start21:33
nightishamanis there a way i can access the logs for lipstick and pulseaudio?21:55

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