bugGNU Octave - Bugs: bug #61017, GUI doesn't work anymore, even...

 
 

bug #61017: GUI doesn't work anymore, even though CLI works fine

Submitted by:  None
Submitted on:  Fri 06 Aug 2021 04:30:38 PM UTC  
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Other
Status:  Ready For Test Assigned to:  None
Originator Name:  David Originator Email:  -email is unavailable-
Open/Closed:  Open Release:  6.3.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)

Fri 27 Aug 2021 08:37:55 PM UTC, comment #35: 

comentario nº33:

> Friendly reminder: Did you come around to testing whether a newer build from https://buildbot.octave.space/#/download works for you?
> Unfortunately, I can't test myself because I cannot reproduce the error.


I just tried this one, and the GUI works:
octave-2021-08-27-00-43-w64-64.zip

Anonymous
Fri 27 Aug 2021 12:35:01 PM UTC, comment #34: 

comentario nº33:

> Friendly reminder: Did you come around to testing whether a newer build from https://buildbot.octave.space/#/download works for you?
> Unfortunately, I can't test myself because I cannot reproduce the error.


I had some trouble this week. I hope I can test it sometime during this weekend. I won't forget, but thanks for reminding me :-)

Anonymous
Fri 27 Aug 2021 09:20:11 AM UTC, comment #33: 

Friendly reminder: Did you come around to testing whether a newer build from https://buildbot.octave.space/#/download works for you?
Unfortunately, I can't test myself because I cannot reproduce the error.

Markus Mützel <mmuetzel>
Project Member
Sat 21 Aug 2021 02:42:46 PM UTC, comment #32: 

comentario nº31:

> I grafted the changes that update to Qt5.15.2 to the release branch of MXE Octave here:
> https://hg.octave.org/mxe-octave/rev/8cfad4a44884
> https://hg.octave.org/mxe-octave/rev/6821341b80cb
>
> @Anonymous (original reporter): Could you please try with a build from octave.space from tomorrow 2021-Aug-22 or later if the GUI is starting correctly for you. Please test with any of the builds but "default-w64". (We already know that the latter works for you.)


Sure.
I'll try it on Monday and I'll let you know.
Thank you.

Anonymous
Sat 21 Aug 2021 02:06:12 PM UTC, comment #31: 

I grafted the changes that update to Qt5.15.2 to the release branch of MXE Octave here:
https://hg.octave.org/mxe-octave/rev/8cfad4a44884
https://hg.octave.org/mxe-octave/rev/6821341b80cb

@Anonymous (original reporter): Could you please try with a build from octave.space from tomorrow 2021-Aug-22 or later if the GUI is starting correctly for you. Please test with any of the builds but "default-w64". (We already know that the latter works for you.)

Markus Mützel <mmuetzel>
Project Member
Sun 15 Aug 2021 11:11:59 AM UTC, comment #30: 

Thanks for testing.

IIUC, we try to keep the dependencies packaged in Octave for Windows stable between minor releases.
I asked on the discourse forum if it would be ok to make an exception for Qt given your observations:
https://octave.discourse.group/t/update-to-qt5-15-in-mxe-octave-release-branch/1484

Markus Mützel <mmuetzel>
Project Member
Sat 14 Aug 2021 12:33:20 PM UTC, comment #29: 

comentario nº28:

> I'm not sure if this will work. But if you are up to an adventure, you could try to copy all files containing `*qt*` from the `bin` folder and the entire `qt5` folder in the `mingw64` folder of the version that is working for you to the respective folders of the version that is currently not working for you.
> Does that "updated" version start for you?
>


Yes, it does work!
Appart from what you told me to do, I had to copy some more DLLs, shown in the attached image. Then, the official stable octave 6.3  release works fine.

Thank you everyone for your help.
I hope this issue is solved soon, because it probably is happening to other people.


Anonymous
Wed 11 Aug 2021 04:07:15 PM UTC, comment #28: 

