Could someone explain this a little more clearly? I didn’t understand what exactly it means.
Thank you.
If enabled in the settings the server chat is selected.
But for most people this is useless because they can not write into server chat it or rarely something is written there.
Setting Open channel chat automatically can be found in the Options > Application Tab.
5 Likes
Warning, for people who are using Plugins in 3.6.0 this version may not work.
2 Likes
Tnx for the hint. Did not update the latest changelog to my initial post.
Plugins must be updated by the author. We will update ours on release day.
7 Likes
The update breaks support for Ubuntu 22.04 (jammy) as it only has the newer libwebp7 in its repositories:
./ts3client_linux_amd64: error while loading shared libraries: libwebp.so.6: cannot open shared object file: No such file or directory
Will forward this to our dev and retest on a fresh machine.
My had no problems but was updated from I think 20.
Tnx
7 Likes
moved by moderator
Hey all, scenario:
Using client 3.5.6 and earlier, I have had a master password set for a long time (to protect my identity etc.).
Updating the client to 3.6.0 beta makes it impossible to open up the client, because it tells me that the master password is wrong. It is NOT wrong.
Workaround: Disable master password in 3.5.6, update to 3.6.0, enable master password.
Even if something changed about the encryption, my master password should stay “valid” if I entered it correctly. Anything I did wrong?
best regards,
@dylan1982
The password still should work after the update. On which operation system is this happening?
We will evaluate this.
2 Likes
btw: in the “Linux dependencies” list the package name libxcb-image should be libxcb-image0 (with a zero at the end)
This happened using Windows 11 22H2 (build 22621.1635) and the current updates from April 2023
KB5025305
KB5025182
KB5025239
KB5025915
I do not use a very complex password in this case - starting with a capital letter, followed by 5 other letters, then two numbers.
I can assure that I did not mistype the password. I have even tried copying it into the master password field to no avail. If I can do anything to help analyze this, let me know.
Best regards,
-dylan
- Our devs is working an a workaround to make client working for Older and latest Ubuntu versions
- Changelog will be changed. Did change it in forum already
- We changed encryption in client libs. We will look into that.
6 Likes
Sorry, but I have to report it again because it has never been this extreme until 3.6.0. Unfortunately I use TS3 more than TS5 because it is faster for me in certain points of administration or these are still missing in TS5.
The written messages are still replaced by the placeholder. I have been sending the placeholder “Enter Chat Message…” more often lately instead of my message or link.
6 Likes
As you know already, this issue did exist before 3.5.7 or 3.6.0 and I could not trigger it that often as shown.
Guess timing is important 
Please retest this with the stable client 3.5.6.
If this happens less for you and is worse again when you go back to 3.6.0, then I may know what could increase that it happens.
You may test this with a clean install of 3.5.6 and config folder (also without setting up myTS login) and later update into beta channel and test again with 3.6.0.
5 Likes
Hi, I do have the same issue. After updating to 3.6.0 Beta it tells me that my master password is wrong. I’m running Windows 10 Pro 22H2 Build 19045.2846.
I remember we had a very similar issue with 3.5.0 Beta (see TeamSpeak - Official TeamSpeak Community Forum). Maybe that’s related to it being broken again.
1 Like
This was reported in post #8 and replied 3 posts above.
Temp solution is to install client 3.5.6 from our website > Remove the password. Then update to beta. There you can set it again. But this password may not work when you go back to 3.5.6.
5 Likes
Another 3.6.0 beta update was released.
This update has 2 fixes.
- Works on new and older Linux distributions. Required libs are in client itself and no longer search in system itself. You may now start the client with the binary directly and not with the runscript.
- Invite dialog missed a
/behind theinvite.teamspeak.comdomain and broke http invites.
- We also changed the date for the beta. But still need to discuss if this can go stable with the issue in the master password. This will delay the stable release at least to june.
Anyone who used a master password in 3.5.6 or older versions.
@green2grey
You now should be able to update from 3.5.6 to latest beta.
7 Likes
Will there be another way for the user to easily see Server Messages and Host Messages when this option is activated?
If not, both message types are going to loose visibility and reach.
1 Like
Sorry for the late reply. This needed a discussion with right person.
For next 3.6.0 Beta and stable release the host and welcome message will be printed in channel chat instead.
–
Also the master password issue will be fixed.
6 Likes
A new beta was released and these are the changes.
- Fixed the master password issue @maxlxl @dylan1982 had
- Fixed the invite dialog where a / was missing behind behind the
invite.teamspeak.com. - When channel chat is activated then welcome message and host message are printed there.
- In change log the release date and
libxcb-image0was changed
9 Likes
