[Compiz] [Bug 1072206] Re: [nvidia] Window content is black
My comment from https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/729979: To make the bug easier to see and understand, make the animation slower: dconf write /com/canonical/unity/minimize-slow-duration 3000 (You can undo this easily with dconf reset /com/canonical/unity/minimize-slow-duration) Now the animation should be slow enough to be able to interrupt it (meaning you are able to press the minimize button, and can move the mouse pointer faster to the launcher symbol and press it than the animated window is going there). You can alternatively reproduce the effects shown in the linked video by moving the mouse pointer to the launcher and try to click the application instantly after the animation was initiated by pressing Strg + Alt + KP0 (numpad 0 key). The main point is, the bug seems to be quite randomly with default settings (most of the time it does not work, however there are situations when it works). I found out, that you can reproduce the bug for sure if you apply the dconf setting mentioned above (you could also apply higher values). The slower the animation is, the more likely it is, that the bug happens. The behaviour is shown in the following video: http://ubuntuone.com/5xMF480diMFbN5np9rERcP Now the very important part: You can see, that the minimize animation ALWAYS works, when it was interrupted before (and the window is black, or without any content). But you have to consider, you are not allowed to shade/unshade, resize or click away from the window! This means doing only minimizing and unminimizing behind one another of the same window (without doing anything that makes the missing window content disappear), it works every second time. If an window is opened, there is no way, that the animation works the first time minimizing, except you maximize it! This means you can always get the animation working if you maximize it before you press the minimize button (you have to maximize again even if the application is already maximized). So to conclude there are two ways of always getting the animation work. I have found an equivalent way to reproducing the bug (which could be relevant): http://ubuntuone.com/16WmSevvitMlG8XfkfYzfE (Note: For single windows in the video the ESC button was used to leave the spread without selecting the window. ) If you minimize a non fullscreen window (after you have opened it), click the spread view, leave it without selecting the minimized window and unminimize it, it gets the same condition as interrupting a window minimize. This behaviour is not true for windows, that minimized correctly before, so the bug does not work for windows maximized an then minimised (last example in the video). The behaviour shown in the second video is a consequence of the bug shown in the first video, so if you can reproduce the second bug this is also a proof for having the first bug. The window content is not always black, for example, if you have set a transparent terminal colour the window content is not black, but completely missing (meaning 100% transparent). If you have a black/transparent window and you focus another window and switch back to the black/transparent window, the window content is there again. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1072206] Re: [nvidia] Window content is black
One thing I forgot: The problem is independent from the minimize animation (it also occurs for other animations like magic lamp). If you disable unityshell plugin, minimize always works without getting black/transparent windows. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1102649] Re: Live window updates stop during minimize animation
Confirmed for latest version of compiz daily in raring. This problem is true for minimizing, but not for unminimizing (consider you only have one window of a particular application open: Now you minimize, live update does not work. If you click the launcher to unminimize the window, live update is working. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1102649 Title: Live window updates stop during minimize animation To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1102649/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1130203] Re: Some applications do not snapp off correctly (wrong cursor position) from maximized state
** Also affects: unity Importance: Undecided Status: New ** Description changed: - If you snap off some applications from maximized state the cursor gets positioned wrong. This is always reproduceable with Libreoffice. + The following problems only occur with unity-shell plugin enabled: + + If you snap off some applications from maximized state the cursor gets positioned wrong. This is always reproduceable with Libreoffice. If Qtcreator is in maximized state when launched the same problems shows as for libreoffice (cursor wrong, gets placed inside the windows instead of the titlebar). - Some other applications such as nautilus always position the cursor as desired. + Some other applications such as nautilus always position the cursor as desired. This can be seen in the following screencast: http://ubuntuone.com/3jn7DJPh2WTUwoZd5HUhtD -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1130203 Title: Some applications do not snapp off correctly (wrong cursor position) from maximized state To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1130203/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1130203] [NEW] Some applications do not snapp off correctly (wrong cursor position) from maximized state
Public bug reported: If you snap off some applications from maximized state the cursor gets positioned wrong. This is always reproduceable with Libreoffice. If Qtcreator is in maximized state when launched the same problems shows as for libreoffice (cursor wrong, gets placed inside the windows instead of the titlebar). Some other applications such as nautilus always position the cursor as desired. This can be seen in the following screencast: http://ubuntuone.com/3jn7DJPh2WTUwoZd5HUhtD ** Affects: compiz Importance: Undecided Status: New ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: raring ** Also affects: compiz Importance: Undecided Status: New -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1130203 Title: Some applications do not snapp off correctly (wrong cursor position) from maximized state To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1130203/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 201681] Re: Window management - Cursor position changes relative to window while dragging windows
Although the situation got much better there are still some corner cases left in 0.9.9.0: https://bugs.launchpad.net/compiz/+bug/1130203 https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1115350 https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1115344 https://bugs.launchpad.net/compiz/+bug/1120646 -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/201681 Title: Window management - Cursor position changes relative to window while dragging windows To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/201681/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1095688] Re: Using corner-resize mode of the grid plugin, there is spacing between terminals
Corrected bug description because the wrong (already fixed) part was split out from bug 1093757. ** Description changed: Split out from bug 1093757 - If you place the window in any corner and then press ControlAltKP5 - the window does not get placed correctly (the application gets resized - correctly but is placed somewhere in between the workspaces. This varies - from position to position. It gets distributed to all workspaces - symmetric.) + Placing terminal windows in corners or top/bottom half causes the windows being not correctly resized. This results to spacings between the terminals and the workspace edge. + This can be seen in the following video (nevermind about the second demonstrated bug): + http://ubuntuone.com/7FZPuXm0KYtV9eHrlRJdf3 -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1095688 Title: Using corner-resize mode of the grid plugin, there is spacing between terminals To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1095688/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1119608] [NEW] Closing windows sometimes shows black areas using Nvidia 313.x drivers
Public bug reported: When using Nvidia 313.09 and 313.18 drivers, closing windows often causes black areas around the disappearing window. This happens quite randomly, though there are windows that are affected more often (in my case this was the System Settings window). I found a way to reproduce the bug more likely: Pressing the close button and alt+f4 simultaneously. The following video shows this effect (you can see: sometimes it happens, sometimes not): http://ubuntuone.com/6yIeUzJJRNqS3x1ydIbgfQ ** Affects: compiz Importance: Undecided Status: New ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: raring ** Also affects: compiz Importance: Undecided Status: New ** Description changed: - When using Nvidia 313.09 and 313.18 drivers, closing windows often causes black areas around the disappearing window. This happens quite randomly, though there are windows that are affected more often (in my case this was the System Settings window). - I found a more way to reproduce the bug more likely: Pressing the close button and alt+f4 simultaneously. - The following video shows this effect (you can see: sometimes it happens, sometimes not): + When using Nvidia 313.09 and 313.18 drivers, closing windows often causes black areas around the disappearing window. This happens quite randomly, though there are windows that are affected more often (in my case this was the System Settings window). + I found a way to reproduce the bug more likely: Pressing the close button and alt+f4 simultaneously. + The following video shows this effect (you can see: sometimes it happens, sometimes not): http://ubuntuone.com/6yIeUzJJRNqS3x1ydIbgfQ -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1119608 Title: Closing windows sometimes shows black areas using Nvidia 313.x drivers To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1119608/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1116538] Re: Strg + Super + Down does not work for windows placed in corners or top/bottom half
@John: yes, sorry about that inconsistency. ** Description changed: If you want to restore a maximized or semi-maximized window Ctrl + Super + Down works. If you want to restore a window placed in corners or top/bottom half Ctrl + Alt + R works. - If you press Ctro + Super + Down for a window placed in corners or + If you press Ctrl + Super + Down for a window placed in corners or top/bottom half, the window gets minimized instead of getting restored first. - Strg + Super + Down should replace Strg + Alt + R, so that restoring + - minimizing using Strg + Super + Down works for all windows the same way. + Ctrl + Super + Down should replace Ctrl + Alt + R, so that restoring + + minimizing using Ctrl + Super + Down works for all windows the same way. Desired resolution: - Replace the Ctrl + Alt+ R shortcut with Ctrl + Alt + Down -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1116538 Title: Strg + Super + Down does not work for windows placed in corners or top/bottom half To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1116538/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115353] Re: Resizing windows (accessibility menu) using arrow keys does not work if resizing using more than one boarder
** Description changed: - If you attempt to resize a window by using the arrow keys and switch between the window boarders (e.g. using up-arrow-key and afterwards right-arrow-key) two issues prevent resizing: - 1.) - When changing boarders the cursor does not get positioned on the boarder of the orange preview box, but on the corner of the original window, which should only be the case if the windows size was not already modified using this boarder. - 2.) - If you modify the height of a window and switch boarders to modify the width of a window, the height of the orange preview box gets reset to the height of the original window, the upper boarder of the orange preview box always stays the same. - This means if you resize using the bottom boarder, switch to another boarder and start to resize, the orange previewbox gets reset so that it is congruent to the original window (with the exception of the boarder you just modified of course. ) - + If you attempt to resize a window by using the arrow keys and switch between the window borders (e.g. using up-arrow-key and afterwards right-arrow-key) two issues prevent resizing: + 1.) + When changing borders the cursor does not get positioned on the border of the orange preview box, but on the corner of the original window, which should only be the case if the windows size was not already modified using this border. + 2.) + If you modify the height of a window and switch borders to modify the width of a window, the height of the orange preview box gets reset to the height of the original window, the upper border of the orange preview box always stays the same. + This means if you resize using the bottom border, switch to another border and start to resize, the orange previewbox gets reset so that it is congruent to the original window (with the exception of the border you just modified of course. ) - If you modify the width of a window and switch boarders to modify the height of a window, the width of the orange preview box gets reset to the width of the original window, the left boarder of the orange preview box always stays the same. - This means if you resize using the right boarder, switch to another boarder and start to resize, the orange previewbox gets reset so that it is congruent to the original window (with the exception of the boarder you just modified of course. ) + If you modify the width of a window and switch borders to modify the height of a window, the width of the orange preview box gets reset to the width of the original window, the left border of the orange preview box always stays the same. + This means if you resize using the right border, switch to another border and start to resize, the orange previewbox gets reset so that it is congruent to the original window (with the exception of the border you just modified of course. ) - This two factors cause the cursor to be positioned relative to the orange preview box. + This two factors cause the cursor to be positioned relative to the orange preview box. The following video demonstrates this issue: http://ubuntuone.com/4wuuFxXU6VCJQVXGv3l6sM ** Summary changed: - Resizing windows (accessibility menu) using arrow keys does not work if resizing using more than one boarder + Resizing windows (accessibility menu) using arrow keys does not work if resizing using more than one border -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115353 Title: Resizing windows (accessibility menu) using arrow keys does not work if resizing using more than one border To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115353/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1082001] Re: Grid/Expo: Corner-resized Grid windows confuse Expo and follow the user from workspace to workspace
@Hugo, With the word Workspace switcher I am referring to a default ubuntu installation, where expo is called Workspace Switcher. ** Description changed: [Test Case] 1. Open a window 2. Hit Ctrl+Alt+Numpad3 to resize it via Grid (for example Firefox) into a corner. Alternatively you can drag the window to a corner to grid-resize it. 3. Open any other window (for example a terminal) 4. Trigger Expo (via Launcher's Workspace Switcher icon or by hitting Super+S for example) 5. Now drag the non-gridded second window (terminal in our case here) to another workspace/viewport What you would expect to happen: The terminal window should now be on the new viewport. The other window should not change position. What actually happens: No matter on which workspace the terminal window is dragged to, the *gridded* window follows. Wait, it gets even better: If you try to switch the workspace without dragging a window, the *gridded* window will follow you, whereever you go. If you resize multiple windows via Grid all will follow you from workspace to workspace. Note 1: I have tested this in a virtual machine with a vanilla default up-to-date installation of Raring also, to make sure non-default settings are not causing this problem. Note 2: This bug makes using Grid in combination with Expo (which are both enabled by default on Ubuntu) completely unusable and should have high priority. - - SUMMARY: - When a window gets positioned in a corner or the top/bottom half and you switch workspace using ẃorkspace switcher the window gets positioned on every workspace you switch to on exactly the same position. - Same is true for dragging one window on the same workspace as the grid positioned window (corners or top/bottom half) to another workspace: the grid placed window follows to the workspace the other window is dragged to. + SUMMARY: + When a window gets positioned in a corner or the top/bottom half and you switch workspace using ẃorkspace switcher (expo) the window gets positioned on every workspace you switch to on exactly the same position. + Same is true for dragging one window on the same workspace as the grid positioned window (corners or top/bottom half) to another workspace: the grid placed window follows to the workspace the other window is dragged to. This behavior is not true for windows that have grid positions when launched! The following video demonstrates the bug: http://ubuntuone.com/2s8kNGM6Qcp3WFfjOwe6XX -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1082001 Title: Grid/Expo: Corner-resized Grid windows confuse Expo and follow the user from workspace to workspace To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1082001/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115343] Re: Semi-maximized windows do not maximize correctly using the maximize button
** Tags added: needs-design -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115343 Title: Semi-maximized windows do not maximize correctly using the maximize button To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115343/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115341] Re: Grid resize: Placing maximized windows on the top edge using shortcuts does not work
** Description changed: - Pressing Strg + Alt + KP (7, 8, 9) in order to position a maximized window in the top corners or on the top half, the panel is not considered, meaning that part of the window disappears under the panel which is unwanted behavior. + Pressing Ctrl + Alt + KP (7, 8, 9) in order to position a maximized window in the top corners or on the top half, the panel is not considered, meaning that part of the window disappears under the panel which is unwanted behavior. The following video demonstrates this: http://ubuntuone.com/2FZ7UGfyrVl0MIHZflaYba -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115341 Title: Grid resize: Placing maximized windows on the top edge using shortcuts does not work To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115341/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115343] Re: Semi-maximized windows do not maximize correctly using the maximize button
** Description changed: - After semi-maximizing (right/left half) a window it can not be maximized pressing the maximize button the first time. Instead the size before semi maximizing the window gets restored, so you need to press the maximize button again in order to really maximize the window. - If an application is already semi maximized when opening, maximizing works. + After semi-maximizing (right/left half) a window it can not be maximized pressing the maximize button the first time. Instead the window gets restored, so you need to press the maximize button again in order to really maximize the window. + If an application is already semi-maximized when opening, maximizing works. The following video demonstrates this: http://ubuntuone.com/43jbUlTisO1Ehg6keRyfF7 -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115343 Title: Semi-maximized windows do not maximize correctly using the maximize button To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115343/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115344] Re: Grid + Maximizing (button) + snapping by mouse to Grid position changes cursor position relative to window
** Tags added: raring -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115344 Title: Grid + Maximizing (button) + snapping by mouse to Grid position changes cursor position relative to window To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115344/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115343] Re: Semi-maximized windows do not maximize correctly using the maximize button
** Tags added: raring -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115343 Title: Semi-maximized windows do not maximize correctly using the maximize button To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115343/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115341] Re: Grid resize: Placing maximized windows on the top edge using shortcuts does not work
** Tags added: raring -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115341 Title: Grid resize: Placing maximized windows on the top edge using shortcuts does not work To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115341/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115350] Re: Grid: Dragging screen centric windows (e.g. Sim unlock required) causes cursor being changed relative to the window
** Tags added: raring -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115350 Title: Grid: Dragging screen centric windows (e.g. Sim unlock required) causes cursor being changed relative to the window To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115350/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1082001] Re: Grid/Expo: Corner-resized Grid windows confuse Expo and follow the user from workspace to workspace
** Tags added: raring -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1082001 Title: Grid/Expo: Corner-resized Grid windows confuse Expo and follow the user from workspace to workspace To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1082001/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115350] Re: Grid: Dragging screen centric windows (e.g. Sim unlock required) causes cursor being changed relative to the window
** Description changed: - If you resize a window which default position is set to the middle of the screen, for example the SIM PIN Unlock required window, it gets moved the center of the screen. (This behavior is not reproducable on Quantal). - If you position the window and drag it off from grid positions the mouse cursor changes relative to the window (Dragging it off moves the window instantly to the center while the mouse pointer keeps its position), which is unwanted behaviour. - Dragging off these windows used to work in Quantal for semi-maximized and maximized state, but back then another bug appeared for semi maximized state which is now gone: the horizontal width of the window was not correctly reset. - After the mouse pointer was set (to drag off the window), the location of the reset window should not change. - The following video demonstrates this behavior: + If you resize a window which default position is set to the middle of the screen, for example the SIM PIN Unlock required window, it gets moved the center of the screen. + If you position the window and drag it off from grid positions the mouse cursor changes relative to the window (Dragging it off moves the window instantly to the center while the mouse pointer keeps its position), which is unwanted behaviour. + Dragging off these windows used to work in Quantal for semi-maximized and maximized state, but back then another bug appeared for semi maximized state which is now gone: the horizontal width of the window was not correctly reset. + After the mouse pointer was set (to drag off the window), the location of the reset window should not change. + The following video demonstrates this behavior: http://ubuntuone.com/1MYUTOAYKqGGdiijKZZZag -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115350 Title: Grid: Dragging screen centric windows (e.g. Sim unlock required) causes cursor being changed relative to the window To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115350/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 729979] Re: [nvidia] Windows appear blank white
@Sam: As I wrote you per mail, your branches seem to fix the minimize issue. Have not tested (as I could not) the spread one (see #135) though. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 729979] Re: [nvidia] Windows appear blank white
I tried to build it on raring (as I said latest daily build, installed only for compiling this branch), but make gives me the mentioned error. I would really like to test this branch to finally test if this bug is gone, because now I have one week time to test. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115341] [NEW] Grid resize: Placing maximized windows on the top edge using shortcuts does not work
Public bug reported: Pressing Strg + Alt + KP (7, 8, 9) in order to position a maximized window in the top corners or on the top half, the panel is not considered, meaning that part of the window disappears under the panel which is unwanted behavior. The following video demonstrates this: http://ubuntuone.com/2FZ7UGfyrVl0MIHZflaYba ** Affects: compiz Importance: Undecided Status: New ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: 0.9.9.2 compiz ** Package changed: compiz (Ubuntu) = compiz ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115341 Title: Grid resize: Placing maximized windows on the top edge using shortcuts does not work To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115341/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1082001] Re: Grid/Expo: Corner-resized Grid windows confuse Expo and follow the user from workspace to workspace
Updated description because bug title and description are not complete: Bottom/Top half grid windows are also affected. ** Description changed: [Test Case] 1. Open a window 2. Hit Ctrl+Alt+Numpad3 to resize it via Grid (for example Firefox) into a corner. -Alternatively you can drag the window to a corner to grid-resize it. + Alternatively you can drag the window to a corner to grid-resize it. 3. Open any other window (for example a terminal) 4. Trigger Expo (via Launcher's Workspace Switcher icon or by hitting Super+S for example) 5. Now drag the non-gridded second window (terminal in our case here) to another workspace/viewport What you would expect to happen: The terminal window should now be on the new viewport. The other window should not change position. What actually happens: No matter on which workspace the terminal window is dragged to, the *gridded* window follows. Wait, it gets even better: If you try to switch the workspace without dragging a window, the *gridded* window will follow you, whereever you go. If you resize multiple windows via Grid all will follow you from workspace to workspace. Note 1: I have tested this in a virtual machine with a vanilla default up-to-date installation of Raring also, to make sure non-default settings are not causing this problem. Note 2: This bug makes using Grid in combination with Expo (which are both enabled by default on Ubuntu) completely unusable and should have high priority. - Note 3: Just corner-gridded windows seem to be affected. + + SUMMARY: + When a window gets positioned in a corner or the top/bottom half and you switch workspace using ẃorkspace switcher the window gets positioned on every workspace you switch to on exactly the same position. + Same is true for dragging one window on the same workspace as the grid positioned window (corners or top/bottom half) to another workspace: the grid placed window follows to the workspace the other window is dragged to. + This behavior is not true for windows that have grid positions when launched! + The following video demonstrates the bug: + http://ubuntuone.com/2s8kNGM6Qcp3WFfjOwe6XX ** Tags added: 0.9.9.2 compiz -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1082001 Title: Grid/Expo: Corner-resized Grid windows confuse Expo and follow the user from workspace to workspace To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1082001/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115343] [NEW] Semi-maximized windows do not maximize correctly using the maximize button
Public bug reported: After semi-maximizing (right/left half) a window it can not be maximized pressing the maximize button the first time. Instead the size before semi maximizing the window gets restored, so you need to press the maximize button again in order to really maximize the window. If an application is already semi maximized when opening, maximizing works. The following video demonstrates this: http://ubuntuone.com/43jbUlTisO1Ehg6keRyfF7 ** Affects: compiz Importance: Undecided Status: New ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: 0.9.9.2 compiz ** Also affects: compiz Importance: Undecided Status: New -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115343 Title: Semi-maximized windows do not maximize correctly using the maximize button To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115343/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115351] [NEW] Workspace switcher: Right clicking launcher items makes quicklist always appearing by changing the workspace (switcher)
Public bug reported: If you right click items on the launcher during the use of workspace switcher, the quicklist is shown on the selected workspace, which is okay, but from now on everytime you switch the workspace using expo/workspace switcher the quicklist is shown. The following video demonstrates this behavior: http://ubuntuone.com/17JaNfW7lfmpKgKLqAyIvO ** Affects: compiz Importance: Undecided Status: New ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: 0.9.9.2 compiz raring ** Also affects: compiz Importance: Undecided Status: New -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115351 Title: Workspace switcher: Right clicking launcher items makes quicklist always appearing by changing the workspace (switcher) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115351/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115344] [NEW] Grid + Maximizing (button) + snapping by mouse to Grid position changes cursor position relative to window
Public bug reported: Using maximize button for windows positioned in corners and snapping the window back to original position (per mouse) results in the cursor position getting changed relatively to the window (similar as described in bug 201681). The following video demonstrates this: http://ubuntuone.com/0nw76anw9GouKK9iAYhwGS ** Affects: compiz Importance: Undecided Status: New ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: 0.9.9.2 compiz ** Also affects: compiz Importance: Undecided Status: New -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115344 Title: Grid + Maximizing (button) + snapping by mouse to Grid position changes cursor position relative to window To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115344/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115350] [NEW] Grid: Dragging screen centric windows (e.g. Sim unlock required) causes cursor being changed relative to the window
Public bug reported: If you resize a window which default position is set to the middle of the screen, for example the SIM PIN Unlock required window, it gets moved the center of the screen. (This behavior is not reproducable on Quantal). If you position the window and drag it off from grid positions the mouse cursor changes relative to the window (Dragging it off moves the window instantly to the center while the mouse pointer keeps its position), which is unwanted behaviour. Dragging off these windows used to work in Quantal for semi-maximized and maximized state, but back then another bug appeared for semi maximized state which is now gone: the horizontal width of the window was not correctly reset. After the mouse pointer was set (to drag off the window), the location of the reset window should not change. The following video demonstrates this behavior: http://ubuntuone.com/1MYUTOAYKqGGdiijKZZZag ** Affects: compiz Importance: Undecided Status: New ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: 0.9.9.2 compiz ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115350 Title: Grid: Dragging screen centric windows (e.g. Sim unlock required) causes cursor being changed relative to the window To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115350/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1115353] [NEW] Resizing windows (accessibility menu) using arrow keys does not work if resizing using more than one boarder
Public bug reported: If you attempt to resize a window by using the arrow keys and switch between the window boarders (e.g. using up-arrow-key and afterwards right-arrow-key) two issues prevent resizing: 1.) When changing boarders the cursor does not get positioned on the boarder of the orange preview box, but on the corner of the original window, which should only be the case if the windows size was not already modified using this boarder. 2.) If you modify the height of a window and switch boarders to modify the width of a window, the height of the orange preview box gets reset to the height of the original window, the upper boarder of the orange preview box always stays the same. This means if you resize using the bottom boarder, switch to another boarder and start to resize, the orange previewbox gets reset so that it is congruent to the original window (with the exception of the boarder you just modified of course. ) If you modify the width of a window and switch boarders to modify the height of a window, the width of the orange preview box gets reset to the width of the original window, the left boarder of the orange preview box always stays the same. This means if you resize using the right boarder, switch to another boarder and start to resize, the orange previewbox gets reset so that it is congruent to the original window (with the exception of the boarder you just modified of course. ) This two factors cause the cursor to be positioned relative to the orange preview box. The following video demonstrates this issue: http://ubuntuone.com/4wuuFxXU6VCJQVXGv3l6sM ** Affects: compiz Importance: Undecided Status: New ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: 0.9.9.2 compiz raring ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1115353 Title: Resizing windows (accessibility menu) using arrow keys does not work if resizing using more than one boarder To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1115353/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 729979] Re: [nvidia] Windows appear blank white
Sam, I am afraid I cannot build your unity branch anymore (on a fresh install of today's daily build) ... I do not know what is causing this error (I have tried everything: compiling and installing bamf and nux first etc.). All build dependencies were fullfilled. I suppose it is not necessary anymore to compile your compiz branch as it has already merged, am I right? (https://bugs.launchpad.net/compiz/+bug/1089811) If I compile unity I get the following error: [ 16%] Building CXX object unity-shared/CMakeFiles/unity-shared.dir/IconLoader.cpp.o /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp: In member function ‘void unity::IconLoader::Impl::IconLoaderTask::PushSchedulerJob()’: /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:637:9: error: ‘void g_io_scheduler_push_job(GIOSchedulerJobFunc, gpointer, GDestroyNotify, gint, GCancellable*)’ is deprecated (declared at /usr/include/glib-2.0/gio/gioscheduler.h:36): Use 'GThreadPool or g_task_run_in_thread' instead [-Werror=deprecated-declarations] /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:637:93: error: ‘void g_io_scheduler_push_job(GIOSchedulerJobFunc, gpointer, GDestroyNotify, gint, GCancellable*)’ is deprecated (declared at /usr/include/glib-2.0/gio/gioscheduler.h:36): Use 'GThreadPool or g_task_run_in_thread' instead [-Werror=deprecated-declarations] /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp: In static member function ‘static gboolean unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc(GIOSchedulerJob*, GCancellable*, gpointer)’: /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:672:7: error: ‘void g_io_scheduler_job_send_to_mainloop_async(GIOSchedulerJob*, GSourceFunc, gpointer, GDestroyNotify)’ is deprecated (declared at /usr/include/glib-2.0/gio/gioscheduler.h:49): Use 'g_main_context_invoke' instead [-Werror=deprecated-declarations] /home/user/unity.fix_1091600/unity-shared/IconLoader.cpp:672:86: error: ‘void g_io_scheduler_job_send_to_mainloop_async(GIOSchedulerJob*, GSourceFunc, gpointer, GDestroyNotify)’ is deprecated (declared at /usr/include/glib-2.0/gio/gioscheduler.h:49): Use 'g_main_context_invoke' instead [-Werror=deprecated-declarations] cc1plus: all warnings being treated as errors make[2]: *** [unity-shared/CMakeFiles/unity-shared.dir/IconLoader.cpp.o] Error 1 make[1]: *** [unity-shared/CMakeFiles/unity-shared.dir/all] Error 2 make: *** [all] Error 2 -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 729979] Re: [nvidia] Windows appear blank white
@Sam, you can see the output of DISPLAY=:0 LD_LIBRARY_PATH=./lib valgrind ./bin/compiz --replace unityshell here: http://ubuntuone.com/00Wd4umgSCxKuxswRIAEkN (--replace ccp works, i only get the crash if i attempt to start unityshell). I noticed that the minimize problem disappears when I disable unity plugin in compiz, so your approach might be right. Sam, how would you build compiz and unity? I compiled unity first using this instruction: http://askubuntu.com/questions/28470/how-do-i-build-unity-from-source/28472#28472 After that I compiled compiz using this instruction: https://answers.launchpad.net/compiz/+question/203490 (comment #1) and started compiz. I will try the pbuilder approach too when I have time. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 729979] Re: [nvidia] Windows appear blank white
Okay I compiled both, but I cannot load unityshell plugin: it reports me an segmentation fault and aborts. Both unity and compiz compiled successfully. I installed them both in my home directory and started compiz with env DISPLAY=:0 LD_LIBRARY_PATH=./lib ./bin/compiz --replace core ccp composite opengl decor snap imgpng compiztoolbox mousepoll move regex vpswitch animation resize grid wall expo place workarounds session fade ezoom scale unityshell Unity was installed the following way: http://askubuntu.com/questions/28470/how-do-i-build-unity-from- source/28472#28472 so I suppose it is working all the time with the installed compiz version, but not with my compiled compiz version. Even using old unity compiz fails to load unity (but wihtout a segmentation error). -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 729979] Re: [nvidia] Windows appear blank white
@Sam: I tried to build both, but I could not compile unity : Cmake has a problem with zeitgeist. Is the version I have installed too new? Output is attached below. I was trying to build it on Raring latest updates. Compiz was built sucessfully, but I cannot test it without building unity (as compiz is incompatible with the installed unity, I suppose this is meant to be so, if not please mention in a response.) ** Attachment added: output.txt https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/729979/+attachment/3480354/+files/output.txt -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 729979] Re: [nvidia] Windows appear blank white
Excuse me, I attached the file in a wrong way. You can find it here: http://ubuntuone.com/6hsVC0HWDdWT2ky9Sux0vE ** Attachment removed: output.txt https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/729979/+attachment/3480354/+files/output.txt -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 729979] Re: [nvidia] Windows appear blank white
@Sam I put the description here because of https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/995659/comments/2 Maybe what I have described is really another bug, because the description of Bug #729979 does not say anything to me, meaning I was never able to reproduce that bug by clicking on the titlebars of two (or more) windows alternately. You said you could not reproduce it, so do I (at least until now). But my way to reproduce the blank windows mentioned in comment #135 does always works. Does it work on you setup too? I just noticed that in comment #132 and #134 part of my problem was already mentioned and therefore confirmed. Yes if you have the code, I am willing to test it out. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 729979] Re: [nvidia] Windows appear blank white
To make the bug easier to see and understand, make the animation slower: dconf write /com/canonical/unity/minimize-slow-duration 3000 (You can undo this easily with dconf reset /com/canonical/unity/minimize-slow-duration) Now the animation should be slow enough to be able to interrupt it (meaning you are able to press the minimize button, and can move the mouse pointer faster to the launcher symbol and press it than the animated window is going there). You can alternatively reproduce the effects shown in the linked video by moving the mouse pointer to the launcher and try to click the application instantly after the animation was initiated by pressing Strg + Alt + KP0 (numpad 0 key). The main point is, the bug seems to be quite randomly with default settings (most of the time it does not work, however there are situations when it works). I found out, that you can reproduce the bug for sure if you apply the dconf setting mentioned above (you could also apply higher values). The slower the animation is, the more likely it is, that the bug happens. The behaviour is shown in the following video: http://ubuntuone.com/5xMF480diMFbN5np9rERcP Now the very important part: You can see, that the minimize animation ALWAYS works, when it was interrupted before (and the window is black, or without any content). But you have to consider, you are not allowed to shade/unshade, resize or click away from the window! This means doing only minimizing and unminimizing behind one another of the same window (without doing anything that makes the missing window content disappear), it works every second time. If an window is opened, there is no way, that the animation works the first time minimizing, except you maximize it! This means you can always get the animation working if you maximize it before you press the minimize button (you have to maximize again even if the application is already maximized). So to conclude there are two ways of always getting the animation work. I have found an equivalent way to reproducing the bug (which could be relevant): http://ubuntuone.com/16WmSevvitMlG8XfkfYzfE (Note: For single windows in the video the ESC button was used to leave the spread without selecting the window. ) If you minimize a non fullscreen window (after you have opened it), click the spread view, leave it without selecting the minimized window and unminimize it, it gets the same condition as interrupting a window minimize. This behaviour is not true for windows, that minimized correctly before, so the bug does not work for windows maximized an then minimised (last example in the video). The behaviour shown in the second video is a consequence of the bug shown in the first video, so if you can reproduce the second bug this is also a proof for having the first bug. The window content is missing when this bug appears, but if the window content is black or completely missing, depends if the window is transparent, or not. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/729979 Title: [nvidia] Windows appear blank white To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/729979/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1093757] Re: Using grid-resize prevents windows from maximizing correctly
After maximizing, the window does not get placed correctly in the upper corners by using the shortcut. (e.g. ControlAltKP9). Everything else is fixed by the fix commited. This can be seen in the following video: http://ubuntuone.com/6N42jasIsueBiLpdCzkdBo -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1093757 Title: Using grid-resize prevents windows from maximizing correctly To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1093757/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1037164] Re: Clicking on semi-maximized windows in a different workspace produce unexpected results
http://ubuntuone.com/2JBSfSD69fTrjLzQWmNgoe If the window is placed in a corner and I use the workspace switcher in the launcher, the window gets placed on the workspace I switch to, as shown in the video. However, if I switch by shortcut, and then access the window with the launcher, the window gets moved to the workspace it was accessed from, so the behavior is not exactly the same as for the semi maximized windows. I noticed, that the bug also works for up and down, but only in a special case as shown in the video: if I open the application an semimaximize it, the bug does not work, but if I close the application and reopen it, it has the same position and I access it from the upper workspace the same behaviour is shown, as for the right left issue. (Note: the window has to have exactly the same size after reopening, otherwise the bug does not seem to appear. You cannot reproduce it with a terminal window) -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1037164 Title: Clicking on semi-maximized windows in a different workspace produce unexpected results To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1037164/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 755842] Re: Non-maximized windows which sit on the border of a workspace move when called
I know you say the bug is fixed and we should open a new bug report, but the issue remains for Compiz version 0.9.9 with exactly the same behavior (But it is indeed partly fixed). Does it really make sense to open a new bug report describing exactly the same issue? This part of the description is fixed: TESTCASE 1: 1. Move a window to the far right workspace so that it overlaps the right side of the screen a little. 2. Switch to the far left workspace where you can see a little of the overlapping window. 3. Alt-Tab to the window. Observed: Window jumps to being entirely on the far left workspace. Expected: Window stays where it was. TESTCASE 2: 1. Move a window to the far left workspace so that it overlaps the left side of the screen a little. 2. Switch to the far right workspace where you can see a little of the overlapping window. 3. Alt-Tab to the window. Observed: Window jumps to being entirely on the far left workspace. Expected: Window stays where it was. This part of the issue is NOT fixed: 1. Put a non-maximized window against the border of your workspace 2. Switch to the adjoining workspace 3. Select the window in Unity Expected Behavior You are switched back to the workspace with the window What actually happens You stay in the current workspace AND the window is shifted slightly into the current workspace I can only confirm that the issue is definitely not fixed on the latest compiz builds (both latest offical Compiz 0.9.9 and Compiz Experimental PPA) . Daniel, should I open a new bug describing the part which is not fixed? -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/755842 Title: Non-maximized windows which sit on the border of a workspace move when called To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/755842/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 755842] Re: Non-maximized windows which sit on the border of a workspace move when called
Oh there is already a bug report : https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1037164 It is not marked fixed and exactly describes the part of the issue which has been left. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/755842 Title: Non-maximized windows which sit on the border of a workspace move when called To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/755842/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1037164] Re: Clicking on semi-maximized windows in a different workspace produce unexpected results
If the window is placed in the upper right corner (ControlAltKP9) or in bottom right corner (ControlAltKP3) the behaviour is also wrong but different: Now the window keeps it's position but moves to the workspace it was accessed from: For example place a window on the upper right workspace in the upper right corner and change to the upper left workspace. Now click the icon in the launcher and the window is dragged completely in the current (upper left) workspace. To conclude, all the transitions concerning accessing a window that is placed on a workspace right to the current workspace do not work. All the transitions for accessing a window in a workspace left to the current workspace work. Only right and left matters, the height does not matter (meaning it does not matter if it is the upper right workspace or the bottom right workspace, only right matters). -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1037164 Title: Clicking on semi-maximized windows in a different workspace produce unexpected results To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1037164/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1037164] Re: Clicking on semi-maximized windows in a different workspace produce unexpected results
** Tags added: compiz-experimental-ppa -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1037164 Title: Clicking on semi-maximized windows in a different workspace produce unexpected results To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1037164/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 1027211] Re: [nvidia] Moving windows freezes and stutters on nvidia (especially if some other window is redrawing).
A good message: With compiz 1:0.9.9~daily12.12.05-0ubuntu2 updated today (on 13.04) and the latest Nvidia 313.09 drivers window resizing is ways better (not perfect but definitely much better). Before today I was not able to resize a window in normal mode, now it is possible (even if there are too much grey areas left). -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1027211 Title: [nvidia] Moving windows freezes and stutters on nvidia (especially if some other window is redrawing). To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1027211/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
[Compiz] [Bug 803296] Re: [regression] Compiz Resize plugin: When Default Resize Mode = Normal, resizing is extremely slow and CPU intensive
I can confirm this bug on Ubuntu 13.04 (latest update from December 5). The windows resize very slowly and the grey areas are very big. Furthermore there is a much too high cpu usage. Compiz 0.9.9 (compiz 1:0.9.9~daily12.12.05-0ubuntu1) NVIDIA Driver Version: 310.19 (Graphics Card: Nvidia Quadro 1000M) I am ready to help with testing. -- You received this bug notification because you are a member of compiz packagers, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/803296 Title: [regression] Compiz Resize plugin: When Default Resize Mode = Normal, resizing is extremely slow and CPU intensive To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/803296/+subscriptions ___ Mailing list: https://launchpad.net/~compiz Post to : compiz@lists.launchpad.net Unsubscribe : https://launchpad.net/~compiz More help : https://help.launchpad.net/ListHelp
