Forum

Page 3 of 4 FirstFirst 1234 LastLast
Results 31 to 45 of 47
  1. #31
    Join Date
    June 2018
    Location
    Poland
    Posts
    98
    I sent the logs and crash dumps. I don't understand why u said I didn't.

  2. #32
    Join Date
    October 2003
    Location
    Germany
    Posts
    2,527
    Quote Originally Posted by Well_Skilled View Post
    I sent the logs and crash dumps. I don't understand why u said I didn't.
    Unfortunately, those are outdated. Please re-send your current crashdumps and logs so we can investigate the issue.

  3. #33
    Join Date
    August 2018
    Location
    DE
    Posts
    19
    Works fine so far. But is it only for me, that unicode symbols or emojis in channelnames aren't aligned properly centered?

  4. #34
    Join Date
    November 2017
    Location
    Cologne, Germany
    Posts
    181
    Quote Originally Posted by TwentyFour View Post
    Works fine so far. But is it only for me, that unicode symbols or emojis in channelnames aren't aligned properly centered?
    No, that's indeed a little odd. The Qt update apparently changed something about the way how those are rendered. Multiple people reported that already and my own channel descriptions are also affected.

  5. #35
    Join Date
    October 2003
    Location
    Germany
    Posts
    2,527
    Quote Originally Posted by RandomHost View Post
    No, that's indeed a little odd. The Qt update apparently changed something about the way how those are rendered. Multiple people reported that already and my own channel descriptions are also affected.
    Well... that's Qt. But hey... at least emojis are colored now on Windows.


  6. #36
    Join Date
    June 2018
    Location
    Poland
    Posts
    98

    Badges

    Hey. Badges are gone while using version 3.3.0
    Last edited by dante696; July 1st, 2019 at 01:17 PM. Reason: merged

  7. #37
    Join Date
    June 2008
    Posts
    18,151
    They are not gone.
    Code:
    + Added support for signed badges to prevent usage of fake data. Note, that
      this feature requires TeamSpeak Server version 3.8.0 or later.
    Use server 3.9.0 and they are back.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  8. #38
    Join Date
    June 2018
    Location
    Poland
    Posts
    98
    I use 3.9.0 already. Everything worked before update to 3.3.0 client.

  9. #39
    Join Date
    June 2008
    Posts
    18,151
    And you still do not see the badges you have active in your account?
    Can you share the the server address so i can test it there? You can do that in a private message in case you don't want to share it to the public.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  10. #40
    Join Date
    June 2018
    Location
    Poland
    Posts
    98
    IP: ts5.red
    U can check it.

  11. #41
    Join Date
    June 2008
    Posts
    18,151
    After you did send me a screenshot and the log i would say the cache is broken or you get blocked by Cloudflare.

    Please try to clear the client cache once
    - Disconnect from all servers
    - Open "Tools -> Options -> Security"
    - Click "Clear Cache" button
    - Let everything you want to delete checked.
    - Press OK
    Last edited by dante696; July 1st, 2019 at 03:35 PM. Reason: changed how to a bit
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  12. #42
    Join Date
    June 2018
    Location
    Poland
    Posts
    98
    Ok it works correctly. Thanks for help Dante

  13. #43
    Join Date
    July 2019
    Posts
    1

    Crash on Linux 5.1.15-300.fc30.x86_64 / TeamSpeak3-Client-linux_amd64-3.3.0

    Hi there, I'm experiencing a crash with TeamSpeak3-Client-linux_amd64-3.3.0.

    I did a clean install, ran TeamSpeak3-Client-linux_amd64-3.3.0.run, and no ~/.ts3client present.

    Running TeamSpeak3-Client-linux_amd64/ts3client_runscript.sh works fine.

    When I go: Tools > Options > Capture and try to do a test, no matter the settings (I tried all of them, I'm using Pulseaudio, as do most Linux users these days), the client immediately crashes.

    I can see the level meter moving for a split second, before the client simply disappears.

    The same thing happens, with setting capture correctly (as I know what devices I should select), and then connecting to a server, and then trying to transmit (holding the PTT key, or simply invoking voice activation transmit).

    This is what the program reports on crash:

    Right after either starting a test, or transmitting, this line appears for a split second, before crashing:
    Code:
    2019-07-01 20:20:17.020296|INFO    |PreProSpeex   |2  |Speex version: 1.2rc1
    Obviously this is just an info that the Speex codec is used.

    and then upon crashing this is the output:

    Code:
    Received signal 4 ILL_ILLOPN 000000f15850
    #0 0x7fb10eac6dfc <unknown>
    #1 0x7fb10eac6951 <unknown>
    #2 0x7fb114811e80 <unknown>
    #3 0x000000f15850 <unknown>
    #4 0x000000c621b3 <unknown>
    #5 0x000000c75ef9 <unknown>
    #6 0x000000c652e5 <unknown>
    #7 0x000000c64561 <unknown>
    #8 0x000000c5d4a0 <unknown>
    #9 0x000000c58acf <unknown>
    #10 0x000000c5f43d <unknown>
    #11 0x7fb1148075a2 start_thread
    #12 0x7fb10c23f303 __GI___clone
      r8: 0000000000000f00  r9: 00000000000003c0 r10: 00000000000003c0 r11: 00007fb0fc38f7f0
     r12: 0000000000000000 r13: 00007fb058009d70 r14: 00007fb0fc38f650 r15: 0000000000000001
      di: 0000000005fa57e0  si: 00007fb0fc38e750  bp: 00007fb0fc38f680  bx: ffffffffffffff88
      dx: 00000000000003c0  ax: 0000000000000000  cx: 00000000000003c0  sp: 00007fb0fc38e750
      ip: 0000000000f15850 efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000000
     trp: 0000000000000006 msk: 0000000000000000 cr2: 0000000000000000
    [end of stack trace]
    Calling _exit(1). Core file will not be generated.



    I manually did export LD_LIBRARY_PATH=".:$LD_LIBRARY_PATH", and ran ldd ./ts3client_linux_amd64, giving me this output:

    Code:
    	linux-vdso.so.1 (0x00007ffe10dfa000)
    	libquazip.so => ./libquazip.so (0x00007f321e3bf000)
    	libdl.so.2 => /lib64/libdl.so.2 (0x00007f321e36c000)
    	librt.so.1 => /lib64/librt.so.1 (0x00007f321e362000)
    	libz.so.1 => /lib64/libz.so.1 (0x00007f321e348000)
    	libm.so.6 => /lib64/libm.so.6 (0x00007f321e202000)
    	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f321e1df000)
    	libQt5Core.so.5 => ./libQt5Core.so.5 (0x00007f321dbb6000)
    	libQt5Gui.so.5 => ./libQt5Gui.so.5 (0x00007f321d5fb000)
    	libQt5Network.so.5 => ./libQt5Network.so.5 (0x00007f321d470000)
    	libQt5Widgets.so.5 => ./libQt5Widgets.so.5 (0x00007f321ce12000)
    	libQt5Sql.so.5 => ./libQt5Sql.so.5 (0x00007f321cdd8000)
    	libQt5WebEngineCore.so.5 => ./libQt5WebEngineCore.so.5 (0x00007f32162d5000)
    	libQt5WebEngineWidgets.so.5 => ./libQt5WebEngineWidgets.so.5 (0x00007f3216294000)
    	libQt5WebChannel.so.5 => ./libQt5WebChannel.so.5 (0x00007f3216274000)
    	libQt5Svg.so.5 => ./libQt5Svg.so.5 (0x00007f321621f000)
    	libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f3216205000)
    	libc++.so.1 => ./libc++.so.1 (0x00007f3215f38000)
    	libc++abi.so.1 => ./libc++abi.so.1 (0x00007f3215d06000)
    	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f3215cec000)
    	libc.so.6 => /lib64/libc.so.6 (0x00007f3215b26000)
    	/lib64/ld-linux-x86-64.so.2 (0x00007f321e5ee000)
    	libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007f3215b21000)
    	libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f32159fd000)
    	libGL.so.1 => /lib64/libGL.so.1 (0x00007f3215967000)
    	libQt5Quick.so.5 => ./libQt5Quick.so.5 (0x00007f32154e4000)
    	libQt5Qml.so.5 => ./libQt5Qml.so.5 (0x00007f321501f000)
    	libQt5Positioning.so.5 => ./libQt5Positioning.so.5 (0x00007f3214f99000)
    	libnss3.so => /lib64/libnss3.so (0x00007f3214e66000)
    	libnssutil3.so => /lib64/libnssutil3.so (0x00007f3214e31000)
    	libsmime3.so => /lib64/libsmime3.so (0x00007f3214e06000)
    	libplds4.so => /lib64/libplds4.so (0x00007f3214e01000)
    	libplc4.so => /lib64/libplc4.so (0x00007f3214dfa000)
    	libnspr4.so => /lib64/libnspr4.so (0x00007f3214db8000)
    	libexpat.so.1 => /lib64/libexpat.so.1 (0x00007f3214d8a000)
    	libfreetype.so.6 => /lib64/libfreetype.so.6 (0x00007f3214ccb000)
    	libfontconfig.so.1 => /lib64/libfontconfig.so.1 (0x00007f3214c83000)
    	libX11.so.6 => /lib64/libX11.so.6 (0x00007f3214b3e000)
    	libX11-xcb.so.1 => /lib64/libX11-xcb.so.1 (0x00007f3214b39000)
    	libxcb.so.1 => /lib64/libxcb.so.1 (0x00007f3214b0e000)
    	libXcomposite.so.1 => /lib64/libXcomposite.so.1 (0x00007f3214b09000)
    	libXcursor.so.1 => /lib64/libXcursor.so.1 (0x00007f3214afa000)
    	libXdamage.so.1 => /lib64/libXdamage.so.1 (0x00007f3214af5000)
    	libXext.so.6 => /lib64/libXext.so.6 (0x00007f3214ae0000)
    	libXfixes.so.3 => /lib64/libXfixes.so.3 (0x00007f3214ad7000)
    	libXi.so.6 => /lib64/libXi.so.6 (0x00007f3214ac5000)
    	libXrender.so.1 => /lib64/libXrender.so.1 (0x00007f3214ab8000)
    	libXtst.so.6 => /lib64/libXtst.so.6 (0x00007f3214aad000)
    	libXss.so.1 => /lib64/libXss.so.1 (0x00007f3214aa8000)
    	libpci.so.3 => /lib64/libpci.so.3 (0x00007f3214a97000)
    	libasound.so.2 => /lib64/libasound.so.2 (0x00007f3214990000)
    	libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007f321493a000)
    	libxml2.so.2 => /lib64/libxml2.so.2 (0x00007f32147cf000)
    	libxslt.so.1 => /lib64/libxslt.so.1 (0x00007f3214789000)
    	libEGL.so.1 => /lib64/libEGL.so.1 (0x00007f3214773000)
    	libQt5PrintSupport.so.5 => ./libQt5PrintSupport.so.5 (0x00007f3214713000)
    	libQt5QuickWidgets.so.5 => ./libQt5QuickWidgets.so.5 (0x00007f32146ff000)
    	libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f3214689000)
    	libGLX.so.0 => /lib64/libGLX.so.0 (0x00007f3214655000)
    	libGLdispatch.so.0 => /lib64/libGLdispatch.so.0 (0x00007f3214598000)
    	libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f3214584000)
    	libpng16.so.16 => /lib64/libpng16.so.16 (0x00007f321454e000)
    	libXau.so.6 => /lib64/libXau.so.6 (0x00007f3214546000)
    	libsystemd.so.0 => /lib64/libsystemd.so.0 (0x00007f3214496000)
    	liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f321446d000)
    	liblz4.so.1 => /lib64/liblz4.so.1 (0x00007f321444e000)
    	libgcrypt.so.20 => /lib64/libgcrypt.so.20 (0x00007f321432e000)
    	libgpg-error.so.0 => /lib64/libgpg-error.so.0 (0x00007f321430b000)
    As you can see, libraries are found and things should be working fine.




    OS: Fedora release 30 (Thirty) x86_64
    Kernel: 5.1.15-300.fc30.x86_64
    DE: Xfce
    WM: Xfwm4
    Pulseaudio: 12.2-6.fc30
    ALSA: 1.1.9-1.fc30

    last update: checked just now, no outstanding updates.

    Hope you guys can help.

    Cheers!
    --poolb

  14. #44
    Join Date
    July 2019
    Posts
    2

    Crash on incoming sound

    • Os: Linux arch
    • CPU: AMD Phenom(tm) II X6 1075T Processor
    • Soundcard 1: VF0790 [Live! Cam Chat HD VF0790], device 0: USB Audio [USB Audio]
    • Soundcard 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio]


    Since the last update (3.3.0-1, installed via official arch linux repos) the TS3 client crashes on incoming sound.
    Terminal output is just:

    Code:
    /usr/bin/teamspeak3: line 47: 26724 Illegal instruction     (core dumped) ./ts3client_linux_amd64 -platform xcb [email protected]
    Downgraded to version 3.2.5-1, still works fine and without any problems.
    The problem is not server-specific (tried various servers). When everything is muted, no crash occurs, so it's definitely on incoming sound.
    I tried deleting any configurations or user-specific files. I tried PulseAudio, ALSA and Jack for both capture and playback settings.
    Someone on the IRC channel suggested you might be requiring SSE4 now, which my CPU doesn't have. Is that true?

    I'll provide any information needed if you ask.

    Cheers,
    Pablo

  15. #45
    Join Date
    August 2018
    Location
    DE
    Posts
    19
    One of the 3.3.0betas indeed crashed on incoming audio, but was fixed in the stable 3.3.0 ... so I recommend you update to those.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. [Discussion] TeamSpeak 3 Client 3.2.1
    By Chris in forum Suggestions and Feedback
    Replies: 25
    Last Post: September 4th, 2018, 07:53 AM
  2. [Discussion] TeamSpeak 3 Client 3.1.8
    By Chris in forum Suggestions and Feedback
    Replies: 12
    Last Post: May 8th, 2018, 01:37 PM
  3. [Discussion] TeamSpeak 3 Client 3.1.7
    By Chris in forum Suggestions and Feedback
    Replies: 9
    Last Post: December 27th, 2017, 02:49 PM
  4. [Discussion] TeamSpeak 3 Client 3.1.6
    By Chris in forum Suggestions and Feedback
    Replies: 17
    Last Post: December 19th, 2017, 01:56 PM
  5. [Discussion] TeamSpeak 3 Client 3.0.19.*
    By Justinien in forum Suggestions and Feedback
    Replies: 18
    Last Post: July 20th, 2016, 06:42 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •