[gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[Mick]

[-- Attachment #1: Type: text/plain, Size: 457 bytes --]

Can someone please explain how the removal of the 'wireless' USE flag from 
powerdevil ends up with no buttons for Suspend-to-RAM, Hibernation, Reboot or 
Shutdown under the Leave tab of the KMenu?  What does wireless have to do with 
those functions which should work regardless?

Also, the sddm DM shutdown/reboot buttons now do not work. O_O

Is Plasma/KDE trying to emulate the inflexibility of Gnome? (no flamewar 
intended please).

-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

On Mon, 24 Jun 2019 21:19:09 +0100, Mick wrote:

> Can someone please explain how the removal of the 'wireless' USE flag
> from powerdevil ends up with no buttons for Suspend-to-RAM,
> Hibernation, Reboot or Shutdown under the Leave tab of the KMenu?  What
> does wireless have to do with those functions which should work
> regardless?

Those options are still present here.


-- 
Neil Bothwick

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[Mick]

[-- Attachment #1: Type: text/plain, Size: 3804 bytes --]

On Monday, 24 June 2019 23:41:03 BST Neil Bothwick wrote:
> On Mon, 24 Jun 2019 21:19:09 +0100, Mick wrote:
> > Can someone please explain how the removal of the 'wireless' USE flag
> > from powerdevil ends up with no buttons for Suspend-to-RAM,
> > Hibernation, Reboot or Shutdown under the Leave tab of the KMenu?  What
> > does wireless have to do with those functions which should work
> > regardless?
> 
> Those options are still present here.

Thanks Neil, these are the packages which were depcleaned following USE="-
wireless" for powerdevil, USE="-espeak" for speech-dispatcher and USE="device-
mapper-only -thin" for lvm:

1561390348: Started emerge on: Jun 24, 2019 16:32:28
1561390348:  *** emerge --ask --verbose --depclean
1561390348:  >>> depclean
1561390428: === Unmerging... (virtual/w3m-0)
1561390432:  >>> unmerge success: virtual/w3m-0
1561390432: === Unmerging... (virtual/linux-sources-3)
1561390436:  >>> unmerge success: virtual/linux-sources-3
1561390436: === Unmerging... (kde-frameworks/networkmanager-qt-5.57.0)
1561390440:  >>> unmerge success: kde-frameworks/networkmanager-qt-5.57.0
1561390440: === Unmerging... (sys-block/thin-provisioning-tools-0.7.0)
1561390445:  >>> unmerge success: sys-block/thin-provisioning-tools-0.7.0
1561390445: === Unmerging... (app-accessibility/espeak-1.48.04-r1)
1561390449:  >>> unmerge success: app-accessibility/espeak-1.48.04-r1
1561390449: === Unmerging... (www-client/w3m-0.5.3_p20180125)
1561390453:  >>> unmerge success: www-client/w3m-0.5.3_p20180125
1561390453: === Unmerging... (media-sound/sox-14.4.2-r1)
1561390458:  >>> unmerge success: media-sound/sox-14.4.2-r1
1561390458: === Unmerging... (net-misc/networkmanager-1.16.0)
1561390464:  >>> unmerge success: net-misc/networkmanager-1.16.0
1561390464: === Unmerging... (net-dialup/ppp-2.4.7-r7)
1561390468:  >>> unmerge success: net-dialup/ppp-2.4.7-r7
1561390468: === Unmerging... (net-misc/dhcp-4.4.1)
1561390473:  >>> unmerge success: net-misc/dhcp-4.4.1
1561390473: === Unmerging... (dev-libs/boehm-gc-7.6.4)
1561390478:  >>> unmerge success: dev-libs/boehm-gc-7.6.4
1561390478: === Unmerging... (media-sound/gsm-1.0.13-r1)
1561390482:  >>> unmerge success: media-sound/gsm-1.0.13-r1
1561390482: === Unmerging... (net-libs/libndp-1.7)
1561390486:  >>> unmerge success: net-libs/libndp-1.7
1561390486: === Unmerging... (net-misc/modemmanager-1.8.2-r1)
1561390493:  >>> unmerge success: net-misc/modemmanager-1.8.2-r1
1561390493: === Unmerging... (dev-libs/newt-0.52.20)
1561390497:  >>> unmerge success: dev-libs/newt-0.52.20
1561390497: === Unmerging... (net-dialup/ppp-scripts-0)
1561390501:  >>> unmerge success: net-dialup/ppp-scripts-0
1561390501: === Unmerging... (sys-libs/slang-2.3.2)
1561390505:  >>> unmerge success: sys-libs/slang-2.3.2
1561390505: === Unmerging... (net-libs/libqmi-1.20.2)
1561390510:  >>> unmerge success: net-libs/libqmi-1.20.2
1561390510: === Unmerging... (net-libs/libmbim-1.16.2)
1561390515:  >>> unmerge success: net-libs/libmbim-1.16.2
1561390515:  *** exiting successfully.
1561390515:  *** terminating.
1561390536: Started emerge on: Jun 24, 2019 16:35:36
1561390536:  *** emerge --ask --verbose @preserved-rebuild
1561390543:  *** exiting successfully.
1561390543:  *** terminating.

I can't see anything in there.  I also uninstalled and reinstalled plasma-
meta, but did not depclean anything.  Could there be something in 
systemsettings?  Yep! Power Management is greyed out:

"Power management configuration module could not be loaded. The Power 
Management Service appears not to be running.  This can be solved by starting 
or scheduling it inside "Startup and Shutdown".

What am I supposed to add in "Startup and Shutdown"?  There is no Power 
Management to start up and no button to add any services.  :-/

-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[Dale]

Mick wrote:
> On Monday, 24 June 2019 23:41:03 BST Neil Bothwick wrote:
>> On Mon, 24 Jun 2019 21:19:09 +0100, Mick wrote:
>>> Can someone please explain how the removal of the 'wireless' USE flag
>>> from powerdevil ends up with no buttons for Suspend-to-RAM,
>>> Hibernation, Reboot or Shutdown under the Leave tab of the KMenu?  What
>>> does wireless have to do with those functions which should work
>>> regardless?
>> Those options are still present here.
> Thanks Neil, these are the packages which were depcleaned following USE="-
> wireless" for powerdevil, USE="-espeak" for speech-dispatcher and USE="device-
> mapper-only -thin" for lvm:
>
> 1561390348: Started emerge on: Jun 24, 2019 16:32:28
> 1561390348:  *** emerge --ask --verbose --depclean
> 1561390348:  >>> depclean
> 1561390428: === Unmerging... (virtual/w3m-0)
> 1561390432:  >>> unmerge success: virtual/w3m-0
> 1561390432: === Unmerging... (virtual/linux-sources-3)
> 1561390436:  >>> unmerge success: virtual/linux-sources-3
> 1561390436: === Unmerging... (kde-frameworks/networkmanager-qt-5.57.0)
> 1561390440:  >>> unmerge success: kde-frameworks/networkmanager-qt-5.57.0
> 1561390440: === Unmerging... (sys-block/thin-provisioning-tools-0.7.0)
> 1561390445:  >>> unmerge success: sys-block/thin-provisioning-tools-0.7.0
> 1561390445: === Unmerging... (app-accessibility/espeak-1.48.04-r1)
> 1561390449:  >>> unmerge success: app-accessibility/espeak-1.48.04-r1
> 1561390449: === Unmerging... (www-client/w3m-0.5.3_p20180125)
> 1561390453:  >>> unmerge success: www-client/w3m-0.5.3_p20180125
> 1561390453: === Unmerging... (media-sound/sox-14.4.2-r1)
> 1561390458:  >>> unmerge success: media-sound/sox-14.4.2-r1
> 1561390458: === Unmerging... (net-misc/networkmanager-1.16.0)
> 1561390464:  >>> unmerge success: net-misc/networkmanager-1.16.0
> 1561390464: === Unmerging... (net-dialup/ppp-2.4.7-r7)
> 1561390468:  >>> unmerge success: net-dialup/ppp-2.4.7-r7
> 1561390468: === Unmerging... (net-misc/dhcp-4.4.1)
> 1561390473:  >>> unmerge success: net-misc/dhcp-4.4.1
> 1561390473: === Unmerging... (dev-libs/boehm-gc-7.6.4)
> 1561390478:  >>> unmerge success: dev-libs/boehm-gc-7.6.4
> 1561390478: === Unmerging... (media-sound/gsm-1.0.13-r1)
> 1561390482:  >>> unmerge success: media-sound/gsm-1.0.13-r1
> 1561390482: === Unmerging... (net-libs/libndp-1.7)
> 1561390486:  >>> unmerge success: net-libs/libndp-1.7
> 1561390486: === Unmerging... (net-misc/modemmanager-1.8.2-r1)
> 1561390493:  >>> unmerge success: net-misc/modemmanager-1.8.2-r1
> 1561390493: === Unmerging... (dev-libs/newt-0.52.20)
> 1561390497:  >>> unmerge success: dev-libs/newt-0.52.20
> 1561390497: === Unmerging... (net-dialup/ppp-scripts-0)
> 1561390501:  >>> unmerge success: net-dialup/ppp-scripts-0
> 1561390501: === Unmerging... (sys-libs/slang-2.3.2)
> 1561390505:  >>> unmerge success: sys-libs/slang-2.3.2
> 1561390505: === Unmerging... (net-libs/libqmi-1.20.2)
> 1561390510:  >>> unmerge success: net-libs/libqmi-1.20.2
> 1561390510: === Unmerging... (net-libs/libmbim-1.16.2)
> 1561390515:  >>> unmerge success: net-libs/libmbim-1.16.2
> 1561390515:  *** exiting successfully.
> 1561390515:  *** terminating.
> 1561390536: Started emerge on: Jun 24, 2019 16:35:36
> 1561390536:  *** emerge --ask --verbose @preserved-rebuild
> 1561390543:  *** exiting successfully.
> 1561390543:  *** terminating.
>
> I can't see anything in there.  I also uninstalled and reinstalled plasma-
> meta, but did not depclean anything.  Could there be something in 
> systemsettings?  Yep! Power Management is greyed out:
>
> "Power management configuration module could not be loaded. The Power 
> Management Service appears not to be running.  This can be solved by starting 
> or scheduling it inside "Startup and Shutdown".
>
> What am I supposed to add in "Startup and Shutdown"?  There is no Power 
> Management to start up and no button to add any services.  :-/
>

I wonder if something is trying to use a old config file.  You may want
to use checkrestart, needrestart or something to check on that.  I still
have checkrestart here but needrestart should pick this up.  If it is
that, logout, got to a console and restart X.  I sometimes just go to
the boot runlevel, make sure no KDE/sddm processes are still running by
killing anything that shouldn't be running and then go back to default
runlevel.  KDE is bad to leave processes running. 

If that does nothing, try revdep-rebuild and see if it catches
anything.  Maybe a emerge -uaDN world will help too. 

Lots of options.  When I did this a good while back, it got a bit dirty
before I got things cleaned out. 

Dale

:-)  :-) 

Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 4600 bytes --]

