boltctl crashed with signal 5

[Rico Landefeld]

I issued `boltctl list` on the command line and got the following error:

```
 Could not create client: Fehler beim Aufruf von StartServiceByName für org.freedesktop.bolt: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.bolt': timed out (service_start_timeout=25000ms)
fish: 'boltctl list' durch Signal SIGTRAP (Verfolgungs- oder Haltepunkt erreicht) beendet
```

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: bolt 0.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 12 11:47:26 2018
ExecutablePath: /usr/bin/boltctl
InstallationDate: Installed on 2017-03-30 (377 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
ProcCmdline: boltctl list
Signal: 5
SourcePackage: bolt
StacktraceTop:
 ()
 __libc_start_main (main=0x55e1cc7fcb00, argc=2, argv=0x7ffea1e3f488, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffea1e3f478) at ../csu/libc-start.c:310
 ()
Title: boltctl crashed with signal 5
UpgradeStatus: Upgraded to bionic on 2018-03-25 (17 days ago)
UserGroups: adm cdrom davfs2 dip docker lpadmin lxd plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop: main (argc=<optimized out>, argv=<optimized out>) at ../cli/boltctl.c:642

[Sebastien Bacher (seb128)]

Thank you for your bug report. It looks like the service is segfaulting for you, could you
- install https://launchpad.net/ubuntu/+source/bolt/0.2-0ubuntu1/+build/14508460/+files/bolt-dbgsym_0.2-0ubuntu1_amd64.ddeb
- start gdb on https://launchpad.net/ubuntu/+source/bolt/0.2-0ubuntu1/+build/14508460/+files/bolt-dbgsym_0.2-0ubuntu1_amd64.ddeb to get a backtrace (details in https://wiki.ubuntu.com/DebuggingProgramCrash)

[Rico Landefeld (rico.landefeld)]

Updated crash file with debug information.

[Rico Landefeld (rico.landefeld)]

Might be related: bolt.service unable to start:
Apr 13 15:28:14 pirx boltd[23052]: bolt 0.2 starting up.
Apr 13 15:28:14 pirx boltd[23052]: config: loading user config
Apr 13 15:28:14 pirx boltd[23052]: store: loading devices
Apr 13 15:28:14 pirx boltd[23052]: [ce010000-0092 ] store: loading device
Apr 13 15:28:14 pirx kernel: boltd[23052]: segfault at 0 ip 00007efd518e45a1 sp 00007fffa5aa3ce8 error 4 in libc-2.27.so[7ef
Apr 13 15:28:14 pirx systemd[1]: bolt.service: Main process exited, code=dumped, status=11/SEGV
Apr 13 15:28:14 pirx systemd[1]: bolt.service: Failed with result 'core-dump'.
Apr 13 15:28:14 pirx systemd[1]: Failed to start Thunderbolt system service.
-- Subject: Unit bolt.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit bolt.service has failed.
--
-- The result is RESULT.
Apr 13 15:28:14 pirx systemd[1]: bolt.service: Service hold-off time over, scheduling restart.
Apr 13 15:28:14 pirx systemd[1]: bolt.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit bolt.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Apr 13 15:28:14 pirx systemd[1]: Stopped Thunderbolt system service.
-- Subject: Unit bolt.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit bolt.service has finished shutting down.
Apr 13 15:28:14 pirx systemd[1]: bolt.service: Start request repeated too quickly.
Apr 13 15:28:14 pirx systemd[1]: bolt.service: Failed with result 'core-dump'.
Apr 13 15:28:14 pirx systemd[1]: Failed to start Thunderbolt system service.
-- Subject: Unit bolt.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit bolt.service has failed.
--
-- The result is RESULT.

[Rico Landefeld (rico.landefeld)]

Core dump of boltd crash.

[Sebastien Bacher (seb128)]

Thanks, backtrace obtained from the coredump

"#0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:62
#1 0x00007f412412ff5b in g_log_writer_journald (
    log_level=log_level@entry=G_LOG_LEVEL_CRITICAL,
    fields=fields@entry=0x55cee82c8cb0, n_fields=<optimized out>,
    user_data=user_data@entry=0x0) at ../../../../glib/gmessages.c:2529
#2 0x000055cee7fd897b in bolt_log_journal (ctx=0x55cee82c8c70,
    log_level=G_LOG_LEVEL_CRITICAL, flags=<optimized out>)
    at ../boltd/bolt-log.c:520