The Octave that you install on Windows does not only contain Octave itself but also a lot of dependencies.
The version that contains "default" in its name packages newer versions of those dependencies than the ones that are used in releases.
I guess an issue was fixed in one or some of those dependencies that allows it run for you. It is difficult to say which one it is though.

My best guess would be it is Qt. The release version is packaged with Qt 5.14.2. The "default" version is packaged with Qt 5.15.2.

I'm not sure if this will work. But if you are up to an adventure, you could try to copy all files containing `*qt*` from the `bin` folder and the entire `qt5` folder in the `mingw64` folder of the version that is working for you to the respective folders of the version that is currently not working for you.
Does that "updated" version start for you?

Markus Mützel <mmuetzel>
Project Member
Wed 11 Aug 2021 01:05:14 PM UTC, comment #27: 

comentario nº25:

> It would probably be most interesting to see if the octave-mxe-default-w64 build is working for you (once it has finished compiling).


Some good news.
As suggested by Markus, I just tried "octave-2021-08-11-00-30-default-w64.zip" (under mxe-default) and it works. I just unzipped, ran "post-install.bat" (with admin rights), and then ran octave.vbs. Gui launches successfuly.

Just for if helps to track down the issue, these are the versions I tried:
  6.1 (stable) zip
  6.3 (stable) zip and installer
from https://buildbot.octave.space/#/download:
  octave-2021-08-11-04-58-w64-64.zip
  octave-2021-08-11-00-30-default-w64.zip

Only the last one works.
Isn't it strange?

Does anyone know what could be the cause?

Anonymous
Wed 11 Aug 2021 09:49:49 AM UTC, comment #26: 

comentario nº25:

> Could you check if you see the same error with one of the nightly builds from octave.space? You can download those from here:
> https://buildbot.octave.space/#/download
>
> It would probably be most interesting to see if the octave-mxe-default-w64 build is working for you (once it has finished compiling).


I just tried octave-2021-08-11-00-42-w64.zip.
Exact same behavior.

Yes, looking at the backtrace, AFAICS, the threads are locked, waiting for some event.
The main thread seems to be doing something related to locale.
...
QLocale::QLocale()
...
QLibraryInfo::location
...

But I'm not a Qt expert either.

Anonymous
Wed 11 Aug 2021 08:25:02 AM UTC, comment #25: 

I'm not sure whether I read the backtraces correctly (I only have a very limited understanding of Qt). But it looks like you are experiencing a dead-lock while initializing the QApplication object. Thread 1 (the GUI thread afaict) seems to be waiting for some other thread. But I'm not sure for which thread it is waiting. All other threads seem to be in a waiting state, too.
Maybe some Qt expert can make more out of this.

Maybe this is something that has been fixed in the meantime (although Qt5.15 no longer receives any open updates from upstream unfortunately).
Could you check if you see the same error with one of the nightly builds from octave.space? You can download those from here:
https://buildbot.octave.space/#/download

It would probably be most interesting to see if the octave-mxe-default-w64 build is working for you (once it has finished compiling).

Markus Mützel <mmuetzel>
Project Member
Wed 11 Aug 2021 08:05:46 AM UTC, comment #24: 

comentario nº23:

> another item you could check (although this may be trivial relative to the adb output)
>
> with the process hanging, in Task Manager, under Details, right click and select Analyze Wait Chain.  Does anything appear. 
>
> I would suggest making sure there's only one octave-gui process hanging when you do this, so they don't interfere.


Nothing. "octave-gui.exe is executing normally"


Anonymous
Tue 10 Aug 2021 08:07:18 PM UTC, comment #23: 

another item you could check (although this may be trivial relative to the adb output)

with the process hanging, in Task Manager, under Details, right click and select Analyze Wait Chain.  Does anything appear. 

I would suggest making sure there's only one octave-gui process hanging when you do this, so they don't interfere.

Nicholas Jankowski <nrjank>
Project Member
Tue 10 Aug 2021 07:41:35 PM UTC, comment #22: 

comment #16:

