TortoiseHg window opens and close immediately

[Marco Azzalini]

Hi, I am trying to start THG from sources (hg update stable) in my Linux Suse Tumbleweed... it start and the window appear for a millisecond but it ends immediately. I can't find  a log file or similar to identify what could be the problem and I haven't error or messages on console?

Can someone give me an hint ?

My enviroment:

Mercurial SCM  (v 5.5.1)

Python 3.8.5

thanks in advance,

Marco

[Manuel Jacob]

What’s the output if you run "thg --nofork --traceback" in the console?

[Yuya Nishihara]

On Tue, 22 Sep 2020 03:02:06 -0700 (PDT), Marco Azzalini wrote:
> Hi, I am trying to start THG from sources (hg update stable) in my Linux
> Suse Tumbleweed... it start and the window appear for a millisecond but it
> ends immediately. I can't find a log file or similar to identify what
> could be the problem and I haven't error or messages on console?

Try "thg --nofork --debug --traceback" to hopefully get some error messages.

[Yuya Nishihara]

(Please CC the list)

On Tue, 22 Sep 2020 12:23:36 +0200, Marco Azzalini wrote:
> >./thg --nofork --debug --traceback
>
> creating cmdworker 'server'
> opening repo: /home/usr/lavoro/thg
> creating cmdworker 'server'
> add ui file to watcher: /home/marco/.hgrc
> add ui file to watcher: /home/usr/lavoro/thg/.hg/hgrc
> Segmentation fault (core dumped)

Maybe something would go wrong in C++ dependency, namely PyQt5, Qt5,
or QScintilla. Try reinstalling these packages from the distribution
repository.

[Yuya Nishihara]

(Please do not drop the CC: thg...@googlegroups.com)

On Wed, 23 Sep 2020 09:24:05 +0200, Marco Azzalini wrote:
> I found this bug details:
> https://bugs.archlinux.org/task/66887
>
> where is described the very same behavior (python crash after qt5 and
> qscintilla libs upgrade) and where there is also a 'fix'.
> The solution is simple: delete .config/TortoiseHg/TortoiseHgQt.ini file
>
> I did it and now my THG seems works again like before.
>

> P.S: I have saved the previous TortoiseHgQt.ini file if someone would like
> to investigate it

Good catch.

Can you attach the original TortoiseHgQt.ini file? If some history data
can't be made public, please remove them.

[Marco Azzalini]

Hi, sorry for dropping thg-dev address in my previous posts.

Anyway, attached you'll find the two  TortoiseHgQt.ini (the .crash obviously is the guilty ;-)  ) 

hoping that this can help to improve the code ;-)

Marco

--

https://ilmilione.org
----
Anche sogliono essere odiatissimi i buoni e i generosi perché ordinariamente sono sinceri, e chiamano le cose coi loro nomi.
Colpa non perdonata dal genere umano, il quale non odia mai tanto chi fa male, né il male stesso, quanto chi lo nomina. 
                                                           - Leopardi -

[Yuya Nishihara]

On Wed, 23 Sep 2020 15:55:39 +0200, Marco Azzalini wrote:
> Anyway, attached you'll find the two TortoiseHgQt.ini (the .crash
> obviously is the guilty ;-) )

Thanks. I'll try it when Qt/PyQt packages are upgraded to 5.15.x. The problem
couldn't be reproduced on Debian sid, which currently provides Qt 5.14.2.

[aayja...@gmail.com]

(sorry for replying from web interface)

(some additional information) this issue has been reported on the Arch Linux bug
tracker [1]. it seems to be an issue in QScintilla 2.11.4 that has been fixed by
Arch package python-qscintilla-qt5 in 2.11.4-3 [2] and upstream QScintilla in
2.11.5 [3].

[1]: https://bugs.archlinux.org/task/66887
[2]: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/qscintilla&id=9f3a8a39a799bb400d146055e4cbf9f2d23b56b4
[3]: https://www.riverbankcomputing.com/static/Downloads/QScintilla/2.11.5/ChangeLog

[Yuya Nishihara]

Okay, so this problem is tied to very specific QScintilla version, and we
wouldn't have to work around it.

Thanks for the information.