Red Hat Bugzilla – Bug 176393
kcontrol network settings does not recognize FC4
Last modified: 2007-11-30 17:11:19 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc4 Firefox/1.0.7 Description of problem: Start kcontrol, go to "Internet & Network", select "Network Settings". The message: "Your Platform is Not Supported You may choose one of the following supported platforms..." Fedora Core 1, 2 and 3 are listed. FC4 is not. Version-Release number of selected component (if applicable): kdebase-3.5.0-0.1.fc4 How reproducible: Always Steps to Reproduce: 1.Start kcontrol 2.Select "Internet & Network" 3.Select "Network Settings" Actual Results: A message with selection list appears. Message reads: "Your Platform is Not Supported You may choose one of the following supported platforms if you are sure your platform behaves the same as the chosen one. Please be sure, because your current network configuration could be damaged." Expected Results: The network configuration section should have come up. Additional info: This is on a fully updated FC4 system, including the arts-1.5.0-0.2.fc4 and kdelibs-3.5.0-0.2.fc4 updates, though it happened with the KDE 3.5 update before those as well (the two updates mentioned to establish update level, not to suggest arts has anything to do with it).
This kcontrol module is actually part of kdeadmin. Grant, could you change the Component field? FC4 is present upstream and will appear on the list as of KDE 3.5.1, which is due for release around Jan. 20, 2006.
coming from #176630, Ive even searched in 2 different kdebase, but i don't even get "Network Settings". Which can be read here http://clunixchit.blogspot.com/2006/01/fc4-kde-35-platform-not-supported-part.html but someone in the "my" comments reported(who has one of my 2 different kdebase) that he has the "Network Settings".
Sorry about the component field mix up, I found which RPM kcontrol was in and used that. I promise to do better if I find something else to report in the future. :-}
*** Bug 176630 has been marked as a duplicate of this bug. ***
Fixed with 3.5.1 update, no longer an issue.