#tigervnc — Public Fediverse posts

TigerVNC Team released #TigerVNC version 1.16.2. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.2. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.2. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.2. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.2. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.1. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.1. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.1. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.1. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.1. https://tigervnc.org/

TigerVNC 1.16 introduce il nuovo server w0vncserver per condividere desktop Wayland, migliora la gestione dei tasti di sistema e aggiorna il viewer nativo #TigerVNC #Software #Linux

https://www.linuxeasy.org/tigervnc-1-16-porta-il-supporto-wayland-con-il-nuovo-w0vncserver/?utm_source=mastodon&utm_medium=jetpack_social

TigerVNC 1.16 introduce il nuovo server w0vncserver per condividere desktop Wayland, migliora la gestione dei tasti di sistema e aggiorna il viewer nativo #TigerVNC #Software #Linux

https://www.linuxeasy.org/tigervnc-1-16-porta-il-supporto-wayland-con-il-nuovo-w0vncserver/?utm_source=mastodon&utm_medium=jetpack_social

TigerVNC 1.16 introduce il nuovo server w0vncserver per condividere desktop Wayland, migliora la gestione dei tasti di sistema e aggiorna il viewer nativo #TigerVNC #Software #Linux

https://www.linuxeasy.org/tigervnc-1-16-porta-il-supporto-wayland-con-il-nuovo-w0vncserver/?utm_source=mastodon&utm_medium=jetpack_social

TigerVNC 1.16 introduce il nuovo server w0vncserver per condividere desktop Wayland, migliora la gestione dei tasti di sistema e aggiorna il viewer nativo #TigerVNC #Software #Linux

https://www.linuxeasy.org/tigervnc-1-16-porta-il-supporto-wayland-con-il-nuovo-w0vncserver/?utm_source=mastodon&utm_medium=jetpack_social

TigerVNC 1.16 introduce il nuovo server w0vncserver per condividere desktop Wayland, migliora la gestione dei tasti di sistema e aggiorna il viewer nativo #TigerVNC #Software #Linux

https://www.linuxeasy.org/tigervnc-1-16-porta-il-supporto-wayland-con-il-nuovo-w0vncserver/?utm_source=mastodon&utm_medium=jetpack_social

#TigerVNC 1.16 Released with Support for Sharing #Wayland Desktops

https://9to5linux.com/tigervnc-1-16-released-with-support-for-sharing-wayland-desktops

#TigerVNC 1.16 Released with Support for Sharing #Wayland Desktops

https://9to5linux.com/tigervnc-1-16-released-with-support-for-sharing-wayland-desktops

#TigerVNC 1.16 Released with Support for Sharing #Wayland Desktops

https://9to5linux.com/tigervnc-1-16-released-with-support-for-sharing-wayland-desktops

#TigerVNC 1.16 Released with Support for Sharing #Wayland Desktops

https://9to5linux.com/tigervnc-1-16-released-with-support-for-sharing-wayland-desktops

#TigerVNC 1.16 Released with Support for Sharing #Wayland Desktops

https://9to5linux.com/tigervnc-1-16-released-with-support-for-sharing-wayland-desktops

TigerVNC Team released #TigerVNC version 1.16.0. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.0. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.0. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.0. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.16.0. https://tigervnc.org/

War mal wieder klar, als ich letztens mit #qemu angefangen habe, dachte ich noch, #spice wäre der Standard um entfernten Desktop der VMs zu übertragen. Nun habe ich die gleichen Dinge in meinen neuen Server, diesmal mit Debian13 reingebaut, da stelle ich fest, #VNC ist dort Standard. Und tatsächlich, spice ist "deprecated", also abgekündigt. Na gut, also alles wieder auf VNC umgerüstet, dabei auf den Tastatur-Foo gestoßen, welchen ich glücklicherweise mit #TigerVNC und minimale Konfiguration seites der VMs und des Hosts hinbekommen habe. Das schöne an solchen Basteleien, der Schreibtisch bleibt sauber und es fällt auch sonst kein Müll an. Und man lernt ausserdem immer ein klein wenig dazu. Das Hirn des alten Sacks bleibt geschmeidig. 🤣

Installing TigerVNC Server on Ubuntu proot-distro on Termux in Android with full UI scaling and audio support!

#Android #TigerVNC #Linux #Ubuntu #Termux #VNC #proot #TechNews #TechUpdates #PulseAudio

https://officialaptivi.wordpress.com/2025/12/27/installing-tigervnc-server-on-ubuntu-proot-distro-on-termux-in-android/

Installing TigerVNC Server on Ubuntu proot-distro on Termux in Android with full UI scaling and audio support!

#Android #TigerVNC #Linux #Ubuntu #Termux #VNC #proot #TechNews #TechUpdates #PulseAudio

https://officialaptivi.wordpress.com/2025/12/27/installing-tigervnc-server-on-ubuntu-proot-distro-on-termux-in-android/

Installing TigerVNC Server on Ubuntu proot-distro on Termux in Android with full UI scaling and audio support!

#Android #TigerVNC #Linux #Ubuntu #Termux #VNC #proot #TechNews #TechUpdates #PulseAudio

https://officialaptivi.wordpress.com/2025/12/27/installing-tigervnc-server-on-ubuntu-proot-distro-on-termux-in-android/

Installing TigerVNC Server on Ubuntu proot-distro on Termux in Android with full UI scaling and audio support!

#Android #TigerVNC #Linux #Ubuntu #Termux #VNC #proot #TechNews #TechUpdates #PulseAudio

