Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
thg
thg
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 788
    • Issues 788
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards

This instance will be upgraded to Heptapod 0.19.0rc2 on 2021-01-18 at 11:00 UTC+1 (a few minutes of downtime)

  • mercurial
  • TortoiseHg
  • thgthg
  • Issues
  • #2071

Closed
Open
Opened Aug 08, 2012 by Bitbucket Importer@bitbucket_importerOwner

crash when pushing with mercurial_keyring

Created originally on Bitbucket by Gurce (Gurce Isikyildiz)

Hi,

I'm on OpenSuse11.4+KDE, using thg-2.4.2. I managed to install the mercurial_keyring add-on, and it pushes fine from the command-line via kde-wallet, but when I try pushing from within thg, it crashes.

It reminds me of a similar issue mentioned at: https://bitbucket.org/tortoisehg/hgtk/issue/1437/gui-freeze-on-suse-linux-after-using

I pondered grafting the patch mentioned there into "backend.py", but it seems as though code similar to that suggested is already in there in the latest keyring code.

There is similar looking error output at the console as was mentioned in that thread too:

{{{ #!python

QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread }}}

I don't know a great deal about python, but I did my best to google around for how to get some sort of trace info.

Via the method mentioned here (which seems to produce a lot of output!): http://stackoverflow.com/questions/2663841/python-tracing-a-segmentation-fault

I managed to capture the activity towards the point of the crash:

line, /home/gurce/tortoisehg-2.4.2/tortoisehg/hgqt/repoview.py:330 line, /home/gurce/tortoisehg-2.4.2/tortoisehg/hgqt/repoview.py:337 QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread return, /home/gurce/tortoisehg-2.4.2/tortoisehg/hgqt/repoview.py:337

Thanks for any help on this.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mercurial/tortoisehg/thg#2071