Black screean by using a self-built arm64-version of TurboVNC

shen

unread,

Dec 3, 2020, 10:29:37 AM12/3/20

to TurboVNC User Discussion/Support

Dear TurboVNC-Users,

I built TurboVNC from source in my Jetson Xavier (aarch64) as follows:

1) build libjpeg-turbo:

git clone https://github.com/libjpeg-turbo/libjpeg-turbo.git

cd libjpeg-turbo && mkdir build && cd build

cmake -G"Unix Makefiles" -DCMAKE_INSTALL_PREFIX=/opt/libjpeg-turbo ../

make -j 8

sudo make install

2) build turbovnc:

git clone https://github.com/TurboVNC/turbovnc.git

cd turbovnc && mkdir build && cd build

cmake -G "Unix Makefiles" -DTVNC_BUILDJAVA=0 ../

make -j 8

sudo make install

Besides:

I didn't change the following 2 things, since I think they are the same (or am I wrong?):
- "DEBARCH=arm64" --> "DEBARCH=aarch64" in pkgsripts/makedpkg
- "Architecture: arm64" --> "Archtecture: aarch64" in pkgsripts/deb-control
I didn't build and install VirtualGL in my Jetson Xavier, since a remote rendering is not necessary at the moment (or must TurboVNC always be used together with VirtualGL?)

When I create a remote desktop in Windows, I got always a black screen.

Where am I wrong and how should I solve the problem?

Best regards,

Shen

DRC

unread,

Dec 3, 2020, 1:47:12 PM12/3/20

to turbovn...@googlegroups.com

The value of DEBARCH for AArch64 Linux platforms may be incorrect in the build system (I will double check), but that is not related to the issue at hand.

I'm not sure what you mean by "when I create a remote desktop in Windows." TurboVNC can only be used to create remote desktops on Linux/Unix systems. We only provide a client (viewer) for Windows.

If I misunderstood you and you are using the TurboVNC Server on Linux/Unix, then tell me which window manager you are trying to use. A black screen is typically due to the window manager failing to start in the TurboVNC Server session. Refer to https://turbovnc.org/Documentation/Compatibility22 for a list of window managers I have personally tested and instructions for each.

It is not necessary to use VirtualGL with TurboVNC. VirtualGL is only necessary if you need GPU acceleration for OpenGL applications running in a TurboVNC session. TurboVNC can run OpenGL applications with software rendering (Mesa) without the use of VirtualGL.

DRC

--
You received this message because you are subscribed to the Google Groups "TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to turbovnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/8d28674d-52fb-46ef-b70f-313ab8b0ecb6n%40googlegroups.com.

shen

unread,

Dec 3, 2020, 3:21:52 PM12/3/20

to TurboVNC User Discussion/Support

Thanks a lot for your reply.

Sorry I didn't describe my problem clearly.

I use the self-built TurboVNC Server in the Jetson Xavier (aarch64, Ubuntu18.04, Unity) and the TurboVNC Viewer (together with Putty) in Windows 10.

The TurboVNC Viewer in Win10 shows a black screen as follows:

Best regards,

Shen

DRC

unread,

Dec 3, 2020, 4:17:28 PM12/3/20

to turbovn...@googlegroups.com

That's a window manager issue, then. Are you really using Unity, which isn't installed by default on Ubuntu 18.04, or are you using the installed version of GNOME 3 that looks like Unity?

To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/3c54ed0c-79b2-4f12-9016-c14b16bf253an%40googlegroups.com.

shen

unread,

Dec 4, 2020, 6:10:14 AM12/4/20

to TurboVNC User Discussion/Support

Yes, I'm sure that I'm using Unity on Ubuntu18.04.

I flashed my Jetson Xavier with JetPack 4.3 of NVIDIA:

https://developer.nvidia.com/jetpack-43-archive

https://www.jetsonhacks.com/2019/12/17/jetpack-4-3-release/

The installed OS is Ubuntu18.04 and there are two DE (Unity7 and GNOME3), which can be selected while logging in:

I always choose the Unity, since I think not all the things run very well in this GNOME.

It is mentioned in the docu of the TurboVNC that the TurboVNC server attempts to use OS specific techniques to launch the user's most recently used window manager:

https://docs.oracle.com/cd/E19279-01/820-3257-12/turbovnc.html

So I think the Unity on Ubuntu18.04 should be launched every time.

