KDE problems - no device management and battery monitor

winek · 2014-02-13 15:35:49

I upgraded my system about a week ago. After I rebooted, I noticed several issues with the desktop environment:

- User list in KDM is blank
- No battery is detected (the notification popup saying something like "No power management engines" also appeared while logging in)
- Pluggable devices are not detected (also, there is no "devices" category in Dolphin under "Places")
- NetworkManager applet causes plasma to segfault

journalctl -b -p err: http://pastebin.com/DYTFwr68

I treid reinstalling polkit/udisks/udisks2/systemd/upower/acpid with no result.

Please, help.

Lone_Wolf · 2014-02-14 09:18:50

maybe something is wrong with your session,
what does this ouput :

$ loginctl show-session $XDG_SESSION_ID

winek · 2014-02-14 14:16:15

Lone_Wolf wrote:

maybe something is wrong with your session,
what does this ouput :
$ loginctl show-session $XDG_SESSION_ID

» olgierd · aspie · piątek, 14 luty 2014 15:15 
          ~ $ loginctl show-session $XDG_SESSION_ID
Failed to get D-Bus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Lone_Wolf · 2014-02-14 23:55:18

that's kinda what i expected, but needed to be sure.

ok, try the following :

- boot to console (append systemd.unit=multi-user.target to your kernel boot line if you normally boot to a display manager/ X)
- login as root
- check journalctl from that boot for dbus related errors
- if there are dbus errrors, pipe dmesg to a file and post it completely

- no dbus errors when booted to console
- login as user (can be another terminal)
- check ~/.xinitrc , and verify it has got an uncommented line 'exec startkde'
- run startx
- repeat the loginctl command above
- post xorg.0.log

winek · 2014-02-15 09:56:57

journalctl -b | grep -Pi 'd-?bus'

lut 15 10:46:06 aspie systemd[1]: Starting D-Bus System Message Bus Socket.
lut 15 10:46:06 aspie systemd[1]: Listening on D-Bus System Message Bus Socket.
lut 15 10:46:11 aspie systemd[1]: Starting D-Bus System Message Bus...
lut 15 10:46:11 aspie systemd[1]: Started D-Bus System Message Bus.
lut 15 10:46:14 aspie dbus[324]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
lut 15 10:46:32 aspie systemd[456]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
lut 15 10:46:39 aspie dbus[324]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
lut 15 10:46:39 aspie ModemManager[319]: <warn>  failed to create PolicyKit authority: 'Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PolicyKit1 timed out'
lut 15 10:46:40 aspie dbus[324]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
lut 15 10:46:40 aspie systemd[500]: Failed to open private bus connection: Failed to connect to socket /run/user/0/dbus/user_bus_socket: No such file or directory
lut 15 10:47:05 aspie dbus[324]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
lut 15 10:47:05 aspie dbus[324]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
lut 15 10:47:05 aspie dbus[324]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
lut 15 10:47:05 aspie dbus[324]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory.
lut 15 10:47:05 aspie dbus[324]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
lut 15 10:47:10 aspie pulseaudio[668]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
lut 15 10:47:10 aspie pulseaudio[668]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
lut 15 10:47:10 aspie pulseaudio[681]: [pulseaudio] bluez5-util.c: Failed to get D-Bus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
lut 15 10:47:10 aspie pulseaudio[681]: [pulseaudio] bluez4-util.c: Failed to get D-Bus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
lut 15 10:47:11 aspie dbus[324]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
lut 15 10:47:11 aspie dbus[324]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory.
lut 15 10:47:11 aspie NetworkManager[320]: <warn> Dispatcher failed: (32) Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory.
lut 15 10:47:28 aspie dbus[324]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
lut 15 10:47:53 aspie dbus[324]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out

dmesg: http://pastebin.com/Zc9b2wEc

Xorg.0.log: http://pastebin.com/x97kiDnn

Lone_Wolf · 2014-02-15 13:30:13

ok, dmesg and xorg.0.log show no errors related to your problem, journaltctl output however does.

lut 15 10:46:14 aspie dbus[324]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
lut 15 10:46:32 aspie systemd[456]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
lut 15 10:46:39 aspie dbus[324]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out

polkit clearly isn't started correctly, but the cause might be with a service required by polkit instead of polkit itself.

Can you post the journalctl output from the 1st upto the last line of the 3 above ?