On Tue, 25 Jun 2019 00:12:56 +0100, Mick wrote:

> > > Can someone please explain how the removal of the 'wireless' USE
> > > flag from powerdevil ends up with no buttons for Suspend-to-RAM,
> > > Hibernation, Reboot or Shutdown under the Leave tab of the KMenu?
> > > What does wireless have to do with those functions which should work
> > > regardless?  
> > 
> > Those options are still present here.  
> 
> Thanks Neil, these are the packages which were depcleaned following
> USE="- wireless" for powerdevil, USE="-espeak" for speech-dispatcher
> and USE="device- mapper-only -thin" for lvm:

Has nobody ever told you about changing only one thing at a time? ;_)

> 1561390348: Started emerge on: Jun 24, 2019 16:32:28
> 1561390348:  *** emerge --ask --verbose --depclean
> 1561390348:  >>> depclean
> 1561390428: === Unmerging... (virtual/w3m-0)
> 1561390432:  >>> unmerge success: virtual/w3m-0
> 1561390432: === Unmerging... (virtual/linux-sources-3)
> 1561390436:  >>> unmerge success: virtual/linux-sources-3
> 1561390436: === Unmerging... (kde-frameworks/networkmanager-qt-5.57.0)
> 1561390440:  >>> unmerge success:
> kde-frameworks/networkmanager-qt-5.57.0 1561390440: === Unmerging...
> (sys-block/thin-provisioning-tools-0.7.0) 1561390445:  >>> unmerge
> success: sys-block/thin-provisioning-tools-0.7.0 1561390445: ===
> Unmerging... (app-accessibility/espeak-1.48.04-r1) 1561390449:  >>>
> unmerge success: app-accessibility/espeak-1.48.04-r1 1561390449: ===
> Unmerging... (www-client/w3m-0.5.3_p20180125) 1561390453:  >>> unmerge
> success: www-client/w3m-0.5.3_p20180125 1561390453: === Unmerging...
> (media-sound/sox-14.4.2-r1) 1561390458:  >>> unmerge success:
> media-sound/sox-14.4.2-r1 1561390458: === Unmerging...
> (net-misc/networkmanager-1.16.0) 1561390464:  >>> unmerge success:
> net-misc/networkmanager-1.16.0 1561390464: === Unmerging...
> (net-dialup/ppp-2.4.7-r7) 1561390468:  >>> unmerge success:
> net-dialup/ppp-2.4.7-r7 1561390468: === Unmerging...
> (net-misc/dhcp-4.4.1) 1561390473:  >>> unmerge success:
> net-misc/dhcp-4.4.1 1561390473: === Unmerging...
> (dev-libs/boehm-gc-7.6.4) 1561390478:  >>> unmerge success:
> dev-libs/boehm-gc-7.6.4 1561390478: === Unmerging...
> (media-sound/gsm-1.0.13-r1) 1561390482:  >>> unmerge success:
> media-sound/gsm-1.0.13-r1 1561390482: === Unmerging...
> (net-libs/libndp-1.7) 1561390486:  >>> unmerge success:
> net-libs/libndp-1.7 1561390486: === Unmerging...
> (net-misc/modemmanager-1.8.2-r1) 1561390493:  >>> unmerge success:
> net-misc/modemmanager-1.8.2-r1 1561390493: === Unmerging...
> (dev-libs/newt-0.52.20) 1561390497:  >>> unmerge success:
> dev-libs/newt-0.52.20 1561390497: === Unmerging...
> (net-dialup/ppp-scripts-0) 1561390501:  >>> unmerge success:
> net-dialup/ppp-scripts-0 1561390501: === Unmerging...
> (sys-libs/slang-2.3.2) 1561390505:  >>> unmerge success:
> sys-libs/slang-2.3.2 1561390505: === Unmerging...
> (net-libs/libqmi-1.20.2) 1561390510:  >>> unmerge success:
> net-libs/libqmi-1.20.2 1561390510: === Unmerging...
> (net-libs/libmbim-1.16.2) 1561390515:  >>> unmerge success:
> net-libs/libmbim-1.16.2 1561390515:  *** exiting successfully.
> 1561390515:  *** terminating.
> 1561390536: Started emerge on: Jun 24, 2019 16:35:36
> 1561390536:  *** emerge --ask --verbose @preserved-rebuild
> 1561390543:  *** exiting successfully.
> 1561390543:  *** terminating.

