--- Please enter the report below this line. --- Probably this doesn't affect just dolphin (see below) but I thought it was a good place to start. Since I upgraded from kde 4.8 to 4.10 dolphin takes at least 20 seconds to start. I think it's related to the places and devices panels. I say this because other kde programs/components that use places and devices are affected in the same way. Examples: Debian Release: jessie/sid 990 unstable ftp.debian.org 101 experimental ftp.debian.org --- Package information. --- Depends (Version) | Installed =========================================-+-=================== kde-runtime (>> 4:4.10) | 4:4.10.5-1 libc6 (>= 2.2) | 2.17-7 libgcc1 (>= 1:4.1.1) | 1:4.8.1-8 libkactivities6 (>= 4:4.10) | 4:4.10.5-1 libkcmutils4 (>= 4:4.10) | 4:4.10.5-1 libkdecore5 (>= 4:4.10) | 4:4.10.5-1 libkdeui5 (>= 4:4.10) | 4:4.10.5-1 libkfile4 (>= 4:4.10) | 4:4.10.5-1 libkio5 (>= 4:4.10.2) | 4:4.10.5-1 libknewstuff3-4 (>= 4:4.10) | 4:4.10.5-1 libkonq5abi1 (>= 4:4.8.1) | 4:4.10.5-1 libkparts4 (>= 4:4.10) | 4:4.10.5-1 libnepomukcore4 (>= 4:4.9.3) | 4:4.10.5-1 libnepomukwidgets4 (>= 4:4.10.0) | 4:4.10.5-1 libphonon4 (>= 4:4.3.0) | 4:4.6.0.0-3 libplasma3 (>= 4:4.10) | 4:4.10.5-1 libqt4-dbus (>= 4:4.5.3) | 4:4.8.5+dfsg-2 libqt4-xml (>= 4:4.5.3) | 4:4.8.5+dfsg-2 libqtcore4 (>= 4:4.8.0) | 4:4.8.5+dfsg-2 libqtgui4 (>= 4:4.7.0~beta2) | 4:4.8.5+dfsg-2 libsolid4 (>= 4:4.10) | 4:4.10.5-1 libsoprano4 (>= 2.1.1) | 2.9.2+dfsg.1-1 libstdc++6 (>= 4.1.1) | 4.8.1-8 libxrender1 | 1:0.9.8-1 phonon | 4:4.6.0.0-3 Recommends (Version) | Installed =========================-+-=========== ruby | 1:1.9.3 Suggests (Version) | Installed =====================================-+-=========== kdesdk-dolphin-plugins | 4:4.10.5+dfsg-1
tag 717932 moreinfo unreproducible thanks Do you have the loopback interface up and running? Please post the output of running ifconfig.
tag 717932 moreinfo unreproducible thanks Do you have the loopback interface up and running? Please post the output of running ifconfig.
lo seems ok: eth2 Link encap:Ethernet HWaddr 10:1f:74:14:c6:63 inet addr:192.168.0.9 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:650048 errors:0 dropped:0 overruns:0 frame:0 TX packets:292963 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:880911238 (840.1 MiB) TX bytes:35170834 (33.5 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:8793528 errors:0 dropped:0 overruns:0 frame:0 TX packets:8793528 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4260907999 (3.9 GiB) TX bytes:4260907999 (3.9 GiB)
lo seems ok: eth2 Link encap:Ethernet HWaddr 10:1f:74:14:c6:63 inet addr:192.168.0.9 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:650048 errors:0 dropped:0 overruns:0 frame:0 TX packets:292963 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:880911238 (840.1 MiB) TX bytes:35170834 (33.5 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:8793528 errors:0 dropped:0 overruns:0 frame:0 TX packets:8793528 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4260907999 (3.9 GiB) TX bytes:4260907999 (3.9 GiB)
lo seems ok: eth2 Link encap:Ethernet HWaddr 10:1f:74:14:c6:63 inet addr:192.168.0.9 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:650048 errors:0 dropped:0 overruns:0 frame:0 TX packets:292963 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:880911238 (840.1 MiB) TX bytes:35170834 (33.5 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:8793528 errors:0 dropped:0 overruns:0 frame:0 TX packets:8793528 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4260907999 (3.9 GiB) TX bytes:4260907999 (3.9 GiB)
downgrading to upower 0.9.17 seems to fix the problem
Spoken too soon.....when the deamon restarts the problem is back. But killing upowerd actually does solve the problem (not in a satisfactory way, of course)