Grid Resize Actions Are Not Working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Compiz Core |
Expired
|
Undecided
|
Unassigned | ||
compiz (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
Grid Resize Actions No Longer does anything
CCSM->Window Management-
Set up the resizing of windows here, and try to get it to automatically resize a window by dragging the window with the mouse until the mouse hits a corner or an edge.
Also try setting up the shortcuts, and trying them too.
Neither one of these ways is working. (at least for me, right now)
and Yes, the Grid plugin is enabled.
p.s.
a large portion of the Maximumize plugin bindings don't work either.
I'm using the ccsm from git, with the Compiz from the repository (all Compiz 0.9.x packages installed)
(just noticed above after writing this bug report, tried the repository's ccsm, got:
Info: No sexy-python package found, don't worry it's optional.
Traceback (most recent call last):
File "/usr/local/
context = compizconfig.
File "compizconfig.pyx", line 1082, in compizconfig.
TypeError: an integer is required
)
lsb_release -idrc
Distributor ID: Ubuntu
Description: Ubuntu 11.04
Release: 11.04
Codename: natty
uname -m
x86_64
Changed in compiz (Ubuntu): | |
status: | Expired → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. Compiz, in particular, is in heavy development and this bug may have been fixed in the development version of Ubuntu (12.04) if not on your current version. If you are able, it would be of great help if you could confirm if the bug still exists by testing a livecd (available at ubuntu.com). When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue. If you are unable to test the development version, please let us know if you are able to reproduce this issue on Ubuntu 11.10.
Thank you for your help and patience.