Activity log for bug #1324114

Date Who What changed Old value New value Message
2014-05-28 12:52:58 Margarita Manterola bug added bug
2014-05-28 12:53:10 Margarita Manterola bug added subscriber Goobuntu Team
2014-05-28 13:48:33 Pavel Ivanov bug added subscriber Pavel Ivanov
2014-06-02 15:38:46 Stephen M. Webb unity: status New Triaged
2014-06-02 15:38:48 Stephen M. Webb unity: importance Undecided Medium
2014-06-11 11:46:44 Pawel Szubert attachment added unity.kill.patch.txt https://bugs.launchpad.net/unity/+bug/1324114/+attachment/4129586/+files/unity.kill.patch.txt
2014-06-12 20:42:07 Philipp Kern bug added subscriber Didier Roche
2014-06-12 23:56:57 Stephen M. Webb bug task added unity (Ubuntu)
2014-06-12 23:57:07 Stephen M. Webb unity (Ubuntu): status New Triaged
2014-06-12 23:57:09 Stephen M. Webb unity (Ubuntu): importance Undecided Medium
2014-06-12 23:57:17 Stephen M. Webb nominated for series Ubuntu Trusty
2014-06-12 23:57:31 Stephen M. Webb unity: milestone 7.3.0
2014-06-12 23:58:06 Stephen M. Webb nominated for series unity/7.2
2014-06-12 23:58:06 Stephen M. Webb bug task added unity/7.2
2014-06-12 23:58:26 Stephen M. Webb unity/7.2: importance Undecided Medium
2014-06-12 23:58:26 Stephen M. Webb unity/7.2: status New Triaged
2014-06-13 00:23:34 Ubuntu Foundations Team Bug Bot tags patch
2014-06-13 00:23:42 Ubuntu Foundations Team Bug Bot bug added subscriber Ubuntu Review Team
2014-06-16 07:06:13 Didier Roche-Tolomelli bug task added unity (Ubuntu Trusty)
2014-06-19 01:43:02 Stephen M. Webb unity: assignee Stephen M. Webb (bregma)
2014-06-19 01:43:07 Stephen M. Webb unity/7.2: assignee Stephen M. Webb (bregma)
2014-06-19 01:43:10 Stephen M. Webb unity/7.2: milestone 7.2.2
2014-06-19 01:48:11 Launchpad Janitor branch linked lp:~bregma/unity/lp-1324114
2014-06-20 02:25:17 Stephen M. Webb unity: status Triaged In Progress
2014-06-20 02:25:34 Stephen M. Webb unity (Ubuntu Trusty): status New Triaged
2014-06-20 02:25:37 Stephen M. Webb unity (Ubuntu): status Triaged In Progress
2014-06-20 02:25:40 Stephen M. Webb unity (Ubuntu): assignee Stephen M. Webb (bregma)
2014-06-20 02:37:48 Stephen M. Webb unity: milestone 7.3.0 7.3.1
2014-07-08 22:53:43 Launchpad Janitor unity (Ubuntu): status In Progress Fix Released
2014-07-11 12:25:29 Stephen M. Webb unity: status In Progress Fix Committed
2014-07-15 18:51:13 Christopher Townsend unity/7.2: milestone 7.2.2 7.2.3
2014-07-24 14:22:59 Launchpad Janitor branch linked lp:~unity-team/unity/prepare-7.2.3-SRU
2014-09-17 00:41:57 Marco Trevisan (Treviño) unity/7.2: status Triaged In Progress
2014-09-17 00:41:59 Marco Trevisan (Treviño) unity (Ubuntu Trusty): status Triaged In Progress
2014-09-17 00:42:16 Marco Trevisan (Treviño) unity (Ubuntu Trusty): assignee Stephen M. Webb (bregma)
2014-09-17 00:42:20 Marco Trevisan (Treviño) unity (Ubuntu Trusty): importance Undecided Medium
2014-09-17 00:45:06 Marco Trevisan (Treviño) 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. 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
2014-09-22 15:27:50 Marco Trevisan (Treviño) attachment added unity_7.2.3+14.04.20140826-0ubuntu1.debdiff https://bugs.launchpad.net/bugs/1324114/+attachment/4211565/+files/unity_7.2.3%2B14.04.20140826-0ubuntu1.debdiff
2014-09-23 19:34:19 Chris J Arges unity (Ubuntu Trusty): status In Progress Fix Committed
2014-09-23 19:34:22 Chris J Arges bug added subscriber Ubuntu Stable Release Updates Team
2014-09-23 19:34:27 Chris J Arges bug added subscriber SRU Verification
2014-09-23 19:34:37 Chris J Arges tags patch patch verification-needed
2014-10-21 20:33:04 Marco Trevisan (Treviño) tags patch verification-needed patch verification-done
2014-10-28 13:19:16 Launchpad Janitor unity (Ubuntu Trusty): status Fix Committed Fix Released
2014-10-28 13:20:59 Chris J Arges removed subscriber Ubuntu Stable Release Updates Team
2014-10-29 16:26:01 Marco Trevisan (Treviño) unity/7.2: status In Progress Fix Committed
2014-10-29 16:56:04 Marco Trevisan (Treviño) unity/7.2: status Fix Committed Fix Released
2015-02-11 16:14:06 Stephen M. Webb unity: status Fix Committed Fix Released