Bug 603476

Created attachment 423622 [details]
Backtrace

*** Bug 603469 has been marked as a duplicate of this bug. ***

Is octave crashes when running from console (without qtoctave)?
Is it crashes if octave-forge not installed?

Is octave crashes when running from console (without qtoctave)?
- No, it doesn't. It runs fine without any crash.

Is it crashes if octave-forge not installed? 
- No, it doesn't.

I erased octave-forge and found that QtOctave is *not* crashing.
I again installed octave-forge and now its *crashing* again.

Can you try to run qtoctave with clean ~/.qtoctave config dir?

Reassigning this bug to octave-forge.

Yes, when I try to run QtOctave with clean ~/.qtoctave dir, there is *no crash* anymore.

(In reply to comment #7)
> Yes, when I try to run QtOctave with clean ~/.qtoctave dir, there is *no crash*
> anymore.    

No crash even with octave-forge installed?  If so, then this bug can be closed.

(In reply to comment #8)
> (In reply to comment #7)
> > Yes, when I try to run QtOctave with clean ~/.qtoctave dir, there is *no crash*
> > anymore.    
> 
> No crash even with octave-forge installed?  If so, then this bug can be closed.    

Crash happens at second qtoctave start after cleaning ~/.qtoctave dir (I guess  may be some additional parameters passed to octave at second start).

(In reply to comment #8)
> (In reply to comment #7)
> > Yes, when I try to run QtOctave with clean ~/.qtoctave dir, there is *no crash*
> > anymore.    
> 
> No crash even with octave-forge installed?  If so, then this bug can be closed.    

let me clear the scenario :

1. I clean ~/.qtoctave dir
2. Run QtOctave
3. No crash
4. But this run created some files in dir

Now I keep the ~/.qtoctave dir as it is (*not* cleaning the content)
i.e. this is the second run.
Here QtOctave *crashes*.

So as pointed out by nucleo, something from ~/.qtoctave dir must be interfering causing Octave to crash. 

I found that cleaning the whole directory is not required. I can simply run 'clear all' from QtOctave terminal and then next time I run QtOctave, it wont crash. But again if I run QtOctave for next time (without using 'clear all' before closing), it will crash.

So I think it has something to do with .variables file.

This might be the same as, or related to, bug #562276.  Can you try to leave octave-forge installed, but disable the "ann" package.  The way I did this was move all the ann-1.0.2 subdirectories:

rpm -ql octave-forge|grep ann-
/usr/libexec/octave/packages/ann-1.0.2
/usr/libexec/octave/packages/ann-1.0.2/x86_64-redhat-linux-gnu-api-v37
/usr/libexec/octave/packages/ann-1.0.2/x86_64-redhat-linux-gnu-api-v37/PKG_ADD
/usr/libexec/octave/packages/ann-1.0.2/x86_64-redhat-linux-gnu-api-v37/ann.oct
/usr/share/octave/packages/ann-1.0.2
/usr/share/octave/packages/ann-1.0.2/packinfo
/usr/share/octave/packages/ann-1.0.2/packinfo/.autoload
/usr/share/octave/packages/ann-1.0.2/packinfo/COPYING
/usr/share/octave/packages/ann-1.0.2/packinfo/ChangeLog
/usr/share/octave/packages/ann-1.0.2/packinfo/DESCRIPTION
/usr/share/octave/packages/ann-1.0.2/packinfo/INDEX
/usr/share/octave/packages/ann-1.0.2/packinfo/dist_admin
/usr/share/octave/packages/ann-1.0.2/packinfo/on_uninstall.m

into disabled subdirectories, i.e.:

$ cd /usr/libexec/octave/packages/
$ sudo mkdir disabled
$ mv -i ann-1.0.2 disabled/

etc.  then I modified (after taking a backup) /usr/share/octave/octave_packages to remove references to the ann package.  This seemed to disable the ann package and I could not duplicate the bug using the method described in bug #562276 comment #10.

Make sure you do all this from plain octave terminal initially.  Then try to duplicate within qtoctave.

Yes, now the qtoctave is *not* crashing anymore.

Keeping octave-forge installed, I disabled the ann package. 
And now it works without any crash or not even one 'mark_as_xxxxx deprecated' warning

*** This bug has been marked as a duplicate of bug 562276 ***