I don't have most of those packages either, I do have w3m and sox but
you'd have to be pretty desperate to start suspecting them.

[ebuild   R    ] kde-plasma/powerdevil-5.16.1:5::gentoo USE="-brightness-control -debug handbook -wireless" 0 KiB

It doesn't look like USE affects it either.

> I can't see anything in there.  I also uninstalled and reinstalled
> plasma- meta, but did not depclean anything.  Could there be something
> in systemsettings?  Yep! Power Management is greyed out:
> 
> "Power management configuration module could not be loaded. The Power 
> Management Service appears not to be running.  This can be solved by
> starting or scheduling it inside "Startup and Shutdown".
> 
> What am I supposed to add in "Startup and Shutdown"?  There is no Power 
> Management to start up and no button to add any services.  :-/
> 

I can't see anything power related in there. I have everything but
automounting enabled.

Have you tried logging in as a new user, to see if it's a configuration
option that's wrong somewhere?


-- 
Neil Bothwick

As long as you do not move you can still choose any direction.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[Mick]

[-- Attachment #1: Type: text/plain, Size: 5259 bytes --]

Thank you both for your suggestions,

On Tuesday, 25 June 2019 09:47:16 BST Neil Bothwick wrote:
> On Tue, 25 Jun 2019 00:12:56 +0100, Mick wrote:
> > > > Can someone please explain how the removal of the 'wireless' USE
> > > > flag from powerdevil ends up with no buttons for Suspend-to-RAM,
> > > > Hibernation, Reboot or Shutdown under the Leave tab of the KMenu?
> > > > What does wireless have to do with those functions which should work
> > > > regardless?
> > > 
> > > Those options are still present here.
> > 
> > Thanks Neil, these are the packages which were depcleaned following
> > USE="- wireless" for powerdevil, USE="-espeak" for speech-dispatcher
> 
> > and USE="device- mapper-only -thin" for lvm:
> Has nobody ever told you about changing only one thing at a time? ;_)
> 
> > 1561390348: Started emerge on: Jun 24, 2019 16:32:28
> > 1561390348:  *** emerge --ask --verbose --depclean
> > 1561390348:  >>> depclean
> > 1561390428: === Unmerging... (virtual/w3m-0)
> > 1561390432:  >>> unmerge success: virtual/w3m-0
> > 1561390432: === Unmerging... (virtual/linux-sources-3)
> > 1561390436:  >>> unmerge success: virtual/linux-sources-3
> > 1561390436: === Unmerging... (kde-frameworks/networkmanager-qt-5.57.0)
> > 1561390440:  >>> unmerge success:
> > kde-frameworks/networkmanager-qt-5.57.0 1561390440: === Unmerging...
> > (sys-block/thin-provisioning-tools-0.7.0) 1561390445:  >>> unmerge
> > success: sys-block/thin-provisioning-tools-0.7.0 1561390445: ===
> > Unmerging... (app-accessibility/espeak-1.48.04-r1) 1561390449:  >>>
> > unmerge success: app-accessibility/espeak-1.48.04-r1 1561390449: ===
> > Unmerging... (www-client/w3m-0.5.3_p20180125) 1561390453:  >>> unmerge
> > success: www-client/w3m-0.5.3_p20180125 1561390453: === Unmerging...
> > (media-sound/sox-14.4.2-r1) 1561390458:  >>> unmerge success:
> > media-sound/sox-14.4.2-r1 1561390458: === Unmerging...
> > (net-misc/networkmanager-1.16.0) 1561390464:  >>> unmerge success:
> > net-misc/networkmanager-1.16.0 1561390464: === Unmerging...
> > (net-dialup/ppp-2.4.7-r7) 1561390468:  >>> unmerge success:
> > net-dialup/ppp-2.4.7-r7 1561390468: === Unmerging...
> > (net-misc/dhcp-4.4.1) 1561390473:  >>> unmerge success:
> > net-misc/dhcp-4.4.1 1561390473: === Unmerging...
> > (dev-libs/boehm-gc-7.6.4) 1561390478:  >>> unmerge success:
> > dev-libs/boehm-gc-7.6.4 1561390478: === Unmerging...
> > (media-sound/gsm-1.0.13-r1) 1561390482:  >>> unmerge success:
> > media-sound/gsm-1.0.13-r1 1561390482: === Unmerging...
> > (net-libs/libndp-1.7) 1561390486:  >>> unmerge success:
> > net-libs/libndp-1.7 1561390486: === Unmerging...
> > (net-misc/modemmanager-1.8.2-r1) 1561390493:  >>> unmerge success:
> > net-misc/modemmanager-1.8.2-r1 1561390493: === Unmerging...
> > (dev-libs/newt-0.52.20) 1561390497:  >>> unmerge success:
> > dev-libs/newt-0.52.20 1561390497: === Unmerging...
> > (net-dialup/ppp-scripts-0) 1561390501:  >>> unmerge success:
> > net-dialup/ppp-scripts-0 1561390501: === Unmerging...
> > (sys-libs/slang-2.3.2) 1561390505:  >>> unmerge success:
> > sys-libs/slang-2.3.2 1561390505: === Unmerging...
> > (net-libs/libqmi-1.20.2) 1561390510:  >>> unmerge success:
> > net-libs/libqmi-1.20.2 1561390510: === Unmerging...
> > (net-libs/libmbim-1.16.2) 1561390515:  >>> unmerge success:
> > net-libs/libmbim-1.16.2 1561390515:  *** exiting successfully.
> > 1561390515:  *** terminating.
> > 1561390536: Started emerge on: Jun 24, 2019 16:35:36
> > 1561390536:  *** emerge --ask --verbose @preserved-rebuild
> > 1561390543:  *** exiting successfully.
> > 1561390543:  *** terminating.
> 
> I don't have most of those packages either, I do have w3m and sox but
> you'd have to be pretty desperate to start suspecting them.

