System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
<freemangordon>
Wizzup: ok, on fremantle, mc is started from xsession script, /etc/X11/Xsession.d/60mission-control, however, I don;t think we shall start it by hand
<freemangordon>
the issue is that tp_proxy_prepare_async() on account manager never finishes (callback is never called)
_fab has quit [Quit: _fab]
pere has quit [Ping timeout: 244 seconds]
<freemangordon>
ugh:
<freemangordon>
2025-05-26T09:21:48.840058+03:00 devuan dbus-daemon[2606]: [session uid=1000 pid=2606] Activating service name='org.freedesktop.Telepathy.AccountManager' requested by ':1.33' (uid=1000 pid=3244 comm="/usr/bin/hildon-status-menu ")
Livio has quit [Remote host closed the connection]
<uvos__>
Wizzup: thanks
Livio has joined #maemo-leste
apac has quit [Ping timeout: 276 seconds]
f_|DEPRECATED has quit [Remote host closed the connection]
apac has joined #maemo-leste
canto_ has joined #maemo-leste
apac has quit [Ping timeout: 276 seconds]
<freemangordon>
(hildon-status-menu:3182): tp-glib/accounts-DEBUG: 13:05:57.240: _tp_account_manager_got_all_cb: Failed to get account manager properties: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
<freemangordon>
(hildon-status-menu:3182): tp-glib/proxy-DEBUG: 13:05:57.240: tp_proxy_invalidate: 0x55f3a9dafb40: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
<freemangordon>
(hildon-status-menu:3182): tp-glib/proxy-DEBUG: 13:05:57.240: tp_proxy_signal_connection_proxy_invalidated: 0x55f3a9fbaee0: TpProxy 0x55f3a9dafb40 invalidated (I have 0x55f3a9dafb40): Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
<freemangordon>
(hildon-status-menu:3182): tp-glib/proxy-DEBUG: 13:05:57.240: tp_proxy_poll_features: 0x55f3a9dafb40: invalidated, ending all requests
<Wizzup>
freemangordon: we can revert the commit and build
arno11 has joined #maemo-leste
<arno11>
freemangordon: ping
<arno11>
dsc_: will try, but not so easy to reproduce from the vm imo. atm, ootb, my tg account can't be enabled/online on boot. if i enable it with few steps after boot (like killing mission control, hsm and addressbook), the account itself works but conversations crashes if i open a chat window
<arno11>
basically, if mission control restarts, conversations tg chat windows crash. that's the main issue for my use case
<arno11>
freemangordon: sorry, maybe that's a bit late to troubleshoot tp/telegram
<freemangordon>
yeah, lets do tomorrow
<freemangordon>
Wizzup: didn't help, will have to debug
akossh has joined #maemo-leste
<arno11>
freemangordon: yep
<freemangordon>
Wizzup: I wonder if I shall waste time or wait for excalibur
<sicelo>
SIP? at least as far as daedalus is concerned, i would say anything that's not a regression, i.e. if we do not know for sure that it was working before - don't block daedalus on it. rather, we can fix as we go, so hpeuflly by excalibur
<arno11>
it was working fine before
<arno11>
(chimaera)
<arno11>
with sphone, vcm
<freemangordon>
mhm
<arno11>
btw i just tried an incoming sip call, sphone crashed after few seconds and i can't select a backend anymore: so no gsm call too. need to reboot
apac has quit [Ping timeout: 245 seconds]
arno11 has quit [Quit: leaving]
apac has joined #maemo-leste
arno11 has joined #maemo-leste
<Wizzup>
freemangordon: either way is ok with me
<Wizzup>
freemangordon: is there a newer version in excalibur?