Re: [Calise-testing] calised -d : screen brightness (avg) always 0.0

[Developement v. t. r. a. d. <cal...@li...>]

It's gonna be very long!
(btw yes, i'm using it as root with calised.timer :)  )
->calised --dump-settings | grep screen
screen: True
->echo $DISPLAY
:0.0
->dbus-send --system --print-reply --type=method_call
--dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager
org.freedesktop.ConsoleKit.Manager.GetSeats
method return sender=:1.1 -> dest=:1.185 reply_serial=2
   array [
      object path "/org/freedesktop/ConsoleKit/Seat1"
   ]
->dbus-send --system --print-reply --type=method_call
--dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Seat1
org.freedesktop.ConsoleKit.Seat.GetActiveSession
method return sender=:1.1 -> dest=:1.186 reply_serial=2
   object path "/org/freedesktop/ConsoleKit/Session1"
->dbus-send --system --print-reply --type=method_call
--dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Session1
org.freedesktop.ConsoleKit.Session.GetX11Display
method return sender=:1.1 -> dest=:1.187 reply_serial=2
   string ":0.0"

I don't understand anything of these lines :D

2012/7/14 Developement versions test results and discussion <
cal...@li...>

> Il 13/07/2012 19:50, Developement versions test results and discussion
> ha scritto:
> > Ok. To be sure, i restarted now calised.
> > I'm in my xfce4 session, and no one of the choices you gave me is true.
> > "date -d @1342201920.59
> > ven 13 lug 2012, 19.52.00, CEST"
> > calised -d:
> > current backlight step:     8147
> > capture timestamp (epoch):  1342201920.59
> > secs before next day state: 7032.40669298
> > day cycle state:            sunset
> > suggested backlight step:   8147
> > ambient brightness:         54.6666666667
> > secs between captures:      65.608
> > brightness percentage:      67.7187477963
> > screen brightness (avg):    0
>
> Ok, then seems to be a bug.
> Try doing:
>
>     calised --dump-settings | grep screen
>
> and
>
>     echo $DISPLAY
>
>
> If the first is set to True and $DISPLAY is not empty then:
>
>     $ dbus-send --system --print-reply --type=method_call
>     --dest=org.freedesktop.ConsoleKit
>     /org/freedesktop/ConsoleKit/Manager
>     org.freedesktop.ConsoleKit.Manager.GetSeats
>
> use object path (usually "/org/freedesktop/ConsoleKit/Seat1") to replace
> (eventually) the one in the row below:
>
>     $ dbus-send --system --print-reply --type=method_call
>     --dest=org.freedesktop.ConsoleKit
>     */org/freedesktop/ConsoleKit/Seat1*
>     org.freedesktop.ConsoleKit.Seat.GetActiveSession
>
> as for just before use object path (usually
> "/org/freedesktop/ConsoleKit/Session1") to replace (eventually) the one
> below:
>
>     $ dbus-send --system --print-reply --type=method_call
>     --dest=org.freedesktop.ConsoleKit
>     */org/freedesktop/ConsoleKit/Session1*
>     org.freedesktop.ConsoleKit.Session.GetX11Display
>
> These are dbus queries that calise sends to know if and, if true, what
> X11 display is active.
> There can be a bug for these since I've set the first of them to run
> once (I thought "seat" won't change).
> Actually accessing any X11 display from outside is "pain in the ass",
> really, even root has to substand X policies and magics...
>
> Thank you for reporting (btw, you're using as root on system startup
> right?).
>
> PS: Just seen your comment on webupd8 calise post: «man, who cares about
> graphical user interfaces, just gimmie the text!!!»
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Calise-testing mailing list
> Cal...@li...
> https://lists.sourceforge.net/lists/listinfo/calise-testing
>