bugGNU Octave - Bugs: bug #50692, Command Window outputs spurious...

 
 

bug #50692: Command Window outputs spurious newline every 30 sec.

Submitter:  None
Submitted:  Fri 31 Mar 2017 04:30:25 PM UTC
   
 
Category:  GUI Severity:  3 - Normal
Priority:  3 - Low Item Group:  Unexpected Error or Warning
Status:  None Assigned to:  None
Originator Name:  tcbrooke Originator Email:  -email is unavailable-
Open/Closed:  * Open Release:  * 6.1.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 04 Apr 2023 06:55:12 PM UTC, comment #38: 

When Octave starts on Windows, it runs in a Windows Console (https://learn.microsoft.com/en-us/windows/console/consoles) and the state of the underlying screen buffer (https://learn.microsoft.com/en-us/windows/console/console-screen-buffers) is displayed in a Qt QWidget object in the Octave GUI.

As far as I know, all the code for this functionality is in the libgui/qterminal/libqterminal/win32 directory of the Octave sources.

A timer is created that causes the function  QConsolePrivate::monitorConsole in Octave's QWinTerminalImpl.cpp file to be called every 10 milliseconds.

That function will reposition the cursor if the cursor position of the screen buffer changes or insert output if the contents of the buffer have changed.

It is possible that something in Octave is causing that to happen.  If so, something would have to be writing a newline character (or something similar) to Octave's standard output stream.  But since this doesn't happen for everyone, I don't think it is something that Octave is doing by default.  And if it is something added locally or due to an add-on package, I would expect behavior to be fixed if you delete all locally installed packages and/or start Octave with the --norc option to prevent Octave from loading any initialization files.

It is also possible that some external process is writing to console screen buffer.

It seems that we need someone who observes this issue and who also has the necessary expertise to debug it.  I don't have a Windows system, and even when I had access to one for running Octave, I never observed the issue.

Even if I were able to observe the issue, I don't know exactly how I would determine what process is writing to Octave's console screen buffer other than disabling background processes that could be doing that until I found that the behavior stopped.

John W. Eaton <jwe>
Group administrator
Tue 04 Apr 2023 02:27:13 PM UTC, comment #37: 


comment #34:

> There are programs like https://www.techspot.com/downloads/5953-dont-sleep.html
>


And also like that:
https://ogymogy.com/windows/capture-screenshots

And there are usual suspects like antivirus.

Dmitri.
--

Dmitri A. Sergatskov <dasergatskov>
Tue 04 Apr 2023 01:50:18 PM UTC, comment #36: 

This is happening for me on v8.1.  It only happens in the GUI command window.  It doesn't matter if Octave has focus or not.  The CLI implementation doesn't exhibit this behavior.  Running Windows 10 on a Lenovo laptop.

Marco Dalla Gasperina <marcodg>
Thu 16 Mar 2023 08:31:08 PM UTC, comment #35: 


comment #34:

> There are programs like https://www.techspot.com/downloads/5953-dont-sleep.html
>
> to defeat programs like https://www.dell.com/support/kbdoc/en-us/000125433/windows-locks-enters-standby-after-1-minute-due-to-dell-optimizer-proximity-sensor
>
> If your corporate laptops have things like that, they may be sending the spurious newlines. Did your corporate IT say what was running every 30 seconds?


My computer definitely falls asleep if I leave it alone for long enough, so an app like that doesn't seem likely. If there was something sending newlines, why wouldn't I see this behavior in other text programs like Word, Notepad, or Visual Studio Code?

I have not contacted my corporate IT; they have no diagnostic skills. If the problem isn't in their flow chart their only solution is to reimage my hard drive.

Mike Liszka <dodeka>
Thu 16 Mar 2023 05:50:55 PM UTC, comment #34: 

There are programs like https://www.techspot.com/downloads/5953-dont-sleep.html

to defeat programs like https://www.dell.com/support/kbdoc/en-us/000125433/windows-locks-enters-standby-after-1-minute-due-to-dell-optimizer-proximity-sensor

If your corporate laptops have things like that, they may be sending the spurious newlines. Did your corporate IT say what was running every 30 seconds?

Anonymous
Thu 16 Mar 2023 04:57:57 PM UTC, comment #33: 

Adding my voice to the choir. I'm running version 5.2.0 on a company laptop, though it apparently is still an issue in version 7.3.0 according to commenter #32.

Please help!!

Mike Liszka <dodeka>
Thu 09 Feb 2023 09:26:14 AM UTC, comment #32: 

I am seeing the issue on 7.3.0 on a company laptop. There are 2 newlines inserted periodically.

Anonymous
Wed 09 Mar 2022 06:25:54 PM UTC, comment #31: 

Commenter #24, 27, 28, 29, and 30 here.

I had Octave open for 1.5 days without seeing any spurious newlines in the command window. During that time I entered various equations in the command window. Then, just now, I opened the editor, typed up a 5 line script and pressed the "Save file and run" icon. I'm now getting the newlines in the command window again! In fact the result of my script has already scrolled up out of view in the time for me to write this update.


Anonymous
Tue 08 Mar 2022 03:16:50 PM UTC, comment #30: 

Commenter #24, 27, 28, 29 here.

Another hint. Using Octave with internet connected and no newlines for over an hour of use this morning.

Please share any ideas of how to figure out what causes the newlines ... i'm sure they'll start up again later today.


Anonymous
Fri 04 Mar 2022 03:35:14 PM UTC, comment #29: 

Commenter #24,27,28 here.

Today I can't get the newlines to stop.
Tried disconnecting internet connection and restarting Octave.
Tried reconnecting internet and restarting Octave.

Can't get the newlines to stop coming every 30seconds : (

Anonymous
Thu 03 Mar 2022 09:38:09 PM UTC, comment #28: 

Commenter #24,27 here.

After enjoying several hours of no surious newlines the problem returned. I disconnected from internet and restarted Octave. Unlike last time I continued to get spurious newlines while disconnected.

I then reconnected to internet. Restarted Octave, and now while connected the newlines every 30seconds has gone away again (for now).

Strange behaviour, but felt I best update lest one thinks disconnecting from internet alone solves problem.

Anonymous
Thu 03 Mar 2022 05:08:57 PM UTC, comment #27: 

Commenter#24 here. Thanks for responses!

I can confirm that I'm observing the issue on a company issued laptop running Windows 10 Enterprise. I also observed the issue at my last employer as well. It was also on a company issued laptop running Windows 10.

I just tested. And if I disconnect the network connection and start Octave after that, the problem appears to have go away! Not the best workaround, but a workaround nonetheless, and I hope a useful hint.

I checked Windows Scheduler and did not find anything happening every 30 seconds.

Interesting side note. I reconnected to the netork, started Octave after that, and the problem hasn't come back yet.

Let me know if other things I can check on.

Anonymous
Wed 02 Mar 2022 02:06:19 PM UTC, comment #26: 

Questions to those of you who can see this problem:

  • Is it only in a corporate Windows environment (including company-issued laptops) or do you also see it on computers that you manage 100% by yourself independent of corporate work?


  • If you can disconnect the network connection from your computer, do so and start Octave after that. Do you see that problem?


It sounds like something is trying to keep a network connection alive by sending a character every 30 seconds, like older SecureCRT. This could also be a third party VB script designed to prevent screen lockout. If you can view Windows Scheduler, check it for 30-second intervals.

Anonymous
Tue 01 Mar 2022 06:40:10 PM UTC, comment #25: 

I agree that it would be great to fix this problem, but first we have to understand what is causing it to happen.  I have never been able to duplicate it.  Can you help us understand why it happens?  With that info, maybe someone could come up with a fix.

John W. Eaton <jwe>
Group administrator
Tue 01 Mar 2022 02:00:06 PM UTC, comment #24: 

March 2022 and this is still an issue. Sure wish this could get fixed. Or maybe a workaround? Has large impact on usability.

Anonymous
Wed 29 Sep 2021 08:07:04 PM UTC, comment #23: 

Oh yeah, company IT stuff (don't get me started); that could also be the culprit ...

The fact that it seems to be dependent on specific HW and SW environments seems to suggest that Octave can't do much about it - but as I wrote it can't be ruled out that on Windows systems, Octave is vulnerable to badly written, seemingly unrelated SW, or badly written or not fully OS-compatible HW drivers (e.g., keyboard / HID drivers).
The 30 sec. interval described in comments below is definitely a clue pointing to background activity outside Octave.

Philip Nienhuis <philipnienhuis>
Group Member
Tue 28 Sep 2021 07:18:03 PM UTC, comment #22: 

comment #20:

> Just a hunch: do you have the Wallpaper Slide Show running in the background? (it changes your background picture by default every 30 seconds)
> I think this bug must be related to some automated background task that runs at regular intervals and is otherwise supposed to be quite harmless; but does interfere in an unexpected way with Octave.


The computer I was using had a lot (like really a lot) of corporate-managed stuff going on in the background, but this did not include a wallpaper slideshow; the wallpaper was in fact locked to a corporate logo image.

I've changed companies, and it's not happening on the much less, um, IT-customized machine I have now.

Mike Britton <mbritton>
Tue 28 Sep 2021 07:16:12 PM UTC, comment #21: 

I never use a slideshow as wallpaper.  Only a static image or black.  But who knows if windows still has a timer running although it does not change anything.  But I can not see how that would insert newlines into octave.

By the way, I think I saw this problem once also in the CLI terminal long ago.  Now I have a new computer and have not seen this problem any more.

-Tom

Tom Ahola <tomahola>
Tue 28 Sep 2021 06:27:21 PM UTC, comment #20: 

Just a hunch: do you have the Wallpaper Slide Show running in the background? (it changes your background picture by default every 30 seconds)

I think this bug must be related to some automated background task that runs at regular intervals and is otherwise supposed to be quite harmless; but does interfere in an unexpected way with Octave.
Octave itself isn't quite a standard Windows application (although on Windows its terminal is based om cmd.exe AFAIK) so I wouldn't be very surprised if it is vulnerable for some remote side effects from other programs/services operations.
It can be helpful to find out which tasks are running by using Task Manager and inspect the Startup and Services tabs (the latter for running services) and try to find out which ones might be candidates for regular activity.

I just searched for "windows background action every 30 seconds" and that yielded quite a few "promising" hits: e.g., crashing & restarting explorer.exe, incompatible sound drivers, network software; that sort of things.
Maybe this one: "https://www.computerhope.com/forum/index.php?topic=153846.0"? it contains a few hints for finding out what might be happening behind your back.

Philip Nienhuis <philipnienhuis>
Group Member
Mon 27 Sep 2021 09:43:57 PM UTC, comment #19: 

I am seeing this behavior in 6.3.0 (x64) on a win10 machine

clark newman <cpnewman>
Tue 01 Dec 2020 07:32:30 PM UTC, comment #18: 

Thanks for checking.
Updating release to 6.1.0.

Markus Mützel <mmuetzel>
Group administrator
Tue 01 Dec 2020 07:31:09 PM UTC, comment #17: 

comment #16:

> Does this still occur for affected systems with Octave 6.1.0?

Yes: I have just upgraded to Octave 6.1.0 and this bug is still affecting my system.

Mike Britton <mbritton>
Tue 01 Dec 2020 04:46:50 PM UTC, comment #16: 

Does this still occur for affected systems with Octave 6.1.0?

Markus Mützel <mmuetzel>
Group administrator
Wed 10 Jul 2019 02:09:01 PM UTC, comment #15: 

This issue is also showing up in the CLI, not just the GUI.

I left the CLI open overnight, and it has started doing this (generating spurious line feeds) at some point, still every 30 seconds, but now slightly after the 17 and 47 second marks of the system clock. This may be a useful clue as to what's causing the issue...

Mike Britton <mbritton>
Fri 05 Jul 2019 02:25:07 PM UTC, comment #14: 

I'm also running into this on a fresh install of Octave 5.1.0 on Windows 10 ("About Octave" reports Octave was configured for "x86_64-w64-mingw32".).

Interestingly, the bonus line breaks are occurring at the 18 and 48 second marks of the system clock for me too, and this remains consistent after closing and reopening Octave.

It looks like this bug has been independently reported quite a few times (4 duplicates, plus several "me too" here), and it impacts the usability pretty significantly. I'd like to request a priority bump on it.

Thanks nevertheless for a very handy and powerful free tool!

Mike Britton <mbritton>
Tue 02 Apr 2019 11:44:46 AM UTC, comment #13: 

This problem is only in the GUI command window, not the CLI terminal.  It happens regardless where the focus is, even when focus is in another application and also when Octave is minimized to the task bar.  It is of course most annoying when you are typing and editing a formula in the command window and suddenly there is a line break in the middle of your formula and you can not go back up.

I have to take back my previous comment about this happening on the 0 and 30 second mark of the system clock.  Now it was at 48 and 18 second marks.  But always exactly 30 seconds apart.

Tom Ahola <tomahola>
Tue 02 Apr 2019 11:04:00 AM UTC, comment #12: 

Where (on which pane) is the focus when this happens? on the terminal pane? or is the focus not on Octave?

I'm asking because at work I often have my PC (Win 7 Enterprise) with Octave in the foreground idle for hours and hours when I'm away for other tasks and I never noted spurious newlines.

Philip Nienhuis <philipnienhuis>
Group Member
Tue 02 Apr 2019 09:16:57 AM UTC, comment #11: 

Re-opening.

Does this also happen with the CLI or only with the GUI?

Markus Mützel <mmuetzel>
Group administrator
Tue 02 Apr 2019 07:47:09 AM UTC, comment #10: 

I have the same problem.  This makes Octave GUI Command line practically unusable.  This bug has been there for over a year.  I used version 4.2.1 earlier and had to abandon use.  Now I tried version 5.1.0 and the bug is still there.  I have Windows 7.

Every 30 seconds, when system time hits an even minute and 30 seconds past the minute, the command window cursor skips to the next line. One can still type to the command line and hit enter in the end. The command line now split at random points to several lines will be successfully computed. The problem is that you can not edit the line back past the inserted line break and the whole thing looks really messy.

I tried to un-install and re-install but that did not help in my case.  I suggest the bug to be re-opened because it practically prevents the use of Octave GUI.

Tom Ahola <tomahola>
Thu 21 Mar 2019 12:34:04 AM UTC, comment #9: 

I confirmed that both 5.1.0-w64 and 4.4.1-w64 still have this problem on my Windows7 computer.


I have tried re-installing Octave and have not loaded any OF packages. But this problem did not go away - very annoying.

It will be greatly appreciated if you can fix this problem.

Auto Tiger <autotiger>
Sun 10 Mar 2019 06:51:56 PM UTC, comment #8: 

No response, asumming this has been fixed in the latest release.  Closing report.

Rik <rik5>
Group administrator
Sun 03 Mar 2019 06:25:23 AM UTC, comment #7: 

Version 4.4.1 is deprecated and no longer supported.  Please try with the latest stable release which is 5.1.0.  The problem is likely to have been fixed.

Rik <rik5>
Group administrator
Thu 24 Jan 2019 04:25:24 PM UTC, comment #6: 

I can't reproduce the problem with 4.4.1 and Windows 7 running in a virtualbox vm.

This sounds like a readline input event hook function is somehow installed and that it is displaying a newline character, except in that case it should happen every 0.1 seconds.  I have no idea what would write a newline every 30 seconds.

John W. Eaton <jwe>
Group administrator
Thu 24 Jan 2019 03:23:21 PM UTC, comment #5: 

The problem is still present in 4.4.1 on Windows 7 64 bits.

Anonymous
Mon 20 Nov 2017 11:15:09 AM UTC, comment #4: 

I have exactly the same problem, no chance of turning that off.
Tried a lot the last few months, nothing worked.
Only use it with CLI now.

Stefan <thehighendoflow>
Wed 28 Jun 2017 10:36:07 PM UTC, comment #3: 

This behavior has been confirmed by an independent reporter using Windows 7 (see bug #51301). Still lacking reproducibility or explanation.

Mike Miller <mtmiller>
Group Member
Tue 04 Apr 2017 05:15:11 PM UTC, comment #2: 

After reinstalling Octave:  still does it.

No OF packages loaded.
Just start "Octave (GUI)" and click things.
However, it's my understanding that some packages are loaded implicitly (e.g., general and miscellaneous).  Here's my path immediately after startup:

p = .;C:\Octave\OCTAVE~1.1\lib\octave\4.2.1\site\oct\x86_64-w64-mingw32;C:\Octave\OCTAVE~1.1\lib\octave\site\oct\
api-v51\x86_64-w64-mingw32;C:\Octave\OCTAVE~1.1\lib\octave\site\oct\x86_64-w64-mingw32;C:\Octave\OCTAVE~1.1\share
\octave\4.2.1\site\m;C:\Octave\OCTAVE~1.1\share\octave\site\api-v51\m;C:\Octave\OCTAVE~1.1\share\octave\site\m;C:
\Octave\OCTAVE~1.1\share\octave\site\m\once_only;C:\Octave\OCTAVE~1.1\share\octave\site\m\startup;C:\Octave\OCTAV
E~1.1\lib\octave\4.2.1\oct\x86_64-w64-mingw32;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m;C:\Octave\OCTAVE~1.1\shar
e\octave\4.2.1\m\audio;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\deprecated;C:\Octave\OCTAVE~1.1\share\octave\4.2
.1\m\elfun;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\general;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\geometry;C
:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\gui;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\help;C:\Octave\OCTAVE~1.1\
share\octave\4.2.1\m\image;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\io;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m
\java;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\linear-algebra;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\miscella
neous;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\ode;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\optimization;C:\Oct
ave\OCTAVE~1.1\share\octave\4.2.1\m\path;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\pkg;C:\Octave\OCTAVE~1.1\share
\octave\4.2.1\m\plot;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\plot\appearance;C:\Octave\OCTAVE~1.1\share\octave\
4.2.1\m\plot\draw;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\plot\util;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\p
olynomial;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\prefs;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\profiler;C:\O
ctave\OCTAVE~1.1\share\octave\4.2.1\m\set;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\signal;C:\Octave\OCTAVE~1.1\s
hare\octave\4.2.1\m\sparse;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\specfun;C:\Octave\OCTAVE~1.1\share\octave\4.
2.1\m\special-matrix;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\startup;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\
statistics;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\statistics\base;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\st
atistics\distributions;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\statistics\models;C:\Octave\OCTAVE~1.1\share\oct
ave\4.2.1\m\statistics\tests;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\strings;C:\Octave\OCTAVE~1.1\share\octave\
4.2.1\m\testfun;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\m\time;C:\Octave\OCTAVE~1.1\share\octave\4.2.1\data

It still does it after closing/showing the Command Window, and/or the File Browser, and/or the Workspace, and/or the Command History panes.

During installation, Octave reported that it couldn't find a JRE.  There is a JRE installed, and on the path, but the items on the path are symlinks.  I could not find a way to tell Octave where to look specifically.

During installation, I selected the [default] "OpenBLAS" library.

No idea if any of that matters.

Anonymous
Mon 03 Apr 2017 08:41:40 PM UTC, comment #1: 

I tried your examples in Octave-4.3.0+ (dev version) but I cannot reproduce your issues.
The sort of problems you describe are often fairly hard to reproduce anyway.
Windows 10 with all its silent if not stealth updates / upgrades is a bit of a moving target - that already broke some of my hardware drivers (reason for me to stick with Win 7 as much as I can).

Have you tried re-installing Octave?
Did you have any OF packages loaded (using the "pkg load <list of packages>" command?
Have you experimented with showing / hiding panes?
(sorry for all those questions but you seem to be able to reproduce, so you're the one best suited to discover some sort of pattern or consistent behavior)

Philip Nienhuis <philipnienhuis>
Group Member
Fri 31 Mar 2017 04:30:25 PM UTC, original submission:  

Some commands/actions cause the Command Window to output a newline every 30 seconds or so. Even when in the middle of entering a command.

Once it starts, there does not seem to be any way to stop it.

Things which seem to cause it to happen:

  • Expand a directory (the '+' icon) in the File Browser panel.
  • Select a recent directory from the File Browser current working directory choice/drop-down/combo-box control
  • Double-click a directory in the File Browser panel.


Things which don't seem to cause it to happen:

  • Scroll the list of files/directories in the File Browser panel.
  • Show the drop-down list of recent directories (without selecting one)
  • Select (single-click) a directory in the File Browser panel.


Additionally, some commands seem to trigger the problem fairly reliably -- but not universally:

  • 'cd Someplace' (no quotes)
  • 'cd ".."'

Others do not:

  • 'cd "Someplace"' (with quotes)


Clearing the command window does NOT stop the periodic newlines.

Unchecking the preference "Synchronize Octave Working Directory with file browser" does not stop the periodic newlines, nor does it prevent them from happening in the first place.

Configuration:

Windows10 (yes, I realize this is still experimental)

GNU Octave, version 4.2.1
Octave was configured for "x86_64-w64-mingw32".

Installed from "octave-4.2.1-w64-installer.exe"

Invoked from "Octave (GUI)" choice on Start menu

Anonymous

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #46694:  octave_bug.png added by tomahola (28KiB - image/png - This is how it looks like with three unwanted line breaks)

 

Carbon-Copy List
  • -email is unavailable- added by dasergatskov (Posted a comment)
  • -email is unavailable- added by marcodg (Posted a comment)
  • -email is unavailable- added by dodeka (Posted a comment)
  • -email is unavailable- added by cpnewman (Posted a comment)
  • -email is unavailable- added by jimfitchusa
  • -email is unavailable- added by mbritton (Posted a comment)
  • -email is unavailable- added by stromi
  • -email is unavailable- added by tomahola (Posted a comment)
  • -email is unavailable- added by autotiger (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by thehighendoflow (Posted a comment)
  • -email is unavailable- added by None (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 19 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-03-01 mmuetzel Carbon-CopyRemoved 102357 -
    2020-12-01 mmuetzel StatusNeed Info None
        Release5.1.0 6.1.0
    2019-10-03 jimfitchusa Carbon-Copy- Added jimfitchusa
    2019-07-12 mmuetzel Dependencies- bugs #56617 is dependent
    2019-05-31 stromi Carbon-Copy- Added stromi
    2019-04-25 mtmiller Dependencies- bugs #56209 is dependent
    2019-04-02 mtmiller Priority5 - Normal 3 - Low
        Item GroupNone Unexpected Error or Warning
        Release4.2.1 5.1.0
    2019-04-02 mtmiller Dependencies- bugs #55897 is dependent
    2019-04-02 rik5 Carbon-CopyRemoved 72865 -
    2019-04-02 mmuetzel Open/ClosedClosed Open
    2019-04-02 tomahola Attached File- Added octave_bug.png, #46694
    2019-03-10 rik5 Open/ClosedOpen Closed
    2019-01-24 mtmiller Carbon-CopyRemoved 80942 -
    2017-07-12 mmuetzel Dependencies- bugs #51446 is dependent
    2017-06-28 mtmiller StatusNone Need Info
    2017-06-23 mtmiller Dependencies- bugs #51301 is dependent

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code