On Sat, Aug 01, 2015 at 09:28:17AM -0300, Fernando de Oliveira wrote:
> Em 30-07-2015 16:50, Ken Moffat escreveu:
> > On Thu, Jul 30, 2015 at 12:01:48PM -0300, Fernando de Oliveira wrote:
> >> Em 25-07-2015 16:06, Ken Moffat escreveu:

Just a brief reply at the moment, I need to refresh the leaven for
my sourdough if I'm going to bake tomorrow.  I'll need to take some
time to look at the details in your post.

> 
> > I also noticed that image buttons did not appear when running the
> > test (not surprising, sddm is not running because I'm in runlevel 3)
> > but the text buttons  ('login' etc) do : on images, these were only
> > visible if the 'can' function returned true.
> 
> Think I have to do it myself to understand this "can" (two or three days
> since I read the code, cannot remember anymore).
> 

The 'canPoweoff', 'canReboot', 'canSuspend', 'canHibernate' are what
is giving me the problem.  They are set by calling dbus to ask
ConsoleKit, polkit and upower [ with pm-utils ] to see if the
current user is allowed to do the action.

For polkit, the old local .plka files are no longer used - now that
mozjs is required there are .rules [ man 8 polkit ] but on their own
they are not the problem for me.

> > At the moment I have
> > made these unconditional (with the elarun theme I got varying results
> > for canSuspend in my earlier testing) but I have not yet reached a
> > place where I'm ready to see if my new theme works.
> 
> Please, update here, when you get it done.
> 

My current status: if I use runlevel 3 to run startkde (the only way
I can run the theme test at the moment) and then change to runlevel
5 my changes work : I can suspend (I don't have swap on this machine,
so hibernate is not possible), I can login, or I can reboot or
poweroff.  But after booting all I can do is login.

I managed to login to a tty as root to get a list of processes when
the greeter is running in runlevel 5, and saw that after startkde
has run there are extra processes for console-kit-daemon [
--no-daemon ], polkitd, upower, udisks2.

So I started trying to write a proper bootscript to fire all those
up.  But it hangs (waiting for Ctrl-C) after most of those daemons
start.  After hitting Ctrl-C enough times the greeter starts but I
still do not have the 'can' capabilities.

With further testing the upowerd and udisks2 startups also reported
errors.  The whole thing is so complex that I begin to unbderstand
some of the desire for systemd.

I know that most of the supplied sddm themes use text buttons to
handle login, poweroff, reboot and those are always displayed but
they seem to invoke the same code as the icons (ImageButton).

How are you starting sddm, please ?  I think you said you use a
bootscript - do you start anything else ?

ĸen
-- 
This one goes up to eleven!
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to