I am!  O_O


> [ebuild   R    ] kde-plasma/powerdevil-5.16.1:5::gentoo
> USE="-brightness-control -debug handbook -wireless" 0 KiB
> 
> It doesn't look like USE affects it either.
> 
> > I can't see anything in there.  I also uninstalled and reinstalled
> > plasma- meta, but did not depclean anything.  Could there be something
> > in systemsettings?  Yep! Power Management is greyed out:
> > 
> > "Power management configuration module could not be loaded. The Power
> > Management Service appears not to be running.  This can be solved by
> > starting or scheduling it inside "Startup and Shutdown".
> > 
> > What am I supposed to add in "Startup and Shutdown"?  There is no Power
> > Management to start up and no button to add any services.  :-/
> 
> I can't see anything power related in there. I have everything but
> automounting enabled.
> 
> Have you tried logging in as a new user, to see if it's a configuration
> option that's wrong somewhere?

I've done one better, installed Enlightenment to try it out on this machine, 
in case it works without intermittently spinning up the CPU when the screen 
goes to sleep, but all the power settings were missing in Enlightenment too.

I run an update today which brought in a new dbus package.  Although 
@preserved-rebuild did not pick up anything, revdep-rebuild which Dale 
suggested and I had not run yet, wants to reinstall quite a few packages 
including ... libreoffice.  O_o

Anyway, I'll let it run its course, reboot and see what I get.

-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[Peter Humphrey]

On Monday, 24 June 2019 21:19:09 BST Mick wrote:
> Can someone please explain how the removal of the 'wireless' USE flag from
> powerdevil ends up with no buttons for Suspend-to-RAM, Hibernation, Reboot
> or Shutdown under the Leave tab of the KMenu?

It doesn't, by itself. I have -wireless set on powerdevil and I have Reboot 
and Shutdown buttons.

> What does wireless have to do with those functions which should work
> regardless?

Nothing, one hopes.

> Also, the sddm DM shutdown/reboot buttons now do not work. O_O
> 
> Is Plasma/KDE trying to emulate the inflexibility of Gnome? (no flamewar
> intended please).

It seems that you're a victim of the hopelessly reticulate interactions among 
plasma components. As I said a minute ago, finding myself similarly afflicted, 
I just had to cut the Gordian knot and start again. (Sorry - a bit of verbal 
diarrhoea there.)

-- 
Regards,
Peter.

Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]

[Mick]

[-- Attachment #1: Type: text/plain, Size: 483 bytes --]

On Tuesday, 25 June 2019 10:14:59 BST Peter Humphrey wrote:
> On Monday, 24 June 2019 21:19:09 BST Mick wrote:

> > Also, the sddm DM shutdown/reboot buttons now do not work. O_O

> It seems that you're a victim of the hopelessly reticulate interactions
> among plasma components.

Yes, it seems by removing plasma-meta and reinstalling I caused some plasma-
KDE hickup, which a revdep-rebuild following this morning's update is now 
hopefully trying to address. 

-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[»Q«]

On Mon, 24 Jun 2019 21:19:09 +0100
Mick <michaelkintzios@gmail.com> wrote:

> Can someone please explain how the removal of the 'wireless' USE flag
> from powerdevil ends up with no buttons for Suspend-to-RAM,
> Hibernation, Reboot or Shutdown under the Leave tab of the KMenu?
> What does wireless have to do with those functions which should work
> regardless?

I have the wireless flag on, and I'm sometimes missing those buttons.
I've never figured out why, but they usually return after I log out of
KDE and back in -- sometimes it takes a reboot.

> Also, the sddm DM shutdown/reboot buttons now do not work. O_O

Those have never worked for me.

Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]

