unity-system-compositor crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

[threarth]

HP Pavilion g6 1352 sl laptpop, with ati radeon 6400/7400M series

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-system-compositor 0.0.1+13.10.20130813.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
Date: Sat Aug 17 18:11:26 2013
ExecutablePath: /usr/sbin/unity-system-compositor
InstallationDate: Installed on 2013-08-17 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130817)
MarkForUpload: True
ProcCmdline: /usr/sbin/unity-system-compositor --from-dm-fd 10 --to-dm-fd 13 --vt 7
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
Signal: 6
SourcePackage: unity-system-compositor
StacktraceTop:
 __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 start_thread (arg=0x7fe3f0d2e700) at pthread_create.c:311
Title: unity-system-compositor crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
 __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:38
 std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:48
 std::(anonymous namespace)::execute_native_thread_routine (__p=<optimized out>) at ../../../../../src/libstdc++-v3/src/c++11/thread.cc:92
 start_thread (arg=0x7fe3f0d2e700) at pthread_create.c:311

[Launchpad Janitor (janitor)]

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

[Jacek Nykis (jacekn)]

I experience the same problem on a system with GeForce GTX 260 graphics card.

[Timo Jyrinki (timo-jyrinki)]

Somehow I'm getting this this morning whenever I attach second monitor, which worked fine yesterday.

[Timo Jyrinki (timo-jyrinki)]

Ah, that was useful to say, I got it working on the fourth attach. Before that, I did 1. boot, 2. login, 3. attach monitor -> nothing seems to happen (like no detection), 4. detach and reattach, 5. is detected but something crashes and I get "low graphics mode" dialog.

[Gareth Woolridge (moon127)]

I also hit this bug with a GeForce GT 650M 2GB.

[Adam Collard (adam-collard)]

FWIW I don't have any external monitors and still hit this on a Dell XPS 13 with Intel graphics

[Daniel van Vugt (vanvugt)]

Unfortunately we're left without a trace (literally). So pointing this at the root cause of that problem.