touch-packages team mailing list archive

[Marco Trevisan (Treviño) <mail@xxxxxxxxx>]

** Changed in: unity/7.2
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1324114

Title:
  Unity kills running compiz, even if it belongs to a different Unity
  session

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  I'm trying to get a setup with two different Unity desktop sessions
  running at the same time.  One for the local desktop, one for a remote
  desktop.  This almost works, except that when starting the second
  Unity session, the compiz process that belongs to the first one is
  killed because of this code in /usr/bin/unity:

      # kill a previous compiz if was there (this is a hack as compiz can
      # sometimes get stuck and not exit on --replace)
      subprocess.call (["pkill", "-9", "compiz"])

  Commenting this line makes both desktop sessions work fine.

  This kill is far too harsh.  If you want to kill compiz, you should
  make sure that you are killing it in the same DISPLAY as the session
  that you are about to start, and not just every possible compiz
  process that is running.

  Please consider either removing the kill or making it apply only to
  processes in the same DISPLAY.

  
  [Impact]
  Running unity script will kill the unity processes in different displays

  [Test case]
  - Run unity in DISPLAY=:0 and in DISPLAY=:1
  - Launch the unity script in DISPLAY=:1, it should kill and restart only the unity
    instance running in DISPLAY=:1

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