bugGNU Octave - Bugs: bug #61835, GNU Octave GUI runs with 4.4.1...

 
 

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.

Submitter:  halit <hngursoy>
Submitted:  Mon 17 Jan 2022 05:30:04 AM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Other
Status:  Need Info Assigned to:  None
Originator Name:  halit Open/Closed:  * Closed
Release:  * 6.3.0 Operating System:  * Microsoft Windows
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Tue 25 Jan 2022 01:00:18 PM UTC, comment #20: 

I was just curious if there is a difference between the 32bit and 64bit installer variants, probably.

I've installed two in parallel on my machine:
octave-6.4.0-w32-installer.exe
octave-6.4.0-w64-installer.exe
(not: octave-6.4.0-w64-64-installer.exe)

The observation is that both variants are running fine, CLI as well as GUI. So, no clue what went wrong before.

Armin MΓΌller <arm_in>
Sun 23 Jan 2022 12:00:53 PM UTC, comment #19: 

comment #18:

> Closing report as this seems to be specific to a given PC rather than a general Octave issue, and there doesn't seem to be a way to successfully debug what is happening.


This is a brief feedback. I was finally able to install and run GUI v:6.4.0 today. First of all, I removed anything and everything related with Octave on my notebook, and then installed v:6.4.0 using "octave-6.4.0-w64-installer.exe"... finally I was able to run the GUI (also CLI) without any problems. Thanks A LOT for your support and help. Sorry for the inconvenience. Halit

halit <hngursoy>
Wed 19 Jan 2022 08:08:41 PM UTC, comment #18: 

Closing report as this seems to be specific to a given PC rather than a general Octave issue, and there doesn't seem to be a way to successfully debug what is happening.

Rik <rik5>
Group administrator
Wed 19 Jan 2022 10:21:52 AM UTC, comment #17: 

Thanks a lot for your support. I do appreciate it a lot. I have given it up.

halit <hngursoy>
Wed 19 Jan 2022 02:08:29 AM UTC, comment #16: 

@hngursoy: could you try to avoid quoting the previous post in your replies?  This makes the discussion lengthy and difficult to follow.

I run out of ideas.  A deperate attempt is to try the installation on another laptop, if it is working there, try to figure out the differences between both systems.

Another final source of errors might be the MS Windows Event log:

https://docs.microsoft.com/en-us/windows/security/threat-protection/auditing/view-the-security-event-log

Anything suspicious there?

Kai Torben Ohlhus <siko1056>
Group Member
Tue 18 Jan 2022 11:01:10 AM UTC, comment #15: 


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.

halit <hngursoy>
Tue 18 Jan 2022 04:01:39 AM UTC, 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?

Kai Torben Ohlhus <siko1056>
Group Member
Tue 18 Jan 2022 03:21:28 AM UTC, comment #13: 


comment #12:

>
> comment #11:
> > comment #10:
> > > We are getting slowly there.  Thus, it is possible to start the Octave 6.3.0 and 6.4.0 CLI (command-line interface = black terminal) versions of Octave on your system.  This is a very important information if Octave entirely refuses to work or the GUI is just not showing up for an unknown reason πŸ˜‰
> > >
> > > When you start Octave 6.4.0 CLI, can you run commands like
> > >


> > > plot (1:10)


> >
> > I have just downloaded and installed 6.4.0 using "octave-6.1.0-w32-installer"
> > Installation run ok, no errors. It is installed under this directory:
> > C:\Octave\Octave-6.4.0
> >
> > I started up CLI and ran "plot(1:10)" a window popped up and a graphic showed up without any problem. I exited CLI. Then I invoked GUI, it showed up for a couple of seconds and then shut down before I did anything... that is all.
> >
> > On my notebook, the other three releases (4.4.1, 5.2.0 and 6.1.0) run OK (both CLI and GUI) without any problem...
> >
>
> I just did a typo error above, and the actual installer I used is as follows:
> "octave-6.4.0-w32-installer.exe"
>


After the first try whenever I run GUI again and again, it never showed up... I got a big white color window and at the top left corner there was Octave Logo, and "Octave". It disappeared in a second. That was it.