https://officialaptivi.wordpress.com/2025/12/27/installing-tigervnc-server-on-ubuntu-proot-distro-on-termux-in-android/

Installing TigerVNC Server on Ubuntu proot-distro on Termux in Android with full UI scaling and audio support!

#Android #TigerVNC #Linux #Ubuntu #Termux #VNC #proot #TechNews #TechUpdates #PulseAudio

https://officialaptivi.wordpress.com/2025/12/27/installing-tigervnc-server-on-ubuntu-proot-distro-on-termux-in-android/

Installing TigerVNC Server on Ubuntu proot-distro on Termux in Android

Termux provides a way to install a proot distro for several popular Linux distributions, such as Arch Linux, Ubuntu, and Fedora. In Android devices, you can make use of one of the proot distributions to run your favorite Linux programs, if they don’t work on a normal Termux environment.

We have used a Ubuntu proot distribution to do what we’re going to do in this article, which is installing and configuring TigerVNC on your proot distribution installation on your Android device. It’s best experienced with a large tablet, more preferrably a powerful tablet, with a 64-bit ARM processor and a latest version of Android.

Before you start following the installation steps, you’ll need to disable background restrictions for child processes, assuming that you’re running the latest version of Android with Developer Options enabled. Make sure that “Disable child process restrictions” is enabled, just like below:

After that, you can follow the below steps:

First, install the Ubuntu proot distribution by opening Terminaux and using proot-distro install ubuntu. After that, log in to the distribution using proot-distro login ubuntu and refresh the package database using apt update.

After the database gets updated, we recommend that you run apt dist-upgrade to make sure that all packages get updated. Afterwards, you can now run apt install tigervnc-standalone-server awesome to install both the TigerVNC Server and the Awesome window manager.

It depends on both your device performance and your internet connection speed, and it may take some time. Afterwards, you should see the following:

Then, start the VNC server using the vncserver command.

Afterwards, download a VNC client app for Android. For instance, we have used RealVNC Viewer to establish the connection to the local VNC server. Add a new connection using the appropriate port that is connected to the mentioned display. For example, we have started the VNC server on display :2, so the port is 5902. Specify the IP address of the local host, such as 127.0.0.1:5902.

Afterwards, press the Connect button at the bottom.

Then, use the same password that you’ve used when you first set up the VNC server.

Afterwards, the VNC display shows up, and the Awesome window manager shows up.

However, the default configuration didn’t match our tablet’s resolution, so you might see blurry display, depending on the device. As a result, we’ll have to kill the VNC server using vncserver -kill :2, and adjust your display number. You can list VNC servers using vncserver -list.

Another problem is that we haven’t installed the terminal emulator. To solve this, you can install a terminal emulator, and we’ll use QTerminal here, using apt install qterminal. However, according to our tests, some terminal emulators don’t work and crash with “Illegal instruction”, such as zutty, kitty, and alacritty.

After the installation of the terminal emulator completes, it’s time to configure our VNC server to match the tablet’s resolution in landscape mode. For example, our tablet’s resolution is 2560×1600 in landscape mode, so we need to create a new file called ~/.config/tigervnc/config to add a new line, geometry=2560x1600, to it. This tells TigerVNC to start the X11 server using 2560×1600 as the resolution. Adapt the screen resolution according to your device’s specifications, such as 2960×1848 for the Galaxy Tab S11 Ultra in landscape mode.

After that, start the VNC server. Now, text, images, and other elements will appear smooth and crisp.

This is further confirmed by opening the connection information. RealVNC Viewer told us that the display size has been set to the resolution that we’ve configured in the abovementioned configuration file.

The other problem we need to solve is that the image quality in the VNC client has been automatically set to the lowest quality possible, which means that we’re losing color, which is unattractive. Fortunately, since we’re on a localhost connection, we can achieve high performance with high quality image by scrolling to Picture Quality and selecting High.

As a result, the VNC display has become much better than before, while maintaining high performance.

However, depending on the DPI of your device, elements may appear very tiny. For example, on our Galaxy Tab S8 that sports the ~274 PPI display, you can read the text only if you zoom in to the text that you want to read, which is inconvenient. In this case, QTerminal appears to be small, because, by default, 96 DPI is used.

To fix this, we’ll need to modify two files: .profile and .Xresources under the home directory. Let’s modify them like this:

• In the .Xresources file, add a single line “Xft.dpi: 274“. You can simplify that by executing the “echo "Xft.dpi: 274" >> ~/.Xresources” command. Adapt this configuration according to your device DPI, such as 239 for the Galaxy Tab S11 Ultra.
• In the .profile file, add the following lines:
  • export QT_AUTO_SCREEN_SCALE_FACTOR=0
  • export QT_SCALE_FACTOR=1
  • export QT_FONT_DPI=225
• Adapt the QT_FONT_DPI environment variable to point to your device DPI, subtracting 50 from it. However, adjust the DPI value to make Qt windows large, as needed. You can use the same command mentioned above, like “echo "export QT_FONT_DPI=225" >> ~/.profile“.

In case you’re using GNOME or GTK apps, make sure that you can use the gsettings command. Afterwards, adjust the following commands (scaling-factor 2 and text-scaling-factor 0.75) until the GTK apps look big enough:

$ gsettings set org.gnome.desktop.interface scaling-factor 2$ gsettings set org.gnome.desktop.interface text-scaling-factor 0.75

Afterwards, start the VNC server.

Once you start the VNC server, the UI elements should become large enough to be readable for you, adjusted to your device’s scaling factor. For example, QTerminal now looks big.

That’s it! Your VNC server has been finally configured!