> Ok.
>
> It is strange that you couldn't find any trace of an octave-gui.ini file even after you where using the Octave 5 GUI.
> Could you please cd to `%APPDATA%\octave` (in a CMD shell) and show which files are in that folder (`dir *`)?


Octave 5 stored settings in c:\users\*username*\.config\octave\qt-settings

With Octave 6 we moved that to %AppData%

Torsten Lilge <ttl>
Project Member
Tue 10 Aug 2021 07:26:37 PM UTC, comment #21: 

comentario nº20:

> - At that shell, run `gdb -p PID` where you replace PID with the PID you noted before.
> - At the (gdb) prompt, execute `thread apply all bt`. That might return a longer list of backtraces that you might need to continue by typing `c`.
> - Please, paste that output here.
>


(gdb) thread  apply all bt

Thread 8 (Thread 6348.0x3940):
#0  0x00007ffc583f0911 in ntdll!DbgBreakPoint () from C:\WINDOWS\SYSTEM32\ntdll.dll
#1  0x00007ffc5841ca4e in ntdll!DbgUiRemoteBreakin () from C:\WINDOWS\SYSTEM32\ntdll.dll
#2  0x00007ffc57867034 in KERNEL32!BaseThreadInitThunk () from C:\WINDOWS\System32\kernel32.dll
#3  0x00007ffc583a2651 in ntdll!RtlUserThreadStart () from C:\WINDOWS\SYSTEM32\ntdll.dll
#4  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 7 (Thread 6348.0x30dc):
#0  0x00007ffc583f0874 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\WINDOWS\SYSTEM32\ntdll.dll
#1  0x00007ffc583a2dc7 in ntdll!TpReleaseCleanupGroupMembers () from C:\WINDOWS\SYSTEM32\ntdll.dll
#2  0x00007ffc57867034 in KERNEL32!BaseThreadInitThunk () from C:\WINDOWS\System32\kernel32.dll
#3  0x00007ffc583a2651 in ntdll!RtlUserThreadStart () from C:\WINDOWS\SYSTEM32\ntdll.dll
#4  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 6 (Thread 6348.0x30d8):
#0  0x00007ffc583f0874 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\WINDOWS\SYSTEM32\ntdll.dll
#1  0x00007ffc583a2dc7 in ntdll!TpReleaseCleanupGroupMembers () from C:\WINDOWS\SYSTEM32\ntdll.dll
#2  0x00007ffc57867034 in KERNEL32!BaseThreadInitThunk () from C:\WINDOWS\System32\kernel32.dll
#3  0x00007ffc583a2651 in ntdll!RtlUserThreadStart () from C:\WINDOWS\SYSTEM32\ntdll.dll
#4  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 5 (Thread 6348.0x24f0):
#0  0x00007ffc583f0874 in ntdll!ZwWaitForWorkViaWorkerFactory () from C:\WINDOWS\SYSTEM32\ntdll.dll
#1  0x00007ffc583a2dc7 in ntdll!TpReleaseCleanupGroupMembers () from C:\WINDOWS\SYSTEM32\ntdll.dll
#2  0x00007ffc57867034 in KERNEL32!BaseThreadInitThunk () from C:\WINDOWS\System32\kernel32.dll
--Type <RET> for more, q to quit, c to continue without paging--
#3  0x00007ffc583a2651 in ntdll!RtlUserThreadStart () from C:\WINDOWS\SYSTEM32\ntdll.dll
#4  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 4 (Thread 6348.0x19b0):
#0  0x00007ffc583ed974 in ntdll!ZwWaitForMultipleObjects () from C:\WINDOWS\SYSTEM32\ntdll.dll
#1  0x00007ffc55adcab0 in WaitForMultipleObjectsEx () from C:\WINDOWS\System32\KernelBase.dll
#2  0x00007ffc55adc9ae in WaitForMultipleObjects () from C:\WINDOWS\System32\KernelBase.dll
#3  0x0000000001e2f083 in openblas_get_parallel_ () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\libblas.dll
#4  0x00007ffc57867034 in KERNEL32!BaseThreadInitThunk () from C:\WINDOWS\System32\kernel32.dll
#5  0x00007ffc583a2651 in ntdll!RtlUserThreadStart () from C:\WINDOWS\SYSTEM32\ntdll.dll
#6  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 3 (Thread 6348.0x19bc):
#0  0x00007ffc583ed974 in ntdll!ZwWaitForMultipleObjects () from C:\WINDOWS\SYSTEM32\ntdll.dll
#1  0x00007ffc55adcab0 in WaitForMultipleObjectsEx () from C:\WINDOWS\System32\KernelBase.dll
#2  0x00007ffc55adc9ae in WaitForMultipleObjects () from C:\WINDOWS\System32\KernelBase.dll
#3  0x0000000001e2f083 in openblas_get_parallel_ () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\libblas.dll
#4  0x00007ffc57867034 in KERNEL32!BaseThreadInitThunk () from C:\WINDOWS\System32\kernel32.dll
#5  0x00007ffc583a2651 in ntdll!RtlUserThreadStart () from C:\WINDOWS\SYSTEM32\ntdll.dll
#6  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 2 (Thread 6348.0x1d48):
#0  0x00007ffc583ed974 in ntdll!ZwWaitForMultipleObjects () from C:\WINDOWS\SYSTEM32\ntdll.dll
#1  0x00007ffc55adcab0 in WaitForMultipleObjectsEx () from C:\WINDOWS\System32\KernelBase.dll
#2  0x00007ffc55adc9ae in WaitForMultipleObjects () from C:\WINDOWS\System32\KernelBase.dll
#3  0x0000000001e2f083 in openblas_get_parallel_ () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\libblas.dll
--Type <RET> for more, q to quit, c to continue without paging--
#4  0x00007ffc57867034 in KERNEL32!BaseThreadInitThunk () from C:\WINDOWS\System32\kernel32.dll
#5  0x00007ffc583a2651 in ntdll!RtlUserThreadStart () from C:\WINDOWS\SYSTEM32\ntdll.dll
#6  0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (Thread 6348.0x1980):
#0  0x00007ffc583ed974 in ntdll!ZwWaitForMultipleObjects () from C:\WINDOWS\SYSTEM32\ntdll.dll
#1  0x00007ffc55adcab0 in WaitForMultipleObjectsEx () from C:\WINDOWS\System32\KernelBase.dll
#2  0x00007ffc55adc9ae in WaitForMultipleObjects () from C:\WINDOWS\System32\KernelBase.dll
#3  0x0000000064942eee in libwinpthread-1!_pthread_rel_time_in_ms () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\libwinpthread-1.dll
#4  0x0000000064941f08 in pthread_cond_init () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\libwinpthread-1.dll
#5  0x0000000064942216 in pthread_cond_init () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\libwinpthread-1.dll
#6  0x0000000064942846 in pthread_cond_wait () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\libwinpthread-1.dll
#7  0x000000006fd41c2e in libstdc++-6!.cxa_guard_acquire () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\libstdc++-6.dll
#8  0x0000000066752194 in QLibraryInfo::location(QLibraryInfo::LibraryLocation) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#9  0x000000006689125a in QLoggingCategory::setFilterRules(QString const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#10 0x000000006689244e in QLoggingCategory::setFilterRules(QString const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#11 0x000000006688f1d8 in QLoggingCategory::defaultCategory() () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#12 0x000000006675369f in operator<<(QDebug, QOperatingSystemVersion const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#13 0x000000006675386e in operator<<(QDebug, QOperatingSystemVersion const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#14 0x0000000066a632e9 in QMessageLogger::warning(char const*, ...) const () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw--Type <RET> for more, q to quit, c to continue without paging--
64\bin\Qt5Core.dll
#15 0x00000000667bf8b7 in operator<<(QDebug, QLocale const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#16 0x00000000667bf995 in operator<<(QDebug, QLocale const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#17 0x00000000667c4145 in QLocale::QLocale() () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#18 0x000000006686ea49 in QResource::QResource(QString const&, QLocale const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#19 0x000000006688c620 in QFileSystemEntry::isRootPath(QString const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#20 0x000000006688c7ce in QFileSystemEntry::isRootPath(QString const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#21 0x000000006685d78e in QFileInfo::exists(QString const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#22 0x0000000066751215 in QLibraryInfo::isDebugBuild() () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#23 0x00000000667516e2 in QLibraryInfo::platformPluginArguments(QString const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#24 0x00000000667521b3 in QLibraryInfo::location(QLibraryInfo::LibraryLocation) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#25 0x000000006691b8a2 in QCoreApplication::libraryPathsLocked() () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#26 0x000000006691bbb3 in QCoreApplication::libraryPaths() () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#27 0x0000000066909ffb in QFactoryLoader::update() () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#28 0x000000006690bb16 in QFactoryLoader::QFactoryLoader(char const*, QString const&, Qt::CaseSensitivity) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#29 0x0000000003a014d5 in QPlatformIntegrationFactory::keys(QString const&) () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Gui.dll
#30 0x0000000003a11326 in QGuiApplicationPrivate::createPlatformIntegration() () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\m--Type <RET> for more, q to quit, c to continue without paging--
ingw64\bin\Qt5Gui.dll
#31 0x0000000003a12718 in QGuiApplicationPrivate::createEventDispatcher() () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Gui.dll
#32 0x000000006691d935 in QCoreApplicationPrivate::init() () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Core.dll
#33 0x0000000003a1545c in QGuiApplicationPrivate::init() () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Gui.dll
#34 0x00000000040ddccf in QApplicationPrivate::init() () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\Qt5Widgets.dll
#35 0x000000006c1500e8 in liboctgui-6!_ZN6octave12base_qobjectC2ERNS_14qt_applicationE () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\liboctgui-6.dll
#36 0x000000006c150d40 in liboctgui-6!_ZN6octave11cli_qobjectC2ERNS_14qt_applicationE () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\liboctgui-6.dll
#37 0x000000006c15916d in liboctgui-6!_ZN6octave14qt_application7executeEv () from C:\PROGRA~1\GNUOCT~1\OCTAVE~1.0\mingw64\bin\liboctgui-6.dll
#38 0x0000000000402f47 in octave-gui!main ()
(

Anonymous
Tue 10 Aug 2021 06:08:00 PM UTC, comment #20: 

Hmm...

It might help to inspect the point at which Octave is hanging when the GUI doesn't show for you.
For this, could you please do the following:
- Start Octave with the .bat file like described earlier (`octave.bat --gui`).
- With the black Window hanging around, open the Task Manager and switch to the "Details" tab. Look for `octave-gui.exe` in that list and take note of the corresponding PID.
- Open the folder where Octave is installed. You should find a file called `cmdshell.bat`. Run that script. That should open an MSYS2 bash.
- At that shell, run `gdb -p PID` where you replace PID with the PID you noted before.
- At the (gdb) prompt, execute `thread apply all bt`. That might return a longer list of backtraces that you might need to continue by typing `c`.
- Please, paste that output here.

Markus Mützel <mmuetzel>
Project Member
Tue 10 Aug 2021 03:37:01 PM UTC, comment #19: 

comentario nº18:

> The configuration files are installed automatically in the %APPDATA% folder.
> At a CMD shell, please type the following and paste what you are seeing:

> echo %APPDATA%
> c:
> cd %APPDATA%\octave
> dir *

>
> Where I wrote `c:` above, please use the drive letter the results of the first command starts with.
>


The APPDATA does exist, but not the octave subdirectory. See attachment (the long message, in English, is: «the system cannot find the path»).

Now, I checked the other computer where Octave 6.3 was working perfectly, and the directory does exist, and also octave-gui.ini is there, as expected.

Obviously, I tried manually copying the file to the exact same location on the problematic computer. No change in behavior...


Anonymous
Tue 10 Aug 2021 02:57:23 PM UTC, comment #18: 

The configuration files are installed automatically in the %APPDATA% folder.
At a CMD shell, please type the following and paste what you are seeing:

echo %APPDATA%
c:
cd %APPDATA%\octave
dir *

Where I wrote `c:` above, please use the drive letter the results of the first command starts with.

Markus Mützel <mmuetzel>
Project Member
Tue 10 Aug 2021 12:18:29 PM UTC, comment #17: 

comentario nº16:

> Ok.
>
> It is strange that you couldn't find any trace of an octave-gui.ini file even after you where using the Octave 5 GUI.
> Could you please cd to `%APPDATA%\octave` (in a CMD shell) and show which files are in that folder (`dir *`)?


There's no octave directory inside my user directory, except:
C:\Users\username\.config\octave
Inside there's a single file: qt-settings.

As I installed octave for all users, the installation path in within C:\Program Files, not %APPDATA%.
There're only two ini files inside the installation directory (C:\Program Files\GNU Octave\Octave-6.3.0): proj.ini and mxe-conf.ini.

Anonymous
Tue 10 Aug 2021 10:20:53 AM UTC, comment #16: 

Ok.

It is strange that you couldn't find any trace of an octave-gui.ini file even after you where using the Octave 5 GUI.
Could you please cd to `%APPDATA%\octave` (in a CMD shell) and show which files are in that folder (`dir *`)?

Markus Mützel <mmuetzel>
Project Member
Tue 10 Aug 2021 10:08:28 AM UTC, comment #15: 

comentario nº14:

> We've had reports from other users that the Octave window "rendered off-screen" for them for some reason.
> To check if that is the case for you:
> While the black window is showing, is there an icon with the Octave logo in the task bar? If you hover that icon, does a small pre-view appear?
> If it does, please hold down the shift key, right click on that preview window and select "Move" (or whatever that translated to) from the context menu. After that, hit any of the arrow keys on the keyboard.
> Does that make the Octave GUI appear on screen?
>


Yes, the octave-gui process stays in background (I can see octave-gui.exe in the task manager), but there's no icon on the task bar except that of the command prompt (if using alt-tab, also there's no gui anywhere).