I have also tried with the GNOME. The TurboVNC Viewer on Win10 shows a black screen too.

Besides, the Display Manager is gdm3 at the moment. I don't know whether it has an influence or not.

Best regards

DRC

unread,

Dec 4, 2020, 12:58:50 PM12/4/20

to turbovn...@googlegroups.com

That documentation is 12 years old and represents Sun Shared Visualization, the product that Sun Microsystems once released around VirtualGL 2.0 - 2.1.1 and TurboVNC 0.3.3 - 0.5. The product and the releases of VirtualGL and TurboVNC that it once contained are long obsolete. Even when I was a Sun Microsystems employee, I did not write the Sun Shared Visualization documentation. I wrote (and still write) the TurboVNC User's Guide: https://turbovnc.org/Documentation/Documentation, which (along with the man pages included in the TurboVNC packages) is the only official source of documentation for the current, independently-developed releases of TurboVNC.

The current version of TurboVNC bears little resemblance to the versions used in Sun Shared Visualization. TurboVNC no longer attempts to launch the user's most-recently-used window manager, because the mechanism by which it did that (the old 'switchdesk' command on Linux systems) is no longer there. These days, our xstartup.turbovnc script attempts to load the "default" window manager for a particular platform, but if you want to use something other than the default, you have to specify the window manager startup script using the -wm argument to vncserver (or the $wm variable in ~/.vnc/turbovncserver.conf or /etc/turbovncserver.conf.) Unity isn't supported on Ubuntu 18.04 and later, much less installed by default, so you might be the first person who has ever attempted to use Unity with TurboVNC on Ubuntu 18.04. I wasn't even aware that you could install Unity on Ubuntu 18.04 until now. Now that I'm aware of it, I can test it myself and document a procedure for its use, assuming that I am able to make it work.

DRC

To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/46af0490-426e-4618-b6c1-f0e40925676en%40googlegroups.com.

DRC

unread,

Dec 4, 2020, 1:14:02 PM12/4/20

to turbovn...@googlegroups.com

Unfortunately, I cannot get Unity to launch from either GDM or LightDM, and with no way of verifying whether that WM even works without TurboVNC, it is impossible for me to fix whatever issues might be preventing it from working with TurboVNC. GNOME 3 in TurboVNC works fine for me on Ubuntu 18.04, so I'm not sure why it isn't launching for you. You might try passing '-wm gnome-session' to /opt/TurboVNC/bin/vncserver.

If you don't want to use GNOME 3 in TurboVNC, I would suggest using MATE as an alternative. It has a clean interface based on GNOME 2, and it works well with Linux VNC servers.

On 12/4/20 5:10 AM, shen wrote:

To view this discussion on the web visit https://groups.google.com/d/msgid/turbovnc-users/46af0490-426e-4618-b6c1-f0e40925676en%40googlegroups.com.

shen

unread,

Dec 8, 2020, 11:57:27 AM12/8/20

to TurboVNC User Discussion/Support

Thanks a lot for your detailed explanation.

I got still a black screen with the Unity and GNOME3 of the Jetson, no matter how I set. So I gave up.

I installed MATE and xfce4 in the Jetson. The TurboVNC starts to work successfully with the both.

But another problem appears: After running well for a few minutes, the remote desktop of the TurboVNC Viewer in Win10 freezes.

I tried many times with the both window managers, but the system turns always into a frozen state.

Best regards

DRC

unread,

Dec 8, 2020, 12:24:45 PM12/8/20

to turbovn...@googlegroups.com

When it freezes, try the following:

1. Disconnect and reconnect to the TurboVNC session. This will tell us
whether the remote session is actually frozen or whether there is some
issue with the viewer or the network layer.

2. If the session is still frozen after disconnecting and reconnecting,
try logging into the server with SSH and running

DISPLAY=:{n} xdpyinfo

where {n} is the X display number of the session. This will tell us
whether the actual TurboVNC X server is frozen.

3. If you are using the Windows native TurboVNC Viewer, try using the
Windows/Java TurboVNC Viewer instead (or vice versa.) This will tell us
whether the issue is specific to one of those viewer implementations.
If the session is still frozen after Step 1, then restart it before
trying to use the other viewer.

4. If you are using the Windows/Java TurboVNC Viewer with built-in TLS
encryption enabled (which is the default), try disabling TLS encryption.
This will tell us whether the issue is related to OpenSSL.