#3 0x000055cee7fd1a04 in daemon_logger (
    level=level@entry=G_LOG_LEVEL_CRITICAL,
    fields=fields@entry=0x7ffeb9682b00, n_fields=n_fields@entry=4,
    user_data=user_data@entry=0x7ffeb96831f0) at ../boltd/bolt-daemon.c:82
#4 0x00007f412412e7de in g_log_structured_array (
    log_level=G_LOG_LEVEL_CRITICAL, fields=0x7ffeb9682b00, n_fields=4)
    at ../../../../glib/gmessages.c:1970
#5 0x00007f412412ec7c in g_log_default_handler (
    log_domain=log_domain@entry=0x7f4123b26bdb "GLib-GObject",
    log_level=log_level@entry=G_LOG_LEVEL_CRITICAL,
    message=message@entry=0x55cee82c4140 "g_enum_get_value_by_nick: assertion 'nick != NULL' failed", unused_data=unused_data@entry=0x0)
    at ../../../../glib/gmessages.c:3158
#6 0x00007f412412ef0d in g_logv (log_domain=0x7f4123b26bdb "GLib-GObject",
    log_level=G_LOG_LEVEL_CRITICAL, format=<optimized out>,
    args=args@entry=0x7ffeb9682c40) at ../../../../glib/gmessages.c:1370
#7 0x00007f412412f07f in g_log (
    log_domain=log_domain@entry=0x7f4123b26bdb "GLib-GObject",
    log_level=log_level@entry=G_LOG_LEVEL_CRITICAL,
    format=format@entry=0x7f412417a581 "%s: assertion '%s' failed")
    at ../../../../glib/gmessages.c:1432
#8 0x00007f412412f8b9 in g_return_if_fail_warning (
    log_domain=log_domain@entry=0x7f4123b26bdb "GLib-GObject",
    pretty_function=pretty_function@entry=0x7f4123b28850 <__func__.13618> "g_enum_get_value_by_nick",
    expression=expression@entry=0x7f4123b2869b "nick != NULL")
    at ../../../../glib/gmessages.c:2809
#9 0x00007f4123afb88c in g_enum_get_value_by_nick (
    enum_class=enum_class@entry=0x55cee82c8c40, nick=nick@entry=0x0)
    at ../../../../gobject/genums.c:461
#10 0x000055cee7fdde06 in bolt_enum_from_string (enum_type=94347146857280,
    string=string@entry=0x0, error=error@entry=0x0)
    at ../common/bolt-enums.c:99
#11 0x000055cee7fde2d7 in bolt_device_type_from_string (str=str@entry=0x0)
    at ../common/bolt-enums.c:306
#12 0x000055cee7fd99cc in bolt_store_get_device (store=0x55cee8293670,
    uid=uid@entry=0x7f410c0088c0 "ce010000-0092-8f18-2279-f8d5b0a3a018",
    error=error@entry=0x7ffeb9682e40) at ../boltd/bolt-store.c:433
#13 0x000055cee7fd339c in bolt_manager_initialize (initable=<optimized out>,
    cancellable=<optimized out>, error=<optimized out>)
    at ../boltd/bolt-manager.c:613
#14 0x00007f4123da05a7 in g_initable_new_valist (object_type=<optimized out>,
    first_property_name=0x0, var_args=0x7ffeb9682ec0, cancellable=0x0,
    error=0x7ffeb9682fa0) at ../../../../gio/ginitable.c:248
#15 0x00007f4123da0659 in g_initable_new (object_type=<optimized out>,
    cancellable=<optimized out>, error=<optimized out>, ...

[Sebastien Bacher (seb128)]

The problem is fixed in upstream git master with https://gitlab.freedesktop.org/bolt/bolt/issues/79

[Sebastien Bacher (seb128)]

Upstream says it's only happening for upgrades that used the early 0.1 version, you can wipe /var/lib/boltd and re-auth the device as a workaround