DietPi-Software | TigerVNC/RealVNC: Connection fails immediately (coredump) on Buster #3070
Comments
|
As a site-note I've set the following hdmi flags in /Dietpi/config.xt: hdmi_group=2 This is a requirement to simulate an HDMI signal from a monitor as per various articles on the raspberrypi forums. |
|
I have just been into this one using realvnc, even though I did not get the same error messages. |
|
@Trunkzeh Did you set
If you did not set Since it should be less conflicting in general, please try it with virtual desktop mode first, thus: For general debugging on service level: With RealVNC additionally: @olem10 I probably find time to run some tests with RealVNC. Possibly this has simply changed a bid with Buster, so our implementation requires an update. Most likely I will then separate the install scripts, so our own service is for TigerVNC only, while we use+configure RealVNC native services separately.
This indeed looks like a doubled/conflicting VNC session on display 1 (default for virtual desktop mode). |
|
No I hadnt changed any settings on Dietpi.txt; I checked the SOFTWARE_VNCSERVER_SHARE_DESKTOP string nonetheless and it is set to 0. I've removed RealVNC; rebooted; installed TigerVNC; rebooted and then removed the two hdmi strings in config.txt and rebooted one last time: This was initially setup as a headless machine (via the AUTO_SETUP_HEADLESS string on dietpi.txt) and there is no HDMI cable plugged in either. Current dietpi.txt settings: SOFTWARE_VNCSERVER_WIDTH=1280 |
|
I am running some test currently. TigerVNC on RPi2. VNC connection from client fails immediately:
Will try tomorrow after setting up display and local desktop. |
|
@MichaIng And I thought I was going mad.. thanks :-) I'll continue fettling with it today to see if I can get it working. I've moved the branch on it to 'dev' so if you push any changes to that branch I can test. |
|
Log from ~/.vnc/xstartup: Out of curiosity; whats the default vnc password on a fresh VNC server install? I assume its dietpi? I ran vncpasswd (and set it to dietpi) and rebooted and still the same issue. |
|
Fixed the bloody problem. Issue is reported TigerVNC/tigervnc#800 and TigerVNC/tigervnc#812; workaround is to ensure vncpasswd sets the readonly password as well as a full-control password. Current behavior is only full-control. |
MichaIng
added
External bug 🐞
|
@Trunkzeh The issues you linked mention some required code change. Also the linked Debian bug report it looks like some code change in the mentioned library is required. Discussion there ended in April 🤔. |
MichaIng
changed the title
|
@MichaIng Running vncpasswd interactively will first ask you to set the full-control password; it will then ask if you want to set a read-only password as well (select Y) then enter and confirm the read-only pass. |
|
An idea to automate the workaround is set both full-control and view-only passwords as part of the TightVNC install. I looked at the tightvnc man pages and noticed you can use the -f flag to specify via stdin. So for example if we chose dietpi as full-control and viewonly as view-only: echo -ne "dietpi\viewonly" | vncpasswd -f > ~/.vnc/passwd |
+ DietPi-Software | Fix wrong shown pre-req software name being installed, when desktop is auto-selected. $software_id is set to SQLite before, which is shown instead of correct LXDE. + DietPi-Software | TigerVNC: Install the netbase package, which is required to solve a failing perl function due to missing dependency. + DietPi-Software | TigerVNC: Resolve "No session for PID <lxpolkit_pid>" error message on login. This is due to "PAMName=login" being ignored in systemd unit as long as "User=" is not set. Setting it to "root" resolves the issue, even that it is the default value. + DietPi-Software | TigerVNC: Specify desktop environment for LXDE explicitly, to avoid message about fallback to default: "DE is (null); No desktop environnement set, fallback to LXDE" + DietPi-Software | TigerVNC: Set read-only password as well, otherwise the connection fails immediately (coredump): #3070 + DietPi-Software | Minor coding
|
@Trunkzeh Many thanks for finding the workaround, the Lol forgot, that it is a Buster-only issue... However does not hurt to apply on Stretch as well. Keep it simple... |
+ DietPi-Software | Fix wrong shown pre-req software name being installed, when desktop is auto-selected. $software_id is set to "SQLite" before, which is shown instead of correct "LXDE". + DietPi-Software | TigerVNC: Install the netbase package, which is required to solve a failing perl function due to missing dependency: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939055 + DietPi-Software | TigerVNC: Resolve "'No session for PID <lxpolkit_pid>'" error message on login. This is due to 'PAMName=login' being ignored in systemd units as long as 'User=' is not set. Setting it to "root" solves the issue, even that it is the default value. + DietPi-Software | TigerVNC: Specify desktop environment for LXDE explicitly, to avoid message about fallback to default: "'DE is (null); No desktop environnement set, fallback to LXDE'" + DietPi-Software | TigerVNC: Set read-only password as well, otherwise the connection fails immediately (coredump): #3070 + DietPi-Software | Minor coding
|
@MichaIng Perfect. I'll do a fresh install tonight and feedback. |
|
@Trunkzeh |
|
@MichaIng: Worked like a charm. Couple of things to note:
|
|
@Trunkzeh
Jep, that is an outstanding task. I plan to implement a desktop preference system like it exists for webservers. So you select a preferred desktop within
We will most likely not gonna offer some custom install paths for desktops. The configuration and maintenance effort is simply too high. But no harm to have a HowTo available for users which want to switch/test.
This is since VNC servers are not controlled by DietPi-Services, so they are not started after installs have finished. This is required since, e.g. if you run installs from within a VNC session, dietpi-services would kill your session and itself by this 😉. Those services (like SSH and all network related services as well) are |
|
@MichaIng The separate ticket was just to see what work would be required for DietPi to use the latest XFCE release; which could then maybe be merged into a PR. I initially thought the .14 release would stay in debian sid for awhile but if its in bullseye then it should trickle down into buster-backports. Removing LXDE and installing another desktop environment works. However the VNC server is inaccessible; i suspect this is due to the .vncsession file points to the old desktop environment? In any case; doing dietpi-software reinstall 28 does the trick. My RPI4 is now hovering around the 62c mark so will switch to XFCE4 next and see how that gets on :-) |
Ah yeah that's true, not the ... Hmm actually |
|
I thought so :-) Found some builds for Raspbian 10 and XFCE 4.14; for those that want to experiment with the new builds: Pre-requisite: XFCE 4.12 already installed on your system Builds are from an openSUSE maintainer; and there are now armhf debs so works on our Pi platform. This is untested so please make sure you backup before you make any changes :) |
|
@MichaIng The original reported issue has been fixed by your PR. Should I close this issue or leave it open for if/when the desktop preference system is implemented? |
|
@Trunkzeh Self reminder: Start vncserver after it has been installed => General approach: Collect non-controlled service name during installs, start those explicitly before exit, since |
Creating a bug report/issue
Required Information
G_DIETPI_VERSION_SUB=25
G_DIETPI_VERSION_RC=3
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
Additional Information (if applicable)
Steps to reproduce
Expected behaviour
Actual behaviour
Extra details
The text was updated successfully, but these errors were encountered: