bugGNU Octave - Bugs: bug #58532, Octave 5.2 crash on RDP session

 
 

bug #58532: Octave 5.2 crash on RDP session

Submitter:  Miguel <geoelo>
Submitted:  Tue 09 Jun 2020 11:34:16 AM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  Need Info Assigned to:  None
Originator Name:  geoelo Open/Closed:  * Closed
Release:  * 5.2.0 Operating System:  * Microsoft Windows
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 10 Mar 2021 09:43:27 PM UTC, comment #4: 

Version 6.2 has partially solved the issue. Octave will not crash, but the terminal will turn into a bunch of colours and Chinese symbols, making it unusable. The rest seems to be working fine.

Miguel <geoelo>
Tue 09 Mar 2021 11:23:21 PM UTC, comment #3: 

Try the newest stable version of Octave (6.2) and see if the problem is still there.  If so, can re-open this report.  For now, however, it is old and I'm going to close it.

Rik <rik5>
Group administrator
Sun 13 Sep 2020 06:45:23 PM UTC, comment #2: 

The Octave Maintainers are getting ready to release version 6.1 of Octave.  It is possible, maybe even likely, that this bug has been fixed.  Could you try the release candidate 6.0.90a at alpha.gnu.org/pub/octave?

Rik <rik5>
Group administrator
Thu 23 Jul 2020 07:46:31 PM UTC, comment #1: 

My opinion is that octave ha a problem with the dpi settings.
See in bug https://savannah.gnu.org/bugs/?58704 the file MyPlot_BugReport_ScreenShot.png.
It is done on a 4K monitor with 150 dpi on Windows 10. The font is too small for the size.

If you describe that the monitor size changes because of RDP it could be that the event for changing screen resolution is not handeled correctly.

Ich selber <octavian>
Tue 09 Jun 2020 11:34:16 AM UTC, original submission:  

Crash occurred after the following working steps:
1. Remotely connect from W10x64Pro (laptop single screen) to W10x64Pro (dual monitor) using buit-in RDP over a VPN.
2. Open octave, launch a script at the remote machine.
3. Disconnect RDP session. Take a coffee.
4. Reconnect.
---> oops, Octave is no longer running. Script was supposed to take like 50 min to complete.

Testing the crash:
---> the exact same script and data competed a run without a crash in a different machine using only a local session (no RDP).
---> the exact same script and data competed a run without a crash at the host machine using chrome remote desktop.

Personal note:
A screen resolution change is involved when using W10RDP built-in client (host has two screens, laptop has only one), whereas no src is involved using third party remote desktop apps. Hence I think the screen resolution change may be the one to blame for the crash.

Miguel <geoelo>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by octavian (Posted a comment)
  • -email is unavailable- added by geoelo (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-03-09 rik5 Open/ClosedOpen Closed
    2020-09-13 rik5 StatusNone Need Info

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code