On Tuesday, 25 June 2019 17:09:55 BST »Q« wrote:
> On Mon, 24 Jun 2019 21:19:09 +0100
> 
> Mick <michaelkintzios@gmail.com> wrote:
> > Can someone please explain how the removal of the 'wireless' USE flag
> > from powerdevil ends up with no buttons for Suspend-to-RAM,
> > Hibernation, Reboot or Shutdown under the Leave tab of the KMenu?
> > What does wireless have to do with those functions which should work
> > regardless?
> 
> I have the wireless flag on, and I'm sometimes missing those buttons.
> I've never figured out why, but they usually return after I log out of
> KDE and back in -- sometimes it takes a reboot.

I've come across the same symptoms on various installations of mine.  However, 
I thought in all cases this was because I was in the middle of an update.  
Anyway, after a prolonged revdep-rebuild, which reinstalled dbus plus another 
21 packages, it seems all buttons are back and I can shutdown and hibernate.  
I have no idea why a revdep-rebuild wanted to rebuild all these packages ... 
but clearly something I did (like uninstalling/reinstalling plasma-meta, or 
changing package specific USE flags?) meant all these needed to be rebuilt.  I 
didn't expect this - thank you Dale for nudging me in the right direction and 
thank you all for your suggestions.  :-)

Next time I login I'll also check if the missing Power Management module 
mentioned in systemsettings has resolved itself.


> > Also, the sddm DM shutdown/reboot buttons now do not work. O_O
> 
> Those have never worked for me.

I just looked at another installation.  The default sddm configuration file (/
usr/share/sddm/sddm.conf.d/00default.conf) shows this:

[General]
# Halt command
HaltCommand=/usr/bin/loginctl poweroff

In an OpenRC system there is no loginctl.  Consequently, unless we define a 
separate config in /etc/ to use shutdown (with sudo?) it won't work.  This 
systemd-ism may be worth a bug report.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]

On Wed, 26 Jun 2019 11:20:20 +0100, Mick wrote:

> I just looked at another installation.  The default sddm configuration
> file (/ usr/share/sddm/sddm.conf.d/00default.conf) shows this:
> 
> [General]
> # Halt command
> HaltCommand=/usr/bin/loginctl poweroff
> 
> In an OpenRC system there is no loginctl.  Consequently, unless we
> define a separate config in /etc/ to use shutdown (with sudo?) it won't
> work.  This systemd-ism may be worth a bug report.

It won't work on systemd either, loginctl has no poweroff command, it
should be systemctl poweroff, which is symlinked to /sbin/poweroff here
so setting it to that should work for modern and ancient systems alike :P


-- 
Neil Bothwick

Nothing is foolproof to a sufficiently talented fool.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[gentoo-user] Re: [Was: What the devil?!!] sddm shutdown & reboot

[Mick]

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

On Wednesday, 26 June 2019 11:34:47 BST Neil Bothwick wrote:
> On Wed, 26 Jun 2019 11:20:20 +0100, Mick wrote:
> > I just looked at another installation.  The default sddm configuration
> > file (/ usr/share/sddm/sddm.conf.d/00default.conf) shows this:
> > 
> > [General]
> > # Halt command
> > HaltCommand=/usr/bin/loginctl poweroff
> > 
> > In an OpenRC system there is no loginctl.  Consequently, unless we
> > define a separate config in /etc/ to use shutdown (with sudo?) it won't
> > work.  This systemd-ism may be worth a bug report.
> 
> It won't work on systemd either, loginctl has no poweroff command, it
> should be systemctl poweroff, which is symlinked to /sbin/poweroff here
> so setting it to that should work for modern and ancient systems alike :P

Could it be loginctl is there to confirm if a local button operation can run /
sbin/poweroff, rather than actually running the command as shown in the sddm 
config file?
-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Re: [Was: What the devil?!!] sddm shutdown & reboot

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

On Wed, 26 Jun 2019 15:15:37 +0100, Mick wrote:

> > > [General]
> > > # Halt command
> > > HaltCommand=/usr/bin/loginctl poweroff
> > > 
> > > In an OpenRC system there is no loginctl.  Consequently, unless we
> > > define a separate config in /etc/ to use shutdown (with sudo?) it
> > > won't work.  This systemd-ism may be worth a bug report.  
> > 
> > It won't work on systemd either, loginctl has no poweroff command, it
> > should be systemctl poweroff, which is symlinked to /sbin/poweroff
> > here so setting it to that should work for modern and ancient systems
> > alike :P  
> 
> Could it be loginctl is there to confirm if a local button operation
> can run / sbin/poweroff, rather than actually running the command as
> shown in the sddm config file?

No, not when I tried it

% loginctl poweroff
Unknown operation poweroff.

This is confirmed by the list of commands in the loginctl man page.


-- 
Neil Bothwick

C Error #029: Well! I'm impressed

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Re: [Was: What the devil?!!] sddm shutdown & reboot

[Arve Barsnes]

On Wed, 26 Jun 2019 at 17:13, Neil Bothwick <neil@digimed.co.uk> wrote:
> > Could it be loginctl is there to confirm if a local button operation
> > can run / sbin/poweroff, rather than actually running the command as
> > shown in the sddm config file?
>
> No, not when I tried it
>
> % loginctl poweroff
> Unknown operation poweroff.
>
> This is confirmed by the list of commands in the loginctl man page.

On the other hand, poweroff and reboot are valid arguments to
/bin/loginctl, installed by elogind

Regards,
Arve

Re: [gentoo-user] Re: [Was: What the devil?!!] sddm shutdown & reboot

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1762 bytes --]

On Wednesday, 26 June 2019 16:49:11 BST Arve Barsnes wrote:
> On Wed, 26 Jun 2019 at 17:13, Neil Bothwick <neil@digimed.co.uk> wrote:
> > > Could it be loginctl is there to confirm if a local button operation
> > > can run / sbin/poweroff, rather than actually running the command as
> > > shown in the sddm config file?
> > 
> > No, not when I tried it
> > 
> > % loginctl poweroff
> > Unknown operation poweroff.
> > 
> > This is confirmed by the list of commands in the loginctl man page.
> 
> On the other hand, poweroff and reboot are valid arguments to
> /bin/loginctl, installed by elogind
> 
> Regards,
> Arve

