Docky with xcompmgr reports no compositing and greys out options
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Docky |
New
|
Low
|
Unassigned | ||
Bug Description
Trying to build a reference system to bring my GF's low-resources (1.2GHz single core) system back to life, using Virtualbox as the target for experimentation.
Docky complained about the lack of compositing when first installed, so I added the lightweight xcompmgr to the system. Subsequently the dock started working with transparency, but still alerts that there's no compositing, and preference options requiring compositing are all greyed out, meaning I can't use auto-hide etc.
Dragging a window 'underneath' docky proves that indeed the compositing support in the system supports the kind of rendering required to support auto-hide.
Is there a way I can encourage docky to attempt richer behaviour, and ungrey the options? Do I need to notify it of it's relationship to xcompmgr more explicitly?
| Cefn (6-launchpad-net-cefn-com) wrote | #1 |
| Changed in docky: | |
| importance: | Undecided → Low |
I cannot seem to attach the apport report from...
sudo apport-cli -f -p docky --save bug.apport
...as the launchpad server fails hard responding my browser is sending something which the server cannot "understand". Happy to share this extra information if someone knows how.