| Summary: | Rescan of translation memory never finishes in the GUI | ||
|---|---|---|---|
| Product: | [Applications] lokalize | Reporter: | Frank Steinmetzger <dev+kde> |
| Component: | translation memory | Assignee: | Simon Depiets <sdepiets> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | fin-w, kishore96, shafff, vit |
| Priority: | NOR | ||
| Version First Reported In: | 21.12.3 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/sdk/lokalize/-/commit/aa584b665bb2c0d8bf8468dbc704dab66f236e05 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
Frank Steinmetzger
2022-03-13 17:39:25 UTC
*** Bug 483406 has been marked as a duplicate of this bug. *** Setting to confirmed as this exists in version 24.02.0 as well (see duplicate bug report). Git commit ac2efe7a07263e6708073bea78851918b4541d46 by Albert Astals Cid. Committed on 25/08/2024 at 10:48. Pushed by aacid into branch 'master'. Fix Translation Memory import job not finishing The fix is two-fold: * We need to call deleteLater on the subjobs so they are actually destroed * There's two places that create ScanJobFeedingBack jobs but only one of them connected to the destroyed signal, add it to the other one M +6 -6 src/tm/tmscanapi.cpp https://invent.kde.org/sdk/lokalize/-/commit/ac2efe7a07263e6708073bea78851918b4541d46 Git commit aa584b665bb2c0d8bf8468dbc704dab66f236e05 by Albert Astals Cid. Committed on 27/08/2024 at 20:22. Pushed by aacid into branch 'release/24.08'. Fix Translation Memory import job not finishing The fix is two-fold: * We need to call deleteLater on the subjobs so they are actually destroed * There's two places that create ScanJobFeedingBack jobs but only one of them connected to the destroyed signal, add it to the other one (cherry picked from commit ac2efe7a07263e6708073bea78851918b4541d46) M +6 -6 src/tm/tmscanapi.cpp https://invent.kde.org/sdk/lokalize/-/commit/aa584b665bb2c0d8bf8468dbc704dab66f236e05 *** Bug 491782 has been marked as a duplicate of this bug. *** |