--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: plasma-widget-networkmanagement: kded4 leak sockets when wifi connections fail
- From: Petter Reinholdtsen <pere@hungry.com>
- Date: Mon, 16 Sep 2013 13:33:06 +0200
- Message-id: <20130916113306.GA4781@ulrik.uio.no>
Package: plasma-widget-networkmanagement
Version: 0.9.0.3-1
Severity: important
Tags: upstream
Dear Maintainer,
My KDE desktop based on Debian Wheezy is unstable. After a few days,
the KDE panel stop working properly, and I have to log out and in
again to get back to work. Clicking on the K menu do not have any
effect until 20-60 seconds later, and the icons like the battery and
network status are unresposive, with similar delays from mouse clicks.
I believe I tracked down the cause, which is that kded4 is running out
of file descriptors because it is leaking sockets. When the problem
happen, the process have above 1020 files open.
With 23010 as the pid of kded4, I used this one-liner to to track the
number of open files and the distribution across different types:
ls -l /proc/23010/fd|wc -l ; ls -l /proc/23010/fd|rev|cut -d\[ -f2|awk '{print $1}'|rev|sort|uniq -c
It show that approximately 2.5 sockets are leaked per minute at the
moment.
With the good help of pinotree on #debian-kde, I was able to find the
most likely part responsible, and it seem to be the "NetworkManager
User Settings service" available in the System Settings->Startup and
Shutdown->Service Manager menu. When I disable it (and run kdeinit4
to make sure the change take effect), the number of open sockets
stopped increasing. When I enable it again, the number of open
sockets start to increase.
When I now had an idea about the affected system, I tried to disable
wifi using the check box in the network-manager control panel, and the
number of open sockets stayed stable again.
Where I am at the moment, I use TP ethernet, and while there are
several wifi networks around, non of them are really working for me.
But I do notice network-manager try to connect over and over again to
a few of them.
This make me suspect that the plasma-widget-networkmanagement code
fail to close some socket when connecting to a wifi network fail.
I'll try to find time to report this problem upstream too.
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages plasma-widget-networkmanagement depends on:
ii kde-runtime 4:4.8.4-2
ii libc6 2.13-38
ii libgcc1 1:4.7.2-5
ii libkcmutils4 4:4.8.4-4
ii libkdecore5 4:4.8.4-4
ii libkdeui5 4:4.8.4-4
ii libkio5 4:4.8.4-4
ii libknotifyconfig4 4:4.8.4-4
ii libplasma3 4:4.8.4-4
ii libqt4-dbus 4:4.8.2+dfsg-11
ii libqt4-network 4:4.8.2+dfsg-11
ii libqt4-svg 4:4.8.2+dfsg-11
ii libqt4-xml 4:4.8.2+dfsg-11
ii libqtcore4 4:4.8.2+dfsg-11
ii libqtgui4 4:4.8.2+dfsg-11
ii libsolid4 4:4.8.4-4
ii libsolidcontrol4abi2 4:4.8.4-6
ii libstdc++6 4.7.2-5
ii mobile-broadband-provider-info 20120708-1
ii network-manager 0.9.4.0-10
Versions of packages plasma-widget-networkmanagement recommends:
ii kwalletmanager 4:4.8.4-3
ii network-manager-openvpn 0.9.4.0-1
ii network-manager-pptp 0.9.4.0-2
ii network-manager-vpnc 0.9.4.0-1
Versions of packages plasma-widget-networkmanagement suggests:
pn kdebase-workspace-bin <none>
-- no debconf information
--- End Message ---