| View previous topic :: View next topic |
| Author |
Message |
Kollin
Veteran
Joined: 25 Feb 2006
Posts: 1139
Location: Sofia/Bulgaria
|
 Posted: Tue Feb 17, 2015 7:33 am Post subject: [SOLVED] Network problem in KDE4?!?! |
 |
|
Ping BEFORE logging in KDE4:
| Code: | PING gmail.com (216.58.208.101) 56(84) bytes of data.
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=1 ttl=59 time=3.73 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=2 ttl=59 time=4.58 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=3 ttl=59 time=1.42 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=4 ttl=59 time=1.46 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=5 ttl=59 time=1.65 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=6 ttl=59 time=1.34 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=7 ttl=59 time=2.21 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=8 ttl=59 time=3.93 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=9 ttl=59 time=1.39 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=10 ttl=59 time=1.39 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=11 ttl=59 time=1.48 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=12 ttl=59 time=1.40 ms
--- gmail.com ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11016ms
rtt min/avg/max/mdev = 1.348/2.171/4.584/1.142 ms |
Ping AFTER logging in KDE4:
| Code: | PING gmail.com (216.58.208.101) 56(84) bytes of data.
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=1 ttl=59 time=328 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=2 ttl=59 time=2124 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=3 ttl=59 time=1131 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=4 ttl=59 time=2697 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=5 ttl=59 time=9.45 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=6 ttl=59 time=1293 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=7 ttl=59 time=304 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=8 ttl=59 time=2943 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=9 ttl=59 time=2108 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=10 ttl=59 time=1108 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=11 ttl=59 time=3063 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=12 ttl=59 time=2093 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=13 ttl=59 time=1094 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=14 ttl=59 time=3097 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=15 ttl=59 time=2.16 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=16 ttl=59 time=35.5 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=17 ttl=59 time=1967 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=18 ttl=59 time=992 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=19 ttl=59 time=3014 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=20 ttl=59 time=2059 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=21 ttl=59 time=1064 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=22 ttl=59 time=3253 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=23 ttl=59 time=1472 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=24 ttl=59 time=2428 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=25 ttl=59 time=2084 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=26 ttl=59 time=5134 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=27 ttl=59 time=4229 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=28 ttl=59 time=3419 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=29 ttl=59 time=2446 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=30 ttl=59 time=1448 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=31 ttl=59 time=4459 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=32 ttl=59 time=1.29 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=33 ttl=59 time=152 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=34 ttl=59 time=1498 ms
64 bytes from sof01s11-in-f5.1e100.net (216.58.208.101): icmp_seq=35 ttl=59 time=531 ms
64 bytes from 216.58.208.101: icmp_seq=36 ttl=59 time=14.9 ms
--- gmail.com ping statistics ---
36 packets transmitted, 36 received, 0% packet loss, time 107864ms
rtt min/avg/max/mdev = 1.299/1808.660/5134.992/1342.325 ms, pipe 4
|
And the strangest part is: If I initiate a network traffic before logging in KDE4(usually online radio with cvlc), ping stays normal:
| Code: | ping google.com
PING google.com (216.58.208.110) 56(84) bytes of data.
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=1 ttl=59 time=4.05 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=2 ttl=59 time=1.44 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=3 ttl=59 time=1.43 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=4 ttl=59 time=1.75 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=5 ttl=59 time=1.42 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=6 ttl=59 time=2.17 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=7 ttl=59 time=2.69 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=8 ttl=59 time=1.44 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=9 ttl=59 time=1.44 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=10 ttl=59 time=1.40 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=11 ttl=59 time=1.45 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=12 ttl=59 time=1.47 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=13 ttl=59 time=1.41 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=14 ttl=59 time=1.39 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=15 ttl=59 time=1.43 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=16 ttl=59 time=1.41 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=17 ttl=59 time=1.40 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=18 ttl=59 time=1.69 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=19 ttl=59 time=3.66 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=20 ttl=59 time=1.46 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=21 ttl=59 time=1.55 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=22 ttl=59 time=2.08 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=23 ttl=59 time=1.57 ms
64 bytes from sof01s11-in-f14.1e100.net (216.58.208.110): icmp_seq=24 ttl=59 time=1.64 ms
|
This is haunting me for years already. I've been through several kde4 and kernel incarnations and this problem stays no matter what. 
_________________
"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."
Last edited by Kollin on Fri Mar 06, 2015 7:01 pm; edited 1 time in total |
|
| Back to top |
|
 |
Atmmac
Tux's lil' helper
Joined: 17 Oct 2013
Posts: 130
Location: Watertown, MA
|
| Posted: Wed Feb 25, 2015 12:00 am Post subject: |
|
|
| I had some weird stuff like this the other day. Try setting a static ip in network manager and see if it works. |
|
| Back to top |
|
|
Kollin
Veteran
Joined: 25 Feb 2006
Posts: 1139
Location: Sofia/Bulgaria
|
| Posted: Wed Feb 25, 2015 10:22 pm Post subject: |
|
|
Sadly static configuration did not help, thank you Atmmac!
_________________
"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..." |
|
| Back to top |
|
|
linuxtuxhellsinki
l33t
Joined: 15 Nov 2004
Posts: 700
Location: Hellsinki
|
| Posted: Sat Feb 28, 2015 9:56 am Post subject: |
|
|
I had some really strange problems when upgrading to KDE-4.14.3 last week (mostly with akonadi semantic-desktop crap) and when I fixed the system from terminal the network was really slow. After I've got the system (=KDE) fixed everything is working fine again.
I don't think that this helps you and I don't know what was exactly causing my problems, but it was strange for me that the upgrading gui/kde could affect the network performance. Only thing I found with top was that while the CPU usage was low there was very high ~99% wait and lots of I/O with plasma/icon-cache files in /var/tmp/kdecache-user/ folder.
_________________
1st use 'Search' & lastly add [Solved] to
the subject of your first post in the thread. |
|
| Back to top |
|
|
Kollin
Veteran
Joined: 25 Feb 2006
Posts: 1139
Location: Sofia/Bulgaria
|
| Posted: Sat Feb 28, 2015 12:36 pm Post subject: |
|
|
Thank you linuxtuxhellsinki!
I found the issue! It was the pulseaudio hogging the network! 
One of these usefalgs was responsible: gnome libsamplerate realtime lirc 
socket-sentry is really a useful tool. 
_________________
"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..." |
|
| Back to top |
|
|
|
Desktop Environments
