| depscribe | mal : yup, i'm sure. got the newest version running after purging; didn't like it, so reverted to the previous version and after nine hours am where i was before the upgrade. | 00:27 |
|---|---|---|
| Halftux | does somebody know if there exists the sources from the new top menu introduced in sfos 3 and where I could find them? | 11:58 |
| r0kk3rz | on the device | 11:59 |
| Halftux | ok so it is script language? do you have some keyword to find the right files on the device? | 12:03 |
| r0kk3rz | all the ui is in qml and typically in plain text on the device | 12:05 |
| Tegu | Halftux: I think 'lipstick' is one keyword | 12:14 |
| Tegu | for example, /usr/share/lipstick-jola-home-qt5/topmenu looks relevant | 12:14 |
| Tegu | jolla* | 12:15 |
| Halftux | ok thank you seems a good starting point I will have a look into it | 12:18 |
| caitlin | just to follow up, bluetooth audio doesn't work in my vw polo | 12:42 |
| _sven | caitlin which device? | 12:45 |
| _sven | caitlin: does it pair yoz | 12:47 |
| _sven | caitlin: does it pair your device? | 12:48 |
| caitlin | pairs fine, does an o2db or whatever it is headset profil | 13:15 |
| caitlin | and then then plays music out of its tinny little xa2 speaker anyway | 13:16 |
| caitlin | so far the only thing it's connected to has been a chinese amplifier with built in blueteeth | 13:16 |
| mal | caitlin: can you check what pactl (maybe pactl list or somthing) shows as used output? | 13:17 |
| caitlin | when connected? | 13:28 |
| mal | yes, to see what it lists and uses | 13:29 |
| caitlin | will do, whe next in the car | 13:29 |
| _sven | caitlin show me the service key line from /var/lib/bluetooth/<device id>/info , pls. use a pastebin site because it's a long line | 13:34 |
| tortoisedoc | lbt : pimng | 13:35 |
| tortoisedoc | s/pimng/ping :P | 13:35 |
| caitlin | _sven, does that need to be do when connected? because there is no info file atm | 15:02 |
| _sven | caitlin: /var/lib/bluetooth/<your-BT-device-id>/<Car-BT-device-id>/info should exist | 15:56 |
| Martiini | Do any developers sit in this #sailfishos chat? | 16:33 |
| r0kk3rz | sure | 16:35 |
| r0kk3rz | thats what this channel is for | 16:35 |
| Martiini | I think, on Sailfish, it's wrong, swiping top-down shows "themes".. Home screen top drawer should be same as on Android - swiping top edge shows all important settings | 16:40 |
| Martiini | :) but then again, I'd change most things on Earth, if it was my decision | 16:45 |
| Martiini | but maybe someone will port Android Nova launcher User Interface to Sailfish. | 16:49 |
| r0kk3rz | wat. yeah no | 17:03 |
| Martiini | why? | 17:04 |
| r0kk3rz | you can remove the ambiences from sfos 3 if they bother you so much | 17:04 |
| Martiini | oki | 17:04 |
| Martiini | remember, how Apple UI development is absolute science, it's not simply some decision made in a developer meeting | 17:06 |
| r0kk3rz | sure | 17:06 |
| DennisRoczek|afk | {{citation needed}} | 17:11 |
| DennisRoczek|afk | some UI decisions are simply crap. Yeah, most seem useful and it's good to hide many options somewhere, but there are also enough decisions which are simply dump | 17:12 |
| DennisRoczek|afk | (speaking of apple) | 17:13 |
| Martiini | can I install repository packages, like in Debian or Arch | 17:13 |
| DennisRoczek|afk | just one simply example: try to modify the standard printer setup to print always black/white and not colorful. you have to enable CUPS web interface and change the option there! | 17:13 |
| Martiini | yes | 17:14 |
| *** frinring_ is now known as frinring | 17:16 | |
| depscribe | Martini : I agreed with you re. themes/ambiences, and I removed them from the top menu. And then yesterday -- you can look at the logs of this chat for details -- | 17:16 |
| Martiini | thanks | 17:17 |
| depscribe | I ran afoul of the one situation where they would have saved me! | 17:17 |
| Martiini | I'll see if it's newbie-hackable .. | 17:17 |
| Martiini | .. but right now I can't su in terminal | 17:17 |
| Martiini | ... can't get root, cause I dont know password | 17:18 |
| r0kk3rz | Martiini: try devel-su | 17:18 |
| r0kk3rz | set password in debeloper options in settings | 17:18 |
| Martiini | humanity is a weird thing - everything is made impossible | 17:18 |
| r0kk3rz | lol. | 17:19 |
| depscribe | Martini = Martiini | 17:19 |
| tango_ | exit | 17:21 |
| tango_ | ehm | 17:21 |
| r0kk3rz | awks | 17:22 |
| DylanVanAssche | For those who are hoping for NFC support: https://git.merproject.org/mer-core/nfcd :) | 17:34 |
| ol | Wow, that's great news! | 17:38 |
| DylanVanAssche | But that's still no indication we can use NFC. However, it's a big step forward :) | 17:39 |
| ol | But what's the reason to start this project if there is no intention to have NFC support? I don't see any other explanation. | 17:40 |
| DylanVanAssche | ol: I mean on app level, the interfacing with the hardware is available using the NFC daemon from above. | 17:41 |
| r0kk3rz | interesting, ill have to check it out | 17:43 |
| ol | Without app support, this project is meaningless. So, I presume, app support should follow, from Jolla or from independent developers. | 17:43 |
| DylanVanAssche | ol: That's what we can hope for... I hope 3rd party devs are allowed to use it when it's ready (not like the Account API or fingerprint daemon) | 17:46 |
| Martiini | aha! it's SUSE - it has zypper | 18:01 |
| r0kk3rz | its not suse | 18:25 |
| halftux | after looking at the setting qml files I need now the source code from the import module com.jolla.settings.system, can't find any sources; is somewhere a good place to look at the sailfish source code not mer-core? Or do I need to contact jolla directly? | 19:12 |
| r0kk3rz | anything with jolla in the name is | 19:35 |
| r0kk3rz | probably closed | 19:35 |
| halftux | yeah you are right found an old list with packages from 1.1.0.39 and it says that jolla-settings-system is proprietary | 19:40 |
| r0kk3rz | general rule is jolla = closed, sailfish/nemo = open | 19:42 |
| halftux | so I would say there is a bug maybe it is a feature, when enabling gps permissions the gps chip powers on, but when disableing the gps permissions the gps chip is still powered determined on the basis of dbus | 19:45 |
| halftux | version 3.0.0.8 | 19:46 |
| aalmi | Hi | 19:57 |
| aalmi | any help here I'm trying to install Sailfish3 to my XA2 | 19:58 |
| aalmi | for some reason fastboot fails | 19:58 |
| halftux | is there an api documentation about this jolla.settings.system module or other modules? The developer section on the homepage was not helpful in this matter. | 19:59 |
| mal | aalmi: which errors? | 20:00 |
| halftux | aalmi: be more specific what fastboot command and which error message. | 20:00 |
| aalmi | FAILED (remote: Command did not succeed) | 20:00 |
| mal | which command? more log please | 20:01 |
| aalmi | it approved xa2's imei2 code and gaved that error | 20:01 |
| aalmi | fastboot -i 0x0fce oem unlock 0xunlockcode | 20:01 |
| aalmi | fastboot devices shows XA2 fine and device should be as ready for unlock as ever | 20:02 |
| aalmi | confused what can I try next no help from instructions | 20:03 |
| mal | so the sony website gave you the code successfully? | 20:03 |
| aalmi | yes for both imei's imei1 did give different error code than imei2 | 20:04 |
| halftux | fastboot version from sony? | 20:04 |
| aalmi | fastboot 8.0.0_r17 on my linux | 20:05 |
| aalmi | installed from repo | 20:06 |
| mal | what error did the other code give, usually only one code should be enough | 20:07 |
| aalmi | clearly fastboot works because it sees XA2 | 20:07 |
| aalmi | imei1 FAILED (remote: Incorrect format for unlock data) | 20:07 |
| aalmi | imei2 FAILED (remote: Command did not succeed) | 20:08 |
| aalmi | both unlockcodes are from sony page | 20:08 |
| aalmi | after giving either imei | 20:08 |
| aalmi | syntax is: fastboot -i 0x0fce oem unlock 0xcode | 20:10 |
| aalmi | runned as root | 20:10 |
| mal | aalmi: maybe try again a few times, rewrite the command to be sure it has no incorrect characters | 20:11 |
| aalmi | fastboot decices shows same device as dmesg shows as XA2 serial | 20:12 |
| aalmi | I've tried multiple times no typos | 20:12 |
| halftux | Note platform tools 26.0.2 or older are required; don't know if newer will hurt | 20:12 |
| halftux | try with older once | 20:12 |
| aalmi | sony site said that those are not needed on linux | 20:12 |
| aalmi | because driver exists already | 20:12 |
| mal | I have used fastboot 7.0.0 r33 successfully | 20:13 |
| aalmi | hmm sorry actually sony site says no usb driver is needed on linux but platform is sec I'll install it | 20:14 |
| halftux | yeah linux can skip this step :-) | 20:14 |
| mal | aalmi: doesn't some place in android show if the device is unlockable, although I would assume sony website would also say if it's not | 20:15 |
| halftux | *#*#7378423#*#* | 20:16 |
| halftux | in dialer to access the service menu | 20:17 |
| aalmi | yeah my xa2 is unlockable yes | 20:19 |
| aalmi | hmm that sony platform-tools brings the same fastboot as I already have from repo | 20:19 |
| mal | check what "sudo fastboot getvar all" says | 20:22 |
| mal | about lock status | 20:22 |
| aalmi | hmm strange (bootloader) unlocked:no | 20:24 |
| aalmi | phone showed after code: Bootloader unlock allowed: yes | 20:25 |
| mal | ok | 20:25 |
| aalmi | any ideas? | 20:25 |
| halftux | you need older tools fastboot could be sometimes a pain | 20:25 |
| *** torotisedoc is now known as tortisedoc_ | 20:28 | |
| aalmi | that sony platform-tools 28.0.0.1 does not even have -i = vendor id option | 20:29 |
| tortisedoc_ | hmhm anoyoe with experience on sb2 internas? | 20:29 |
| aalmi | fastboot on 28.0.0.1 I mean | 20:29 |
| r0kk3rz | sb2 is made of magic and voodoo | 20:29 |
| mal | aalmi: so then leave it out? | 20:29 |
| tortisedoc_ | r0kk3rz : its not rocket science | 20:30 |
| tortisedoc_ | but there are some "dark" corners yes | 20:30 |
| mal | aalmi: are you completely sure the first code is correct? | 20:30 |
| r0kk3rz | tortisedoc_: nah rocket science has texts books about it | 20:30 |
| tortisedoc_ | like the fact that readlink is not mapped the same way as any other file accessing primitive | 20:30 |
| mal | and you added 0x to the beginning, and made sure it wasn't in the code already | 20:31 |
| tortisedoc_ | r0kk3rz : sb2 has the code ;) | 20:31 |
| tortisedoc_ | but the code can only get you that far | 20:31 |
| halftux | aalmi: get fastboot 26.0.2 | 20:31 |
| r0kk3rz | code tells you what it does, not why it does | 20:32 |
| tortisedoc_ | r0kk3rz : exactly | 20:32 |
| r0kk3rz | tortisedoc_: still rusting then? | 20:34 |
| tortisedoc_ | r0kk3rz : yep | 20:34 |
| tortisedoc_ | slowly crawling up the rusty turd mountain | 20:34 |
| aalmi | mal: yahoo | 20:39 |
| aalmi | OKAY [ 1.469s] finished. total time: 1.469s | 20:39 |
| aalmi | 26.0.0.2 fastboot did the trick | 20:40 |
| aalmi | imei1 code worked fine | 20:40 |
| mal | ok, very odd why version affects so much | 20:42 |
| mal | I had older version than you and it has worked fine | 20:42 |
| aalmi | mal now flashing device fingers crossed | 20:45 |
| halftux | I would guess that the old version is needed only for unlocking, for flashing newer version should/could work | 20:47 |
| halftux | *with newer | 20:48 |
| aalmi | mal/halftux: success flashing complete. My first sailfish boots | 20:51 |
| halftux | congrats | 20:52 |
| mal | good | 20:52 |
| halftux | btw you don't need -i = vendor id option when it is not supported but you should make sure that only one phone is connected to your pc | 20:54 |
| aalmi | so it was | 20:56 |
| halftux | related to sony new platform tools... | 20:57 |
| halftux | you did a good job :-) | 20:57 |
| tortisedoc_ | ping lbt | 21:19 |
| lbt | tortisedoc_: pong | 21:20 |
| tortisedoc_ | lbt : about that stack size issue with rustc compilation | 21:22 |
| lbt | yes | 21:22 |
| tortisedoc_ | is there any chance for increasing the default stack size (say double it) on system level, so that local ulimit could increase the stack size? | 21:23 |
| tortisedoc_ | lbt : I dont even know if you are the right person to talk to about this btw :) | 21:24 |
| lbt | I am | 21:24 |
| tortisedoc_ | ok great | 21:25 |
| lbt | looking | 21:25 |
| aalmi | btw I need to configure to sailfish ipsec vpn using x.509 psk auth any suggestions what works | 21:34 |
| tortisedoc_ | lbt : thanks | 21:39 |
| lbt | tortisedoc_: can I trigger a rebuild on that log ? | 21:40 |
| tortisedoc_ | feel frei | 21:40 |
| tortisedoc_ | darn | 21:40 |
| *** tortisedoc_ is now known as tortoisedoc_ | 21:40 | |
| antis | Hi, have just seen SF3 is finally available for FP2. Awesome work, @mal! | 21:40 |
| tortoisedoc_ | time to go to sleep | 21:40 |
| lbt | tortoisedoc_: OK | 21:40 |
| lbt | see the log now | 21:40 |
| lbt | lines around 6s | 21:40 |
| lbt | ulimit -s | 21:41 |
| tortoisedoc_ | line 61: ulimit: stack size: cannot modify limit: Operation not permitted | 21:41 |
| tortoisedoc_ | that one? :P | 21:42 |
| mal | antis: yes, it has been available for a few days | 21:42 |
| lbt | ah | 21:42 |
| tortoisedoc_ | grumble | 21:42 |
| tortoisedoc_ | cant modify the spec file | 21:42 |
| lbt | tortoisedoc_: OK so the build runs as a user and you're exceeding the hard ulimit | 21:42 |
| lbt | rly? | 21:42 |
| tortoisedoc_ | yeah | 21:42 |
| tortoisedoc_ | (from the web interface) | 21:43 |
| lbt | logged in? | 21:43 |
| tortoisedoc_ | no :D | 21:43 |
| lbt | done it for you :) | 21:43 |
| tortoisedoc_ | thanks! | 21:43 |
| lbt | stack size (kbytes, -s) 16384 | 21:44 |
| tortoisedoc_ | its crazy that they get this rustc turd to overflow an 8 MB stack | 21:44 |
| lbt | so it did double it (which is what you asked for and is safer than giving an open hard limit) | 21:44 |
| antis | mal: cool really! i don't have much time - working hard in car industry you know… | 21:44 |
| tortoisedoc_ | thanks again | 21:44 |
| tortoisedoc_ | yes at least locally doubling it seems to do the trick | 21:44 |
| lbt | looks like it's building now | 21:44 |
| lbt | lets see in the morning | 21:44 |
| tortoisedoc_ | of course in the future it might need more | 21:45 |
| tortoisedoc_ | but hopefully not | 21:45 |
| tortoisedoc_ | yea thanks | 21:45 |
| lbt | this is a nasty hack to the core build script so maybe we need a way to do this properly and upstream that | 21:45 |
| antis | mal: is there anything special before upgrading from 2.2.018? | 21:45 |
| mal | antis: no, it should work fine, the usual update method as described in wiki | 21:46 |
| tortoisedoc_ | lbt : I guess there's no way to "parametrize" this safely | 21:47 |
| tortoisedoc_ | (i mean through build job config) | 21:47 |
| antis | mal, ok. then procedure as usual. creating backup just in case… | 21:47 |
| lbt | we're due an upgrade to OBS | 21:47 |
| lbt | this is the 2014 release at the minute :) | 21:48 |
| lbt | so there's a lot of changes afoor | 21:48 |
| lbt | afoot | 21:48 |
| lbt | so when 2.9 drops next january-ish we'll see | 21:48 |
| lbt | if there's not then it's probably a sane thing to push upstream | 21:49 |
| tortoisedoc_ | yeah | 21:51 |
| tortoisedoc_ | also this glibc is pushing the boundaries of entropy evolution :D | 21:51 |
| tortoisedoc_ | lbt : rc/build/i686-unknown-linux-gnu/stage1-std/release/deps -Clink-arg=-Wl,-z,relro,-z,now` (signal: 7, SIGBUS: access to undefined memory) | 22:07 |
| tortoisedoc_ | what's the system ulimit -s? | 22:07 |
| tortoisedoc_ | (ie. not the chroot, the system one) | 22:07 |
| lbt | this is running in a kvm vm | 22:11 |
| lbt | the script you see is running as 'init' | 22:11 |
| lbt | so it's pretty much the kvm system limit | 22:11 |
| lbt | and it has a lot of RAM | 22:12 |
| lbt | this isn't an area I'm really familiar with either | 22:13 |
| lbt | setting this via ulimit -s as root in a script that parents all subsequent activity should work | 22:13 |
| lbt | limits.conf isn't really relevant because we've dropped into a kvm | 22:14 |
| lbt | additionally I don't think ulimit -all would lie | 22:14 |
| lbt | stack size (kbytes, -s) 16384 | 22:14 |
| lbt | I can up it again just to see... | 22:15 |
| lbt | there we are : 32768 | 22:15 |
| tortoisedoc_ | hmm | 22:16 |
| tortoisedoc_ | lbt : im not sure, but the kvm overrides the host's limit? | 22:16 |
| lbt | it runs it's own kernel | 22:17 |
| lbt | so yes | 22:17 |
| lbt | stack size (kbytes, -s) 32768 | 22:18 |
| tortoisedoc_ | so its different in that from the "normal" sb2 kit that ships with the mer sdk | 22:18 |
| lbt | mmm | 22:19 |
| ol | lbt (IRC): What do you mean by "when 2.9 drops next january-ish"? OBS 2.9 was released long ago. It's 2.9.5 already. | 22:19 |
| lbt | this isn't an sb2 build is it ? | 22:19 |
| lbt | ol: I mean in Mer :) | 22:19 |
| lbt | also "hi" :) | 22:19 |
| tortoisedoc_ | lbt : you mean the one on obs? | 22:19 |
| lbt | ol: and thanks for the fwd porting work you've done over the years | 22:20 |
| lbt | I'm going to try and push the sb2 stuff upstream this time | 22:20 |
| lbt | tortoisedoc_: yes | 22:20 |
| ol | lbt (IRC): Mer 2.9? Or Mer OBS 2.9? :-) | 22:20 |
| tortoisedoc_ | ah a sb2 forwarding? that'd be nice :) however I wonder what will break.. | 22:20 |
| lbt | ol: build.m.o will upgrade to 2.9.5+mer patches | 22:21 |
| ol | lbt (IRC): The most difficult part is porting changed to build. OBS itself is quite trivial, I presume. | 22:21 |
| lbt | ol: correct | 22:21 |
| lbt | ol: I have the build changes working now | 22:21 |
| lbt | so it's ported to the sha1 dropped with 2.9.5 | 22:22 |
| ol | I already have ported all changes to build 20180212, but never tested. | 22:22 |
| * tortoisedoc_ dropped sha1 grumble grumble | 22:22 | |
| ol | Oh, they work? Cool! | 22:22 |
| lbt | yep ... I have a running instance of 2.9.5 building against sfos 2.2.1.18 or whatever it was pre 3.0 | 22:23 |
| lbt | some minor glitches in build to resolve but nothing big | 22:23 |
| lbt | and then some functionality we need internally to copy projects without rebuilding them | 22:23 |
| lbt | that might hurt !!! | 22:23 |
| lbt | but it's all looking good | 22:24 |
| lbt | I've also refactored the patches to feature sets | 22:24 |
| lbt | so they're not all messy | 22:24 |
| ol | There are still issues with sb2-specific patches to build: corruption of build target when building locally with "osc build", you have to remove build root directory to make build re-create it. But as build root is creatd from scratch in OBS, this problem does not affect OBS builds. | 22:25 |
| lbt | oh I've not checked that | 22:26 |
| ol | But I didn't test your refactored patches. I was just keeping porting original patches over and over again. | 22:26 |
| lbt | the refactor is more a re-order & squash which gave an empyt git diff - then I ported that | 22:28 |
| lbt | it's still a WIP though - should be a bit tidier next week | 22:29 |
| ol | But you did it against 2014.08.01, right? | 22:29 |
| ol | Why not newer version? | 22:30 |
| lbt | initially against that version to make sure the squashing and re-ordering and jiggling of the patches gave an empty diff | 22:35 |
| lbt | then once I had a clean set of patches I applied them to 20180111 | 22:35 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!