[Discussion] TeamSpeak 3 Client 3.1.6

[Chris]

This thread is for discussion and feedback for the 3.1.6 release of the TeamSpeak Client.
Please see the announcement for changelog / features.

All posts related to myTeamSpeak's Server Nickname have been moved to a new thread since this is not a client topic -> Feedback or Problems with Server nickname

[Wulf_]

Hello,
ts3 client on linux updated to 3.1.6, didn't start anymore.
Error message when started in terminal: terminating with uncaught exception of type boost::system::system_error: Error creating HTTP connection factory: X509 - Read/write of file failed

I ran strace:
[pid 24975] stat("/usr/lib/ssl/certs/cacert.pem", 0x7fff27cb45a8) = -1 ENOENT (No such file or directory)

$ ls /usr/lib/ssl/certs/cacert.pem -l
lrwxrwxrwx 1 root root 44 Jun 23 2014 /usr/lib/ssl/certs/cacert.pem -> /usr/share/ca-certificates/cacert/cacert.crt


Removing the dead symlink fixed the issue, ts3 works again.


I have no idea why there was a dead symlink, but this should not cause ts3 to crash on start.

[X3r0X]

Hello,
whats the purpose of still showing it every 6 hours? Why not showing it just once "per session", there is a red exclamation mark the statusubar anyways. Just remind the user while closing that "settings" haven't been synced?!

* Don't spam "failed to connect to myteamspeak server" notifications. Show
it once after client start and then again only in intervals of 6 hours.

Cheers

[dante696]

Once per session and the warning in the status bar wasn't enough in our opinion.

We wanted to find a value that is bigger than every 5-10 minutes but still doesn't annoy every hour. So we choose to show it every 6 hours instead.

[X3r0X]

Hey dante696,
I really think myTeamspeak is increasing value of Teamspeak, but the message doesn't increase value in anyway as I can't do anything about it to fix.

However just my 2 cents.

Cheers

[dante696]

Sure we appreciate your opinion.

We started with 6 hours because we had no other feedback or opinion so far. This behavior still can be changed in a future update.
Maybe once per session is enough.

----------------------------------------------------

Important
All posts related to myTeamSpeak's Server Nickname have been moved to a new thread since this is not a client topic -> Feedback or Problems with Server nickname

[pr00cw]

TS3 crashes on KUbuntu 17.04 since a fresh-install of today.
It was working before on the same OS.

strace -o strace.log ./ts3client_runscript.sh
QCoreApplication::applicationDirPath: Please instantiate the QApplication object first
terminating with uncaught exception of type boost::system::system_error: Error creating HTTP connection factory: X509 - Read/write of file failed
./ts3client_runscript.sh: line 51:  4661 Aborted                 ./ts3client_linux_amd64 [email protected]

See attachement.
The reported file "/usr/lib/ssl/cert.pem" does NOT exist on my system.

[dante696]

The client requires a working and readable certificate to be installed on your system to make ssl connections or else the client will not work.

stat("/usr/lib/ssl/cert.pem", 0x7fff06275630) = -1 ENOENT (No such file or directory)

[pr00cw]

I'm not sure what exactly you mean.
Under '/usr/lib/ssl/certs/' are all my trusted certificates.
I don't think you mean creating an own certificate, do you ?

Edit
Installed 3.1.5 and everything is working again.
I assume teamspeak starts looking in the wrong places for it's files with 3.1.6
For everyone else with that problem: http://ftp.4players.de/pub/hosted/ts3/releases/3.1.5/ and you're running again.
TLDR: 3.1.6 on (K)Ubuntu 17 is broken use 3.1.5

[Chris]

Make sure to use the provided start script to start the client. The start script provided with the client will attempt to use the system openssl installation to determine the path to the trusted root certificates.
Make sure you do not have SSL_CERT_FILE or SSL_CERT_DIR environment variables set. If either of these variables is set, these variables will be honored and used instead of the location being automatically detected.

[pr00cw]

Make sure to use the provided start script to start the client. The start script provided with the client will attempt to use the system openssl installation to determine the path to the trusted root certificates.

I'm always using the ts3client_runscript.sh, (in fact none version will start without it, as the QT libs won't be found otherwise).

Make sure you do not have SSL_CERT_FILE or SSL_CERT_DIR environment variables set. If either of these variables is set, these variables will be honored and used instead of the location being automatically detected.

[email protected]:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
[email protected]:~$ echo $SSL_CERT_FILE

[email protected]:~$ echo $SSL_CERT_DIR

[email protected]:~$

[Wulf_]

You're looking at the wrong stuff.
pr00cw provided an strace of only the shell script.
if [ -f "${OPENSSL_DIR}/cert.pem" ] results in the failed stat call. Really not a problem.
The script will set SSL_CERT_DIR=/usr/lib/ssl/certs

The problem is that some code will try to read each and every file in $SSL_CERT_DIR.
openssl usually uses hashes to read only the files it really needs, e.g. /etc/ssl/certs/119afc2e.0

But the new ts3 client reads them all. And fails if one cannot be opened. It's a bug in ts3, not on our systems.

[dante696]

Thanks for all the details you gave us.
Unfortunately we could not reproduce this on any Linux system so far but we are investigating in that problem.

[reichi]

Thanks for all the details you gave us.
Unfortunately we could not reproduce this on any Linux system so far but we are investigating in that problem.

Same issue here.
I'm on Linux Mint 18.2 (ubuntu 16.04 will have the same issues)

[srg84]

Hi All!!

The solution in Linux Mint is simple!

Delete or comment this block of text in ts3client_runscript.sh

if [ -f ./libssl.so.* ]
then
  #Bundeled libssl is used. Now make sure SSL_CERT_FILE or SSL_CERT_DIR are not
  #already set. If they are, we respect those settings.
  if [ -z "$SSL_CERT_FILE" ] && [ -z "$SSL_CERT_DIR" ]
  then
     #get ssl dir according to system openssl
     OPENSSL_DIR=`openssl version -d | grep -Po '(?<=\").*(?=\")'`

	 #Is cert.pem located there?
     if [ -f "${OPENSSL_DIR}/cert.pem" ]
     then
	   #Use this file
       export SSL_CERT_FILE=${OPENSSL_DIR}/cert.pem

	 #Is certs dir located there?
     elif [ -d "${OPENSSL_DIR}/certs" ]
     then
	   #Use this dir
       export SSL_CERT_DIR=${OPENSSL_DIR}/certs
     else
	   #An unknown configuration was found. Or openssl/ca certificates were not
	   #installed
       echo "Could not find CA certificates location"
       exit 3
    fi
  fi
fi

I think the problem is that we have $SSL_CERT_FILE and $SSL_CERT_DIR variables empty, but the script "thinks" he have values on them.