Am 8. März 2021 23:30:11 MEZ schrieb Matthias Klein <matth...@extraklein.de>: >Am Mon, 8 Mar 2021 22:44:37 +0100 >schrieb Joachim Falk <joachim.f...@gmx.de>: > >> Hi Matthias, >> >> I tried to replicate the problem, but could start the mate desktop >> just fine. I will attache my configuration. I used > >Hi Joachim, > >Thanks a lot for your help! > >> Can you try to start something simpler to determine where exactly the >> problem is? Use something like: tigervncserver --localhost no >> --xstartup /usr/bin/xterm This should get you a VNC session running a >> simple xterm. > >The call tigervncserver --localhost no --xstartup /usr/bin/xterm >started an xterm and the MATE desktop in the background. > >After that I tried some variants in the ~/xstartup file. I got the >original content from the internet, and didn't really understand it. > >The following variant works: >unset SESSION_MANAGER >unset DBUS_SESSION_BUS_ADDRESS >/usr/bin/mate-session > >That means instead of "exec /usr/bin/mate-session &" I now use >"/usr/bin/mate-session" in the last line. > >Do you have any idea why the original call doesn't work anymore, and >what is the difference between the calls? > >Many greetings, >Matthias
In 1.11, autokill is enabled on default. If autokill is enabled, then the Xtigervnc server is killed when the xstartup script terminates. If you use "/usr/bin/mate-session &", then the xstartup script will immediately terminates because the mate desktop is started in the background, that is what the & does. Removing the & will start the mate desktop in the foreground, which means the xstartup script will only terminate after you have logged out of the desktop. -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
