Stefan, I am so sorry about that.
I have windows laptop where I run putty and vcxsrv and honestly dolphin and e.g. xclock has been working but does not work anymore
A very basic X program like xterm or xclock is a much easier test; it takes much more complex things like the Qt platform plugins (xcb vs. Wayland) out of the equation.
Still the question is on which side the problem lies: On your Tumbleweed machine where the program is running or on your Windows machine where you want it to be displayed. If you have another machine to connect to, it would be helpful to try starting an xterm or xclock from there as well to isolate the problem.
@nikkej why not solve the issue by using Cockpit and the built in browser?
If you use the flatpak version, there is no supporting tools required on the remote systemâŚ
Wasnât the original problem that Dolphin wouldnât run anymore?
(Running on TW and displayed on the remote Windows machine, as we now know.)
Ahh, my bad, perhaps the web ui version, which would mean installing the Cockpit pattern on the remote Tumbleweed setupâŚ
@nikkej Thinking some more (coffee helpsâŚ) why not just install winscp?
Thanks Malcolm, that is something I must lean and consider.
For some reason âEnable X11 forwardâ checkbox were unchecked in PuTTYâs settings altough it has been for sure previously checkeed.
OK. Lesson learned: Donât trust those Qt messages about missing shared libs and reinstalling the application - they are completely bogus and will only lead you down the wrong path.
Thatâs why I suppress them in QDirStat and in Myrlyn.
Yes, you are right Stefan. Now that also dolphin start there are not even single line warning about missing libraries
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.