the output of systemctl status polkit.service would also be useful.
You might wan to check out https://wiki.archlinux.org/index.php/Sy … emd_errors to investigate further.

winek · 2014-02-15 18:37:07

systemctl status polkit.service:

polkit.service - Authorization Manager
   Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
   Active: failed (Result: timeout) since sob 2014-02-15 19:17:15 CET; 5min ago
     Docs: man:polkit(8)
 Main PID: 365

lut 15 19:15:45 aspie systemd[1]: Starting Authorization Manager...
lut 15 19:15:46 aspie polkitd[365]: Started polkitd version 0.112
lut 15 19:17:15 aspie systemd[1]: polkit.service operation timed out. Terminating.
lut 15 19:17:15 aspie systemd[1]: Failed to start Authorization Manager.
lut 15 19:17:15 aspie systemd[1]: Unit polkit.service entered failed state.

journalctl: http://pastebin.com/bxsNhgth

Lone_Wolf · 2014-02-16 16:25:35

lut 15 19:15:45 aspie systemd[1]: Starting Authorization Manager...
lut 15 19:15:46 aspie polkitd[365]: Started polkitd version 0.112
lut 15 19:15:50 aspie mysqld[306]: 2014-02-15 19:15:50 306 [Note] InnoDB: 128 rollback segment(s) are active.
lut 15 19:15:50 aspie mysqld[306]: 2014-02-15 19:15:50 306 [Note] InnoDB: Waiting for purge to start
lut 15 19:15:50 aspie mysqld[306]: 2014-02-15 19:15:50 306 [Note] InnoDB: 5.6.14 started; log sequence number 18039216
lut 15 19:15:51 aspie mysqld[306]: 2014-02-15 19:15:51 306 [Note] RSA private key file not found: /var/lib/mysql//private_key.pem. Some authentication plugins will not work.
lut 15 19:15:51 aspie mysqld[306]: 2014-02-15 19:15:51 306 [Note] RSA public key file not found: /var/lib/mysql//public_key.pem. Some authentication plugins will not work.
lut 15 19:15:51 aspie mysqld[306]: 2014-02-15 19:15:51 306 [Note] Server hostname (bind-address): '*'; port: 3306
lut 15 19:15:51 aspie mysqld[306]: 2014-02-15 19:15:51 306 [Note] IPv6 is available.
lut 15 19:15:51 aspie mysqld[306]: 2014-02-15 19:15:51 306 [Note]   - '::' resolves to '::';
lut 15 19:15:51 aspie mysqld[306]: 2014-02-15 19:15:51 306 [Note] Server socket created on IP: '::'.
lut 15 19:15:51 aspie mysqld[306]: 2014-02-15 19:15:51 306 [ERROR] Column count of mysql.events_waits_current is wrong. Expected 19, found 16. Created with MySQL 50529, now running 50614. Please use mysql_upgrade to fix this error.
lut 15 19:15:51 aspie mysqld[306]: 2014-02-15 19:15:51 306 [ERROR] Column count of mysql.events_waits_history is wrong. Expected 19, found 16. Created with MySQL 50529, now running 50614. Please use mysql_upgrade to fix this error.

it looks like there's is a problem with mariadb (mysql) on your system, check pacman.log for any messages .

If you don't find any, try running mysql_upgrade as suggested in the log.

winek · 2014-02-19 14:47:30

There are no mysql related warnings/errors in pacman.log, and running mysql_upgrade didn't solve the problem. I think this fuckup is related with polkit and/or dbus, but I don't know why it's broken and how to repair it.

Arch Linux

#1 2014-02-13 15:35:49

KDE problems - no device management and battery monitor

#2 2014-02-14 09:18:50

Re: KDE problems - no device management and battery monitor

#3 2014-02-14 14:16:15

Re: KDE problems - no device management and battery monitor

#4 2014-02-14 23:55:18

Re: KDE problems - no device management and battery monitor

#5 2014-02-15 09:56:57

Re: KDE problems - no device management and battery monitor

#6 2014-02-15 13:30:13

Re: KDE problems - no device management and battery monitor

#7 2014-02-15 18:37:07

Re: KDE problems - no device management and battery monitor

#8 2014-02-16 16:25:35

Re: KDE problems - no device management and battery monitor

#9 2014-02-19 14:47:30

Re: KDE problems - no device management and battery monitor

Board footer