| View previous topic :: View next topic |
| Author |
Message |
koan
Apprentice
Joined: 01 May 2006
Posts: 169
Location: Melbourne
|
 Posted: Sun Jul 06, 2014 10:23 pm Post subject: [solved] DBUS 1.8.x breaks upower |
 |
|
I am running systemd with dbus and upower, all stable tree.
dbus (with systemd use flag) wants to update to 1.8.x and when this happens, upower breaks, as does most multimedia things.
Messages reports that upower can't connect to dbus, yet dbus is running fine. What am I missing?
If I revert to dbus 1.6.x all is well.
| Code: | $ sudo systemctl status upower.service
● upower.service - Daemon for power management
Loaded: loaded (/usr/lib64/systemd/system/upower.service; enabled)
Active: failed (Result: start-limit) since Mon 2014-07-07 08:15:55 EST; 16s ago
Docs: man:upowerd(8)
Process: 21590 ExecStart=/usr/lib/upower/upowerd (code=exited, status=1/FAILURE)
Main PID: 21590 (code=exited, status=1/FAILURE)
Jul 07 08:15:54 zone systemd[1]: Failed to start Daemon for power management.
Jul 07 08:15:54 zone systemd[1]: Unit upower.service entered failed state.
Jul 07 08:15:55 zone systemd[1]: upower.service holdoff time over, scheduling restart.
Jul 07 08:15:55 zone systemd[1]: Stopping Daemon for power management...
Jul 07 08:15:55 zone systemd[1]: Starting Daemon for power management...
Jul 07 08:15:55 zone systemd[1]: upower.service start request repeated too quickly, refusing to start.
Jul 07 08:15:55 zone systemd[1]: Failed to start Daemon for power management.
Jul 07 08:15:55 zone systemd[1]: Unit upower.service entered failed state. |
| Code: | $ sudo journalctl -xn
-- Logs begin at Tue 2014-04-29 07:01:03 EST, end at Mon 2014-07-07 08:17:43 EST. --
Jul 07 08:16:11 zone sudo[21592]: pam_unix(sudo:session): session opened for user root by paul(uid=0Jul 07 08:16:11 zone sudo[21592]: pam_systemd(sudo:session): Failed to connect to system bus: No such file or directory
Jul 07 08:16:11 zone sudo[21592]: pam_unix(sudo:session): session closed for user root
Jul 07 08:17:26 zone sudo[21599]: paul : TTY=pts/1 ; PWD=/var/log/portage/elog ; USER=root ; COMMAND=/usr/bin/systemctl status dbus
Jul 07 08:17:26 zone sudo[21599]: pam_unix(sudo:session): session opened for user root by paul(uid=0)
Jul 07 08:17:26 zone sudo[21599]: pam_systemd(sudo:session): Failed to connect to system bus: No such file or directory
Jul 07 08:17:26 zone sudo[21599]: pam_unix(sudo:session): session closed for user root
|
| Code: | $ ps auwx | grep dbus
paul 2510 0.0 0.0 24348 624 ? S Jul06 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
paul 2511 0.0 0.0 18524 1952 ? Ss Jul06 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
paul 2895 0.0 0.0 17432 1456 ? S Jul06 0:00 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3 |
From messages:
| Code: | Jul 7 08:15:54 zone systemd[1]: Starting Daemon for power management...
Jul 7 08:15:54 zone upowerd[21588]: (upowerd:21588): UPower-WARNING **: Couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Jul 7 08:15:54 zone systemd[1]: upower.service: main process exited, code=exited, status=1/FAILURE
Jul 7 08:15:54 zone systemd[1]: Failed to start Daemon for power management.
Jul 7 08:15:54 zone systemd[1]: Unit upower.service entered failed state.
Jul 7 08:15:54 zone systemd[1]: upower.service holdoff time over, scheduling restart.
Jul 7 08:15:54 zone systemd[1]: Stopping Daemon for power management...
|
| Code: | $ qdbus
:1.1
org.kde.klauncher
:1.10
org.kde.knotify
:1.12
org.freedesktop.ScreenSaver
org.kde.ksmserver
org.kde.ksmserver-2570
org.kde.screensaver
:1.13
org.kde.KWin
org.kde.kwin
org.kde.kwin-2583
org.kde.kwin.Compositing
org.kde.kwin.Effects
org.kde.kwin.Screenshot
org.kde.kwin.Scripting
:1.15
org.freedesktop.Notifications
org.kde.DeviceNotifications
org.kde.StatusNotifierHost-2602
org.kde.plasma-desktop
:1.17
org.kde.JobViewServer
org.kde.kuiserver
:1.19
org.freedesktop.Akonadi.Control
org.freedesktop.Akonadi.Control.lock
:1.2
org.kde.StatusNotifierWatcher
org.kde.kded
org.kde.keyboard
:1.20
org.freedesktop.Akonadi
:1.23
org.kde.NepomukServer
:1.25
org.kde.NepomukStorage
org.kde.nepomuk.services.nepomukontologyloader
org.kde.nepomuk.services.nepomukqueryservice
org.kde.nepomuk.services.nepomukstorage
....snip....
|
Last edited by koan on Tue Jul 08, 2014 4:32 am; edited 1 time in total |
|
| Back to top |
|
 |
SamuliSuominen
Retired Dev
Joined: 30 Sep 2005
Posts: 2133
Location: Finland
|
| Posted: Mon Jul 07, 2014 7:27 am Post subject: |
|
|
| 1.6.x to 1.8.x is a major upgrade and dbus. and everything using dbus, needs to be restarted. have you done that? |
|
| Back to top |
|
|
koan
Apprentice
Joined: 01 May 2006
Posts: 169
Location: Melbourne
|
| Posted: Mon Jul 07, 2014 7:58 am Post subject: |
|
|
| ssuominen wrote: | | 1.6.x to 1.8.x is a major upgrade and dbus. and everything using dbus, needs to be restarted. have you done that? |
Yes, rebooted in fact - that is when I noticed that power management and my audio devices weren't working any more. Also preserved-rebuilt - but nothing to do there.
I don't think there is anything unusual about my setup, so I think there would be more reports if it was a common problem.
That's why I figured I must have missed something. Does dbus 1.8.x rely on something I might not have done? Could upower be looking in the wrong place for the socket? |
|
| Back to top |
|
|
SamuliSuominen
Retired Dev
Joined: 30 Sep 2005
Posts: 2133
Location: Finland
|
| Posted: Mon Jul 07, 2014 8:11 am Post subject: |
|
|
| koan wrote: | | ssuominen wrote: | | 1.6.x to 1.8.x is a major upgrade and dbus. and everything using dbus, needs to be restarted. have you done that? |
Yes, rebooted in fact - that is when I noticed that power management and my audio devices weren't working any more. Also preserved-rebuilt - but nothing to do there.
I don't think there is anything unusual about my setup, so I think there would be more reports if it was a common problem.
That's why I figured I must have missed something. Does dbus 1.8.x rely on something I might not have done? Could upower be looking in the wrong place for the socket? |
Have you recompiled systemd since upgrading to 1.8.x? To my best knowledge, it shouldn't be required, but you never can be sure. Perhaps emerging dbus with `emerge --noconfmem` is good idea as well, to ensure files in /etc get updated.
This is the first time I'm hearing someone having actual problems with the upgrade. |
|
| Back to top |
|
|
koan
Apprentice
Joined: 01 May 2006
Posts: 169
Location: Melbourne
|
| Posted: Mon Jul 07, 2014 1:17 pm Post subject: |
|
|
It was when I went to re-emerge dbus that I saw it.
I had the systemd use flag suppressed for systemd. I cannot fathom why, perhaps I did it to solve some problem pre-systemd.
But I also don't understand how dbus / systemd was working without dbus having systemd previously.
Perhaps the use flag had little effect on dbus 1.6.
Anyway, this problem is solved, category: stupidity. |
|
| Back to top |
|
|
SamuliSuominen
Retired Dev
Joined: 30 Sep 2005
Posts: 2133
Location: Finland
|
| Posted: Mon Jul 07, 2014 2:30 pm Post subject: |
|
|
| koan wrote: | It was when I went to re-emerge dbus that I saw it.
I had the systemd use flag suppressed for systemd. I cannot fathom why, perhaps I did it to solve some problem pre-systemd.
But I also don't understand how dbus / systemd was working without dbus having systemd previously.
Perhaps the use flag had little effect on dbus 1.6.
Anyway, this problem is solved, category: stupidity. |
oh, wow. i should have asked for 'emerge -pv dbus systemd' output.
i'm glad you got it solved.
perhaps update the thread subject to say [solved]? |
|
| Back to top |
|
|
|
Desktop Environments
