twinkle terminate called after throwing an instance of 'std::logic_error'

Status changed to 'Confirmed' because the bug affects multiple users.

I saw an app report dialog pointing to the failure that I believe is referenced in bug 1631210. Then when trying to launch from the command line I see:

% twinkle
Language name: "en"
terminate called after throwing an instance of 'std::logic_error'
  what(): Mutex lock failed
Abort (core dumped)

This started happening on a 16.04 system after installing an update that included the following packages:

accountsservice (0.6.40-2ubuntu11.3)
apt-transport-https (1.2.15)
apt-utils (1.2.15)
cinnamon (3.2.1-1~xenial0)
cinnamon-common (3.2.1-1~xenial0)
cinnamon-control-center (3.2.0-1~xenial0)
cinnamon-control-center-data (3.2.0-1~xenial0)
cinnamon-desktop-data (3.2.0-1~xenial0)
cinnamon-l10n (3.2.1-1~xenial0)
cinnamon-screensaver (3.2.3-1~xenial0)
cinnamon-session (3.2.0-1~xenial0)
cinnamon-session-common (3.2.0-1~xenial0)
cinnamon-settings-daemon (3.2.0-1~xenial0)
cjs (3.2.0-1~xenial0)
fonts-lato (2.0-1)
gawk (1:4.1.3+dfsg-0.1)
gir1.2-accountsservice-1.0 (0.6.40-2ubuntu11.3)
gir1.2-cinnamondesktop-3.0 (3.2.0-1~xenial0)
gir1.2-cmenu-3.0 (3.2.0-1~xenial0)
gir1.2-cvc-1.0 (3.2.0-1~xenial0)
gir1.2-meta-muffin-0.0 (3.2.0-1~xenial0)
gir1.2-xapp-1.0 (1.0.2-1~xenial1)
gist (4.5.0-2)
hddtemp (0.3-beta15-52)
inxi (2.2.35-0ubuntu1)
isc-dhcp-client (4.3.3-5ubuntu12.4)
isc-dhcp-common (4.3.3-5ubuntu12.4)
iso-flag-png (1.0.0-1~xenial0)
javascript-common (11)
libaccountsservice0:amd64 (0.6.40-2ubuntu11.3)
libapt-inst2.0:amd64 (1.2.15)
libcinnamon-control-center1:amd64 (3.2.0-1~xenial0)
libcinnamon-desktop4:amd64 (3.2.0-1~xenial0)
libcinnamon-menu-3-0 (3.2.0-1~xenial0)
libcjs0e (3.2.0-1~xenial0)
libcscreensaver0:amd64 (3.2.3-1~xenial0)
libcvc0:amd64 (3.2.0-1~xenial0)
libfcitx-config4:amd64 (1:4.2.9.1-1ubuntu1.16.04.1)
libfcitx-gclient0:amd64 (1:4.2.9.1-1ubuntu1.16.04.1)
libfcitx-utils0:amd64 (1:4.2.9.1-1ubuntu1.16.04.1)
libjs-jquery (1.11.3+dfsg-4)
libmuffin0 (3.2.0-1~xenial0)
libnemo-extension1 (3.2.0-1~xenial0)
libprocps4:amd64 (2:3.3.10-4ubuntu2.2)
libruby2.3:amd64 (2.3.1-2~16.04)
libxapp1:amd64 (1.0.2-1~xenial1)
linux-firmware (1.157.5)
lm-sensors (1:3.4.0-2)
muffin-common (3.2.0-1~xenial0)
nemo (3.2.0-1~xenial0)
nemo-data (3.2.0-1~xenial0)
nemo-fileroller (3.2.0-1~xenial0)
procps (2:3.3.10-4ubuntu2.2)
python3-distupgrade (1:16.04.18)
python3-xlib (0.14+20091101-5)
rake (10.5.0-2)
ruby (1:2.3.0+1)
ruby2.3 (2.3.1-2~16.04)
ruby-did-you-mean (1.0.0-2)
rubygems-integration (1.10)
ruby-json (1.8.3-1build4)
ruby-minitest (5.8.4-2)
ruby-net-telnet (0.1.1-2)
ruby-power-assert (0.2.7-1)
ruby-test-unit (3.1.7-2)
ubuntu-release-upgrader-core (1:16.04.18)
ubuntu-release-upgrader-gtk (1:16.04.18)
unattended-upgrades (0.90ubuntu0.2)
xapps-common (1.0.2-1~xenial1)
xserver-common (2:1.18.4-0ubuntu0.2)
xserver-xorg-core (2:1.18.4-0ubuntu0.2)

Hi, Twinkle upstream co-maintainer here. This issue has been filed on our GitHub tracker[1], and we have a pending pull request which fixes it[2].

[1] https://github.com/LubosD/twinkle/issues/88
[2] https://github.com/LubosD/twinkle/pull/150

To summarize, this issue arises when two user profiles sharing the same SIP username are enabled. This would require enabling the "Use domain name to create a unique contact header value" option (in "SIP protocol" > "General" > "Protocol options"). Normally, Twinkle would display a message informing you of this fact, but here it crashes before it had a chance to do so.

(If Twinkle crashes on start, you probably have both configured to activate at startup. Manually edit your configuration file (~/.twinkle/twinkle.sys) and remove the appropriate "start_user_profile" lines. At this point, Twinkle should start again, and you can enable the option for both users.)