Hi all,

since I installed KDE4 on Debian SID, KDE applications are very very slow to start. I made an strace to see what happends and saw this -for instance in starting Kwrite- where application is waiting a LONG time

connect(11, {sa_family=AF_INET, sin_port=htons(640), sin_addr=inet_addr("127.0.0.1")}, 16

Same for Kate, Konqueror, okular, dolphin, etc ...

Starting non KDE applications (Iceweasel/Firefox Icedove/thunderbird OpenOffice aso) is not a problem

Thanks for any hint
--
Daniel

Are you inside a KDE session when this occurs?
Has the $KDEHOME variable been set?

bcooksley wrote:Are you inside a KDE session when this occurs?
Has the $KDEHOME variable been set?

I'm inside a KDE session (started applications from Yakuake). KDEHOME was not set so I set it to ~./kde -in Debian there is no kde4- but result is the same.

Does this occur if you start applications from KRunner/Konsole?

Also, has the DBus session bus started successfully? And is kdeinit and klauncher running?

bcooksley wrote:Does this occur if you start applications from KRunner/Konsole?

Yes

bcooksley wrote:Also, has the DBus session bus started successfully? And is kdeinit and klauncher running?

Yes they are running

dh@listryx:>ps ax|grep kdeinit
5603 ? Ss 0:00 kdeinit4: kdeinit4 Running...
5710 ? Ss 0:00 kdeinit Running...
5713 ? S 0:00 dcopserver [kdeinit] --nosid --suicide
5715 ? S 0:00 klauncher [kdeinit] --new-startup
5717 ? S 0:00 kded [kdeinit] --new-startup
5845 ? S 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-dh/klauncherMT5604.slave-socket local:/tmp/ksock
7194 ? S 0:00 knotify [kdeinit]
12341 ? S 0:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-dh/klauncherMT5604.slave-socket local:/tmp/ksock
12435 pts/1 S+ 0:00 grep kdeinit

dh@listryx:>ps ax|grep dbus
4167 ? Ss 0:02 /usr/bin/dbus-daemon --system
5416 ? S 0:00 dbus-launch --autolaunch 9adeb30166829e837bb26f0045ec3534 --binary-syntax --close-stderr
5417 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
5556 ? Ss 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/keytouchd-launch /usr/bin/startkde
5559 ? S 0:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/keytouchd-launch /usr/bin/startkde
5560 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
6041 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
6042 pts/1 S 0:00 dbus-launch --autolaunch 9adeb30166829e837bb26f0045ec3534 --binary-syntax --close-stderr
12456 pts/1 S+ 0:00 grep dbus

At this time, I start the applications (mainly okular and dolphin) once the user session is opened -it takes the time but they start- and then I can use them without problem.

Which type of connection to 127.0.0.1 IP address are they waiting for?

Thanks for your help.

Unfortunately I have no idea.....
Can you reproduce under a new user?

bcooksley wrote:Unfortunately I have no idea.....
Can you reproduce under a new user?

I removed my .kde directory when switching from KDE3 to KDE4. Anyway, I again removed the actual .kde directory -> same. I create a new user -> same.

I also notice that user KDE session takes ages before being usable (~ 5mn)

That nobody knows why applications try to create localhost like
[...]
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 11
connect(11, {sa_family=AF_INET, sin_port=htons(809), sin_addr=inet_addr("127.0.0.1")}, 16

seems strange to me. First line of my /etc/hosts

127.0.0.1 localhost localhost.localdomain

Has it something to do with DNS?

--
Daniel

A naive question: is your loopback interface (lo) properly configured?

einar wrote:A naive question: is your loopback interface (lo) properly configured?

That's the first I check if I see localhost IP involved

dh@listryx:~>sudo ifconfig
lo Link encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:156218 errors:0 dropped:0 overruns:0 frame:0
TX packets:156218 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:28698171 (27.3 MiB) TX bytes:28698171 (27.3 MiB)

Can you please ensure your packages are fully and validly installed?

bcooksley wrote:Can you please ensure your packages are fully and validly installed?

Yes, I think so:

i A kde-icons-oxygen - Oxygen icon theme for KDE 4
i kde-l10n-fr - French (fr) localization files for KDE
i kde-standard - the K Desktop Environment, standard deskto
i A kde-window-manager - the KDE 4 window manager (KWin)
i A kdebase - base applications from the official KDE re
i kdebase-bin - core binaries for the KDE 4 base module
i kdebase-data - shared data files for the KDE 4 base modul
i A kdebase-runtime - runtime components from the official KDE 4
i A kdebase-runtime-bin-kde4 - Programmes nécessaires aux modules d'exécu
i A kdebase-runtime-data - shared data files for the KDE 4 base runti
i A kdebase-runtime-data-common - shared data files for the KDE 4 base runti
i A kdebase-workspace - base workspace components from the officia
i A kdebase-workspace-bin - core binaries for the KDE 4 base workspace
i A kdebase-workspace-data - shared data files for the KDE 4 base works
i A kdebase-workspace-kgreet-plugin - KDE greet libraries for authentication
i A kdebase-workspace-libs4+5 - libraries provided by the KDE 4 base works
i kdebluetooth - KDE Bluetooth Framework
i kdeeject - script used by KDE to eject removable medi
i A kdelibs-bin - executables for all KDE 4 core application
i kdelibs-data - Données partagées de base pour toutes les
i A kdelibs4c2a - Bibliothèques et binaires de base pour tou
i A kdelibs5 - core libraries for all KDE 4 applications
i A kdelibs5-data - core shared data for all KDE 4 application
i kdemultimedia-kio-plugins - transparent audio CD access for KDE 4 appl
i kdenetwork - applications réseau de la version officiel
i A kdenetwork-filesharing - network filesharing configuration module f
i kdepasswd - password changer for KDE 4
i A kdepimlibs-data - core shared data for KDE PIM 4 application
i A kdepimlibs5 - core libraries for KDE PIM 4 applications
i kdevelop - An integrated development environment for
i kdevelop-data - Data files for the KDevelop IDE
i kdevelop-doc - Documentation for the KDevelop IDE
i A libkde4-ruby1.8 - kde4 bindings for ruby
i A libkdecorations4 - library used by decorations for the KDE 4
i A libkdepim4 - Bibliothèque PIM de KDE
i A libsmokekde4-2 - KDE smoke libraries
i A python-kde4 - Python bindings for the KDE 4 libraries
i system-config-printer-kde - KDE 4 printer configuration utility

Thanks for your help

Problem disappear and I suspect udev: my eth interface -always eth0- was modified in eth4 at around the same time I upgraded from Kde3 to Kde4.

Yesterday I decide to adapt the udev setup so eth0 will stay as eth0. I also reboot computer for other stuffs and "oh miracle" no more timeout. Even graphics event from kwin are working w/o "responding to slow, I disable it" message!

Thanks to you bcooksley for your help

--
Daniel

I have exactly the same problem, but renaming eth did not solve it After hours of searching I suspect dbus which makes everything so slow. Unfortunately I do not know, what should I try. I can provide any logs - just name it. I've already cleared all tmp directories. Again key points:

* new home (new user) does not solve it
* it happens everytime I login
* every application using dbus is somehow slow
* strace of any slow application shows something like

Code: Select all

clock_gettime(CLOCK_MONOTONIC, {3163, 397023575}) = 0
writev(8, [{"l\1\0\1\21\0\0\0\"\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/fre"..., 144}, {"\f\0\0\0org.kde.kded\0", 17}], 2) = 161
gettimeofday({1247688346, 716881}, NULL) = 0
poll([{fd=8, events=POLLIN}], 1, 25000) = 1 ([{fd=8, revents=POLLIN}])
read(8, "l\2\1\1\t\0\0\0%\0\0\0=\0\0\0\6\1s\0\5\0\0\0:1.95\0\0\0"..., 2048) = 89
read(8, 0x9095728, 2048)                = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {3163, 398668477}) = 0
writev(8, [{"l\1\0\1\0\0\0\0#\0\0\0k\0\0\0\1\1o\0\5\0\0\0/kded\0\0\0"..., 128}, {"", 0}], 2) = 128
gettimeofday({1247688346, 717703}, NULL) = 0
poll([{fd=8, events=POLLIN}], 1, 25000


Is "qdbusviewer" affected by this "slowness"?

The KDE environment is dependent upon DBus and if it loses access to the session bus then applications will fail to start, access to files will be degraded or not posssible, and the system is basically crippled.

bcooksley wrote:Is "qdbusviewer" affected by this "slowness"?

No it isn't. It started immediately. When I clicked on org.freedesktop.PowerManagement, it froze for a while giving me an error

Code: Select all

Connected to D-Bus.

Error: Call to object / at org.freedesktop.PowerManagement: 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.) failed

This happens also on org.kde.kded, org.kde.kmix and some others.

Any ideas (other than find a dbus forum)? I really appreciate your help.