KDE programs - KDE Konsole

[ghost]

Hi guys,

Could you have a look whether KDE konsole works?

If so, could you make a mention?

I played around but without LoWe so far and I have had troubles getting kde konsole to work, in particular I cuold not type anything (I was using xming though; that is why I would like to know whether it works on LoWe, then I could try it).

Thanks!

[kpocza]

Hi shevegen,

I took a look at whether KDE konsole works or not under LoWe. From icewm by the way but anyway I experienced the same, I couldn't type. Though it has shown an error message at startup, please see image:

In the recent days/weeks I'll examine the problem in details and get back with the results.

[kpocza]

Hi @shevegen,

I've examined the KDE konsole typing issue, however without proper solution. I've compared the strace -f output of konsole on "UoW supported by LoWe" and on a Ubuntu box and found that there are many-many failing and not completely implemented syscalls on UoW. This is of course not a big surprise. I'd suggest you to wait for the next W10+WSL upgrade. I'll definitely try konsole on it.

[kpocza]

@shevegen I've upgrade to W10 Fall Creators Update and rechecked Konsole. I was able to type, open new tabs, etc. It seems to be functioning. Please recheck it.

[WSLUser]

@kpocza using LoWe to utilize Konsole or no? Also, have you tried using it within the Plasma desktop environment or a separate X window?

[kpocza]

@ntklotz I've used LoWe. It wasn't Plasma desktop env for sure, maybe Unity, wmaker or icewm.

[WSLUser]

@kpocza Have you tried it on 17.10 Artful?

Was it successful on Unity, xfce, etc.? Are you able to test KDE Plasma? Before using this, I'm wanting to see where the limitations are, especially as there are specific bugs in WSL that are related to 17.10 (fixes for those bugs are being released in one of the next few Insider builds but do me no good as I don't run an Insider build and don't plan to either.)

[kpocza]

@ntklotz I've tried it on 16.04 .

It was successful on Unity, wmaker, icewm, xfce and KDE Plasma.

What I can say is that heavyweight desktop environments like Unity and KDE Plasma (especially Unity) are quite slow but their lightweight counterparts are well usable. The background processes of heavyweight solutions are sometimes dying but the desktop still remains responsive (I think these situations are gracefully recovered).

(I'm always using the latest stable and recommended W10 OS and Ubuntu on WSL, so don't even try Insider builds and non-LTS Ubuntu.)

[WSLUser]

Cool! As I stated in my previous comment, I only run the officially released version of Win10, FCU at this point. However I do have non-LTS enabled. My specific bugs shouldn't affect this based on what your results show but considering running a Docker container within Ubuntu.exe (just because I can) with the Insider preview build inside that contains the fixes for non-LTS. Also do you know if LoWe will conflict with PulseAudio as they both affect audio?

[kpocza]

@DarthSpock Are you able to run Docker containers on WSL? Isn't it just the Docker client that can run on WSL? I have no experience running LoWe and PulseAudio together, maybe they will step on each other's toes, maybe one of them will win. But for sure if ALSA emulation is not enabled in LoWe it won't touch the specific devices. If you are running X you don't have to worry as snd devices are not supervised by LoWe according to the default loweagent.conf.

[WSLUser]

I'll be testing for the containers when I have time for it. By the way, how do you install LoWe?

[kpocza]

@DarthSpock You have to first build LoWe and then configure it. Please refer to the available project docs.

Building docs: https://github.com/kpocza/LoWe/blob/master/docs/buildrun.md

Config docs for X programs: https://github.com/kpocza/LoWe/blob/master/docs/x.md

[kpocza]

No activity since Nov. Closing.