Bug#848102: [octave] crashed with some random typing in octave editor

[Lumin]

On Thu, 1 Feb 2018 at 11:17 Mike Miller  wrote:

> On Wed, Dec 14, 2016 at 06:44:53 +, lumin wrote:
> > Randomly typing something in octave editor will cause
> > a crash with SIGSEGV.
> >
> > For example, I launched Octave and typed merely "asdfasdf"
> > and then octave crashed.
>
> Can you please try with the version of octave currently in testing?


I’m on unstable. I tried octave 4.2.1-5 (unstable) and the issue refers
By this bug no longer exists. Since the octave version in testing
Is the same, I think that should be ok too.


> Since this was reported, Octave now uses Qt 5 and it's possible that
> this bug only affects an older set of Qt and/or QScintilla libs.
>
> I used to be able to trigger a similar bug by installing qt-at-spi and
> setting the QT_ACCESSIBILITY environment variable. But as I understand
> it the Qt 5 a11y support has been redesigned.
>
> If octave still crashes for you, please provide your locale, keyboard
> layout, and any input method settings.


Thank you, this problem is resolved. I cannot crash octave editor by
The same way.


> --
> mike
>
-- 
Best,

Bug#848102: [octave] crashed with some random typing in octave editor

[Mike Miller]

On Wed, Dec 14, 2016 at 06:44:53 +, lumin wrote:
> Randomly typing something in octave editor will cause
> a crash with SIGSEGV.
> 
> For example, I launched Octave and typed merely "asdfasdf"
> and then octave crashed.

Can you please try with the version of octave currently in testing?
Since this was reported, Octave now uses Qt 5 and it's possible that
this bug only affects an older set of Qt and/or QScintilla libs.

I used to be able to trigger a similar bug by installing qt-at-spi and
setting the QT_ACCESSIBILITY environment variable. But as I understand
it the Qt 5 a11y support has been redesigned.

If octave still crashes for you, please provide your locale, keyboard
layout, and any input method settings.

-- 
mike


signature.asc
Description: PGP signature

Bug#848102: [octave] crashed with some random typing in octave editor

[Ed Peguillan III]

I confirm this issue. Typing in the editor causes octave to exit "with 
signal 11." I was able to stop it from crashing by disabling one or more 
text autocompletion features in preferences.


Menu: Edit -> Preferences... -> Editor -> Autocompletion

I just unchecked everything in that section, and it seems not to crash 
anymore.


Ed

On Wed, 14 Dec 2016 06:44:53 + lumin  wrote:
> Package: octave
> Version: 4.2.0-1
> Severity: normal
>
> Hi,
>
> Randomly typing something in octave editor will cause
> a crash with SIGSEGV.
>
> For example, I launched Octave and typed merely "asdfasdf"
> and then octave crashed.
>
> (gdb) run
> Starting program: /usr/bin/octave
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library 
"/lib/x86_64-linux-gnu/libthread_db.so.1".

> Gtk-Message: Failed to load module "canberra-gtk-module"
> octave exited with signal 11
> [Inferior 1 (process 12389) exited normally]
> (gdb)
>
>

Bug#848102: [octave] crashed with some random typing in octave editor

[lumin]

Package: octave
Version: 4.2.0-1
Severity: normal

Hi,

Randomly typing something in octave editor will cause
a crash with SIGSEGV.

For example, I launched Octave and typed merely "asdfasdf"
and then octave crashed.

(gdb) run
Starting program: /usr/bin/octave 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Gtk-Message: Failed to load module "canberra-gtk-module"
octave exited with signal 11
[Inferior 1 (process 12389) exited normally]
(gdb)