Created attachment 107876 [details] Debugging of trojita - full backtrace of all threads Hi! I am using the latest trojita version on linux debian jessie. I have a problem with updating my addressbook. The scenario I can reproduce everytime is the following: - Launch trojita - Insert password (or continue without it) - Open addressbook - Set filter, that only one contact match (when more items are displayed, it works) - Update phone number (or other columns) - Try to set other filter --> Segmentation fault Versions: Trojita - last build from master commit 55666e70e2fce1553feaac8931710c5028960118 Author: l10n daemon script <scripty@kde.org> Date: Mon Sep 11 03:15:08 2017 +0200 Qt - version 5.3.2+dfsg-4+deb8u2 Debugger output is in the attachment.. If something more is needed to find the problem, do not hasitate to ask. Regards, Richard Eliáš
Not reproducible here (you're aware that your Qt version is slightly dated?) "Try to set other filter" How in particular? The backtrace sugests the removal of another (the last?) index, ie. do you need to alter the filter to something "invalid", do you simply clear it, just pass focus to the filter lineedit, ...?
Created attachment 107883 [details] Changing filter Ok, Set other filter = Double click on text in filter and type another word - by pressing first letter, trojita crashed... Screenshot of situation is attached..
Same is happening after update to debian 9 (stretch). Versions of libraries: QT: qt5-default: 5.7.1+dfsg-3+b1 Trojita: commit e5ac7890ad09d2bd71c75ede421860b99e02290b Merge: 55666e70 71878b21 Author: Jan Kundrát <jkt@kde.org> Date: Mon Sep 18 16:00:54 2017 +0200 Logs are attached.
Created attachment 108490 [details] Debugging of trojita - full backtrace of all threads - debian stretch Backtrace when segfault happened
It looks like D-Bus is used from a secondary thread. Not sure if this is supported by Qt.
Thank you for the report, Richard. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Hi, Yes, the scenario works well..