we're providing this as an alternative is
with the issue with _aligned_recalloc(), and it isn't just rebuilding
the library, it's building a newer version that does not contain the
bug that causes the segfault.
-Nick
-
To unsubscribe, e-mai
5 guacd[156163]: Internal RDP client disconnected
Jun 7 11:14:50 tmxqrocnsG5 guacd[156163]: guacd[156163]:INFO:#011Internal RDP
client disconnected
Jun 7 11:14:50 tmxqrocnsG5 kernel: [205223.091624] guacd[156169]: segfault at
10 ip 7fa1fc3e3622 sp 7f9f92573c80 error 4 in
libguac-clien
>> I'll get an RC going today.
>> For any users encountering this while looking to upgrade, interim solutions
>> would include any of the following:
>> * Build and install guacamole-server from the "staging/1.5.3" branch on git.
>> * Leverage the "guacamole/guacd" Docker image for guacd.
>> *
, as follows: gdb --args /path/to/guacd -L debug -f
>> * You'll get a gdb> prompt, and you can type "run"
>> * Attempt the connection, reproducing the segmentation fault.
>> * Once the segfault occurs, gdb will drop to the gdb> prompt, again, and you
>> can then
On 6/9/23 07:00, Nick Couchman wrote:
I upgraded to 1.5.2 this morning, and had the same problem with
disconnection from all hosts. Base OS is Rocky Enterprise Linux 8.7. I
had to revert back to the previous Guac version. This is serious enough
that a 1.5.3 will likely need to be released
>
> I upgraded to 1.5.2 this morning, and had the same problem with
> disconnection from all hosts. Base OS is Rocky Enterprise Linux 8.7. I
> had to revert back to the previous Guac version. This is serious enough
> that a 1.5.3 will likely need to be released when this is fixed.
>
Yes, a fix
Gabriel was seeing, as
the 1.5.2 segfault was definitely introduced by a change in 1.5.2, and
Gabriel mentioned running version 1.4.0.
-Nick
-
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
For additional commands
, as follows: gdb --args /path/to/guacd -L debug -f
>> * You'll get a gdb> prompt, and you can type "run"
>> * Attempt the connection, reproducing the segmentation fault.
>> * Once the segfault occurs, gdb will drop to the gdb> prompt, again, and you
>> can then
nection, reproducing the segmentation fault.
* Once the segfault occurs, gdb will drop to the gdb> prompt, again,
and you can then type "bt full" to get the full backtrace.
* Make sure to remove any sensitive data - for example, when I was
debugging a segfault with 1.5.2, it would print out my con
> Usually they're "core.", so you may want to search for "-name core.\*".
I did not find anything:
# for i in `find / -name "core.*" -print 2>/dev/null`
do
file $i | grep "core file" >/dev/null
if [ $? -eq 0 ]; then
file $i
fi
done
#
-Gabriel
guacd[156163]: Internal RDP client disconnected
Jun 7 11:14:50 tmxqrocnsG5 guacd[156163]: guacd[156163]: INFO:#011Internal RDP
client disconnected
Jun 7 11:14:50 tmxqrocnsG5 kernel: [205223.091624] guacd[156169]: segfault at
10 ip 7fa1fc3e3622 sp 7f9f92573c80 error 4 in
libguac-client
On Wed, Jun 7, 2023 at 12:51 PM Gabriel Huerta Araujo
wrote:
>
> > If you can find the coredump file and do the backtrace on that file, that
> > would be helpful, so we can see where the segfault is actually happening.
>
> > These files which are their file extensión?
&
> If you can find the coredump file and do the backtrace on that file, that
> would be helpful, so we can see where the segfault is actually happening.
> These files which are their file extensión?
I tried to identify segfault (core files) and I did not find them
for i in `find / -
s the same issue as Gabriel was seeing, as
the 1.5.2 segfault was definitely introduced by a change in 1.5.2, and
Gabriel mentioned running version 1.4.0.
-Nick
-
To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org
F
40 20 <48> 8b 78 10 e8 25 e9 fe ff 8b 43 18 85
>> c0 74 0e 31 c0 5b c3 66 2e
>> Jun 4 02:00:17 tmxqrocnsG5 kernel: [10453755.209724] guacd[3337136]:
>> segfault at 10 ip 7f79a06a7622 sp 7f77f5ef2c80 error 4 in
>> libguac-client-rdp.so.0.0.0[7f79a0695000+1a000]
Thanks a lot Nick for your soon answer.
> If you can find the coredump file and do the backtrace on that file, that
> would be helpful, so we can see where the segfault is actually happening.
These files which are their file extensión?
> Those libraries are used by all recent
ff 53 48 8b 07 48 89 fb 48
> 89 de 48 8b 40 10 48 8b 40 20 <48> 8b 78 10 e8 25 e9 fe ff 8b 43 18 85 c0 74
> 0e 31 c0 5b c3 66 2e
> Jun 4 02:00:17 tmxqrocnsG5 kernel: [10453755.209724] guacd[3337136]:
> segfault at 10 ip 7f79a06a7622 sp 7f77f5ef2c80 error 4 in
> libg
43 18 85 c0 74 0e
31 c0 5b c3 66 2e
Jun 4 02:00:17 tmxqrocnsG5 kernel: [10453755.209724] guacd[3337136]: segfault
at 10 ip 7f79a06a7622 sp 7f77f5ef2c80 error 4 in
libguac-client-rdp.so.0.0.0[7f79a0695000+1a000]
Is this solve with this recommendation?
Install these libraries:
freerd
fferent version of the libvnc
dependency with an incompatible ABI, that could definitely cause a
segfault. The memory offsets, sizes, etc. of VNC-related structures
provided by libvnc might not match.
Similarly, if an incompatible ABI change was made to libvnc, but
guacamole-server was not r
: Wednesday, August 19, 2020 3:17 PM
To: user@guacamole.apache.org
Subject: Re: Segfault with VNC on 1.2.0
On Wed, Aug 19, 2020 at 8:21 AM Devine, Harry (FAA)
mailto:harry.dev...@faa.gov.invalid>> wrote:
Our users are reporting segmentation faults since we upgraded to 1.2.0
yesterday in regards
; Aug 18 14:20:33 access systemd: Starting Hostname Service...
>
> Aug 18 14:20:33 access dbus[1231]: [system] Successfully activated service
> 'org.freedesktop.hostname1'
>
> Aug 18 14:20:33 access systemd: Started Hostname Service.
>
> Aug 18 14:20:50 access kernel: guacd[15400]:
uacd[15400]: segfault at 1 ip 7ff42a0f0faf
sp 7ff425605c18 error 4 in libc-2.17.so[7ff42a056000+1c3000]
Aug 18 14:20:50 access abrt-hook-ccpp: Process 15386 (guacd) of user 0 killed
by SIGSEGV - dumping core
Aug 18 14:20:51 access guacd[31477]: Connection
"$d368bfac-36a2-421d-91f1-9c640d
If you look at the uptime stamps on
the log messages, you'll see that the NIC comes up 20 seconds after the kernel
boots, which is about right (maybe a little slow...probably depends on the disk
backing it). The first segfault doesn't happen until 447 seconds into the
system uptime, almost 8 m
that the NIC comes up 20 seconds
after the kernel boots, which is about right (maybe a little
slow...probably depends on the disk backing it). The first segfault
doesn't happen until 447 seconds into the system uptime, almost 8 minutes
after boot time.
-Nick
i saw that, I also found it strange, it´s a VmWare Server, like as mine and
i don´t receive this messages.
Em qua., 17 de jun. de 2020 às 14:54, Charaoui, Jérôme <
jchara...@cmaisonneuve.qc.ca> escreveu:
> Hi,
>
> Le 20-06-17 à 13 h 46, Guilherme Carvalho a écrit :
> > NIC Link is Up 1 Mbps
new mount options
>> do not match the existing superblock, will be ignored
>> Jun 17 11:40:38 srv-ckg-app-16 kernel: [ 447.312963] show_signal_msg: 10
>> callbacks suppressed
>> Jun 17 11:40:38 srv-ckg-app-16 kernel: [ 447.312968] guacd[2835]:
>> segfault at 0 ip
Hi,
Le 20-06-17 à 13 h 46, Guilherme Carvalho a écrit :
> NIC Link is Up 1 Mbps
To me that looks like the server is losing network connectivity right
before guacd crashes.
-- Jerome
-
To unsubscribe, e-mail:
: 10
> callbacks suppressed
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [ 447.312968] guacd[2835]:
> segfault at 0 ip sp 7fe622ffcb18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [ 447.312963] show_signal_msg: 10
>
0
> callbacks suppressed
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [ 447.312968] guacd[2835]:
> segfault at 0 ip sp 7fe622ffcb18 error 14 in
> guacd[55eda1436000+7000]
> Jun 17 11:40:38 srv-ckg-app-16 kernel: [ 447.312963] show_signal_msg: 10
> callbacks suppr
-16 kernel: [ 24.337831] new mount options do
not match the existing superblock, will be ignored
Jun 17 11:40:38 srv-ckg-app-16 kernel: [ 447.312963] show_signal_msg: 10
callbacks suppressed
Jun 17 11:40:38 srv-ckg-app-16 kernel: [ 447.312968] guacd[2835]: segfault
at 0 ip sp
; life of me I cant find it.
>
> --
> *From:* Salatiel Filho
> *Sent:* Tuesday, March 17, 2020 1:21:50 PM
> *To:* user@guacamole.apache.org
> *Subject:* guacd segfault connecting to windows 10
>
> Hi, I have an instance of guacamole 1.1.0(compiled from source ) running
> o
it.
From: Salatiel Filho
Sent: Tuesday, March 17, 2020 1:21:50 PM
To: user@guacamole.apache.org
Subject: guacd segfault connecting to windows 10
Hi, I have an instance of guacamole 1.1.0(compiled from source ) running on
Ubuntu 18.04. It works just fine when connecting to Windows 7 RDP, but when I
Hi, I have an instance of guacamole 1.1.0(compiled from source ) running on
Ubuntu 18.04. It works just fine when connecting to Windows 7 RDP, but
when I try to connect to WIndows 10 RDP it fails. Log shows a segfault.
Anyone faced this before ?
Here it is the log for guacd:
Mar 17 17:18:22
uot;$12c5328c-c127-453d-bc9c-f631bf8e90f8" removed.
>> Jun 27 16:10:34 pulsemaster kernel: [717204.421339] guacd[28944]: segfault
>> at 10 ip 7f9ead26c692 sp 7f9eaec7ad10 error 4 in
>> libguac-client-vnc.so.0.0.0[7f9ead264000+13000]
>> ...
>>
>
> This s
aster kernel: [717204.421339] guacd[28944]: segfault at
> 10 ip 7f9ead26c692 sp 7f9eaec7ad10 error 4 in
> libguac-client-vnc.so.0.0.0[7f9ead264000+13000]
> ...
>
This segfault is occurring after the connection has already ended,
while the resources consumed by that connection are
ues with that
version of libvncclient, but I'd expect the segfault message to happen in
libvncclient not the Guacamole library, if that were the case.
> Any special configuration for VNC?
>
> for the client, this is nothing special
>
> Are you trying to use encryption?
>
&
eaders)
> > ii libguac11:amd64 0.9.14-1
> > amd64HTML5 web application for accessing remote
> > desktops (library)
> > ii libguac11-dbgsym:amd64 0.9.14-1
> >
md64HTML5 web application for accessing remote desktops
> (library)
> ii libguac11-dbgsym:amd64 0.9.14-1
> amd64Debug symbols for libguac11
> *
>
>
What version of the libvncserver/libvncclient are you buildin
amd64HTML5 web application for accessing remote desktops
(library)
ii libguac11-dbgsym:amd64 0.9.14-1
amd64Debug symbols for libguac11
Each time i use the vnc plugin i can see a segfault
sometime I get segfault on vnc
> connections. Rdp work fine.
>
> 15 мар. 2018 г. 9:20 ПП пользователь "Mike Jumper" <
> mike.jum...@guac-dev.org> написал:
>
> Are you sure that you've installed libguac-client-vnc and libguac from the
>> same build of
Yep, I installed clean debian server and install guacamole 0.9.14 and
migrate mysql db from 0.9.12. If I use old 0.9.12 machine no problem, If I
try to use the same connections with 0.9.14 sometime I get segfault on vnc
connections. Rdp work fine.
15 мар. 2018 г. 9:20 ПП пользователь "
; 15 мар. 2018 г. 8:18 ПП пользователь "Mike Jumper" <
> mike.jum...@guac-dev.org> написал:
>
>> On Mar 15, 2018 10:09, "Евгений Н. Жуков" <eugene.zhu...@gmail.com>
>> wrote:
>>
>> Hi! I've updated to 0.9.14 and now guacd often crashed with a
rashed with an error
>
> Mar 14 14:08:53 CloudProxy kernel: [403126.766972] guacd[29877]: segfault
> at 10 ip 7f1e0d98ee42 sp 7f1e067fbd10 error 4 in
> libguac-client-vnc.so.0.0.0[7f1e0d986000+14000]
> Mar 14 14:13:22 CloudProxy kernel: [403396.543124] guacd[29931]: segfault
43 matches
Mail list logo
