Package: connman
Version: 1.32-0.1
Followup-For: Bug #827296

Dear Maintainer,

I can confirm Bohdan's report. With the newer libgnutls30 3.5.3-2 I get the 
(default) timeout of 90 s from conman.service (defined in 
DefaultTimeoutStopSec=90s):

journalctl -u connman
[...]
Aug 23 09:18:55 amy systemd[1]: Starting Connection service...
Aug 23 09:20:25 amy systemd[1]: connman.service: Start operation timed out. 
Terminating.
Aug 23 09:20:25 amy systemd[1]: Failed to start Connection service.
Aug 23 09:20:25 amy systemd[1]: connman.service: Unit entered failed state.
Aug 23 09:20:25 amy systemd[1]: connman.service: Failed with result 'timeout'.
Aug 23 09:20:25 amy systemd[1]: connman.service: Service hold-off time over, 
scheduling restart.
Aug 23 09:20:25 amy systemd[1]: Stopped Connection service.
Aug 23 09:20:25 amy systemd[1]: Starting Connection service...
Aug 23 09:20:36 amy systemd[1]: Started Connection service.
Aug 23 09:20:36 amy connmand[1758]: Connection Manager version 1.32
Aug 23 09:20:36 amy connmand[1758]: Checking loopback interface settings  
[...]

With the older 3.5.2-2 the timout-problem disappears. Thank you Bohdan!

Kind regards

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages connman depends on:
ii  dbus                 1.10.10-1
ii  init-system-helpers  1.42
ii  libc6                2.23-5
ii  libdbus-1-3          1.10.10-1
ii  libglib2.0-0         2.48.1-3
ii  libgnutls30          3.5.3-2
ii  libreadline6         6.3-8+b4
ii  libxtables11         1.6.0-3
ii  lsb-base             9.20160629

Versions of packages connman recommends:
pn  bluez          <none>
pn  ofono          <none>
ii  wpasupplicant  2.5-2+v2.4-2

Versions of packages connman suggests:
pn  indicator-network  <none>

-- no debconf information

Reply via email to