This bug appears to be fixed in Trusty.
$ python3 undecoratated.py
configure-event w=100 h=100 origin=(1, 0, 0)
configure-event w=100 h=100 origin=(1, 50, 50)
configure-event w=100 h=100 origin=(1, 50, 50)
configure-event w=100 h=100 origin=(1, 50, 50)
All good, and it doesn't affect Onboard
** Changed in: onboard (Ubuntu)
Status: New = Fix Released
--
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/882825
Title:
Does not save the configuration file under ~/.config/
** Package changed: gtk+3.0 (Ubuntu) = ubuntu
** Package changed: ubuntu = compiz (Ubuntu)
** 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.
I was always using screen0 and
dbus-send --print-reply --dest=org.freedesktop.compiz
/org/freedesktop/compiz/obs/screen0/brightness_values
org.freedesktop.compiz.set array:int32:80
doesn't work. If no introspection, Is there any up-to-date documentation or
working examples?
--
You received
Same here, I used to set screen brightness with something like
dbus-send --print-reply --dest=org.freedesktop.compiz
/org/freedesktop/compiz-1/obs/screen0/brightness_values
org.freedesktop.compiz.set array:int32:80
that has no effect now.
Also the examples at http://wiki.compiz.org/Plugins/Dbus
Testing compiz 1:0.8.3+git20091005-0ubuntu5 with xorg-edgers
libdrm/mesa/glx/drm on radeon HD 4670 and X-GNOME-AutoRestart=false in
/usr/share/applications/nautilus.desktop.
The screen corruption is no where to be seen. The only glitch I came
across is a brief unfiltered flash of every freshly
6 matches
Mail list logo
