*** This bug is a duplicate of bug 1158161 ***
https://bugs.launchpad.net/bugs/1158161
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1158161, so it is being marked as such. Please
*** This bug is a duplicate of bug 1140505 ***
https://bugs.launchpad.net/bugs/1140505
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1140505, so it is being marked as such. Please
*** This bug is a duplicate of bug 1140505 ***
https://bugs.launchpad.net/bugs/1140505
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1140505, so it is being marked as such. Please
*** This bug is a duplicate of bug 1140505 ***
https://bugs.launchpad.net/bugs/1140505
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1140505, so it is being marked as such. Please
At least for me having unity loaded makes no difference. Starting compiz
with 'compiz --replace core composite opengl decor' is enough to
reproduce this issue (decor seems to be required to trigger this bug).
--
You received this bug notification because you are a member of compiz
packagers,
** Also affects: compiz
Importance: Undecided
Status: New
** Changed in: compiz
Status: New = Confirmed
--
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/1138517
Title:
This seems to be a regression caused by compiz r3623 (reverting that
revision makes the gap disappear) and is not Unity related (this can be
reproduced by just loading core and decor plugins).
** Package changed: unity (Ubuntu) = compiz (Ubuntu)
** Also affects: compiz
Importance: Undecided
** Summary changed:
- Wallpaper bleeds through on top right when app is maximized
+ [regression-r3623] Wallpaper bleeds through on top right when a window is
opened maximized
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in
Although this bug happens often with grid plugin, it's not the root
cause of this issue (there was a bug in grid that has kept this problem
hidden in the past). This bug can be reproduced with only core loaded by
maximizing and restoring terminal window using key bindings.
When the window is
*** This bug is a duplicate of bug 1082001 ***
https://bugs.launchpad.net/bugs/1082001
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1082001, so it is being marked as such. Please
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
** Changed in: compiz (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
Public bug reported:
Steps to reproduce:
1. Open Gnome Terminal
2. Maximize the window with the maximize keybinding (Ctrl+Super+Up)
3. Immidiately restore the window with the restore window keybinding
(Ctrl+Super+Down)
What happens:
- Window is unmaximized but it still fills the entire desktop
No, this isn't fixed yet (but I can't change the status). Wonder why
launchpad thinks this is...
--
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/925867
Title:
[regression] Window
The crash seems to happen when the random animation chosen is dodge
that's only supposed to be used as focus animation.
Dodge animation is occasionally chosen as it's initialized with
AnimEffectUsedFor::none() which incorrectly marks the dodge animation to
be used with all events.
The same
** Changed in: compiz
Assignee: (unassigned) = sampo555 (sampo555)
** Changed in: compiz
Status: New = In Progress
--
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/1048840
** Changed in: compiz
Assignee: (unassigned) = sampo555 (sampo555)
** Changed in: compiz
Status: New = In Progress
--
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/1098185
For Quantal this was (probably) fixed by r3296 in
lp:ubuntu/compiz/quantal (the lost patch was merged back to the
packaging).
--
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/1035114
I did some digging about this issue and discovered that if a window is
semi maximized, CompWindow::border is set to values of maximized window
borders (left 0px, right 0px) but the normal border (left 1px, right
1px) is still drawn around semi-maximized windows.
So, if a window is semi-maximized,
** Changed in: compiz/0.9.8
Status: Triaged = In Progress
** Changed in: compiz/0.9.8
Assignee: (unassigned) = sampo555 (sampo555)
--
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net
*** This bug is a duplicate of bug 1040885 ***
https://bugs.launchpad.net/bugs/1040885
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1040885, so it is being marked as such. Please
** Changed in: compiz
Status: Confirmed = In Progress
** Changed in: compiz
Assignee: (unassigned) = sampo555 (sampo555)
--
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
** Changed in: compiz
Status: New = In Progress
** Changed in: compiz
Assignee: (unassigned) = sampo555 (sampo555)
--
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/1066187
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command, as it will automatically gather
debugging information, in a terminal:
apport-collect 1057283
This bug did not have a package associated with it, which is important
for
I think this is actually the same bug as bug 1037142. The result is just a
little different. Test the following:
1. Open a new window (not maximized)
2. Start workspace switcher
3. Click once on the opened, non-maximized window [Workspace switcher closes]
4. Move mouse to the top edge of your
A little more reliable way to reproduce this bug:
1. Open a new window (not maximized)
2. Start workspace switcher
3. Click once on the opened, non-maximized window [Workspace switcher closes]
4. Move mouse to the top/left/right edge of your screen
5. An orange grid overlay appears covering
This seems to be fixed in Quantal (and in Compiz trunk) as windows seem
follow my mouse no matter what try (drag windows around, grab semi-
maximised windows).
After some digging and testing, the fix seems to be in revision 63 of lp
:compiz-snap-plugin which was later merged to lp:compiz. As the
** 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/1035114
Title:
[Regression][Expo] Focused workspace in
** Description changed:
- This feature got lost in Quantal when lp:compiz-expo-plugin (without
- this feature) was merged to the compiz trunk.
-
- The code to add this functionality back can be found from lp:ubuntu
- /compiz-plugins-main
+ This feature got lost in Quantal when
The problem is only happening when the window is maximized to the Left
or Right edge. If you place a window to for example top left, or bottom,
the window is resized correctly after it's snapped away from its
position.
Grid leaves the unmaximation to some other component and that doesn't
restore
This is not actually caused by workspace switch or is limited to two
windows of the same app. It's a bit more generic issue.
After playing around with fullscreen windows, I found out that following things
happen:
1. Press F11 - Window A is fullscreened
2. Change to Window B - Press F11 - Window
I was able to reproduce this in Oneiric with Compiz version
1:0.9.6+bzr20110929-0ubuntu6.
--
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/284362
Title:
Crash pressing alt+f4 while in
31 matches
Mail list logo