Bonus 1: you can install PulseAudio on the Termux environment outside proot-distro using pkg install pulseaudio. Afterwards, run the following command:

$ pkill pulseaudio$ pulseaudio --start --load="module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1" --exit-idle-time=-1

If your audio doesn’t work, or if pactl list shows that the null driver is being used, stop the PulseAudio server using pulseaudio -k, then execute the below command (note the LD_PRELOAD environment variable):

$ pkill pulseaudio$ LD_PRELOAD=/system/lib64/libskcodec.so pulseaudio --start --load="module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1" --exit-idle-time=-1

Now, when you list devices running on PulseAudio, you should see:

After that, go to inside the proot-distro environment and install Audacious to test PulseAudio using apt install audacious. Then, start the VNC server, open Audacious, and add your favorite music by going to /storage/emulated/0 and navigating to your music library folder. After that, raise your tablet’s volume and sound should come out from your tablet’s speakers. A working sound configuration will be like this (with neofetch installed with apt install fastfetch):

Bonus 2: Since Audacious supports playing online radio stations (Icecast or SHOUTcast) effortlessly without having to use dedicated Android apps, you can use it to play your favorite online radio station according to your taste, such as AH.FM, which plays trance and other EDM music. Although this radio station has a dedicated app for phones, you can use Audacious to stream it.

Bonus 3: You can make a new user using adduser <name>, replacing <name> with your desired username. Then, log out of the proot-distro environment and log in with your user using proot-distro login ubuntu --user <name>. You’ll have to retry the UI and VNC scaling configuration steps. This is required for applications and daemons, such as xscreensaver, that may forbid logging in as root. For example, xscreensaver refuses to run on root, so this is required to be able to run. We recommend making a user for your proot distro to avoid running everything as root. Below shows xscreensaver running on a proot-distro with the Scooter screensaver that we have backported six years ago.

#Android #Linux #news #oneUi #smartphone #Tech #Technology #Termux #TigerVNC #Ubuntu #update

Installing TigerVNC Server on Ubuntu proot-distro on Termux in Android

Termux provides a way to install a proot distro for several popular Linux distributions, such as Arch Linux, Ubuntu, and Fedora. In Android devices, you can make use of one of the proot distributions to run your favorite Linux programs, if they don’t work on a normal Termux environment.

We have used a Ubuntu proot distribution to do what we’re going to do in this article, which is installing and configuring TigerVNC on your proot distribution installation on your Android device. It’s best experienced with a large tablet, more preferrably a powerful tablet, with a 64-bit ARM processor and a latest version of Android.

Before you start following the installation steps, you’ll need to disable background restrictions for child processes, assuming that you’re running the latest version of Android with Developer Options enabled. Make sure that “Disable child process restrictions” is enabled, just like below:

After that, you can follow the below steps:

First, install the Ubuntu proot distribution by opening Termux and using proot-distro install ubuntu. After that, log in to the distribution using proot-distro login ubuntu and refresh the package database using apt update.

After the database gets updated, we recommend that you run apt dist-upgrade to make sure that all packages get updated. Afterwards, you can now run apt install tigervnc-standalone-server awesome to install both the TigerVNC Server and the Awesome window manager.

It depends on both your device performance and your internet connection speed, and it may take some time. Afterwards, you should see the following:

Then, start the VNC server using the vncserver command.

Afterwards, download a VNC client app for Android. For instance, we have used RealVNC Viewer to establish the connection to the local VNC server. Add a new connection using the appropriate port that is connected to the mentioned display. For example, we have started the VNC server on display :2, so the port is 5902. Specify the IP address of the local host, such as 127.0.0.1:5902.

Afterwards, press the Connect button at the bottom.

Then, use the same password that you’ve used when you first set up the VNC server.

Afterwards, the VNC display shows up, and the Awesome window manager shows up.

However, the default configuration didn’t match our tablet’s resolution, so you might see blurry display, depending on the device. As a result, we’ll have to kill the VNC server using vncserver -kill :2, and adjust your display number. You can list VNC servers using vncserver -list.

Another problem is that we haven’t installed the terminal emulator. To solve this, you can install a terminal emulator, and we’ll use QTerminal here, using apt install qterminal. However, according to our tests, some terminal emulators don’t work and crash with “Illegal instruction”, such as zutty, kitty, and alacritty.

After the installation of the terminal emulator completes, it’s time to configure our VNC server to match the tablet’s resolution in landscape mode. For example, our tablet’s resolution is 2560×1600 in landscape mode, so we need to create a new file called ~/.config/tigervnc/config to add a new line, geometry=2560x1600, to it. This tells TigerVNC to start the X11 server using 2560×1600 as the resolution. Adapt the screen resolution according to your device’s specifications, such as 2960×1848 for the Galaxy Tab S11 Ultra in landscape mode.

After that, start the VNC server. Now, text, images, and other elements will appear smooth and crisp.

This is further confirmed by opening the connection information. RealVNC Viewer told us that the display size has been set to the resolution that we’ve configured in the abovementioned configuration file.

The other problem we need to solve is that the image quality in the VNC client has been automatically set to the lowest quality possible, which means that we’re losing color, which is unattractive. Fortunately, since we’re on a localhost connection, we can achieve high performance with high quality image by scrolling to Picture Quality and selecting High.

As a result, the VNC display has become much better than before, while maintaining high performance.

However, depending on the DPI of your device, elements may appear very tiny. For example, on our Galaxy Tab S8 that sports the ~274 PPI display, you can read the text only if you zoom in to the text that you want to read, which is inconvenient. In this case, QTerminal appears to be small, because, by default, 96 DPI is used.

