octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: dev (gui) build does not start on kubuntu 13.04


From: Torsten
Subject: Re: dev (gui) build does not start on kubuntu 13.04
Date: Mon, 19 Aug 2013 19:39:36 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8

On 19.08.2013 18:24, Daniel J Sebald wrote:
> On 08/19/2013 03:00 AM, Torsten wrote:
>> On 18.08.2013 22:58, Kirill Fuior wrote:
>>> I've tried to delete all content of this file and then start octave
>>> again, but it didn't help.
>>> But octave has wrote something to this file (attached --
>>> qt-settings_new).
>>
>> Are you sure that qt-settings_new is the file that octave rewrites when
>> it starts with an empty qt-settings file? Most of the entries in
>> qt-settings_new can not be written when octave crashes and does not exit
>> in a normal way. Instead, the few entries in your attached qt-settings
>> file are actually written at startup and from this it seems that
>> creating the editor widget might be the problem. I will have a look at
>> this tonight.
> 
> Are you thinking that because these settings
> 
> address@hidden()
> address@hidden()
> 
> still say Invalid that the editor widget isn't working properly? Perhaps
> QSci is missing from Kirill's system.

@Invalid() is okay for empty string lists in the settings but one of
Kirill's settings file is empty except for:

[DockWidgets]
TerminalDockWidget_floating_geometry= ...
HistoryDockWidget_floating_geometry= ...
FilesDockWidget_floating_geometry= ...
DocumentationDockWidget_floating_geometry= ...

I guess this file is the one that was written during the test with an
empty settings file. AFAIK the xxxxx_floating_geometry are the only
settings that can be written during startup. The next dock widget would
have been the editor (see dock_widget_list () in main-window.h).

Well, I just see that this would mean the crash occurs when settings the
editor's window properties not when construction the editor ...

Torsten



reply via email to

[Prev in Thread] Current Thread [Next in Thread]