bugGNU Octave - Bugs: bug #42133, Array/vector generator failure...

 
 

bug #42133: Array/vector generator failure [0:0.01:0.98]

Submitter:  None
Submitted:  Thu 17 Apr 2014 09:35:35 AM UTC
   
 
Category:  Interpreter Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Incorrect Result
Status:  Works For Me Assigned to:  None
Originator Name:  Lulamile Mzamo Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * 3.8.1
Operating System:  * GNU/Linux Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sat 19 Apr 2014 04:20:22 PM UTC, comment #13: 

I can't reproduce this particular problem on either Debian or Ubuntu desktops with qt-at-spi installed and enabled. I do see the extra "Debug" messages in the command window when Octave starts, indicating that the component is doing something, but I don't see the empty range behavior reported here.

And yes, qt-at-spi is installed by default for Ubuntu Unity and Kubuntu desktop installs and possibly enabled by default, I can't tell right now.

Mike Miller <mtmiller>
Group Member
Fri 18 Apr 2014 07:22:37 PM UTC, comment #12: 

Unknown, I don't know that we know enough about the reason for this problem or the previous one (bug #41552 for reference) to know whether it's something that Octave is doing wrong or a bug in the Qt accessibility plugin.

It is troubling that this comes up a lot from Unity users, I am not sure whether this is enabled by default for all Unity installs, I'll check later. If it is, that's a large potential user base that could have crashes or other weird problems like this one.

I can also try to reproduce this on Debian with qt-at-spi installed, now that we know that it's the culprit for this bug also.

Mike Miller <mtmiller>
Group Member
Fri 18 Apr 2014 07:04:02 PM UTC, comment #11: 

Is this something Octave should do or would that cause other trouble?  Is there some way we can allow QT_ACCESSIBILITY to be set but avoid the problems with input that it seems to cause for Octave's command window?

John W. Eaton <jwe>
Group administrator
Fri 18 Apr 2014 05:32:13 PM UTC, comment #10: 

Unsetting the QT_ACCESSIBILITY environment variable works perfectly.

Thanks.

Lulamile <lulamile>
Fri 18 Apr 2014 03:36:09 PM UTC, comment #9: 

I notice you're using Ubuntu Unity. Does the problem go away if you run octave --force-gui from a terminal with the QT_ACCESSIBILITY environment variable unset? For example:


$ echo $QT_ACCESSIBILITY
$ unset QT_ACCESSIBILITY
$ octave --force-gui


Or if you run the following to disable this for your desktop settings, then log out and log in again:


gsettings set org.gnome.desktop.interface toolkit-accessibility false


This is kind of a longshot, but this was the solution to another bug report that had to do with the Octave GUI on the Ubuntu desktop with a11y enabled. The additional messages you are seeing at startup look like they have to do with the Qt a11y plugin.

Mike Miller <mtmiller>
Group Member
Fri 18 Apr 2014 02:34:44 PM UTC, comment #8: 

I rebooted and tried to repeat the result of the last post. I couldn't.

Lulamile <lulamile>
Fri 18 Apr 2014 02:15:36 PM UTC, comment #7: 

Something odd just happened.

1. I closed Octave GUI, (still keeping the Octave in the terminal open.
2. Then opened the GUI, (still with the Octave non-GUI/terminal open.

*And now its working (see screendump)*
I will reboot and try again.


Lulamile <lulamile>
Fri 18 Apr 2014 02:09:56 PM UTC, comment #6: 

This is happening only in the GUI command window.
I have tried both and it still fails on the GUI Command window.
Please see attached screen dumps.


Lulamile <lulamile>
Fri 18 Apr 2014 01:23:24 PM UTC, comment #5: 

Do you get the same results if you create a one-liner m-file with the same range assignment and run or source it from the command line in the GUI?

Do you get the same results if you copy and paste the range assignment text from this bug report or from a terminal into the GUI command window?

Mike Miller <mtmiller>
Group Member
Fri 18 Apr 2014 07:03:11 AM UTC, comment #4: 

Regarding Installation:
I downloaded octave-3.8.1.tar.bz2 from the ftp site, untarred it and compiled using ./configure the installed using make install

I'm using gcc and g++ v4:4.8.1.

To repeat: This behaviour only happens in GUI mode, NOT in terminal mode.

Lula

Lulamile <lulamile>
Fri 18 Apr 2014 01:45:33 AM UTC, comment #3: 

Problem only in Gui mode. Terminal mode is fine.
Im using 3.8.1 on Ubuntu 13.10.

Lulamile <lulamile>
Thu 17 Apr 2014 11:31:46 PM UTC, comment #2: 

Works for me as well.

I think you should also try running without the '--force-gui' option so we can see whether this is a GUI or Interpreter issue.

Rik <rik5>
Group administrator
Thu 17 Apr 2014 01:39:55 PM UTC, comment #1: 

I'm unable to reproduce this problem.  I think we need more information.

How did you install Octave?

Did you build it from source yourself?  If so, what configure options did you use?  What compiler?

John W. Eaton <jwe>
Group administrator
Thu 17 Apr 2014 09:35:35 AM UTC, original submission:  

The following input returns wrong results when using the GUI, sometimes. Its not consistent because sometimes it works but sometimes not.
a=[0:0.01:0.98] returns a = [](1x0)

Screen dump below:

Debug: Got bus address:  "unix:abstract=/tmp/dbus-45wn9ZnHyl,guid=3c7cab63236071e08643aaeb534f723c"
Debug: Connected to accessibility bus at:  "unix:abstract=/tmp/dbus-45wn9ZnHyl,guid=3c7cab63236071e08643aaeb534f723c"
Debug: Registered DEC:  true
Debug: Registered event listener change listener:  true
GNU Octave, version 3.8.1
Copyright (C) 2014 John W. Eaton and others.
This is free software; see the source code for copying conditions.
There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  For details, type 'warranty'.

Octave was configured for "i686-pc-linux-gnu".

Additional information about Octave is available at http://www.octave.org.

Please contribute if you find this software useful.
For more information, visit http://www.octave.org/get-involved.html

Read http://www.octave.org/bugs.html to learn how to submit bug reports.
For information about changes from previous versions, type 'news'.

>> a = [0:0.01:0.98]

a = [](1x0)

>> a = [0:1:10]

a =

    0    1    2    3    4    5    6    7    8    9   10

>> a = [0:0.01:0.98]

a = [](1x0)

>>



Anonymous

 

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

Attach Files:
   
   
Comment:
   

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by lulamile (Posted a comment)
  • -email is unavailable- added by rik5 (Updated the item)
  • -email is unavailable- added by jwe (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 8 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2014-04-18 rik5 Open/ClosedOpen Closed
    2014-04-18 lulamile Attached File- Added Screenshot from 2014-04-18 16:09:44.png, #31208
    2014-04-18 lulamile Attached File- Added Screenshot from 2014-04-18 16:06:06.png, #31206
        Attached File- Added Screenshot from 2014-04-18 16:06:41.png, #31207
    2014-04-18 lulamile Attached File- Added Screenshot from 2014-04-18 16:00:59.png, #31204
        Attached File- Added Screenshot from 2014-04-18 16:00:49.png, #31205
    2014-04-17 rik5 CategoryGUI Interpreter
        StatusNone Works For Me

    Back to the top

    Powered by Savane 3.13-02a9.
    Corresponding source code