5. Check the server log
(~/.vnc/{hostname}-{TurboVNC-display-number}.log) for any errors that
might be occurring just prior to the freeze.

6. Try disabling the screen blanker in the TurboVNC session.

>> login.jpg
>> I always choose the Unity, since I think not all the things run
>> very well in this GNOME.
>>
>> It is mentioned in the docu of the TurboVNC that the TurboVNC
>> server attempts to use OS specific techniques to launch the user's
>> most recently used window manager:
>> https://docs.oracle.com/cd/E19279-01/820-3257-12/turbovnc.html
>> So I think the Unity on Ubuntu18.04 should be launched every time.
>> I have also tried with the GNOME. The TurboVNC Viewer on Win10
>> shows a black screen too.
>>

>> Besides, the Display Manager is *gdm3* at the moment. I don't know

>> whether it has an influence or not.
>>
>> Best regards
>>
>>
>> DRC schrieb am Donnerstag, 3. Dezember 2020 um 22:17:28 UTC+1:
>>
>> That's a window manager issue, then. Are you really using
>> Unity, which isn't installed by default on Ubuntu 18.04, or
>> are you using the installed version of GNOME 3 that looks like
>> Unity?
>>
>> On 12/3/20 2:21 PM, shen wrote:
>>> Thanks a lot for your reply.
>>>
>>> Sorry I didn't describe my problem clearly.
>>> I use the self-built TurboVNC Server in the Jetson Xavier
>>> (aarch64, Ubuntu18.04, Unity) and the TurboVNC Viewer
>>> (together with Putty) in Windows 10.
>>> The TurboVNC Viewer in Win10 shows a black screen as follows:

>>>> * I *didn't* change the following 2 things, since I

>>>> think they are the same (or am I wrong?):

>>>> o "DEBARCH=arm64" --> "DEBARCH=aarch64" in
>>>> pkgsripts/makedpkg
>>>> o "Architecture: arm64" --> "Archtecture: aarch64"
>>>> in pkgsripts/deb-control
>>>> * I didn't build and install VirtualGL in my Jetson

>>>> Xavier, since a remote rendering is not necessary at
>>>> the moment (or must TurboVNC always be used together
>>>> with VirtualGL?)
>>>>
>>>>
>>>> When I create a remote desktop in Windows, I got always
>>>> a black screen.
>>>> Where am I wrong and how should I solve the problem?
>>>>
>>>> Best regards,
>>>> Shen
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to
>>>> the Google Groups "TurboVNC User Discussion/Support" group.
>>>> To unsubscribe from this group and stop receiving emails
>>>> from it, send an email to turbovnc-user...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/turbovnc-users/8d28674d-52fb-46ef-b70f-313ab8b0ecb6n%40googlegroups.com

>>>> <https://groups.google.com/d/msgid/turbovnc-users/8d28674d-52fb-46ef-b70f-313ab8b0ecb6n%40googlegroups.com?utm_medium=email&utm_source=footer>.

>>>
>>> --
>>> You received this message because you are subscribed to the
>>> Google Groups "TurboVNC User Discussion/Support" group.
>>> To unsubscribe from this group and stop receiving emails from
>>> it, send an email to turbovnc-user...@googlegroups.com.
>>> To view this discussion on the web visit

>>> https://groups.google.com/d/msgid/turbovnc-users/3c54ed0c-79b2-4f12-9016-c14b16bf253an%40googlegroups.com
>>> <https://groups.google.com/d/msgid/turbovnc-users/3c54ed0c-79b2-4f12-9016-c14b16bf253an%40googlegroups.com?utm_medium=email&utm_source=footer>.

>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "TurboVNC User Discussion/Support" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to turbovnc-user...@googlegroups.com.
>> To view this discussion on the web visit

>> https://groups.google.com/d/msgid/turbovnc-users/46af0490-426e-4618-b6c1-f0e40925676en%40googlegroups.com
>> <https://groups.google.com/d/msgid/turbovnc-users/46af0490-426e-4618-b6c1-f0e40925676en%40googlegroups.com?utm_medium=email&utm_source=footer>.

>
> --
> You received this message because you are subscribed to the Google
> Groups "TurboVNC User Discussion/Support" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to turbovnc-user...@googlegroups.com

