<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Your network issues with KDE are probably due to the change in<br>the Network Manager API, which caused all sorts of fuss.<br><br>> Date: Thu, 2 Jun 2011 02:03:57 -0700<br>> From: caf@omen.com<br>> To: test@lists.fedoraproject.org<br>> Subject: F15: KDE To the Rescue<br>> <br>> After some experimentation I was able to get KDE to work<br>> with vncserver. The trick? Put "startkde" near the beginning<br>> of xstartup in the ~/.vnc directory.<br>> <br>> It's a bit of a change from Gnome 2 but seems to work well<br>> over a VNC connection. At least I don't have to fight KDE<br>> as I did Gnome 3 and Gnome 3's brain damaged fallback.<br>> <br>> It does appear that the network config under KDE operates<br>> in a different universe from that of the Gnome version.<br>> I spent many hours getting the two ethernet ports properly<br>> set up.<br>> <br>> -- <br>> Chuck Forsberg WA7KGX N2469R caf@omen.com www.omen.com<br>> Developer of Industrial ZMODEM(Tm) for Embedded Applications<br>> Omen Technology Inc "The High Reliability Software"<br>> 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430<br>> <br>> -- <br>> test mailing list<br>> test@lists.fedoraproject.org<br>> To unsubscribe: <br>> https://admin.fedoraproject.org/mailman/listinfo/test<br> </body>
</html>