Summary: | akkregator crash when Kontact is closed | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Julian Schmidt <julian> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | imurzich |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Julian Schmidt
2015-11-04 13:26:58 UTC
Created attachment 95451 [details]
New crash information added by DrKonqi
kontact (5.0.2) using Qt 5.4.2
I read RSS feeds and E-Mail. When I read RSS I opened links in the external browser. After this, when I closed Kontact the error occured.
-- Backtrace (Reduced):
#6 QString::QString (other=..., this=this@entry=0x7fffb4bb8b10) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:811
#7 Akregator::SearchBar::text (this=0x2b7b8b0) at ../../../akregator/src/searchbar.cpp:125
#8 0x00007f80f1189f4f in Akregator::MainWidget::saveProperties (this=0x2b507a0, config=...) at ../../../akregator/src/mainwidget.cpp:1183
#9 0x00007f80f11840b4 in Akregator::Part::autoSaveProperties (this=this@entry=0x2b26b50) at ../../../akregator/src/akregator_part.cpp:871
#10 0x00007f80f1184149 in Akregator::Part::slotOnShutdown (this=this@entry=0x2b26b50) at ../../../akregator/src/akregator_part.cpp:349
Git commit 0cdf18e32555b8fe63ebe3a752a5a3c3df9afbc2 by Montel Laurent. Committed on 12/11/2015 at 21:15. Pushed by mlaurent into branch 'master'. Try to fix Bug 354832 - akkregator crash when Kontact is closed M +6 -3 akregator/src/akregator_part.cpp M +1 -1 akregator/src/akregator_part.h http://commits.kde.org/kdepim/0cdf18e32555b8fe63ebe3a752a5a3c3df9afbc2 This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input. |