> <mailto:turbovnc-user...@googlegroups.com>.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/turbovnc-users/e885f670-aa5e-457d-987d-2f78baa934d2n%40googlegroups.com
> <https://groups.google.com/d/msgid/turbovnc-users/e885f670-aa5e-457d-987d-2f78baa934d2n%40googlegroups.com?utm_medium=email&utm_source=footer>.

shen

unread,

Dec 9, 2020, 8:34:29 AM12/9/20

to TurboVNC User Discussion/Support

Thanks a lot for your tips.

I found that:

On Xfce4, when I clicked the network icon on the upper right corner of the desktop, the system turns into a frozen state at once.
After each reconnection, the following appears always:

So I think the frozen problem may be partly caused by the network manager. I reinstalled the network manager with "sudo apt install network-manager network-manager-gnome" (I think MATE and Xfce4 can also use network-manager-gnome). But there is no help.

Except the frozen problem, I also oft got disconnected problems suddenly like "Connection closed" and "WriteExact: Socket error while running", which I have never encountered on an AMD64-version before.

For the frozen problem, I tried each of your tips, but the problem exists still.

1. Disconnect and reconnect to the TurboVNC session. This will tell us
whether the remote session is actually frozen or whether there is some
issue with the viewer or the network layer.

--> The remote session is actually frozen.

2. If the session is still frozen after disconnecting and reconnecting,
try logging into the server with SSH and running

DISPLAY=:{n} xdpyinfo

where {n} is the X display number of the session. This will tell us
whether the actual TurboVNC X server is frozen.

--> xdpyinfo: unable to open display ":1"

and sometimes it shows nothing.

3. If you are using the Windows native TurboVNC Viewer, try using the
Windows/Java TurboVNC Viewer instead (or vice versa.) This will tell us
whether the issue is specific to one of those viewer implementations.
If the session is still frozen after Step 1, then restart it before
trying to use the other viewer.

--> With the Windows/Java TurboVNV, I got the frozen problem even more frequently.

4. If you are using the Windows/Java TurboVNC Viewer with built-in TLS
encryption enabled (which is the default), try disabling TLS encryption.
This will tell us whether the issue is related to OpenSSL.

--> I disabled TLS encryption, but also got the frozen problem.

5. Try disabling the screen blanker in the TurboVNC session.
--> I disabled the screen blanker, but also got the frozen problem.

6. Check the server log

(~/.vnc/{hostname}-{TurboVNC-display-number}.log) for any errors that
might be occurring just prior to the freeze.

--> I checked the log-file when no problem has appeared. There are already many "error" and "failed" etc., which never appear on an AMD64-version, as follows:

TurboVNC Server (Xvnc) 64-bit v2.2.6 (build 20201203)

Visit http://www.TurboVNC.org for more information on TurboVNC

09/12/2020 13:01:34 Using security configuration file /opt/TurboVNC/etc/turbovncserver-security.conf

09/12/2020 13:01:34 Enabled security type 'tlsvnc'

09/12/2020 13:01:34 Enabled security type 'tlsotp'

09/12/2020 13:01:34 Enabled security type 'tlsplain'

09/12/2020 13:01:34 Enabled security type 'x509vnc'

09/12/2020 13:01:34 Enabled security type 'x509otp'

09/12/2020 13:01:34 Enabled security type 'x509plain'

09/12/2020 13:01:34 Enabled security type 'vnc'

09/12/2020 13:01:34 Enabled security type 'otp'

09/12/2020 13:01:34 Enabled security type 'unixlogin'

09/12/2020 13:01:34 Enabled security type 'plain'

09/12/2020 13:01:34 Desktop name 'TurboVNC: xavier:2 (kfzb)' (xavier:2)

09/12/2020 13:01:34 Protocol versions supported: 3.3, 3.7, 3.8, 3.7t, 3.8t

09/12/2020 13:01:34 Listening for VNC connections on TCP port 5902

09/12/2020 13:01:34 Interface 0.0.0.0

09/12/2020 13:01:34 Framebuffer: BGRX 8/8/8/8

09/12/2020 13:01:34 New desktop size: 1240 x 900

09/12/2020 13:01:34 New screen layout:

09/12/2020 13:01:34 0x00000040 (output 0x00000040): 1240x900+0+0

09/12/2020 13:01:34 Maximum clipboard transfer size: 1048576 bytes

09/12/2020 13:01:34 VNC extension running!

Unable to create /home/kfzb/.dbus/session-bus

gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used

mate-session[10309]: WARNING: Unable to find provider '' of required component 'dock'

Window manager warning: Log level 128: Name com.canonical.AppMenu.Registrar does not exist on the session bus

Window manager warning: Log level 16: XPresent is not compatible with your current system configuration.

caja-dropbox is not installed, doing nothing.

(process:10492): indicator-sound-WARNING **: 13:01:39.199: volume-control-pulse.

vala:735: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.

ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files

gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used

SSH_AUTH_SOCK=/run/user/1000/keyring/ssh

gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used

(process:10492): AccountsService-WARNING **: 13:01:39.333: Could not get current seat: No data available

SSH_AUTH_SOCK=/run/user/1000/keyring/ssh

gnome-keyring-daemon: insufficient process capabilities, insecure memory might get used

SSH_AUTH_SOCK=/run/user/1000/keyring/ssh

(process:10544): AccountsService-WARNING **: 13:01:39.790: Could not get current seat: No data available

Failure: Module initialization failed

*** ERROR ***

TI:13:01:41 TH:0x5594527100 FI:gpm-manager.c FN:gpm_manager_systemd_inhibit,1782

- Error in dbus - GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied

Traceback:

mate-power-manager(+0x1af94) [0x55628e1f94]

mate-power-manager(+0x133ec) [0x55628da3ec]

/usr/lib/aarch64-linux-gnu/libgobject-2.0.so.0(g_type_create_instance+0x2ec) [0x7f8ed08dc4]

no maximize: true

** (update-notifier:10515): WARNING **: 13:01:41.302: already running?

(nm-applet:10473): nm-applet-WARNING **: 13:01:41.924: GDBus.Error:org.freedesktop.NetworkManager.AgentManager.PermissionDenied: An agent with this ID is already registered for this user.

No nvidia-settings and prime-select detected.

Initializing caja-open-terminal extension

09/12/2020 13:01:42 Autoprobing TCP port in (all) network interface

09/12/2020 13:01:42 Listening IPv6://[::]:5900

09/12/2020 13:01:42 Listening IPv4://0.0.0.0:5900

09/12/2020 13:01:42 Problems in NewSocketListenTCP()

09/12/2020 13:01:42 Listening IPv6://[::]:5901

09/12/2020 13:01:42 Listening IPv4://0.0.0.0:5901

09/12/2020 13:01:42 Autoprobing selected port 5901

09/12/2020 13:01:42 Advertising security type: 'TLS' (18)

09/12/2020 13:01:42 Re-binding socket to listen for VNC connections on TCP port 5901 in (all) interface

09/12/2020 13:01:42 Listening IPv6://[::]:5901

09/12/2020 13:01:42 Listening IPv4://0.0.0.0:5901

09/12/2020 13:01:42 Clearing securityTypes

09/12/2020 13:01:42 Advertising security type: 'TLS' (18)

09/12/2020 13:01:42 Clearing securityTypes

09/12/2020 13:01:42 Advertising security type: 'TLS' (18)

09/12/2020 13:01:42 Advertising authentication type: 'No Authentication' (1)

09/12/2020 13:01:42 Re-binding socket to listen for VNC connections on TCP port 5901 in (all) interface

09/12/2020 13:01:42 Listening IPv6://[::]:5901

09/12/2020 13:01:42 Listening IPv4://0.0.0.0:5901

09/12/2020 13:01:42 Clearing securityTypes

09/12/2020 13:01:42 Clearing authTypes

09/12/2020 13:01:42 Advertising security type: 'TLS' (18)

09/12/2020 13:01:42 Advertising authentication type: 'No Authentication' (1)

09/12/2020 13:01:42 Advertising security type: 'No Authentication' (1)

blueman-applet version 2.0.5 starting

There is an instance already running

(nm-applet:10473): Gtk-WARNING **: 13:01:42.838: Can't set a parent on widget which has a parent

(polkit-mate-authentication-agent-1:10476): polkit-mate-1-WARNING **: 13:01:43.124: No icon for themed icon with name 'nm-icon'

RuntimeError: object at 0x7f722775a0 of type RenameMenu is not initialized

RuntimeError: object at 0x7f72277eb0 of type FolderColorMenu is not initialized

Gtk-Message: 13:01:43.365: GtkDialog mapped without a transient parent. This is discouraged.

Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600007 (Authentica)

Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

