I am new to the openSUSE forums, so I am not quite sure whether the Laptop forum is the right one for my question.
I have been running openSUSE 12.3 with KDE on my Dell Latitude E5530 laptop for some time now, and have been very pleased with it.
This morning (October 12, 2013) I installed the latest updates for openSUSE 12.3, and now my KDE desktop has some issues.
It takes a very long time (several minutes) to appear (and sometimes it does not appear fully). My wireless networking does not function, and I get a message that the laptop is not plugged in to the power grid, when in fact it is.
In /var/log/messages I notice some messages I have not seen before installing the updates:
dbus[486]: [system] Activating via systemd: service name=‘org.freedesktop.UDisks2’ unit=‘udisks2.service’
dbus[486]: [system] Failed to activate ‘org.freedesktop.UDisks2’: timed out
dbus[486]: [system] Activating via systemd: service name=‘org.freedesktop.UPower’ unit=‘upower.service’
dbus[486]: [system] Failed to activate ‘org.freedesktop.UPower’: timed out
These messages start appearing as soon as I log in on the GUI screen, and are repeated over and over again.
The five icons that KDE shows after logging in (disk, toolbox, globe, monitor and KDE logo) take a long time to appear.
Logging on tty1 works ok. I don’t see any processes taking up a lot of processing power.
dbus version: dbus-1-1.7.4-7.1.x86_64
Does anyone know how to fix this, or whether this problem has been reported before? I did not find anything recent.
I haven’t installed that update yet, but maybe it causes your problem (there was a similar issue in 13.1beta as well after dbus-1 was updated).
Try to switch back to the previous version:
Run YaST->Software Management, search for dbus, click on the “Versions” tab in the bottom-right part of the window, and switch all dbus packages to the previous version there.
Wait a moment. I just had a look at the update repo, and the latest version in there is dbus-1-1.6.8-2.10.1.
So where have you got that update from? (apparently it’s an older Factory version that was broken)
Please show the output of “rpm -qi dbus-1” and “zypper lr -d”.
Thank you for your reply. You may be on to something here.
This is what rpm -qi dbus-1 and zypper lr -d report:
rpm -qi dbus-1
Name : dbus-1
Version : 1.7.4
Release : 7.1
Architecture: x86_64
Install Date: Sat Oct 12 11:44:27 2013
Group : System/Daemons
Size : 907702
License : GPL-2.0+ or AFL-2.1
Signature : RSA/SHA256, Mon Sep 30 09:59:19 2013, Key ID b88b2fd43dbdc284
Source RPM : dbus-1-x11-1.7.4-7.1.src.rpm
Build Date : Mon Sep 30 09:58:29 2013
Build Host : build05
Relocations : (not relocatable)
Packager : openSUSE:Submitting bug reports - openSUSE
Vendor : openSUSE
URL : dbus
Summary : D-Bus Message Bus System
Description :
D-Bus is a message bus system, a simple way for applications to talk to
one another. D-Bus supplies both a system daemon and a
per-user-login-session daemon. Also, the message bus is built on top of
a general one-to-one message passing framework, which can be used by
any two apps to communicate directly (without going through the message
bus daemon).
Distribution: openSUSE Factory
zypper lr -d
| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
Because you have that repo in your list, most likely other packages have been switched to their Factory versions as well already.
I would recommend to remove that repo and run “sudo zypper dup” to switch everything back to the 12.3 versions.
And another note: you should remove the “Packman Essentials” repo (#7) as well. You have the full Packman repo anyway (#1), that one also contains the packages from Essentials.
Oh, and since you mentioned wireless network problems:
Your having a repo in your list with broadcom driver packages for 12.3’s kernel (3.7.10), apparently this driver is needed for your wireless, right?
Those packages won’t work anymore if you use Factory’s kernel (3.11.x).
If you already have the Factory’s kernel installed, have a look into “Advanced Options” at the boot menu, maybe you’re lucky and still have the 3.7.10 kernel available as well. If you boot that, the broadcom driver (and wireless network therefore) should work again.
I am happy to say that everything is working again, including wireless networking.
I removed both repositories (Factory and Packman Essentials), and ran ‘zypper dup’.
Fortunately my kernel had not been updated to 3.1.11, so I did not have to revert to a previous kernel.
Thank you very much for your help. I really appreciate it!