Sunday, 2020-05-03

OksanaGoing mildly insane. After several zypper refresh & update, Sailfish OS didn't boot on Fxtec Pro1 anymore - stuck on splash screen. Flashing with Factory Reset tool didn't help - still stuck, just splashscreen now reset to default.00:56
OksanaSo, I fastbooted into twrp, and with File Manager and terminal reduced size of Data from 55GB to 11GB (removed all videos downloaded from Wikimedia Commons, deleted *.part and so on), and am now backing up to a microSD card.00:57
OksanaHopefully, my audio recordings, epub books, browser bookmarks+session/tabs+logins/passwords , Notes and such are saved into the back up.00:58
T42<ankaos> @elros34 [@ankaos be more verbose, what config, which fi …], my defconfig cyanogenmod_d802_defconfig01:01
T42<elros34> yeah I don't believe that is your real .config (too old kernel to have almost everything enabled). I asked about config.gz. I can't help you. you are still showing me mer-kernel-check against cyanogenmod_d802_defconfig  which is pointless as I told you many times01:09
T42<ankaos> you asked about config.gz01:13
T42<ankaos> @elros34 [yeah I don't believe that is your real .config …], yea this link :)01:15
OksanaTWRP backup format is... strange. I expected a zip ball, not a few data.ext4.win00 files.01:15
OksanaTrying to install Sailfish OS from zip. Failed to mount/data , Device or resource busy. Failed to mount /vendor (invalid argument)01:16
T42<elros34> @ankaos ok so you didn't enable audit like I told you many times but lets leave it right now. How is your dmesg and journal now?01:17
T42<ankaos> I deleted all the files. because it doesn't work.01:17
T42<elros34> @Oksana: if /data is already mounted then there will be warning that it can't mount /data01:18
OksanaHmm, I didn't manually mount it, but maybe, backup did mount it.01:19
OksanaAnyway, Sailfish OS installed fine, brand new, but, now I have got to somehow extract files out of TWRP back up.01:25
T42<leewp14> Is anyone able to clone sensorfw? I keep getting rpc failed result=52. It worked fine yesterday.02:01
T42<birdzhang> @leewp14 of course, rpc error means your network is not good02:07
T42<leewp14> Thanks. I will investigate on my own…02:14
r0kk3rzOksana: what did i tell you about zypper update :P04:09
DylanVanAsschemal (IRC): So updating mesa is fine for you? You can keep a lower version in the latte repos?05:11
DylanVanAsschemal (IRC): I updated some packages in native:common to the latest version and fixed the gst-plugins-good package.07:13
DylanVanAsscheRemoving `talloc` builddep from `mesa` seems to result into a build failure:
DylanVanAsscheI have to go now.07:13
DylanVanAsschemal (IRC): Good news! Updating `libdrm` and `mesa` to the latest release fixed the building issue 🎉08:41
malDylanVanAssche: looks quite ok now, gst-vaapi still needs updating11:00
malDylanVanAssche: wondering about mesa updating, in a way using same mesa version as official one would be nice but if native ports need newer then having newer makes sense11:01
T42<leewp14> @adampigg : do you still have the sfos package for n7000?11:42
deathmisthow does `/home` encryption work exactly? I'd like to include and test that on my port; is adding `sailfish-device-encryption` to patterns enough?11:46
DylanVanAsschemal (IRC): We have our own mesa in dontbeevil adaptation. I updated it to the latest mesa release.11:47
DylanVanAsscheFor lima driver it's the best way since it gets updates very frequently.11:47
DylanVanAsschemal (IRC): I didn't do  gst-vaapi since it was disabled, was not sure11:47
malDylanVanAssche: disabled? it's only used for x86 builds11:52
malafaik latte uses it?11:52
DylanVanAsscheAh yes, it's only disabled for arm.11:53
DylanVanAsscheI haven't resolved mesa on native-common since it's a version from piggz to stay latte compatible I think?11:53
malDylanVanAssche: so just removing the talloc dependency wasn't enough?11:54
malthat is just an obsolete dependency that does nothing11:55
DylanVanAsschemal (IRC): Not really, I removed it and I had a build failure about some missing .so files. I took a wild guess and just updated mesa + libdrm, builds fine now :D11:56
DylanVanAsscheI checked the release notes of libdrm and it seems that these .so files were available in a newer version than we have.11:56
malDylanVanAssche: maybe you used wrong version, it was built from 19.1.4+git1 tag not from master11:56
DylanVanAsschemal (IRC): Hmmm maybe, but updating it wouldn't hurt I guess?11:57
malwell if latte works then updating is fine11:58
malpiggz: ^11:58
DylanVanAsscheI updated it in the dontbeevil repo, not in the native common. one  If piggz can test the latest mesa, we can update it in native common as well11:59
malsure, let's wait for that, you can fix gst-vaapi, should be simple submodule update11:59
DylanVanAsschemal (IRC): If I want to fix it, I need to change the build URL from piggz gitlab to mine. Maybe let piggz do that?12:01
DylanVanAsschemal (IRC): There is something weird now going on, after some time everything freezes on the screen since the mesa update. I would wait12:02
malDylanVanAssche: ok, piggz can do it12:04
deathmistmal: any idea what's needed for `/home` encryption enablement on a SFOS port? installing `sailfish-device-encryption`, adding and enabling encryption from system settings leads to on my device12:12
DylanVanAsschedeathmist (IRC): AFAIK, you need a separate home and root partition. Not sure if that's the case for your port12:13
deathmistso I'd need Btrfs subvolumes because this is just a droid and there's no way I'll mess partition tables on this thing12:16
rinigusDeathmist: or use LVM, as xperias do12:23
deathmist.-. I have no clue how either of those work though12:23
rinigusDeathmist: as encryption is just a pin, it was very simple to decrypt. wasn't there someone who showed that its just few seconds/minutes if data is extracted to PC?12:25
rinigus^ in the sense that is using pin to encrypt data12:25
rinigus... that's as far as I understood from chats - not checked the code nor have deep understanding of how it works12:26
deathmistmeh, I'll look into encryption later then12:53
deathmistif others here have already moved to, can you sign into Jolla accounts on initial setup screen if connecting to internet via WLAN instead of cellular data? for me the system date & time are just incorrect (and not auto-updating by default) and I get "Problem with network"12:54
T42<elros34> for me auto update time is always checked at first boot but I didn't try to sign into to Jolla account. If I disable it once it doesn't use correct timezone anymore (AFAIK known bug)13:13
piggzmal: my firewall fix also worked for birdzhang13:21
T42<birdzhang> yeah, thank you ;)14:01
T42<birdzhang> @deathmist same issue on my two device, network problem14:02
malhmm, very strange14:05
deathmistthis wasn't an issue on 3.2.1, I've always connected to WLAN on the initial setup screen14:12
maldeathmist: afaik home encryption assumes the official way for the port meaning separate home which is not the case for community ports14:13
maldeathmist: btrfs is not used in new devices like sonys, those use the normal ext414:14
maland lvm14:15
maldeathmist: I haven't yet built a 3.3.0 image so I need to test that14:16
DylanVanAsschemal (IRC): When I run `zypper ref` of a repo, the repo is not updated. Zypper says it is up to date but if you look on OBS, the package has a different version there. Any idea?14:58
DylanVanAsschenvm it seems that it needed some propagation. However, that's the first time that it takes so long15:02
malDylanVanAssche: which OBS project?15:14
DylanVanAsschemal (IRC): Dont be evil:
DylanVanAsscheI'm just not sure what the difference is between the list of packages on OBS (when you surf to the repo URL) and what zypper sees15:55
deathmistmal: any news on fingerprint MW for community devices btw?16:09
malno news16:10
DylanVanAsschemal (IRC): Appearently, the flashlight plugin of Jolla Settings is closed source and hardcoded to droid stuff.16:42
DylanVanAsscheNow for the PinePhone, this won't work. It tries to create a gstreamer source element which only works on droid devices.16:42
DylanVanAsscheDo you have an idea on how we can fix this? Like writing such plugin ourselves? But no idea how to do that16:42
malDylanVanAssche: yeah, it needs to be fixed somehow16:46
malneeds some discussion internally16:47
DylanVanAsscheOr maybe OSS that plugin 😁 heheheh16:47
DylanVanAsscheOkay, do I need to bring it up during a SFOS community meeting?16:47
malDylanVanAssche: does camera work in pinephone yet? does flash work via gstreamer?16:48
DylanVanAsschemal (IRC): Cameras are not working yet (they work, but not via gstreamer yet). Flash is controlled via /sys/class/leds or using V4L2 APIs (more likely if you are using multimedia stuff)16:50
malDylanVanAssche: first we need to see which way to use flash on that device16:55
DylanVanAsschemal (IRC): I would go for the V4L2 API, you need to implement the camera stuff anyway as a V4L2 API (which QtMultimedia supports). The GPIO interface is used for scripting stuff and such.16:56
DylanVanAsscheThat's the same way AFAIK as the hybris devices16:57
abransonlooks to me like it would work through v4l2-request>libva>gst-va>qtmm16:58
DylanVanAsscheYep something like that16:58
deathmist has been down for 8 hours at least today, doesn't look like maintenance stuff either17:01
DylanVanAsschemal (IRC): Mesa is fixed for the PinePhone. We need to use the 'master' branch, not the point releases. The LIMA driver fixes are not backported to the releases, so a release can be broken for LIMA. Master works fine for the PinePhone 🎉 but not suitable I guess for native-common?17:45
malDylanVanAssche: maybe pinephone should use its own mesa for now then, hopefully next release will work for both, need to get information from piggz about latte first18:20
T42<adampigg> argh, too much to do!18:25
DylanVanAsschemal (IRC): Sure :)18:38
deathmistmal: is still down :/19:13
maldeathmist: yeah, I informed the relevant people already19:13
piggzmal: experimenting with new mesa on latte....19:32
piggzlast working was 19.1.419:32
malpiggz: so the issue was never solved?19:40
malpiggz: update bluetooth-rfkill-event-hciattach in latte project19:54
piggzmal: bt rfkill event has a conflict with a system package now...20:03
piggzFile /usr/sbin/bluetooth_rfkill_event20:03
piggz  from install of20:03
piggz     bluetooth-rfkill-event-hciattach-1.0.8-1.3.1.jolla.i486 (adaptation-community)20:03
piggz  conflicts with file from package20:03
piggz     bluetooth-rfkill-event-1.0.6+bluez5.20190210090636.1.g35e927a-1.2.1.jolla.i486 (@System)20:03
piggzmal: oh, this looks like fantastic news20:05
piggz@eugenio_g7 mesa 20.1.0-rc1 works ....20:06
piggznow mal will make me check the latest point release :/20:06
malpiggz: why do you have two of those rfkill event packages installed20:10
malI assume that other one is some test version20:10
T42<eugenio_g7> piggz: \o/20:11
piggzrebuilding 20.0.620:11
piggzmal: no idea atm ... ill look in a sec20:11
piggzmal: yeah, that version is gone now, it didnt have a repo20:13
deathmistmal: I tried logging in using cellular data instead of WLAN in initial setup, time & date got set correctly this time (and afterwards even had automatic update in system settings enabled) but I STILL get "Problem with network" and can't sign in, this is a new issue with 3.3.0, 3.2.1 did not have this issue20:20
piggzapparently, mesa 20 brought lots of intel fixes ... last version i tried was 19.3.320:20
deathmistand that older version could also update my time & date to be correct even if I choce WLAN during initial setup for networking instead of cellular data20:21
piggzmal: @eugenio_g7 mesa 20.0.6 is also safe for latte20:31
piggzmal: can bluetooth-rfkill-event-hciattach goto common?20:35
malpiggz: so if you have a good version of mesa updae native common20:42
piggzmal: gr8, can drop that....20:44
piggzwonder what i should do about the broadcom-bluetooth-bluez5 ....20:54
piggzi could either PR it or drop it .... maybe it coul dbe dropped because it is just a build requres for bluez-libs20:54
piggzno, maybe its required20:55
piggzi should PR ir20:55
malpiggz: I replaced gst-vaapi in native-common20:59
piggzjust seen20:59
piggzmal: at some point, mer-core should update its mesa and we should use that instead of mine ... mine is just a dumping ground of tags in random testing order!21:00
malpiggz: we would a separate spec for the driver version and that needs some discussion21:01
malpiggz: I'll replace libva also unless there is some good reason why it's old21:03
piggzmal: sure21:03
piggzi know the intel-vaapi-plugin is also v old21:03
piggzi think there was a reason, like build deps21:03
malI can revert it then21:04
piggztry it, if its no good we will find out21:06
piggzive deleted mesa from latte repo now ... its a very slim repo!21:06
malpiggz: would be nice know what the issue with intel-vaapi-plugin was21:07
piggzmal: looking at the source ... ive made the version 1.5 for some reason21:08
piggzmal: its the libva and libdrm versions....21:17
piggzthose are a lot better than they used to be21:19
piggzso maybe less of an issue21:19
malpiggz: we seem to have new enough libdrm21:20
piggzmal: ok, if you update them, i will re-package intel-vaapi-driver on a rebased verison21:21
malpiggz: libdrm_dep = dependency('libdrm', version : '>= 2.4.52'), we have 2.4.9721:21
piggzyeah, when i was packaging all this for latte originally, out libdrm was much older21:22
malI'll update libva then21:22
malto 2.6.121:22
piggzintel-vaapi-driver 2.4.0 requires libdrm 2.4.52 libva 1.4.021:23
malhopefullythat new one works21:24
malpiggz: there has been quite much of mer-core updated so it's not that far behind anymore as it used to be21:24
piggzmal: whats this doing
malpiggz: libva-intel-driver-2.4.0+2.4.0.sailfish.20200503212748.ef1c1cd.tar.gz vs intel-vaapi-driver-2.4.0+2.4.0.sailfish.20200503212748.ef1c1cd21:39
malnote the name difference21:39
malpiggz: btw, would be nicer to do that repo the usual submodule way21:41
piggzwas thinking that21:41
malwhy is the source not updating in that package21:51
piggzi dont know!21:52
piggzthe package name matches the rpm name... it shouldnt be gotting intel-vaapi-driver from anywaher!21:53
malpiggz: look at the spec on OBS, that is the old one21:55
piggzmal: ill continue in the morning, its at least building now, and fialing later22:01
piggzmal: ok, i got it built22:06
T42<adampigg> Mal, oddly,  had to specify revision22:28
T42<elros34> IIRC obs doesn't like - in tags, that could be related22:40

Generated by 2.17.1 by Marius Gedminas - find it at!