To fix this, we’ll need to modify two files: .profile and .Xresources under the home directory. Let’s modify them like this:

• In the .Xresources file, add a single line “Xft.dpi: 274“. You can simplify that by executing the “echo "Xft.dpi: 274" >> ~/.Xresources” command. Adapt this configuration according to your device DPI, such as 239 for the Galaxy Tab S11 Ultra.
• In the .profile file, add the following lines:
  • export QT_AUTO_SCREEN_SCALE_FACTOR=0
  • export QT_SCALE_FACTOR=1
  • export QT_FONT_DPI=225
• Adapt the QT_FONT_DPI environment variable to point to your device DPI, subtracting 50 from it. However, adjust the DPI value to make Qt windows large, as needed. You can use the same command mentioned above, like “echo "export QT_FONT_DPI=225" >> ~/.profile“.

In case you’re using GNOME or GTK apps, make sure that you can use the gsettings command. Afterwards, adjust the following commands (scaling-factor 2 and text-scaling-factor 0.75) until the GTK apps look big enough:

$ gsettings set org.gnome.desktop.interface scaling-factor 2$ gsettings set org.gnome.desktop.interface text-scaling-factor 0.75

Afterwards, start the VNC server.

Once you start the VNC server, the UI elements should become large enough to be readable for you, adjusted to your device’s scaling factor. For example, QTerminal now looks big.

That’s it! Your VNC server has been finally configured!

Bonus 1: you can install PulseAudio on the Termux environment outside proot-distro using pkg install pulseaudio. Afterwards, run the following command:

$ pkill pulseaudio$ pulseaudio --start --load="module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1" --exit-idle-time=-1

If your audio doesn’t work, or if pactl list shows that the null driver is being used, stop the PulseAudio server using pulseaudio -k, then execute the below command (note the LD_PRELOAD environment variable):

$ pkill pulseaudio$ LD_PRELOAD=/system/lib64/libskcodec.so pulseaudio --start --load="module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1" --exit-idle-time=-1

Now, when you list devices running on PulseAudio, you should see:

After that, go to inside the proot-distro environment and install Audacious to test PulseAudio using apt install audacious. Then, start the VNC server, open Audacious, and add your favorite music by going to /storage/emulated/0 and navigating to your music library folder. After that, raise your tablet’s volume and sound should come out from your tablet’s speakers. A working sound configuration will be like this (with neofetch installed with apt install fastfetch):

Bonus 2: Since Audacious supports playing online radio stations (Icecast or SHOUTcast) effortlessly without having to use dedicated Android apps, you can use it to play your favorite online radio station according to your taste, such as AH.FM, which plays trance and other EDM music. Although this radio station has a dedicated app for phones, you can use Audacious to stream it.

Bonus 3: You can make a new user using adduser <name>, replacing <name> with your desired username. Then, log out of the proot-distro environment and log in with your user using proot-distro login ubuntu --user <name>. You’ll have to retry the UI and VNC scaling configuration steps. This is required for applications and daemons, such as xscreensaver, that may forbid logging in as root. For example, xscreensaver refuses to run on root, so this is required to be able to run. We recommend making a user for your proot distro to avoid running everything as root. Below shows xscreensaver running on a proot-distro with the Scooter screensaver that we have ported from xlockmore six years ago.

#Android #Linux #news #oneUi #smartphone #Tech #Technology #Termux #TigerVNC #Ubuntu #update

Installing TigerVNC Server on Ubuntu proot-distro on Termux in Android

Termux provides a way to install a proot distro for several popular Linux distributions, such as Arch Linux, Ubuntu, and Fedora. In Android devices, you can make use of one of the proot distributions to run your favorite Linux programs, if they don’t work on a normal Termux environment.

We have used a Ubuntu proot distribution to do what we’re going to do in this article, which is installing and configuring TigerVNC on your proot distribution installation on your Android device. It’s best experienced with a large tablet, more preferrably a powerful tablet, with a 64-bit ARM processor and a latest version of Android.

Before you start following the installation steps, you’ll need to disable background restrictions for child processes, assuming that you’re running the latest version of Android with Developer Options enabled. Make sure that “Disable child process restrictions” is enabled, just like below:

After that, you can follow the below steps:

First, install the Ubuntu proot distribution by opening Termux and using proot-distro install ubuntu. After that, log in to the distribution using proot-distro login ubuntu and refresh the package database using apt update.

After the database gets updated, we recommend that you run apt dist-upgrade to make sure that all packages get updated. Afterwards, you can now run apt install tigervnc-standalone-server awesome to install both the TigerVNC Server and the Awesome window manager.

It depends on both your device performance and your internet connection speed, and it may take some time. Afterwards, you should see the following:

Then, start the VNC server using the vncserver command.

Afterwards, download a VNC client app for Android. For instance, we have used RealVNC Viewer to establish the connection to the local VNC server. Add a new connection using the appropriate port that is connected to the mentioned display. For example, we have started the VNC server on display :2, so the port is 5902. Specify the IP address of the local host, such as 127.0.0.1:5902.

Afterwards, press the Connect button at the bottom.

Then, use the same password that you’ve used when you first set up the VNC server.

Afterwards, the VNC display shows up, and the Awesome window manager shows up.

However, the default configuration didn’t match our tablet’s resolution, so you might see blurry display, depending on the device. As a result, we’ll have to kill the VNC server using vncserver -kill :2, and adjust your display number. You can list VNC servers using vncserver -list.