OK, I got this partly wrong.

1. There is a /bin/loginctl installed by elogind in openrc, but there is no /
usr/bin/loginctl, which is what the sddm default settings file mentions.

2. Running '/bin/loginctl poweroff' from a console, while logged in as a user 
works fine.

3. Despite the above, some installations of mine do not react to sddm button 
presses to shutdown/reboot, but an older installation does.  On some 
installations which I suspect are running some (older) default sddm theme 
there are no shutdown/reboot buttons shown at all.  :-/

4. The installation which has buttons showing and reacts to it is an old 
installation, which has been hacked to death.  At some point in its life it 
had an /etc/sddm/ config file, modified to do stuff which the default settings 
would not do.  This file is no longer there, so sddm should be reading the 
default settings under /usr/share/sddm/ but I don't know if some settings were 
cached by sddm and this is why this PC works as it should, but others don't.

All this has left me confused and I'm thinking startx in a terminal is not 
such a bad idea after all ...

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Re: [Was: What the devil?!!] sddm shutdown & reboot

[Peter Humphrey]

On Wednesday, 26 June 2019 20:18:55 BST Mick wrote:

> All this has left me confused and I'm thinking startx in a terminal is not
> such a bad idea after all ...

Have you tried the value I gave you? It works fine here.

HaltCommand=/sbin/shutdown -h -P now

-- 
Regards,
Peter.

Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[Peter Humphrey]

On Wednesday, 26 June 2019 11:20:20 BST Mick wrote:

> I just looked at another installation.  The default sddm configuration file
> (/ usr/share/sddm/sddm.conf.d/00default.conf) shows this:
> 
> [General]
> # Halt command
> HaltCommand=/usr/bin/loginctl poweroff
> 
> In an OpenRC system there is no loginctl.  Consequently, unless we define a
> separate config in /etc/ to use shutdown (with sudo?) it won't work.  This
> systemd-ism may be worth a bug report.

Here, it shows 'HaltCommand=/sbin/shutdown -h -P now'.

-- 
Regards,
Peter.

Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]

On Wednesday, 26 June 2019 15:22:45 BST Peter Humphrey wrote:
> On Wednesday, 26 June 2019 11:20:20 BST Mick wrote:
> > I just looked at another installation.  The default sddm configuration
> > file (/usr/share/sddm/sddm.conf.d/00default.conf) shows this:
> > 
> > [General]
> > # Halt command
> > HaltCommand=/usr/bin/loginctl poweroff
> > 
> > In an OpenRC system there is no loginctl.  Consequently, unless we define
> > a
> > separate config in /etc/ to use shutdown (with sudo?) it won't work.  This
> > systemd-ism may be worth a bug report.
> 
> Here, it shows 'HaltCommand=/sbin/shutdown -h -P now'.

Where 'here' is ... where?  :-)

Your own /etc/sddm/ configuration file, or the default installed under /usr/
share/sddm/sddm.conf.d/ ?

The sddm package no longer installs a config file in etc.  The user may do so 
if desired/required and modify it accordingly.  However, the sample file 
offered by sddm has the above mentioned incongruity in it, which means the 
shutdown and reboot commands issued by its interface invariably do not work in 
openrc and it seems the same applies to systemd.

I'll check a couple more of my installations here to see if they differ. 
-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[Daniel Frey]

On 6/26/19 8:16 AM, Mick wrote:
> On Wednesday, 26 June 2019 15:22:45 BST Peter Humphrey wrote:
>> On Wednesday, 26 June 2019 11:20:20 BST Mick wrote:
>>> I just looked at another installation.  The default sddm configuration
>>> file (/usr/share/sddm/sddm.conf.d/00default.conf) shows this:
>>>
>>> [General]
>>> # Halt command
>>> HaltCommand=/usr/bin/loginctl poweroff
>>>
>>> In an OpenRC system there is no loginctl.  Consequently, unless we define
>>> a
>>> separate config in /etc/ to use shutdown (with sudo?) it won't work.  This
>>> systemd-ism may be worth a bug report.
>>
>> Here, it shows 'HaltCommand=/sbin/shutdown -h -P now'.
> 
> Where 'here' is ... where?  :-)
> 
> Your own /etc/sddm/ configuration file, or the default installed under /usr/
> share/sddm/sddm.conf.d/ ?
> 
> The sddm package no longer installs a config file in etc.  The user may do so
> if desired/required and modify it accordingly.  However, the sample file
> offered by sddm has the above mentioned incongruity in it, which means the
> shutdown and reboot commands issued by its interface invariably do not work in
> openrc and it seems the same applies to systemd.
> 
> I'll check a couple more of my installations here to see if they differ.
> 

I don't have any /etc/sddm.conf - it's all default config and mine is 
working with no tweaking (OpenRC). Same as mentioned above in the 
default config file: HaltCommand=/sbin/shutdown -h -P now

Dan

Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[Peter Humphrey]

On Wednesday, 26 June 2019 16:16:36 BST Mick wrote:
> On Wednesday, 26 June 2019 15:22:45 BST Peter Humphrey wrote:
> > On Wednesday, 26 June 2019 11:20:20 BST Mick wrote:
> > > I just looked at another installation.  The default sddm configuration
> > > file (/usr/share/sddm/sddm.conf.d/00default.conf) shows this:
> > > 
> > > [General]
> > > # Halt command
> > > HaltCommand=/usr/bin/loginctl poweroff
> > > 
> > > In an OpenRC system there is no loginctl.  Consequently, unless we
> > > define
> > > a
> > > separate config in /etc/ to use shutdown (with sudo?) it won't work. 
> > > This
> > > systemd-ism may be worth a bug report.
> > 
> > Here, it shows 'HaltCommand=/sbin/shutdown -h -P now'.
> 
> Where 'here' is ... where?  :-)

# grep Halt /usr/share/sddm/sddm.conf.d/00default.conf
# Halt command
HaltCommand=/sbin/shutdown -h -P now

