libera/#maemo-leste/ Wednesday, 2022-03-02

Wizzuphoneycomb is assembled02:41
Wizzupshould be able to get it set up tomorrow02:42
Guest18624Hi, yesterday I got the Droid 4 to connect to the GSM network, with some help from you guys. In addition to the instructions on the page https://leste.maemo.org/Status/Phone, this is what I've done:06:34
Guest18624# after adding the beowulf-devel repository,06:34
Guest18624# sudo apt update throws GPG error for beowulf/Extras06:34
Guest18624# easy install of the packages:06:34
Guest18624sudo apt install sphone06:34
Guest18624sudo apt install hildon-connectivity-mobile06:34
Guest18624sudo apt install ofono-scripts06:34
Guest18624# in case the SIM was PIN-protected:06:34
Guest18624startup-pin-query06:34
Guest18624# then connected to GSM network:06:34
Guest18624# immediately received SMS from my carrier06:34
Guest18624# could call and receive calls (but couldn't hear)06:34
Guest18624# 3G mobile data enabled by default06:34
Guest18624 /usr/share/ofono/scripts/enable-modem06:35
Guest18624 /usr/share/ofono/scripts/online-modem06:35
bencohalright, gonna try to upgrade leste here ... what do I need to disable first for it not to reboot? (yeah, I always seem to forget)12:42
uvostouch /etc/no_lg_reboots12:43
bencohthanks :)12:43
uvosbut leste config should do that for you12:43
uvos(if your version is recent enough)12:43
bencohdoubt it is12:44
Wizzupalso reboot after that file12:45
Wizzuphoneycomb is up and running12:45
Wizzupnow I just need to migrate the rpi systems12:45
bencohreboot after the touch? alright12:45
Wizzupywesa12:45
Wizzupyes12:45
bencohI was about to press enter :)12:45
bencohyay, looks like it worked12:59
bencohlet's see if it reboots12:59
bencoh(I didn't dist-upgrade though)12:59
bencohoh, is dist-upgrade safe on leste?12:59
uvosyes13:00
uvosand sometimes its nesscary13:00
uvosfreemangordon: log dosent really show anything13:04
uvosuvos.xyz/maserati/sphone-abook.log13:04
bencohinteresting ... I got a text getty prompt instead of Xorg after upgrade without dist-upgrade13:07
bencohI guess kernel version doesn't match xorg driver?13:07
bencoh(nice that it doesn't crash at boot)13:08
uvosuname -a, xorg.log?13:08
bencoh5.10.3013:08
uvosyes wrong kernel13:08
bencohthought so13:08
bencohnow, to upgrade it from console without usbnet ....13:09
uvoswpa_cli13:09
bencohyeah13:10
uvosfreemangordon: so to repduce: have a eds database, any kind with some contacts. make it default. build sphone from git,  have it load contacts-ui-abook instead of -exec, open the dialer, click contacts.13:12
Wizzupbencoh: I think icd might work without x13:17
Wizzupin any case, yes, you must dist-upgrade13:17
uvosicd has pretty piss poor performace on d4 without x13:18
uvosbecause it ussualy fails at least once trying to connect13:18
uvosand then you would have to wait a long time for it to try again13:18
Wizzupyes, that is a kernel bug13:18
Wizzupnot icd2 bug13:18
uvossure13:18
uvosbut in pactice it just dosent work13:18
Wizzupbtw, other topic13:19
uvosif you cant use th ui13:19
WizzupI was thinking we should make or revamp some simple roadmap that we all agree on, on bugs and/or features to work on13:19
WizzupI have a few people who are interested in helping out but I have trouble pointing them at specific things to pick up13:19
Wizzupour issue list is kinda large and not ordered by priority in any way13:19
uvosalso imo it kind of is a icd2 "bug"13:19
uvosit just dosent try hard enough. the connection can fail for any reason incl stuff like temporary interferance13:20
uvosit should just try again13:20
Wizzupright it defers to wpa_supplicant on that13:20
uvosWizzup: not sure what the difference is between icd2 driving wpa and wpa_cli driving wpa13:21
uvos(wpa_cli never ever fails to connect on d4)13:21
Wizzuppretty sure the first time fails13:21
Wizzupand then it just retries13:21
uvosnot always13:21
Wizzupdriven by wpa_supplicant standalone logic13:21
uvosand right the problem is icd2 dosent try again13:21
uvosim not sure why but it just gives up after one try13:21
uvosif you connect with wpa_cli it just tries again and suceeds13:22
uvosthis is also true if you start wpa_supplicant with -c13:22
uvoslooks like i got another d4 display cable to die on me :(13:59
Wizzupweird, how does that happen14:00
Wizzupdo you regularly open them up?14:00
uvosno idea14:01
uvossure regularly14:01
uvosi mean i use it as a primary device14:01
uvosthat comes with lots of openings14:01
WizzupI can send you something, if you let me know, I am leaving friday morning14:01
uvosnah its fine14:02
uvosi still have 2 others14:02
uvosbut at some point if you find a d4 thats broken in a different way sure14:02
Wizzupprobably about 12 atm, but those are in the us14:03
Wizzuplooks like 5 out of 6 mz617 are in a good state14:03
Wizzupone had a power button that looks like someone *really* wanted to power it off :p14:03
uvos:P14:03
Wizzupok so the honeycomb is set up, just need to move the build systems there14:04
Wizzupmight need to re-install debian or something, the pi rootfses might be too pi specific, not sure14:04
Wizzupbtw, any ideas on the roadmap thing?14:04
uvosi dont think its a bad idea per say14:04
uvosbut idk how you would organise it14:04
Wizzupwiki page, with links to issues, and the wiki page could be ordered by general goals and then perhaps with some dates as to when we'd -like- to do it14:05
humpelstilzchen[But people just work on whatever they want to, not sure if a roadmap helps in pinning more important issues14:05
uvosi dont think deadlines are particularly usefull14:05
uvospinning more important tasks helps14:05
uvostimelines dont14:06
uvosimo14:06
Wizzuptimelines are not to push pressure, of course14:06
Wizzuphumpelstilzchen[: well, I think it would be good to have a bit more direction in that sense14:06
Wizzupdoesn't mean people can't do whatever they want :)14:06
Wizzupbut it could help with "how much do we think we care about feature X vs bug or feature Y" when it comes up14:07
Wizzupwhich often happens14:07
uvossure14:07
uvosmostly https://github.com/maemo-leste/hildon-status-menu/pull/314:07
uvosI want https://github.com/maemo-leste/libmatchbox2/pull/814:08
uvosprs https://github.com/maemo-leste/hildon-input-method/pull/714:08
uvosrewieved https://github.com/maemo-leste/hildon-desktop/pull/1814:08
uvos:P14:08
Wizzuphonestly I love track of these things and just forget, so it's good to remind me14:08
uvosyours it quite new14:08
uvosits mostly freemangordon thats really slow14:08
uvosahm14:08
Wizzuplol I don'14:09
Wizzupt think so14:09
Wizzupbut ok14:09
Wizzupon the at-spi pr, could you clarify what was tested?14:09
Wizzuplike, gtk3 apps? does it work in browser (html) input fields?14:09
uvosfirefox-esr, various qt apps14:09
uvosyes it works everywhere14:09
uvosalso gtk314:09
Wizzupdoes it support context awareness?14:10
Wizzuplike, read current text of input?14:10
uvosit could (sometimes app implementation is uneven) but dosent rn14:10
uvoswrt slow reviews, some of those sit since nov 2021 i think thats to long. just give me commit access at that point.14:13
Wizzupit's also just lack of time in some cases14:13
Wizzupwhat would also help me is a way to test some of it, for example the status menu notifier thing14:14
uvosim not saying it malicous14:14
Wizzupwhat should I install to test it, see how it works as expected?14:14
uvosanything that creates a status menu item :P14:14
uvos(various media players, any im program etc)14:15
uvosi used telegram and cantata and some others14:15
uvoskonversation i think14:15
Wizzupor just a screenshot or two would also help imho14:16
Wizzupbut yeah not saying that's the reason :)14:16
Wizzupjust a more general thing14:16
uvoshmm14:21
uvoslooks like the cable was damaged by sand14:21
uvosdont go to the beatch14:21
Wizzupheh14:24
Wizzupthe beaches I go to are stone beaches, so should be ok14:24
lelMerlijnWajer closed a pull request: https://github.com/maemo-leste/hildon-desktop/pull/18 (launcher: quote command sent to terminal emulator)14:38
Wizzupfreemangordon: I merged this pr, but then realised that I think you're the maintainer, so please check if it's all OK14:39
Wizzupfreemangordon: I think I wrote that code, and I think it looks ok, but please lmk14:40
Wizzupactually I'll just build it14:40
Wizzupit's a clear bugfix for my code14:40
freemangordonuvos: abook debug does not seem to be enabled15:03
freemangordonshould look like this https://pastebin.com/9dSmPR5Z15:05
Wizzupfreemangordon: also, what do you think of this: https://github.com/maemo-leste/libmatchbox2/pull/8/commits/fbe9670b3509696f0464d3d9450384063135ef0515:05
Wizzup( https://github.com/maemo-leste/libmatchbox2/pull/8 )15:05
freemangordonI am not sure I understand what is this about, so feel free to either merge or drop15:06
freemangordonI mean - I lack the knowledge to judge if this is the correct fix15:07
freemangordonuvos: re slow review - I would say that our priorities differ sometimes15:09
freemangordonalso, I think you are well aware how much time I spend on Xorg DDX/omapdrm15:09
freemangordonif you feel you can do that better and faster, please, be my guest15:10
freemangordonnot to say I wasted time chasing regressions in mce caused by use, spent time on sdl, etc15:10
freemangordonso I don;t really think it is fair to call me "slow"15:11
freemangordons/use/U15:11
uvosi did not cause any regesions in mce....15:12
freemangordonsure you did, but lets not go into that, it does not really matter15:13
uvosno15:13
freemangordonwell, ok15:13
uvosthose bugs existed in fremantle too15:13
freemangordonyou made no mistakes, ever15:13
uvosi dident say that15:14
freemangordonok, ok15:14
freemangordonplease, have a look at pastebin ^^^15:14
uvosidk how to enable debug output in abook then15:14
uvosthe envvar you posed is not sufficent15:14
freemangordonsee pastebin ^^^15:14
uvosyes i used that15:15
freemangordonuser@devuan:~/maemo/git/abook/osso-abook$ G_MESSAGES_DEBUG=all OSSO_ABOOK_DEBUG=all ./lib/test_contact_chooser15:15
uvosyes both of those where set15:15
freemangordonweird15:15
* freemangordon checks something15:15
freemangordonuvos: if I install sphone, will it use osso-abook? or I shall build from the repos?15:16
uvosno15:16
uvosyou have to build from repos15:16
uvosand make it load the moduel as stated above15:16
freemangordonabove?15:16
uvos[13:12] <uvos> freemangordon: so to repduce: have a eds database, any kind with some contacts. make it default. build sphone from git,  have it load contacts-ui-abook instead of -exec, open the dialer, click contacts.15:17
uvosthe modules to be loaded are in /usr/share/sphone.ini15:17
freemangordonI am not sure I understand "have it load contacts-ui-abook instead of -exec"15:17
* freemangordon pulls sphone15:18
uvoslook at  /usr/share/sphone.ini15:18
uvosshould be clear then15:18
freemangordonok15:18
uvos /usr/share/sphone/sphone.ini15:18
freemangordonok15:19
freemangordonuvos: sorru, it is still not clear to me. shall I modify ContactsUiExec section?15:24
uvosno15:24
uvostheres not sutch section15:24
uvosModules=15:25
freemangordon[ContactsUiExec]15:25
freemangordon# Application to call to open contacts15:25
freemangordonContactsExec=/usr/bin/gnome-contacts15:25
uvos+contacts-ui-abook15:25
uvos-contacts-ui-exec15:25
freemangordonok15:25
uvosright forgot about that15:25
uvosanyhow15:25
uvosthe module15:25
freemangordonok, got it15:25
freemangordonuvos: I do;t think abook code is called at all15:27
freemangordon*don;t15:27
uvoswell it shows the window15:27
freemangordonI see something "a..."15:28
freemangordonkeep in mind I don't have phone contacts here15:28
freemangordonbut that should not make any difference15:28
uvosi click on contacts15:28
uvosabook opens a window15:28
uvos"Choose contact"15:28
uvos(no contacts)15:28
freemangordonno, I have "a..." as a contact here15:29
uvossyncevolution --print-databases?15:29
freemangordon-bash: syncevolution: command not found15:30
freemangordonI have EDS only15:30
freemangordonshall I install that?15:30
uvosyou can probubly have eds print the databases too somehow15:30
uvossure15:30
freemangordonI'll install syncevolution15:30
freemangordonhttps://pastebin.com/jwtNnr1215:31
uvosright15:32
uvosso your default is the same as system-address-book15:32
uvosprobubly you need to create some other database to make it break15:32
uvos(and make it default)15:32
freemangordonneed a second15:33
freemangordonI don;t see the book selection code called15:33
* freemangordon fires gdb15:34
freemangordonuvos: you are missing a call to  osso_abook_init()15:41
uvosfreemangordon: ok thanks15:42
freemangordonwait15:42
freemangordonit will fix missing logs15:42
freemangordonlemme test it here first15:42
freemangordonuvos: you better call   osso_abook_debug_init() instead of osso_abook_init()15:44
uvosok15:44
freemangordonosso_abook_init() requires osso_context I am not sure you can get15:44
uvoswell one could be created just for this module15:45
uvos(in the module)15:45
uvosbut ok15:45
freemangordonno need I think15:45
freemangordonlets first see if we can get sane logs15:46
uvosanyhow15:46
uvosafk15:46
freemangordonuvos: you should keep config in /etc, not in usr/share15:49
freemangordonit gets overwritten on reinstall15:49
WizzupI think it is some systemish so put configs in /usr/share15:54
Wizzuplike X also moved some stuff there15:54
Wizzupmaybe it's like system provided vs user set or something15:54
Wizzupsystemdism*15:54
freemangordonaha15:54
freemangordonbut, it gets overwritten without warning15:54
_uvos_freemangordon: yes as is intended, according LFHS /usr/share contains distro configuration /etc contains system wide administrator configuration and ~ contains user configuration15:58
_uvos_freemangordon: for sphone /usr/share contains defaults if it cant read a config file from ~/.sphone15:59
_uvos_but should be better documented15:59
freemangordonah, I see16:00
freemangordonuvos: also, you *must* call  hildon_gtk_init() and not gtk_init() on leste16:07
freemangordonwell, on hildon16:07
freemangordonsee http://maemo.org/api_refs/5.0/beta/hildon/hildon-Main.html16:08
freemangordonthis https://pastebin.com/bRR5YHuC16:13
freemangordonbut, make sure module init is called before *any* gtk function is called16:13
* Wizzup has pine64 keyboard case16:59
buZzi notice some 'broken' pinephones are hitting marktplaats.nl16:59
uvosthats not going to work17:00
uvossphone stricktly has no odering restrcitons on modules17:00
uvosso have to do this some other way17:00
Wizzupthat's going to be tricky17:00
freemangordonuvos: so, why gtk functions are called in module init time?17:01
freemangordon*at17:01
uvosbecause the main process inits gtk17:01
freemangordonthat's fine17:01
freemangordonit is ok to call gtk_init17:01
uvos(when required)17:01
uvos1646233641 <freemangordon> uvos: also, you *must* call  hildon_gtk_init() and not gtk_init() on leste17:02
uvos?17:02
freemangordondid you look at link and the patch?17:02
uvos+        hildon_init();17:02
uvosthis is supplement to gtk_init?17:02
freemangordonyou either call hildon_gtk_init() and not gtk_init() or you call hildon_init() *after* gtk_init()17:02
freemangordonyes17:02
uvosok hmm17:03
uvosstill this means the main process depends on libhildon17:03
uvosnot great either17:03
uvosill have to think of something17:03
freemangordonno, you can call that from abook module17:03
uvosno17:03
freemangordonwhy?17:03
uvossome of the other modules also use libhildon17:04
uvos(so far to no ill efect)17:04
freemangordonah17:04
freemangordonok, but how d o you init gtk2 then?17:04
uvosi gues just using hildon buttons and sutch happens to be fine17:04
freemangordonyeah17:04
freemangordonyou still have to call gtk_init at exactly one place17:04
uvosright it dose that17:05
freemangordonand before any gtk function is called17:05
uvosin glibloop or qtloop (depending on if you want qt support also)17:05
freemangordonwell, you should find a way to call hildon_gtk_init then instead of gtk_init when running on hildon, somehow17:06
uvosi assume libhildon dosent allow you to check if its initalized17:06
uvosotherwise the first module to need it could run hildon_init17:06
freemangordonuvos: how do you guarantee that gtk is inited?17:07
freemangordonglibloop is a module?17:07
uvosyes but no glibloop17:07
uvosits special17:07
freemangordonah,17:07
uvosits a initalization module17:07
freemangordonwell then you need either special hildonloop17:07
uvossure17:08
uvoscould do that17:08
uvosbut would rather avoid ofc17:08
uvos(if possible)17:08
freemangordonor dload("libhildon") and call hildon_gtk_init on success17:08
Wizzupor make the modules ordered?17:09
uvosew :P17:09
freemangordonor this, yeah17:09
uvosthe dload might work17:09
uvoscreating a hildon module is annoying17:09
uvossince you then also need a hildonqt module too17:09
freemangordonI am not really sure what happens if you call iy more than  once17:10
freemangordon*it17:10
freemangordonI guess nothing bad17:10
uvosmight leak some ram17:10
* freemangordon chacks the code17:10
uvosill maybe look at it later17:10
freemangordon*checks17:10
Wizzuphumpelstilzchen[: hm, my keyboard only worked for a bit, and now it doesn't17:12
Wizzuphumpelstilzchen[: any idea how I can debug that? (pp)17:12
freemangordonuvos: https://github.com/maemo-leste/libhildon/blob/47cf0dc1c34e8d931f6644f5324d7ebb1effe763/hildon/hildon-main.c#L10217:12
Wizzup[   52.193516] kb151 2-0015: Charger read failed - MCU returned 0xff17:12
Wizzup[   52.199690] kb151 2-0015: Failed to initialize the charger17:12
Wizzup[   57.335600] kb151 2-0015: Charger is initialized17:12
freemangordonnothing bad will happen17:12
humpelstilzchen[Wizzup: not really, mine just worked17:12
freemangordonoh, actually it is bad17:12
freemangordong_critical()17:12
freemangordonthis will abort17:12
uvosright17:12
uvosmaybe, we dont need it to be g_critical17:13
freemangordonyeah17:13
uvosit dosent sound critical17:13
humpelstilzchen[Wizzup: try to press on the connection again with some force17:13
Wizzuphumpelstilzchen[: right ok17:13
Wizzupit seems to charge though17:13
freemangordonuvos: but it calls gtk_init too17:13
uvoshmm?17:14
freemangordonthis is reallt tricky as maemo qt module calls hildon_gtk_init() too, iirc17:14
uvosoh hmm17:14
freemangordonhttps://github.com/maemo-leste/libhildon/blob/47cf0dc1c34e8d931f6644f5324d7ebb1effe763/hildon/hildon-main.c#L14017:14
freemangordonnot 100% sure about qt though17:14
uvosso far this works regardless17:14
uvosif so17:14
uvossince sphone with qtloop inits qt17:15
uvosand using it works fine17:15
uvoseven thoug it also inits gtk17:15
freemangordonbut hildon works by chance17:15
uvosright17:15
uvosi mean with regards to mameo qt patform17:15
freemangordonanyway, the patch I posted ^^^ is good enough for testing17:16
freemangordonlike, I see a correct list of contacts here with it17:16
uvosok17:16
freemangordonalso, please consider using https://github.com/maemo-leste/osso-abook/blob/master/lib/test-contact-chooser.c to experiment17:16
uvosfreemangordon: btw please consider droping -DMAEMO_GTK=1 from gtk17:18
uvosnot setting this is supposed to make it use non hildonised gtk17:19
uvosbut this dosent work, and apears to be simply missing the maemo5 version of gtk17:19
Wizzupoh, this is patch this one guy did?17:19
uvosWizzup: no idea17:19
WizzupI think this is for the whole gtk build17:19
Wizzupnot for individual gtk apps17:19
Wizzupjust to be clear17:19
uvosWizzup: so if you build an app without this set17:19
uvosWizzup: it fails to compile for lack of some hildon specific headers17:20
uvoswhich is quite annoying building gtk2 apps17:20
Wizzupthat's silly, it should default to that when gtk2 is built with it on17:20
Wizzupweird that we don't see it for any of our other gtk apps?17:20
Wizzupis this some cmake thing where you don't have the pkgconfig stuff?17:21
uvosthe ones we imported from fremantle all have this17:21
uvosidk if we build any non hildon gtk2 apps17:21
uvosi dont think we do (besides sphone)17:21
uvosWizzup: wrt cmake, dunno, point is nothing compiles without this define17:22
Wizzupuvos: right, but I haven't run into it anywhere17:24
Wizzupis why I ask17:24
freemangordonneither do I17:24
freemangordonI would say something pkgconfig is missing17:24
freemangordonuvos: hildon-1.pc defines that17:27
uvosright17:27
uvosbut why should gtk applications that dont use hildon-1 use this17:27
uvos /libhildon17:27
freemangordonwhat applications are thise?17:27
freemangordon*those17:27
uvosany gtk2 application17:27
freemangordonlike?17:27
uvosin this case sphone17:27
uvoscome on17:27
freemangordonI don;t know what do you include17:27
uvosgimp :P17:27
freemangordonwhat is the error?17:28
uvosill look into it later, i ran into this when first compiling sphone17:28
freemangordonok17:28
uvos(when it was a pure gtk2 applicaion)17:28
lelMerlijnWajer closed a pull request: https://github.com/maemo-leste/libmatchbox2/pull/8 (Drop support for _MOTIF_WM_HINTS)18:40
Wizzupuvos: I guess this also needs h-d rebuild18:42
uvosyes18:55
uvosimo it might make sense to just pull libmatchbox2 and clutter into hildon-desktops tree18:55
uvossince both of those are special versions just for h-d that cant really be used as real libs anymore18:56
Wizzupuvos: might make sense yeah, but the current setup works ok for me22:04
Wizzupbut I agree it might be better otherwise (but maybe a bit senseless currently)22:04
freemangordonyeah, I think we have more important things to do first22:05
Wizzupright, about that roadmap22:10
freemangordonthat was a nasty one https://github.com/maemo-leste/modest/commit/336605ba0dd718a7a28dbf2687c0b7029d122f7b22:15
freemangordondidn;t test, but the same issue exists on fremantle22:15
Wizzupnice find!22:22
Wizzupcalebtheythem[m]: calebtheythem[m4: ping, which one is your acc?23:06
calebtheythem[m]wizzup: the first one you mentioned, i think it's caleb_m on IRC?23:07
calebtheythem[m]the second one is a dead account23:07

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