Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Missing shutdown/reboot buttons in KDE.
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
VoxUnius
n00b
n00b


Joined: 31 Jul 2018
Posts: 8

PostPosted: Tue Jul 31, 2018 4:33 am    Post subject: Missing shutdown/reboot buttons in KDE. Reply with quote

Hi guys,

This is my first post here :)

I have searched through the forum and found some posts with similar problem, but the setup was different.

The problems is described in the subject. I am using systemd with sddm. I found from the forum that emerging consolekit would enable the buttons, and indeed it has. However, after rebooting the machine, sddm did not start. It looks like consolekit and systemd are not working well together.

Installing lightdm instead of sddm did not help either.

I suspect getting rid of systemd would resolve the issue, but, could it be done without such a surgery?

Cheers.
Back to top
View user's profile Send private message
Perfect Gentleman
l33t
l33t


Joined: 18 May 2014
Posts: 747

PostPosted: Tue Jul 31, 2018 6:14 am    Post subject: Reply with quote

consolekit or elogind?
check
Code:
rc-status -a
if dbus consolekit/elogind are running
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 19913
Location: here

PostPosted: Tue Jul 31, 2018 6:44 am    Post subject: Reply with quote

Perfect Gentleman wrote:
consolekit or elogind?

I think systemd
VoxUnius wrote:
I suspect getting rid of systemd would resolve the issue, but, could it be done without such a surgery



@VoxUnius: welcome to gentoo forum.
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
VoxUnius
n00b
n00b


Joined: 31 Jul 2018
Posts: 8

PostPosted: Tue Jul 31, 2018 2:18 pm    Post subject: Reply with quote

Yes, it is systemd. If it was OpenRC, I would have installed consolekit and got rid of the problem.

fedeliallalinea wrote:
@VoxUnius: welcome to gentoo forum.

Cheers :)
Back to top
View user's profile Send private message
bunder
Bodhisattva
Bodhisattva


Joined: 10 Apr 2004
Posts: 5722

PostPosted: Tue Jul 31, 2018 9:42 pm    Post subject: Reply with quote

Is dbus also running? I don't remember if dbus has any involvement in these buttons appearing, or if its just consolekit.
_________________
overlay | patches
Neddyseagoon wrote:
The problem with leaving is that you can only do it once and it reduces your influence.
Back to top
View user's profile Send private message
VoxUnius
n00b
n00b


Joined: 31 Jul 2018
Posts: 8

PostPosted: Tue Jul 31, 2018 9:48 pm    Post subject: Reply with quote

Yes, dbus is running.

Code:
gentoo ~ # systemctl status dbus
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: disabled)
   Active: active (running) since Wed 2018-08-01 07:42:26 AEST; 3min 17s ago
     Docs: man:dbus-daemon(1)
 Main PID: 362 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           └─362 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

Aug 01 07:42:30 gentoo dbus[362]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Aug 01 07:42:30 gentoo dbus[362]: [system] Activating service name='org.kde.powerdevil.discretegpuhelper' (using servicehelper)
Aug 01 07:42:30 gentoo dbus[362]: [system] Successfully activated service 'org.kde.powerdevil.discretegpuhelper'
Aug 01 07:42:30 gentoo dbus[362]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
Aug 01 07:42:30 gentoo backlighthelper[682]: powerdevil: no kernel backlight interface found
Aug 01 07:42:30 gentoo dbus[362]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Aug 01 07:42:39 gentoo dbus[362]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Aug 01 07:42:39 gentoo dbus[362]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug 01 07:42:54 gentoo dbus[362]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Aug 01 07:42:54 gentoo dbus[362]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Back to top
View user's profile Send private message
big
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2007
Posts: 84

PostPosted: Sat Aug 11, 2018 1:59 am    Post subject: Reply with quote

Check kde-plasma/powerdevil and sys-power/upower
_________________
be big,no bug
Back to top
View user's profile Send private message
VoxUnius
n00b
n00b


