[Bug 874146] Re: New windows open on the wrong monitor, Place Plugin settings silently ignored

2012-10-24 Thread Dmitriy Balakin
I can confirm the behavior described in #31, 33 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874146 Title: New windows open on the wrong monitor, Place Plugin settings silently ignored To manage

[Bug 874146] Re: New windows open on the wrong monitor, Place Plugin settings silently ignored

2012-10-23 Thread Daniel van Vugt
** Changed in: compiz-core Status: In Progress => Triaged ** Changed in: compiz-core Assignee: MC Return (mc-return) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874146 T

[Bug 874146] Re: New windows open on the wrong monitor, Place Plugin settings silently ignored

2012-10-21 Thread Gao Shichao
@MCReturn I'm quite sure I've restarted my computer. I find it interesting that after I place the smaller display(1280*1024) left of the larger(1920*1080) in system settings->Display, when I click sound settings, system settings ,etc on the smaller display the window will always show on the la

[Bug 874146] Re: New windows open on the wrong monitor, Place Plugin settings silently ignored

2012-10-21 Thread MC Return
@xgdgsc: 1. Please make sure that you have restarted Compiz/Unity before testing the fix. 2. Use the "Place" plugin to adjust place window settings, make sure you use the default settings in General Compiz Options->Display Settings (click on the 3 "x" to reset those). 3. Note that some windows (

[Bug 874146] Re: New windows open on the wrong monitor, Place Plugin settings silently ignored

2012-10-20 Thread Gao Shichao
After applying the fix in #29 , when I set the CCSM>>General Options>>Display settings to "Smart Mode" , if I click the sound settings from the sound applet on the smaller display, the settings dialog appears still on the larger display. I don't think it's right behavior. Thanks for your effort ,

[Bug 874146] Re: New windows open on the wrong monitor, Place Plugin settings silently ignored

2012-10-20 Thread MC Return
Here you can see the fix in action. Other Place Plugin settings also work now, but this is the preferred behaviour for most multi-display users. ** Attachment added: "Unity and Place working together in harmony ;)" https://bugs.launchpad.net/compiz-core/+bug/874146/+attachment/3406177/+files/

[Bug 874146] Re: New windows open on the wrong monitor, Place Plugin settings silently ignored

2012-10-20 Thread MC Return
For all of you, who do not want until the fix is available via update can simply edit the .xml files in /usr/share/compiz, namely unityshell.xml and place.xml. 1. In unityshell.xml (sudo gedit /usr/share/compiz/unityshell.xml) remove the line place in the block. 2. In place.xml (sudo gedit /usr/

[Bug 874146] Re: New windows open on the wrong monitor, Place Plugin settings silently ignored

2012-10-20 Thread MC Return
** Branch linked: lp:~mc-return/compiz/compiz.merge-fix874146-place- plugin-broken ** Branch linked: lp:~mc-return/unity/unity.merge-fix874146-place- plugin-broken ** Branch unlinked: lp:~mc-return/compiz/compiz.merge-fix874146-place- plugin-broken ** Branch linked: lp:~mc-return/compiz/compiz.m

[Bug 874146] Re: New windows open on the wrong monitor, Place Plugin settings silently ignored

2012-10-20 Thread MC Return
The problem here is (once again) that unityshell loads after the place plugin and overrides its settings. Also the standard setting of the Place plugin is not optimal if multi- monitors are used, because the standard setting for Multi Output Mode is set to "Use active output device", which is bett

[Bug 874146] Re: New windows open on the wrong monitor, Place Plugin settings silently ignored

2012-10-20 Thread MC Return
** Summary changed: - New windows open on the wrong monitor + New windows open on the wrong monitor, Place Plugin settings silently ignored -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874146 Title: