bugGNU Octave - Bugs: bug #51212, Unable to open Octave GUI at all

 
 

bug #51212: Unable to open Octave GUI at all

Submitter:  None
Submitted:  Fri 09 Jun 2017 03:19:24 PM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Installation Failure
Status:  Works For Me Assigned to:  None
Originator Name:  Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 4.2.1
Operating System:  * Microsoft Windows Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 05 Sep 2017 04:40:12 AM UTC, comment #14: 

I don't know what the exact problem is, but it is likely related to the original reporters specific hardware and software setup.  Lots of people are successfully running Octave on Windows without having these delays.  Marking this as "Works for Me".

Rik <rik5>
Group administrator
Mon 12 Jun 2017 09:03:18 PM UTC, comment #13: 

Hi Dmitri,

Below are the times it took to execute the tasks after disconnecting from all network drives:

Start GUI - 13 minutes
Create new .m file - 5 minutes
Make a plot - seconds (standard length of time)
Save plot - 2 minutes

By the way, thanks for all your help!

Anonymous
Mon 12 Jun 2017 08:36:34 PM UTC, comment #12: 

Could you un-mount those drives (temporary) and repeat your
tests (start guy, create new .m file, make a plot, save/print
a plot to pdf file). It looks to me that Qt is missing something
(probably fonts) and goes looking for it wherever it can.

Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Mon 12 Jun 2017 08:26:14 PM UTC, comment #11: 

Yes, but Octave is installed locally and my current directory is also local.

I haven't tried pulling programs and files from the network drives yet.

Anonymous
Mon 12 Jun 2017 08:21:29 PM UTC, comment #10: 

Do you have any network mounted drives?

Dmitri.

Dmitri A. Sergatskov <dasergatskov>
Mon 12 Jun 2017 08:16:34 PM UTC, comment #9: 

OP here.

GUI finally loaded after 1-1.5 hours (I let it run through lunch). However, it's VERY slow. Creating a new .m file takes 5-10 minutes. Saving a .fig takes just as long. The actual command window seems to be OK and once the .m file is created, run time seems to be similar to MATLAB (though I haven't tried a really long program yet).

Re-opening the GUI still takes 10-15 minutes unfortunately.

Anonymous
Mon 12 Jun 2017 06:02:52 PM UTC, comment #8: 

Please take note that this bug report is about starting the Octave GUI on Windows 7. Anonymous comment #5, what you are seeing on Fedora with KDE is probably a completely separate issue and should be a new bug report if you want to help debug it. Posting here is distracting from the original issue.

Mike Miller <mtmiller>
Group Member
Mon 12 Jun 2017 03:56:34 PM UTC, comment #7: 

Fedora 25 comes with octave 4.0.3.
Did you compile your own 4.2.1?

Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Mon 12 Jun 2017 03:53:15 PM UTC, comment #6: 

Very weird.  I'm not sure how to debug it or fix this.

Rik <rik5>
Group administrator
Mon 12 Jun 2017 03:02:27 PM UTC, comment #5: 

This exact bug seems to happen on KDE spin of Fedora 25. Clean install on both real hardware and inside of a virtual machine (KVM) behave the same - start octave and it shows up as a blank screen.

If one runs octave from command line using gdb, then it works fine:
$ gdb octave
(gdb) run

Also, if the original (non working) instance is killed using 'xkill' (or it times out), then subsequent instances of octave seem to work fine.

Note that octave works in the default Fedora 25 desktop (i.e. Workstation Gnome spin).

Anonymous
Fri 09 Jun 2017 08:29:18 PM UTC, comment #4: 

It's possible.  I think I've seen chatter on some of the mailing lists about the first execution taking as long as 24 hours.

Rik <rik5>
Group administrator
Fri 09 Jun 2017 03:46:56 PM UTC, comment #3: 

I'll let it sit in the background for the rest of the day. It might just need extra time?

Anonymous
Fri 09 Jun 2017 03:45:40 PM UTC, comment #2: 

No, Windows 7 64-bit.

Anonymous
Fri 09 Jun 2017 03:36:24 PM UTC, comment #1: 

Are you running Windows 10?

Rik <rik5>
Group administrator
Fri 09 Jun 2017 03:19:24 PM UTC, original submission:  

Clean install, have never been able to open Octave GUI at all. CLI appears to be OK.


Anonymous

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #40893:  screenshot1.PNG added by None (106KiB - image/png)
file #40894:  screenshot2.PNG added by None (97KiB - image/png)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by dasergatskov (Posted a comment)
  • -email is unavailable- added by rik5 (Posted a comment)
  •  

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

    Date Changed by Updated Field Previous Value => Replaced by
    2017-09-05 rik5 StatusNone Works For Me
        Open/ClosedOpen Closed
    2017-06-09 None Attached File- Added screenshot1.PNG, #40893
        Attached File- Added screenshot2.PNG, #40894

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code