Another problem is that we haven’t installed the terminal emulator. To solve this, you can install a terminal emulator, and we’ll use QTerminal here, using apt install qterminal. However, according to our tests, some terminal emulators don’t work and crash with “Illegal instruction”, such as zutty, kitty, and alacritty.

After the installation of the terminal emulator completes, it’s time to configure our VNC server to match the tablet’s resolution in landscape mode. For example, our tablet’s resolution is 2560×1600 in landscape mode, so we need to create a new file called ~/.config/tigervnc/config to add a new line, geometry=2560x1600, to it. This tells TigerVNC to start the X11 server using 2560×1600 as the resolution. Adapt the screen resolution according to your device’s specifications, such as 2960×1848 for the Galaxy Tab S11 Ultra in landscape mode.

After that, start the VNC server. Now, text, images, and other elements will appear smooth and crisp.

This is further confirmed by opening the connection information. RealVNC Viewer told us that the display size has been set to the resolution that we’ve configured in the abovementioned configuration file.

The other problem we need to solve is that the image quality in the VNC client has been automatically set to the lowest quality possible, which means that we’re losing color, which is unattractive. Fortunately, since we’re on a localhost connection, we can achieve high performance with high quality image by scrolling to Picture Quality and selecting High.

As a result, the VNC display has become much better than before, while maintaining high performance.

However, depending on the DPI of your device, elements may appear very tiny. For example, on our Galaxy Tab S8 that sports the ~274 PPI display, you can read the text only if you zoom in to the text that you want to read, which is inconvenient. In this case, QTerminal appears to be small, because, by default, 96 DPI is used.

To fix this, we’ll need to modify two files: .profile and .Xresources under the home directory. Let’s modify them like this:

• In the .Xresources file, add a single line “Xft.dpi: 274“. You can simplify that by executing the “echo "Xft.dpi: 274" >> ~/.Xresources” command. Adapt this configuration according to your device DPI, such as 239 for the Galaxy Tab S11 Ultra.
• In the .profile file, add the following lines:
  • export QT_AUTO_SCREEN_SCALE_FACTOR=0
  • export QT_SCALE_FACTOR=1
  • export QT_FONT_DPI=225
• Adapt the QT_FONT_DPI environment variable to point to your device DPI, subtracting 50 from it. However, adjust the DPI value to make Qt windows large, as needed. You can use the same command mentioned above, like “echo "export QT_FONT_DPI=225" >> ~/.profile“.

In case you’re using GNOME or GTK apps, make sure that you can use the gsettings command. Afterwards, adjust the following commands (scaling-factor 2 and text-scaling-factor 0.75) until the GTK apps look big enough:

$ gsettings set org.gnome.desktop.interface scaling-factor 2$ gsettings set org.gnome.desktop.interface text-scaling-factor 0.75

Afterwards, start the VNC server.

Once you start the VNC server, the UI elements should become large enough to be readable for you, adjusted to your device’s scaling factor. For example, QTerminal now looks big.

That’s it! Your VNC server has been finally configured!

Bonus 1: you can install PulseAudio on the Termux environment outside proot-distro using pkg install pulseaudio. Afterwards, run the following command:

$ pkill pulseaudio$ pulseaudio --start --load="module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1" --exit-idle-time=-1

If your audio doesn’t work, or if pactl list shows that the null driver is being used, stop the PulseAudio server using pulseaudio -k, then execute the below command (note the LD_PRELOAD environment variable):

$ pkill pulseaudio$ LD_PRELOAD=/system/lib64/libskcodec.so pulseaudio --start --load="module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1" --exit-idle-time=-1

Now, when you list devices running on PulseAudio, you should see:

After that, go to inside the proot-distro environment and install Audacious to test PulseAudio using apt install audacious. Then, start the VNC server, open Audacious, and add your favorite music by going to /storage/emulated/0 and navigating to your music library folder. After that, raise your tablet’s volume and sound should come out from your tablet’s speakers. A working sound configuration will be like this (with neofetch installed with apt install fastfetch):

Bonus 2: Since Audacious supports playing online radio stations (Icecast or SHOUTcast) effortlessly without having to use dedicated Android apps, you can use it to play your favorite online radio station according to your taste, such as AH.FM, which plays trance and other EDM music. Although this radio station has a dedicated app for phones, you can use Audacious to stream it.

Bonus 3: You can make a new user using adduser <name>, replacing <name> with your desired username. Then, log out of the proot-distro environment and log in with your user using proot-distro login ubuntu --user <name>. You’ll have to retry the UI and VNC scaling configuration steps. This is required for applications and daemons, such as xscreensaver, that may forbid logging in as root. For example, xscreensaver refuses to run on root, so this is required to be able to run. We recommend making a user for your proot distro to avoid running everything as root. Below shows xscreensaver running on a proot-distro with the Scooter screensaver that we have ported from xlockmore six years ago.

#Android #Linux #news #oneUi #smartphone #Tech #Technology #Termux #TigerVNC #Ubuntu #update

Installing TigerVNC Server on Ubuntu proot-distro on Termux in Android

Termux provides a way to install a proot distro for several popular Linux distributions, such as Arch Linux, Ubuntu, and Fedora. In Android devices, you can make use of one of the proot distributions to run your favorite Linux programs, if they don’t work on a normal Termux environment.

We have used a Ubuntu proot distribution to do what we’re going to do in this article, which is installing and configuring TigerVNC on your proot distribution installation on your Android device. It’s best experienced with a large tablet, more preferrably a powerful tablet, with a 64-bit ARM processor and a latest version of Android.

