On Mon, Nov 26, 2018 at 03:57:25PM +0100, Tomasz Kłoczko wrote:
On Mon, 26 Nov 2018 at 15:19, Tom Gundersen <teg(a)jklm.no>
wrote:
[..]
>>> What Fedora version? Ideally provide specific rpm versions.
>>> dbus-in-F29 != dbus-in-F30 now.
>>
>> I’m talking about F30 recent change in which has been implemented switch to
dubs-broker.
>
> Thanks for the report, and sorry for the inconvenience.
np .. when tree is chopped chops are flying around :)
> There was indeed a bug in the dbus-broker spec file, which we now fixed with
version 16-7 (should land in rawhide any minute).
IMO it would be good to learn something out of that small fault
because few thing went really odd way.
1) if dbus service crashes/is not availaible temporary IMO it wold be
good to prepare whole desktop apps code to not crash but handle dbus
disconnection and maybe display centered message that it is not
possible to connect to dbus. Crashing everything looks really *bad*.
3) any other dependency on running dbus service should be IMO closely
investigated and if something is just crashing it should be
changed/redesigned to handle this to at least log that to system logs
(nothing like this after all was possible to find in systemd journal
or rsyslogd logs).
Feel free to provide patches. There was 15 years to fix it.
Alternatively, dbus-broker may store fds in systemd and serialize state
over restarts.
--
Tomasz Torcz "Funeral in the morning, IDE hacking
xmpp: zdzichubg(a)chrome.pl in the afternoon and evening." - Alan Cox