Bug 221022 - Akregator crash when closing from systrey. [internalWinId, QWidget::effectiveWinId, QXIMInputContext::reset]
Summary: Akregator crash when closing from systrey. [internalWinId, QWidget::effectiv...
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
: 221796 222159 224749 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-01-02 20:55 UTC by Petar Petrov
Modified: 2018-10-27 02:10 UTC (History)
10 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (1.94 KB, text/plain)
2010-01-29 00:47 UTC, l.mierzwa
Details
New crash information added by DrKonqi (1.80 KB, text/plain)
2010-01-29 10:19 UTC, Juha Tiensyrjä
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Petar Petrov 2010-01-02 20:55:44 UTC
Application: akregator (1.6.0)
KDE Platform Version: 4.3.86 (KDE 4.3.86 (KDE 4.4 >= 20091231)) "release 1"
Qt Version: 4.6.1
Operating System: Linux 2.6.31.5-0.1-default i686
Distribution: "openSUSE 11.2 (i586)"

-- Information about the crash:
Akregator crashed when i closed it from system tray. The crash haven't occured after that.

The crash does not seem to be reproducible.

 -- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
[Current thread is 1 (Thread 0xb3af3760 (LWP 25632))]

Thread 3 (Thread 0xae664b70 (LWP 31534)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb4b8b0c2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb5fac2d4 in pthread_cond_timedwait () from /lib/libc.so.6
#3  0xb6c19e9c in wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:85
#4  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#5  0xb6c0e64e in QThreadPoolThread::run (this=0x850bfd0) at concurrent/qthreadpool.cpp:140
#6  0xb6c18ebf in QThreadPrivate::start (arg=0x850bfd0) at thread/qthread_unix.cpp:248
#7  0xb4b866e5 in start_thread () from /lib/libpthread.so.0
#8  0xb4b86600 in ?? () from /lib/libpthread.so.0

Thread 2 (Thread 0xaf853b70 (LWP 31536)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb4b8b0c2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb5fac2d4 in pthread_cond_timedwait () from /lib/libc.so.6
#3  0xb6c19e9c in wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:85
#4  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#5  0xb6c0e64e in QThreadPoolThread::run (this=0x83fe9e8) at concurrent/qthreadpool.cpp:140
#6  0xb6c18ebf in QThreadPrivate::start (arg=0x83fe9e8) at thread/qthread_unix.cpp:248
#7  0xb4b866e5 in start_thread () from /lib/libpthread.so.0
#8  0xb4b86600 in ?? () from /lib/libpthread.so.0

Thread 1 (Thread 0xb3af3760 (LWP 25632)):
[KCrash Handler]
#6  0xb62ccfe1 in internalWinId (this=<value optimized out>) at ../../src/gui/kernel/qwidget.h:234
#7  QWidget::effectiveWinId (this=<value optimized out>) at kernel/qwidget.cpp:2338
#8  0xb68ce846 in QXIMInputContext::reset (this=0x8b18478) at inputmethod/qximinputcontext_x11.cpp:535
#9  0xb68cde0d in QXIMInputContext::setFocusWidget (this=0x8b18478, w=0x0) at inputmethod/qximinputcontext_x11.cpp:605
#10 0xb68cd90c in QXIMInputContext::close_xim (this=0x8b18478) at inputmethod/qximinputcontext_x11.cpp:489
#11 0xb68cd9c4 in QXIMInputContext::~QXIMInputContext (this=0x8b18478, __in_chrg=<value optimized out>) at inputmethod/qximinputcontext_x11.cpp:498
#12 0xb62fd11d in qt_cleanup () at kernel/qapplication_x11.cpp:2605
#13 0xb627ea40 in QApplication::~QApplication (this=0xbfe4d830, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1081
#14 0xb731eef8 in KApplication::~KApplication (this=0xbfe4d830, __in_chrg=<value optimized out>) at /usr/src/debug/kdelibs-4.3.86svn1068163/kdeui/kernel/kapplication.cpp:896
#15 0xb73264c8 in KUniqueApplication::~KUniqueApplication (this=0xbfe4d830, __in_chrg=<value optimized out>) at /usr/src/debug/kdelibs-4.3.86svn1068163/kdeui/kernel/kuniqueapplication.cpp:372
#16 0xb76ee598 in KontactInterface::PimUniqueApplication::~PimUniqueApplication (this=0xbfe4d830, __in_chrg=<value optimized out>)
    at /usr/src/debug/kdepimlibs-4.3.86svn1068163/kontactinterface/pimuniqueapplication.cpp:58
#17 0x0804fbeb in ~Application (this=<value optimized out>, __in_chrg=<value optimized out>) at /usr/src/debug/kdepim-4.3.86svn1068163/akregator/src/main.cpp:41
#18 main (this=<value optimized out>, __in_chrg=<value optimized out>) at /usr/src/debug/kdepim-4.3.86svn1068163/akregator/src/main.cpp:103

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-03 16:12:59 UTC
This is probably a bug in the Qt library. Regards
Comment 2 Dario Andres 2010-01-08 14:40:05 UTC
*** Bug 221796 has been marked as a duplicate of this bug. ***
Comment 3 Dario Andres 2010-01-11 13:58:41 UTC
*** Bug 222159 has been marked as a duplicate of this bug. ***
Comment 4 Dario Andres 2010-01-11 13:59:21 UTC
I wonder if this could be related to bug 216878...
Comment 5 l.mierzwa 2010-01-29 00:47:55 UTC
Created attachment 40331 [details]
New crash information added by DrKonqi

Amarok from 4.4 rc2 just crashed on exit.
Comment 6 Juha Tiensyrjä 2010-01-29 10:19:48 UTC
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.
Comment 7 Frank Osterfeld 2010-01-29 13:08:12 UTC
*** Bug 224749 has been marked as a duplicate of this bug. ***
Comment 8 Nicolas L. 2010-08-12 22:25:23 UTC
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
Comment 9 Christoph Feck 2013-09-12 21:47:17 UTC
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)
Comment 10 Andrew Crouthamel 2018-09-25 03:32:55 UTC
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!
Comment 11 Andrew Crouthamel 2018-10-27 02:10:18 UTC
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!