If I run octave-gui several times, the task manager shows the exact same number of octave-gui processes. So, there can be lot of them (see attachment). They just keep "idle", with no CPU consumption and about 7~8 Mbytes of memory usage each.


Anonymous
Tue 10 Aug 2021 09:32:50 AM UTC, comment #14: 

You are writing that nothing happens after you executed `octave.bat --gui` from the PowerShell prompt but the black window that appears.
IIUC, the black window will be there as long as the Octave process is running. If it isn't just flashing, that means that the Octave process didn't crash immediately.

We've had reports from other users that the Octave window "rendered off-screen" for them for some reason.
To check if that is the case for you:
While the black window is showing, is there an icon with the Octave logo in the task bar? If you hover that icon, does a small pre-view appear?
If it does, please hold down the shift key, right click on that preview window and select "Move" (or whatever that translated to) from the context menu. After that, hit any of the arrow keys on the keyboard.
Does that make the Octave GUI appear on screen?

Markus Mützel <mmuetzel>
Project Member
Tue 10 Aug 2021 09:16:15 AM UTC, comment #13: 

comentario nº11:

> Troubleshooting windows is always difficult like this.
>
> use the zip package installer to install to a location without spaces.  I suggest just creating a C:\Octave folder, and putting the octave-6.3.0-w64 folder under that.
>
> After unzipping, run the 'post-install.bat' file in the main folder. That may take a minute or two.
>


