2016-09-03 23:34 GMT+02:00 oz <[email protected]>: > On Fri, 2 Sep 2016 10:53:45 +0200 Alexander Sack <[email protected]> wrote: >> >> tags 827296 + moreinfo >> severity 827296 normal >> thanks >> >> Hi, >> >> this seems to be a feature. Seems you were able to resolve this issue? >> Anything you think that should be done here? >> >> Network Manager also has a similar wait job. timeout there is 30 >> seconds. connman just seem to have a higher default timeout in code >> (120 seconds). >> >> You could customize the job with --timeout=30 or we could use that as >> the default in the package if we feel there is strong reason to >> believe that majority of debian users will want the shorter timeout. >> >> Let me know if you are happy with the ability to tweak by yourself... >> >> Thanks, >> >> - Alexander > > > Hi Alexander, > > thanks for responding. The problem is twofold. One problem is, that connman > is buggy with libgnutls30 >= 3.5.3-2. Because of this bug a global, default > timeout is triggered, located in Debian's /etc/systemd/system.conf as > "DefaultTimeoutStartSec=90s". This slows down *every* boot unnecessary. I > was able to resolve this bug only by a forced downgrade to 3.5.2-2. This bug > should be fixed.
I am not sure I understand this one... do you know what the problem is that triggers the start delay? Does connman crash? Does the dbus service not come up/respond etc.? > > The second aspect is, that I don't use TLS-Tunnels or > Hotspot-Captive-Portals. A new option in Debian's connmand binary to switch > off TLS at boottime would be helpful against TLS-related bugs & security > holes and would give back the control to the user. > > Thank you.
