colinux-devel

[coLinux-devel] RE: Problem running KDE

[Alex <ab3...@ho...>]

I have similar problems. Often KDE stops responding, then after some =
timeout it resumes working.
Anybody have success in running KDE? Just curious is it common problem =
or something wrong in my setup?

Thank You


>>Hello,
>>
>> First I'd like to thank for a very interesting project! Keep good =
working!
>>
 >>I've tried it for some days and it look very usefull.
 >>
 >>Now to my question: I have a problem to run KDE environment. I've=20
 >>installed Cygwin X and permit host 192.168.0.40 (xhost +192.168.0.40) =

 >>which is colinux virtual machine on my Windows XP box. On colinux=20
 >>machine I've installed KDE (apt-get install kde), set DISPLAY (export =

 >>DISPLAY=3D"192.168.0.1:0") and tried to start kde (startkde). =
Starting KDE=20
 >>screen have appeared, but it has taken a VERY long time before KDE=20
 >>really started. There were also dialog boxes with messages like =
"Sound=20
 >>server fatal error: cpu overload, aborting" and "device /dev/dsp =
can't=20
 >>be opened" (the second is usual, when I don't have a rigth module in=20
 >>kernel for my sound card, I know, but I don't know yet, what to do =
with=20
 >>this in colinux).
>>=20
 >>Am I doing anything wrong? Should I kill (someway) arts daemon (or=20
 >>disable it, while starting KDE)?
>>=20
 >>Thank in advance for any help. Sorry for poor english.
>>=20
 >>Fastek

Re: [coLinux-devel] RE: Problem running KDE

[Sean B. <sea...@so...>]

SSB0aGluayB0aGF0IG9uZSBvZiB0aGUgcHJvYmxlbXMgaXMgdGhhdCBLREUgYW5kIEdub21lIGFy
ZSBub3QgZGVzaWduZWQgdG8gYmUgcnVuIG92ZXIgYSBuZXR3b3JrIGNvbm5lY3Rpb24uIFRoZXkg
YXJlIGp1c3QgdG9vIGhlYXZ5IHRvIGRvIHRoYXQgbm93IHVubGVzcyB5b3UgaGF2ZSBhIHNlcmlv
dXNseSBmYXN0IG5ldHdvcmsgcGlwZS4gVGhlaXIgdGFyZ2V0cyBhcmUgZGVza3RvcCBtYWNoaW5l
cyBhZnRlciBhbGwuIEkgdGhpbmsgdGhlIHN5bXB0b21zIGNvdWxkIGJlIHRoYXQgc2VydmljZXMg
YXJlIHNpbGVudGx5IHRpbWluZyBvdXQgYXMgdGhlIGNvZGUgaXMgbm90IGludGVuZGVkIHRvIGJl
IHJ1biBpbiB0aGlzIHdheSAodGhvdWdoIGZvdCBleGFtcGxlIHRoZSBkaWFsb2cgZm9yIGFydHMg
ZGFlbW9uIHRpbWluZyBvdXQgZXRjIGlzIGEgcmVjZW50IGltcGxlbWVudGF0aW9uIGluIGtkZSku
IA0KDQpIaXN0b3JpY2FsbHkgd2luZG93IG1hbmFnZXJzIHdlcmUgbW9zdGx5IHJ1biBvdmVyIG5l
dHdvcmsgY29ubmVjdGlvbnMgZnJvbSBYLVRlcm1pbmFscyBhbmQgdGhlcmUgYXJlIG1hbnkgb3Ro
ZXJzIHRvIGNob29zZSBmcm9tOiBmdndtMiBhbmQgRW5saWdodGVubWVudCBkbyB0aGUgam9iLiBJ
ZiB0aGUgdmlydHVhbCBuZXR3b3JrIGNhcmQgcmFuIGF0IGEgaGlnaGVyIHRocm91Z2hwdXQgKEkg
aGF2ZSBub3QgZG9uZSBhbnkgYmVuY2htYXJrcyBzbyBJIGRvbnQga25vdyB3aGF0IGl0IGlzKSB0
aGluZ3MgbWF5IGJlIGJldHRlci4gQmVpbmcgcmVhbGlzdGljIEN5Z3dpbi9YIGlzIHByZXR0eSBz
bG93IGFueXdheS4gSGF2aW5nIHRob3VnaHQgYWJvdXQgaXQgSSB3b3VsZCBub3QgZXhwZWN0IHJ1
bm5pbmcgWCBhcHBzIHJlbW90ZWx5IGZyb20gaXQgdG8gYmUgZmFzdGVyIGFzIHRoZXkgY291bGQg
b25seSBiZSBzbG93ZXIgYmVjYXVzZSBvZiB0aGUgbmV0d29yayBsaW5rLiBIb3cgYWJvdXQgY29u
ZWN0aW5nIGEgcGh5c2ljYWwgbWFjaGluZSBhbmQgZ2V0dGluZyBhIGJhc2VsaW5lPyBBbGwgaW4g
YWxsIEkgY29uc2lkZXIgdGhpcyBjYXBhYmlsaXR5IHByb3ZpZGVkIGJ5IGNvTGludXggdG8gYmUg
YSBwcm9vZiBvZiBjb25jZXB0LiANCg0KU29tZXRoaW5nIHRoYXQgSSBhbSBjdXJyZW50bHkgbG9v
a2luZyBhdCBpcyB0d2Vha2luZyBLREUgYW5kL29yIEdub21lIHNvIHRoYXQgYWxsIG9mIHRoZSBl
eWUgY2FuZHkgaXMgZGlzYWJsZWQgZXRjIHRvIGFsbGV2aWF0ZSBzb21lIGxvYWQuIFBlcmhhcHMg
dHJ5IGRpc2FibGluZyBzb3VuZCBiZWZvcmUgdGhlIHNlc3Npb24gaXMgc3RhcnRlZCBhcyBzb3Vu
ZCB3b250IHdvcmsgYW55d2F5IGFuZCB0aGlzIGlzIG9uZSBvZiB0aGUgdGhpbmdzIHRoYXQgSSBm
aW5kIG9uIGEgbmF0aXZlIExpbnV4IGJveCBpbXBhaXJzIHBlcmZvcm1hbmNlLiBUaGVyZSBhcmUg
YWxzbyBwYXRjaGVzIHRvIHRoZSBrZXJuZWwgdGhhdCBvcHRpbWl6ZSB0aGUgc2NoZWR1bGVyIGFu
ZCBzbyBvbi4gUGVyaGFwcyB0aGVzZSBjb3VsZCBiZSBhcHBsaWVkLiBObyBpZGVhLiAyLjY/IEkg
dGhpbmsgdGhhdCBJIHdpbGwgZW5kIHVwIHdhaXRpbmcgdW50aWwgYSB2aXJ0dWFsIGdyYXBoaWNz
IGNhcmQgaXMgaW1wbGVtZW50ZWQgaW4gY29MaW51eCBhcyBpbiB2bXdhcmUgKHRoZSBkaWZmcyBm
b3IgdGhlaXIgY2FyZCBhcmUgYXZhaWxhYmxlIGZvciB0aGlzIGZyb20gdGhlaXIgc2l0ZSBidHcg
YXMgaXQgaXMgb3BlbiBzb3VyY2UpLg0KDQpBbnlvbmUgaGFkIGFueSBvdGhlciBpZGVhcyBhbG9u
ZyB0aGlzIGxpbmU/DQo=