Ok, I've done everything you proposed, just I used E:\octave instead of C:\Octave.
No change in behavior. I also disabled antivirus and even added an exception for octave-gui.exe...

comentario nº12:

> Could you please also look at
>
> C:\Users\*username*\.config\octave
>
> which was used for saving the preferences in versions 5.x and older? Newer versions are trying to import these settings. If there is an ini file in this directory, please rename it and try again.


Yes, that directory existed, but contained no ini file. Just a file called qt-settings (no extension). I also tried to remove it, but no change in behavior either.

More info
---------

Octave 5.1 still runs fine.
I also tried octave 6.1 (zip), which behaves exactly the same as 6.3. The gui doesn't work.

I took a look into the windows registry but I didn't find anything which seems wrong to me.
I also checked the system variables, but there is no reference to octave whatsoever in there.

Anonymous
Tue 10 Aug 2021 04:58:42 AM UTC, comment #12: 

Could you please also look at

C:\Users\*username*\.config\octave

which was used for saving the preferences in versions 5.x and older? Newer versions are trying to import these settings. If there is an ini file in this directory, please rename it and try again.

Torsten Lilge <ttl>
Project Member
Tue 10 Aug 2021 02:48:15 AM UTC, comment #11: 

Troubleshooting windows is always difficult like this.

some other thoughts:

first - after uninstalling and deleting all mention of octave from the following folders:
c:\users\*username*\
(look for files starting with .octave and maybe an octave folder)

c:\users\*username*\AppData\Local
c:\users\*username*\AppData\Roaming
c:\users\*username*\AppData\LocalLow
(I have octave subfolders in two of those)

use the zip package installer to install to a location without spaces.  I suggest just creating a C:\Octave folder, and putting the octave-6.3.0-w64 folder under that.

After unzipping, run the 'post-install.bat' file in the main folder. That may take a minute or two.

so that's about as clean a state as you can get.

Then try running the octave.vbs file in that same folder.  if that doesn't work, again try the octave.bat file pointed to earlier, and just confirm no change in behavior.

If that doesn't work, can you temporarily disable whatever security software you are running (windows defender, etc.) and see if that changes either the vbs or bat behavior?

absent that, I'm not sure what conflict could be preventing the program from running.

Nicholas Jankowski <nrjank>
Project Member
Mon 09 Aug 2021 09:37:53 PM UTC, comment #10: 

comentario nº9:

> sorry, that should have said:
>
> "if the .bat file successfully opens an octave CLI..."


Just running the bat file opens a CLI.

Running octave.bat --gui from a command prompt just opens a new command prompt windows that stays black forever.
See attachment.
I used power shell, but the same goes for the regular windows command prompt.


