Oksana_ | r0kk3rz: After installing Sailfish OS anew, I didn't run any zypper update. I didn't have to, OS automagically did it itself. Camera stopped working soon, then after reboot cellular network went down as well. Glad that it is still capable of booting, at least. But would like cellular network back! And camera, too. | 05:48 |
---|---|---|
r0kk3rz | huh | 05:49 |
Oksana_ | Sooo, should I somehow try to recover Sailfish 3.2.1.20 on Fxtec Pro1 to working state, or should I try to switch to Sailfish 3.3.0.16 in hopes it will work better? | 05:49 |
r0kk3rz | it wont automagically update things | 05:50 |
Oksana_ | zyp in --oldpackage doesn't work, Package not found for both nemo-gstreamer1.0-interfaces and the other thing. | 05:50 |
r0kk3rz | yeah you cant really go backwards | 05:50 |
Oksana_ | Well, the GUI might have decided to automagically check for Sailfish OS updates. Who knows this Jolla thing... | 05:51 |
r0kk3rz | no, the gui will do no such thing | 05:51 |
Oksana_ | Storeman doesn't run zypper update on non-OpenRepos packages, right? | 05:51 |
r0kk3rz | not sure, i should hope not | 05:52 |
Oksana_ | Doesn't Sailfish OS during installation check for operating system updates? | 05:52 |
r0kk3rz | no | 05:52 |
Oksana_ | What does Sailfish OS updates thingie in Settings do, and based on what triggers? | 05:52 |
r0kk3rz | the settings thing is for official devices | 05:53 |
r0kk3rz | which does nothing on ported devices | 05:53 |
Oksana_ | Because I definitely didn't run zypper update. I didn't even run zypper refresh. | 05:53 |
Oksana_ | zypper --verify and version --dup, these two I have run. They wouldn't have run update, right? | 05:54 |
r0kk3rz | did you deliberately update a version? | 05:55 |
Oksana_ | These two have given errors - zypper has said something about 'product', version has said something else. | 05:55 |
Oksana_ | Sailfish is 3.2.1.20. And I don't know what version --dup does, besides saying nothing provides libstdc++.so.6(CXXABI_1.3.9) needed by geoclue-provider-hybris-binder-0.2.28-1.4.5.jolla.armv7hl | 05:56 |
r0kk3rz | so you flashed a 3.2.1 image? | 05:57 |
Oksana_ | zypper --verify gives product:# This file is copied as hw-release-0.0.1+master.20200502113015.be0be38.2.analogous to os-release is not installableSolution 1: deinstallation of product:# This file is copied as hw-release-0.0.1+master.20200502113015.be0be38.2.analogous to os-release | 05:57 |
Oksana_ | Yes, I flashed https://community.fxtec.com/topic/2467-community-build32120updated-jan-20-sailfish-os-for-fxtec-pro1/ | 05:57 |
r0kk3rz | ok good | 05:58 |
r0kk3rz | why did you do version --dup then? | 05:58 |
Oksana_ | I don't remember the particular order. It is quite possible that I have only run it after problems started. But, difficult to be certain. | 06:01 |
r0kk3rz | i suspect its the cause | 06:02 |
r0kk3rz | clearly theres packages in the OBS repo, that if installed will break things | 06:02 |
r0kk3rz | and you will need to wait until 3.3.0 is ready | 06:03 |
r0kk3rz | version --dup will probably install them | 06:03 |
Oksana_ | So, what does Sailfish OS updates thing in Settings do? Because I find it more believable that I clicked the GUI thing than that I started running random things in command line while everything was still working. | 06:04 |
r0kk3rz | for ported devices, nothing | 06:05 |
r0kk3rz | and you should never run random things in command line :P | 06:06 |
* Oksana_ is still sure that every time I run version --dup manually in command line, it backed out after 9 retried due to the error and didn't actually do anything - but alright, cannot undo whatever was done, let's try updating to 3.3.0.16, since there is no way to downgrade... | 06:12 | |
r0kk3rz | probably wait before doint that | 06:12 |
Oksana_ | Hmm, wait for what? | 06:12 |
Oksana_ | Ah, more polished 3.3? | 06:13 |
r0kk3rz | wait for the porters to say its ready | 06:13 |
Oksana_ | Where are the updates? I have heard of Telegram, but, I don't have a Telegram account. | 06:15 |
Oksana_ | Somebody is already using 3.3.0.14 on Fxtec Pro1, apparently, but, they do seem to have a "black camera" problem... | 06:18 |
r0kk3rz | yeah, evidently there is something that needs fixing | 06:19 |
r0kk3rz | updated droidmedia maybe | 06:20 |
T42 | <birdzhang> use latest droidmedia and gst-droid can fix | 06:24 |
r0kk3rz | @birdzhang did you fix your version package? | 06:31 |
Oksana_ | Are there any problems visible in the rpm -qa output attached to the forum post http://talk.maemo.org/showthread.php?p=1567303#post1567303 ? If there are old versions available somewhere to downgrade to, I could install them manually. | 06:31 |
T42 | <birdzhang> yeah, i use @elros34 's function | 06:31 |
r0kk3rz | how do i do that? | 06:34 |
T42 | <birdzhang> https://pastebin.com/nC9Dxh1q | 06:36 |
piggz | @elros34 yeah, it like the other tag name | 06:44 |
piggz | Oksana_: camera stopped working becuase you are on devel: repo and some packages got updated in the common repos | 06:44 |
piggz | if you update to 3.3 in the devel: repo you should be ok, but you should also switch to the testing: repo for users which has been announced a few time | 06:45 |
Oksana_ | So, common repos have newer packages than devel: repo, and the update breaks things because they are not from devel: repo anymore. | 06:45 |
piggz | well, the devel: common repo expects to always be on the latest version, and for the pr1 we hadnt yet updated the droidmedia and gst-droid packages to match | 06:47 |
piggz | if you are on 3.2 still, you should switch your repos to testing: | 06:48 |
Oksana_ | piggz: Would you mind pointing me to how switch to testing: repo? I know that ssu re 3.3.0.16 (is it the correct version?) can change version from 3.2.1.20, with version --dup to follow afterwards, but not much besides that... | 06:48 |
piggz | are you in the sfos-users-telegram group? | 06:48 |
piggz | sorry, sfos-pro1-users | 06:49 |
Oksana_ | No, I don't have a Telegram account | 06:49 |
piggz | ok, i think we also posted in the forums, but... basically | 06:49 |
r0kk3rz | Oksana_: you would ssu dr the devel repo, and ssu ar the testing repo | 06:49 |
piggz | edit /usr/share/ssu/features.d/adaptation-community.ini | 06:50 |
piggz | Adam Pigg, [01.05.20 22:13] | 06:50 |
piggz | At the moment, the file will likely be pointing to the devel: repository http://repo.merproject.org/obs/nemo:/devel:/hw:/fxtec:/t5/sailfish_latest_%(arch)/ | 06:50 |
piggz | Adam Pigg, [01.05.20 22:15] | 06:50 |
piggz | This should be changed to: http://repo.merproject.org/obs/nemo:/testing:/hw:/fxtec:/t5/sailfishos_%(release)/ | 06:50 |
piggz | Adam Pigg, [01.05.20 22:16] | 06:50 |
piggz | Then issue the command: | 06:50 |
piggz | ssu re 3.2.1.20 && ssu ur && zypper ref && zypper dup | 06:50 |
piggz | Oksana_: and, id quite like to know if everything in the testing repo works .... | 06:53 |
piggz | you probably also need to edit the adaptation-community-common repo file too | 06:53 |
piggz | to match | 06:53 |
piggz | mal: you approved this in november https://github.com/mer-hybris/broadcom-bluetooth/pull/2 not merged yet | 07:30 |
piggz | mal: also, https://build.merproject.org/package/show/nemo:devel:hw:xiaomi:latte/bluetooth-rfkill-event-hciattach could go in common or common-native? | 07:31 |
r0kk3rz | you cant merge it? | 07:31 |
piggz | i dunno, it =s mer-hybris, do i have permission there | 07:31 |
piggz | no i cant | 07:32 |
piggz | r0kk3rz: porters-ci question for ya ..... | 07:38 |
r0kk3rz | hmmm? | 07:38 |
piggz | we added the repo and package name for harbour-storeman to our pinephone package, along with webcat | 07:38 |
piggz | webcat gets installed, but there is no mention of storeman in the logs at all | 07:38 |
piggz | it just seems to be ignored...th logs show the repo being refreshed | 07:39 |
piggz | ideas? | 07:39 |
r0kk3rz | you added the things to the ks? | 07:39 |
r0kk3rz | i would've thought it would abort if it couldnt find the package | 07:40 |
r0kk3rz | not sure, i see no obvious error | 07:46 |
piggz | r0kk3rz: i would have thought that too! | 08:14 |
piggz | https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/-/blob/master/pinephone-1.0/Jolla-@RELEASE@-pinephone-1.0-@ARCH@.ks#L60 | 08:14 |
mal | piggz: do you want to make tiny change to both specs in broadcom-bluetooth, change license from Apache 2.0 to ASL 2.0 | 09:20 |
piggz | mal: sure | 09:20 |
T42 | <elros34> @Oksana_: I stopped using storeman sometime ago because it upgrades other apps when I was installing something using it. Not sure if this is still a problem or it affects system packages. | 09:47 |
T42 | <edp_17> Hi guys. When I am building hybris-hal, I am getting this error: https://paste.ubuntu.com/p/yGtTjrsTRs/ | 12:09 |
T42 | <edp_17> This error doesn't make sense to me as I thought this step will create the kernel and boot.img files in out/target/product/$DEVICE/ | 12:10 |
T42 | <edp_17> Or am I missing something? | 12:10 |
piggz | mal: where does ssu gets its device vendor name from? | 12:13 |
atlochowski | <elros34> yes, when you want to update just one app in storeman, it always updating all packages (apps). | 13:11 |
mal | piggz: I think from file generated from this during build https://github.com/mer-hybris/droid-hal-configs/blob/master/ssu/board-mappings.d/05-sfe.ini.in | 13:12 |
mal | or something like that | 13:12 |
piggz | mal: abranson: looks ok then ... file looks correct, and latte says (latte /latte ) in ssu status too | 13:16 |
piggz | we should request store access then maybe, but im not sure if we can read imei yet | 13:17 |
abranson | maybe that vendor should be something else? | 13:17 |
DylanVanAssche | We can't read IMEI yet | 13:17 |
piggz | abranson: the settings file is correct https://hastebin.com/ileluyikit.makefile | 13:18 |
piggz | DylanVanAssche: whats your UID in ssu status ? | 13:19 |
DylanVanAssche | 02ba177f6d77 piggz (IRC) yours? | 13:19 |
piggz | 02ba38cdc901 | 13:20 |
DylanVanAssche | So it's unique? That's not good? | 13:20 |
piggz | no, it is good | 13:20 |
DylanVanAssche | But it needs to be stable across reboots? | 13:21 |
piggz | DylanVanAssche: mine is stable across boots | 13:23 |
DylanVanAssche | piggz (IRC): Mine is stable too 🎉 | 13:28 |
mal | abranson: it's normal to have latte/latte | 13:29 |
mal | piggz: DylanVanAssche is that related to wlan mac in any way? | 13:30 |
DylanVanAssche | mal (IRC): ssu device id? Without IMEI it is based on MAC addresses if I remember correctly | 13:32 |
mal | yeah, it should be | 13:33 |
piggz | mal: abranson: this seems naughty | 14:05 |
piggz | [nemo@PinePhone ~]$ rpm -qa --qf '[%{obsoletes}\n]' store-client | 14:05 |
piggz | harbour-storeman | 14:05 |
piggz | harbour-warehouse | 14:05 |
piggz | DylanVanAssche: ^^ | 14:05 |
abranson | piggz: Obsoletes: harbour-storeman <= 0.0.15 | 14:06 |
abranson | because of that old packagekit problem | 14:07 |
piggz | ah | 14:07 |
piggz | thought i had it then | 14:07 |
abranson | there are a couple of those around to remove packages that break upgrades | 14:10 |
piggz | maybe ill try and cheat, and install the package manually at the end of the kickstart | 14:11 |
DylanVanAssche | That's an option 😁 Cheating all the way! | 14:14 |
piggz | DylanVanAssche: building now, if its works, ill MR :D | 14:16 |
DylanVanAssche | piggz (IRC): Nice 🙂 Should we add Jolla Store access first or just announce the 3.3.0 release when storeman is in there? | 14:17 |
piggz | see what pketo says ? | 14:17 |
piggz | the holder of store access :D | 14:17 |
T42 | <Nebrassy> so bluetooth works for me if I restart bluebinder after boot, but I can't get it to work normally | 15:34 |
T42 | <Nebrassy> is it possible to delay its start ? | 15:45 |
T42 | <elros34> check sources there is already delay, maybe it doesn't work for you | 15:53 |
T42 | <Nebrassy> I tried adding sleep 20 in various places in bluebinder_wait.sh and bluebinder_post.sh but didn't help | 15:56 |
T42 | <Nebrassy> Also I'd like to build for multiple devices on the same machine, is it simple to do so? | 15:59 |
T42 | <elros34> have you checked in journal that it really delay start, not just timeout or smth | 16:01 |
T42 | <Nebrassy> With sleep 10 in bluebinder_wait.sh , when I restart bluebinder it takes 10 seconds and works so it is delaying | 16:02 |
T42 | <Nebrassy> In bluebinder_post.sh it times out | 16:03 |
DylanVanAssche | spiiroin (IRC): We talked a while ago about polling in mce for battery states. However, we haven't defined how we actually can implement it. For the PinePhone, cable states and battery full state are reported and the gauge is updated. Between those events, no updates are passed to the mce's battery state. We would only need to poll a sysfs interface in a certain interval, but I have no idea atm how to properly | 16:05 |
DylanVanAssche | implement that in mce. | 16:05 |
T42 | <elros34> I mean on system boot | 16:05 |
spiiroin | DylanVanAssche: I've planned something like that in my head. But that was mostly geared towards not missing unnotified battery percent changes during discharging = pace does not matter that much, heartbeat could be used. | 16:37 |
spiiroin | having also major/rapid changes go without notifications are a bit more problematic | 16:38 |
spiiroin | IIRC pine phone was silent about some things on cable disconnect -> getting some things immediately (disconnect) and some up to 12 seconds later (battery state) might cause hiccups | 16:38 |
spiiroin | so there might be need for both time and event based polling - which easily turns ugly and unreliably (basically back to statefs problems) | 16:40 |
spiiroin | I might have a change to get my hands on / remote connection to a pine phone - which could make things a bit easier to gauge | 16:41 |
DylanVanAssche | spiiroin (IRC): That would be nice 🙂 I was thinking about a hacky hardcoded implementation (just to test 😁 ): mce_wakelocked_timeout_add -> function to read a file (the battery capacity) and send the value over the mce datapipes | 16:51 |
piggz | spiiroin: still around? | 17:21 |
T42 | <Nebrassy> log for camera, after taking a video, switching back to photo crashes cam, also happens on jolla camera | 17:42 |
T42 | <Nebrassy> http://haste.aicp-rom.com/elofiqucil.nginx | 17:42 |
T42 | <Nebrassy> and needs restart to work again | 17:42 |
DylanVanAssche | spiiroin (IRC): I quickly hacked together my idea here: https://git.sailfishos.org/DylanVanAssc/mce/commit/9826d2ef7085ac4708b677420688bb9f167c8727 | 18:44 |
DylanVanAssche | Works on the PinePhone, hardcoded like hell, drains the battery like hell but the battery gauge gets updated 🎉 | 18:44 |
DylanVanAssche | If this idea is okay, the code can be rewritten, improved, ... to get something usable. Or do you have a better idea? | 18:44 |
piggz | mal: what should the permissions be in /etc/dconf/db ? | 19:15 |
piggz | my pro1 has r+x on the directories, but pinephone doesnt | 19:16 |
piggz | r+x seems more normal | 19:16 |
piggz | sure this must be related https://git.sailfishos.org/mer-core/dconf/commit/fa720e00e451fd61169965ad3155ee3b674d3639#58552dee00c159daab3e1d43ef26ed6156a8cdc0 | 19:17 |
mal | piggz: folders 755 and files 644 root:root | 19:21 |
mal | piggz: why would only your device have issues | 19:25 |
mal | piggz: why is there a exit 0 here https://github.com/sailfish-on-dontbeevil/droid-config-pinephone/blob/master/rpm/droid-config-pinephone.spec#L38 | 19:27 |
piggz | mal: iirc, as we were experimenting with how to add users/groups (ended up in kickstart) when i commented out the pre section, it required an exit 0 | 19:28 |
piggz | the whol section can be removed now | 19:29 |
piggz | ----and it has been! | 19:32 |
mal | piggz: are all folders and files in /etc/dconf with wrong permissions? | 19:33 |
mal | piggz: is the issue only with 3.3.0? | 19:33 |
piggz | mal: the perms are wrong becuase of the fix we have in the kickstart ... | 19:33 |
piggz | the fix "fixes" it for us but isnt quite right | 19:34 |
piggz | before the perms are totally off | 19:34 |
piggz | mal: see https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/-/blob/master/pinephone-1.0/Jolla-@RELEASE@-pinephone-1.0-@ARCH@.ks#L101 | 19:35 |
piggz | maybe ishoudadd an ls -lhR to the start to print the perms? | 19:36 |
piggz | mal: and yes, only in 3.3 | 19:36 |
piggz | and we do it again here https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/-/blob/master/pinephone-1.0/Jolla-@RELEASE@-pinephone-1.0-@ARCH@.ks#L148 | 19:37 |
mal | hmm, that is very strange | 19:39 |
piggz | mal: im running a pipeline now that wil print the permissions before edititing .... and i learned some chmod magic to set the correct permissions in a single command | 19:45 |
mal | piggz: I'm making a test build for fp2 to see if the image looks good | 19:53 |
mal | piggz: can you point me to some broken build in ci | 19:57 |
piggz | mal: if you watch this log you will see the perms shortly https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/-/jobs/537749099 | 19:59 |
piggz | mal: this is probably the first broken one https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/-/jobs/534717680 | 20:00 |
piggz | mal: you can see here that after package installation, the oneshats fail https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/-/jobs/537749099#L2795 | 20:02 |
piggz | and here, missing read perms for non root https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/-/jobs/537749099#L2891 | 20:02 |
piggz | hmmmm, at the start the perms look reasonable https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/-/jobs/537749099#L2636 | 20:04 |
piggz | the oneshot for dconf update fails https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/-/jobs/537749099#L2704 | 20:05 |
piggz | i bet its because we havnt created users by that point | 20:06 |
piggz | actually, dconf oneshot is supposed to fail https://gitlab.com/sailfishos-porters-ci/dont_be_evil-ci/-/jobs/537749099#L2704 | 20:08 |
T42 | <elros34> just an idea, did you regenerate ks file for 3.3.0? IIRC "user --name=nemo --groups" is no longer there | 20:11 |
piggz | @elros34 we didnt ... but we have to do a lot of user/group manlging on pine becuase we dont have DHD to do it for us | 20:20 |
piggz | but a diff would be nice to see changes | 20:20 |
T42 | <elros34> basically just the user part: https://pastebin.com/nRrXyxJp | 20:28 |
piggz | @elros43 thats interesting in itself ... i wonder where that happens | 20:32 |
piggz | must be sailfish-setup? | 20:32 |
T42 | <elros34> I guess, I didn't investigate it. I created 3.3.0 image for mainline device some time ago but didn't test it much | 20:34 |
piggz | the oenshots that are triggering the permission errors are all enable-*-hints | 20:47 |
piggz | it could be that su -c ...... | 20:49 |
piggz | lets see | 20:49 |
piggz | mal: that was it!!!!! | 21:05 |
piggz | @elros34 thx! | 21:05 |
mal | piggz: what? | 21:05 |
piggz | changed: | 21:06 |
piggz | su -c "/usr/bin/oneshot --mic" | 21:06 |
piggz | to | 21:06 |
mal | ah, so old .ks | 21:06 |
piggz | /usr/bin/oneshot --mic | 21:06 |
mal | good to update my .ks files then | 21:06 |
mal | I always use the same files | 21:06 |
piggz | as do we! | 21:06 |
piggz | the diff is pretty small | 21:06 |
piggz | see [21:28] <T42> <elros34> basically just the user part: https://pastebin.com/nRrXyxJp | 21:07 |
mal | piggz: I think I had a lot older .ks because my diff was much bigger | 21:07 |
mal | could be even years old .ks | 21:08 |
piggz | ours is about to get smaller with all those hacks taken out | 21:08 |
mal | PSA: when you build images for 3.3.0.16 recreate your .ks file, do not use old .ks files | 21:14 |
mal | piggz: people using ci need to remember that .ks file issue | 21:14 |
mal | probably easy to use old file there | 21:15 |
piggz | yup | 21:15 |
piggz | i need to look into sailfish-setup to see what that does for us ... maybe we could drop some uer stuff if its handled there | 21:16 |
mal | piggz: hmm, I recreated the .ks but it still has the wrong oneshot command | 21:17 |
piggz | mal: how is su -c "command" different to command ? ... isnt mic running as root anyway? | 21:17 |
piggz | mal: asl @elros34 where he made the diff from i guess :) | 21:17 |
piggz | s/ask | 21:18 |
mal | ah, forgot to update target | 21:18 |
mal | oops | 21:18 |
piggz | heh | 21:20 |
mal | piggz: yep, now my build log looks clean | 21:33 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!