don't know if you finally found the reason of the warning message you
mentioned back in july. On a freshly built Debian stretch virtual
machine I have the same issue today :
** (wxgui.py:5023): WARNING **: invalid source position for vertical
gradient
I guess it is not a fatal issue as GRASS seems to work nicely despite
this error.
Best,
Vincent.
Le samedi 08 juillet 2017 à 12:01 -0700, Helmut Kudrnovsky a écrit :
On Wed, Sep 20, 2017 at 9:06 AM, Vincent Bain <bain@toraval.fr> wrote:
Hi Helmut,
don't know if you finally found the reason of the warning message you
mentioned back in july. On a freshly built Debian stretch virtual
machine I have the same issue today :
** (wxgui.py:5023): WARNING **: invalid source position for vertical
gradient
I guess it is not a fatal issue as GRASS seems to work nicely despite
this error.
Searching the error in internet I found a similar one:
unfortunately I don't have any idea where to find the relevant piece of
code implied.
Vincent.
Le mercredi 20 septembre 2017 à 10:23 +0200, Markus Neteler a écrit :
On Wed, Sep 20, 2017 at 9:06 AM, Vincent Bain <bain@toraval.fr> wrote:
> Hi Helmut,
>
> don't know if you finally found the reason of the warning message you
> mentioned back in july. On a freshly built Debian stretch virtual
> machine I have the same issue today :
>
>
> ** (wxgui.py:5023): WARNING **: invalid source position for vertical
> gradient
>
> I guess it is not a fatal issue as GRASS seems to work nicely despite
> this error.
Searching the error in internet I found a similar one:
You would need to isolate which part of the GUI is responsible for it, otherwise there is too many options to guess. If this started recently, maybe you can isolate the commit, that would help too.
Anna
···
On Sep 20, 2017 4:59 AM, “Vincent Bain” <bain@toraval.fr> wrote:
Thank you Markus for your suggestion,
unfortunately I don’t have any idea where to find the relevant piece of
code implied.
Vincent.
Le mercredi 20 septembre 2017 à 10:23 +0200, Markus Neteler a écrit :
On Wed, Sep 20, 2017 at 9:06 AM, Vincent Bain <bain@toraval.fr> wrote:
Hi Helmut,
don’t know if you finally found the reason of the warning message you
mentioned back in july. On a freshly built Debian stretch virtual
machine I have the same issue today :
** (wxgui.py:5023): WARNING **: invalid source position for vertical
gradient
I guess it is not a fatal issue as GRASS seems to work nicely despite
this error.
Searching the error in internet I found a similar one:
the messages pops up in the terminal when I interact with the layer
manager window like : swithching between thumbnail, resizing window,
confirming deletion of a map).
after digging it a little bit deeper, I guess it has rather something to
do with the environment : I currently work on different debian machines;
the issue happens when I build the latest trunk version (r:71500) on a
new/clean debian 9 (stretch). Building the same release on my old debian
8 works fine.
I have several concurrent python versions on my old machine I switch
with update-alternative, but I am not sure about which version GRASS is
built against on each machine...
Vincent.
Le mercredi 20 septembre 2017 à 07:06 -0400, Anna Petrášová a écrit :
You would need to isolate which part of the GUI is responsible for it,
otherwise there is too many options to guess. If this started
recently, maybe you can isolate the commit, that would help too.
Anna
On Sep 20, 2017 4:59 AM, "Vincent Bain" <bain@toraval.fr> wrote:
Thank you Markus for your suggestion,
unfortunately I don't have any idea where to find the relevant
piece of
code implied.
Vincent.
Le mercredi 20 septembre 2017 à 10:23 +0200, Markus Neteler a
écrit :
> On Wed, Sep 20, 2017 at 9:06 AM, Vincent Bain
<bain@toraval.fr> wrote:
> > Hi Helmut,
> >
> > don't know if you finally found the reason of the warning
message you
> > mentioned back in july. On a freshly built Debian stretch
virtual
> > machine I have the same issue today :
> >
> >
> > ** (wxgui.py:5023): WARNING **: invalid source position
for vertical
> > gradient
> >
> > I guess it is not a fatal issue as GRASS seems to work
nicely despite
> > this error.
>
> Searching the error in internet I found a similar one:
>
> ** (thunar:2530): WARNING **: invalid source position for
vertical gradient
> https://github.com/lassekongo83/zuki-themes/issues/104
>
> Fix:
> https://github.com/lassekongo83/zuki-themes/commit/318efd3a83f6305414f58b9dca417072c16e5ef6
>
> Maybe something like this could be applied also here?
>
> Markus
On Wed, Sep 20, 2017 at 2:01 PM, Vincent Bain <bain@toraval.fr> wrote:
...
after digging it a little bit deeper, I guess it has rather something to
do with the environment : I currently work on different debian machines;
the issue happens when I build the latest trunk version (r:71500) on a
new/clean debian 9 (stretch). Building the same release on my old debian
8 works fine.
Please check the wxPython version, through g.gui > Help > About system
On another hand, trying to find out what was new between debian 9.0 and
debian 8.8 configurations, I noticed there was a difference concerning
wx-config alternatives:
- in the former it pointed towards
/usr/lib/i386-linux-gnu/wx/config/base-unicode-3.0
- while in the newer it points toward
/usr/lib/i386-linux-gnu/wx/config/gtk2-unicode-3.0
I tried to rebuild (after a distclean) with the previous configuration,
i.e. base-unicode-3.0
$ update-alternatives --config wx-config
but the error still rises.
Perhaps I should try to revert to wxPython 3.0.1.1
Vincent.
Le mercredi 20 septembre 2017 à 15:23 +0200, Markus Neteler a écrit :
On Wed, Sep 20, 2017 at 2:01 PM, Vincent Bain <bain@toraval.fr> wrote:
...
> after digging it a little bit deeper, I guess it has rather something to
> do with the environment : I currently work on different debian machines;
> the issue happens when I build the latest trunk version (r:71500) on a
> new/clean debian 9 (stretch). Building the same release on my old debian
> 8 works fine.
Please check the wxPython version, through g.gui > Help > About system
As Robert asked, is there a way to set, at least temporarily, the
verbosity of these messages ?
V.
Le mercredi 20 septembre 2017 à 15:44 +0200, Vincent Bain a écrit :
wxPython: 3.0.2.0
My old debian 8.8 install has wxPython: 3.0.1.1
On another hand, trying to find out what was new between debian 9.0 and
debian 8.8 configurations, I noticed there was a difference concerning
wx-config alternatives:
- in the former it pointed towards
/usr/lib/i386-linux-gnu/wx/config/base-unicode-3.0
- while in the newer it points toward
/usr/lib/i386-linux-gnu/wx/config/gtk2-unicode-3.0
I tried to rebuild (after a distclean) with the previous configuration,
i.e. base-unicode-3.0
$ update-alternatives --config wx-config
but the error still rises.
Perhaps I should try to revert to wxPython 3.0.1.1
Vincent.
Le mercredi 20 septembre 2017 à 15:23 +0200, Markus Neteler a écrit :
> On Wed, Sep 20, 2017 at 2:01 PM, Vincent Bain <bain@toraval.fr> wrote:
> ...
> > after digging it a little bit deeper, I guess it has rather something to
> > do with the environment : I currently work on different debian machines;
> > the issue happens when I build the latest trunk version (r:71500) on a
> > new/clean debian 9 (stretch). Building the same release on my old debian
> > 8 works fine.
>
> Please check the wxPython version, through g.gui > Help > About system
>
> Markus
As Robert asked, is there a way to set, at least temporarily, the
verbosity of these messages ?
not easily I think, maybe if you recompile some of the underlying
libraries and set somehow their verbosity, it would be theoretically
possible, but I didn't investigate that option.
V.
Le mercredi 20 septembre 2017 à 15:44 +0200, Vincent Bain a écrit :
wxPython: 3.0.2.0
My old debian 8.8 install has wxPython: 3.0.1.1
On another hand, trying to find out what was new between debian 9.0 and
debian 8.8 configurations, I noticed there was a difference concerning
wx-config alternatives:
- in the former it pointed towards
/usr/lib/i386-linux-gnu/wx/config/base-unicode-3.0
- while in the newer it points toward
/usr/lib/i386-linux-gnu/wx/config/gtk2-unicode-3.0
I tried to rebuild (after a distclean) with the previous configuration,
i.e. base-unicode-3.0
$ update-alternatives --config wx-config
but the error still rises.
Perhaps I should try to revert to wxPython 3.0.1.1
Vincent.
Le mercredi 20 septembre 2017 à 15:23 +0200, Markus Neteler a écrit :
> On Wed, Sep 20, 2017 at 2:01 PM, Vincent Bain <bain@toraval.fr> wrote:
> ...
> > after digging it a little bit deeper, I guess it has rather something to
> > do with the environment : I currently work on different debian machines;
> > the issue happens when I build the latest trunk version (r:71500) on a
> > new/clean debian 9 (stretch). Building the same release on my old debian
> > 8 works fine.
>
> Please check the wxPython version, through g.gui > Help > About system
>
> Markus
It might not be specifically a GRASS issue. Changing the gtk+ theme
engine of my desktop from Adwaita to Clearlooks solved the problem in
one go, no more warnings... did not look attentively but it seems
adwaita was the only problematic theme (I mean among those installed
down here).
Hope this instant of serendipity can help you find a cure to this buggy
behavior !
Yours,
Vincent.
Le mercredi 20 septembre 2017 à 10:44 -0400, Anna Petrášová a écrit :
On Wed, Sep 20, 2017 at 10:39 AM, Vincent Bain <bain@toraval.fr> wrote:
> looks like this problem appeared some time ago :
>
> https://lists.osgeo.org/pipermail/grass-user/2016-August/074641.html
>
> As Robert asked, is there a way to set, at least temporarily, the
> verbosity of these messages ?
>
not easily I think, maybe if you recompile some of the underlying
libraries and set somehow their verbosity, it would be theoretically
possible, but I didn't investigate that option.
>
> V.
>
> Le mercredi 20 septembre 2017 à 15:44 +0200, Vincent Bain a écrit :
>> wxPython: 3.0.2.0
>>
>> My old debian 8.8 install has wxPython: 3.0.1.1
>>
>> On another hand, trying to find out what was new between debian 9.0 and
>> debian 8.8 configurations, I noticed there was a difference concerning
>> wx-config alternatives:
>>
>> - in the former it pointed towards
>> /usr/lib/i386-linux-gnu/wx/config/base-unicode-3.0
>> - while in the newer it points toward
>> /usr/lib/i386-linux-gnu/wx/config/gtk2-unicode-3.0
>>
>> I tried to rebuild (after a distclean) with the previous configuration,
>> i.e. base-unicode-3.0
>>
>> $ update-alternatives --config wx-config
>>
>> but the error still rises.
>>
>> Perhaps I should try to revert to wxPython 3.0.1.1
>>
>>
>>
>> Vincent.
>>
>> Le mercredi 20 septembre 2017 à 15:23 +0200, Markus Neteler a écrit :
>> > On Wed, Sep 20, 2017 at 2:01 PM, Vincent Bain <bain@toraval.fr> wrote:
>> > ...
>> > > after digging it a little bit deeper, I guess it has rather something to
>> > > do with the environment : I currently work on different debian machines;
>> > > the issue happens when I build the latest trunk version (r:71500) on a
>> > > new/clean debian 9 (stretch). Building the same release on my old debian
>> > > 8 works fine.
>> >
>> > Please check the wxPython version, through g.gui > Help > About system
>> >
>> > Markus
>>
>>
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev