[Octave-bug-tracker] [bug #61835] GNU Octave GUI runs with 4.4.1 (w32), 5.2.0 (w32) and 6.1.0 (w32) but not with 6.3.0, 6.4.0 (w32) under windows 10.

[halit]

Follow-up Comment #15, bug #61835 (project octave):


[comment #14 comment #14:]
> @hngursoy: Yes, I absolutely believe you, that (4.4.1, 5.2.0 and 6.1.0) are
working fine 😉 
> 
> The tricky part is now to find out what makes those working installations
different from the new ones.  And therefore I need your help, as I do not have
physical access to your system.  Thus if I ask questions, I need information
to exclude a particular source of errors.  I also run different Octave
versions in parallel on MS Windows.  It is not impossible.
> 
> As the Octave 6.4.0 GUI seems to pop up on the first run for a short instant
of time, I am tempted to believe it is in the end
> 
> https://wiki.octave.org/FAQ#MS_Windows (comment #1)
> 
> Please make sure the following directories and files are properly deleted
before starting Octave again:
> 
> 
> After Octave upgrade the GUI does not open / shuts down immediately.
> Solution:
> Version 5.2.0 and older: Delete the folder
C:\Users\YOUR_USER_NAME\.config\octave
> Version 6.1.0 and newer: Delete the folder %APPDATA%\octave, which generally
is located at C:\Users\YOUR_USER_NAME\AppData\Roaming\octave
> 
> 
> Another source of error might be that you have multiple screens attached to
your PC.  Is this the case?
> 

starting from the last one, there are no multiple screens... only notebook and
its screen. 

I have followed the instructions and deleted all user related config files
related with octave. I have made the following observations:

1. when I start up the versions 4.4.1 and 5.2.0 they create a config file
under my user directory however the versions 6.1.0 and 6.4.0 do not do this...
I have already verified this several times with those four releases, 4.1, 5.2,
6.1, and 6.4...

2. When I run GUI I can see the previously executed commands from the command
history window. I invoked "exit" with 4.1, 5.2 and 6.1 and the window shows
those histories... however there is nothing with the history of 6.4 release,
from this I conclude that 6.4 never comes up as an running application, it is
terminated even before it actually starts up. 


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61835>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/