(I hadn't seen this message when I replied just now.)

-- 
Gentoo testing system
gcc 9.1.0, sys-kernel/gentoo-sources 5.1.15
QT 5.12.3, KDE frameworks 5.59.0, KDE plasma 5.16.2
KDE apps 19.04.2 incl KMail 19.04.2-r1 (5.11.2), akonadi 19.04.0
dev-db/mariadb-10.3.16
x11-drivers/xf86-video-amdgpu 19.0.0
dev-libs/amdgpu-pro-opencl 18.20.684755

[gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[»Q«]

On Wed, 26 Jun 2019 11:20:20 +0100
Mick <michaelkintzios@gmail.com> wrote:

> On Tuesday, 25 June 2019 17:09:55 BST »Q« wrote:
> > On Mon, 24 Jun 2019 21:19:09 +0100
> > 
> > Mick <michaelkintzios@gmail.com> wrote:  

> > > Also, the sddm DM shutdown/reboot buttons now do not work. O_O  
> > 
> > Those have never worked for me.  
> 
> I just looked at another installation.  The default sddm
> configuration file (/ usr/share/sddm/sddm.conf.d/00default.conf)
> shows this:
> 
> [General]
> # Halt command
> HaltCommand=/usr/bin/loginctl poweroff
> 
> In an OpenRC system there is no loginctl.  Consequently, unless we
> define a separate config in /etc/ to use shutdown (with sudo?) it
> won't work.  This systemd-ism may be worth a bug report.

In /usr/share/sddm/sddm.conf.d/00default.conf I have 

  HaltCommand=/sbin/shutdown -h -P now

  RebootCommand=/sbin/shutdown -r now

I just checked it with sddm-0.18.0, then upgraded to 0.18.1-r1, and it
stayed the same, I guess because I have USE="-systemd".  

Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

On Wed, 26 Jun 2019 18:00:22 -0500, »Q« wrote:

> > In an OpenRC system there is no loginctl.  Consequently, unless we
> > define a separate config in /etc/ to use shutdown (with sudo?) it
> > won't work.  This systemd-ism may be worth a bug report.  
> 
> In /usr/share/sddm/sddm.conf.d/00default.conf I have 
> 
>   HaltCommand=/sbin/shutdown -h -P now
> 
>   RebootCommand=/sbin/shutdown -r now
> 
> I just checked it with sddm-0.18.0, then upgraded to 0.18.1-r1, and it
> stayed the same, I guess because I have USE="-systemd".  

And on a systemd setup, I have

	HaltCommand=/usr/bin/systemctl poweroff

so where did Mick's loginctl option come from?


-- 
Neil Bothwick

By the time you can make ends meet, they move the ends.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[Mike Gilbert]

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

On Wed, Jun 26, 2019, 7:30 PM Neil Bothwick <neil@digimed.co.uk> wrote:

> On Wed, 26 Jun 2019 18:00:22 -0500, »Q« wrote:
>
> > > In an OpenRC system there is no loginctl.  Consequently, unless we
> > > define a separate config in /etc/ to use shutdown (with sudo?) it
> > > won't work.  This systemd-ism may be worth a bug report.
> >
> > In /usr/share/sddm/sddm.conf.d/00default.conf I have
> >
> >   HaltCommand=/sbin/shutdown -h -P now
> >
> >   RebootCommand=/sbin/shutdown -r now
> >
> > I just checked it with sddm-0.18.0, then upgraded to 0.18.1-r1, and it
> > stayed the same, I guess because I have USE="-systemd".
>
> And on a systemd setup, I have
>
>         HaltCommand=/usr/bin/systemctl poweroff
>
> so where did Mick's loginctl option come from?
>

elogind

>

[-- Attachment #2: Type: text/html, Size: 1405 bytes --]

Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[Mick]

[-- Attachment #1: Type: text/plain, Size: 3270 bytes --]

On Thursday, 27 June 2019 02:18:05 BST Mike Gilbert wrote:
> On Wed, Jun 26, 2019, 7:30 PM Neil Bothwick <neil@digimed.co.uk> wrote:
> > On Wed, 26 Jun 2019 18:00:22 -0500, »Q« wrote:
> > > > In an OpenRC system there is no loginctl.  Consequently, unless we
> > > > define a separate config in /etc/ to use shutdown (with sudo?) it
> > > > won't work.  This systemd-ism may be worth a bug report.
> > > 
> > > In /usr/share/sddm/sddm.conf.d/00default.conf I have
> > > 
> > >   HaltCommand=/sbin/shutdown -h -P now
> > >   
> > >   RebootCommand=/sbin/shutdown -r now
> > > 
> > > I just checked it with sddm-0.18.0, then upgraded to 0.18.1-r1, and it
> > > stayed the same, I guess because I have USE="-systemd".
> > 
> > And on a systemd setup, I have
> > 
> >         HaltCommand=/usr/bin/systemctl poweroff
> > 
> > so where did Mick's loginctl option come from?
> 
> elogind

Yes!  It seems elogind affects the commands in file /usr/share/sddm/
sddm.conf.d/00default.conf to use a different HaltCommand and RebootCommand:

$ egrep -i 'Halt|Reboot' /usr/share/sddm/sddm.conf.d/00default.conf 
# Halt command
HaltCommand=/usr/bin/loginctl poweroff
# Reboot command
RebootCommand=/usr/bin/loginctl reboot

Here's a kicker:  I do not have '/usr/bin/loginctl' in this (openrc + elogind, 
but -consolekit, -systemd) system:

$ which loginctl
/bin/loginctl

$ ls -la /usr/bin/loginctl
ls: cannot access '/usr/bin/loginctl': No such file or directory

$ /usr/bin/loginctl poweroff
-bash: /usr/bin/loginctl: No such file or directory

NOTE: Running '/bin/loginctl poweroff' from a console works.


So perhaps this explains why I also do not have Shutdown/Reboot buttons 
showing up on the default theme at the top RH corner?  Errm ... not so!  
Please walk through this test case with me:

1. I log out, or reboot.  The sddm DM screen shows no Shutdown/Reboot buttons.  
Consequently, I have no means of shutting down or rebooting from the DM 
screen.

2. I log out, drop into a console, stop the xdm rc service and restart it.  
The sddm screen launches and it now presents Shutdown/Reboot buttons as it 
should!

Question: if /usr/bin/loginctl is not present, what commands do the buttons 
operate/which config file they read, to shutdown/reboot?

NOTE: If I login/out, or reboot, the buttons are gone again.  :-/

3. I use KDE's systemsettings 'Startup and Shutdown/Login Screen (SDDM)' to 
change the default theme.  This creates a new /etc/sddm.conf file, with the 
new Theme entry I selected,  but the Halt/Reboot commands are empty.  I logout 
or reboot and the buttons are absent again, or when shown in the new theme 
they are either greyed out and do not work (Breeze) or not greyed out and 
still not work.

I have not tried setting up a config file in /etc/ and modifying it 
comprehensively, i.e. specifying my own theme, Halt/Reboot commands, etc., but 
I do not have a coherent theory why the above behaviour is observed.

The next thing to try:

I don't have elogind starting up as a boot level rc service, because it is 
launched when needed by dbus or pam.  Perhaps if elogind is running as a 
background service sddm will (re)launch differently?

-- 

Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[Mick]

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]

On Thursday, 27 June 2019 10:55:16 BST Mick wrote:

> The next thing to try:
> 
> I don't have elogind starting up as a boot level rc service, because it is
> launched when needed by dbus or pam.  Perhaps if elogind is running as a
> background service sddm will (re)launch differently?

I just tried it and it works.  :-)

With elogind running as a boot service, sddm launches with the Shutdown/Reboot 
buttons shown and they work as expected.  However, as I do not have a /usr/
bin/loginctl, all I can assume is irrespective of the HaltCommand path 
specified in the default sddm config, when launched sddm searches all paths 
and eventually finds /bin/loginctl, which it runs when a button is pressed.

As we've established with no -elogind +consolekit the commands specified in 
the default sddm config file are different.  Also, with consolekit being a 
default rc service, it is running at the time sddm is launched.

Thank you all for your responses.
-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[»Q«]

On Thu, 27 Jun 2019 12:42:56 +0100
Mick <michaelkintzios@gmail.com> wrote:

> On Thursday, 27 June 2019 10:55:16 BST Mick wrote:
> 
> > The next thing to try:
> > 
> > I don't have elogind starting up as a boot level rc service,
> > because it is launched when needed by dbus or pam.  Perhaps if
> > elogind is running as a background service sddm will (re)launch
> > differently?  
> 
> I just tried it and it works.  :-)
> 
> With elogind running as a boot service, sddm launches with the
> Shutdown/Reboot buttons shown and they work as expected.  However, as
> I do not have a /usr/ bin/loginctl, all I can assume is irrespective
> of the HaltCommand path specified in the default sddm config, when
> launched sddm searches all paths and eventually finds /bin/loginctl,
> which it runs when a button is pressed.
> 
> As we've established with no -elogind +consolekit the commands
> specified in the default sddm config file are different.  Also, with
> consolekit being a default rc service, it is running at the time sddm
> is launched.