Before you start following the installation steps, you’ll need to disable background restrictions for child processes, assuming that you’re running the latest version of Android with Developer Options enabled. Make sure that “Disable child process restrictions” is enabled, just like below:

After that, you can follow the below steps:

First, install the Ubuntu proot distribution by opening Terminaux and using proot-distro install ubuntu. After that, log in to the distribution using proot-distro login ubuntu and refresh the package database using apt update.

After the database gets updated, we recommend that you run apt dist-upgrade to make sure that all packages get updated. Afterwards, you can now run apt install tigervnc-standalone-server awesome to install both the TigerVNC Server and the Awesome window manager.

It depends on both your device performance and your internet connection speed, and it may take some time. Afterwards, you should see the following:

Then, start the VNC server using the vncserver command.

Afterwards, download a VNC client app for Android. For instance, we have used RealVNC Viewer to establish the connection to the local VNC server. Add a new connection using the appropriate port that is connected to the mentioned display. For example, we have started the VNC server on display :2, so the port is 5902. Specify the IP address of the local host, such as 127.0.0.1:5902.

Afterwards, press the Connect button at the bottom.

Then, use the same password that you’ve used when you first set up the VNC server.

Afterwards, the VNC display shows up, and the Awesome window manager shows up.

However, the default configuration didn’t match our tablet’s resolution, so you might see blurry display, depending on the device. As a result, we’ll have to kill the VNC server using vncserver -kill :2, and adjust your display number. You can list VNC servers using vncserver -list.

Another problem is that we haven’t installed the terminal emulator. To solve this, you can install a terminal emulator, and we’ll use QTerminal here, using apt install qterminal. However, according to our tests, some terminal emulators don’t work and crash with “Illegal instruction”, such as zutty, kitty, and alacritty.

After the installation of the terminal emulator completes, it’s time to configure our VNC server to match the tablet’s resolution in landscape mode. For example, our tablet’s resolution is 2560×1600 in landscape mode, so we need to create a new file called ~/.config/tigervnc/config to add a new line, geometry=2560x1600, to it. This tells TigerVNC to start the X11 server using 2560×1600 as the resolution. Adapt the screen resolution according to your device’s specifications, such as 2960×1848 for the Galaxy Tab S11 Ultra in landscape mode.

After that, start the VNC server. Now, text, images, and other elements will appear smooth and crisp.

This is further confirmed by opening the connection information. RealVNC Viewer told us that the display size has been set to the resolution that we’ve configured in the abovementioned configuration file.

The other problem we need to solve is that the image quality in the VNC client has been automatically set to the lowest quality possible, which means that we’re losing color, which is unattractive. Fortunately, since we’re on a localhost connection, we can achieve high performance with high quality image by scrolling to Picture Quality and selecting High.

As a result, the VNC display has become much better than before, while maintaining high performance.

However, depending on the DPI of your device, elements may appear very tiny. For example, on our Galaxy Tab S8 that sports the ~274 PPI display, you can read the text only if you zoom in to the text that you want to read, which is inconvenient. In this case, QTerminal appears to be small, because, by default, 96 DPI is used.

To fix this, we’ll need to modify two files: .profile and .Xresources under the home directory. Let’s modify them like this:

• In the .Xresources file, add a single line “Xft.dpi: 274“. You can simplify that by executing the “echo "Xft.dpi: 274" >> ~/.Xresources” command. Adapt this configuration according to your device DPI, such as 239 for the Galaxy Tab S11 Ultra.
• In the .profile file, add the following lines:
  • export QT_AUTO_SCREEN_SCALE_FACTOR=0
  • export QT_SCALE_FACTOR=1
  • export QT_FONT_DPI=225
• Adapt the QT_FONT_DPI environment variable to point to your device DPI, subtracting 50 from it. However, adjust the DPI value to make Qt windows large, as needed. You can use the same command mentioned above, like “echo "export QT_FONT_DPI=225" >> ~/.profile“.

In case you’re using GNOME or GTK apps, make sure that you can use the gsettings command. Afterwards, adjust the following commands (scaling-factor 2 and text-scaling-factor 0.75) until the GTK apps look big enough:

$ gsettings set org.gnome.desktop.interface scaling-factor 2$ gsettings set org.gnome.desktop.interface text-scaling-factor 0.75

Afterwards, start the VNC server.

Once you start the VNC server, the UI elements should become large enough to be readable for you, adjusted to your device’s scaling factor. For example, QTerminal now looks big.

That’s it! Your VNC server has been finally configured!

Bonus 1: you can install PulseAudio on the Termux environment outside proot-distro using pkg install pulseaudio. Afterwards, run the following command:

$ pkill pulseaudio$ pulseaudio --start --load="module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1" --exit-idle-time=-1

If your audio doesn’t work, or if pactl list shows that the null driver is being used, stop the PulseAudio server using pulseaudio -k, then execute the below command (note the LD_PRELOAD environment variable):

$ pkill pulseaudio$ LD_PRELOAD=/system/lib64/libskcodec.so pulseaudio --start --load="module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1" --exit-idle-time=-1

Now, when you list devices running on PulseAudio, you should see:

After that, go to inside the proot-distro environment and install Audacious to test PulseAudio using apt install audacious. Then, start the VNC server, open Audacious, and add your favorite music by going to /storage/emulated/0 and navigating to your music library folder. After that, raise your tablet’s volume and sound should come out from your tablet’s speakers. A working sound configuration will be like this (with neofetch installed with apt install fastfetch):

