bugGNU Octave - Bugs: bug #45459, GUI will not open

 
 

bug #45459: GUI will not open

Submitted by:  None
Submitted on:  Wed 01 Jul 2015 10:20:12 PM UTC  
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Segfault, Bus Error, etc.
Status:  Invalid Assigned to:  None
Originator Name:  Adam Originator Email:  -email is unavailable-
Open/Closed:  Closed Release:  4.0.0
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)

Mon 20 Jan 2020 07:32:17 AM UTC, comment #18: 

comment #17:

> Marcel,  do you use the same settings file in your office and at home?


YES

Marcel Rüegg <maruee>
Fri 17 Jan 2020 04:13:09 PM UTC, comment #17: 

Marcel,  do you use the same settings file in your office and at home?

Torsten Lilge <ttl>
Project Member
Fri 17 Jan 2020 06:59:00 AM UTC, comment #16: 

I run Octave 5.1.0(GUI) on Windows 10 and I'm suffering the same problem:
- Octave is crashing when transporting my labtop from one room to another
- otherwise, Octave is running OK at my workplace, but not during home office

Some more inputs to it: When running it at work, we have network drives (e.g. M:/ ...), when running Octave at home I have the folders available with synchronisation only. I see that in the qt-settings-file lots of those paths are saved. So I guess there might be a connection.

Marcel Rüegg <maruee>
Fri 26 Jan 2018 10:36:14 PM UTC, comment #15: 

Okay, so I discovered that it does not crash if I replace the [MainWindow] section of the qt-settings file with the corresponding section from a good qt-settings file.

(I drew inspiration from 41953 and 52839, since Ron's problems happened after changing the window location.)

Any suggestions for further debugging on my end?

Clint <terikin>
Wed 10 Jan 2018 03:23:05 PM UTC, comment #14: 

Okay, so I managed to build an installer for 4.3.0, and it has the same crashing problem on my Win10 machine.  I'll see about modifying sections of the qt-settings file to isolate the problem some time soon.

Clint <terikin>
Mon 08 Jan 2018 07:29:36 PM UTC, comment #13: 

Perhaps by default mxe-octave gets the same version of the code as was used for the official windows installer for 4.2.1?

What does the start message say when you start octave in cli mode (4.2.1 or 4.3.0)? Did you follow the instruction in the section http://wiki.octave.org/Windows_Installer#Creating_Octave_development_versions_for_Windows_with_mxe-octave ?

For approaching the problem's core you might exchange one section  at a time of your settings file with the related section of the default settings file and then we cna have a closer to the section which cases the crash.

Torsten Lilge <ttl>
Project Member
Mon 08 Jan 2018 06:54:30 PM UTC, comment #12: 

Hm.  I'm having the problem on Windows 10.
Is there an installer available somewhere for a newer version than 4.2.1?  I checked https://ftp.gnu.org/gnu/octave/windows/, but those only go to 4.2.1.  I did follow the instructions on this page:  wiki.octave.org/Windows_Installer  to build my own Windows installer from an ubuntu machine, but the GUI still crashes if I try to open it using my bad qt-settings file.  (Perhaps by default mxe-octave gets the same version of the code as was used for the official windows installer for 4.2.1?  I haven't had time to learn exactly what code it automatically downloads and compiles to make the installer package.)

(It isn't a pressing problem for me, as I worked around it by just re-creating the qt-settings file, but I'm happy to help find the source of the bug for the sake of others, if it is indeed still a bug.)

Clint <terikin>
Sun 07 Jan 2018 05:34:05 PM UTC, comment #11: 

With a recent build from the default branch, the GUI is starting on my Windows 7 system.

Torsten Lilge <ttl>
Project Member
Fri 05 Jan 2018 10:42:00 PM UTC, comment #10: 

Although there are some inconsistencies in the settings file (e.g., empty mru-list, but non-empty list of related encodings) i was able to start Octave on Ubuntu with this settings file. I will try this on windows within the next days.

Torsten Lilge <ttl>
Project Member
Fri 05 Jan 2018 07:31:57 PM UTC, comment #9: 

I should add - I'm actually running Octave version 4.2.1, not release 4.0.0 as the bug info currently notes.  (Apologies if I'm not posting all this in the right place.)

Clint <terikin>
Fri 05 Jan 2018 07:25:24 PM UTC, comment #8: 

I see this is an old posting, but I'm getting the exact same behavior as the original poster.  If I delete the qt-settings file, Octave works fine.  I'm attaching my qt-settings file that makes Octave crash upon opening, in the hopes that it helps to identify the problem.

(file #42850)

Clint <terikin>
Sat 12 Sep 2015 07:13:38 PM UTC, comment #7: 

OP has resolved the issue by deleting the qt-settings file. Since there doesn't seem to be anything left here to debug, closing as invalid. This bug may resurface, but we'll need someone willing to help debug what changes to qt-settings cause the crash.

Mike Miller <mtmiller>
Project Administrator
Fri 03 Jul 2015 05:54:38 PM UTC, comment #6: 

I suspect a relation with this bug:
https://savannah.gnu.org/bugs/index.php?45366
...that I hit when helping Dan fix another bug related to forcefully quitting Octave.

Philip Nienhuis <philipnienhuis>
Project Member
Thu 02 Jul 2015 05:45:39 PM UTC, comment #5: 

Have you made a backup from the old qt-settings? I yes you could attach the old which triggers the crash and the new one so we could compare them.

Andreas Weber <andy1978>
Project Member
Thu 02 Jul 2015 05:28:04 PM UTC, comment #4: 

That seems to have resolved the problem. I'm curious to see if I will need to do this regularly or if this will be a one-time fix.

Anonymous
Thu 02 Jul 2015 05:24:13 PM UTC, comment #3: 

Try to delete this file:

C:\Users\<your_login_name_here>\.config\qt-settings

(maybe back it up first)

and start Octave again.

Philip Nienhuis <philipnienhuis>
Project Member
Thu 02 Jul 2015 01:36:07 PM UTC, comment #2: 

Both opening the GUI directly and from the command line give the same result. There is usually no error message. Most times it will begin to open, crash, and close with no message. Occasionally, it will give an error message that says "octave-gui.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." This is less common than the GUI just disappearing.

Anonymous
Thu 02 Jul 2015 01:30:05 PM UTC, comment #1: 

Thanks for your bug report. Are there any error messages or information displayed about why Octave won't start? Is anything displayed if you try to start the GUI from a command line window?

Mike Miller <mtmiller>
Project Administrator
Wed 01 Jul 2015 10:20:12 PM UTC, original submission:  

Running GNU Octave 4.0.0 on Windows and for the first day everything worked fine. The GUI opened and worked just as I hoped it would. However, when I came back the next day, the GUI would crash every time I attempted to open it. The command line still works, but the GUI still crashes, despite attempts to uninstall and reinstall the program.

Anonymous

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #42850:  qt-settings added by terikin (37KiB - application/octet-stream - qt-settings file that leads to a crash on Windows 10)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by maruee (Posted a comment)
  • -email is unavailable- added by ttl (Posted a comment)
  • -email is unavailable- added by terikin (Updated the item)
  • -email is unavailable- added by andy1978 (Posted a comment)
  •  

    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 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-01-25 mtmiller Carbon-CopyRemoved 80942 => -
    2018-01-05 terikin Attached File- => Added qt-settings, #42850
    2015-09-12 mtmiller StatusNeed Info => Invalid
        Open/ClosedOpen => Closed
    2015-07-02 mtmiller StatusNone => Need Info

    Back to the top


    Powered by Savane 3.5