INFO:root:The HUD is disabled via org.mate.hud in gsettings.

(nm-applet:10473): Gtk-CRITICAL **: 13:02:08.053: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:02:08.128: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:02:14.478: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:02:14.573: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:02:14.633: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:02:14.719: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:02:20.658: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-CRITICAL **: 13:02:20.659: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:02:20.794: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:02:20.953: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-CRITICAL **: 13:02:20.954: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:02:21.066: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:02:22.373: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:02:22.562: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:02:22.655: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:02:22.757: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:02:26.204: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:02:26.350: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:02:26.454: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:02:26.550: Can't set a parent on widget which has a parent

09/12/2020 13:03:58 Got connection from client 127.0.0.1

09/12/2020 13:03:58 Using protocol version 3.8

09/12/2020 13:03:58 Enabling TightVNC protocol extensions

09/12/2020 13:03:58 Advertising Tight auth cap 'VENCRYPT'

09/12/2020 13:03:58 Advertising Tight auth cap 'VNCAUTH_'

09/12/2020 13:03:58 Advertising Tight auth cap 'ULGNAUTH'

09/12/2020 13:04:00 Client 127.0.0.1 gone

09/12/2020 13:04:00 Statistics:

09/12/2020 13:04:00 framebuffer updates 0, rectangles 0, bytes 0

09/12/2020 13:04:10 Got connection from client 127.0.0.1

09/12/2020 13:04:10 Using protocol version 3.8

09/12/2020 13:04:10 Enabling TightVNC protocol extensions

09/12/2020 13:04:10 Advertising Tight auth cap 'VENCRYPT'

09/12/2020 13:04:10 Advertising Tight auth cap 'VNCAUTH_'

09/12/2020 13:04:10 Advertising Tight auth cap 'ULGNAUTH'

09/12/2020 13:04:13 Full-control authentication enabled for 127.0.0.1

09/12/2020 13:04:13 Pixel format for client 127.0.0.1:

09/12/2020 13:04:13 32 bpp, depth 24, little endian

09/12/2020 13:04:13 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0

09/12/2020 13:04:13 no translation needed

09/12/2020 13:04:13 Using tight encoding for client 127.0.0.1

09/12/2020 13:04:13 Interframe comparison enabled

09/12/2020 13:04:13 Enabling full-color cursor updates for client 127.0.0.1

09/12/2020 13:04:13 Enabling cursor position updates for client 127.0.0.1

09/12/2020 13:04:13 Using JPEG subsampling 0, Q92 for client 127.0.0.1

09/12/2020 13:04:13 Using JPEG quality 80 for client 127.0.0.1

09/12/2020 13:04:13 Using JPEG subsampling 2 for client 127.0.0.1

09/12/2020 13:04:13 Enabling LastRect protocol extension for client 127.0.0.1

09/12/2020 13:04:13 Enabling Desktop Size protocol extension for client 127.0.0.1

09/12/2020 13:04:13 Enabling Extended Desktop Size protocol extension for client 127.0.0.1

09/12/2020 13:04:13 Enabling Continuous Updates protocol extension for client 127.0.0.1

09/12/2020 13:04:13 Enabling Fence protocol extension for client 127.0.0.1

09/12/2020 13:04:13 Enabling GII protocol extension for client 127.0.0.1

09/12/2020 13:04:13 Using Tight compression level 1 for client 127.0.0.1

09/12/2020 13:04:13 Using 4 threads for Tight encoding

09/12/2020 13:04:13 Client supports GII version 1

09/12/2020 13:04:13 New screen layout:

09/12/2020 13:04:13 0x00000040 (output 0x00000040): 1240x900+0+0

09/12/2020 13:04:13 Continuous updates enabled

09/12/2020 13:04:16 New desktop size: 1920 x 1112

09/12/2020 13:04:16 Interframe comparison disabled

09/12/2020 13:04:16 Interframe comparison enabled

09/12/2020 13:04:16 New screen layout:

09/12/2020 13:04:16 0x00000040 (output 0x00000040): 1920x1112+0+0

09/12/2020 13:04:16 Continuous updates enabled

(nm-applet:10473): Gtk-CRITICAL **: 13:06:28.964: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:06:29.032: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:06:38.977: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-CRITICAL **: 13:06:38.978: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:06:39.008: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:06:39.040: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:06:39.055: Can't set a parent on widget which has a parent

