Bug 306942

Summary: networkmanager blocking pc
Product: [Unmaintained] Network Management Reporter: dany <danyconnect>
Component: knetworkmanagerAssignee: Lamarque V. Souza <lamarque>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: 0.9   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description dany 2012-09-17 16:06:31 UTC
when i inserting wireless and lan with no internet link and force to open a site kde is blocking 

Reproducible: Always

Steps to Reproduce:
1.when my net is down 
2.open a browser a open a site
3.desktop is unavaible. only can be used to disconnect the network


Expected Results:  
all return to normal

kubuntu 12.04 and kubuntu 12.10 do the same problem
Comment 1 Lamarque V. Souza 2012-09-17 16:38:36 UTC
I do not get your steps to reproduce. If the network is already down how you can only use the desktop to disconnect the network? And why do you think Plasma NM is the one blocking your computer? It can be a plasmoid that does not work properly when disconnected.

By the way, which Plasma NM version do you use? You can see the version string by clicking on "Manage Connections" -> "Other". If you use Plasma NM below 0.9.0.4 then upgrade.
Comment 2 dany 2012-09-17 17:02:35 UTC
i used NM 0.9.0.4 and kubuntu 12.04 on asus laptop k50in

I used router or modem 3g , by the way ... steps

1. i connect to the internet by router or modem 3G and navigate ... all ok 
2. when connection is avaiable, but no link (internet) and i want to navigate then the freezing  ( meniu not working , NM NOT WORKING)
3. plug cable lan / or out usb 3g modem and all return to normal

that it tnx
Comment 3 Lamarque V. Souza 2012-09-17 17:08:42 UTC
That looks like a plasmoid blocking the Plasma Desktop. I am pretty sure Plasma NM does not do that, there must be something else. What plasmoids do you use? KTorrent is application that I have heard to cause such problems.
Comment 4 Lamarque V. Souza 2012-09-17 17:12:12 UTC

*** This bug has been marked as a duplicate of bug 299347 ***