| Summary: | kontact or akregator crash after close/restart | ||
|---|---|---|---|
| Product: | [Applications] akregator | Reporter: | Michael Kaeck <mkaeck> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | 2357913729, abhshk.btra, ampp.4me, arbedall, arojas, bizyaev, bux23, cruzki123, daniele.fognini, eagle.bugs.kde.org, GrokIt, grosales, igunublue, ivoviniciusspjsl, kaeslaek, kde, kdenis, keplicz, ketelsen.malte, kevin.v, linux, mark_p._sanders, martin.tlustos, Mathias.Homann, metkometko, mfraz74+kde, moltonel, moonwalker, mtijink.bugs, phobian, rb03884, robby.engelmann, ryan, slawek, ultrabla, winter |
| Priority: | VHI | Keywords: | drkonqi |
| Version: | 5.5.2 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/akregator/d0a5f4159cddcca656ca8bbcbd6e551e3499c166 | Version Fixed In: | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
Michael Kaeck
2017-04-06 17:52:32 UTC
According to bug 363899 and bug 364663 this should be fixed in version 5.2.x, but this report (and a duplicate) is from version 5.3.0. *** Bug 354495 has been marked as a duplicate of this bug. *** *** Bug 359180 has been marked as a duplicate of this bug. *** *** Bug 366267 has been marked as a duplicate of this bug. *** *** Bug 372282 has been marked as a duplicate of this bug. *** *** Bug 378256 has been marked as a duplicate of this bug. *** *** Bug 379331 has been marked as a duplicate of this bug. *** *** Bug 381137 has been marked as a duplicate of this bug. *** *** Bug 381221 has been marked as a duplicate of this bug. *** *** Bug 350822 has been marked as a duplicate of this bug. *** *** Bug 381683 has been marked as a duplicate of this bug. *** For me the crash happens absolutely every time I launch Akregator in standalone mode and every time I close Kontact if I launch Akregator as part of Kontact. If I launch Kontact I can see articles in Akregator, but I cannot do anything with them - keyboard shortcuts don't work, context menu doesn't pop up on right-click, going through main application menu all of the items in Article menu are greyed out. If I create a new user account on my machine and start Akregator there it starts fine. In existing account I tried deleting ~/.local/share/akregator and ~/.config/akregatorrc but I still see the same symptoms. The stack trace of the crashing thread in case of closing Kontact is similar: Thread 1 (Thread 0x7f188f794900 (LWP 30706)): [KCrash Handler] #6 0x0000000000000110 in ?? () #7 0x00007f18ac4962b9 in QMetaObject::cast (this=0x7f177e4b71e0 <Akregator::WebEngineFrame::staticMetaObject>, obj=obj@entry=0x1fdc460) at kernel/qmetaobject.cpp:366 #8 0x00007f18ac4962f5 in QMetaObject::cast (this=<optimized out>, obj=obj@entry=0x1fdc460) at kernel/qmetaobject.cpp:355 #9 0x00007f177e25520a in qobject_cast<Akregator::WebEngineFrame*> (object=0x1fdc460) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:514 #10 Akregator::FrameManager::saveProperties (this=0x1e0d800, config=...) at /workspace/build/src/frame/framemanager.cpp:281 #11 0x00007f177e73d53f in Akregator::MainWidget::saveProperties (this=<optimized out>, config=...) at /workspace/build/src/mainwidget.cpp:1237 #12 0x00007f177e736186 in Akregator::Part::autoSaveProperties (this=this@entry=0x1e00130) at /workspace/build/src/akregator_part.cpp:860 #13 0x00007f177e736219 in Akregator::Part::slotOnShutdown (this=0x1e00130) at /workspace/build/src/akregator_part.cpp:394 #14 0x00007f18ac4b93f6 in QtPrivate::QSlotObjectBase::call (a=0x7ffcaa34b430, r=0x1e00130, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #15 QMetaObject::activate (sender=0x7ffcaa34b720, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcaa34b430) at kernel/qobject.cpp:3749 #16 0x00007f18ac4b99d7 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7f18ac74a4a0 <QCoreApplication::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcaa34b430) at kernel/qobject.cpp:3628 #17 0x00007f18ac531fa7 in QCoreApplication::aboutToQuit (this=<optimized out>, _t1=...) at .moc/moc_qcoreapplication.cpp:250 #18 0x00007f18ac48facb in QCoreApplicationPrivate::execCleanup (this=0x1281ba0) at kernel/qcoreapplication.cpp:1311 #19 0x00007f18ac493dcc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1295 #20 0x0000000000404427 in main (argc=1, argv=0x7ffcaa34b878) at /workspace/build/src/main.cpp:227 I think I found what triggers the crash. Akregator doesn't seem to like the Title bar button Menubar style, as soon as I switched from Title bar button to In application Akregator stopped crashing, on switching back to Title bar button it started crashing again with the same stack trace. This finding should help you confirm the bug. I suspect some of the menu code (in particular the article menu) is written in such a way that whenever menubar is disabled that causes a) the article menu to stop working and b) Akregator to crash on either start (if standalone) or exit (if embedded into Kontact). This suspicion is based on the fact that after I disabled the Title bar button menu in System Settings Kontact still kept all menubars hidden (standalone Akregator was abiding by System Settings rules and was showing menubar properly, without crashing) and I had to edit ~/.config/kontactrc to remove all MenuBar=disabled lines, until I did so Kontact kept crashing with stack trace like the one I posted in my earlier comment. Oh, completely forgot to mention - this is on Ubuntu 16.04 with KDE Neon User repos, Akregator and Kontact versions 5.5.2. The issue Alexey A Nikitin describes does not appear to be the same as my issue, since I did not disable the menubar. (In reply to Matthijs from comment #16) > The issue Alexey A Nikitin describes does not appear to be the same as my > issue, since I did not disable the menubar. If the stack trace is (nearly) the same chances are the same code path is activated, meaning if the crash is fixed for one case chances are it'll be fixed for another one too. I can confirm that for openSUSE Tumbleweed and latest Qt, Frameworks, Plasma, Apps... "Title bar button Menubar style, as soon as I switched from Title bar button to In application Akregator stopped crashing" can someone give me instructions on how to set the "Title bar button Menubar style"? so I can try to also get this crash and then try to fix. Systemsettings --> Application Style --> Widget Style --> Fine Tuning --> Set "Menubar Style" to "Title Bar Button" thanks. I'll run Kontact for a couple days and see if I can reproduce the crash. I use akregator quite a bit should it should be a good test. I noticed that I still get similar stack trace on exiting Kontact with Akregator embedded in it if I exit it while it's minimized to tray: Thread 1 (Thread 0x7fc49d7cd900 (LWP 4503)): [KCrash Handler] #6 0x00007fc4ba4ce2b7 in QMetaObject::cast (this=0x7fc38c4041e0 <Akregator::WebEngineFrame::staticMetaObject>, obj=obj@entry=0x2773970) at kernel/qmetaobject.cpp:366 #7 0x00007fc4ba4ce2f5 in QMetaObject::cast (this=<optimized out>, obj=obj@entry=0x2773970) at kernel/qmetaobject.cpp:355 #8 0x00007fc38c1a220a in qobject_cast<Akregator::WebEngineFrame*> (object=0x2773970) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:514 #9 Akregator::FrameManager::saveProperties (this=0x25d03b0, config=...) at /workspace/build/src/frame/framemanager.cpp:281 #10 0x00007fc38c68a53f in Akregator::MainWidget::saveProperties (this=<optimized out>, config=...) at /workspace/build/src/mainwidget.cpp:1237 #11 0x00007fc38c683186 in Akregator::Part::autoSaveProperties (this=this@entry=0x259f9a0) at /workspace/build/src/akregator_part.cpp:860 #12 0x00007fc38c683219 in Akregator::Part::slotOnShutdown (this=0x259f9a0) at /workspace/build/src/akregator_part.cpp:394 #13 0x00007fc4ba4f13f6 in QtPrivate::QSlotObjectBase::call (a=0x7ffe9a4835a0, r=0x259f9a0, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #14 QMetaObject::activate (sender=0x7ffe9a483890, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe9a4835a0) at kernel/qobject.cpp:3749 #15 0x00007fc4ba4f19d7 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7fc4ba7824a0 <QCoreApplication::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe9a4835a0) at kernel/qobject.cpp:3628 #16 0x00007fc4ba569fa7 in QCoreApplication::aboutToQuit (this=<optimized out>, _t1=...) at .moc/moc_qcoreapplication.cpp:250 #17 0x00007fc4ba4c7acb in QCoreApplicationPrivate::execCleanup (this=0x1a70ba0) at kernel/qcoreapplication.cpp:1311 #18 0x00007fc4ba4cbdcc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1295 #19 0x0000000000404427 in main (argc=1, argv=0x7ffe9a4839e8) at /workspace/build/src/main.cpp:227 If the window is visible no crash occurs. *** Bug 382000 has been marked as a duplicate of this bug. *** I found a workaround for this bug, which may be useful for others: since the bug is related to session restore, disabling it fixes the crashes for me. The session restore was not useful for me anyway. 1. Exclude akregator from the session restore in the settings 2. Add "akregator --hide-mainwindow" to the autostart apps Created attachment 107697 [details]
New crash information added by DrKonqi
akregator (5.5.1) using Qt 5.7.1
- What I was doing when the application crashed:
Opened application and crashed. When launched the application once more it keeps crashing.
-- Backtrace (Reduced):
#8 0x00007f45614d73ec in Akregator::FrameManager::saveProperties(KConfigGroup&) () from /lib64/libakregatorprivate.so.5
#9 0x00007f45291a6c03 in Akregator::MainWidget::saveProperties(KConfigGroup&) () from /usr/lib64/qt5/plugins/akregatorpart.so
#10 0x00007f452919f1dc in Akregator::Part::saveCrashProperties() () from /usr/lib64/qt5/plugins/akregatorpart.so
#12 0x00007f455d4ba8da in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#13 0x00007f455dcdd5dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
Git commit d0a5f4159cddcca656ca8bbcbd6e551e3499c166 by Anthony Fieroni. Committed on 10/09/2017 at 18:59. Pushed by anthonyfieroni into branch 'Applications/17.08'. [akregator] Make sure part is created before main windows is restored DIfferential Revision: https://phabricator.kde.org/D6739 Related: bug 381822, bug 381825, bug 377129 Signed-off-by: Anthony Fieroni <bvbfan@abv.bg> M +5 -8 src/main.cpp https://commits.kde.org/akregator/d0a5f4159cddcca656ca8bbcbd6e551e3499c166 Created attachment 107806 [details] New crash information added by DrKonqi akregator (5.6.1) using Qt 5.9.1 - What I was doing when the application crashed: Starting Akregator; this patch: https://commits.kde.org/akregator/d0a5f4159cddcca656ca8bbcbd6e551e3499c166 should be integrated already. Either the patch did not cure the bug or this is distinct case? -- Backtrace (Reduced): #8 0x00007f3d9c420f4c in qobject_cast<Akregator::WebEngineFrame*> (object=0x5610d6dcf050) at /usr/include/qt5/QtCore/qobject.h:514 #9 Akregator::FrameManager::saveProperties (this=0x5610d6e9a860, config=...) at /usr/src/debug/akregator-17.08.1/src/frame/framemanager.cpp:278 #10 0x00007f3d6a0dd973 in Akregator::MainWidget::saveProperties (this=0x5610d6f6a490, config=...) at /usr/src/debug/akregator-17.08.1/src/mainwidget.cpp:1227 #11 0x00007f3d6a0d63ac in Akregator::Part::saveCrashProperties (this=0x5610d6f8ca80) at /usr/src/debug/akregator-17.08.1/src/akregator_part.cpp:777 #12 0x00007f3d6a0d6425 in Akregator::Part::slotAutoSave (this=<optimized out>) at /usr/src/debug/akregator-17.08.1/src/akregator_part.cpp:782 I think it should be reopened, see last crash report... *** Bug 383926 has been marked as a duplicate of this bug. *** Still reproducible after commit d0a5f4159cddcca656ca8bbcbd6e551e3499c166 *** Bug 385316 has been marked as a duplicate of this bug. *** Created attachment 108402 [details]
New crash information added by DrKonqi
akregator (5.6.2) using Qt 5.9.2
- What I was doing when the application crashed:
You probably have enough backtraces at this stage, but some more tidbits of info:
* Both the "title bar buttons" and "application menu widget" settings cause the error, not just the first one.
* The "in application" workaround works for me.
* I've been using "application menu widget" setting for a long time without troubles, but I recently upgraded QT 5.7.1 -> 5.9.2 and akregator 17.08.1 -> 17.08.2, so I guess that the crash is also related to QT 5.9.
I've only tested standalone, not inside kontact.
-- Backtrace (Reduced):
#8 0x00007f6b8f3a8073 in qobject_cast<Akregator::WebEngineFrame*> (object=0x55ded155b2c0) at /usr/include/qt5/QtCore/qobject.h:514
#9 Akregator::FrameManager::saveProperties (this=0x55ded12a1210, config=...) at /var/tmp/portage/kde-apps/akregator-17.08.2/work/akregator-17.08.2/src/frame/framemanager.cpp:278
#10 0x00007f6b5841d895 in Akregator::MainWidget::saveProperties (this=<optimized out>, config=...) at /var/tmp/portage/kde-apps/akregator-17.08.2/work/akregator-17.08.2/src/mainwidget.cpp:1227
#11 0x00007f6b584182ad in Akregator::Part::saveCrashProperties (this=0x55ded12db690) at /var/tmp/portage/kde-apps/akregator-17.08.2/work/akregator-17.08.2/src/akregator_part.cpp:780
#12 0x00007f6b8ce1ceef in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5
*** Bug 386680 has been marked as a duplicate of this bug. *** *** Bug 387581 has been marked as a duplicate of this bug. *** *** Bug 388046 has been marked as a duplicate of this bug. *** *** Bug 387893 has been marked as a duplicate of this bug. *** Bug 387893 confirms it is caused by changing the menubar style. Created attachment 110322 [details]
New crash information added by DrKonqi
akregator (5.7.1) using Qt 5.9.3
- What I was doing when the application crashed:
I'm testing this on Leap 15 Build 1115.1 Plasma 5.11.95 and akregator still crashes if the menubar is enabled. Disabling the menubar allows akregator to start up.
-- Backtrace (Reduced):
#7 0x00007f8c7048636c in qobject_cast<Akregator::WebEngineFrame*> (object=0x5622fd212e90) at /usr/include/qt5/QtCore/qobject.h:514
#8 Akregator::FrameManager::saveProperties (this=0x5622fce7dad0, config=...) at /usr/src/debug/akregator-17.12.1/src/frame/framemanager.cpp:275
#9 0x00007f8c3816bbf3 in Akregator::MainWidget::saveProperties (this=0x5622fcf56130, config=...) at /usr/src/debug/akregator-17.12.1/src/mainwidget.cpp:1231
#10 0x00007f8c3816478c in Akregator::Part::saveCrashProperties (this=0x5622fcea2da0) at /usr/src/debug/akregator-17.12.1/src/akregator_part.cpp:780
#11 0x00007f8c38164805 in Akregator::Part::slotAutoSave (this=<optimized out>) at /usr/src/debug/akregator-17.12.1/src/akregator_part.cpp:785
*** Bug 391456 has been marked as a duplicate of this bug. *** *** Bug 388896 has been marked as a duplicate of this bug. *** *** Bug 393672 has been marked as a duplicate of this bug. *** *** Bug 400616 has been marked as a duplicate of this bug. *** *** Bug 402127 has been marked as a duplicate of this bug. *** *** Bug 403309 has been marked as a duplicate of this bug. *** Created attachment 124044 [details]
New crash information added by DrKonqi
kontact (5.12.3) using Qt 5.13.2
- What I was doing when the application crashed:
Every times, I close kontact, I have a crash of it.
-- Backtrace (Reduced):
#9 0x00007feea0e47cec in qobject_cast<Akregator::WebEngineFrame*> (object=0x559db896f660) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:508
#10 Akregator::FrameManager::saveProperties (this=0x559db88fb1a0, config=...) at ./src/frame/framemanager.cpp:277
#11 0x00007feea1336573 in Akregator::MainWidget::saveProperties (this=0x559db89dca20, config=...) at ./src/mainwidget.cpp:1237
#12 0x00007feea132ee9c in Akregator::Part::saveCrashProperties (this=0x559db88dbc80) at ./src/akregator_part.cpp:821
#13 0x00007fefffb15432 in QObject::event (this=0x559db88dbc80, e=<optimized out>) at kernel/qobject.cpp:1260
Created attachment 128118 [details]
New crash information added by DrKonqi
kontact (5.13.2 (19.12.2)) using Qt 5.13.2
- What I was doing when the application crashed:
opening Kontact after it was closed for a while
-- Backtrace (Reduced):
#7 0x00007f0e0482b08c in Akregator::FrameManager::saveProperties(KConfigGroup&) () from /lib64/libakregatorprivate.so.5
#8 0x00007f0e04927a36 in Akregator::MainWidget::saveProperties(KConfigGroup&) () from /usr/lib64/qt5/plugins/akregatorpart.so
#9 0x00007f0e04921798 in Akregator::Part::saveCrashProperties() () from /usr/lib64/qt5/plugins/akregatorpart.so
#10 0x00007f0eaf26d352 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#11 0x00007f0eafb4de76 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! 4 years old. this bug has disappeared and resurfaced many times since then, most likely different reasons each time. Not using the app anymore. Go ahead and close. Ryan On Fri, Oct 7, 2022, at 17:38, Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=378513 > > Justin Zobel <justin.zobel@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > Status|REOPENED |NEEDSINFO > > --- Comment #47 from Justin Zobel <justin.zobel@gmail.com> --- > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! > > -- > You are receiving this mail because: > You are on the CC list for the bug. |