[jira] [Commented] (GUACAMOLE-950) segfault in guacd

2020-02-07 Thread Nick Couchman (Jira)


[ 
https://issues.apache.org/jira/browse/GUACAMOLE-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17032781#comment-17032781
 ] 

Nick Couchman commented on GUACAMOLE-950:
-

Yeah, we'll definitely want to see the stack trace.  Basically you either need 
to start gdb, first, and then run guacd from there, or attach to an existing 
guacd process.  You'll also want to "set follow-fork-mode child" so that gdb 
debugs the child guacd process and not the parent guacd process.  After it 
crashes run "bt" to get the back trace, and send that output.

> segfault in guacd 
> --
>
> Key: GUACAMOLE-950
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-950
> Project: Guacamole
>  Issue Type: Bug
>  Components: guacamole-server
>Affects Versions: 1.1.0
> Environment: Guacamole 1.1.0 under Tomcat8 on Ubuntu 18.04, running 
> as virtual machine
>Reporter: Toby
>Priority: Minor
> Attachments: trace_connected.txt, trace_segfault.txt
>
>
> Upgraded from 1.0.0 on Ubuntu 16.04 to 1.1.0 on Ubuntu 18.04.  Moved from 
> Tomcat7 to Tomcat8.  Config is largely unchanged.
> Two Windows 10 Enterprise destinations and a third is 2012R2.  One of the two 
> Windows 10 will cause guacd to segfault on connection.  2012R2 works fine.  I 
> see a mouse pointer in the upper left very briefly and then I get 
> home/reconnect/logout.  I have pared the config down to just domain, 
> username, password, NLA security, ignore-cert directives for all three 
> destinations. 
> Uploaded syslog traces, one of a normal connect to the other windows 10 
> device, one as the segmentation fault I get when connecting to the other.
> Have also tried rebuilding without webp and websockets to no effect.
> I'm happy to build one for gdb and get a core, but I'll need a little help 
> doing that.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (GUACAMOLE-950) segfault in guacd

2020-02-07 Thread Toby (Jira)
Toby created GUACAMOLE-950:
--

 Summary: segfault in guacd 
 Key: GUACAMOLE-950
 URL: https://issues.apache.org/jira/browse/GUACAMOLE-950
 Project: Guacamole
  Issue Type: Bug
  Components: guacamole-server
Affects Versions: 1.1.0
 Environment: Guacamole 1.1.0 under Tomcat8 on Ubuntu 18.04, running as 
virtual machine
Reporter: Toby
 Attachments: trace_connected.txt, trace_segfault.txt

Upgraded from 1.0.0 on Ubuntu 16.04 to 1.1.0 on Ubuntu 18.04.  Moved from 
Tomcat7 to Tomcat8.  Config is largely unchanged.

Two Windows 10 Enterprise destinations and a third is 2012R2.  One of the two 
Windows 10 will cause guacd to segfault on connection.  2012R2 works fine.  I 
see a mouse pointer in the upper left very briefly and then I get 
home/reconnect/logout.  I have pared the config down to just domain, username, 
password, NLA security, ignore-cert directives for all three destinations. 

Uploaded syslog traces, one of a normal connect to the other windows 10 device, 
one as the segmentation fault I get when connecting to the other.

Have also tried rebuilding without webp and websockets to no effect.

I'm happy to build one for gdb and get a core, but I'll need a little help 
doing that.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GUACAMOLE-883) Touch mouse emulation no longer works as of iOS 13

2020-02-07 Thread Mario Wagner (Jira)


[ 
https://issues.apache.org/jira/browse/GUACAMOLE-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17032490#comment-17032490
 ] 

Mario Wagner commented on GUACAMOLE-883:


did you clear your browser cache?

use eg chrome debugger to check if changes are applied

> Touch mouse emulation no longer works as of iOS 13
> --
>
> Key: GUACAMOLE-883
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-883
> Project: Guacamole
>  Issue Type: Bug
>  Components: guacamole-client
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Thomas
>Assignee: Mike Jumper
>Priority: Minor
>
> With devices running iOS 13, it is no longer possible to interact with remote 
> desktops using touch-driven mouse emulation. The specific reason for this is 
> not yet known. Older releases of iOS work correctly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GUACAMOLE-883) Touch mouse emulation no longer works as of iOS 13

2020-02-07 Thread Thomas (Jira)


[ 
https://issues.apache.org/jira/browse/GUACAMOLE-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17032209#comment-17032209
 ] 

Thomas commented on GUACAMOLE-883:
--

Hi Nick and Mario, i have tried to edit the file in line 95 and redeployed the 
.war file . It si not working for me or maybe i do something wrong.

> Touch mouse emulation no longer works as of iOS 13
> --
>
> Key: GUACAMOLE-883
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-883
> Project: Guacamole
>  Issue Type: Bug
>  Components: guacamole-client
>Affects Versions: 1.0.0, 1.1.0
>Reporter: Thomas
>Assignee: Mike Jumper
>Priority: Minor
>
> With devices running iOS 13, it is no longer possible to interact with remote 
> desktops using touch-driven mouse emulation. The specific reason for this is 
> not yet known. Older releases of iOS work correctly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)