Registered Member
|
I'm having troubles running a vncserver with KDE. The thread was originally at:
viewtopic.php?f=22&t=111264&p=266034#p266034 but by suggestion of the moderator bcooksley I moved it here. I'll appreciate any help. Daniel |
|
Ok, please first clarify the problem.
I guess it's not the initial crash in kded apparently caused by the Wacom module, but the inability to minimize/maximize (we'll exclude "close" for the moment, since that's more complex) windows through the titlebar, right? a) check that you're running kwin at all (there's "metacity --replace" and that will get you, well, "metacity", not "kwin")
b) assuming you actually run kwin, what happens if you restart kwin?
c) Does this only apply to the windows inside the VNC client, the VNC client itself or all windows in the Desktop of the host (ie. the vnc client and all other windows on that desktop) d) Which window decoration do you use and does changing it have any impact?
|
Registered Member
|
a) if I enter 'metacity --replace', and type "ps aux | grep kwin" I get:
b) then if type 'kwin --replace' then the terminal prints:
and again I cannot perform any action on ANY window, c) when I enter 'kcmshell4 kwindecoration' a window with pictures of the decorations appear, and in the terminal that I typed the command I get:
If I use the xfce4 manager, then everything works. Thanks. Daniel |
|
That seems wrong - replacing the WM should kill any kwin - how many kwin processes are there after "kwin --replace&"?
I've a suspicion here, but it's important to know which window decoration is used (the output of the command is irrelevant, but which decoration is selected?) Plese try whether your issues remain with the "oxygen" decoration (no "oxygen-air" etc.) - in doubt the "laptop" one. NOT Plastik or anything you can download from kde-look.org |
Registered Member
|
The host is running kwin, so I assume that the 'ps' is showing that one. I'm not familiar with these commands, but if I type 'metacity --replace' in the VNC instance it is not affecting what the host is doing, right?
|
|
Ok, just to get that straight:
Only the windows in the vnc instance are affected, whatever you do inside there, resp. just running vnc has no impact on the host behavior, right? In that case, please also only operate inside the vnc instance (when checking for running processes) and esp. try to alter the decoration there. If the host is unaffected (no problems there and running metacity in the host has no impact on the remote behavior either), there's no point on obtaining information about it. |
Registered Member
|
Yes, it appears that whatever I do in the VNC instance does not affect the host instance. Are you asking to check the processes inside the VNC instance only? How do I do that with the 'ps' command? (or other)
|
|
open a konsole there?
also please answer the question about the decoration - i suspect the absence of the input extension to be the cause here and the qml usage of it through the aurorae decos the issue. |
Registered Member
|
Hi,
Sorry if this has already been resolved, but I admit that I don't know the resolution ... . I have exactly the same issue - connecting via VNC (Xvnc) seems to cause KDE to crash. If I use Mate or xfce4 it works fine. What can I do to help debug this? Thanks, ... Russell |
|
Bug:
https://bugs.kde.org/show_bug.cgi?id=320459 Fix: https://git.reviewboard.kde.org/r/112623/ Workaround: add ------------- snip -------------------------------- [Windeco] UseExtendedWindowBorders=false ------------- /snip ------------------------------- to .kde[4]/share/config/oxygenrc (create it, if it doesn't exist and re-use an exisiting [Windeco] group) |
Registered Member
|
Thanks so much! Yes, this fixes the lack of window controls - much appreciated!
FYI, I still get a segmentation fault in kdeinit4 ... is this expected? And do I need to remove the workaround later, when the fix is in place? Thanks again, ... Russell |
|
Yes, crashing is a core feature of ... whaaat? No. If you encounter a reproducible crash (and a Dr. Konqui dialog) please report it (Dr. Konqui should guide you through this)
No, but you can. Once VNC has sufficient input shaping support, this will allow you to resize windows with "invisible" borders - until then it has no effect. |
Registered Member
|
Makes sense - thanks again for the help! |
Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar