Bug 209546 - when clicking on a wired network profile, nothing is happening
Summary: when clicking on a wired network profile, nothing is happening
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: Network Management
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-05 18:23 UTC by schmirrwurst
Modified: 2011-06-07 07:56 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screenshot applet (10.48 KB, image/png)
2009-10-05 18:24 UTC, schmirrwurst
Details
daemonLog (7.22 KB, text/plain)
2009-10-09 11:10 UTC, schmirrwurst
Details

Note You need to log in before you can comment on or make changes to this bug.
Description schmirrwurst 2009-10-05 18:23:16 UTC
Version:            (using KDE 4.3.1)
Installed from:    Ubuntu Packages

I have two wired network profiles :
- automatic : dhcp etc...
- fixed ip address

When kde is starting, the default profile is applying : dhcp; and then I try to click on the second one, nothing happens, where it was supposed to change to reconfigure the device to fixed ip....
Comment 1 schmirrwurst 2009-10-05 18:24:09 UTC
Created attachment 37384 [details]
screenshot applet
Comment 2 Will Stephenson 2009-10-07 15:48:59 UTC
Please attach the NetworkManager log (/var/log/daemon.log on buntu) from when knetworkmanager started - it should show an 'invalid' line describing what is wrong with the second fixed ip address connectin.
Comment 3 schmirrwurst 2009-10-09 11:02:26 UTC
In fact, I had a look at that log, but it seems that networkmanager is only trying to load the default config (that is ok), but didn't notice my action to change the profile...
I have also the impression that the applet is not registering my click on that profile...
Comment 4 schmirrwurst 2009-10-09 11:10:50 UTC
Created attachment 37467 [details]
daemonLog
Comment 5 Will Stephenson 2009-11-17 19:21:39 UTC
The connection is invalid because there is something wrong with an IPv4 address.  We are in the process of adding input validation to prevent these kinds of errors.

Could you attach the relevant config file from ~/.kde4/share/apps/networkmanagement/connections here too, so we can see what the error is?
Comment 6 Lamarque V. Souza 2011-03-19 04:14:16 UTC
Is this still happening?