[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Changed in: unity Status: Fix Committed = Fix Released -- 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: Fix Released 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 -- 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- 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: Fix Committed Status in Unity 7.2 series: Fix Committed 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 -- 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Changed in: unity/7.2 Status: Fix Committed = Fix Released -- 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: 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 -- 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
This bug was fixed in the package unity - 7.2.3+14.04.20140826-0ubuntu1 --- unity (7.2.3+14.04.20140826-0ubuntu1) trusty; urgency=medium [ Andrea Azzarone ] * Remove cross fade effect during lock/unlocking. A simple fading works just fine. (LP: #1312107) * Manually emit nux::Area::geometry_changed beucase nux can fail to emit it. (LP: #1292391) [ Pawel Szubert ] * Reduce the scope of the kill command when restarting Compiz. (LP: #1324114) [ Marco Trevisan (Treviño) ] * LockScreenAcceleratorController: do ther configured action on power special keys press. We finally can suspend, shutdown, hibernate or start the screensaver when the screen is locked, using the Suspend, Sleep, Hibernate and PowerOff hardware keys. Also the Shutdown dialog doesn't allow now to lock the session if it is not allowed by settings. (LP: #1306211) (LP: #1320051) (LP: #1320071) * Previews: scale the dash preview contents to match current monitor scaling. Improved also the scaling of search-bar, spinner, categories and many other components. (LP: #1339629) * FilterWidgets: add support for scaling (LP: #1340171) * OverlayRendering: correctly scale the overlays borders and edges to match settings. DashStyle has been modified to return smart pointers of textures that are loaded depending on the scale level. The cache will make sure that we don't duplicate the textures and that they get removed when not needed anymore. Also thanks to this the SearchBarSpinner textures (and the other spinners as well) uses the SVGs scaled at the proper size (I desgined a new SVG for the magnifier, as we only had a PNG). (LP: #1283415) (LP: #1340394) * Hud: scale to match current DPI settings for monitor. (LP: #1340477) [ Eleni Maria Stea ] * Previews: scale the dash preview contents to match current monitor scaling. Improved also the scaling of search-bar, spinner, categories and many other components. (LP: #1339629) [ Stephen M. Webb ] * Reduce the scope of the kill command when restarting Compiz. (LP: #1324114) [ Chris Townsend ] * Bump version to 7.2.3. unity (7.2.2+14.04.20140714-0ubuntu2) trusty; urgency=medium [ Andrea Azzarone ] * Remove cross fade effect during lock/unlocking. A simple fading works just fine. (LP: #1312107) * Manually emit nux::Area::geometry_changed beucase nux can fail to emit it. (LP: #1292391) * TextInput: use GdkKeymap to check the caps-lock status (LP: #1347735) [ Pawel Szubert ] * Reduce the scope of the kill command when restarting Compiz. (LP: #1324114) [ Marco Trevisan (Treviño) ] * LockScreenAcceleratorController: do ther configured action on power special keys press. We finally can suspend, shutdown, hibernate or start the screensaver when the screen is locked, using the Suspend, Sleep, Hibernate and PowerOff hardware keys. Also the Shutdown dialog doesn't allow now to lock the session if it is not allowed by settings. (LP: #1306211) (LP: #1320051) (LP: #1320071) * Previews: scale the dash preview contents to match current monitor scaling. Improved also the scaling of search-bar, spinner, categories and many other components. (LP: #1339629) * FilterWidgets: add support for scaling (LP: #1340171) * OverlayRendering: correctly scale the overlays borders and edges to match settings. DashStyle has been modified to return smart pointers of textures that are loaded depending on the scale level. The cache will make sure that we don't duplicate the textures and that they get removed when not needed anymore. Also thanks to this the SearchBarSpinner textures (and the other spinners as well) uses the SVGs scaled at the proper size (I desgined a new SVG for the magnifier, as we only had a PNG). (LP: #1283415) (LP: #1340394) * Hud: scale to match current DPI settings for monitor. (LP: #1340477) * PlacesOverlayVScrollBar and VScrollBarOverlayWindow: add support for scaling. Add a new ScrollView class to create ScrollViews with an OverlayScrollbar and with scaling support. Using them in dash Scopes and Previews. (LP: #1340996) * LockScreenShield: Add GrabScreen function and retry to make sure we really get the grab. It might happen that the grab is not possible because the PluginAdapter::IsScreenGrabbed request has still not being fully processed, and thus nux is not able to grab the pointer/keyboard. By doing this we instead try to grab the screen, and if this is not happening, we wait a little until we don't get the ungrab event. In this way, if we eventually get the grab, all will work as expected. Otherwise, we cancel the lock request (very unlikely to happen). (LP: #1349128) * PlacesOverlayVScrollBar: redirect the mouse wheel scroll events coming from the thumb to the scrollview. This will make the scrollview to handle then and perform the same
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Tags removed: verification-needed ** Tags added: verification-done -- 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: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed 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 -- 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
Could somebody help verifying the fix so that version can move to utopic-updates? -- 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: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed 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 -- 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
unity_7.2.3+14.04.20140826-0ubuntu1.debdiff ** Patch 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 -- 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: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: In Progress 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 -- 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Changed in: unity/7.2 Status: Triaged = In Progress ** Changed in: unity (Ubuntu Trusty) Status: Triaged = In Progress ** Changed in: unity (Ubuntu Trusty) Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: unity (Ubuntu Trusty) Importance: Undecided = Medium ** Description changed: - 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]) + # 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. + + [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 -- 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: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: In Progress 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 -- 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Branch linked: lp:~unity-team/unity/prepare-7.2.3-SRU -- 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: Fix Committed Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Changed in: unity/7.2 Milestone: 7.2.2 = 7.2.3 -- 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: Fix Committed Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Changed in: unity Status: In Progress = Fix Committed -- 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: Fix Committed Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
This bug was fixed in the package unity - 7.3.0+14.10.20140708-0ubuntu1 --- unity (7.3.0+14.10.20140708-0ubuntu1) utopic; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Stephen M. Webb ] * reduce the scope of the kill command when restarting compiz (LP: #1324114) [ Eleni Maria Stea ] * Changed the PreviewStyle.h/cpp to use em sizes (RawPixel). * Added scale factor to Preview (base class), preview container and to the components they contain. * Scaled the ApplicationPreview and the containing widgets and components. * Scaled GenericPreview and its widgets. * scaled ErrorPreview * Scaled MoviePreview and widgets [ Pawel Szubert ] * reduce the scope of the kill command when restarting compiz (LP: #1324114) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 08 Jul 2014 14:35:37 + ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- 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: In Progress Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Changed in: unity Status: Triaged = In Progress ** Changed in: unity (Ubuntu Trusty) Status: New = Triaged ** Changed in: unity (Ubuntu) Status: Triaged = In Progress ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Stephen M. Webb (bregma) -- 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: In Progress Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Changed in: unity Milestone: 7.3.0 = 7.3.1 -- 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: In Progress Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Branch linked: lp:~bregma/unity/lp-1324114 -- 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 Status in “unity” source package in Trusty: New 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** Changed in: unity Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: unity/7.2 Assignee: (unassigned) = Stephen M. Webb (bregma) ** Changed in: unity/7.2 Milestone: None = 7.2.2 -- 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 Status in “unity” source package in Trusty: New 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
I'm not working on Compiz/Unity anymore, but I agree with the bug description and the comments to where compiz/unity headed to today. We had a lot of stability problem at the time, hence this helper to reset unity (which is never used in the session itself to start unity). Stephen's team will handle it. I'm accepting the SRU nomination for trusty as well. ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New -- 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 Status in “unity” source package in Trusty: New 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
** 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
[Dx-packages] [Bug 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
The attachment unity.kill.patch.txt seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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
