From bob at proulx.com Mon Feb 3 06:29:55 2025 From: bob at proulx.com (Bob Proulx) Date: Sun, 2 Feb 2025 23:29:55 -0700 Subject: Elliptical Curves In-Reply-To: <0386d1df-11dc-41fe-811a-f794c4997cbd@basz.org> References: <0386d1df-11dc-41fe-811a-f794c4997cbd@basz.org> Message-ID: <20250202232936980203106@bob.proulx.com> Baszler wrote: > Reading Quanta mag I found an interesting site that someone has done a very > good explanation of Elliptical curves with pretty pictures and animations. > It even has an example how the TLS 1.3 does the key exchange (but in a > graphical and simple format) > > https://curves.xargs.org I finally got around to looking at this site. Pretty cool! Thanks for sharing! Bob From jdewitt.nclug at gmail.com Sun Feb 9 21:17:50 2025 From: jdewitt.nclug at gmail.com (j dewitt) Date: Sun, 9 Feb 2025 14:17:50 -0700 Subject: Tuesday February 11th, 2024 NCLUG Meeting Message-ID: What: Tuesday February 11th, 2024 NCLUG Meeting When: Tuesday February 11th, 2024, 6pm Where: Fort Collins Creator Hub, 1304 Duff Dr Unit 15, Fort Collins, CO; map: https://maps.google.com/maps?f=q&hl=en&q=1304+Duff+Dr+Unit+15%2C+Fort+Collins%2C+CO%2C+us Please join us Tuesday at the Collins Creator Hub Crafting area, 1304 Duff Dr Unit 15, Fort Collins, CO 80524. Topic: Short Topics Please come and tell us about a project, tech topic, or problem that interests you in around 10 minutes. Quick demos are a plus! If you have a Linux related topic, short or long, that you would like to present in a future meeting, please let us know. Following the meeting, please join us for food. Space for the meetings is generously provided by The Fort Collins Creator Hub. Thanks, FCCH! For more information about FCCH, please visit: http://www.fortcollinscreatorhub.org/ *Please note, if this is your first time at the Creator Hub, please read and sign the facility waiver at the front visitor desk. See you there, James DeWitt From c.brian.sturgill at gmail.com Tue Feb 11 23:33:48 2025 From: c.brian.sturgill at gmail.com (Brian Sturgill) Date: Tue, 11 Feb 2025 16:33:48 -0700 Subject: Kokoro addresses. Message-ID: I played with the Kokoro tts this week. I thought I would warn people about being careful about links on the web with kokoro in its name. Many of these are spyware sites. The correct addresses you want are: https://github.com/hexgrad/kokoro https://huggingface.co/hexgrad/Kokoro-82M Be aware that the pip install will not build correctly for ARM. Kokoro is disappointing on marginal hardware. -- Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob at proulx.com Wed Feb 12 02:52:10 2025 From: bob at proulx.com (Bob Proulx) Date: Tue, 11 Feb 2025 19:52:10 -0700 Subject: Tuesday February 11th, 2024 NCLUG Meeting In-Reply-To: References: Message-ID: <20250211181705992695221@bob.proulx.com> j dewitt wrote: > What: Tuesday February 11th, 2024 NCLUG Meeting Brian started our meeting off. Demonstrating TUI interfaces. There is a cool dialog creation tool called Textual. It's a really cool and very featureful tool that builds text terminal interfaces. Interfaces with what looks to the eye like graphics. Some of them looked like it was rendering graphs and images but it is all terminal based. Wow! But wait! There's more! In addition to creating truly amazing text terminal interfaces it can also generate HTML to create web pages from the same source. Can use it for terminal interfaces and also generate matching web pages for it. Cool stuff. Check it out! https://textual.textualize.io/ https://github.com/Textualize/rich https://github.com/ceccopierangiolieugenio/pyTermTk Morey started with a charity site for the Memphis City Zoo. If you are mad at someone you can have them print out a floor sign with their name on it and then they will take a video of an elephant pooping on it. Morey talked about AI. N8N. Node aware work flow automation. Visual Basic without the Visual Basic. But on steroids. Visual programming language. For AI things. Connect up multiple OpenAI instances so that multiple LLM ML engines are all talking to each other to create a larger machine. As a demo Morey spoke into the air and asked the machine to send a message to his friend Andy with a message to meet tomorrow at some time, and it listens and creates all of the needed things and out goes the message. Or it will go into their calendar. Or other targets. Bob talked about the 3 million strong botnet that is abusing the GNU Savannah git CGIT cgit.cgi human web rendering of git version control. It turns out that fail2ban with iptables just can't handle it. Around 100,000 entries things really grind. But enter "ipset" which is an additional utility that can be installed. Using ipset and it's database one can include 3 million addresses into the firewall and block them. Which is pretty amazing. But with 3 million bots strong it can hit once a day and still overwhelm you. To help to mitigate things I configured nginx to match the abuse pattern and then instead of routing the request to cgit.cgi as normal instead simply "return 400" immediately. That by itself helps to shed load from the system hugely. Nginx FTW! Morey talked about the new-ish downtown Fort Collins city co-working space. Related to us a meet he had there recently. He was at the co-working space and talked there about AI and gave us the demo he gave there. Use photos and images and AI to generate 3D models. Some very impressive 3D models created from images of houses, buildings, trees, foliage. Sy then got the project display hose. Sy has a couple of proxmox servers. Sy was not happy with the default interface to observe and configure new VMs. But templates can be used to improve the situation. Demonstrated a template with Zabbix monitoring configured. Can more easily set up VMs wth Zabbix montoring all ready to go. Sy demonstrated Zabbix. Can monitor all kinds of things. Can send alerts. Can create tickets. All fully FLOSS. https://en.wikipedia.org/wiki/Zabbix Dan introduced himself to the group. He told us a sad (and funny) story of his recent computer problems. His machine was broken, fixed, broken, then fixed. Decided to replace MS-Windows with GNU/Linux. Now is unable to unmute his microphone. A classic problem! The group think, primarily Stephen, worked on trying to make this work with most of us kibitzing but unfortunately we couldn't debug it immediately on the fly. From c.brian.sturgill at gmail.com Fri Feb 14 17:06:25 2025 From: c.brian.sturgill at gmail.com (Brian Sturgill) Date: Fri, 14 Feb 2025 10:06:25 -0700 Subject: 24-bit color in Linux command-line apps. Message-ID: For most Linux terminal apps, the answer is yes, 24-bit is supported. If you ssh in, you need to set an environment variable: export COLORTERM=truecolor https://github.com/Textualize/textual/discussions/3339 TERM is generally set to xterm-256color. Note, Textual still looks pretty good at 256 colors. -- Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: From microcraftx at gmail.com Tue Feb 18 22:20:40 2025 From: microcraftx at gmail.com (Phil Marsh) Date: Tue, 18 Feb 2025 14:20:40 -0800 Subject: Hi Bob question on getting TurboVNC running Message-ID: Hi Bob, I was wondering if you or anyone else could kindly help me with a problem using TurboVNC. If I log into my machine using Telnet and try to start TurboVNC from the command line it fails. The logfile is attached. I think these are the important lines showing the failure: Errors from xkbcomp are not fatal to the X server xstartup.turbovnc: Creating new session bus instance: xstartup.turbovnc: unix:path=/tmp/dbus-ATPDyrqwtE,guid=fa8e0d6a693c79d3511ff9b167b50124 xstartup.turbovnc: The session desktop file for the default window manager was xstartup.turbovnc: not found at: xstartup.turbovnc: /usr/share/xsessions/gnome.desktop xstartup.turbovnc: /usr/share/xsessions/ubuntu.desktop Thanks! Phil -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: carbontechlab:1.log Type: text/x-log Size: 3182 bytes Desc: not available URL: From microcraftx at gmail.com Tue Feb 18 22:25:25 2025 From: microcraftx at gmail.com (Phil Marsh) Date: Tue, 18 Feb 2025 14:25:25 -0800 Subject: Hi Bob question on getting TurboVNC running In-Reply-To: References: Message-ID: Also, if I start TurboVNC server on a terminal opened at consol (on my local monitor rather than Telnet) TurboVNC server starts and its logfile contains the text at the end: Errors from xkbcomp are not fatal to the X server xstartup.turbovnc: Creating new session bus instance: xstartup.turbovnc: unix:path=/tmp/dbus-XSpMzGYbFQ,guid=3749806eaf5c1e208f48a16467b507d6 xstartup.turbovnc: Using 'xubuntu' window manager in xstartup.turbovnc: /usr/share/xsessions/xubuntu.desktop xstartup.turbovnc: Executing /etc/X11/Xsession "startxfce4" I'm wondering why TurboVNC server fails to start in a Telnet terminal (using this over OpenVPN when I'm remote)? Thanks! Phil On Tue, Feb 18, 2025 at 2:20?PM Phil Marsh wrote: > Hi Bob, > I was wondering if you or anyone else could kindly help me with a problem > using TurboVNC. > If I log into my machine using Telnet and try to start TurboVNC from the > command line it fails. The logfile is attached. > I think these are the important lines showing the failure: > > Errors from xkbcomp are not fatal to the X server > xstartup.turbovnc: Creating new session bus instance: > xstartup.turbovnc: > unix:path=/tmp/dbus-ATPDyrqwtE,guid=fa8e0d6a693c79d3511ff9b167b50124 > xstartup.turbovnc: The session desktop file for the default window manager > was > xstartup.turbovnc: not found at: > xstartup.turbovnc: /usr/share/xsessions/gnome.desktop > xstartup.turbovnc: /usr/share/xsessions/ubuntu.desktop > > Thanks! > Phil > -------------- next part -------------- An HTML attachment was scrubbed... URL: From microcraftx at gmail.com Tue Feb 18 22:28:37 2025 From: microcraftx at gmail.com (Phil Marsh) Date: Tue, 18 Feb 2025 14:28:37 -0800 Subject: Hi Bob question on getting TurboVNC running In-Reply-To: References: Message-ID: This is Ubuntu 24.04. Oddly enough, thor, my server running Ubuntu 22.04 can start the TurboVNC server (vncserver) from a Telnet window. Thanks, Phil On Tue, Feb 18, 2025 at 2:25?PM Phil Marsh wrote: > Also, if I start TurboVNC server on a terminal opened at consol (on my > local monitor rather than Telnet) TurboVNC server starts and its logfile > contains the text at the end: > > Errors from xkbcomp are not fatal to the X server > xstartup.turbovnc: Creating new session bus instance: > xstartup.turbovnc: > unix:path=/tmp/dbus-XSpMzGYbFQ,guid=3749806eaf5c1e208f48a16467b507d6 > xstartup.turbovnc: Using 'xubuntu' window manager in > xstartup.turbovnc: /usr/share/xsessions/xubuntu.desktop > xstartup.turbovnc: Executing /etc/X11/Xsession "startxfce4" > > I'm wondering why TurboVNC server fails to start in a Telnet terminal > (using this over OpenVPN when I'm remote)? > Thanks! > Phil > > On Tue, Feb 18, 2025 at 2:20?PM Phil Marsh wrote: > >> Hi Bob, >> I was wondering if you or anyone else could kindly help me with a problem >> using TurboVNC. >> If I log into my machine using Telnet and try to start TurboVNC from the >> command line it fails. The logfile is attached. >> I think these are the important lines showing the failure: >> >> Errors from xkbcomp are not fatal to the X server >> xstartup.turbovnc: Creating new session bus instance: >> xstartup.turbovnc: >> unix:path=/tmp/dbus-ATPDyrqwtE,guid=fa8e0d6a693c79d3511ff9b167b50124 >> xstartup.turbovnc: The session desktop file for the default window >> manager was >> xstartup.turbovnc: not found at: >> xstartup.turbovnc: /usr/share/xsessions/gnome.desktop >> xstartup.turbovnc: /usr/share/xsessions/ubuntu.desktop >> >> Thanks! >> Phil >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From swarren-tag-list-nclug at wwwdotorg.org Wed Feb 19 00:18:43 2025 From: swarren-tag-list-nclug at wwwdotorg.org (Stephen Warren) Date: Tue, 18 Feb 2025 17:18:43 -0700 Subject: Hi Bob question on getting TurboVNC running In-Reply-To: References: Message-ID: <19812f2a-27e5-4427-8890-081139ede022@wwwdotorg.org> Perhaps it's trying to tell you to use ssh not telnet:-P Does TurboVNC run its own X server, or expect to connect to an existing console X session and screen-scrape it? If the latter, you'd need to set DISPLAY before running it. But since the logs mention "startxfce4" I guess it's starting its own session. In that case, I don't think there's enough log quoted to diagnose the problem. On 2/18/25 15:28, Phil Marsh wrote: > This is Ubuntu 24.04. > Oddly enough, thor,? my server running Ubuntu 22.04 can start the > TurboVNC server (vncserver) from a Telnet window. > Thanks, > Phil > > On Tue, Feb 18, 2025 at 2:25?PM Phil Marsh > wrote: > > Also, if I start TurboVNC server on a terminal opened at consol (on > my local monitor rather than Telnet) TurboVNC server starts and its > logfile contains the text at the end: > > Errors from xkbcomp are not fatal to the X server > xstartup.turbovnc: Creating new session bus instance: > xstartup.turbovnc: ? unix:path=/tmp/dbus- > XSpMzGYbFQ,guid=3749806eaf5c1e208f48a16467b507d6 > xstartup.turbovnc: Using 'xubuntu' window manager in > xstartup.turbovnc: ? /usr/share/xsessions/xubuntu.desktop > xstartup.turbovnc: Executing /etc/X11/Xsession "startxfce4" > > I'm wondering why TurboVNC server fails to start in a Telnet > terminal (using this over OpenVPN when I'm remote)? > Thanks! > Phil > > On Tue, Feb 18, 2025 at 2:20?PM Phil Marsh > wrote: > > Hi Bob, > I was wondering if you or anyone else could kindly help me with > a problem using TurboVNC. > If I log into my machine using Telnet and try to start TurboVNC > from the command line it fails. The logfile is attached. > I think these are the important lines showing the failure: > > Errors from xkbcomp are not fatal to the X server > xstartup.turbovnc: Creating new session bus instance: > xstartup.turbovnc: ? unix:path=/tmp/dbus- > ATPDyrqwtE,guid=fa8e0d6a693c79d3511ff9b167b50124 > xstartup.turbovnc: The session desktop file for the default > window manager was > xstartup.turbovnc: ? not found at: > xstartup.turbovnc: ? /usr/share/xsessions/gnome.desktop > xstartup.turbovnc: ? /usr/share/xsessions/ubuntu.desktop > > Thanks! > Phil > From microcraftx at gmail.com Wed Feb 19 00:37:16 2025 From: microcraftx at gmail.com (Phil Marsh) Date: Tue, 18 Feb 2025 16:37:16 -0800 Subject: Hi Bob question on getting TurboVNC running In-Reply-To: <19812f2a-27e5-4427-8890-081139ede022@wwwdotorg.org> References: <19812f2a-27e5-4427-8890-081139ede022@wwwdotorg.org> Message-ID: Hi Stephen, Thanks. However, my other server's TurboVNC starts OK using a Telnet terminal window. Thanks, Phil On Tue, Feb 18, 2025 at 4:19?PM Stephen Warren < swarren-tag-list-nclug at wwwdotorg.org> wrote: > Perhaps it's trying to tell you to use ssh not telnet:-P > > Does TurboVNC run its own X server, or expect to connect to an existing > console X session and screen-scrape it? If the latter, you'd need to set > DISPLAY before running it. But since the logs mention "startxfce4" I > guess it's starting its own session. In that case, I don't think there's > enough log quoted to diagnose the problem. > > On 2/18/25 15:28, Phil Marsh wrote: > > This is Ubuntu 24.04. > > Oddly enough, thor, my server running Ubuntu 22.04 can start the > > TurboVNC server (vncserver) from a Telnet window. > > Thanks, > > Phil > > > > On Tue, Feb 18, 2025 at 2:25?PM Phil Marsh > > wrote: > > > > Also, if I start TurboVNC server on a terminal opened at consol (on > > my local monitor rather than Telnet) TurboVNC server starts and its > > logfile contains the text at the end: > > > > Errors from xkbcomp are not fatal to the X server > > xstartup.turbovnc: Creating new session bus instance: > > xstartup.turbovnc: unix:path=/tmp/dbus- > > XSpMzGYbFQ,guid=3749806eaf5c1e208f48a16467b507d6 > > xstartup.turbovnc: Using 'xubuntu' window manager in > > xstartup.turbovnc: /usr/share/xsessions/xubuntu.desktop > > xstartup.turbovnc: Executing /etc/X11/Xsession "startxfce4" > > > > I'm wondering why TurboVNC server fails to start in a Telnet > > terminal (using this over OpenVPN when I'm remote)? > > Thanks! > > Phil > > > > On Tue, Feb 18, 2025 at 2:20?PM Phil Marsh > > wrote: > > > > Hi Bob, > > I was wondering if you or anyone else could kindly help me with > > a problem using TurboVNC. > > If I log into my machine using Telnet and try to start TurboVNC > > from the command line it fails. The logfile is attached. > > I think these are the important lines showing the failure: > > > > Errors from xkbcomp are not fatal to the X server > > xstartup.turbovnc: Creating new session bus instance: > > xstartup.turbovnc: unix:path=/tmp/dbus- > > ATPDyrqwtE,guid=fa8e0d6a693c79d3511ff9b167b50124 > > xstartup.turbovnc: The session desktop file for the default > > window manager was > > xstartup.turbovnc: not found at: > > xstartup.turbovnc: /usr/share/xsessions/gnome.desktop > > xstartup.turbovnc: /usr/share/xsessions/ubuntu.desktop > > > > Thanks! > > Phil > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From adj at fnord.greeley.co.us Wed Feb 19 02:17:31 2025 From: adj at fnord.greeley.co.us (Aaron D. Johnson) Date: Wed, 19 Feb 2025 02:17:31 +0000 Subject: Hi Bob question on getting TurboVNC running In-Reply-To: Your message of "Tue, 18 Feb 2025 16:37:16 -0800." Message-ID: <20250219021731.5DE3BF6E4@zarathud.internal.fnord.greeley.co.us> Phil Marsh writes: > Thanks. However, my other server's TurboVNC starts OK using a Telnet > terminal window. Stephen is on the right track here. The two servers' environments are different in a way that matters to TurboVNC. This may well include TurboVNC itself. Not a TurboVNC user myself, SSH X11 forwarding works for my use cases. But if I were stuck in your situation, I'd be starting out comparing the contents of the TurboVNC log files on server A and server B. Read them side by side... Use diff... There are plenty of tools for this. Also would be good to compare package lists between the two servers. And the process environment variables. Further question... It is 2025. Why are you using the plain text telnet protocol for any traffic between your computers? SSH has been a thing for 30 years now. (Well, almost... July 1995 was the first source release.) Key based authentication and not typing passwords is kinda nice. Join us in the 21st century... "ssh" is shorter to type than "telnet", too. - Aaron From microcraftx at gmail.com Wed Feb 19 06:22:16 2025 From: microcraftx at gmail.com (Phil Marsh) Date: Tue, 18 Feb 2025 22:22:16 -0800 Subject: Hi Bob question on getting TurboVNC running In-Reply-To: <20250219021731.5DE3BF6E4@zarathud.internal.fnord.greeley.co.us> References: <20250219021731.5DE3BF6E4@zarathud.internal.fnord.greeley.co.us> Message-ID: Hi Aaron, You're right, but I have no need for the encryption ssh provides because my connection is tunneled through OpenVPN and encryption just adds overhead. However, SSH also provides x11 forwarding which I don't get from Telnet of course. So it can make sense to use ssh through the OpenVPN tunnel anyway and I'll try that. If I use SSH as stand-alone, I'll be setting up a reverse SSH tunnel. However, I still don't understand why I can start the Turbo VNC server (command vncserver) from a Telnet terminal on my other machines (Ubuntu 22.04) but not on the Ubuntu 24.04 machine I've set up for a small company here in CA at UCI. If I could start the VNC server only on SSH, then I'd say that's the solution. It doesn't matter whether the Telnet terminal window is remote or running on the local machine as per the results. I'd be surprised if SSH helped here? Thanks, Phil On Tue, Feb 18, 2025 at 6:18?PM Aaron D. Johnson wrote: > Phil Marsh writes: > > Thanks. However, my other server's TurboVNC starts OK using a Telnet > > terminal window. > > Stephen is on the right track here. The two servers' environments are > different in a way that matters to TurboVNC. This may well include > TurboVNC itself. Not a TurboVNC user myself, SSH X11 forwarding works > for my use cases. But if I were stuck in your situation, I'd be > starting out comparing the contents of the TurboVNC log files on > server A and server B. Read them side by side... Use diff... There > are plenty of tools for this. > > Also would be good to compare package lists between the two servers. > And the process environment variables. > > Further question... It is 2025. Why are you using the plain text > telnet protocol for any traffic between your computers? SSH has been > a thing for 30 years now. (Well, almost... July 1995 was the first > source release.) Key based authentication and not typing passwords is > kinda nice. Join us in the 21st century... "ssh" is shorter to type > than "telnet", too. > > - Aaron > -------------- next part -------------- An HTML attachment was scrubbed... URL: From microcraftx at gmail.com Wed Feb 19 07:26:34 2025 From: microcraftx at gmail.com (Phil Marsh) Date: Tue, 18 Feb 2025 23:26:34 -0800 Subject: Hi Bob question on getting TurboVNC running In-Reply-To: References: <20250219021731.5DE3BF6E4@zarathud.internal.fnord.greeley.co.us> Message-ID: Hi Aaron, I tried issuing vncserver from an SSH terminal and the VNC server also failed to start. The ending lines of the unsuccessful logfile are: Errors from xkbcomp are not fatal to the X server xstartup.turbovnc: Creating new session bus instance: xstartup.turbovnc: unix:path=/tmp/dbus-AuF7HAlcQZ,guid=087f3dae01918291221bb56567b585ff xstartup.turbovnc: The session desktop file for the default window manager was xstartup.turbovnc: not found at: xstartup.turbovnc: /usr/share/xsessions/gnome.desktop xstartup.turbovnc: /usr/share/xsessions/ubuntu.desktop Killing Xvnc process ID 10292 ################# and the corresponding lines from a successful star of vncserver are: Errors from xkbcomp are not fatal to the X server xstartup.turbovnc: Creating new session bus instance: xstartup.turbovnc: unix:path=/tmp/dbus-NYBQm0ryxE,guid=5026c84f2da1c51e16cf0b0a67b5106e xstartup.turbovnc: Using 'xubuntu' window manager in xstartup.turbovnc: /usr/share/xsessions/xubuntu.desktop xstartup.turbovnc: Executing /etc/X11/Xsession "startxfce4" 18/02/2025 15:28:46 [1] Got connection from 10.8.2.1 on port 40626 18/02/2025 15:28:46 [1] Normal socket connection 18/02/2025 15:28:46 [1] Using protocol version 3.8 18/02/2025 15:28:46 [1] rfbSendSecurityTypeList: advertise sectype tight 18/02/2025 15:28:46 [1] Enabling TightVNC protocol extensions 18/02/2025 15:28:46 [1] Advertising Tight auth cap 'VNCAUTH_' 18/02/2025 15:28:56 [1] Full-control authentication enabled 18/02/2025 15:28:56 Number of connected clients: 1 18/02/2025 15:28:56 [1] Pixel format: 18/02/2025 15:28:56 [1] 32 bpp, depth 24, little endian 18/02/2025 15:28:56 [1] true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 18/02/2025 15:28:56 [1] no translation needed 18/02/2025 15:28:56 [1] Enabling Desktop Size protocol extension 18/02/2025 15:28:56 [1] Enabling Extended Desktop Size protocol extension 18/02/2025 15:28:56 [1] rfbProcessClientNormalMessage: ignoring unknown encoding -307 (fffffecd) 18/02/2025 15:28:56 [1] Enabling LastRect protocol extension 18/02/2025 15:28:56 [1] Enabling Continuous Updates protocol extension 18/02/2025 15:28:56 [1] Enabling Fence protocol extension 18/02/2025 15:28:56 [1] Enabling GII protocol extension 18/02/2025 15:28:56 [1] Using tight encoding 18/02/2025 15:28:56 [1] Enabling CopyRect encoding 18/02/2025 15:28:56 [1] Using JPEG subsampling 1, Q41 18/02/2025 15:28:56 [1] Using JPEG quality 25 18/02/2025 15:28:56 [1] Using JPEG subsampling 1 18/02/2025 15:28:56 [1] Using Tight compression level 1 18/02/2025 15:28:56 Using 4 threads for Tight encoding 18/02/2025 15:28:57 [1] Client supports GII version 1 18/02/2025 15:28:57 [1] GII Device Create: ELAN25B4:00 04F3:25B4 18/02/2025 15:28:57 [1] GII device ID = 1 18/02/2025 15:28:58 [1] Continuous updates enabled 18/02/2025 15:30:23 New desktop size: 3126 x 1707 18/02/2025 15:30:23 New screen layout: 18/02/2025 15:30:23 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 15:30:23 [1] Continuous updates enabled 18/02/2025 15:30:23 [1] Continuous updates enabled 18/02/2025 15:38:47 New desktop size: 3200 x 1707 18/02/2025 15:38:47 New screen layout: 18/02/2025 15:38:47 0x00000040 (output 0x00000040): 3200x1707+0+0 18/02/2025 15:38:47 [1] Continuous updates enabled 18/02/2025 15:38:47 [1] Continuous updates enabled 18/02/2025 16:38:13 New desktop size: 3126 x 1707 18/02/2025 16:38:13 New screen layout: 18/02/2025 16:38:13 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 16:38:13 [1] Continuous updates enabled 18/02/2025 16:38:13 [1] Continuous updates enabled 18/02/2025 16:45:51 New desktop size: 1240 x 900 18/02/2025 16:45:51 New screen layout: 18/02/2025 16:45:51 0x00000040 (output 0x00000040): 1240x900+0+0 18/02/2025 16:45:51 [1] Continuous updates enabled 18/02/2025 16:45:51 [1] Continuous updates enabled 18/02/2025 16:45:54 New desktop size: 3126 x 1707 18/02/2025 16:45:54 New screen layout: 18/02/2025 16:45:54 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 16:45:54 [1] Continuous updates enabled 18/02/2025 16:45:54 [1] Continuous updates enabled 18/02/2025 16:53:01 New desktop size: 3200 x 1707 18/02/2025 16:53:01 New screen layout: 18/02/2025 16:53:01 0x00000040 (output 0x00000040): 3200x1707+0+0 18/02/2025 16:53:01 [1] Continuous updates enabled 18/02/2025 16:53:01 [1] Continuous updates enabled 18/02/2025 17:14:28 New desktop size: 3126 x 1707 18/02/2025 17:14:28 New screen layout: 18/02/2025 17:14:28 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 17:14:28 [1] Continuous updates enabled 18/02/2025 17:14:28 [1] Continuous updates enabled 18/02/2025 17:19:41 New desktop size: 3200 x 1707 18/02/2025 17:19:41 New screen layout: 18/02/2025 17:19:41 0x00000040 (output 0x00000040): 3200x1707+0+0 18/02/2025 17:19:41 [1] Continuous updates enabled 18/02/2025 17:19:41 [1] Continuous updates enabled 18/02/2025 17:36:59 New desktop size: 3126 x 1707 18/02/2025 17:36:59 New screen layout: 18/02/2025 17:36:59 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 17:36:59 [1] Continuous updates enabled 18/02/2025 17:36:59 [1] Continuous updates enabled 18/02/2025 17:45:36 New desktop size: 3200 x 1707 18/02/2025 17:45:36 New screen layout: 18/02/2025 17:45:36 0x00000040 (output 0x00000040): 3200x1707+0+0 18/02/2025 17:45:36 [1] Continuous updates enabled 18/02/2025 17:45:36 [1] Continuous updates enabled 18/02/2025 17:57:41 New desktop size: 3126 x 1707 18/02/2025 17:57:41 New screen layout: 18/02/2025 17:57:41 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 17:57:41 [1] Continuous updates enabled 18/02/2025 17:57:41 [1] Continuous updates enabled 18/02/2025 18:02:41 New desktop size: 3200 x 1707 18/02/2025 18:02:41 New screen layout: 18/02/2025 18:02:41 0x00000040 (output 0x00000040): 3200x1707+0+0 18/02/2025 18:02:41 [1] Continuous updates enabled 18/02/2025 18:02:41 [1] Continuous updates enabled 18/02/2025 18:29:32 New desktop size: 3126 x 1707 18/02/2025 18:29:32 New screen layout: 18/02/2025 18:29:32 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 18:29:32 [1] Continuous updates enabled 18/02/2025 18:29:32 [1] Continuous updates enabled 18/02/2025 18:34:33 New desktop size: 3200 x 1707 18/02/2025 18:34:33 New screen layout: 18/02/2025 18:34:33 0x00000040 (output 0x00000040): 3200x1707+0+0 18/02/2025 18:34:33 [1] Continuous updates enabled 18/02/2025 18:34:33 [1] Continuous updates enabled 18/02/2025 18:36:38 New desktop size: 3126 x 1707 18/02/2025 18:36:38 New screen layout: 18/02/2025 18:36:38 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 18:36:38 [1] Continuous updates enabled 18/02/2025 18:36:38 [1] Continuous updates enabled 18/02/2025 18:41:39 New desktop size: 3200 x 1707 18/02/2025 18:41:39 New screen layout: 18/02/2025 18:41:39 0x00000040 (output 0x00000040): 3200x1707+0+0 18/02/2025 18:41:39 [1] Continuous updates enabled 18/02/2025 18:41:39 [1] Continuous updates enabled 18/02/2025 18:48:38 New desktop size: 3126 x 1707 18/02/2025 18:48:38 New screen layout: 18/02/2025 18:48:38 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 18:48:38 [1] Continuous updates enabled 18/02/2025 18:48:38 [1] Continuous updates enabled 18/02/2025 18:53:38 New desktop size: 3200 x 1707 18/02/2025 18:53:38 New screen layout: 18/02/2025 18:53:38 0x00000040 (output 0x00000040): 3200x1707+0+0 18/02/2025 18:53:38 [1] Continuous updates enabled 18/02/2025 18:53:38 [1] Continuous updates enabled 18/02/2025 18:57:19 New desktop size: 3126 x 1707 18/02/2025 18:57:19 New screen layout: 18/02/2025 18:57:19 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 18:57:19 [1] Continuous updates enabled 18/02/2025 18:57:19 [1] Continuous updates enabled 18/02/2025 18:57:25 New desktop size: 1240 x 900 18/02/2025 18:57:25 New screen layout: 18/02/2025 18:57:25 0x00000040 (output 0x00000040): 1240x900+0+0 18/02/2025 18:57:25 [1] Continuous updates enabled 18/02/2025 18:57:25 [1] Continuous updates enabled 18/02/2025 18:57:28 New desktop size: 3126 x 1707 18/02/2025 18:57:28 New screen layout: 18/02/2025 18:57:28 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 18:57:28 [1] Continuous updates enabled 18/02/2025 18:57:28 [1] Continuous updates enabled 18/02/2025 19:02:32 [2] Got connection from 127.0.0.1 on port 45904 18/02/2025 19:02:32 [2] Normal socket connection 18/02/2025 19:02:32 [2] Using protocol version 3.8 18/02/2025 19:02:32 [2] rfbSendSecurityTypeList: advertise sectype tight 18/02/2025 19:02:32 [2] Enabling TightVNC protocol extensions 18/02/2025 19:02:32 [2] Advertising Tight auth cap 'VNCAUTH_' 18/02/2025 19:02:36 [2] Full-control authentication enabled 18/02/2025 19:02:36 Number of connected clients: 2 18/02/2025 19:02:36 [2] Pixel format: 18/02/2025 19:02:36 [2] 32 bpp, depth 24, little endian 18/02/2025 19:02:36 [2] true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 18/02/2025 19:02:36 [2] no translation needed 18/02/2025 19:02:36 [2] Enabling full-color cursor updates 18/02/2025 19:02:36 [2] Enabling Desktop Size protocol extension 18/02/2025 19:02:36 [2] Enabling Extended Desktop Size protocol extension 18/02/2025 19:02:36 [2] rfbProcessClientNormalMessage: ignoring unknown encoding -307 (fffffecd) 18/02/2025 19:02:36 [2] Enabling LastRect protocol extension 18/02/2025 19:02:36 [2] Enabling Continuous Updates protocol extension 18/02/2025 19:02:36 [2] Enabling Fence protocol extension 18/02/2025 19:02:36 [2] Enabling Extended Clipboard protocol extension 18/02/2025 19:02:36 [2] Enabling GII protocol extension 18/02/2025 19:02:36 [2] Enabling QEMU Extended Key Event protocol extension 18/02/2025 19:02:36 [2] Enabling QEMU LED State protocol extension 18/02/2025 19:02:36 [2] Enabling VMware LED State protocol extension 18/02/2025 19:02:36 [2] Enabling Tight Encoding Without Zlib protocol extension 18/02/2025 19:02:36 [2] Enabling Extended Mouse Buttons protocol extension 18/02/2025 19:02:36 [2] Using tight encoding 18/02/2025 19:02:36 [2] Enabling CopyRect encoding 18/02/2025 19:02:36 [2] Using JPEG subsampling 0, Q100 18/02/2025 19:02:36 [2] Using JPEG quality 95 18/02/2025 19:02:36 [2] Using JPEG subsampling 0 18/02/2025 19:02:36 [2] Using Tight compression level 1 18/02/2025 19:02:36 [2] Client clipboard capabilities: 18/02/2025 19:02:36 [2] - Plain text (limit = 0 bytes) 18/02/2025 19:02:36 [2] Client supports GII version 1 18/02/2025 19:02:36 New desktop size: 1920 x 1005 18/02/2025 19:02:36 New screen layout: 18/02/2025 19:02:36 0x00000040 (output 0x00000040): 1910x999+0+0 18/02/2025 19:02:36 [2] WARNING: Framebuffer update at 0,0 with dimensions 3126x1707 has been clipped to the screen boundaries 18/02/2025 19:02:36 [1] Continuous updates enabled 18/02/2025 19:02:36 [2] Continuous updates enabled 18/02/2025 19:02:36 [2] Continuous updates enabled 18/02/2025 19:02:36 [2] Continuous updates enabled 18/02/2025 19:02:36 [1] GII Device Create: ELAN25B4:00 04F3:25B4 18/02/2025 19:02:36 [1] Device 'ELAN25B4:00 04F3:25B4' already exists with GII device ID 1 18/02/2025 19:02:36 [1] Continuous updates enabled 18/02/2025 19:02:36 New screen layout: 18/02/2025 19:02:36 0x00000040 (output 0x00000040): 1920x1005+0+0 18/02/2025 19:02:36 [2] Continuous updates enabled 18/02/2025 19:02:36 [2] Continuous updates enabled 18/02/2025 19:02:37 [1] Continuous updates enabled 18/02/2025 19:02:37 [1] Continuous updates enabled 18/02/2025 19:02:59 New desktop size: 3126 x 1707 18/02/2025 19:02:59 New screen layout: 18/02/2025 19:02:59 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 19:02:59 [2] Continuous updates enabled 18/02/2025 19:02:59 [1] Continuous updates enabled 18/02/2025 19:02:59 [1] Continuous updates enabled 18/02/2025 19:02:59 [2] Continuous updates enabled 18/02/2025 19:03:32 New desktop size: 1920 x 1005 18/02/2025 19:03:32 New screen layout: 18/02/2025 19:03:32 0x00000040 (output 0x00000040): 1920x1005+0+0 18/02/2025 19:03:32 [2] Continuous updates enabled 18/02/2025 19:03:32 [1] Continuous updates enabled 18/02/2025 19:03:32 [1] Continuous updates enabled 18/02/2025 19:03:32 [2] Continuous updates enabled 18/02/2025 19:03:36 New desktop size: 3126 x 1707 18/02/2025 19:03:36 New screen layout: 18/02/2025 19:03:36 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 19:03:36 [2] Continuous updates enabled 18/02/2025 19:03:36 [1] Continuous updates enabled 18/02/2025 19:03:36 [1] Continuous updates enabled 18/02/2025 19:03:36 [2] Continuous updates enabled 18/02/2025 19:10:51 [2] Client gone 18/02/2025 19:10:51 [2] Statistics: 18/02/2025 19:10:51 [2] key events received 0, pointer events 819 18/02/2025 19:10:51 [2] framebuffer updates 7124, rectangles 659634, bytes -2108824550 18/02/2025 19:10:51 [2] LastRect markers 3511, bytes 42132 18/02/2025 19:10:51 [2] cursor shape updates 81, bytes 323580 18/02/2025 19:10:51 [2] CopyRect rectangles 19, bytes 304 18/02/2025 19:10:51 [2] Tight rectangles 656023, bytes -2109190566 18/02/2025 19:10:51 [2] raw equivalent 65402.227832 Mbytes, compression ratio 29.921733 18/02/2025 19:10:51 Number of connected clients: 1 18/02/2025 19:10:51 Using 4 threads for Tight encoding 18/02/2025 19:12:29 New desktop size: 3200 x 1707 18/02/2025 19:12:29 New screen layout: 18/02/2025 19:12:29 0x00000040 (output 0x00000040): 3200x1707+0+0 18/02/2025 19:12:29 [1] Continuous updates enabled 18/02/2025 19:12:29 [1] Continuous updates enabled 18/02/2025 19:12:58 [3] Got connection from 127.0.0.1 on port 44952 18/02/2025 19:12:58 [3] Normal socket connection 18/02/2025 19:12:58 [3] Using protocol version 3.8 18/02/2025 19:12:58 [3] rfbSendSecurityTypeList: advertise sectype tight 18/02/2025 19:12:58 [3] Enabling TightVNC protocol extensions 18/02/2025 19:12:58 [3] Advertising Tight auth cap 'VNCAUTH_' 18/02/2025 19:13:26 [3] Full-control authentication enabled 18/02/2025 19:13:26 Number of connected clients: 2 18/02/2025 19:13:26 [3] Pixel format: 18/02/2025 19:13:26 [3] 32 bpp, depth 24, little endian 18/02/2025 19:13:26 [3] true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 18/02/2025 19:13:26 [3] no translation needed 18/02/2025 19:13:26 [3] Enabling full-color cursor updates 18/02/2025 19:13:26 [3] Enabling Desktop Size protocol extension 18/02/2025 19:13:26 [3] Enabling Extended Desktop Size protocol extension 18/02/2025 19:13:26 [3] rfbProcessClientNormalMessage: ignoring unknown encoding -307 (fffffecd) 18/02/2025 19:13:26 [3] Enabling LastRect protocol extension 18/02/2025 19:13:26 [3] Enabling Continuous Updates protocol extension 18/02/2025 19:13:26 [3] Enabling Fence protocol extension 18/02/2025 19:13:26 [3] Enabling Extended Clipboard protocol extension 18/02/2025 19:13:26 [3] Enabling GII protocol extension 18/02/2025 19:13:26 [3] Enabling QEMU Extended Key Event protocol extension 18/02/2025 19:13:26 [3] Enabling QEMU LED State protocol extension 18/02/2025 19:13:26 [3] Enabling VMware LED State protocol extension 18/02/2025 19:13:26 [3] Enabling Tight Encoding Without Zlib protocol extension 18/02/2025 19:13:26 [3] Enabling Extended Mouse Buttons protocol extension 18/02/2025 19:13:26 [3] Using tight encoding 18/02/2025 19:13:26 [3] Enabling CopyRect encoding 18/02/2025 19:13:26 [3] Using JPEG subsampling 0, Q100 18/02/2025 19:13:26 [3] Using JPEG quality 95 18/02/2025 19:13:26 [3] Using JPEG subsampling 0 18/02/2025 19:13:26 [3] Using Tight compression level 1 18/02/2025 19:13:26 [3] Client clipboard capabilities: 18/02/2025 19:13:26 [3] - Plain text (limit = 0 bytes) 18/02/2025 19:13:26 [3] Client supports GII version 1 18/02/2025 19:13:26 New desktop size: 1920 x 1005 18/02/2025 19:13:26 New screen layout: 18/02/2025 19:13:26 0x00000040 (output 0x00000040): 1910x999+0+0 18/02/2025 19:13:26 [3] WARNING: Framebuffer update at 0,0 with dimensions 3200x1707 has been clipped to the screen boundaries 18/02/2025 19:13:26 [3] WARNING: Framebuffer update at 0,0 with dimensions 3200x1707 has been clipped to the screen boundaries 18/02/2025 19:13:26 [3] Continuous updates enabled 18/02/2025 19:13:26 [3] Continuous updates enabled 18/02/2025 19:13:26 [3] Continuous updates enabled 18/02/2025 19:13:26 [1] Continuous updates enabled 18/02/2025 19:13:26 [1] Continuous updates enabled 18/02/2025 19:13:26 New screen layout: 18/02/2025 19:13:26 0x00000040 (output 0x00000040): 1920x1005+0+0 18/02/2025 19:13:27 [3] Continuous updates enabled 18/02/2025 19:13:27 [3] Continuous updates enabled 18/02/2025 19:13:27 [1] Continuous updates enabled 18/02/2025 19:13:27 [1] Continuous updates enabled 18/02/2025 19:13:43 New desktop size: 1900 x 989 18/02/2025 19:13:43 New screen layout: 18/02/2025 19:13:43 0x00000040 (output 0x00000040): 1852x865+0+0 18/02/2025 19:13:43 [3] Continuous updates enabled 18/02/2025 19:13:43 [3] Continuous updates enabled 18/02/2025 19:13:43 [1] Continuous updates enabled 18/02/2025 19:13:43 [1] Continuous updates enabled 18/02/2025 19:13:44 New screen layout: 18/02/2025 19:13:44 0x00000040 (output 0x00000040): 1900x989+0+0 18/02/2025 19:13:44 [3] Continuous updates enabled 18/02/2025 19:13:44 [3] Continuous updates enabled 18/02/2025 19:13:44 [1] Continuous updates enabled 18/02/2025 19:13:44 [1] Continuous updates enabled 18/02/2025 19:14:02 [3] Client gone 18/02/2025 19:14:02 [3] Statistics: 18/02/2025 19:14:02 [3] key events received 0, pointer events 683 18/02/2025 19:14:02 [3] framebuffer updates 929, rectangles 37981, bytes 129380711 18/02/2025 19:14:02 [3] LastRect markers 696, bytes 8352 18/02/2025 19:14:02 [3] cursor shape updates 48, bytes 126768 18/02/2025 19:14:02 [3] CopyRect rectangles 11, bytes 176 18/02/2025 19:14:02 [3] Tight rectangles 37226, bytes 129245415 18/02/2025 19:14:02 [3] raw equivalent 2047.268932 Mbytes, compression ratio 15.840167 18/02/2025 19:14:02 Number of connected clients: 1 18/02/2025 19:14:02 Using 4 threads for Tight encoding 18/02/2025 19:24:43 [4] Got connection from 127.0.0.1 on port 42296 18/02/2025 19:24:43 [4] Normal socket connection 18/02/2025 19:24:43 [4] Using protocol version 3.8 18/02/2025 19:24:43 [4] rfbSendSecurityTypeList: advertise sectype tight 18/02/2025 19:24:43 [4] Enabling TightVNC protocol extensions 18/02/2025 19:24:43 [4] Advertising Tight auth cap 'VNCAUTH_' 18/02/2025 19:24:46 [4] Full-control authentication enabled 18/02/2025 19:24:46 Number of connected clients: 2 18/02/2025 19:24:46 [4] Pixel format: 18/02/2025 19:24:46 [4] 32 bpp, depth 24, little endian 18/02/2025 19:24:46 [4] true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 18/02/2025 19:24:46 [4] no translation needed 18/02/2025 19:24:46 [4] Enabling full-color cursor updates 18/02/2025 19:24:46 [4] Enabling Desktop Size protocol extension 18/02/2025 19:24:46 [4] Enabling Extended Desktop Size protocol extension 18/02/2025 19:24:46 [4] rfbProcessClientNormalMessage: ignoring unknown encoding -307 (fffffecd) 18/02/2025 19:24:46 [4] Enabling LastRect protocol extension 18/02/2025 19:24:46 [4] Enabling Continuous Updates protocol extension 18/02/2025 19:24:46 [4] Enabling Fence protocol extension 18/02/2025 19:24:46 [4] Enabling Extended Clipboard protocol extension 18/02/2025 19:24:46 [4] Enabling GII protocol extension 18/02/2025 19:24:46 [4] Enabling QEMU Extended Key Event protocol extension 18/02/2025 19:24:46 [4] Enabling QEMU LED State protocol extension 18/02/2025 19:24:46 [4] Enabling VMware LED State protocol extension 18/02/2025 19:24:46 [4] Enabling Tight Encoding Without Zlib protocol extension 18/02/2025 19:24:46 [4] Enabling Extended Mouse Buttons protocol extension 18/02/2025 19:24:46 [4] Using tight encoding 18/02/2025 19:24:46 [4] Enabling CopyRect encoding 18/02/2025 19:24:46 [4] Using JPEG subsampling 0, Q100 18/02/2025 19:24:46 [4] Using JPEG quality 95 18/02/2025 19:24:46 [4] Using JPEG subsampling 0 18/02/2025 19:24:46 [4] Using Tight compression level 1 18/02/2025 19:24:46 [4] Client clipboard capabilities: 18/02/2025 19:24:46 [4] - Plain text (limit = 0 bytes) 18/02/2025 19:24:46 [4] Client supports GII version 1 18/02/2025 19:24:46 New screen layout: 18/02/2025 19:24:46 0x00000040 (output 0x00000040): 1900x989+0+0 18/02/2025 19:24:46 [4] Continuous updates enabled 18/02/2025 19:24:46 [4] Continuous updates enabled 18/02/2025 19:24:46 [4] Continuous updates enabled 18/02/2025 19:24:46 [1] Continuous updates enabled 18/02/2025 19:24:46 [1] Continuous updates enabled 18/02/2025 19:50:28 [4] Client gone 18/02/2025 19:50:28 [4] Statistics: 18/02/2025 19:50:28 [4] key events received 0, pointer events 12339 18/02/2025 19:50:28 [4] framebuffer updates 54456, rectangles 6500006, bytes 1118068892 18/02/2025 19:50:28 [4] LastRect markers 45826, bytes 549912 18/02/2025 19:50:28 [4] cursor shape updates 683, bytes 2717892 18/02/2025 19:50:28 [4] CopyRect rectangles 7, bytes 112 18/02/2025 19:50:28 [4] Tight rectangles 6453490, bytes 1114800976 18/02/2025 19:50:28 [4] raw equivalent 308416.257244 Mbytes, compression ratio 13.652997 18/02/2025 19:50:28 Number of connected clients: 1 18/02/2025 19:50:28 Using 4 threads for Tight encoding 18/02/2025 19:50:44 [5] Got connection from 127.0.0.1 on port 60142 18/02/2025 19:50:44 [5] Normal socket connection 18/02/2025 19:50:44 [5] Using protocol version 3.8 18/02/2025 19:50:44 [5] rfbSendSecurityTypeList: advertise sectype tight 18/02/2025 19:50:44 [5] Enabling TightVNC protocol extensions 18/02/2025 19:50:44 [5] Advertising Tight auth cap 'VNCAUTH_' 18/02/2025 19:50:47 [5] Full-control authentication enabled 18/02/2025 19:50:47 Number of connected clients: 2 18/02/2025 19:50:47 [5] Pixel format: 18/02/2025 19:50:47 [5] 32 bpp, depth 24, little endian 18/02/2025 19:50:47 [5] true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 18/02/2025 19:50:47 [5] no translation needed 18/02/2025 19:50:47 [5] Enabling full-color cursor updates 18/02/2025 19:50:47 [5] Enabling Desktop Size protocol extension 18/02/2025 19:50:47 [5] Enabling Extended Desktop Size protocol extension 18/02/2025 19:50:47 [5] rfbProcessClientNormalMessage: ignoring unknown encoding -307 (fffffecd) 18/02/2025 19:50:47 [5] Enabling LastRect protocol extension 18/02/2025 19:50:47 [5] Enabling Continuous Updates protocol extension 18/02/2025 19:50:47 [5] Enabling Fence protocol extension 18/02/2025 19:50:47 [5] Enabling Extended Clipboard protocol extension 18/02/2025 19:50:47 [5] Enabling GII protocol extension 18/02/2025 19:50:47 [5] Enabling QEMU Extended Key Event protocol extension 18/02/2025 19:50:47 [5] Enabling QEMU LED State protocol extension 18/02/2025 19:50:47 [5] Enabling VMware LED State protocol extension 18/02/2025 19:50:47 [5] Enabling Tight Encoding Without Zlib protocol extension 18/02/2025 19:50:47 [5] Enabling Extended Mouse Buttons protocol extension 18/02/2025 19:50:47 [5] Using tight encoding 18/02/2025 19:50:47 [5] Enabling CopyRect encoding 18/02/2025 19:50:47 [5] Using JPEG subsampling 0, Q100 18/02/2025 19:50:47 [5] Using JPEG quality 95 18/02/2025 19:50:47 [5] Using JPEG subsampling 0 18/02/2025 19:50:47 [5] Using Tight compression level 1 18/02/2025 19:50:47 [5] Client clipboard capabilities: 18/02/2025 19:50:47 [5] - Plain text (limit = 0 bytes) 18/02/2025 19:50:47 [5] Client supports GII version 1 18/02/2025 19:50:47 New screen layout: 18/02/2025 19:50:47 0x00000040 (output 0x00000040): 1900x989+0+0 18/02/2025 19:50:47 [5] Continuous updates enabled 18/02/2025 19:50:47 [5] Continuous updates enabled 18/02/2025 19:50:47 [5] Continuous updates enabled 18/02/2025 19:50:47 [1] Continuous updates enabled 18/02/2025 19:50:47 [1] Continuous updates enabled 18/02/2025 19:51:04 [5] Client gone 18/02/2025 19:51:04 [5] Statistics: 18/02/2025 19:51:04 [5] key events received 0, pointer events 101 18/02/2025 19:51:04 [5] framebuffer updates 439, rectangles 51011, bytes 160034507 18/02/2025 19:51:04 [5] LastRect markers 323, bytes 3876 18/02/2025 19:51:04 [5] cursor shape updates 13, bytes 32364 18/02/2025 19:51:04 [5] Tight rectangles 50675, bytes 159998267 18/02/2025 19:51:04 [5] raw equivalent 2105.995308 Mbytes, compression ratio 13.162613 18/02/2025 19:51:04 Number of connected clients: 1 18/02/2025 19:51:04 Using 4 threads for Tight encoding 18/02/2025 21:46:13 New desktop size: 3126 x 1707 18/02/2025 21:46:13 New screen layout: 18/02/2025 21:46:13 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 21:46:14 [1] Continuous updates enabled 18/02/2025 21:46:14 [1] Continuous updates enabled 18/02/2025 21:52:00 New desktop size: 3200 x 1707 18/02/2025 21:52:00 New screen layout: 18/02/2025 21:52:00 0x00000040 (output 0x00000040): 3200x1707+0+0 18/02/2025 21:52:00 [1] Continuous updates enabled 18/02/2025 21:52:00 [1] Continuous updates enabled 18/02/2025 22:03:14 New desktop size: 3126 x 1707 18/02/2025 22:03:14 New screen layout: 18/02/2025 22:03:14 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 22:03:14 [1] Continuous updates enabled 18/02/2025 22:03:14 [1] Continuous updates enabled 18/02/2025 22:05:27 New desktop size: 1900 x 989 18/02/2025 22:05:27 New screen layout: 18/02/2025 22:05:27 0x00000040 (output 0x00000040): 1900x989+0+0 18/02/2025 22:05:27 [1] Continuous updates enabled 18/02/2025 22:05:27 [1] Continuous updates enabled 18/02/2025 22:05:30 New desktop size: 3126 x 1707 18/02/2025 22:05:30 New screen layout: 18/02/2025 22:05:30 0x00000040 (output 0x00000040): 3126x1707+0+0 18/02/2025 22:05:30 [1] Continuous updates enabled 18/02/2025 22:05:30 [1] Continuous updates enabled 18/02/2025 22:14:00 New desktop size: 1900 x 989 18/02/2025 22:14:00 New screen layout: 18/02/2025 22:14:00 0x00000040 (output 0x00000040): 1900x989+0+0 18/02/2025 22:14:00 [1] Continuous updates enabled 18/02/2025 22:14:00 [1] Continuous updates enabled 18/02/2025 22:52:29 [1] Client gone 18/02/2025 22:52:29 [1] Statistics: 18/02/2025 22:52:29 [1] key events received 308, pointer events 31144 18/02/2025 22:52:29 [1] framebuffer updates 200001, rectangles 11580089, bytes 1904679475 18/02/2025 22:52:29 [1] LastRect markers 91652, bytes 1099824 18/02/2025 22:52:29 [1] CopyRect rectangles 296, bytes 4736 18/02/2025 22:52:29 [1] Tight rectangles 11488141, bytes 1903574915 18/02/2025 22:52:29 [1] raw equivalent 699545.828532 Mbytes, compression ratio 66.664620 18/02/2025 22:52:29 Device 'ELAN25B4:00 04F3:25B4' no longer used by any clients. Deleting. 18/02/2025 22:52:29 Number of connected clients: 0 18/02/2025 22:56:08 [6] Got connection from 10.8.2.9 on port 49666 18/02/2025 22:56:08 [6] Normal socket connection 18/02/2025 22:56:09 [6] Using protocol version 3.8 18/02/2025 22:56:09 [6] rfbSendSecurityTypeList: advertise sectype tight 18/02/2025 22:56:09 [6] Enabling TightVNC protocol extensions 18/02/2025 22:56:09 [6] Advertising Tight auth cap 'VNCAUTH_' 18/02/2025 22:56:12 [6] Full-control authentication enabled 18/02/2025 22:56:12 Number of connected clients: 1 18/02/2025 22:56:12 [6] Pixel format: 18/02/2025 22:56:12 [6] 32 bpp, depth 24, little endian 18/02/2025 22:56:12 [6] true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 18/02/2025 22:56:12 [6] no translation needed 18/02/2025 22:56:12 [6] Enabling Desktop Size protocol extension 18/02/2025 22:56:12 [6] Enabling Extended Desktop Size protocol extension 18/02/2025 22:56:12 [6] rfbProcessClientNormalMessage: ignoring unknown encoding -307 (fffffecd) 18/02/2025 22:56:12 [6] Enabling LastRect protocol extension 18/02/2025 22:56:12 [6] Enabling Continuous Updates protocol extension 18/02/2025 22:56:12 [6] Enabling Fence protocol extension 18/02/2025 22:56:12 [6] Enabling GII protocol extension 18/02/2025 22:56:12 [6] Using tight encoding 18/02/2025 22:56:12 [6] Enabling CopyRect encoding 18/02/2025 22:56:12 [6] Using JPEG subsampling 1, Q41 18/02/2025 22:56:12 [6] Using JPEG quality 21 18/02/2025 22:56:12 [6] Using JPEG subsampling 1 18/02/2025 22:56:12 [6] Using Tight compression level 1 18/02/2025 22:56:12 Using 4 threads for Tight encoding 18/02/2025 22:56:12 [6] Client supports GII version 1 18/02/2025 22:56:12 [6] GII Device Create: ELAN25B4:00 04F3:25B4 18/02/2025 22:56:12 [6] GII device ID = 1 18/02/2025 22:56:12 New desktop size: 3200 x 1800 18/02/2025 22:56:12 New screen layout: 18/02/2025 22:56:12 0x00000040 (output 0x00000040): 3200x1800+0+0 18/02/2025 22:56:12 [6] Continuous updates enabled 18/02/2025 22:56:12 [6] Continuous updates enabled 18/02/2025 22:56:12 [6] Continuous updates enabled 18/02/2025 22:58:53 [6] Client gone 18/02/2025 22:58:53 [6] Statistics: 18/02/2025 22:58:53 [6] key events received 122, pointer events 1209 18/02/2025 22:58:53 [6] framebuffer updates 2819, rectangles 99051, bytes 64898153 18/02/2025 22:58:53 [6] LastRect markers 1873, bytes 22476 18/02/2025 22:58:53 [6] CopyRect rectangles 1, bytes 16 18/02/2025 22:58:53 [6] Tight rectangles 97177, bytes 64875661 18/02/2025 22:58:53 [6] raw equivalent 5138.323712 Mbytes, compression ratio 79.202641 18/02/2025 22:58:53 Device 'ELAN25B4:00 04F3:25B4' no longer used by any clients. Deleting. 18/02/2025 22:58:53 Number of connected clients: 0 On Tue, Feb 18, 2025 at 10:22?PM Phil Marsh wrote: > Hi Aaron, > You're right, but I have no need for the encryption ssh provides because > my connection is tunneled through OpenVPN and encryption just adds > overhead. However, SSH also provides x11 forwarding which I don't get from > Telnet of course. So it can make sense to use ssh through the OpenVPN > tunnel anyway and I'll try that. If I use SSH as stand-alone, I'll be > setting up a reverse SSH tunnel. > However, I still don't understand why I can start the Turbo VNC server > (command vncserver) from a Telnet terminal on my other machines (Ubuntu > 22.04) but not on the Ubuntu 24.04 machine I've set up for a small company > here in CA at UCI. If I could start the VNC server only on SSH, then I'd > say that's the solution. It doesn't matter whether the Telnet terminal > window is remote or running on the local machine as per the results. I'd be > surprised if SSH helped here? > Thanks, Phil > > On Tue, Feb 18, 2025 at 6:18?PM Aaron D. Johnson > wrote: > >> Phil Marsh writes: >> > Thanks. However, my other server's TurboVNC starts OK using a Telnet >> > terminal window. >> >> Stephen is on the right track here. The two servers' environments are >> different in a way that matters to TurboVNC. This may well include >> TurboVNC itself. Not a TurboVNC user myself, SSH X11 forwarding works >> for my use cases. But if I were stuck in your situation, I'd be >> starting out comparing the contents of the TurboVNC log files on >> server A and server B. Read them side by side... Use diff... There >> are plenty of tools for this. >> >> Also would be good to compare package lists between the two servers. >> And the process environment variables. >> >> Further question... It is 2025. Why are you using the plain text >> telnet protocol for any traffic between your computers? SSH has been >> a thing for 30 years now. (Well, almost... July 1995 was the first >> source release.) Key based authentication and not typing passwords is >> kinda nice. Join us in the 21st century... "ssh" is shorter to type >> than "telnet", too. >> >> - Aaron >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From microcraftx at gmail.com Wed Feb 19 07:38:11 2025 From: microcraftx at gmail.com (Phil Marsh) Date: Tue, 18 Feb 2025 23:38:11 -0800 Subject: Hi Bob question on getting TurboVNC running In-Reply-To: References: <20250219021731.5DE3BF6E4@zarathud.internal.fnord.greeley.co.us> Message-ID: The base problem appears to be that running vncserver on the physical machine terminal results in /usr/share/xsessions/xubuntu.desktop being found and used as required by the window manager. The successful start log shows: xstartup.turbovnc: Using 'xubuntu' window manager in xstartup.turbovnc: /usr/share/xsessions/xubuntu.desktop xstartup.turbovnc: Executing /etc/X11/Xsession "startxfce4" in SSH or Telnet terminal window vncserver is unsuccessful and the start log shows: xstartup.turbovnc: The session desktop file for the default window manager was xstartup.turbovnc: not found at: xstartup.turbovnc: /usr/share/xsessions/gnome.desktop xstartup.turbovnc: /usr/share/xsessions/ubuntu.desktop Killing Xvnc process ID 10292 Indeed /usr/share/xsessions/xubuntu.desktop does exist but /usr/share/xsessions/gnome.desktop /usr/share/xsessions/ubuntu.desktop do NOT exist I'm wondering why vncserver is trying to use the nonexistent desktops to start when in SSH or Telnet terminals? Thanks, Phil On Tue, Feb 18, 2025 at 11:26?PM Phil Marsh wrote: > Hi Aaron, > I tried issuing vncserver from an SSH terminal and the VNC server also > failed to start. The ending lines of the unsuccessful logfile are: > Errors from xkbcomp are not fatal to the X server > xstartup.turbovnc: Creating new session bus instance: > xstartup.turbovnc: > unix:path=/tmp/dbus-AuF7HAlcQZ,guid=087f3dae01918291221bb56567b585ff > xstartup.turbovnc: The session desktop file for the default window manager > was > xstartup.turbovnc: not found at: > xstartup.turbovnc: /usr/share/xsessions/gnome.desktop > xstartup.turbovnc: /usr/share/xsessions/ubuntu.desktop > Killing Xvnc process ID 10292 > > ################# > > and the corresponding lines from a successful star of vncserver are: > Errors from xkbcomp are not fatal to the X server > xstartup.turbovnc: Creating new session bus instance: > xstartup.turbovnc: > unix:path=/tmp/dbus-NYBQm0ryxE,guid=5026c84f2da1c51e16cf0b0a67b5106e > xstartup.turbovnc: Using 'xubuntu' window manager in > xstartup.turbovnc: /usr/share/xsessions/xubuntu.desktop > xstartup.turbovnc: Executing /etc/X11/Xsession "startxfce4" > > 18/02/2025 15:28:46 [1] Got connection from 10.8.2.1 on port 40626 > 18/02/2025 15:28:46 [1] Normal socket connection > 18/02/2025 15:28:46 [1] Using protocol version 3.8 > 18/02/2025 15:28:46 [1] rfbSendSecurityTypeList: advertise sectype tight > 18/02/2025 15:28:46 [1] Enabling TightVNC protocol extensions > 18/02/2025 15:28:46 [1] Advertising Tight auth cap 'VNCAUTH_' > 18/02/2025 15:28:56 [1] Full-control authentication enabled > 18/02/2025 15:28:56 Number of connected clients: 1 > 18/02/2025 15:28:56 [1] Pixel format: > 18/02/2025 15:28:56 [1] 32 bpp, depth 24, little endian > 18/02/2025 15:28:56 [1] true colour: max r 255 g 255 b 255, shift r 16 g > 8 b 0 > 18/02/2025 15:28:56 [1] no translation needed > 18/02/2025 15:28:56 [1] Enabling Desktop Size protocol extension > 18/02/2025 15:28:56 [1] Enabling Extended Desktop Size protocol extension > 18/02/2025 15:28:56 [1] rfbProcessClientNormalMessage: ignoring unknown > encoding -307 (fffffecd) > 18/02/2025 15:28:56 [1] Enabling LastRect protocol extension > 18/02/2025 15:28:56 [1] Enabling Continuous Updates protocol extension > 18/02/2025 15:28:56 [1] Enabling Fence protocol extension > 18/02/2025 15:28:56 [1] Enabling GII protocol extension > 18/02/2025 15:28:56 [1] Using tight encoding > 18/02/2025 15:28:56 [1] Enabling CopyRect encoding > 18/02/2025 15:28:56 [1] Using JPEG subsampling 1, Q41 > 18/02/2025 15:28:56 [1] Using JPEG quality 25 > 18/02/2025 15:28:56 [1] Using JPEG subsampling 1 > 18/02/2025 15:28:56 [1] Using Tight compression level 1 > 18/02/2025 15:28:56 Using 4 threads for Tight encoding > 18/02/2025 15:28:57 [1] Client supports GII version 1 > 18/02/2025 15:28:57 [1] GII Device Create: ELAN25B4:00 04F3:25B4 > 18/02/2025 15:28:57 [1] GII device ID = 1 > 18/02/2025 15:28:58 [1] Continuous updates enabled > 18/02/2025 15:30:23 New desktop size: 3126 x 1707 > 18/02/2025 15:30:23 New screen layout: > 18/02/2025 15:30:23 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 15:30:23 [1] Continuous updates enabled > 18/02/2025 15:30:23 [1] Continuous updates enabled > 18/02/2025 15:38:47 New desktop size: 3200 x 1707 > 18/02/2025 15:38:47 New screen layout: > 18/02/2025 15:38:47 0x00000040 (output 0x00000040): 3200x1707+0+0 > 18/02/2025 15:38:47 [1] Continuous updates enabled > 18/02/2025 15:38:47 [1] Continuous updates enabled > 18/02/2025 16:38:13 New desktop size: 3126 x 1707 > 18/02/2025 16:38:13 New screen layout: > 18/02/2025 16:38:13 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 16:38:13 [1] Continuous updates enabled > 18/02/2025 16:38:13 [1] Continuous updates enabled > 18/02/2025 16:45:51 New desktop size: 1240 x 900 > 18/02/2025 16:45:51 New screen layout: > 18/02/2025 16:45:51 0x00000040 (output 0x00000040): 1240x900+0+0 > 18/02/2025 16:45:51 [1] Continuous updates enabled > 18/02/2025 16:45:51 [1] Continuous updates enabled > 18/02/2025 16:45:54 New desktop size: 3126 x 1707 > 18/02/2025 16:45:54 New screen layout: > 18/02/2025 16:45:54 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 16:45:54 [1] Continuous updates enabled > 18/02/2025 16:45:54 [1] Continuous updates enabled > 18/02/2025 16:53:01 New desktop size: 3200 x 1707 > 18/02/2025 16:53:01 New screen layout: > 18/02/2025 16:53:01 0x00000040 (output 0x00000040): 3200x1707+0+0 > 18/02/2025 16:53:01 [1] Continuous updates enabled > 18/02/2025 16:53:01 [1] Continuous updates enabled > 18/02/2025 17:14:28 New desktop size: 3126 x 1707 > 18/02/2025 17:14:28 New screen layout: > 18/02/2025 17:14:28 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 17:14:28 [1] Continuous updates enabled > 18/02/2025 17:14:28 [1] Continuous updates enabled > 18/02/2025 17:19:41 New desktop size: 3200 x 1707 > 18/02/2025 17:19:41 New screen layout: > 18/02/2025 17:19:41 0x00000040 (output 0x00000040): 3200x1707+0+0 > 18/02/2025 17:19:41 [1] Continuous updates enabled > 18/02/2025 17:19:41 [1] Continuous updates enabled > 18/02/2025 17:36:59 New desktop size: 3126 x 1707 > 18/02/2025 17:36:59 New screen layout: > 18/02/2025 17:36:59 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 17:36:59 [1] Continuous updates enabled > 18/02/2025 17:36:59 [1] Continuous updates enabled > 18/02/2025 17:45:36 New desktop size: 3200 x 1707 > 18/02/2025 17:45:36 New screen layout: > 18/02/2025 17:45:36 0x00000040 (output 0x00000040): 3200x1707+0+0 > 18/02/2025 17:45:36 [1] Continuous updates enabled > 18/02/2025 17:45:36 [1] Continuous updates enabled > 18/02/2025 17:57:41 New desktop size: 3126 x 1707 > 18/02/2025 17:57:41 New screen layout: > 18/02/2025 17:57:41 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 17:57:41 [1] Continuous updates enabled > 18/02/2025 17:57:41 [1] Continuous updates enabled > 18/02/2025 18:02:41 New desktop size: 3200 x 1707 > 18/02/2025 18:02:41 New screen layout: > 18/02/2025 18:02:41 0x00000040 (output 0x00000040): 3200x1707+0+0 > 18/02/2025 18:02:41 [1] Continuous updates enabled > 18/02/2025 18:02:41 [1] Continuous updates enabled > 18/02/2025 18:29:32 New desktop size: 3126 x 1707 > 18/02/2025 18:29:32 New screen layout: > 18/02/2025 18:29:32 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 18:29:32 [1] Continuous updates enabled > 18/02/2025 18:29:32 [1] Continuous updates enabled > 18/02/2025 18:34:33 New desktop size: 3200 x 1707 > 18/02/2025 18:34:33 New screen layout: > 18/02/2025 18:34:33 0x00000040 (output 0x00000040): 3200x1707+0+0 > 18/02/2025 18:34:33 [1] Continuous updates enabled > 18/02/2025 18:34:33 [1] Continuous updates enabled > 18/02/2025 18:36:38 New desktop size: 3126 x 1707 > 18/02/2025 18:36:38 New screen layout: > 18/02/2025 18:36:38 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 18:36:38 [1] Continuous updates enabled > 18/02/2025 18:36:38 [1] Continuous updates enabled > 18/02/2025 18:41:39 New desktop size: 3200 x 1707 > 18/02/2025 18:41:39 New screen layout: > 18/02/2025 18:41:39 0x00000040 (output 0x00000040): 3200x1707+0+0 > 18/02/2025 18:41:39 [1] Continuous updates enabled > 18/02/2025 18:41:39 [1] Continuous updates enabled > 18/02/2025 18:48:38 New desktop size: 3126 x 1707 > 18/02/2025 18:48:38 New screen layout: > 18/02/2025 18:48:38 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 18:48:38 [1] Continuous updates enabled > 18/02/2025 18:48:38 [1] Continuous updates enabled > 18/02/2025 18:53:38 New desktop size: 3200 x 1707 > 18/02/2025 18:53:38 New screen layout: > 18/02/2025 18:53:38 0x00000040 (output 0x00000040): 3200x1707+0+0 > 18/02/2025 18:53:38 [1] Continuous updates enabled > 18/02/2025 18:53:38 [1] Continuous updates enabled > 18/02/2025 18:57:19 New desktop size: 3126 x 1707 > 18/02/2025 18:57:19 New screen layout: > 18/02/2025 18:57:19 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 18:57:19 [1] Continuous updates enabled > 18/02/2025 18:57:19 [1] Continuous updates enabled > 18/02/2025 18:57:25 New desktop size: 1240 x 900 > 18/02/2025 18:57:25 New screen layout: > 18/02/2025 18:57:25 0x00000040 (output 0x00000040): 1240x900+0+0 > 18/02/2025 18:57:25 [1] Continuous updates enabled > 18/02/2025 18:57:25 [1] Continuous updates enabled > 18/02/2025 18:57:28 New desktop size: 3126 x 1707 > 18/02/2025 18:57:28 New screen layout: > 18/02/2025 18:57:28 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 18:57:28 [1] Continuous updates enabled > 18/02/2025 18:57:28 [1] Continuous updates enabled > > 18/02/2025 19:02:32 [2] Got connection from 127.0.0.1 on port 45904 > 18/02/2025 19:02:32 [2] Normal socket connection > 18/02/2025 19:02:32 [2] Using protocol version 3.8 > 18/02/2025 19:02:32 [2] rfbSendSecurityTypeList: advertise sectype tight > 18/02/2025 19:02:32 [2] Enabling TightVNC protocol extensions > 18/02/2025 19:02:32 [2] Advertising Tight auth cap 'VNCAUTH_' > 18/02/2025 19:02:36 [2] Full-control authentication enabled > 18/02/2025 19:02:36 Number of connected clients: 2 > 18/02/2025 19:02:36 [2] Pixel format: > 18/02/2025 19:02:36 [2] 32 bpp, depth 24, little endian > 18/02/2025 19:02:36 [2] true colour: max r 255 g 255 b 255, shift r 16 g > 8 b 0 > 18/02/2025 19:02:36 [2] no translation needed > 18/02/2025 19:02:36 [2] Enabling full-color cursor updates > 18/02/2025 19:02:36 [2] Enabling Desktop Size protocol extension > 18/02/2025 19:02:36 [2] Enabling Extended Desktop Size protocol extension > 18/02/2025 19:02:36 [2] rfbProcessClientNormalMessage: ignoring unknown > encoding -307 (fffffecd) > 18/02/2025 19:02:36 [2] Enabling LastRect protocol extension > 18/02/2025 19:02:36 [2] Enabling Continuous Updates protocol extension > 18/02/2025 19:02:36 [2] Enabling Fence protocol extension > 18/02/2025 19:02:36 [2] Enabling Extended Clipboard protocol extension > 18/02/2025 19:02:36 [2] Enabling GII protocol extension > 18/02/2025 19:02:36 [2] Enabling QEMU Extended Key Event protocol extension > 18/02/2025 19:02:36 [2] Enabling QEMU LED State protocol extension > 18/02/2025 19:02:36 [2] Enabling VMware LED State protocol extension > 18/02/2025 19:02:36 [2] Enabling Tight Encoding Without Zlib protocol > extension > 18/02/2025 19:02:36 [2] Enabling Extended Mouse Buttons protocol extension > 18/02/2025 19:02:36 [2] Using tight encoding > 18/02/2025 19:02:36 [2] Enabling CopyRect encoding > 18/02/2025 19:02:36 [2] Using JPEG subsampling 0, Q100 > 18/02/2025 19:02:36 [2] Using JPEG quality 95 > 18/02/2025 19:02:36 [2] Using JPEG subsampling 0 > 18/02/2025 19:02:36 [2] Using Tight compression level 1 > 18/02/2025 19:02:36 [2] Client clipboard capabilities: > 18/02/2025 19:02:36 [2] - Plain text (limit = 0 bytes) > 18/02/2025 19:02:36 [2] Client supports GII version 1 > 18/02/2025 19:02:36 New desktop size: 1920 x 1005 > 18/02/2025 19:02:36 New screen layout: > 18/02/2025 19:02:36 0x00000040 (output 0x00000040): 1910x999+0+0 > 18/02/2025 19:02:36 [2] WARNING: Framebuffer update at 0,0 with dimensions > 3126x1707 has been clipped to the screen boundaries > 18/02/2025 19:02:36 [1] Continuous updates enabled > 18/02/2025 19:02:36 [2] Continuous updates enabled > 18/02/2025 19:02:36 [2] Continuous updates enabled > 18/02/2025 19:02:36 [2] Continuous updates enabled > 18/02/2025 19:02:36 [1] GII Device Create: ELAN25B4:00 04F3:25B4 > 18/02/2025 19:02:36 [1] Device 'ELAN25B4:00 04F3:25B4' already exists with > GII device ID 1 > 18/02/2025 19:02:36 [1] Continuous updates enabled > 18/02/2025 19:02:36 New screen layout: > 18/02/2025 19:02:36 0x00000040 (output 0x00000040): 1920x1005+0+0 > 18/02/2025 19:02:36 [2] Continuous updates enabled > 18/02/2025 19:02:36 [2] Continuous updates enabled > 18/02/2025 19:02:37 [1] Continuous updates enabled > 18/02/2025 19:02:37 [1] Continuous updates enabled > 18/02/2025 19:02:59 New desktop size: 3126 x 1707 > 18/02/2025 19:02:59 New screen layout: > 18/02/2025 19:02:59 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 19:02:59 [2] Continuous updates enabled > 18/02/2025 19:02:59 [1] Continuous updates enabled > 18/02/2025 19:02:59 [1] Continuous updates enabled > 18/02/2025 19:02:59 [2] Continuous updates enabled > 18/02/2025 19:03:32 New desktop size: 1920 x 1005 > 18/02/2025 19:03:32 New screen layout: > 18/02/2025 19:03:32 0x00000040 (output 0x00000040): 1920x1005+0+0 > 18/02/2025 19:03:32 [2] Continuous updates enabled > 18/02/2025 19:03:32 [1] Continuous updates enabled > 18/02/2025 19:03:32 [1] Continuous updates enabled > 18/02/2025 19:03:32 [2] Continuous updates enabled > 18/02/2025 19:03:36 New desktop size: 3126 x 1707 > 18/02/2025 19:03:36 New screen layout: > 18/02/2025 19:03:36 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 19:03:36 [2] Continuous updates enabled > 18/02/2025 19:03:36 [1] Continuous updates enabled > 18/02/2025 19:03:36 [1] Continuous updates enabled > 18/02/2025 19:03:36 [2] Continuous updates enabled > 18/02/2025 19:10:51 [2] Client gone > 18/02/2025 19:10:51 [2] Statistics: > 18/02/2025 19:10:51 [2] key events received 0, pointer events 819 > 18/02/2025 19:10:51 [2] framebuffer updates 7124, rectangles 659634, > bytes -2108824550 > 18/02/2025 19:10:51 [2] LastRect markers 3511, bytes 42132 > 18/02/2025 19:10:51 [2] cursor shape updates 81, bytes 323580 > 18/02/2025 19:10:51 [2] CopyRect rectangles 19, bytes 304 > 18/02/2025 19:10:51 [2] Tight rectangles 656023, bytes -2109190566 > 18/02/2025 19:10:51 [2] raw equivalent 65402.227832 Mbytes, compression > ratio 29.921733 > 18/02/2025 19:10:51 Number of connected clients: 1 > 18/02/2025 19:10:51 Using 4 threads for Tight encoding > 18/02/2025 19:12:29 New desktop size: 3200 x 1707 > 18/02/2025 19:12:29 New screen layout: > 18/02/2025 19:12:29 0x00000040 (output 0x00000040): 3200x1707+0+0 > 18/02/2025 19:12:29 [1] Continuous updates enabled > 18/02/2025 19:12:29 [1] Continuous updates enabled > > 18/02/2025 19:12:58 [3] Got connection from 127.0.0.1 on port 44952 > 18/02/2025 19:12:58 [3] Normal socket connection > 18/02/2025 19:12:58 [3] Using protocol version 3.8 > 18/02/2025 19:12:58 [3] rfbSendSecurityTypeList: advertise sectype tight > 18/02/2025 19:12:58 [3] Enabling TightVNC protocol extensions > 18/02/2025 19:12:58 [3] Advertising Tight auth cap 'VNCAUTH_' > 18/02/2025 19:13:26 [3] Full-control authentication enabled > 18/02/2025 19:13:26 Number of connected clients: 2 > 18/02/2025 19:13:26 [3] Pixel format: > 18/02/2025 19:13:26 [3] 32 bpp, depth 24, little endian > 18/02/2025 19:13:26 [3] true colour: max r 255 g 255 b 255, shift r 16 g > 8 b 0 > 18/02/2025 19:13:26 [3] no translation needed > 18/02/2025 19:13:26 [3] Enabling full-color cursor updates > 18/02/2025 19:13:26 [3] Enabling Desktop Size protocol extension > 18/02/2025 19:13:26 [3] Enabling Extended Desktop Size protocol extension > 18/02/2025 19:13:26 [3] rfbProcessClientNormalMessage: ignoring unknown > encoding -307 (fffffecd) > 18/02/2025 19:13:26 [3] Enabling LastRect protocol extension > 18/02/2025 19:13:26 [3] Enabling Continuous Updates protocol extension > 18/02/2025 19:13:26 [3] Enabling Fence protocol extension > 18/02/2025 19:13:26 [3] Enabling Extended Clipboard protocol extension > 18/02/2025 19:13:26 [3] Enabling GII protocol extension > 18/02/2025 19:13:26 [3] Enabling QEMU Extended Key Event protocol extension > 18/02/2025 19:13:26 [3] Enabling QEMU LED State protocol extension > 18/02/2025 19:13:26 [3] Enabling VMware LED State protocol extension > 18/02/2025 19:13:26 [3] Enabling Tight Encoding Without Zlib protocol > extension > 18/02/2025 19:13:26 [3] Enabling Extended Mouse Buttons protocol extension > 18/02/2025 19:13:26 [3] Using tight encoding > 18/02/2025 19:13:26 [3] Enabling CopyRect encoding > 18/02/2025 19:13:26 [3] Using JPEG subsampling 0, Q100 > 18/02/2025 19:13:26 [3] Using JPEG quality 95 > 18/02/2025 19:13:26 [3] Using JPEG subsampling 0 > 18/02/2025 19:13:26 [3] Using Tight compression level 1 > 18/02/2025 19:13:26 [3] Client clipboard capabilities: > 18/02/2025 19:13:26 [3] - Plain text (limit = 0 bytes) > 18/02/2025 19:13:26 [3] Client supports GII version 1 > 18/02/2025 19:13:26 New desktop size: 1920 x 1005 > 18/02/2025 19:13:26 New screen layout: > 18/02/2025 19:13:26 0x00000040 (output 0x00000040): 1910x999+0+0 > 18/02/2025 19:13:26 [3] WARNING: Framebuffer update at 0,0 with dimensions > 3200x1707 has been clipped to the screen boundaries > 18/02/2025 19:13:26 [3] WARNING: Framebuffer update at 0,0 with dimensions > 3200x1707 has been clipped to the screen boundaries > 18/02/2025 19:13:26 [3] Continuous updates enabled > 18/02/2025 19:13:26 [3] Continuous updates enabled > 18/02/2025 19:13:26 [3] Continuous updates enabled > 18/02/2025 19:13:26 [1] Continuous updates enabled > 18/02/2025 19:13:26 [1] Continuous updates enabled > 18/02/2025 19:13:26 New screen layout: > 18/02/2025 19:13:26 0x00000040 (output 0x00000040): 1920x1005+0+0 > 18/02/2025 19:13:27 [3] Continuous updates enabled > 18/02/2025 19:13:27 [3] Continuous updates enabled > 18/02/2025 19:13:27 [1] Continuous updates enabled > 18/02/2025 19:13:27 [1] Continuous updates enabled > 18/02/2025 19:13:43 New desktop size: 1900 x 989 > 18/02/2025 19:13:43 New screen layout: > 18/02/2025 19:13:43 0x00000040 (output 0x00000040): 1852x865+0+0 > 18/02/2025 19:13:43 [3] Continuous updates enabled > 18/02/2025 19:13:43 [3] Continuous updates enabled > 18/02/2025 19:13:43 [1] Continuous updates enabled > 18/02/2025 19:13:43 [1] Continuous updates enabled > 18/02/2025 19:13:44 New screen layout: > 18/02/2025 19:13:44 0x00000040 (output 0x00000040): 1900x989+0+0 > 18/02/2025 19:13:44 [3] Continuous updates enabled > 18/02/2025 19:13:44 [3] Continuous updates enabled > 18/02/2025 19:13:44 [1] Continuous updates enabled > 18/02/2025 19:13:44 [1] Continuous updates enabled > 18/02/2025 19:14:02 [3] Client gone > 18/02/2025 19:14:02 [3] Statistics: > 18/02/2025 19:14:02 [3] key events received 0, pointer events 683 > 18/02/2025 19:14:02 [3] framebuffer updates 929, rectangles 37981, bytes > 129380711 > 18/02/2025 19:14:02 [3] LastRect markers 696, bytes 8352 > 18/02/2025 19:14:02 [3] cursor shape updates 48, bytes 126768 > 18/02/2025 19:14:02 [3] CopyRect rectangles 11, bytes 176 > 18/02/2025 19:14:02 [3] Tight rectangles 37226, bytes 129245415 > 18/02/2025 19:14:02 [3] raw equivalent 2047.268932 Mbytes, compression > ratio 15.840167 > 18/02/2025 19:14:02 Number of connected clients: 1 > 18/02/2025 19:14:02 Using 4 threads for Tight encoding > > 18/02/2025 19:24:43 [4] Got connection from 127.0.0.1 on port 42296 > 18/02/2025 19:24:43 [4] Normal socket connection > 18/02/2025 19:24:43 [4] Using protocol version 3.8 > 18/02/2025 19:24:43 [4] rfbSendSecurityTypeList: advertise sectype tight > 18/02/2025 19:24:43 [4] Enabling TightVNC protocol extensions > 18/02/2025 19:24:43 [4] Advertising Tight auth cap 'VNCAUTH_' > 18/02/2025 19:24:46 [4] Full-control authentication enabled > 18/02/2025 19:24:46 Number of connected clients: 2 > 18/02/2025 19:24:46 [4] Pixel format: > 18/02/2025 19:24:46 [4] 32 bpp, depth 24, little endian > 18/02/2025 19:24:46 [4] true colour: max r 255 g 255 b 255, shift r 16 g > 8 b 0 > 18/02/2025 19:24:46 [4] no translation needed > 18/02/2025 19:24:46 [4] Enabling full-color cursor updates > 18/02/2025 19:24:46 [4] Enabling Desktop Size protocol extension > 18/02/2025 19:24:46 [4] Enabling Extended Desktop Size protocol extension > 18/02/2025 19:24:46 [4] rfbProcessClientNormalMessage: ignoring unknown > encoding -307 (fffffecd) > 18/02/2025 19:24:46 [4] Enabling LastRect protocol extension > 18/02/2025 19:24:46 [4] Enabling Continuous Updates protocol extension > 18/02/2025 19:24:46 [4] Enabling Fence protocol extension > 18/02/2025 19:24:46 [4] Enabling Extended Clipboard protocol extension > 18/02/2025 19:24:46 [4] Enabling GII protocol extension > 18/02/2025 19:24:46 [4] Enabling QEMU Extended Key Event protocol extension > 18/02/2025 19:24:46 [4] Enabling QEMU LED State protocol extension > 18/02/2025 19:24:46 [4] Enabling VMware LED State protocol extension > 18/02/2025 19:24:46 [4] Enabling Tight Encoding Without Zlib protocol > extension > 18/02/2025 19:24:46 [4] Enabling Extended Mouse Buttons protocol extension > 18/02/2025 19:24:46 [4] Using tight encoding > 18/02/2025 19:24:46 [4] Enabling CopyRect encoding > 18/02/2025 19:24:46 [4] Using JPEG subsampling 0, Q100 > 18/02/2025 19:24:46 [4] Using JPEG quality 95 > 18/02/2025 19:24:46 [4] Using JPEG subsampling 0 > 18/02/2025 19:24:46 [4] Using Tight compression level 1 > 18/02/2025 19:24:46 [4] Client clipboard capabilities: > 18/02/2025 19:24:46 [4] - Plain text (limit = 0 bytes) > 18/02/2025 19:24:46 [4] Client supports GII version 1 > 18/02/2025 19:24:46 New screen layout: > 18/02/2025 19:24:46 0x00000040 (output 0x00000040): 1900x989+0+0 > 18/02/2025 19:24:46 [4] Continuous updates enabled > 18/02/2025 19:24:46 [4] Continuous updates enabled > 18/02/2025 19:24:46 [4] Continuous updates enabled > 18/02/2025 19:24:46 [1] Continuous updates enabled > 18/02/2025 19:24:46 [1] Continuous updates enabled > 18/02/2025 19:50:28 [4] Client gone > 18/02/2025 19:50:28 [4] Statistics: > 18/02/2025 19:50:28 [4] key events received 0, pointer events 12339 > 18/02/2025 19:50:28 [4] framebuffer updates 54456, rectangles 6500006, > bytes 1118068892 > 18/02/2025 19:50:28 [4] LastRect markers 45826, bytes 549912 > 18/02/2025 19:50:28 [4] cursor shape updates 683, bytes 2717892 > 18/02/2025 19:50:28 [4] CopyRect rectangles 7, bytes 112 > 18/02/2025 19:50:28 [4] Tight rectangles 6453490, bytes 1114800976 > 18/02/2025 19:50:28 [4] raw equivalent 308416.257244 Mbytes, compression > ratio 13.652997 > 18/02/2025 19:50:28 Number of connected clients: 1 > 18/02/2025 19:50:28 Using 4 threads for Tight encoding > > 18/02/2025 19:50:44 [5] Got connection from 127.0.0.1 on port 60142 > 18/02/2025 19:50:44 [5] Normal socket connection > 18/02/2025 19:50:44 [5] Using protocol version 3.8 > 18/02/2025 19:50:44 [5] rfbSendSecurityTypeList: advertise sectype tight > 18/02/2025 19:50:44 [5] Enabling TightVNC protocol extensions > 18/02/2025 19:50:44 [5] Advertising Tight auth cap 'VNCAUTH_' > 18/02/2025 19:50:47 [5] Full-control authentication enabled > 18/02/2025 19:50:47 Number of connected clients: 2 > 18/02/2025 19:50:47 [5] Pixel format: > 18/02/2025 19:50:47 [5] 32 bpp, depth 24, little endian > 18/02/2025 19:50:47 [5] true colour: max r 255 g 255 b 255, shift r 16 g > 8 b 0 > 18/02/2025 19:50:47 [5] no translation needed > 18/02/2025 19:50:47 [5] Enabling full-color cursor updates > 18/02/2025 19:50:47 [5] Enabling Desktop Size protocol extension > 18/02/2025 19:50:47 [5] Enabling Extended Desktop Size protocol extension > 18/02/2025 19:50:47 [5] rfbProcessClientNormalMessage: ignoring unknown > encoding -307 (fffffecd) > 18/02/2025 19:50:47 [5] Enabling LastRect protocol extension > 18/02/2025 19:50:47 [5] Enabling Continuous Updates protocol extension > 18/02/2025 19:50:47 [5] Enabling Fence protocol extension > 18/02/2025 19:50:47 [5] Enabling Extended Clipboard protocol extension > 18/02/2025 19:50:47 [5] Enabling GII protocol extension > 18/02/2025 19:50:47 [5] Enabling QEMU Extended Key Event protocol extension > 18/02/2025 19:50:47 [5] Enabling QEMU LED State protocol extension > 18/02/2025 19:50:47 [5] Enabling VMware LED State protocol extension > 18/02/2025 19:50:47 [5] Enabling Tight Encoding Without Zlib protocol > extension > 18/02/2025 19:50:47 [5] Enabling Extended Mouse Buttons protocol extension > 18/02/2025 19:50:47 [5] Using tight encoding > 18/02/2025 19:50:47 [5] Enabling CopyRect encoding > 18/02/2025 19:50:47 [5] Using JPEG subsampling 0, Q100 > 18/02/2025 19:50:47 [5] Using JPEG quality 95 > 18/02/2025 19:50:47 [5] Using JPEG subsampling 0 > 18/02/2025 19:50:47 [5] Using Tight compression level 1 > 18/02/2025 19:50:47 [5] Client clipboard capabilities: > 18/02/2025 19:50:47 [5] - Plain text (limit = 0 bytes) > 18/02/2025 19:50:47 [5] Client supports GII version 1 > 18/02/2025 19:50:47 New screen layout: > 18/02/2025 19:50:47 0x00000040 (output 0x00000040): 1900x989+0+0 > 18/02/2025 19:50:47 [5] Continuous updates enabled > 18/02/2025 19:50:47 [5] Continuous updates enabled > 18/02/2025 19:50:47 [5] Continuous updates enabled > 18/02/2025 19:50:47 [1] Continuous updates enabled > 18/02/2025 19:50:47 [1] Continuous updates enabled > 18/02/2025 19:51:04 [5] Client gone > 18/02/2025 19:51:04 [5] Statistics: > 18/02/2025 19:51:04 [5] key events received 0, pointer events 101 > 18/02/2025 19:51:04 [5] framebuffer updates 439, rectangles 51011, bytes > 160034507 > 18/02/2025 19:51:04 [5] LastRect markers 323, bytes 3876 > 18/02/2025 19:51:04 [5] cursor shape updates 13, bytes 32364 > 18/02/2025 19:51:04 [5] Tight rectangles 50675, bytes 159998267 > 18/02/2025 19:51:04 [5] raw equivalent 2105.995308 Mbytes, compression > ratio 13.162613 > 18/02/2025 19:51:04 Number of connected clients: 1 > 18/02/2025 19:51:04 Using 4 threads for Tight encoding > 18/02/2025 21:46:13 New desktop size: 3126 x 1707 > 18/02/2025 21:46:13 New screen layout: > 18/02/2025 21:46:13 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 21:46:14 [1] Continuous updates enabled > 18/02/2025 21:46:14 [1] Continuous updates enabled > 18/02/2025 21:52:00 New desktop size: 3200 x 1707 > 18/02/2025 21:52:00 New screen layout: > 18/02/2025 21:52:00 0x00000040 (output 0x00000040): 3200x1707+0+0 > 18/02/2025 21:52:00 [1] Continuous updates enabled > 18/02/2025 21:52:00 [1] Continuous updates enabled > 18/02/2025 22:03:14 New desktop size: 3126 x 1707 > 18/02/2025 22:03:14 New screen layout: > 18/02/2025 22:03:14 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 22:03:14 [1] Continuous updates enabled > 18/02/2025 22:03:14 [1] Continuous updates enabled > 18/02/2025 22:05:27 New desktop size: 1900 x 989 > 18/02/2025 22:05:27 New screen layout: > 18/02/2025 22:05:27 0x00000040 (output 0x00000040): 1900x989+0+0 > 18/02/2025 22:05:27 [1] Continuous updates enabled > 18/02/2025 22:05:27 [1] Continuous updates enabled > 18/02/2025 22:05:30 New desktop size: 3126 x 1707 > 18/02/2025 22:05:30 New screen layout: > 18/02/2025 22:05:30 0x00000040 (output 0x00000040): 3126x1707+0+0 > 18/02/2025 22:05:30 [1] Continuous updates enabled > 18/02/2025 22:05:30 [1] Continuous updates enabled > 18/02/2025 22:14:00 New desktop size: 1900 x 989 > 18/02/2025 22:14:00 New screen layout: > 18/02/2025 22:14:00 0x00000040 (output 0x00000040): 1900x989+0+0 > 18/02/2025 22:14:00 [1] Continuous updates enabled > 18/02/2025 22:14:00 [1] Continuous updates enabled > 18/02/2025 22:52:29 [1] Client gone > 18/02/2025 22:52:29 [1] Statistics: > 18/02/2025 22:52:29 [1] key events received 308, pointer events 31144 > 18/02/2025 22:52:29 [1] framebuffer updates 200001, rectangles 11580089, > bytes 1904679475 > 18/02/2025 22:52:29 [1] LastRect markers 91652, bytes 1099824 > 18/02/2025 22:52:29 [1] CopyRect rectangles 296, bytes 4736 > 18/02/2025 22:52:29 [1] Tight rectangles 11488141, bytes 1903574915 > 18/02/2025 22:52:29 [1] raw equivalent 699545.828532 Mbytes, compression > ratio 66.664620 > 18/02/2025 22:52:29 Device 'ELAN25B4:00 04F3:25B4' no longer used by any > clients. Deleting. > 18/02/2025 22:52:29 Number of connected clients: 0 > > 18/02/2025 22:56:08 [6] Got connection from 10.8.2.9 on port 49666 > 18/02/2025 22:56:08 [6] Normal socket connection > 18/02/2025 22:56:09 [6] Using protocol version 3.8 > 18/02/2025 22:56:09 [6] rfbSendSecurityTypeList: advertise sectype tight > 18/02/2025 22:56:09 [6] Enabling TightVNC protocol extensions > 18/02/2025 22:56:09 [6] Advertising Tight auth cap 'VNCAUTH_' > 18/02/2025 22:56:12 [6] Full-control authentication enabled > 18/02/2025 22:56:12 Number of connected clients: 1 > 18/02/2025 22:56:12 [6] Pixel format: > 18/02/2025 22:56:12 [6] 32 bpp, depth 24, little endian > 18/02/2025 22:56:12 [6] true colour: max r 255 g 255 b 255, shift r 16 g > 8 b 0 > 18/02/2025 22:56:12 [6] no translation needed > 18/02/2025 22:56:12 [6] Enabling Desktop Size protocol extension > 18/02/2025 22:56:12 [6] Enabling Extended Desktop Size protocol extension > 18/02/2025 22:56:12 [6] rfbProcessClientNormalMessage: ignoring unknown > encoding -307 (fffffecd) > 18/02/2025 22:56:12 [6] Enabling LastRect protocol extension > 18/02/2025 22:56:12 [6] Enabling Continuous Updates protocol extension > 18/02/2025 22:56:12 [6] Enabling Fence protocol extension > 18/02/2025 22:56:12 [6] Enabling GII protocol extension > 18/02/2025 22:56:12 [6] Using tight encoding > 18/02/2025 22:56:12 [6] Enabling CopyRect encoding > 18/02/2025 22:56:12 [6] Using JPEG subsampling 1, Q41 > 18/02/2025 22:56:12 [6] Using JPEG quality 21 > 18/02/2025 22:56:12 [6] Using JPEG subsampling 1 > 18/02/2025 22:56:12 [6] Using Tight compression level 1 > 18/02/2025 22:56:12 Using 4 threads for Tight encoding > 18/02/2025 22:56:12 [6] Client supports GII version 1 > 18/02/2025 22:56:12 [6] GII Device Create: ELAN25B4:00 04F3:25B4 > 18/02/2025 22:56:12 [6] GII device ID = 1 > 18/02/2025 22:56:12 New desktop size: 3200 x 1800 > 18/02/2025 22:56:12 New screen layout: > 18/02/2025 22:56:12 0x00000040 (output 0x00000040): 3200x1800+0+0 > 18/02/2025 22:56:12 [6] Continuous updates enabled > 18/02/2025 22:56:12 [6] Continuous updates enabled > 18/02/2025 22:56:12 [6] Continuous updates enabled > 18/02/2025 22:58:53 [6] Client gone > 18/02/2025 22:58:53 [6] Statistics: > 18/02/2025 22:58:53 [6] key events received 122, pointer events 1209 > 18/02/2025 22:58:53 [6] framebuffer updates 2819, rectangles 99051, > bytes 64898153 > 18/02/2025 22:58:53 [6] LastRect markers 1873, bytes 22476 > 18/02/2025 22:58:53 [6] CopyRect rectangles 1, bytes 16 > 18/02/2025 22:58:53 [6] Tight rectangles 97177, bytes 64875661 > 18/02/2025 22:58:53 [6] raw equivalent 5138.323712 Mbytes, compression > ratio 79.202641 > 18/02/2025 22:58:53 Device 'ELAN25B4:00 04F3:25B4' no longer used by any > clients. Deleting. > 18/02/2025 22:58:53 Number of connected clients: 0 > > > On Tue, Feb 18, 2025 at 10:22?PM Phil Marsh wrote: > >> Hi Aaron, >> You're right, but I have no need for the encryption ssh provides because >> my connection is tunneled through OpenVPN and encryption just adds >> overhead. However, SSH also provides x11 forwarding which I don't get from >> Telnet of course. So it can make sense to use ssh through the OpenVPN >> tunnel anyway and I'll try that. If I use SSH as stand-alone, I'll be >> setting up a reverse SSH tunnel. >> However, I still don't understand why I can start the Turbo VNC server >> (command vncserver) from a Telnet terminal on my other machines (Ubuntu >> 22.04) but not on the Ubuntu 24.04 machine I've set up for a small company >> here in CA at UCI. If I could start the VNC server only on SSH, then I'd >> say that's the solution. It doesn't matter whether the Telnet terminal >> window is remote or running on the local machine as per the results. I'd be >> surprised if SSH helped here? >> Thanks, Phil >> >> On Tue, Feb 18, 2025 at 6:18?PM Aaron D. Johnson >> wrote: >> >>> Phil Marsh writes: >>> > Thanks. However, my other server's TurboVNC starts OK using a Telnet >>> > terminal window. >>> >>> Stephen is on the right track here. The two servers' environments are >>> different in a way that matters to TurboVNC. This may well include >>> TurboVNC itself. Not a TurboVNC user myself, SSH X11 forwarding works >>> for my use cases. But if I were stuck in your situation, I'd be >>> starting out comparing the contents of the TurboVNC log files on >>> server A and server B. Read them side by side... Use diff... There >>> are plenty of tools for this. >>> >>> Also would be good to compare package lists between the two servers. >>> And the process environment variables. >>> >>> Further question... It is 2025. Why are you using the plain text >>> telnet protocol for any traffic between your computers? SSH has been >>> a thing for 30 years now. (Well, almost... July 1995 was the first >>> source release.) Key based authentication and not typing passwords is >>> kinda nice. Join us in the 21st century... "ssh" is shorter to type >>> than "telnet", too. >>> >>> - Aaron >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From adj at fnord.greeley.co.us Wed Feb 19 16:43:13 2025 From: adj at fnord.greeley.co.us (Aaron D. Johnson) Date: Wed, 19 Feb 2025 16:43:13 +0000 Subject: Hi Bob question on getting TurboVNC running In-Reply-To: Your message of "Tue, 18 Feb 2025 22:22:16 -0800." Message-ID: <20250219164313.6EA5C10B32@zarathud.internal.fnord.greeley.co.us> Phil Marsh writes: > You're right, but I have no need for the encryption ssh provides > because my connection is tunneled through OpenVPN and encryption > just adds overhead. However, SSH also provides x11 forwarding which > I don't get from Telnet of course. So it can make sense to use ssh > through the OpenVPN tunnel anyway and I'll try that. If I use SSH > as stand-alone, I'll be setting up a reverse SSH tunnel. You're not required to do the X11 forwarding with SSH. And I disagree that the encryption "just adds overhead." It provides not just privacy of your communications, but also authentication of the server's identity, passwordless logon, and still saves 3 characters of typing when initiating a session. Further, the encryption overhead is just not measurable in 2025 -- the Intel CPU AES encryption acceleration instructions were introduced in January 2010. I've seen your current laptop and heard many descriptions of your servers. They are not so old that they lack this feature. Moving on to the actual problem, though... > However, I still don't understand why I can start the Turbo VNC > server (command vncserver) from a Telnet terminal on my other > machines (Ubuntu 22.04) but not on the Ubuntu 24.04 machine I've set > up for a small company here in CA at UCI. If I could start the VNC > server only on SSH, then I'd say that's the solution. It doesn't > matter whether the Telnet terminal window is remote or running on > the local machine as per the results. I'd be surprised if SSH > helped here? As I said last night... There is some difference in the two servers' configuration that is impacting you. Compare logs from the TurboVNC invocations on both machines. Compare package lists. Compare process environment variables. There will be differences, and one (or more) of those differences is what is preventing your desired outcome. - Aaron From adj at fnord.greeley.co.us Wed Feb 19 17:17:13 2025 From: adj at fnord.greeley.co.us (Aaron D. Johnson) Date: Wed, 19 Feb 2025 17:17:13 +0000 Subject: Hi Bob question on getting TurboVNC running In-Reply-To: Your message of "Tue, 18 Feb 2025 23:38:11 -0800." Message-ID: <20250219171714.0101210120@zarathud.internal.fnord.greeley.co.us> Phil Marsh writes: > Indeed /usr/share/xsessions/xubuntu.desktop does exist but > /usr/share/xsessions/gnome.desktop > /usr/share/xsessions/ubuntu.desktop > do NOT exist > I'm wondering why vncserver is trying to use the nonexistent desktops to > start when in SSH or Telnet terminals? What does the documentation say? And what is different in the process environment when connected by a remote terminal compared to your (logged in locally?) session where it does work as you expect? I might be a little off base here, but am reasonably sure you said you are getting different results on two different servers. If that is the case, for the server where it does work as expected, try running dpkg -S /usr/share/xsessions/*desktop This will list out installed packages that contain files in that directory. (Pretty sure you did say you're running Ubuntu. dpkg is the package manager there. But they also have snaps. And probably other things that install files, too.) On the machine where it does not work as expected, are the packages listed installed at all? Is there a TurboVNC option to specify what session you want it to launch? - Aaron From jafo00 at gmail.com Thu Feb 20 02:06:59 2025 From: jafo00 at gmail.com (Sean Reifschneider) Date: Wed, 19 Feb 2025 19:06:59 -0700 Subject: Hi Bob question on getting TurboVNC running In-Reply-To: <20250219171714.0101210120@zarathud.internal.fnord.greeley.co.us> References: <20250219171714.0101210120@zarathud.internal.fnord.greeley.co.us> Message-ID: On Wed, Feb 19, 2025 at 10:18?AM Aaron D. Johnson wrote: > What does the documentation say? And what is different in the process > Unfortunately, it looks like the documentation is fairly sparse. I took a look at it and couldn't even see how to install it. Aside: I agree with Aaron on the call about SSH adding overhead of encryption. I use SSH for nearly every interaction on all my systems, and I'm copying files at gigabit speeds over SSH on top of a tailscale VPN. Gaining public key authentication and host verification is a huge deal. I don't ever allow password authentication on my systems except at the console. Here are a few thoughts: It looks like the developer of TurboVNC offers professional services and is desperately in need of funds, so you may wish to consider buying support from the developer and asking this question of them. There is also a low-traffic user mailing list that might be good to ask on. Next I'd start looking at the "xstartup.turbovnc" script. Try adding some debugging, possibly a "set -xv" to the script to get runtime tracing of the run, but also look at what the script is doing. In particular, it seems to interface with the environment, so you may want to check environment variables on the session where it works and where it doesn't for things like TVNC_WM, DESKTOP_SESSION, DBUS_SESSION_BUS_ADDRESS, DESKTOP_SESSION... The message you are seeing seems to come from line 98 of https://github.com/TurboVNC/turbovnc/blob/main/unix/xstartup.turbovnc so some debugging and understanding of that script where it works and where it doesn't is likely to be enlightening. The message you are seeing when it works comes from line 177. Looks like, from reading that script, the difference is when it works "DESKTOP_SESSION=xubuntu". But there may be some other settings that are influencing it. I imagine when you say you are "at the console" vs "telnet", you are in an X session on the console? That is likely providing some environment settings that is telling the xstartup.turbovnc to use "xubuntu", where the telnet session is triggering the block of code above where it tries "the default window manager". I mean, one option is to, where it works, do "set >itworks", and then from the session where it does not work do "source itworks" to blindly set the environment to match (though that might cause other issues). Sean -------------- next part -------------- An HTML attachment was scrubbed... URL: