This client is able to connect to servers and stays responsible while our Chat or myTS system unavailable. It may happen that the client takes longer to close while a reconnect to service is ongoing.
The check for the update in beta 73 will take as long the reconnect is happening. Please be a bit patient.
Here is the full changelog
* Fixed client being unresponsive if chat services are unavailable
* Fixed erroneously replacing emoji text with an image when Rich Text Editing is disabled
* Fixed crash when attempting to connect while not being able to resolve DNS
* Fixed Open Extension directory not working correctly
* Fixed File dialog filters not working correctly
* Fixed Save Image button moving out of frame with long filenames
* Fixed shared servers still being shown after closing the client
* Fixed changed avatars of users sometimes not updating locally
* Fixed a few error messages not showing up correctly
* Improved multiple files with the same name being attached to a chat. The client will append _n to the file name instead of overwriting the previous file
* Improved handling of chat attachments, client will no longer offer download action if the file was previously downloaded and still exists
* Shorten long filenames for chat attachments for display in the UI
* Revamped the user experience when setting / changing your Avatar
* Changed the look of file attachments in chats
* Changed priority for search results, now prioritizes possible TeamSpeak server connection results
* Changed the order of users in the invite to room dialog, now displays users that can be invited at the top
* Changed OS X to macOS again
Notes for this thread
Feedback as per always is welcome in this thread . Issues that are not related to this update belong to it’s own thread.
We suggest to place your wishes for upcoming releases in existing or new threads in the suggestion area instead of the release thread. We mention this because each update post will be closed after some days and the wish or suggestion could be lost.
We allow ourselves to delete all the off-topic posts from this thread.
I’m not sure if the problem I reported has already been fixed in Beta 74.
However, I just had the problem that my client was freezed again, but the chat was displayed on the left, I could only not load new messages and or send, I could therefore no longer perform any actions on the servers.
The whole thing happened when I connected to the alpha and beta server, then the client was there, but no interactions went through. After that I wanted to close the client, but it did not seem to do that properly see:
in addition, apparently the problem with connecting directly after startup (when the chat is still offline) still exists. had just started the client and wanted to connect to my server on the left, but the message came: “Failed to establish connection To Teamspeak Server”.
An error from tschat.log:
[2023-05-09 15:47:09.335] [warning] Get display name failed: Protocol error: error=Profile was not found errorCode=M_NOT_FOUND softLogout=false retryAfterMs=0
[2023-05-09 15:47:09.335] [warning] Failed to find display name for userId=censored
[2023-05-09 15:47:09.668] [error] Last activity ago not found
[2023-05-09 15:47:09.668] [error] Last activity ago not found
Just a general question:
I noticed the most recent TS5 client release is still based on Chromium 109 which has been EOL for quite some time now and generally speaking, it is not advisable to lag behind on those releases, especially when there is a plethora of serious vulnerabilities affecting even recent versions.
In the past week, almost all applications based on e.g. Electron or Chromium of sorts bundling libwebp or image processing libraries using libwebp had to release updates to prevent exploitation. What are TeamSpeak’s plans of dealing with this? It is a quite considerable risk to run the application at this point.
CEF 109 was first released 10 months ago, in December 2022 as a beta, and fully released in January this year. Where did you get this information from?
Chrome EOL’ed Windows 7/8 with version 109, maybe that’s it?
Regarding the webp security concerns, updates were issued for older versions, including 109.
But I agree, TS needs to apply these patches, regardless the chromium version.
Nonetheless, as you said, this does nothing for us if they do not ship a TS version with those changes (we are currently on Chromium “109.0.0.0” which is not even a valid version).
Google’s docs on release cycles are a little bit confusing to me Chromium Docs - Chrome Release Cycle
I assumed that every branch (major stable release) is only maintained for 4-8 weeks.
They seem to point out though that you should stay within the last 4 major release versions to prioritize security and new (security) features.
In any case, there have been 0 TeamSpeak (both beta client and server) patches for any of the vulnerabilities that came into existence for months!
. Issues that are not related to this update belong to it’s own thread.