Anonymous
Mon 09 Aug 2021 06:58:02 PM UTC, comment #9: 

sorry, that should have said:

"if the .bat file successfully opens an octave CLI..."

Nicholas Jankowski <nrjank>
Project Member
Mon 09 Aug 2021 06:57:26 PM UTC, comment #8: 

if the .bat file successfully opens an octave gui, next please open a command prompt, navigate to the

..\octave-6.3.0-w64\mingw64\bin

folder. Assuming it's under C:\Program Files\GNU Octave, you would type something like:

cd "C:\Program Files\GNU Octave\octave-6.3.0-w64\mingw64\bin"

or

cd "C:\Program Files\GNU Octave\mingw64\bin"

(because of the spaces in the folders, I think you need the "")

then run the command:
octave.bat --gui

let us know if anything starts.

Nicholas Jankowski <nrjank>
Project Member
Mon 09 Aug 2021 06:03:34 PM UTC, comment #7: 

in ..\octave-6.3.0-w64\mingw64\bin there should also be a octave.bat file. 

does anything happen if you run that file?

Nicholas Jankowski <nrjank>
Project Member
Mon 09 Aug 2021 02:30:38 PM UTC, comment #6: 

The only two ini files in the installation directory (both local and portable) are:

proj.ini
mxe-conf.ini

None of them related to the gui.
Inside AppData there're no ini files (my installation is on "C:\Program Files\GNU Octave").
Maybe "octave-gui.ini" is created the first time the gui is launched. But, in my case, the gui did never launch.

Does anybody know how could I investigate the issue or collect additional information?