I use openrc, so I have sddm installed with -elogind -systemd
+consolekit +pam.  Putting consolekit in the default runlevel does make
the buttons work the first time sddm is launched, on reboot.

Without the conosolekit service in the default runlevel, the buttons
are greyed out after reboot, but restarting xdm some time after booting,
still without consolekit running, makes the buttons come alive and
work.  So there's something in play other than consolekit for me.

(I don't actually need to sort this out -- I'm just curious.)

Re: [gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2711 bytes --]

On Friday, 28 June 2019 16:06:50 BST »Q« wrote:
> On Thu, 27 Jun 2019 12:42:56 +0100
> 
> Mick <michaelkintzios@gmail.com> wrote:
> > On Thursday, 27 June 2019 10:55:16 BST Mick wrote:
> > > The next thing to try:
> > > 
> > > I don't have elogind starting up as a boot level rc service,
> > > because it is launched when needed by dbus or pam.  Perhaps if
> > > elogind is running as a background service sddm will (re)launch
> > > differently?
> > 
> > I just tried it and it works.  :-)
> > 
> > With elogind running as a boot service, sddm launches with the
> > Shutdown/Reboot buttons shown and they work as expected.  However, as
> > I do not have a /usr/ bin/loginctl, all I can assume is irrespective
> > of the HaltCommand path specified in the default sddm config, when
> > launched sddm searches all paths and eventually finds /bin/loginctl,
> > which it runs when a button is pressed.
> > 
> > As we've established with no -elogind +consolekit the commands
> > specified in the default sddm config file are different.  Also, with
> > consolekit being a default rc service, it is running at the time sddm
> > is launched.
> 
> I use openrc, so I have sddm installed with -elogind -systemd
> +consolekit +pam.  Putting consolekit in the default runlevel does make
> the buttons work the first time sddm is launched, on reboot.
> 
> Without the conosolekit service in the default runlevel, the buttons
> are greyed out after reboot, but restarting xdm some time after booting,
> still without consolekit running, makes the buttons come alive and
> work.  

At this stage, when you are restarting xdm, you've logged in the console and 
(I'm guessing) dbus+polkit+pam are running even if consolekit is not.  
Consolekit is needed for multiple users, so it is not necessary for this 
purpose, although if it's already running I understand it helps with the 
authentication by calling on pam.  So, I'm surmising, dbus calls in polkit & 
pam, since you're logged in, which allows access to /sbin/shutdown.

 # ldd /usr/bin/sddm | grep dbus
	libdbus-1.so.3 => /usr/lib64/libdbus-1.so.3 (0x00007f5374160000)


> So there's something in play other than consolekit for me.
> 
> (I don't actually need to sort this out -- I'm just curious.)

It may have something to do with dbus/polkit, which authenticates access to 
the /sbin/shutdown file locally by sddm and this makes the buttons visible/
actionable.  If you have not logged in yet, after a reboot, then only dbus is 
running at that stage with no authentication mechanism.  I may be *wildly* 
wrong, but no doubt more knowledgeable members will drop by soon to correct 
me.

-- 
Regards,

Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[gentoo-user] Re: What the devil?!! [or Plasma teething problems Ia.]

[»Q«]

On Fri, 28 Jun 2019 17:13:49 +0100
Mick <michaelkintzios@gmail.com> wrote:

> So, I'm surmising, dbus calls in polkit & pam, since you're logged
> in, which allows access to /sbin/shutdown.

Thanks for the explanation. :)