Bug 452424 - Crash on an attempt to save a file
Summary: Crash on an attempt to save a file
Status: RESOLVED WORKSFORME
Alias: None
Product: lokalize
Classification: Applications
Component: general (other bugs)
Version First Reported In: 21.12.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Simon Depiets
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-09 08:02 UTC by Mario Blättermann
Modified: 2026-01-09 11:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mario Blättermann 2022-04-09 08:02:43 UTC
Application: lokalize (21.12.3)

Qt Version: 5.15.3
Frameworks Version: 5.92.0
Operating System: Linux 5.17.1-arch1-1 x86_64
Windowing System: X11
Distribution: EndeavourOS
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
Immediately after completing the translation of a gettext message, I tried to save the .po file, but Lokalize crashed. After restarting it, it obviously shows the recently changed gettext messages from an internal backup, and I'm able to save my work.

I'm unsure if this crash is really reproducible. Well, such crashes happen very often, but I don't know whether for the same reason. But especially with very big files (> 1000 gettext messages), Lokalize is very sensitive. Then it is almost impossible to work without saving the file after each translated message.

-- Backtrace:
Application: Lokalize (lokalize), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f713f5dee6a in QSortFilterProxyModel::parent(QModelIndex const&) const () from /usr/lib/libQt5Core.so.5
#5  0x0000561d097a1aa0 in ?? ()
#6  0x00007f713f6297d6 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#7  0x00007f71401631c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#8  0x00007f713f6055aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#9  0x00007f713f6060a9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#10 0x00007f713f64d678 in ?? () from /usr/lib/libQt5Core.so.5
#11 0x00007f713da03163 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#12 0x00007f713da599e9 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x00007f713da006c5 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#14 0x00007f713f65157a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#15 0x00007f713f5fd88b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#16 0x00007f713f608fd7 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#17 0x0000561d096f8ca6 in ?? ()
#18 0x00007f713ee16310 in __libc_start_call_main () from /usr/lib/libc.so.6
#19 0x00007f713ee163c1 in __libc_start_main_impl () from /usr/lib/libc.so.6
#20 0x0000561d096f9a45 in _start ()
[Inferior 1 (process 4602) detached]
Comment 1 Finley Watson 2025-12-10 01:52:34 UTC
Are you still experiencing frequent crashes like this?
Comment 2 Bug Janitor Service 2025-12-25 03:46:30 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2026-01-09 03:47:11 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
Comment 4 Mario Blättermann 2026-01-09 10:56:55 UTC
Sorry for the horrible delay... I was pretty busy with other thingds.
Indeed, it works again. Some months ago, I switched from Arch to Fedora, and since then, it never happned again, even wirh very huge files (> 6000 messages). By the way, under Fedora I use Wayland instead of Xorg, maybe this was the reason...?
Comment 5 Finley Watson 2026-01-09 11:04:15 UTC
no problem, thanks for the update! feel free to reopen if you have the issue again.