Anonymous
Mon 09 Aug 2021 02:45:07 AM UTC, comment #5: 

this happened to me before.  the key was deleting the octave-gui.ini file.

for me this file on Windows 10 this was located at:

C:\Users\nicholas.jankowski\AppData\Roaming\octave

Nicholas Jankowski <nrjank>
Project Member
Fri 06 Aug 2021 09:03:37 PM UTC, comment #4: 

comentario nº3:

> Could you please have a look at the folder c:\users\your_username\appdata\octave, remove or rename the file octave-gui.ini and try again?


There's no such file...
Neither in that path, neither in the installation directory, neither in the portable (zip) installation.

Anonymous
Fri 06 Aug 2021 08:44:39 PM UTC, comment #3: 

Could you please have a look at the folder c:\users\your_username\appdata\octave, remove or rename the file octave-gui.ini and try again?

Torsten Lilge <ttl>
Project Member
Fri 06 Aug 2021 06:29:08 PM UTC, comment #2: 

comentario nº1:

> If you pull up the Windows start menu and type "octave", do you see choices labeled "Octave (GUI)" and "Octave (CLI)" among other entries? If you run the entry labeled "Octave (GUI)" does it load properly?


Yes, I see both.
And, no, it doesn't load. Nothing happends.
Just the CLI works.


Anonymous
Fri 06 Aug 2021 05:41:15 PM UTC, comment #1: 

If you pull up the Windows start menu and type "octave", do you see choices labeled "Octave (GUI)" and "Octave (CLI)" among other entries? If you run the entry labeled "Octave (GUI)" does it load properly?

Anonymous
Fri 06 Aug 2021 04:30:38 PM UTC, original submission:  

Hello.
I've been working with Octave 5.1 until now. No problems.
I just tried Octave 6.3 (x64), and the GUI doesn't work.

I tried:
- double clicking on octave.vbs (nothing happends)
- double clicking on octave-gui.exe (inside mingw64\bin directory). A Windows' command promt opens up, but remains black forever (see attachment #1).

The CLI works fine (see attachment #2).

I tried the ZIP (portable) version, but the installer too. Exact same effect.

Octave 5.1 still works perfectly.

I'm using: Windows 10 x64 (up to date) on a core i5 2500K and 12 GB RAM.

I installed Octave 6.3 on another computer, and works perfect.

Is there anything I can do to provide more useful information or debug what is going on? I'm a software developer, and can deal with technical stuff.

Thank you very much, and willing to help.

Anonymous

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #51777:  octave-fix.png added by None (29KiB - image/png)
file #51760:  octave-waitchain.png added by None (12KiB - image/png)
file #51759:  octave-no@appdata.png added by None (18KiB - image/png)
file #51758:  octave_taskmngr.png added by None (21KiB - image/png)
file #51755:  octave_bat.png added by None (27KiB - image/png)
file #51745:  octave-gui-menu.png added by None (74KiB - image/png)
file #51743:  octave-gui.png added by None (8KiB - image/png)
file #51744:  octave-cli.png added by None (33KiB - 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 mmuetzel (Posted a comment)
  • -email is unavailable- added by nrjank (Posted a comment)
  • -email is unavailable- added by ttl (Posted a comment)
  • -email is unavailable- added by None (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 9 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-08-21 mmuetzel StatusNone => Ready For Test
    2021-08-14 None Attached File- => Added octave-fix.png, #51777
    2021-08-11 None Attached File- => Added octave-waitchain.png, #51760
    2021-08-10 None Attached File- => Added octave-no@appdata.png, #51759
    2021-08-10 None Attached File- => Added octave_taskmngr.png, #51758
    2021-08-09 None Attached File- => Added octave_bat.png, #51755
    2021-08-06 None Attached File- => Added octave-gui-menu.png, #51745
    2021-08-06 None Attached File- => Added octave-gui.png, #51743
        Attached File- => Added octave-cli.png, #51744

    Back to the top


    Powered by Savane 3.6