compiz team mailing list archive

[Frank <1366351@xxxxxxxxxxxxxxxxxx>]

I had this issue after booting into Unity very often but not all the
time with an AMD Athlon(tm) 5350 APU with Radeon(tm) R3.

At first I connected a second monitor to the system (first monitor is connected via DVI port, second monitor via HDMI port). Thereafter I realized that this monitor was not necessary for all my work and decided to temporarily turn off the second monitor in the unity system settings (via section "Displays").
Later, I disconnected the second monitor completely and left the "disabled" setting unchanged for this monitor in the Unity system settings (section "Displays"). Thereafter, I observed this issue on the computer and the pain started.

A few days ago, I reconnected the second monitor again, changed the
Unity system settings back to "enabled", and disconnected the monitor
again. Until now, I have not observed this issue any more. I will keep
an eye on it.

Is it possible that there is a race condition in the code and Unity
tries to disable a monitor that is not connected to the system at that
time?

Maybe this comment will help other people. I will add a line to this
comment if I see this issue again within the next few days.

-- 
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1366351

Title:
  compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-
  daemon goes away

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1366351/+subscriptions