Bonus 2: Since Audacious supports playing online radio stations (Icecast or SHOUTcast) effortlessly without having to use dedicated Android apps, you can use it to play your favorite online radio station according to your taste, such as AH.FM, which plays trance and other EDM music. Although this radio station has a dedicated app for phones, you can use Audacious to stream it.

Bonus 3: You can make a new user using adduser <name>, replacing <name> with your desired username. Then, log out of the proot-distro environment and log in with your user using proot-distro login ubuntu --user <name>. You’ll have to retry the UI and VNC scaling configuration steps. This is required for applications and daemons, such as xscreensaver, that may forbid logging in as root. For example, xscreensaver refuses to run on root, so this is required to be able to run. We recommend making a user for your proot distro to avoid running everything as root. Below shows xscreensaver running on a proot-distro with the Scooter screensaver that we have backported six years ago.

#Android #Linux #news #oneUi #smartphone #Tech #Technology #Termux #TigerVNC #Ubuntu #update

Installing TigerVNC Server on Ubuntu proot-distro on Termux in Android

Termux provides a way to install a proot distro for several popular Linux distributions, such as Arch Linux, Ubuntu, and Fedora. In Android devices, you can make use of one of the proot distributions to run your favorite Linux programs, if they don’t work on a normal Termux environment.

We have used a Ubuntu proot distribution to do what we’re going to do in this article, which is installing and configuring TigerVNC on your proot distribution installation on your Android device. It’s best experienced with a large tablet, more preferrably a powerful tablet, with a 64-bit ARM processor and a latest version of Android.

Before you start following the installation steps, you’ll need to disable background restrictions for child processes, assuming that you’re running the latest version of Android with Developer Options enabled. Make sure that “Disable child process restrictions” is enabled, just like below:

After that, you can follow the below steps:

First, install the Ubuntu proot distribution by opening Termux and using proot-distro install ubuntu. After that, log in to the distribution using proot-distro login ubuntu and refresh the package database using apt update.

After the database gets updated, we recommend that you run apt dist-upgrade to make sure that all packages get updated. Afterwards, you can now run apt install tigervnc-standalone-server awesome to install both the TigerVNC Server and the Awesome window manager.

It depends on both your device performance and your internet connection speed, and it may take some time. Afterwards, you should see the following:

Then, start the VNC server using the vncserver command.

Afterwards, download a VNC client app for Android. For instance, we have used RealVNC Viewer to establish the connection to the local VNC server. Add a new connection using the appropriate port that is connected to the mentioned display. For example, we have started the VNC server on display :2, so the port is 5902. Specify the IP address of the local host, such as 127.0.0.1:5902.

Afterwards, press the Connect button at the bottom.

Then, use the same password that you’ve used when you first set up the VNC server.

Afterwards, the VNC display shows up, and the Awesome window manager shows up.

However, the default configuration didn’t match our tablet’s resolution, so you might see blurry display, depending on the device. As a result, we’ll have to kill the VNC server using vncserver -kill :2, and adjust your display number. You can list VNC servers using vncserver -list.

Another problem is that we haven’t installed the terminal emulator. To solve this, you can install a terminal emulator, and we’ll use QTerminal here, using apt install qterminal. However, according to our tests, some terminal emulators don’t work and crash with “Illegal instruction”, such as zutty, kitty, and alacritty.

After the installation of the terminal emulator completes, it’s time to configure our VNC server to match the tablet’s resolution in landscape mode. For example, our tablet’s resolution is 2560×1600 in landscape mode, so we need to create a new file called ~/.config/tigervnc/config to add a new line, geometry=2560x1600, to it. This tells TigerVNC to start the X11 server using 2560×1600 as the resolution. Adapt the screen resolution according to your device’s specifications, such as 2960×1848 for the Galaxy Tab S11 Ultra in landscape mode.

After that, start the VNC server. Now, text, images, and other elements will appear smooth and crisp.

This is further confirmed by opening the connection information. RealVNC Viewer told us that the display size has been set to the resolution that we’ve configured in the abovementioned configuration file.

The other problem we need to solve is that the image quality in the VNC client has been automatically set to the lowest quality possible, which means that we’re losing color, which is unattractive. Fortunately, since we’re on a localhost connection, we can achieve high performance with high quality image by scrolling to Picture Quality and selecting High.

As a result, the VNC display has become much better than before, while maintaining high performance.

However, depending on the DPI of your device, elements may appear very tiny. For example, on our Galaxy Tab S8 that sports the ~274 PPI display, you can read the text only if you zoom in to the text that you want to read, which is inconvenient. In this case, QTerminal appears to be small, because, by default, 96 DPI is used.

To fix this, we’ll need to modify two files: .profile and .Xresources under the home directory. Let’s modify them like this:

• In the .Xresources file, add a single line “Xft.dpi: 274“. You can simplify that by executing the “echo "Xft.dpi: 274" >> ~/.Xresources” command. Adapt this configuration according to your device DPI, such as 239 for the Galaxy Tab S11 Ultra.
• In the .profile file, add the following lines:
  • export QT_AUTO_SCREEN_SCALE_FACTOR=0
  • export QT_SCALE_FACTOR=1
  • export QT_FONT_DPI=225
• Adapt the QT_FONT_DPI environment variable to point to your device DPI, subtracting 50 from it. However, adjust the DPI value to make Qt windows large, as needed. You can use the same command mentioned above, like “echo "export QT_FONT_DPI=225" >> ~/.profile“.

In case you’re using GNOME or GTK apps, make sure that you can use the gsettings command. Afterwards, adjust the following commands (scaling-factor 2 and text-scaling-factor 0.75) until the GTK apps look big enough:

