[Top][All Lists]

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

Re: Octave over ssh

From: Rik
Subject: Re: Octave over ssh
Date: Wed, 27 Nov 2013 08:24:27 -0800

On 11/27/2013 07:29 AM, address@hidden wrote:
> Message: 6
> Date: Wed, 27 Nov 2013 10:27:46 -0500
> From: "John W. Eaton" <address@hidden>
> To: octave maintainers mailing list <address@hidden>
> Cc: address@hidden
> Subject: Qt/gtk style difference with local vs. ssh connection
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
> When I start the Octave GUI I get something that looks like the first
> attached screenshot.  I'm using gnome on a Debian system and this is
> the theme I expect.  If I first ssh -X localhost and then start
> Octave, I get the window theme shown in the second attached
> screenshot.  I don't understand the difference, or how to avoid it.
> Searching the web tells me that I should ensure that the configuration
> files are installed on both systems.  But In both cases, I'm logged in
> to the same account on the same system, so exactly the same set of
> configuration files are present in both cases.  And if I use strace to
> watch what files are opened, I see that the Octave process running
> over the ssh connection is not even attempting to open any gtk
> configuration files.
> Hmm.
> OK, I compared the environments and the ssh connection did not have
> DESKTOP_ENVIRONMENT=gnome.  If I export that setting, then I get
> something that looks like the third attached screenshot.  At least
> that is using the theme I expect, but the layout is not identical to
> what I see when I run Octave locally (there is extra space around the
> text box that displays the warning message).
> Does anyone have a clue about what could cause this difference in the
> layout?
> Could someone check whether there is a similar problem for KDE users?

It works for me with KDE.  That might just be coincidence, but it could
also be that KDE just plays nicely with Qt apps since it uses Qt itself.

> I'm not sure whether Octave itself can do anything about this problem,
> but we could at least document it.
> jwe

reply via email to

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