FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian KDE

 
 
LinkBack Thread Tools
 
Old 07-01-2012, 11:49 AM
chymian
 
Default plasma desktop hangs

hi everybody,

since a while now (at least a year), KDE does have the following behavior:

while the WLAN-connection is stable, every thing is good.
moving my laptop (i.e. to the terrasse) where it often still has a 50% signal, the pbls. begin:

while it rechecks/reconnect to the wlan, plasma hangs (menues, systray, etc all frozen, kwin still is responsable, can move
windows) for a minute or 2! that happens on movment and also, while I don't move the box - just out of the sky on rechecking
the connection.

first, I used Network-Manager + plasmoid, which often was not able to reconnect. I had to manual stop the manager, sometimes
reload the module & restart the manager, then wait till KDE realises, that there is network again.
after it had lost the connection once, it's keeping me asking over and over for the WLAN-secret, which was already in kwallet
and too often, the only way out was to complety remove the connection and configure it new.

then I moved to WICD, (for the price of loosing my comfortable VPN's setup).
WICD is ****MUCH**** more stable, never asks for the password but still hangs plasma now and then. but seems to be 80%
more stable.


since I swapped hardware 4 weeks ago, it dosen't look like a driver/module-pbl. to me. (b43 before, iwlwifi now).
I also see this on some laptops of friends, all KDE 4.4 - 4.8, wheezy.
and I checked it with three different WLAN-routers - all same behavior.

so, even if it's a driver-/network-pbl. the basic line here:

plasma should definitly NOT freeze on a lost network connection.

running on
KDE-SC 4.8.4,
wheezy,
wicd 1.7.2.4-2, wicd-kde 0.3.0-2

kernel 3.0 ... .3.5-rc2 (all show the same behavior)

all I see in the syslog is: wlan dropped connection and is trying to reconnect for a while.


any hint's, how to prevent KDE from freezing?
anybody sees the same behavior?
and who get's the bug-report? kde for freezing?, kernel for dropping, one (or both) of the network-managers?


since I didn't got an answeer on debian-user for a week, I cross post it to the kde-list. sorry for that, but I think I should have
done this in the first place.

update: since plasma hangs on the described network-problem quit often, it also hangs sometimes after switching activities for
a minute or so.

any hint, how to hunt it down?

cheers,
günter



log starts, with unpluging my ext. HDD before I move the laptop:

Jun 26 14:28:41 merkaba acpid: input device has been disconnected, fd 12
Jun 26 14:28:45 merkaba kernel: [ 3982.161109] ata5: hard resetting link
Jun 26 14:28:46 merkaba kernel: [ 3982.465661] ata5: SATA link down (SStatus 0 SControl 310)
Jun 26 14:28:46 merkaba kernel: [ 3982.465672] ata5.00: disabled
Jun 26 14:28:46 merkaba kernel: [ 3982.476617] ata5: EH complete
Jun 26 14:28:46 merkaba kernel: [ 3982.476635] ata5.00: detaching (SCSI 4:0:0:0)
Jun 26 14:28:46 merkaba kernel: [ 3982.477260] sd 4:0:0:0: [sdc] Synchronizing SCSI cache
Jun 26 14:28:46 merkaba kernel: [ 3982.477336] sd 4:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jun 26 14:28:46 merkaba kernel: [ 3982.477347] sd 4:0:0:0: [sdc] Stopping disk
Jun 26 14:28:46 merkaba kernel: [ 3982.477367] sd 4:0:0:0: [sdc] START_STOP FAILED
Jun 26 14:28:46 merkaba kernel: [ 3982.477372] sd 4:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Jun 26 14:29:44 merkaba anacron[20062]: Anacron 2.3 started on 2012-06-26
Jun 26 14:29:44 merkaba anacron[20062]: Normal exit (0 jobs run)
Jun 26 14:30:07 merkaba init: Switching to runlevel: 5
Jun 26 14:30:07 merkaba acpid: client connected from 20382[0:0]
Jun 26 14:30:07 merkaba acpid: 1 client rule loaded
Jun 26 14:30:07 merkaba kdm_greet[20406]: Cannot set locale. Translations will not work.
Jun 26 14:30:07 merkaba kdm_greet[20406]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or
directory
Jun 26 14:33:05 merkaba kdm: :0[20520]: pam_ecryptfs: Passphrase file wrapped
Jun 26 14:35:33 merkaba amd[3608]: No fs type specified (key = "/defaults", map = ""root"")
Jun 26 14:35:33 merkaba amd[3608]: Unknown host: .Trash
Jun 26 14:35:33 merkaba amd[3608]: No fs type specified (key = "/defaults", map = ""root"")
Jun 26 14:35:33 merkaba amd[3608]: Unknown host: .Trash-1000
Jun 26 14:35:48 merkaba pulseaudio[21647]: [pulseaudio] pid.c: Daemon already running.
Jun 26 14:35:48 merkaba pulseaudio[21654]: [pulseaudio] pid.c: Daemon already running.
Jun 26 14:36:48 merkaba kernel: [ 4464.281193] cfg80211: Calling CRDA to update world regulatory domain
Jun 26 14:36:51 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:36:51 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:36:51 merkaba dhclient: All rights reserved.
Jun 26 14:36:51 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:36:51 merkaba dhclient:
Jun 26 14:36:52 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:36:52 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:36:52 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:36:52 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:36:52 merkaba dnsmasq[2879]: reading /var/run/dnsmasq/resolv.conf
Jun 26 14:36:52 merkaba dnsmasq[2879]: using nameserver 192.168.2.9#53
Jun 26 14:36:52 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:36:52 merkaba avahi-daemon[2309]: Withdrawing address record for 192.168.2.58 on wlan0.
Jun 26 14:36:52 merkaba avahi-daemon[2309]: Withdrawing address record for 192.168.2.9 on wlan0.
Jun 26 14:36:52 merkaba avahi-daemon[2309]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.9.
Jun 26 14:36:52 merkaba avahi-daemon[2309]: Interface wlan0.IPv4 no longer relevant for mDNS.
Jun 26 14:36:52 merkaba avahi-daemon[2309]: Received packet from invalid interface.
Jun 26 14:36:52 merkaba avahi-dnsconfd[2614]: DNS Server 192.168.2.9 removed (interface: 3.IPv4)
Jun 26 14:36:52 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:36:52 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:36:52 merkaba kernel: [ 4467.660429] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:36:52 merkaba kernel: [ 4467.667163] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:36:52 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:36:52 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:36:52 merkaba dhclient: All rights reserved.
Jun 26 14:36:52 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:36:52 merkaba dhclient:
Jun 26 14:36:52 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:36:52 merkaba dhclient: Listening on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:36:52 merkaba dhclient: Sending on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:36:52 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:36:52 merkaba dhclient: DHCPRELEASE on eth0 to 192.168.2.1 port 67
Jun 26 14:36:52 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:36:52 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:36:52 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:36:52 merkaba kernel: [ 4468.222787] r8169 0000:04:00.2: eth0: link down
Jun 26 14:36:56 merkaba kernel: [ 4472.482235] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:36:56 merkaba kernel: [ 4472.488959] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:37:00 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:37:00 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:37:00 merkaba dhclient: All rights reserved.
Jun 26 14:37:00 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:37:00 merkaba dhclient:
Jun 26 14:37:00 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:37:00 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:37:00 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:37:00 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:37:00 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:37:00 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:37:00 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:00 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:37:00 merkaba kernel: [ 4476.421177] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:37:00 merkaba kernel: [ 4476.427901] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:37:01 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:37:01 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:37:01 merkaba dhclient: All rights reserved.
Jun 26 14:37:01 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:37:01 merkaba dhclient:
Jun 26 14:37:01 merkaba dhclient: Listening on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:37:01 merkaba dhclient: Sending on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:37:01 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:37:01 merkaba dhclient: DHCPRELEASE on eth0 to 192.168.2.1 port 67
Jun 26 14:37:01 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:37:01 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:37:01 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:01 merkaba kernel: [ 4476.732113] r8169 0000:04:00.2: eth0: link down
Jun 26 14:37:01 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:37:01 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:37:01 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:37:01 merkaba dhclient: All rights reserved.
Jun 26 14:37:01 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:37:01 merkaba dhclient:
Jun 26 14:37:01 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:37:01 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:37:01 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:37:01 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:37:01 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:37:01 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:37:01 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:01 merkaba kernel: [ 4477.458198] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:37:01 merkaba kernel: [ 4477.464931] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:37:04 merkaba kernel: [ 4479.920784] wlan0: authenticate with 00:1a:4f:02:ad:91
Jun 26 14:37:04 merkaba kernel: [ 4479.922695] wlan0: send auth to 00:1a:4f:02:ad:91 (try 1/3)
Jun 26 14:37:04 merkaba kernel: [ 4479.924660] wlan0: authenticated
Jun 26 14:37:04 merkaba kernel: [ 4479.924687] wlan0: waiting for beacon from 00:1a:4f:02:ad:91
Jun 26 14:37:04 merkaba kernel: [ 4479.942717] wlan0: associate with 00:1a:4f:02:ad:91 (try 1/3)
Jun 26 14:37:04 merkaba kernel: [ 4479.946235] wlan0: RX AssocResp from 00:1a:4f:02:ad:91 (capab=0x411 status=0 aid=2)
Jun 26 14:37:04 merkaba kernel: [ 4479.946243] wlan0: associated
Jun 26 14:37:05 merkaba avahi-daemon[2309]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.9.
Jun 26 14:37:05 merkaba avahi-daemon[2309]: New relevant interface wlan0.IPv4 for mDNS.
Jun 26 14:37:05 merkaba avahi-daemon[2309]: Registering new address record for 192.168.2.9 on wlan0.IPv4.
Jun 26 14:37:05 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:06 merkaba avahi-dnsconfd[2614]: New DNS Server 192.168.2.9 (interface: 3.IPv4)
Jun 26 14:37:06 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:08 merkaba kernel: [ 4483.965577] wlan0: deauthenticated from 00:1a:4f:02:ad:91 (Reason: 1)
Jun 26 14:37:08 merkaba kernel: [ 4484.006758] cfg80211: Calling CRDA to update world regulatory domain
Jun 26 14:37:08 merkaba dnsmasq[2879]: reading /var/run/dnsmasq/resolv.conf
Jun 26 14:37:08 merkaba dnsmasq[2879]: using nameserver 192.168.2.1#53
Jun 26 14:37:08 merkaba dnsmasq[2879]: using nameserver 192.168.33.1#53
Jun 26 14:37:08 merkaba dnsmasq[2879]: using nameserver 192.168.2.9#53
Jun 26 14:37:08 merkaba dnsmasq[2487]: reading /etc/resolv.conf
Jun 26 14:37:08 merkaba dnsmasq[2487]: using nameserver 127.0.0.1#53
Jun 26 14:37:11 merkaba kernel: [ 4487.260971] wlan0: authenticate with 00:1a:4f:02:ad:91
Jun 26 14:37:11 merkaba kernel: [ 4487.262919] wlan0: send auth to 00:1a:4f:02:ad:91 (try 1/3)
Jun 26 14:37:11 merkaba kernel: [ 4487.463512] wlan0: send auth to 00:1a:4f:02:ad:91 (try 2/3)
Jun 26 14:37:12 merkaba kernel: [ 4487.664177] wlan0: send auth to 00:1a:4f:02:ad:91 (try 3/3)
Jun 26 14:37:12 merkaba kernel: [ 4487.864880] wlan0: authentication with 00:1a:4f:02:ad:91 timed out
Jun 26 14:37:12 merkaba kernel: [ 4487.881065] iwlwifi 0000:03:00.0: ACTIVATE a non DRIVER active station id 0 addr
00:1a:4f:02:ad:91
Jun 26 14:37:42 merkaba avahi-daemon[2309]: Withdrawing address record for 192.168.2.9 on wlan0.
Jun 26 14:37:42 merkaba avahi-daemon[2309]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.9.
Jun 26 14:37:42 merkaba avahi-daemon[2309]: Interface wlan0.IPv4 no longer relevant for mDNS.
Jun 26 14:37:42 merkaba avahi-dnsconfd[2614]: DNS Server 192.168.2.9 removed (interface: 3.IPv4)
Jun 26 14:37:42 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:42 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:37:42 merkaba kernel: [ 4518.403398] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:37:42 merkaba kernel: [ 4518.410109] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:37:46 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:37:46 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:37:46 merkaba dhclient: All rights reserved.
Jun 26 14:37:46 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:37:46 merkaba dhclient:
Jun 26 14:37:46 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:37:46 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:37:46 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:37:46 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:37:46 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:37:46 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:37:46 merkaba dnsmasq[2879]: reading /var/run/dnsmasq/resolv.conf
Jun 26 14:37:46 merkaba dnsmasq[2879]: using nameserver 192.168.2.9#53
Jun 26 14:37:46 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:46 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:37:46 merkaba kernel: [ 4521.832071] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:37:46 merkaba kernel: [ 4521.838803] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:37:46 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:37:46 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:37:46 merkaba dhclient: All rights reserved.
Jun 26 14:37:46 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:37:46 merkaba dhclient:
Jun 26 14:37:46 merkaba dhclient: Listening on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:37:46 merkaba dhclient: Sending on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:37:46 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:37:46 merkaba dhclient: DHCPRELEASE on eth0 to 192.168.2.1 port 67
Jun 26 14:37:46 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:37:46 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:37:46 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:46 merkaba kernel: [ 4522.106535] r8169 0000:04:00.2: eth0: link down
Jun 26 14:37:46 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:37:46 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:37:46 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:37:46 merkaba dhclient: All rights reserved.
Jun 26 14:37:46 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:37:46 merkaba dhclient:
Jun 26 14:37:46 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:37:46 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:37:46 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:37:46 merkaba ddclient[2827]: WARNING: cannot connect to checkip.dyndns.com:80 socket: IO::Socket::INET: Bad
hostname 'checkip.dyndns.com'
Jun 26 14:37:46 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:37:46 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:37:46 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:37:46 merkaba ddclient[2827]: WARNING: cannot connect to checkip.dyndns.com:80 socket: IO::Socket::INET: Bad
hostname 'checkip.dyndns.com'
Jun 26 14:37:46 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:46 merkaba kernel: [ 4522.301154] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:37:46 merkaba kernel: [ 4522.307882] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:37:47 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:37:47 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:37:47 merkaba dhclient: All rights reserved.
Jun 26 14:37:47 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:37:47 merkaba dhclient:
Jun 26 14:37:47 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:37:47 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:37:47 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:37:47 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:37:47 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:37:47 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:37:47 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:47 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:37:47 merkaba kernel: [ 4523.412641] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:37:47 merkaba kernel: [ 4523.419361] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:37:48 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:37:48 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:37:48 merkaba dhclient: All rights reserved.
Jun 26 14:37:48 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:37:48 merkaba dhclient:
Jun 26 14:37:48 merkaba dhclient: Listening on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:37:48 merkaba dhclient: Sending on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:37:48 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:37:48 merkaba dhclient: DHCPRELEASE on eth0 to 192.168.2.1 port 67
Jun 26 14:37:48 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:37:48 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:37:48 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:48 merkaba kernel: [ 4523.695170] r8169 0000:04:00.2: eth0: link down
Jun 26 14:37:49 merkaba kernel: [ 4524.529430] wlan0: authenticate with 00:1a:4f:02:ad:91
Jun 26 14:37:49 merkaba kernel: [ 4524.531398] wlan0: send auth to 00:1a:4f:02:ad:91 (try 1/3)
Jun 26 14:37:49 merkaba kernel: [ 4524.533091] wlan0: authenticated
Jun 26 14:37:49 merkaba kernel: [ 4524.533296] wlan0: associate with 00:1a:4f:02:ad:91 (try 1/3)
Jun 26 14:37:49 merkaba kernel: [ 4524.537003] wlan0: RX AssocResp from 00:1a:4f:02:ad:91 (capab=0x411 status=0 aid=2)
Jun 26 14:37:49 merkaba kernel: [ 4524.537008] wlan0: associated
Jun 26 14:37:50 merkaba avahi-daemon[2309]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.9.
Jun 26 14:37:50 merkaba dnsmasq[2487]: reading /etc/resolv.conf
Jun 26 14:37:50 merkaba dnsmasq[2487]: using nameserver 127.0.0.1#53
Jun 26 14:37:50 merkaba avahi-daemon[2309]: New relevant interface wlan0.IPv4 for mDNS.
Jun 26 14:37:50 merkaba avahi-daemon[2309]: Registering new address record for 192.168.2.9 on wlan0.IPv4.
Jun 26 14:37:51 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:51 merkaba avahi-dnsconfd[2614]: New DNS Server 192.168.2.9 (interface: 3.IPv4)
Jun 26 14:37:51 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:37:56 merkaba dnsmasq[2879]: reading /var/run/dnsmasq/resolv.conf
Jun 26 14:37:56 merkaba dnsmasq[2879]: using nameserver 192.168.2.1#53
Jun 26 14:37:56 merkaba dnsmasq[2879]: using nameserver 192.168.33.1#53
Jun 26 14:37:56 merkaba dnsmasq[2879]: using nameserver 192.168.2.9#53
Jun 26 14:37:56 merkaba dnsmasq[2487]: reading /etc/resolv.conf
Jun 26 14:37:56 merkaba dnsmasq[2487]: using nameserver 127.0.0.1#53
Jun 26 14:37:59 merkaba ntpdate[23035]: step time server 192.53.103.108 offset -5.905022 sec
Jun 26 14:38:07 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:38:07 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:38:07 merkaba dhclient: All rights reserved.
Jun 26 14:38:07 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:38:07 merkaba dhclient:
Jun 26 14:38:07 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:07 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:07 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:38:07 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:38:07 merkaba dnsmasq[2879]: reading /var/run/dnsmasq/resolv.conf
Jun 26 14:38:07 merkaba dnsmasq[2879]: using nameserver 192.168.2.9#53
Jun 26 14:38:07 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:07 merkaba avahi-daemon[2309]: Withdrawing address record for 192.168.2.9 on wlan0.
Jun 26 14:38:07 merkaba avahi-daemon[2309]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.9.
Jun 26 14:38:07 merkaba dnsmasq[2487]: reading /etc/resolv.conf
Jun 26 14:38:07 merkaba dnsmasq[2487]: using nameserver 127.0.0.1#53
Jun 26 14:38:07 merkaba avahi-daemon[2309]: Interface wlan0.IPv4 no longer relevant for mDNS.
Jun 26 14:38:07 merkaba avahi-dnsconfd[2614]: DNS Server 192.168.2.9 removed (interface: 3.IPv4)
Jun 26 14:38:07 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:07 merkaba kernel: [ 4549.200483] wlan0: deauthenticating from 00:1a:4f:02:ad:91 by local choice (reason=3)
Jun 26 14:38:07 merkaba kernel: [ 4549.225316] cfg80211: Calling CRDA to update world regulatory domain
Jun 26 14:38:07 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:38:07 merkaba kernel: [ 4549.243513] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:38:07 merkaba kernel: [ 4549.250263] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:38:08 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:38:08 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:38:08 merkaba dhclient: All rights reserved.
Jun 26 14:38:08 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:38:08 merkaba dhclient:
Jun 26 14:38:08 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:38:08 merkaba dhclient: Listening on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:38:08 merkaba dhclient: Sending on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:38:08 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:38:08 merkaba dhclient: DHCPRELEASE on eth0 to 192.168.2.1 port 67
Jun 26 14:38:08 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:38:08 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:38:08 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:08 merkaba kernel: [ 4549.874195] r8169 0000:04:00.2: eth0: link down
Jun 26 14:38:08 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:38:08 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:38:08 merkaba dhclient: All rights reserved.
Jun 26 14:38:08 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:38:08 merkaba dhclient:
Jun 26 14:38:08 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:38:08 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:38:08 merkaba dhclient: All rights reserved.
Jun 26 14:38:08 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:38:08 merkaba dhclient:
Jun 26 14:38:08 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:08 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:08 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:38:08 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:08 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:08 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:38:08 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:38:08 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:38:08 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:38:08 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:38:08 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:38:08 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:38:08 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:08 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:08 merkaba kernel: [ 4550.044384] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:38:08 merkaba kernel: [ 4550.051119] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:38:08 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:38:08 merkaba kernel: [ 4550.183138] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:38:08 merkaba kernel: [ 4550.189877] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:38:09 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:38:09 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:38:09 merkaba dhclient: All rights reserved.
Jun 26 14:38:09 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:38:09 merkaba dhclient:
Jun 26 14:38:09 merkaba dhclient: Listening on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:38:09 merkaba dhclient: Sending on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:38:09 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:38:09 merkaba dhclient: DHCPRELEASE on eth0 to 192.168.2.1 port 67
Jun 26 14:38:09 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:38:09 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:38:09 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:09 merkaba kernel: [ 4550.563153] r8169 0000:04:00.2: eth0: link down
Jun 26 14:38:09 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:38:09 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:38:09 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:38:09 merkaba dhclient: All rights reserved.
Jun 26 14:38:09 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:38:09 merkaba dhclient:
Jun 26 14:38:09 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:09 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:09 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:38:09 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:38:09 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:38:09 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:38:09 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:09 merkaba kernel: [ 4550.748910] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:38:09 merkaba kernel: [ 4550.755655] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:38:11 merkaba kernel: [ 4552.436606] wlan0: authenticate with 00:04:0e:da:1e:70
Jun 26 14:38:11 merkaba kernel: [ 4552.438665] wlan0: send auth to 00:04:0e:da:1e:70 (try 1/3)
Jun 26 14:38:11 merkaba kernel: [ 4552.442162] wlan0: authenticated
Jun 26 14:38:11 merkaba kernel: [ 4552.442710] wlan0: associate with 00:04:0e:da:1e:70 (try 1/3)
Jun 26 14:38:11 merkaba kernel: [ 4552.446522] wlan0: RX AssocResp from 00:04:0e:da:1e:70 (capab=0x411 status=0 aid=1)
Jun 26 14:38:11 merkaba kernel: [ 4552.446530] wlan0: associated
Jun 26 14:38:11 merkaba kernel: [ 4552.910437] wlan0: deauthenticating from 00:04:0e:da:1e:70 by local choice (reason=3)
Jun 26 14:38:11 merkaba kernel: [ 4552.921496] cfg80211: Calling CRDA to update world regulatory domain
Jun 26 14:38:12 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:38:50 merkaba kernel: [ 4591.304345] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:38:50 merkaba kernel: [ 4591.311061] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:38:50 merkaba kernel: [ 4591.456170] wlan0: authenticate with 00:04:0e:da:1e:70
Jun 26 14:38:50 merkaba kernel: [ 4591.458251] wlan0: send auth to 00:04:0e:da:1e:70 (try 1/3)
Jun 26 14:38:50 merkaba kernel: [ 4591.459959] wlan0: authenticated
Jun 26 14:38:50 merkaba kernel: [ 4591.460639] wlan0: associate with 00:04:0e:da:1e:70 (try 1/3)
Jun 26 14:38:50 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:38:50 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:38:50 merkaba dhclient: All rights reserved.
Jun 26 14:38:50 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:38:50 merkaba dhclient:
Jun 26 14:38:50 merkaba kernel: [ 4591.464065] wlan0: RX AssocResp from 00:04:0e:da:1e:70 (capab=0x411 status=0 aid=1)
Jun 26 14:38:50 merkaba kernel: [ 4591.464073] wlan0: associated
Jun 26 14:38:50 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:50 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:50 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:38:50 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:38:50 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:38:50 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:38:50 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:50 merkaba kernel: [ 4591.545573] wlan0: deauthenticating from 00:04:0e:da:1e:70 by local choice (reason=3)
Jun 26 14:38:50 merkaba kernel: [ 4591.556982] cfg80211: Calling CRDA to update world regulatory domain
Jun 26 14:38:50 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:38:50 merkaba kernel: [ 4591.574364] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:38:50 merkaba kernel: [ 4591.581081] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:38:50 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:38:50 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:38:50 merkaba dhclient: All rights reserved.
Jun 26 14:38:50 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:38:50 merkaba dhclient:
Jun 26 14:38:50 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:38:50 merkaba dhclient: Listening on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:38:50 merkaba dhclient: Sending on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:38:50 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:38:50 merkaba dhclient: DHCPRELEASE on eth0 to 192.168.2.1 port 67
Jun 26 14:38:50 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:38:50 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:38:50 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:50 merkaba kernel: [ 4592.237098] r8169 0000:04:00.2: eth0: link down
Jun 26 14:38:55 merkaba kernel: [ 4596.298711] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:38:55 merkaba kernel: [ 4596.305438] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:38:58 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:38:58 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:38:58 merkaba dhclient: All rights reserved.
Jun 26 14:38:58 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:38:58 merkaba dhclient:
Jun 26 14:38:58 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:58 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:58 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:38:58 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:38:58 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:38:58 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:38:58 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:58 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:38:58 merkaba kernel: [ 4599.855159] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:38:58 merkaba kernel: [ 4599.861911] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:38:58 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:38:58 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:38:58 merkaba dhclient: All rights reserved.
Jun 26 14:38:58 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:38:58 merkaba dhclient:
Jun 26 14:38:58 merkaba dhclient: Listening on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:38:58 merkaba dhclient: Sending on LPF/eth0/00:90:f5:d0:62:b1
Jun 26 14:38:58 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:38:58 merkaba dhclient: DHCPRELEASE on eth0 to 192.168.2.1 port 67
Jun 26 14:38:58 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:38:58 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:38:58 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:58 merkaba kernel: [ 4600.149302] r8169 0000:04:00.2: eth0: link down
Jun 26 14:38:58 merkaba dhclient: receive_packet failed on wlan0: Network is down
Jun 26 14:38:58 merkaba dhclient: Internet Systems Consortium DHCP Client 4.2.2
Jun 26 14:38:58 merkaba dhclient: Copyright 2004-2011 Internet Systems Consortium.
Jun 26 14:38:58 merkaba dhclient: All rights reserved.
Jun 26 14:38:58 merkaba dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 26 14:38:58 merkaba dhclient:
Jun 26 14:38:58 merkaba dhclient: Listening on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:58 merkaba dhclient: Sending on LPF/wlan0/88:53:2e:b4:9a:60
Jun 26 14:38:58 merkaba dhclient: Sending on Socket/fallback
Jun 26 14:38:59 merkaba dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
Jun 26 14:38:59 merkaba dhclient: send_packet: Network is unreachable
Jun 26 14:38:59 merkaba dhclient: send_packet: please consult README file regarding broadcast address.
Jun 26 14:38:59 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:38:59 merkaba kernel: [ 4600.329976] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
Jun 26 14:38:59 merkaba kernel: [ 4600.336707] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Jun 26 14:39:01 merkaba kernel: [ 4602.580036] wlan0: authenticate with 00:04:0e:da:1e:70
Jun 26 14:39:01 merkaba kernel: [ 4602.582238] wlan0: send auth to 00:04:0e:da:1e:70 (try 1/3)
Jun 26 14:39:01 merkaba kernel: [ 4602.584023] wlan0: authenticated
Jun 26 14:39:01 merkaba kernel: [ 4602.585070] wlan0: associate with 00:04:0e:da:1e:70 (try 1/3)
Jun 26 14:39:01 merkaba kernel: [ 4602.588487] wlan0: RX AssocResp from 00:04:0e:da:1e:70 (capab=0x411 status=0 aid=1)
Jun 26 14:39:01 merkaba kernel: [ 4602.588493] wlan0: associated
Jun 26 14:39:02 merkaba avahi-daemon[2309]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.9.
Jun 26 14:39:02 merkaba avahi-daemon[2309]: New relevant interface wlan0.IPv4 for mDNS.
Jun 26 14:39:02 merkaba avahi-daemon[2309]: Registering new address record for 192.168.2.9 on wlan0.IPv4.
Jun 26 14:39:02 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:39:03 merkaba avahi-dnsconfd[2614]: New DNS Server 192.168.2.9 (interface: 3.IPv4)
Jun 26 14:39:03 merkaba dnsmasq[2879]: read /etc/hosts - 34 addresses
Jun 26 14:39:04 merkaba dnsmasq[2879]: reading /var/run/dnsmasq/resolv.conf
Jun 26 14:39:04 merkaba dnsmasq[2879]: using nameserver 192.168.33.1#53
Jun 26 14:39:04 merkaba dnsmasq[2879]: using nameserver 192.168.2.1#53
Jun 26 14:39:04 merkaba dnsmasq[2879]: using nameserver 192.168.2.9#53
Jun 26 14:39:04 merkaba dnsmasq[2487]: reading /etc/resolv.conf
Jun 26 14:39:04 merkaba dnsmasq[2487]: using nameserver 127.0.0.1#53
Jun 26 14:39:15 merkaba ntpdate[24238]: adjust time server 131.188.3.220 offset -0.003779 sec
Jun 26 14:39:37 merkaba kernel: [ 4638.969041] process `skype' is using obsolete setsockopt SO_BSDCOMPAT
Jun 26 15:14:23 merkaba pulseaudio[21044]: [alsa-sink] alsa-sink.c: ALSA weckte uns auf, um neue Daten auf das Gerät zu
schreiben, doch es gab nichts zum Schreiben!


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201207011349.32089.chymian@gmx.net">http://lists.debian.org/201207011349.32089.chymian@gmx.net
 
Old 07-01-2012, 01:39 PM
Kevin Krammer
 
Default plasma desktop hangs

On Sunday, 2012-07-01, chymian wrote:
> hi everybody,
>
> since a while now (at least a year), KDE does have the following behavior:
>
> while the WLAN-connection is stable, every thing is good.
> moving my laptop (i.e. to the terrasse) where it often still has a 50%
> signal, the pbls. begin:
>
> while it rechecks/reconnect to the wlan, plasma hangs (menues, systray, etc
> all frozen, kwin still is responsable, can move windows) for a minute or
> 2! that happens on movment and also, while I don't move the box - just out
> of the sky on rechecking the connection.
>
> first, I used Network-Manager + plasmoid, which often was not able to
> reconnect. I had to manual stop the manager, sometimes reload the module &
> restart the manager, then wait till KDE realises, that there is network
> again. after it had lost the connection once, it's keeping me asking over
> and over for the WLAN-secret, which was already in kwallet and too often,
> the only way out was to complety remove the connection and configure it
> new.
>
> then I moved to WICD, (for the price of loosing my comfortable VPN's
> setup). WICD is ****MUCH**** more stable, never asks for the password but
> still hangs plasma now and then. but seems to be 80% more stable.
>
>
> since I swapped hardware 4 weeks ago, it dosen't look like a
> driver/module-pbl. to me. (b43 before, iwlwifi now). I also see this on
> some laptops of friends, all KDE 4.4 - 4.8, wheezy. and I checked it with
> three different WLAN-routers - all same behavior.

Maybe it is a certain applet that triggers this behavior, e.g. something that
gets data from a web service?

I've never had any problem with dropping network connections, neither WLAN nor
mobile broadband (where this happens a lot more often, e.g. when on a train).

Cheers,
Kevin
 
Old 07-01-2012, 02:48 PM
chymian
 
Default plasma desktop hangs

Hi again,

*

Am So, 1. Juli 2012, 15:39:43 schrieb Kevin Krammer:

> On Sunday, 2012-07-01, chymian wrote:

> > hi everybody,

> >

*

it seems to be, as kevin wrote:



> Maybe it is a certain applet that triggers this behavior, e.g. something

> that gets data from a web service?

*

I found the following appear every 5 min in my .xsession-errors

Failed to get chart. <urlopen error timed out>Updating...

Failed to get chart. <urlopen error timed out>Updating...

Failed to get chart. <urlopen error timed out>Updating...

Failed to get chart. <urlopen error timed out>Updating...

Failed to get chart. <urlopen error timed out>Updating...

Failed to get chart. <urlopen error timed out>Updating...

Failed to get chart. <urlopen error timed out>Updating...

Failed to get chart. <urlopen error timed out>Updating...

Failed to get chart. <urlopen error timed out>Updating...

Failed to get chart. <urlopen error timed out>Updating...

Failed to get chart. <urlopen error timed out>Updating...

Failed to get chart. <urlopen error timed out>Updating...

*

which could come from my SOHO-plasmoids.

and is EXACT the time, when the desktop freezes for 3 minutes.

*

BUT: the point here:

*

>> plasma should definitly NOT freeze on a lost network connection.

*

or even, if a plasmoid can't update it's content!

*

> I've never had any problem with dropping network connections, neither WLAN

> nor mobile broadband (where this happens a lot more often, e.g. when on a

> train).

*

so, what's the difference?

mine freezes every 5 min because of a couple of plasmoids cannot update it's self, even when I have a network-connection.

aka. on a web-server-pbl. they connect to?

*

*

>

> Cheers,

> Kevin

*

cheers

günter
 
Old 07-01-2012, 05:17 PM
Marco Valli
 
Default plasma desktop hangs

In data domenica 1 luglio 2012 13:49:31, chymian ha scritto:
> any hint's, how to prevent KDE from freezing?

Package ifupdown is installed?

--
Marco Valli


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201207011917.42484.marco@bastardi.net">http://lists.debian.org/201207011917.42484.marco@bastardi.net
 
Old 07-01-2012, 10:44 PM
Mirosław Zalewski
 
Default plasma desktop hangs

On 01/07/2012 at 16:48, chymian <chymian@gmx.net> wrote:

> BUT: the point here:
> >> plasma should definitly NOT freeze on a lost network connection.
>
> or even, if a plasmoid can't update it's content!

This is probably caused by plasma design - i.e. all plasmoids run under single
process. So, if one plasmoid tries to connect, it virtually hangs whole
desktop for that time.

This issue was discussed some time ago on planet KDE, but I can't find that
post right now.

I have found that brainstorm discussion from few years back:
http://forum.kde.org/viewtopic.php?f=90&t=45255
It seems that rationale was: plasmoid crash causes whole desktop to crash, so
we should run them in separate processes. But plasmoids don't crash that often
now, so we do not have to run them in separate processes.

Your case shows that there is still pretty strong reason to run plasmoids in
separate processes (if only my suppositions are right). You should definitely
post your findings in KDE forums - either in linked thread, or in new thread
(which may get more attention).

But you should not post a bug report to Debian's BTS - there is really not
much that Debian's KDE packaging team can do about it.

As for corrupted configplasma-desktop-appletsrc file - it would be nice if you
could provide step-by-step instructions how to reproduce that. I will check on
Arch Linux with KDE to ensure that this is Debian issue. As KDE packaging team
recently said on that mailing list, they prefer that KDE bugs goes directly to
KDE, not Debian BTS. Debian BTS is appropriate for packaging issues and things
that do not happen outside Debian.
--
Best regards
Mirosław Zalewski


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201207020044.40863.miniopl@poczta.onet.pl">http://lists.debian.org/201207020044.40863.miniopl@poczta.onet.pl
 
Old 07-02-2012, 03:20 PM
chymian
 
Default plasma desktop hangs

hi miro,
thx for answering.

Am Mo, 2. Juli 2012, 00:44:40 schrieb Mirosław Zalewski:
> On 01/07/2012 at 16:48, chymian <chymian@gmx.net> wrote:
> > BUT: the point here:
> > >> plasma should definitly NOT freeze on a lost network connection.
> >
> > or even, if a plasmoid can't update it's content!
>
> This is probably caused by plasma design - i.e. all plasmoids run under
> single process. So, if one plasmoid tries to connect, it virtually hangs
> whole desktop for that time.
>
> This issue was discussed some time ago on planet KDE, but I can't find that
> post right now.
>
> I have found that brainstorm discussion from few years back:
> http://forum.kde.org/viewtopic.php?f=90&t=45255
> It seems that rationale was: plasmoid crash causes whole desktop to crash,
> so we should run them in separate processes. But plasmoids don't crash
> that often now, so we do not have to run them in separate processes.
>
> Your case shows that there is still pretty strong reason to run plasmoids
> in separate processes (if only my suppositions are right). You should
> definitely post your findings in KDE forums - either in linked thread, or
> in new thread (which may get more attention).

at the end of the long, dark valley, there is a house - made of paper - and it's starting to rain.

>
> But you should not post a bug report to Debian's BTS - there is really not
> much that Debian's KDE packaging team can do about it.

That's what I thought and why I'm asking.

>
> As for corrupted configplasma-desktop-appletsrc file - it would be nice if
> you could provide step-by-step instructions how to reproduce that. I will
> check on Arch Linux with KDE to ensure that this is Debian issue. As KDE
> packaging team recently said on that mailing list, they prefer that KDE
> bugs goes directly to KDE, not Debian BTS. Debian BTS is appropriate for
> packaging issues and things that do not happen outside Debian.


I followed your advice and opened up a new thread:

http://forum.kde.org/viewtopic.php?f=67&t=106640

as you can read there as well, I don't now how to reproduce, other then doing the normal updates, which did scramble the
desktop a couple of times in the last half year.
there had been other people on the list, reporting that. (don't find the mails at the moment)

for me, I start over with a empty .kde in the next days - again
and will monitor more closely on the config files.
if i find a misbehavior again, smashed config-files, etc. I will report.


have a nice day.
günter


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201207021720.28077.chymian@gmx.net">http://lists.debian.org/201207021720.28077.chymian@gmx.net
 
Old 07-06-2012, 08:02 AM
David Jarvie
 
Default plasma desktop hangs

On Monday 02 July 2012 16:20:27 chymian wrote:
> I followed your advice and opened up a new thread:
>
> http://forum.kde.org/viewtopic.php?f=67&t=106640

Just a word of warning - many KDE developers do not read forums. Unless you know that the forum you posted to is read by developers, you should raise issues either on the appropriate KDE mailing list (see http://lists.kde.org) or if it's a bug, at https://bugs.kde.org.

--
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201207060902.17316.djarvie@kde.org">http://lists.debian.org/201207060902.17316.djarvie@kde.org
 
Old 07-06-2012, 08:16 AM
Kevin Krammer
 
Default plasma desktop hangs

On Monday, 2012-07-02, Mirosław Zalewski wrote:

> I have found that brainstorm discussion from few years back:
> http://forum.kde.org/viewtopic.php?f=90&t=45255
> It seems that rationale was: plasmoid crash causes whole desktop to crash,
> so we should run them in separate processes. But plasmoids don't crash
> that often now, so we do not have to run them in separate processes.

The main decision factor is that at least X11, which is currently the main
target for Free Software desktop shells, does not offer suitable mechanisms of
merging multiprozess drawings, especially if the "container" needs to be able
to manipulate the "child" drawings in some way (e.g. control geometry or
orientation).

I don't know enough about Wayland but this might become viable at that point.

> Your case shows that there is still pretty strong reason to run plasmoids
> in separate processes (if only my suppositions are right). You should
> definitely post your findings in KDE forums - either in linked thread, or
> in new thread (which may get more attention).

One thing that is not touched at all by the limitation regarding visualization
is data processing. Applets are not restricted in any way to either use event
based asynchronous processing, thread based processing or out-of-process
processing.

> But you should not post a bug report to Debian's BTS - there is really not
> much that Debian's KDE packaging team can do about it.

Indeed.

As I wrote in my other reply, make sure to report the freeze issue against the
applet causing it, it's developers needs to learn that just like with
applications networking must not be done in a way that blocks UI.

Cheers,
Kevin
 

Thread Tools




All times are GMT. The time now is 11:40 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org