halit <hngursoy>
Tue 18 Jan 2022 03:11:55 AM UTC, comment #12: 


comment #11:

> comment #10:
> > We are getting slowly there.  Thus, it is possible to start the Octave 6.3.0 and 6.4.0 CLI (command-line interface = black terminal) versions of Octave on your system.  This is a very important information if Octave entirely refuses to work or the GUI is just not showing up for an unknown reason πŸ˜‰
> >
> > When you start Octave 6.4.0 CLI, can you run commands like
> >


> > plot (1:10)


>
> I have just downloaded and installed 6.4.0 using "octave-6.1.0-w32-installer"
> Installation run ok, no errors. It is installed under this directory:
> C:\Octave\Octave-6.4.0
>
> I started up CLI and ran "plot(1:10)" a window popped up and a graphic showed up without any problem. I exited CLI. Then I invoked GUI, it showed up for a couple of seconds and then shut down before I did anything... that is all.
>
> On my notebook, the other three releases (4.4.1, 5.2.0 and 6.1.0) run OK (both CLI and GUI) without any problem...
>


I just did a typo error above, and the actual installer I used is as follows:
"octave-6.4.0-w32-installer.exe"

halit <hngursoy>
Tue 18 Jan 2022 03:08:48 AM UTC, comment #11: 

comment #10:

> We are getting slowly there.  Thus, it is possible to start the Octave 6.3.0 and 6.4.0 CLI (command-line interface = black terminal) versions of Octave on your system.  This is a very important information if Octave entirely refuses to work or the GUI is just not showing up for an unknown reason πŸ˜‰
>
> When you start Octave 6.4.0 CLI, can you run commands like
>


> plot (1:10)


I have just downloaded and installed 6.4.0 using "octave-6.1.0-w32-installer"
Installation run ok, no errors. It is installed under this directory:
C:\Octave\Octave-6.4.0

I started up CLI and ran "plot(1:10)" a window popped up and a graphic showed up without any problem. I exited CLI. Then I invoked GUI, it showed up for a couple of seconds and then shut down before I did anything... that is all.

On my notebook, the other three releases (4.4.1, 5.2.0 and 6.1.0) run OK (both CLI and GUI) without any problem...

halit <hngursoy>
Tue 18 Jan 2022 01:07:13 AM UTC, comment #10: 

We are getting slowly there.  Thus, it is possible to start the Octave 6.3.0 and 6.4.0 CLI (command-line interface = black terminal) versions of Octave on your system.  This is a very important information if Octave entirely refuses to work or the GUI is just not showing up for an unknown reason πŸ˜‰

When you start Octave 6.4.0 CLI, can you run commands like


plot (1:10)


Kai Torben Ohlhus <siko1056>
Group Member
Mon 17 Jan 2022 10:09:43 PM UTC, comment #9: 

comment #8:

>
> comment #7:
> > In comment #5, I wanted to know the installation location on your local file system, e.g.
> >
> > C:\Octave\6.3.0\
> >
> > or alike πŸ™‚
> >
> > Windows Defender was in the past less a problem, thus AV is probably not guilty.
> >
> > How about the Octave CLI versions (comment #1)?
>
> No problem with CLI what so ever...


On my notebook currently there are 3 releases installed as follows:

C:\Octave\Octave-4.4.1
C:\Octave\Octave-5.2.0.0
C:\Octave\Octave-6.1.0

they run OK, both CLI and GUI.

I have similarly installed the problematic releases in the same way...

C:\Octave\Octave-6.3.0
C:\Octave\Octave-6.4.0

Then I got the GUI problem, and I uninstalled them.

halit <hngursoy>
Mon 17 Jan 2022 08:59:19 PM UTC, comment #8: 


comment #7:

> In comment #5, I wanted to know the installation location on your local file system, e.g.
>
> C:\Octave\6.3.0\
>
> or alike πŸ™‚
>
> Windows Defender was in the past less a problem, thus AV is probably not guilty.
>
> How about the Octave CLI versions (comment #1)?


No problem with CLI what so ever...

halit <hngursoy>
Mon 17 Jan 2022 04:09:40 PM UTC, comment #7: 

In comment #5, I wanted to know the installation location on your local file system, e.g.

C:\Octave\6.3.0\

or alike πŸ™‚

Windows Defender was in the past less a problem, thus AV is probably not guilty.

How about the Octave CLI versions (comment #1)?

Kai Torben Ohlhus <siko1056>
Group Member
Mon 17 Jan 2022 02:51:16 PM UTC, comment #6: 


comment #5:

> Was it possible to post the installation location of all Octave releases?
>
> Do you use any "Anti-virus" software which might block "quarantine" Octave files?


This is the site where I have downloaded those five releases...

Index of /gnu/octave/windows
https://ftp.gnu.org/gnu/octave/windows/

On the notebook there exist windows' AV utility (under windows security). That is all nothing else.

If that AV is a factor somehow it does not affect three previous releases but the last two ones.

halit <hngursoy>
Mon 17 Jan 2022 02:04:28 PM UTC, comment #5: 

Was it possible to post the installation location of all Octave releases?

Do you use any "Anti-virus" software which might block "quarantine" Octave files?

Kai Torben Ohlhus <siko1056>
Group Member
Mon 17 Jan 2022 01:40:31 PM UTC, comment #4: 


comment #2:

> Special characters (i.e. non ASCII) and blank / space characters in the installation path might also pose a problem.


Thanks for the reply.

I have downloaded 5 releases (maybe 10 times in total), in the same way in the same drive on notebook all of them have been installed without ant error. GUI runs (namely comes up) with the three older releases but it does not run (never comes up) with the two recent releases. I have not made any changes on the notebook. Once the installed version failed, I have uninstalled it before installing it again or installing another release. In other words, I have not touched ant windows system parameters (path, etc.) during the installations. I have also installed working versions multiple times to make sure that they are completely OK.

halit <hngursoy>
Mon 17 Jan 2022 01:33:31 PM UTC, comment #3: 

comment #1:

> Thanks for the report, this seems weird.  Does any of the well-known tricks help?
>
> https://wiki.octave.org/FAQ#MS_Windows
>
> Furthermore, does "not run" mean there is no reaction at all clicking on the Octave icon?
>
> Does the command-line interface (Octave CLI) work for the respective versions?


Thanks or the reply message.

I have not looked into those "tricks", I was not aware of them.
 
"not run" means, GUI does not come up at all. In is strange, GUI runs perfectly with those two version but not with the two recent ones. I have download the releases from the same location (https://ftp.gnu.org/gnu/octave/windows/). I have downloaded them into the same drive on my notebook. Installations run without any problem or error. I have not made any changes on my notebook nevertheless I have not been able to run the GUI with the two recent releases.

halit <hngursoy>
Mon 17 Jan 2022 11:16:02 AM UTC, comment #2: 

Special characters (i.e. non ASCII) and blank / space characters in the installation path might also pose a problem.

Armin MΓΌller <arm_in>
Mon 17 Jan 2022 09:02:56 AM UTC, comment #1: 

Thanks for the report, this seems weird.  Does any of the well-known tricks help?

https://wiki.octave.org/FAQ#MS_Windows

Furthermore, does "not run" mean there is no reaction at all clicking on the Octave icon?

Does the command-line interface (Octave CLI) work for the respective versions?

Kai Torben Ohlhus <siko1056>
Group Member
Mon 17 Jan 2022 05:30:04 AM UTC, original submission:  

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.

It (GUI) runs with:
octave-4.4.1-w32,
octave-5.2.0-w32, and
octave-6.1.0-w32

but I failed in multiple attempts with
octave-6.3.0-w32 and
octave-6.4.0-w32


halit <hngursoy>

 

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

Attach Files:
   
   
Comment:
   

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 (Posted a comment)
  • -email is unavailable- added by arm_in (Posted a comment)
  • -email is unavailable- added by siko1056 (Posted a comment)
  • -email is unavailable- added by hngursoy (Submitted the item)
  •  

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

    Date Changed by Updated Field Previous Value => Replaced by
    2022-01-19 rik5 Open/ClosedOpen Closed
    2022-01-17 siko1056 StatusNone Need Info

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code