RuntimeError: object at 0x7f722775a0 of type RenameMenu is not initialized

RuntimeError: object at 0x7f72277eb0 of type FolderColorMenu is not initialized

RuntimeError: object at 0x7f722775a0 of type RenameMenu is not initialized

RuntimeError: object at 0x7f72277eb0 of type FolderColorMenu is not initialized

RuntimeError: object at 0x7f722775a0 of type RenameMenu is not initialized

untimeError: object at 0x7f72277eb0 of type FolderColorMenu is not initialized

RuntimeError: object at 0x7f722775a0 of type RenameMenu is not initialized

RuntimeError: object at 0x7f72277eb0 of type FolderColorMenu is not initialized

** (zeitgeist-datahub:10534): WARNING **: 13:12:44.823: zeitgeist-datahub.vala:210: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.DatabaseError: SQL error: 5, database is locked

** (zeitgeist-datahub:10534): WARNING **: 13:14:43.990: zeitgeist-datahub.vala:210: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required

[11470:11470:1209/131445.381822:ERROR:angle_platform_impl.cc(43)] Display.cpp:805 (initialize): ANGLE Display::initialize error 12289: GLX is not present.

[11470:11470:1209/131445.382387:ERROR:gl_surface_egl.cc(773)] EGL Driver message (Critical) eglInitialize: GLX is not present.

[11470:11470:1209/131445.382608:ERROR:gl_surface_egl.cc(1322)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type

[11470:11470:1209/131445.383767:ERROR:angle_platform_impl.cc(43)] Display.cpp:805 (initialize): ANGLE Display::initialize error 12289: GLX is not present.

[11470:11470:1209/131445.384026:ERROR:gl_surface_egl.cc(773)] EGL Driver message (Critical) eglInitialize: GLX is not present.

[11470:11470:1209/131445.384245:ERROR:gl_surface_egl.cc(1322)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED

[11470:11470:1209/131445.384435:ERROR:gl_initializer_linux_x11.cc(160)] GLSurfaceEGL::InitializeOneOff failed.

[11470:11470:1209/131445.413873:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization

RuntimeError: object at 0x7f722775a0 of type RenameMenu is not initialized

RuntimeError: object at 0x7f72277eb0 of type FolderColorMenu is not initialized

Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x38000f5 (NetworkMan)

Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

(gedit:11421): Gtk-WARNING **: 13:15:46.650: Attempting to read the recently used resources file at '/home/kfzb/.local/share/recently-used.xbel',

but the parser failed: Failed to open file \u201c/home/kfzb/.local/share/recently-used.xbel\u201d: Permission denied.

(caja:10402): Gtk-WARNING **: 13:15:53.041: Attempting to read the recently used resources file at '/home/kfzb/.local/share/recently-used.xbel', but the parser failed: Failed to open file \u201c/home/kfzb/.local/share/recently-used.xbel\u201d: Permission denied.

(zeitgeist-datahub:10534): Gtk-WARNING **: 13:15:53.041: Attempting to read the recently used resources file at '/home/kfzb/.local/share/recently-used.xbel', but the parser failed: Failed to open file ?/home/kfzb/.local/share/recently-used.xbel?: Permission denied.

(nm-applet:10473): Gtk-CRITICAL **: 13:15:57.908: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-CRITICAL **: 13:15:57.909: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:15:58.848: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:15:58.912: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:15:58.926: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:15:59.118: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:15:59.139: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:15:59.168: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:15:59.211: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:15:59.263: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-CRITICAL **: 13:15:59.264: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:15:59.323: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:15:59.376: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:15:59.391: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:15:59.416: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:15:59.434: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:16:02.415: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:16:02.447: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:16:02.467: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:16:02.513: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:16:02.592: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:16:02.696: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:16:02.749: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:16:02.852: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:16:02.970: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:16:03.034: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:16:05.862: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:16:05.981: Can't set a parent on widget which has a parent

(nm-applet:10473): Gtk-CRITICAL **: 13:16:06.059: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed

(nm-applet:10473): Gtk-WARNING **: 13:16:06.143: Can't set a parent on widget which has a parent

(caja:10402): Gtk-CRITICAL **: 13:16:49.403: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed

(caja:10402): Gtk-CRITICAL **: 13:16:49.404: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed

(caja:10402): Gtk-CRITICAL **: 13:16:49.405: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed