Am 11.06.2018 um 11:02 schrieb Sven Schreiber:
Am 11.06.2018 um 10:56 schrieb Allin Cottrell:
> On Mon, 11 Jun 2018, Sven Schreiber wrote:
>
>> Am 11.06.2018 um 09:39 schrieb Sven Schreiber:
>>>
>>> on Ubuntu with yesterday's git version I'm noticing that "quite
>>> often" the menus are not responding anymore (not clickable). It
>>> seems to happen when a script terminates with an error, but not
>>> 100% sure about that.
>>>
>> I take that back, it also happens without a script error. (maybe
>> running a script per se)
>
> A time-consuming script can of course preempt resources and slow down
> or even disable menu access for a while. I guess that's not what you
> mean?
No, the script is small and finishes quickly.
> Nothing has changed lately in the GUI code, apart from adding syntax
> highlighting for the console, so I don't know what's going on here.
OK.
To clarify: Only the menus of the main window are affected, not the
clickable buttons in any window. Context menu (right-click on a
series) also works.
>
> I do know, however, that Ubuntu does some very idiosyncratic things
> in relation to the GUI in general and GTK in particular. To avoid
> severe breakage to gretl under Ubuntu we have a "trick" in place,
> namely putting UBUNTU_MENUPROXY=0 into the environment at start-up. I
> guess it's possible that this trick (which dates back a few years)
> has somehow rotted due to changes in the OS.
Artur, you're a long-time Ubuntu user I think. Have you noticed anything?
(I'm running gretl in German, I think Artur does it in English.)
Hi Sven,
no I haven't noticed anything on my Ubuntu machine. However, I should
add that I am mainly using the Budgie Desktop and on another machine the
Lubuntu (LXDE) environment. Yes, I am using gretl in English.
Best,
Artur