12:19 a.m.
Should it be possible to run KDE plasma in a VNC session?
When I try starting it I get the dialog box...
Plasma is unable to start as it could not correctly use OpenGL2. Please check that your
graphic drivers are set up correctly.
--
You're Welcome Zachary Quinto
1:06 a.m.
Am 08.01.2017 um 07:19 schrieb Ed Greshko:
Should it be possible to run KDE plasma in a VNC session?
When I try starting it I get the dialog box...
Plasma is unable to start as it could not correctly use OpenGL2. Please check that your
graphic drivers are set up correctly
forget it - these days are sadly gone and even if you get it to work
it's unusable since version 5
hence i created a "openbox" vncserver.service to at least have some
graphical remote desktop for acting on remote machines when moving the
data over VPN is no option
1:12 a.m.
On 01/08/17 15:06, Reindl Harald wrote:
Am 08.01.2017 um 07:19 schrieb Ed Greshko:
> Should it be possible to run KDE plasma in a VNC session?
>
> When I try starting it I get the dialog box...
>
> Plasma is unable to start as it could not correctly use OpenGL2. Please check that
your
> graphic drivers are set up correctly
forget it - these days are sadly gone and even if you get it to work it's unusable
since
version 5
hence i created a "openbox" vncserver.service to at least have some graphical
remote
desktop for acting on remote machines when moving the data over VPN is no option
OK....
I was pretty sure that was going to be the answer. Just needed a bit of confirmation.
Thanks.
--
You're Welcome Zachary Quinto
8:24 a.m.
On Sat, Jan 7, 2017 at 11:06 PM, Reindl Harald <h.reindl(a)thelounge.net>
wrote:
Am 08.01.2017 um 07:19 schrieb Ed Greshko:
> Should it be possible to run KDE plasma in a VNC session?
>
> When I try starting it I get the dialog box...
>
> Plasma is unable to start as it could not correctly use OpenGL2. Please
> check that your
> graphic drivers are set up correctly
>
forget it - these days are sadly gone and even if you get it to work it's
unusable since version 5
hence i created a "openbox" vncserver.service to at least have some
graphical remote desktop for acting on remote machines when moving the data
over VPN is no option
Ed, Harald:
Not an expert on this by a long shot, but I've been using it for the last
few weeks on a daily basis since I'm away on travel and has been working
pretty good for me.
i am using TigerVNC, and didn't do anything except to add --> exec startkde
<-- to the xstartup file in the .vnc directory.
Both server and remote are radeon, not sure if that makes a difference or
not.
Now the home system is set to use OpenGL, but when I connect to it remotely
it shows that it is using XRender as the compositor. I didn't do anything
to make that
change, looks like it is done by TigerVNC somehow.
Again, I just installed and pretty much just added the "startkde"
statement..
8:39 a.m.
Gerald B. Cox ha scritto:
On Sat, Jan 7, 2017 at 11:06 PM, Reindl Harald <h.reindl(a)thelounge.net
<mailto:h.reindl@thelounge.net>> wrote:
Am 08.01.2017 um 07:19 schrieb Ed Greshko:
Should it be possible to run KDE plasma in a VNC session?
When I try starting it I get the dialog box...
Plasma is unable to start as it could not correctly use OpenGL2.
Please check that your
graphic drivers are set up correctly
forget it - these days are sadly gone and even if you get it to work it's
unusable since version 5
hence i created a "openbox" vncserver.service to at least have some
graphical remote desktop for acting on remote machines when moving the
data over VPN is no option
Ed, Harald:
Not an expert on this by a long shot, but I've been using it for the last few
weeks on a daily basis since I'm away on travel and has been working pretty
good for me.
i am using TigerVNC, and didn't do anything except to add --> exec startkde
<-- to the xstartup file in the .vnc directory.
Both server and remote are radeon, not sure if that makes a difference or not.
Now the home system is set to use OpenGL, but when I connect to it remotely it
shows that it is using XRender as the compositor. I didn't do anything to
make that
change, looks like it is done by TigerVNC somehow.
Again, I just installed and pretty much just added the "startkde" statement..
The renderer of KWin is one thing, but I think that Plasma (or better, the
QtQuick 2 that is used by Plasma) requires OpenGL by default (unless you have
the new 2D renderer with a recent version of Qt[1]).
Maybe Plasma did not start because the VM had no support for an OpenGL driver
(like LLVMPipe)?
[1] https://blog.qt.io/blog/2015/01/22/introducing-the-qt-quick-2d-renderer/
--
Luigi
8:51 a.m.
On Sun, Jan 8, 2017 at 6:39 AM, Luigi Toscano <luigi.toscano(a)tiscali.it>
wrote:
The renderer of KWin is one thing, but I think that Plasma (or
better, the
QtQuick 2 that is used by Plasma) requires OpenGL by default (unless you
have
the new 2D renderer with a recent version of Qt[1]).
Maybe Plasma did not start because the VM had no support for an OpenGL
driver
(like LLVMPipe)?
[1] https://blog.qt.io/blog/2015/01/22/introducing-the-qt-
quick-2d-renderer/
As far as installed software is concerned I'm not doing anything exotic -
just have updates-testing enabled. And as far as configuration is
concerned the only thing I've changed is the desktop theme. So if I'm using
something it's likely its the default.
5:44 p.m.
On 01/08/17 23:43, Kevin Kofler wrote:
Ed Greshko wrote:
> Plasma is unable to start as it could not correctly use OpenGL2. Please
> check that your graphic drivers are set up correctly.
export QT_XCB_FORCE_SOFTWARE_OPENGL=1
can do wonders.
And where in the process are you suggesting I place this, hopefully, magic bullet?
--
You're Welcome Zachary Quinto
11:14 p.m.
Am 09.01.2017 um 00:44 schrieb Ed Greshko:
On 01/08/17 23:43, Kevin Kofler wrote:
> Ed Greshko wrote:
>> Plasma is unable to start as it could not correctly use OpenGL2. Please
>> check that your graphic drivers are set up correctly.
> export QT_XCB_FORCE_SOFTWARE_OPENGL=1
> can do wonders.
And where in the process are you suggesting I place this, hopefully, magic bullet?
as early as possible since "export" defines ENV vars which are available
for every process started later including subshells
11:34 p.m.
On 01/09/17 13:14, Reindl Harald wrote:
Am 09.01.2017 um 00:44 schrieb Ed Greshko:
> On 01/08/17 23:43, Kevin Kofler wrote:
>> Ed Greshko wrote:
>>> Plasma is unable to start as it could not correctly use OpenGL2. Please
>>> check that your graphic drivers are set up correctly.
>> export QT_XCB_FORCE_SOFTWARE_OPENGL=1
>> can do wonders.
>
> And where in the process are you suggesting I place this, hopefully, magic bullet?
as early as possible since "export" defines ENV vars which are available for
every
process started later including subshells
Well, doing the export just prior to starting the vncserver had no effect.
--
You're Welcome Zachary Quinto
12:06 a.m.
Am 09.01.2017 um 06:34 schrieb Ed Greshko:
On 01/09/17 13:14, Reindl Harald wrote:
>
> Am 09.01.2017 um 00:44 schrieb Ed Greshko:
>> On 01/08/17 23:43, Kevin Kofler wrote:
>>> Ed Greshko wrote:
>>>> Plasma is unable to start as it could not correctly use OpenGL2. Please
>>>> check that your graphic drivers are set up correctly.
>>> export QT_XCB_FORCE_SOFTWARE_OPENGL=1
>>> can do wonders.
>>
>> And where in the process are you suggesting I place this, hopefully, magic
bullet?
>
> as early as possible since "export" defines ENV vars which are available
for every
> process started later including subshells
>
Well, doing the export just prior to starting the vncserver had no effect
show the whole start sequence
nobody knows how you start the vncserver
in case of systemd random existiting env-vars don't make it to the
service which is a good thing to have a defined and clean environment
and prevent leaking data as in the old days phpinfo() showed the IP and
port from the admin who started httpd via SSH and such horrible things
https://coreos.com/os/docs/latest/using-environment-variables-in-systemd-...
2:58 a.m.
On 01/09/17 14:06, Reindl Harald wrote:
show the whole start sequence
nobody knows how you start the vncserver
[egreshko@acer ~]$ export QT_XCB_FORCE_SOFTWARE_OPENGL=1
[egreshko@acer ~]$ vncserver -depth 24 :2
New 'acer.greshko.com:2 (egreshko)' desktop is acer.greshko.com:2
Starting applications specified in /home/egreshko/.vnc/xstartup
Log file is /home/egreshko/.vnc/acer.greshko.com:2.log
--
You're Welcome Zachary Quinto
7:35 a.m.
On Mon, Jan 9, 2017 at 12:58 AM, Ed Greshko <ed.greshko(a)greshko.com> wrote:
Starting applications specified in /home/egreshko/.vnc/xstartup
Log file is /home/egreshko/.vnc/acer.greshko.com:2.log
If it helps here is what I have in the files in my .vnc directory:
config:
## Supported server options to pass to vncserver upon invocation can be
listed
## in this file. See the following manpages for more: vncserver(1) Xvnc(1).
## Several common ones are shown below. Uncomment and modify to your
liking.
##
# securitytypes=vncauth,tlsvnc
# desktop=sandbox
# geometry=2000x1200
# localhost
# alwaysshared
geometry=800x600
xstartup:
#!/bin/sh
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
#exec /etc/X11/xinit/xinitrc
#exec startlxqt
exec startkde
passwd:
xxxxxxxxxxxxx
I then simply enter: vncserver
which starts the session
then on the remote I invoke the tigervnc client
2672
days inactive
2673
days old
12 comments
5 participants
participants (5)
-
Ed Greshko -
Gerald B. Cox -
Kevin Kofler -
Luigi Toscano -
Reindl Harald