Allan Hall's community posts

because the upgrade fr om 22.04.4 LTS to 24.10 LTS broke they system. System errors all over the place.

That doesnt explain why going from 22.04.2 LTS to 22.04.4 LTS broke the RU.

I have a virtual environment here wh ere I could test and see what you were seeing but I am confused. In one paragraph you say you went from 22.04.4 to 24.10 (which does not exist) and in the next paragraph you say you went from 22.04.2 to 22.04.4. Could you please clarify?

A few items I have noticed while using the Linux beta 1.0.17.

1) Using the address book manager I can not see an import into the General address book. I created a new book and told it to use the XML exported fr om my Windows version. While this works, kinda, I now can not delete the old General address book I am not using.

2) Attempting to delete the General address book using the X delete from the main screen causes the software to crash and the General address book remains.

3) Renaming a new address book in the address book manager causes the software to crash although the name change works.

4) Single clicking to select a client instead tried to connect to it. There seems to be no way to select so I can copy paste to a different address book.

5) The sort order is different in the Linux version as compared to the Windows version. In my Windows version the items I want at the beginning I have proceeded by a ! character. In the Linux version this seems to have no effect as the list is sorted by the second character. In other words....

Windows sort order:
!!Temp
!!Temp2
!Print Server 1
!Print Server 2
Alpha
Bravo
Etc etc

But in Linux I get this instead:
Alpha
Bravo
Delta
Echo
Foxtrot
Golf
Hotel
India
Juliet
Kilo
Lima
Metro
November
Oscar
!Print Server 1
!Print Server 2
Quebec
Romeo
Sierra
!!Temp
!!Temp2
Uniform
Victor
etc etc.

While this is minor, it is very annoying. I would prefer you pick one, either one, and stick with it across platforms. It can be frustrating when you are already dealing with a client who did something stupid and now the remote info is not wh ere you expect it to be.

6) If you are using a dark theme (I am running KDE Plasma with the default dark theme) when you connect to an agent the three boxes at the top of the screen are VERY hard to tell have any markings on them. In fact, I just clicked on each one to see what it did, I could not read anything on the buttons. Now the fly-out on the right button with the little three line menu, that is great, no issues.

I have to admit I have not been using the Linux version that much but it is working pretty well overall for a beta.

Yes, switching to xorg instead of Wayland solved that issue. Can I assume that support for Wayland is eventually coming?

A point to help others, if you attempt to switch to xorg from Wayland in VB7 you will no longer be able to log in. Close the VM, enable 3D acceleration in the settings, relaunch the VM and you should be good.

I also want to make sure I am doing the install right as Linux is not really a comfortable arena for me. The only way I could get it to "install" is to use dpkg. Double clicking on it, right click and select archive manager, right click and select open with...run software, all do not actually install the software. Using dpkg installs it so that I can then hit the Windows key and search for it, then run it.

Is that correct or am I missing something?

Agent 1.0.17.b17_amd64 on 64bit Ubuntu 23.10. It shows in the viewer under Windows 11 as running but when I connect I get the normal "Connecting to ....  Please wait" screen, then the screen on the viewer goes black and thats it. The Ubuntu install is running in VirtualBox (7.0.14) on the same computer so I can see both screens. I do not believe It is just a display problem because I have an active terminal and keypresses are not transmitted and right clicks do nothing. On the Ubuntu machine, I can see in the Remote Utilities pop-up the other machine is showing as connected.

Ideas?

Been about a month, any news?

Been almost a week, any word? This is making it VERY difficult to support my customer.

Logs from V6 and V7 viewer sent.

I just double-checked to be sure, my primary DNS is Google at 8.8.8.8, my secondary is Level3 at 4.2.2.2.

I did a nslookup from my PC (which typically runs the viewer, 6.10.10), the PC running 7.2.2.0 viewer on the same network as the agent, and the PC running the agent. In addition, I directly queried 8.8.8.8 (Google), 4.2.2.2 (level3), and 1.1.1.1 (Cloudflare). All of the results were the same, 64.20.61.146.

Flushing the DNS cache has no effect.