Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#57207 - [teamspeak3] Invalid filepath for teamspeak3 binary in launch script

Attached to Project: Community Packages
Opened by Philipp Lindner (vredez) - Tuesday, 23 January 2018, 19:32 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 28 January 2018, 11:29 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 15
Private No

Details

Description:

The binary which is pointed to by the /usr/bin/teamspeak3 launchscript does not exist anymore:
<code bash>
$ teamspeak3
/usr/bin/teamspeak3: line 46: ./ts3client_linux_amd64: No such file or directory
</code>

Additional info:
* package version: 3.1.8-1

Steps to reproduce:

Install teamspeak3 3.1.8-1 and run it via the teampspeak3 launch script
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Sunday, 28 January 2018, 11:29 GMT
Reason for closing:  Fixed
Comment by Yuri Santos (broodinho) - Wednesday, 24 January 2018, 17:09 GMT
A think this is happening because the working directory of the initialization script is pointing to "/usr/bin/" (which is the path of symbolic link) instead "/opt/teamspeak3/" where the real script file is located.
I don't know the most correct way to fix this, but instead of cd "$(dirname "${BASH_SOURCE[0]}")"on the #3 line, you can put cd "$(dirname "$(realpath "$0")")"
This way the script get the original path of script instead of symbolic link.

OFF: I don't know how to post code blocks, sorry...
Comment by Phillip Schichtel (pschichtel) - Wednesday, 24 January 2018, 18:39 GMT
Upstream report: https://forum.teamspeak.com/threads/134617-Linux-client-not-starting-when-run-though-symlink-since-3-1-8?p=454315#post454315

Loading...