bugGNU Octave - Bugs: bug #37161, "Welcome to Octave"...


bug #37161: "Welcome to Octave" window in infinite loop

Submitted by:  Edward Meyer <eem2314>
Submitted on:  Tue 21 Aug 2012 06:59:00 PM UTC  
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Installation Failure
Status:  Fixed Assigned to:  None
Originator Name:  Ed Meyer Open/Closed:  Closed
Release:  dev Operating System:  GNU/Linux

Add a New Comment (Rich Markup)

You are not logged in

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


Fri 31 Aug 2012 01:53:40 AM UTC, comment #5: 

Yes, thanks, working for me with that change.

I'll take a look at how the settings are used, I think we can have it continue on and behave reasonably even if it fails to copy the default settings file, if the user's home directory is not writable, quota full, whatever.

Mike Miller <mtmiller>
Project Administrator
Thu 30 Aug 2012 04:06:57 PM UTC, comment #4: 

I checked in the following change.  Does it fix the problem for you?


John W. Eaton <jwe>
Project Administrator
Thu 30 Aug 2012 03:59:18 AM UTC, comment #3: 

Mike, thanks for diagnosing the problem.  I'll take a look at fixing the order of initialization.

John W. Eaton <jwe>
Project Administrator
Thu 30 Aug 2012 02:31:05 AM UTC, comment #2: 

There's still a problem when running the first time after a make install. The default_qt_settings_file function needs Voct_etc_dir, but octave_initialize_interpreter isn't called until after the GUI is up (octave_main_thread::run). I tried to fix this by simply moving octave_initialize_interpreter to octave_start_gui, but that causes other problems (e.g. no readline).

So parts of octave_initialize_interpreter need to run after the GUI, and specifically QTerminal, is ready, but the GUI setup needs some of the global values initialized by this function. Maybe split octave_initialize_interpreter into octave_initialize_interpreter_settings and octave_initialize_interpreter_terminal?

Mike Miller <mtmiller>
Project Administrator
Tue 21 Aug 2012 09:49:58 PM UTC, comment #1: 

I checked in the following change for the installation issue:


Perhaps someone else can fix the copy file issue.  I'm not sure what is the proper thing to do when errors like that are encountered in the gui.

John W. Eaton <jwe>
Project Administrator
Tue 21 Aug 2012 06:59:00 PM UTC, original submission:  

after building and installing (as root) the opening gui window is in an infinite loop: when the "finish" button is pressed a duplicate window replaces it.
This is because in resource-manager.cc:114 the Qfile::copy fails because the file default-qt-settings was installed like so:

 /usr/bin/install -c -m 644 ../../libgui/default-qt-settings '/usr/local/share/octave//etc'

note the double slash where $(version) goes but apparently was not set.  The code looks for default-qt-settings in

It also seems like the Qfile::copy failure should have been caught

Edward Meyer <eem2314>


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

Attach Files:

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 (Updated the item)
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by eem2314 (Submitted the item)
  • -email is unavailable- added by eem2314

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

    Date Changed by Updated Field Previous Value => Replaced by
    2012-09-05 rik5 StatusReady For Test => Fixed
        Open/ClosedOpen => Closed
    2012-08-30 jwe StatusNone => Ready For Test
    2012-08-21 eem2314 Carbon-Copy- => Added eem2314@gmail.com

    Back to the top

    Powered by Savane 3.5