Re: [coLinux-devel] RE: Problem running KDE

[<my...@gm...>]

I actually have been running KDE remotely for over a year with no
problems. At work, I have a 1GHz Windows 2K PC with Cygwin/X11 server
connecting to a 1 GHz Linux PC over the corporate LAN (100Mbps with a fair
amount of network traffic). It is actually faster to run KDE remotely on
Linux than running it localy on Cygwin! I turned off the KDE animation
effects and sound and it words great. Although KDE is more heavyweight
that the original X apps, most modern PCs and LANs have much more capacity
than what was available in the early days of X. I would expect that KDE on
cL should be able to just work fine over a loopback connection - its just
a matter of working out all of the issues.

Larry

> I think that one of the problems is that KDE and Gnome are not designed to
> be run over a network connection. They are just too heavy to do that now
> unless you have a seriously fast network pipe. Their targets are desktop
> machines after all. I think the symptoms could be that services are
> silently timing out as the code is not intended to be run in this way
> (though fot example the dialog for arts daemon timing out etc is a recent
> implementation in kde).
>
> Historically window managers were mostly run over network connections from
> X-Terminals and there are many others to choose from: fvwm2 and
> Enlightenment do the job. If the virtual network card ran at a higher
> throughput (I have not done any benchmarks so I dont know what it is)
> things may be better. Being realistic Cygwin/X is pretty slow anyway.
> Having thought about it I would not expect running X apps remotely from it
> to be faster as they could only be slower because of the network link. How
> about conecting a physical machine and getting a baseline? All in all I
> consider this capability provided by coLinux to be a proof of concept.
>
> Something that I am currently looking at is tweaking KDE and/or Gnome so
> that all of the eye candy is disabled etc to alleviate some load. Perhaps
> try disabling sound before the session is started as sound wont work
> anyway and this is one of the things that I find on a native Linux box
> impairs performance. There are also patches to the kernel that optimize
> the scheduler and so on. Perhaps these could be applied. No idea. 2.6? I
> think that I will end up waiting until a virtual graphics card is
> implemented in coLinux as in vmware (the diffs for their card are
> available for this from their site btw as it is open source).
>
> Anyone had any other ideas along this line?
> ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÒó^¶+,¦‰ì¢·o/Ò¥çJÖ«µŠ.¬¸§»)¦ÃhÃðnŠWZ×^¦Z2jšlýg›±êï‰Ç¬~ŠËŠ{±Â+aiúÞx5C²‡íÁªÞ’+_®‰ˆÏ–'$6Œÿ†ÛiÿÿÚvÏè±Ùÿr‰¿ý§ÿ‰ßžÿjYhsøóú)rOÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿýÊŠ{±ýׯzYšŠX§‚X¬µÊŠ{±ýׯz_åŠËlþÊ.­ÇŸ¢¸þw­†Ûi³ÿÿ–+-³û(º·~Šà{ùÞ·ùb²Û?–+-ŠwèýÊ%Š{±ýׯ
>