Segmentation fault on Arch

Forums / NoMachine for Linux / Segmentation fault on Arch

Tagged: 

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #29135
    Avatarhatunike
    Participant

    I’m unable to start the nxplayer whenever i try to run the application i get :

    415612 segmentation fault (core dumped) ./nxplayer

    I’m using Arch. I’ve tried uninstalling and reinstalling several different ways. Even just downloading the Enterprise Client and always this same error (tried installing via yay -S nomachine, direct tar from site, as well as client stand along application).

     

    NXCLIENT – Version 6.11.2

    NoMachine Enterprise Free Client

    Arch Linux

     

     

    #29180
    AvatarBritgirl
    Keymaster

    We make regular tests on Arch (rolling release) so this is strange.

    Can you tell me what the kernel version is and system architecture?

    Also, what desktop environment are you using?

    #29186
    Avatarhatunike
    Participant

    Arch Linux x86_64
    5.8.3-arch1-1
    i3 (specifically i3-gaps)

    For what it’s worth, i have a friend that has a very similar setup to me (same kernel, same architecture) and everything works great for him.

    #29199
    AvatarBritgirl
    Keymaster

    We tested again with i3-gaps and everything is running fine. Please try with the free x84_64.tar.gz package and tell us if you still get the same behaviour.

    #29215
    Avatarhatunike
    Participant

    Yes, same behavior. I downloaded the free x84_64.tar.gz and installed via the install script. It should be noted that the server is working and does work regardless of the way i install it – it is simply the nxplayer that has the segmentation fault (regardless of how I install it).

    #29247
    Avatarkroy
    Contributor

    Can you send backtrace from the core? Instructions for your system you can find there: https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces. Please send also output of the command: ldd /usr/NX/bin/nxplayer.bin.

    #29347
    Avatarhatunike
    Participant

    I’m pretty new to this stuff, so sorry if i didn’t grab the right stuff. But here is what i’ve found, so i discovered that nxclient is just dumping like every second. I had like 10,000 dumps. i’ll post nxclient AND nxplayer – each had dumps :

    Reading symbols from /usr/NX/bin/nxclient.bin…
    (No debugging symbols found in /usr/NX/bin/nxclient.bin)
    [New LWP 1749644]
    [New LWP 1749651]
    [New LWP 1749653]
    [New LWP 1749652]
    [New LWP 1749649]
    [New LWP 1749650]
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library “/usr/lib/libthread_db.so.1”.
    Core was generated by/usr/NX/bin/nxclient.bin –monitor –pid 3732785′.
    Program terminated with signal SIGSEGV, Segmentation fault.
    #0 0x00007fa1799fa168 in ?? () from /usr/NX/lib/libfreetype.so
    [Current thread is 1 (Thread 0x7fa1769fc8c0 (LWP 1749644))]

    Reading symbols from /usr/NX/bin/nxplayer.bin…
    (No debugging symbols found in /usr/NX/bin/nxplayer.bin)
    [New LWP 1706195]
    [New LWP 1706203]
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library “/usr/lib/libthread_db.so.1”.
    Core was generated by `/usr/NX/bin/nxplayer.bin’.
    Program terminated with signal SIGSEGV, Segmentation fault.
    #0 0x00007f1df9199168 in ?? () from /usr/NX/lib/libfreetype.so
    [Current thread is 1 (Thread 0x7f1df74be8c0 (LWP 1706195))]
    (gdb)

    Just for completeness this is what the coredumpct list kind of looks like, truncated to just a few of the 10,000 logs :

    Thu 2020-09-03 17:23:03 MDT 1705897 1000 1000 11 present /usr/NX/bin/nxclient.bin
    Thu 2020-09-03 17:23:05 MDT 1705999 1000 1000 11 present /usr/NX/bin/nxclient.bin
    Thu 2020-09-03 17:23:06 MDT 1706081 1000 1000 11 present /usr/NX/bin/nxclient.bin
    Thu 2020-09-03 17:23:07 MDT 1706162 1000 1000 11 present /usr/NX/bin/nxclient.bin
    Thu 2020-09-03 17:23:08 MDT 1706195 1000 1000 11 present /usr/NX/bin/nxplayer.bin
    Thu 2020-09-03 17:23:09 MDT 1706242 1000 1000 11 present /usr/NX/bin/nxclient.bin
    Thu 2020-09-03 17:23:10 MDT 1706349 1000 1000 11 present /usr/NX/bin/nxclient.bin
    Thu 2020-09-03 17:23:11 MDT 1706431 1000 1000 11 present /usr/NX/bin/nxclient.bin
    Thu 2020-09-03 17:23:13 MDT 1706506 1000 1000 11 present /usr/NX/bin/nxclient.bin
    Thu 2020-09-03 17:23:45 MDT 1706768 1000 1000 11 present /usr/NX/bin/nxclient.bin

    finally – here is the ldd /usr/NX/bin/nxplayer.bin :

    ldd /usr/NX/bin/nxplayer.bin
    linux-vdso.so.1 (0x00007fff5ca67000)
    libnxdifb.so => not found
    libnxdixl.so => not found
    libnxdiex.so => not found
    libnxcsl.so => not found
    libnxcim.so => not found
    libnxc.so => not found
    libnx.so => not found
    libnxd.so => not found
    libnxn.so => not found
    libnxne.so => not found
    libnxlo.so => not found
    libogg.so => /usr/lib/libogg.so (0x00007fae67edb000)
    libz.so => /usr/lib/libz.so (0x00007fae67ebf000)
    libpixman.so => not found
    libqt.so => not found
    libmdnsd.so => not found
    libdl.so.2 => /usr/lib/libdl.so.2 (0x00007fae67eb9000)
    libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007fae67e97000)
    libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fae67cb8000)
    libm.so.6 => /usr/lib/libm.so.6 (0x00007fae67b72000)
    libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007fae67b58000)
    libc.so.6 => /usr/lib/libc.so.6 (0x00007fae6798f000)
    /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007fae67f0b000)

    #29350
    Avatarkroy
    Contributor

    Please send also backtrace to get detailed information.

    sudo gdb -c [core-file-nxplayer-path] /usr/NX/bin/nxplayer.bin

    Inside gdb program execute command thread apply all bt full and paste output here or attach in the text file.

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.