FS#57208 - [teamspeak3] 3.1.8-1 does not start

Attached to Project: Community Packages
Opened by Nils Siemons (re-l124c41) - Tuesday, 23 January 2018, 19:42 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 23 January 2018, 23:31 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 6
Private No

Details

Description:
Teamspeak does not start anymore after I updated to 3.1.8-1.
When I try to start it from a terminal it reports:

/usr/bin/teamspeak3: line 46: ./ts3client_linux_amd64: No such file or directory

The file DOES exist, so I suspect there must be some issue with the runscript which causes it to not find the binary.

Additional info:
* package version(s): 3.1.8-1

Steps to reproduce:
Attempt to run teamspeak3.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 23 January 2018, 23:31 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#57207 
Comment by J (J) - Tuesday, 23 January 2018, 20:06 GMT
A workaround right now is to run /opt/teamspeak3/ts3client_runscript.sh directly.
Comment by Nils Siemons (re-l124c41) - Tuesday, 23 January 2018, 20:10 GMT
I can confirm running the runscript directly works as a workaround.
Comment by Steffen Klee (kleest) - Tuesday, 23 January 2018, 22:13 GMT
This is because of the following changes in the upstream runscript:

--- a/3.1.7/ts3client_runscript.sh
+++ b/3.1.8/ts3client_runscript.sh
@@ -1,40 +1,36 @@
#!/bin/bash

-D1=$(readlink -f "$0")
-D2=$(dirname "${D1}")
-cd "${D2}"
+cd "$(dirname "${BASH_SOURCE[0]}")"

readlink resolves the symlink /usr/bin/teamspeak3 pointing to /opt/teamspeak3/ts3client_runscript.sh correctly whereas BASH_SOURCE does not (not to mention this is bash-only).

Loading...