I will need to see your system setup/configuration. Could you please run the following command:
dietpi-bugreport
Follow the onscreen instructions. When the text document appears, press CTRL+X to cancel (we don’t need it ). You will be given a reference CODE, please put it in your reply.
I manualy start with “vncserver” conmand.
I use android client VNC viewer, but server crushes before I even connect.
I will try tomorow to run bugreport with vncserver as autostart option. Today i run bugreport with manual login option.
I tried above but does not crashes.
When I put vncserver autostart option vnc server is not started. And then I start GUI with startx and one error appears:
“GDBus.error.org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject”
Does it have any relation with vncserver not starting?
New reference code from bugreport: 8ac2451e8073-1
Thanks for sending the updated bug report, looking into it now. It appears the vnc server is running when you sent the bug report. I’ll need some extra information, please see below.
Login succesuful, few seconds is ok, then terminal crushes.
As I am unable to replicate the issue at my end, is there any possibility you could record the issue when it occurs (Eg: video from a fresh reboot)? I really need to see what happens. WIll help with the debugging process.
Can you also please paste the result from the following command:
~/.bashrc: executed by bash(1) for non-login shells.
/DietPi/dietpi/login
And the Youtube link is:
r6cgHIAq-ic
Sorry for low quality, I recorded it with my mobile phone.
And this is what I found in the log:
12/01/16 16:38:34 Xvnc version TightVNC-1.3.9
12/01/16 16:38:34 Copyright (C) 2000-2007 TightVNC Group
12/01/16 16:38:34 Copyright (C) 1999 AT&T Laboratories Cambridge
12/01/16 16:38:34 All Rights Reserved.
12/01/16 16:38:34 See http://www.tightvnc.com/ for information on TightVNC
12/01/16 16:38:34 Desktop name ‘X’ (DietPi:0)
12/01/16 16:38:34 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
12/01/16 16:38:34 Listening for VNC connections on TCP port 5900
Font directory ‘/usr/share/fonts/X11/Type1/’ not found - ignoring
Font directory ‘/usr/share/fonts/X11/75dpi/’ not found - ignoring
Font directory ‘/usr/share/fonts/X11/100dpi/’ not found - ignoring
xrdb: No such file or directory
xrdb: can’t open file ‘/root/.Xresources’
It appears VNCserver is being launched by the autostart correctly. It is running . Have you tried connecting with a VNC viewer?
In regards to the “garbled text” afterwards:
What you are seeing is not an error, basically the terminal print is misaligned which only happens on the OrangePi. As my OrangePi PC’s HDMI output is broken (there goes any testing), the only thing I can do is explain how to hide the text.
Save and exit:
Press CTRL+X and say yes to save changes.
12/01/16 17:39:48 Xvnc version TightVNC-1.3.9
12/01/16 17:39:48 Copyright (C) 2000-2007 TightVNC Group
12/01/16 17:39:48 Copyright (C) 1999 AT&T Laboratories Cambridge
12/01/16 17:39:48 All Rights Reserved.
12/01/16 17:39:48 See http://www.tightvnc.com/ for information on TightVNC
12/01/16 17:39:48 Desktop name 'X' (DietPi-xu4:0)
12/01/16 17:39:48 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t
12/01/16 17:39:48 Listening for VNC connections on TCP port 5900
Font directory '/usr/share/fonts/X11/Type1/' not found - ignoring
Font directory '/usr/share/fonts/X11/75dpi/' not found - ignoring
Font directory '/usr/share/fonts/X11/100dpi/' not found - ignoring
xrdb: No such file or directory
xrdb: can't open file '/root/.Xresources'
Yep, I get the same on all devices.
When we install Xserver/Xorg, we only install the minimal xfonts to save resources. xrdb is not installed, you won’t need it either. You can safely ignore those items in the logfile.