Joined: 31 Jul 2018
Posts: 8

PostPosted: Sat Aug 11, 2018 2:04 am    Post subject: Reply with quote

Both installed:
Code:
*  sys-power/upower
      Latest version available: 0.99.5
      Latest version installed: 0.99.5

*  kde-plasma/powerdevil
      Latest version available: 5.12.5
      Latest version installed: 5.12.5
Back to top
View user's profile Send private message
PrSo
Tux's lil' helper
Tux's lil' helper


Joined: 01 Jun 2017
Posts: 123

PostPosted: Sat Aug 11, 2018 6:08 am    Post subject: Reply with quote

IMHO if you are using systemd consolekit appear to be redundant.
Quote:

Enable the systemd USE flag globally (in make.conf). The consolekit USE flag should also be disabled to prevent conflicts with the systemd-logind service.

Please see the wiki.

The polkit could be the culprit also.

If sddm does not start, please give us the output of "/var/log/sddm.log", or if it starts, the "~/.local/share/sddm/xorg-session.log" output.
BTW you could do this by app-text/wgetpaste because xorg-session.log could be huge.

You could also check if something is wrong with your config setup by creating a new user (just to test it out) and check if everything works properly with the new user session.
Back to top
View user's profile Send private message
big
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jan 2007
Posts: 84

PostPosted: Sat Aug 11, 2018 12:18 pm    Post subject: Reply with quote

You cannot make ConsoleKit and systemd-logind work simultaneously, because they conflict with each other.
If you are planning to replace systemd with OpenRC, you can switch to consolekit or elogind instead.

Make sure that powerdevil and upower are installed. Also check that the user is in the users group.
If you stick to Systemd, make sure sddm.service run after systemd-logind.service.
Check this issue
_________________
be big,no bug
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6579
Location: Austria

PostPosted: Sat Aug 11, 2018 1:15 pm    Post subject: Reply with quote

big wrote:
If you stick to Systemd, make sure sddm.service run after systemd-logind.service.
Check this issue

That issue is fixed in Gentoo in any sddm version >=0.17.0-r4.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
VoxUnius
n00b
n00b


Joined: 31 Jul 2018
Posts: 8

PostPosted: Sun Aug 12, 2018 11:53 am    Post subject: Reply with quote

Thanks, guys. Ok, answering questions one by one:

1. I removed consolekit once sddm ceased to start up properly.
2. systemd use flag has been set globally. Also the system was build using a systemd profile.
3. I did follow the systemd wiki instructions when I installed the system.
4. SDDM only starts when consolekit is not installed. However, installing consolekit enables the buttons, but it only works until the first reboot.
5. Creating new user did not resolve the problem. Buttons were still missing.
6. xorg-session.log has nothing suspicious in it.
Code:
startkde: Starting up...
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/disable_kmix.upd' for new updates
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/fonts_akregator.upd' for new updates
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/fonts_global.upd' for new updates
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/fonts_global_toolbar.upd' for new updates
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/fonts_kate.upd' for new updates
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/gtkbreeze5.5.upd' for new updates
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/kcalcrc.upd' for new updates
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/kde4breeze.upd' for new updates
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/krdb_libpathwipe.upd' for new updates
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/krunnerplugins.upd' for new updates
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/kscreenlocker.upd' for new updates
2018-08-12T21:43:49 Checking update-file '/usr/share/kconf_update/okular.upd' for new updates
OpenGL vendor string:                   NVIDIA Corporation
OpenGL renderer string:                 GeForce GTX 1080/PCIe/SSE2
OpenGL version string:                  4.6.0 NVIDIA 390.77
OpenGL shading language version string: 4.60 NVIDIA
Driver:                                 NVIDIA
Driver version:                         390.77
GPU class:                              Unknown
OpenGL version:                         4.6
GLSL version:                           4.60
X server version:                       1.19.5
Linux kernel version:                   4.9.113
Requires strict binding:                no
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
startkde: Shutting down...
startkde: Done.
kdeinit5: Communication error with launcher. Exiting!

