system-settings crashed with SIGABRT in raise()

[Jean-Baptiste Lallement]

TEST CASE:
1. Open BT indicator and disable BT
2. Open system-settings
3. Select BT
4. Enable/Disable BT several times (max 2 or 3)

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: ubuntu-system-settings 0.1+13.10.20131004-0ubuntu1
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion: 2.12.5-0ubuntu1
Architecture: armhf
Date: Mon Oct 7 09:10:03 2013
ExecutablePath: /usr/bin/system-settings
ExecutableTimestamp: 1380866469
InstallationDate: Installed on 2013-10-05 (1 days ago)
InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20131005)
MarkForUpload: True
ProcCmdline: system-settings
ProcCwd: /home/phablet
Signal: 6
SourcePackage: ubuntu-system-settings
StacktraceTop:
 ?? () from /lib/arm-linux-gnueabihf/libc.so.6
 raise () from /lib/arm-linux-gnueabihf/libc.so.6
 abort () from /lib/arm-linux-gnueabihf/libc.so.6
 __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
 ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
Title: system-settings crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1234930, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Charles Kerr (charlesk)]

The trace is different, but this looks like the same issue as Bug #1236249