Re: [hugin-ptx] Re: Hugin 2019 crash at startup

2019-05-03 Thread Greg 'groggy' Lehey
On Friday, 3 May 2019 at 20:11:23 +0200, giuseppe porciani wrote: > 2019-05-03 8:52 GMT+02:00, T. Modes : >> Am Montag, 29. April 2019 09:57:51 UTC+2 schrieb Groogle: >>> (hugin:6057): Gtk-WARNING **: 19:18:30.940: gtk_window_present_with_time() >>> should not be called with 0, or GDK_CURRENT_

Re: [hugin-ptx] Re: Hugin 2019 crash at startup

2019-05-03 Thread Greg 'groggy' Lehey
On Thursday, 2 May 2019 at 23:52:24 -0700, T. Modes wrote: > Am Montag, 29. April 2019 09:57:51 UTC+2 schrieb Groogle: >> >> (hugin:6057): Gtk-WARNING **: 19:18:30.940: gtk_window_present_with_time() >> should not be called with 0, or GDK_CURRENT_TIME as a timestamp, the >> timestamp >> sho

Re: [hugin-ptx] Re: Hugin 2019 crash at startup

2019-05-03 Thread giuseppe porciani
Thank you very much! Giuseppe https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"; target="_blank">https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"; alt="" width="46" height="2

[hugin-ptx] Re: Hugin 2019 crash at startup

2019-05-02 Thread T. Modes
Am Montag, 29. April 2019 09:57:51 UTC+2 schrieb Groogle: > > > (hugin:6057): Gtk-WARNING **: 19:18:30.940: > gtk_window_present_with_time() > should not be called with 0, or GDK_CURRENT_TIME as a timestamp, the > timestamp > should instead be gathered at the time the user initiated the