** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity (Ubuntu)
Status: New => Triaged
** Changed in: unity (Ubuntu)
Importance: Undecided => Medium
** Changed in: unity
Milestone: None => 7.3.0
** Also affects: unity/7.2
Importance: Undecided
Status: New
** Changed in: unity/7.2
Importance: Undecided => Medium
** Changed in: unity/7.2
Status: New => Triaged
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1324114
Title:
Unity kills running compiz, even if it belongs to a different Unity
session
Status in Unity:
Triaged
Status in Unity 7.2 series:
Triaged
Status in “unity” package in Ubuntu:
Triaged
Bug description:
Hi!
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.
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1324114/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
