01:02 <Wizzup> dsc_: you will get some x11 window msg

01:02 <Wizzup> I can check when I am home

01:06 <Wizzup> actually, here https://github.com/maemo-leste/hildon-control-panel-personalisation/blob/master/personalisation_app.c#L264

01:06 <Wizzup> so I think you get a x11 client message with atom _GTK_READ_RCFILES

01:38 <Wizzup> dsc_: I can help you with the qt code for this

08:52 <dsc_> Wizzup: thanks

10:23 <humanbeta> Bug report Pinephone: Alarm of clock app does not make sound., there is also old crash bug in time setting. User Guide App crash in start. Calendar Widget works, but disappear if you touch it.

12:50 <uvos__> Wizzup: hmm indeed something broke allarms

12:50 <uvos__> you cant set a ringtone anymore nor activate a alarm in its dialog

12:50 <uvos__> you can activate the alarm in the list

12:50 <uvos__> and alarms where you set a ringtone in the past still have it set

12:51 <uvos__> (but you cant change it)

14:16 <Wizzup> hm, I used the alarms this morning

14:16 <Wizzup> I think

14:16 <uvos__> sure and it works as long as you have old alarms to use

14:16 <uvos__> you cant set new ones and assing them a ring tone

14:17 <uvos__> (or change the ring tone of old ones)

14:19 <Wizzup> ah

14:27 <Wizzup> sicelo: the modem also disappeared on my d4 now

14:27 <Wizzup> it didn't come back automatically

18:53 <sicelo> Wizzup: maybe power related, no idea really

18:56 <sicelo> freemangordon: did you see my mail to ofono M-L?

18:57 <Wizzup> sicelo: hm, I think probably not, but could be

18:58 <sicelo> what i am not sure about is: where/how can i cache the operator name while inside `reg_status_ind_cb` function, such that it's available in `name_get_resp_cb` to be able to use it if the normal way to get operator name failed?

19:00 <sicelo> Wizzup: yeah, tbh I'm not too convinced about power being at fault. since it's not like the device then dies shortly after. so even if it was a brownout, i'd expect the modem to at least try to probe again when things stabilize

19:02 <Wizzup> well, I also have a new battery which has much more charge

19:02 <Wizzup> (and it did happen before the new battery too)

19:02 <sicelo> ah, that helps a lot to rule it out

19:02 <Wizzup> I'm still calibrating the battery

19:05 <sicelo> freemangordon: i tried to cache the operator name in nitz_name of the nd struct inside reg_status_ind_cb. but this struct isn't available in name_get_resp_cb.

19:05 <sicelo> i

19:05 <sicelo> i

19:06 <sicelo> i'm not sure if there's another way, otherwise i guess i have to extend one of the functions to take an extra argument? just worried if i do so, i don't break other things, especially the parameters passed around the callbacks

23:59 <uvos> i also find the brownout theroy hard to belive for another reason: i used the d4 with android alot, and i never found the modem to be flaky at all.

23:59 <uvos> so if it dissapears when the battery is low, android musst be really really good at hideing this fact and bringing it back fast somehow