[Bug 241307] New: KDE hangs if active network device is broken

[HLS System Design Martin Hofius]

https://bugs.kde.org/show_bug.cgi?id=241307

           Summary: KDE hangs if active network device is broken
           Product: kde
           Version: unspecified
          Platform: openSUSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: martin at hofius-online.com


Version:           unspecified (using KDE 4.3.5) 
OS:                Linux

The KDE System didn't respond to any key press or mouse click after the router
device (AVM Fritz!Box) lost its internet connection. Nevertheless I could the
mouse pointer around and non KDE programs (e.g. firefox) were responsive. I
could also switch to other linux consoles (STRG+ALT+Fn).
After stopping the network device with "ifdown eth0" everything worked again -
until restarting it with "ifup eth0".
Today I watched a similar (or the same) on a different machine (also KDE 4.3.5)
while I had to reset this router over a WLAN connection - the KDE was hanging
until networkmanager had disabled the current (and broken) WLAN connection.

In some cases the missing reactions came after some minutes...

Reproducible: Always

Steps to Reproduce:
Login to KDE 4.3.5 and start a non-KDE application (e.g. firefox)
Disconnect the active network connection without stopping the network device
first (e.g. by drawing the network cable...)
Try some mouse clicks on KDE parts

Actual Results:  
KDE parts are no more responding to the mouse clicks and key press; the non KDE
application (firefox) performs normal

Expected Results:  
All parts should respond normal clicks and key press.

The first machine wich showed this bug is equipped with a nvidia grahpics
adapter which is suspected to be involved in such a behaviour. But the second
machine mentioned above is a notebook with an old intel graphic chipset
(855GM).

I also noticed that after revoking after a suspend to RAM the screen saver and
a mouse pionter appear, but mouse clicks or key press (to show up the password
entry field) are ignored for about 30 seconds.

I declared this bug as a major because without knowing a workaround (e.g.
stopping the network device) most desktop users will not wait for several
minutes but switch off the system and therefor loose their data.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.