NoMachine 4.3.23 SIGTRAP signals

Forum / NoMachine for Linux / NoMachine 4.3.23 SIGTRAP signals

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #4838
    mebbe
    Participant

    I just installed the latest 4.3 release, and there are a lot of nice improvements. Especially the pixel-perfect rendering in full sessions is an eagerly awaited feature for me!

    Unfortunately I get a large number of crashes in various applications (Xfce file manager, Eclipse (via java crash), …), and when looking at the statistics collected by the abrt-tool in Fedora, they all seem to be killed by a SIGTRAP signal. I have a fairly standard Fedora 20 installation with Xfce.

    One example from crash info collected by abrt:
    $ more package
    Thunar-1.6.3-2.fc20
    $ more reason
    thunar killed by SIGTRAP
    $ more kernel
    3.16.2-201.fc20.x86_64
    $gdb /usr/bin/thunar coredump
    Program terminated with signal SIGTRAP, Trace/breakpoint trap.
    #0  0x0000003a3ca504e9 in g_logv (log_domain=0x3a4da7ef26 “Gdk”, log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7fff9e675a30) at gmessages.c:989
    989            G_BREAKPOINT ();
    (gdb) bt
    #0  0x0000003a3ca504e9 in g_logv (log_domain=0x3a4da7ef26 “Gdk”, log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7fff9e675a30) at gmessages.c:989
    #1  0x0000003a3ca5063f in g_log (log_domain=log_domain@entry=0x3a4da7ef26 “Gdk”, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x3a4da9da74 “%s”)
    at gmessages.c:1025
    #2  0x0000003a4da685eb in gdk_x_error (display=<optimized out>, error=<optimized out>) at gdkmain-x11.c:486
    #3  0x0000003a3ee450bb in _XError () from /lib64/libX11.so.6
    #4  0x0000003a3ee420b7 in handle_error () from /lib64/libX11.so.6
    #5  0x0000003a3ee42175 in handle_response () from /lib64/libX11.so.6
    #6  0x0000003a3ee42b25 in _XEventsQueued () from /lib64/libX11.so.6
    #7  0x0000003a3ee345bd in XPending () from /lib64/libX11.so.6
    #8  0x0000003a4da5ca71 in gdk_check_xpending (display=<optimized out>) at gdkevents-x11.c:159
    #9  0x0000003a4da5cadc in gdk_event_check (source=0x9c5d60) at gdkevents-x11.c:2378
    #10 0x0000003a3ca48ff9 in g_main_context_check (context=context@entry=0x9c5e50, max_priority=2147483647, fds=fds@entry=0xbe95f0, n_fds=n_fds@entry=5) at gmain.c:3557
    #11 0x0000003a3ca49533 in g_main_context_iterate (context=0x9c5e50, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3710
    #12 0x0000003a3ca49a3a in g_main_loop_run (loop=0xc00990) at gmain.c:3907
    #13 0x0000003a4cf45b57 in IA__gtk_main () at gtkmain.c:1257
    #14 0x000000000041f2db in main (argc=2, argv=0x7fff9e676008) at main.c:310

    Problem in Fedora 20, my setup or regression in NX 4.3?

    #5221
    Britgirl
    Participant

    A patch for this issue was released in version 4.3.24. See here:

    https://www.nomachine.com/TR10L04590

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

This topic was marked as solved, you can't post.