bugGNU Octave - Bugs: bug #53207, crash when Octave starts on...

 
 

bug #53207: crash when Octave starts on Windows after removing external 4K display

Submitted by:  Kip <kobenauf>
Submitted on:  Thu 22 Feb 2018 06:55:33 PM UTC  
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  Closed
Release:  5.0.1 Operating System:  Microsoft Windows

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

( Jump to the original submission)

Thu 10 Jan 2019 07:27:29 PM UTC, comment #12: 

@Philip: Thanks for testing.

A positive feedback from the OP would be nice (Kip, are you still following?) since his problem is slightly different to yours and produced a crash. However, if there is no response until the release we should probably close the report.

Torsten Lilge <ttl>
Project Member
Wed 09 Jan 2019 07:59:00 PM UTC, comment #11: 

The fix from comment #5works AFAICS. Wonderful!

Do we need to wait for the OP to check again before closing this report?

Philip Nienhuis <philipnienhuis>
Project Member
Sat 05 Jan 2019 10:53:10 PM UTC, comment #10: 

OK Torsten, the issues in comments #7 and #9 works fine now. A reset editor pane's title bar is also within reach now.
Thanks!

Next week at work I'll try the semi-original issue, i.e., what happens when I had the main GUI window on the left monitor and the editor on the right, ad after logging out next log in remotely with just one screen.

Philip Nienhuis <philipnienhuis>
Project Member
Fri 04 Jan 2019 09:59:42 PM UTC, comment #9: 

Thanks Torsten, I'll try tonight or this coming (but busy) weekend.

BTW the editor pane was positioned such (on Windows 7) that the title bar was outside the screen upper limit so that I couldn't even grab it and move the pane. What worked was extending the lower  pane border to the screen bottom, when releasing the mouse button a tiny stripe of the title bar got exposed, enough to grab it.

Philip Nienhuis <philipnienhuis>
Project Member
Fri 04 Jan 2019 09:10:25 PM UTC, comment #8: 

@Philip: I hope cset http://hg.savannah.gnu.org/hgweb/octave/rev/93c4fabb2ead restores the former functionality in your setup.

Torsten Lilge <ttl>
Project Member
Fri 04 Jan 2019 05:35:41 PM UTC, comment #7: 

What I now find is this:

At home I usually have the Octave main GUI window on a 1920x1200 monitor on the left and the editor pane on a 1024x1280 monitor (i.e., rotated 90 degrees) to the right of it.
Until (II suppose) this fix Octave would always remember that editor pane position. But now, even if the editor pane has just a few pixel columns on the smaller right monitor, Octave resets the editor pane position to the upper left corner of the larger 1920x1200 monitor. This behavior is very annoying.

(I first -mistakenly?- thought this was related to bug #55286)

Release => 5.0.1

Philip Nienhuis <philipnienhuis>
Project Member
Mon 24 Dec 2018 11:56:10 AM UTC, comment #6: 

Thanks Torsten.
I'll try asap, but I'm afraid for me that's only after Jan 7th as that's my first work day after the Xmas holidays.

Philip Nienhuis <philipnienhuis>
Project Member
Mon 24 Dec 2018 11:17:06 AM UTC, comment #5: 

Changeset http://hg.savannah.gnu.org/hgweb/octave/rev/c95884eed1cf makes restoring the gui's geometry more robust. Maybe some of the issues reported here are fixed by these changes.

Torsten Lilge <ttl>
Project Member
Sat 22 Dec 2018 11:35:12 PM UTC, comment #4: 

This simply sounds related to stored qt-settings that assume upon the next start of octave screen dimensions that are no more valid.

@OP: Octave saves all its GUI settings, incl. window positions, into the file %USERPROFILE%\.config\octave\qt-settngs
If you remove that file Octave should start w/o problems but with default layout.

I have a somewhat related issue: my work PC has a two-monitor setup where I have the undocked GUI editor on the right monitor, But often I log in remotely to that PC from a single-screen PC and then I can't access the editor anymore. My workarounds are:
- keeping a tiny strip of the editorÅ› pane's left border on the left monitor so that I can always grab at least part of the editor pane so I can resize it and then drag it on the left monitor;
- have two separate qt-settings files, one for double-and one for single monitors, that I copy into place when needed.

Perhaps Octave needs to check saved window positions with current screen limits and adapt the former if the new screen is much smaller than the previous one.
Or Octave might have a start-up option (command line option) to select a specific qt-settings file. On Windows systems that could be organized using separate .bat or .vbs files for each HW setup.

Philip Nienhuis <philipnienhuis>
Project Member
Tue 06 Mar 2018 05:59:06 AM UTC, comment #3: 

I mean the subwindows of the GUI like editor, file browser etc.

Torsten Lilge <ttl>
Project Member
Mon 05 Mar 2018 08:54:43 PM UTC, comment #2: 

By floating widgets, do you mean toolbars inside Octave IDE?  I haven't moved any of those to float, if that's what you mean.

Kip <kobenauf>
Mon 05 Mar 2018 06:15:27 PM UTC, comment #1: 

Does this always happen or only when you have floating widgets. Could you please test if you get a crash when all widgets were docked on the 4K Screen?

Torsten Lilge <ttl>
Project Member
Thu 22 Feb 2018 06:55:33 PM UTC, original submission:  

I dock my Windows 10 latptop to a 4K monitor.  Octave runs fine.  When I undock, Octave sometimes gets in a state where octave-gui.exe crashes every time on startup.  I noticed the window opens briefly before it starts, where half the window is off the screen.  If I dock again I can re-open it successfully. 

In the distant past I used to commonly see problems with Windows programs that opened partially or entirely off screen.  I wonder if that is part of the issue here. My laptop has much lower resolution and screen space than my external monitor, and if my Octave window was over to the side or down too far, or too large, it might be launching on the smaller screen size is causing a problem.

Kip <kobenauf>

 

(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 ttl (Posted a comment)
  • -email is unavailable- added by kobenauf (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

     

     

    Follow 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-02-01 mtmiller StatusReady For Test => Fixed
        Open/ClosedOpen => Closed
    2019-01-04 mtmiller Carbon-CopyRemoved 80942 => -
    2019-01-04 philipnienhuis Release4.2.1 => 5.0.1
    2018-12-24 ttl StatusNeed Info => Ready For Test
    2018-03-26 mtmiller StatusNone => Need Info
        SummaryCrash on startup => crash when Octave starts on Windows after removing external 4K display

    Back to the top


    Powered by Savane 3.5