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".
|
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!
|
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.
--
|
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.
|
Mon 12 Jun 2017 08:21:29 PM UTC, comment #10:
Do you have any network mounted drives?
Dmitri.
|
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.
|
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.
|
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.
--
|
Mon 12 Jun 2017 03:53:15 PM UTC, comment #6:
Very weird. I'm not sure how to debug it or fix this.
|
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).
|
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.
|
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?
|
Fri 09 Jun 2017 03:45:40 PM UTC, comment #2:
No, Windows 7 64-bit.
|
Fri 09 Jun 2017 03:36:24 PM UTC, comment #1:
Are you running Windows 10?
|
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.
|