7. As mentioned above, both powerdevil and upower are installed.
8. sddm does run after systemd-logind service.

What was that suspicion about poolkit?
Back to top
View user's profile Send private message
PrSo
Tux's lil' helper
Tux's lil' helper


Joined: 01 Jun 2017
Posts: 123

PostPosted: Sun Aug 12, 2018 6:59 pm    Post subject: Reply with quote

Polkit gives permission for the user ie. to reboot or to shutdown the system as it controls all system-wide privileges. If rules are messed up you could see similar behavior like yours, but creating new user and testing things up has eliminated that option (I suppose).

Like big wrote, ConsoleKit and systemd-logind conflict with each other.

Is your system up to date, mean, when did you did "emerge --sync" and "emerge -avuDN --with-bdeps y --changed-deps --keep-going @world" (for example) last time? If never please do this.

From the fragment of pasted log:

Quote:
X server version: 1.19.5
Linux kernel version: 4.9.113


Are you using mixed stable/testing packages in your setup ( in make.conf ACCEPT_KEYWORDS is "~amd64" or "amd64")?
Please see the wiki.

Kde is starting up and after that immediately shutting down?

Quote:
startkde: Shutting down...
startkde: Done.
kdeinit5: Communication error with launcher. Exiting!

or you are doing this manually?
Back to top
View user's profile Send private message
VoxUnius
n00b
n00b


Joined: 31 Jul 2018
Posts: 8

PostPosted: Mon Aug 13, 2018 2:42 am    Post subject: Reply with quote

The system is up to date, yes. I updated it yesterday in fact.

I did not put ~amd64 into make.conf. I only put it against ~6 packages in package.accept_keywords (like wine, skype etc.,nothing relevant really). I had a problem with nvidia drivers and gentoo kernel, so I had to find a working driver/kernel combination. Kernel v4.9 was the one that had no problem. Given that Nvidia has released newer drivers recently, I should probably try a newer kernel. Anyway, this should not be related.

KDE does not shut down immediately. That log was produced for the new user I was asked to test. I just started up KDE, confirmed the buttons were still missing, and shut it down. This is why it is so short.
Back to top
View user's profile Send private message
PrSo
Tux's lil' helper
Tux's lil' helper


Joined: 01 Jun 2017
Posts: 123

PostPosted: Mon Aug 13, 2018 7:14 am    Post subject: Reply with quote

Thanks for clarifying that.

I'm not a systemd guy (using elogind), but should dbus be emerged with USE="systemd user-session" flags? (I don't know flags of yours, although could be wrong, tough).
Back to top
View user's profile Send private message
VoxUnius
n00b
n00b


Joined: 31 Jul 2018
Posts: 8

PostPosted: Mon Aug 13, 2018 7:20 am    Post subject: Reply with quote

Looks like no one likes systemd here :)

Anyway, dbus was emerged with user-session flag. Ans systemd flag was set globally.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6579
Location: Austria

PostPosted: Mon Aug 13, 2018 1:36 pm    Post subject: Reply with quote

Make sure you have either polkit-0.113-r4 or polkit-0.115-r1 installed (none in between).
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
VoxUnius
n00b
n00b


Joined: 31 Jul 2018
Posts: 8

PostPosted: Mon Aug 13, 2018 1:41 pm    Post subject: Reply with quote

Code:
*  sys-auth/polkit
      Latest version available: 0.113-r4
      Latest version installed: 0.113-r4
Back to top
View user's profile Send private message
DanAlucard
n00b
n00b


Joined: 16 Oct 2018
Posts: 1

PostPosted: Tue Oct 16, 2018 5:41 pm    Post subject: Reply with quote

I'm facing this same issue.
Fresh installation; systemd

Tried everything described here to no avail.
I'm forced everytime to close session and then shutdown while on SDDM, or starting a terminal while on KDE and running [systemctl shutdown] as root.
PITA :cry:
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum