Re: guacd segmentation fault

El 11.02.22 a las 14:33, Nick Couchman escribió: > On Fri, Feb 11, 2022 at 5:19 AM Jürgen Kuri > wrote: > > El 10.02.22 a las 14:27, Vieri escribió: > > Hi, > > > > Everything seems to work fine on my system except for RDP connections. > In syslog

Re: guacd segmentation fault

On Fri, Feb 11, 2022 at 5:19 AM Jürgen Kuri wrote: > El 10.02.22 a las 14:27, Vieri escribió: > > Hi, > > > > Everything seems to work fine on my system except for RDP connections. > In syslog I can see this segfault: > > > > guacd[122526]: freerdp_connect:freerdp_set_last_error_ex resetting

Re: guacd segmentation fault

El 10.02.22 a las 14:27, Vieri escribió: > Hi, > > Everything seems to work fine on my system except for RDP connections. In > syslog I can see this segfault: > > guacd[122526]: freerdp_connect:freerdp_set_last_error_ex resetting error state > guacd[122526]: Support for CLIPRDR (clipboard

Re: guacd segmentation fault

On Thu, Feb 10, 2022, 05:28 Vieri wrote: > Hi, > > Everything seems to work fine on my system except for RDP connections. In > syslog I can see this segfault: > > ... > > I'm using freerdp 2.4.1. > Was this the same version of FreeRDP that was present when guacamole-server was built, or was

guacd segmentation fault

Hi, Everything seems to work fine on my system except for RDP connections. In syslog I can see this segfault: guacd[122526]: freerdp_connect:freerdp_set_last_error_ex resetting error state guacd[122526]: Support for CLIPRDR (clipboard redirection) registered. Awaiting channel connection.

Re: guacd segmentation fault

On Wednesday, January 29, 2020, 9:03:12 AM GMT+1, Mike Jumper wrote: > > To disconnect, you hit Ctrl+Alt+Shift to open the menu, click the dropdown > with your username, and select "Disconnect". You can also > always open your connection in a new tab and close the tab when you're done. The

Re: guacd segmentation fault

On Tue, Jan 28, 2020, 23:30 Vieri wrote: > On Wednesday, January 29, 2020, 8:19:50 AM GMT+1, Nick Couchman < > vn...@apache.org> wrote: > > > >> I'd like to ask a related question, though. How can I disconnect a VNC > connection from Guacamole without having to log out (from > >> Guacamole,

Re: guacd segmentation fault

On Wednesday, January 29, 2020, 8:30:17 AM GMT+1, Vieri wrote: > > If I open more VNC connections and come back to the "recent list", I get even > more of these messages. Correction: I only see the "last"/most recent VNC connection as active. However, I'm not sure the "less recent" VNC

Re: guacd segmentation fault

On Wednesday, January 29, 2020, 8:19:50 AM GMT+1, Nick Couchman wrote: > >> I'd like to ask a related question, though. How can I disconnect a VNC >> connection from Guacamole without having to log out (from >> Guacamole, that is)? What I mean is that if I connect to several VNC servers >>

Re: guacd segmentation fault

> > > I'd like to ask a related question, though. How can I disconnect a VNC > connection from Guacamole without having to log out (from Guacamole, that > is)? What I mean is that if I connect to several VNC servers from the > Guacamole connection list and come back to the main panel (connection >

Re: guacd segmentation fault

On Wednesday, January 29, 2020, 5:16:04 AM GMT+1, Mike Jumper wrote: > >> Thread 2.6 "guacd" received signal SIGSEGV, Segmentation fault.> [Switching >> to Thread 0x768ea700 (LWP 5855)] >> 0x77daabd0 in free () from /lib64/libc.so.6 >> (gdb) bt >> #0  0x77daabd0 in free ()

Re: guacd segmentation fault

On Tue, Jan 28, 2020 at 4:01 PM Vieri wrote: > > > On Tuesday, January 28, 2020, 7:19:07 PM GMT+1, Mike Jumper < > mjum...@apache.org> wrote: > > > > If it's possible in Gentoo to install debug symbols for libvncclient, > that might get a more meaningful backtrace from gdb, seeing as the

Re: guacd segmentation fault

On Tuesday, January 28, 2020, 7:19:07 PM GMT+1, Mike Jumper wrote: > > If it's possible in Gentoo to install debug symbols for libvncclient, that > might get a more meaningful backtrace from gdb, seeing as the segfault is > occuring within > libvncclient and it's not currently clear

Re: guacd segmentation fault

On Tue, Jan 28, 2020, 10:11 Vieri wrote: > > On Tuesday, January 28, 2020, 6:48:07 PM GMT+1, Vieri > wrote: > > Hhmm, it seems that my distro has recently published a patch to fix this > "crash on exit". I will apply it to see if the segfaults go away. > > > > >

Re: guacd segmentation fault

On Tuesday, January 28, 2020, 6:48:07 PM GMT+1, Vieri wrote: > Hhmm, it seems that my distro has recently published a patch to fix this > "crash on exit". I will apply it to see if the segfaults go away. > > 

guacd segmentation fault

Hhmm, it seems that my distro has recently published a patch to fix this "crash on exit". I will apply it to see if the segfaults go away.

Re: guacd segmentation fault

On Tuesday, January 28, 2020, 5:49:54 PM GMT+1, Mike Jumper wrote: >> (gdb) bt >> #0  0x77daabd0 in free () from /lib64/libc.so.6 >> #1  0x7699746d in rfbClientCleanup () from >> /usr/lib64/libvncclient.so.1 >> #2  0x769ac26c in guac_vnc_client_free_handler >>

Re: guacd segmentation fault

On Tue, Jan 28, 2020, 08:37 Vieri wrote: > ... > (gdb) bt > #0 0x77daabd0 in free () from /lib64/libc.so.6 > #1 0x7699746d in rfbClientCleanup () from > /usr/lib64/libvncclient.so.1 > #2 0x769ac26c in guac_vnc_client_free_handler > (client=0x7000b390) at

Re: guacd segmentation fault

On Tuesday, January 28, 2020, 4:47:33 PM GMT+1, Mike Jumper wrote: > > If you are starting from the main guacd process, you need to use "set > follow-fork-mode child" or gdb will stay with the parent process (11254 > above) rather than > follow the child processes (11321and 11338 above)

Re: guacd segmentation fault

On Tue, Jan 28, 2020, 03:08 Vieri wrote: > On Tuesday, January 28, 2020, 8:18:38 AM GMT+1, Nick Couchman < > vn...@apache.org> wrote: > > > > Note that it's quite possible you're hitting a bug or known issue in the > libvnc implementation. The stack trace will be helpful. > > I recompiled

Re: guacd segmentation fault

On Tuesday, January 28, 2020, 8:18:38 AM GMT+1, Nick Couchman wrote: > > Note that it's quite possible you're hitting a bug or known issue in the > libvnc implementation.  The stack trace will be helpful. I recompiled guacd with -g -O0, then I ran the following through gdb. # gdb

guacd segmentation fault

BTW, I do not see the "disconnect" item as in https://guacamole.apache.org/doc/gug/using-guacamole.html#client-user-menu. I only see: Home, Settings, Logout. - To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org For

Re: guacd segmentation fault

On Tuesday, January 28, 2020, 8:18:38 AM GMT+1, Nick Couchman wrote: > > Note that it's quite possible you're hitting a bug or known issue in the > libvnc implementation.  The stack trace will be helpful. I guess I need to recompile guacd with debugging symbols (-g). I'll try asap. In any

Re: guacd segmentation fault

On Tue, Jan 28, 2020 at 2:14 AM Vieri wrote: > Hi, > > The segmentation fault seems to happen only when closing VNC sessions, and > it also seems to occur when logging out the guacamole client. I have a > feeling I'm not closing my VNC sessions properly. How do you properly close > a VNC

guacd segmentation fault

Hi, The segmentation fault seems to happen only when closing VNC sessions, and it also seems to occur when logging out the guacamole client. I have a feeling I'm not closing my VNC sessions properly. How do you properly close a VNC connection in Guacamole? Vieri

Re: guacd segmentation fault

On Tue, Jan 28, 2020 at 2:04 AM Vieri wrote: > Hi, > > Using GIT version. > > I see segmentation faults when closing a connection. It does not affect > user experience. > > Jan 27 15:22:50 guacd[15911]: Connection > "$f7c7eff3-e1b9-4431-a13a-059bd9fd3d04" removed. > Jan 27 15:22:50 kernel:

guacd segmentation fault

Hi, Using GIT version. I see segmentation faults when closing a connection. It does not affect user experience. Jan 27 15:22:50 guacd[15911]: Connection "$f7c7eff3-e1b9-4431-a13a-059bd9fd3d04" removed. Jan 27 15:22:50 kernel: guacd[27423]: segfault at 7efe54a6a008 ip 7efe58adcbd0 sp