$ gsettings set org.gnome.desktop.interface scaling-factor 2$ gsettings set org.gnome.desktop.interface text-scaling-factor 0.75

Afterwards, start the VNC server.

Once you start the VNC server, the UI elements should become large enough to be readable for you, adjusted to your device’s scaling factor. For example, QTerminal now looks big.

That’s it! Your VNC server has been finally configured!

Bonus 1: you can install PulseAudio on the Termux environment outside proot-distro using pkg install pulseaudio. Afterwards, run the following command:

$ pkill pulseaudio$ pulseaudio --start --load="module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1" --exit-idle-time=-1

If your audio doesn’t work, or if pactl list shows that the null driver is being used, stop the PulseAudio server using pulseaudio -k, then execute the below command (note the LD_PRELOAD environment variable):

$ pkill pulseaudio$ LD_PRELOAD=/system/lib64/libskcodec.so pulseaudio --start --load="module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1" --exit-idle-time=-1

Now, when you list devices running on PulseAudio, you should see:

After that, go to inside the proot-distro environment and install Audacious to test PulseAudio using apt install audacious. Then, start the VNC server, open Audacious, and add your favorite music by going to /storage/emulated/0 and navigating to your music library folder. After that, raise your tablet’s volume and sound should come out from your tablet’s speakers. A working sound configuration will be like this (with neofetch installed with apt install fastfetch):

Bonus 2: Since Audacious supports playing online radio stations (Icecast or SHOUTcast) effortlessly without having to use dedicated Android apps, you can use it to play your favorite online radio station according to your taste, such as AH.FM, which plays trance and other EDM music. Although this radio station has a dedicated app for phones, you can use Audacious to stream it.

Bonus 3: You can make a new user using adduser <name>, replacing <name> with your desired username. Then, log out of the proot-distro environment and log in with your user using proot-distro login ubuntu --user <name>. You’ll have to retry the UI and VNC scaling configuration steps. This is required for applications and daemons, such as xscreensaver, that may forbid logging in as root. For example, xscreensaver refuses to run on root, so this is required to be able to run. We recommend making a user for your proot distro to avoid running everything as root. Below shows xscreensaver running on a proot-distro with the Scooter screensaver that we have ported from xlockmore six years ago.

#Android #Linux #news #oneUi #smartphone #Tech #Technology #Termux #TigerVNC #Ubuntu #update

#Troubleshooting #TigerVNC Server: on #Termux

If you try to start your #VNC #server on Termux, but get the following error:
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5905
vncext: Created VNC server for screen 0
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
(EE)
Fatal server error:
(EE) Failed to activate virtual core keyboard: 2(EE)

Try the solution at:
https://github.com/termux/termux-packages/issues/25005#issuecomment-2955984775

#Troubleshooting #TigerVNC Server: on #Termux

If you try to start your #VNC #server on Termux, but get the following error:
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5905
vncext: Created VNC server for screen 0
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
(EE)
Fatal server error:
(EE) Failed to activate virtual core keyboard: 2(EE)

Try the solution at:
https://github.com/termux/termux-packages/issues/25005#issuecomment-2955984775

#TigerVNC 1.15.0 has been released (#TightVNC / #VNC / #VirtualNetworkComputing / #RFB / #RemoteFrameBuffer / #RemoteDesktopSoftware / #RemoteDesktop) https://tigervnc.org/

#TigerVNC 1.15.0 has been released (#TightVNC / #VNC / #VirtualNetworkComputing / #RFB / #RemoteFrameBuffer / #RemoteDesktopSoftware / #RemoteDesktop) https://tigervnc.org/

#TigerVNC 1.15.0 has been released (#TightVNC / #VNC / #VirtualNetworkComputing / #RFB / #RemoteFrameBuffer / #RemoteDesktopSoftware / #RemoteDesktop) https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.15.0. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.15.0. https://tigervnc.org/

TigerVNC Team released #TigerVNC version 1.15.0. https://tigervnc.org/

TigerVNC 1.14.1 fixes critical bugs, including VncAuth handling and improved viewer compatibility with RealVNC servers.
https://linuxiac.com/tigervnc-1-14-1-released/

#tigervnc #vnc #remotedesktop

TigerVNC 1.14.1 fixes critical bugs, including VncAuth handling and improved viewer compatibility with RealVNC servers.
https://linuxiac.com/tigervnc-1-14-1-released/

#tigervnc #vnc #remotedesktop

TigerVNC 1.14.1 fixes critical bugs, including VncAuth handling and improved viewer compatibility with RealVNC servers.
https://linuxiac.com/tigervnc-1-14-1-released/

#tigervnc #vnc #remotedesktop

TigerVNC 1.14.1 fixes critical bugs, including VncAuth handling and improved viewer compatibility with RealVNC servers.
https://linuxiac.com/tigervnc-1-14-1-released/

#tigervnc #vnc #remotedesktop

TigerVNC 1.14.1 fixes critical bugs, including VncAuth handling and improved viewer compatibility with RealVNC servers.
https://linuxiac.com/tigervnc-1-14-1-released/

#tigervnc #vnc #remotedesktop

Bye, bye, #Remmina, fue hermoso mientras duró... Y duró hasta que te encajonaron en las #GtkCsd :nc_sad:

¡Hola #TigerVNC (`tigervnc-viewer`)! Qué bonitas opciones de línea de comandos tienes, tan flexibles, tan adaptables a cualquier entorno de escritorio... ¿A qué hora sales por el pan? :nc_wink_blep: