Summary: | Akregator crash when closing from systrey. [internalWinId, QWidget::effectiveWinId, QXIMInputContext::reset] | ||
---|---|---|---|
Product: | [Applications] akregator | Reporter: | Petar Petrov <marokanski.kazak> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andresbajotierra, antonio, carlsymons, cfeck, darktears31, juha.tiensyrja, kde, l.mierzwa, marokanski.kazak, p.varet |
Priority: | NOR | Keywords: | triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Petar Petrov
2010-01-02 20:55:44 UTC
This is probably a bug in the Qt library. Regards *** Bug 221796 has been marked as a duplicate of this bug. *** *** Bug 222159 has been marked as a duplicate of this bug. *** I wonder if this could be related to bug 216878... Created attachment 40331 [details]
New crash information added by DrKonqi
Amarok from 4.4 rc2 just crashed on exit.
Created attachment 40344 [details]
New crash information added by DrKonqi
I just closed Akregator from the system tray, and it crashed. I cannot reproduce it right now, but if I remember correctly, it has crashed the same way a couple of times before during 4.4 beta and rc cycles.
*** Bug 224749 has been marked as a duplicate of this bug. *** from comment #6: -- Information about the crash: I just closed Akregator from the system tray, and it crashed. I cannot reproduce it right now, but if I remember correctly, it has crashed the same way a couple of times before during 4.4 beta and rc cycles. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault [KCrash Handler] #5 QWidget::internalWinId (this=0xcbecd0) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:234 #6 QWidget::effectiveWinId (this=0xcbecd0) at kernel/qwidget.cpp:2337 #7 0x00007ffcaee27182 in QXIMInputContext::reset (this=0x1394da0) at inputmethod/qximinputcontext_x11.cpp:535 #8 0x00007ffcaee2685c in QXIMInputContext::setFocusWidget (this=0x1394da0, w=0x0) at inputmethod/qximinputcontext_x11.cpp:605 #9 0x00007ffcaee2640f in QXIMInputContext::close_xim (this=0x1394da0) at inputmethod/qximinputcontext_x11.cpp:489 #10 0x00007ffcaee264a0 in ~QXIMInputContext (this=0xcbecd0, __in_chrg=<value optimized out>) at inputmethod/qximinputcontext_x11.cpp:498 #11 0x00007ffcadeeba8c in QObjectPrivate::deleteChildren (this=0x1213fe0) at kernel/qobject.cpp:1998 #12 0x00007ffcadef2b34 in ~QObject (this=<value optimized out>, __in_chrg=<value optimized out>) at kernel/qobject.cpp:987 #13 0x00007ffc9616df8a in ~QMultiInputContext (this=0xfc0860, __in_chrg=<value optimized out>) at qmultiinputcontext.cpp:111 #14 0x00007ffcae8cf88e in qt_cleanup () at kernel/qapplication_x11.cpp:2605 #15 0x00007ffcae86158c in ~QApplication (this=0x7fff0d540fe0, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1079 #16 0x0000000000409810 in _start () Possible duplicates by query: bug 222159, bug 221796. Reported using DrKonqi This crash report is at least 3 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources. If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports (To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED) Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |