Summary: | Cannot acces the translation memory after a second launch of Lokalize | ||
---|---|---|---|
Product: | [Applications] lokalize | Reporter: | Dimitrios Glentadakis <dglent> |
Component: | translation memory | Assignee: | Simon Depiets <sdepiets> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | shafff |
Priority: | NOR | ||
Version: | 19.04.0 | ||
Target Milestone: | --- | ||
Platform: | Mageia RPMs | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/sdk/lokalize/commit/8ce6b3d89598b6bc7570d11e7063b08394b3c0c9 | Version Fixed In: |
Description
Dimitrios Glentadakis
2020-05-30 05:29:22 UTC
Desktop environement: LXQt 0.15.0 Qt : 5.12.6 KDE Framework : lib64kf5plasma5-5.57.0-1.mga7 plasma-framework-5.57.0-1.mga7 Git commit 8ce6b3d89598b6bc7570d11e7063b08394b3c0c9 by Simon Depiets. Committed on 14/06/2020 at 03:16. Pushed by sdepiets into branch 'master'. Use thread specific names for connection Names There seems to have been two issues with TM connections. The first was that the TM connection was closed on project change (while they are actually all opened for stats purposes). The second was that the connection names where not thread specific, which could cause issues, and it will now be the case. Related: bug 416427 M +4 -2 src/project/project.cpp M +41 -27 src/tm/jobs.cpp https://invent.kde.org/sdk/lokalize/commit/8ce6b3d89598b6bc7570d11e7063b08394b3c0c9 I have made some changes in the handling of TM connections, could you build from master and give it a try ? It works ok now Thank you! |