You are not logged in.
Edit4: a fixed libusbx package has been released.
Edit3: I reported it https://bugs.archlinux.org/task/36418 but meanwhile, people suffering from this can systemctl restart upower and then do run nohup strace -o /dev/null -p $(pidof upowerd) it makes the problem disappear...
Edit2: the problem is https://bugzilla.redhat.com/show_bug.cgi?id=985484
Edit: I thought I solved it but a couple dock-undock operations brings back the problem:
qdbus --system org.freedesktop.UPower
Error: org.freedesktop.DBus.Error.NoReply
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.This causes every KDE window to appear after a 25 second wait cos apparently every new KDE window (even file uploads from Chrome) apparently needs to talk to upower and they wait 25 seconds for a timeout.
If I do a systemctl restart upower, then it gets fixed. There's nothing relevant in dmesg, journalctl, xsession-errors.
Last edited by chx (2013-08-05 08:14:12)
Offline
Same here. It's quite difficult to replicate, it just comes and goes. I first noticed this when I updated to KDE 4.11 RC2.
Offline
It is https://bugzilla.redhat.com/show_bug.cgi?id=985484 and it's fixed. I presume the next libusbx release will fix it properly.
Offline
Thank you very much for posting this workaround. This bug has been affecting me as well, but now at least I can be productive while we wait for upstream to fix it.
Last edited by AuHop (2013-08-05 02:01:29)
Offline
There is an updated libusbx package in testing which appears to have the necessary patch applied. I built myself a fixed up package manually and it's been OK since then.
Offline