Bug 273757 - Konversation chrash after reconneced
Summary: Konversation chrash after reconneced
Status: RESOLVED WORKSFORME
Alias: None
Product: Oxygen
Classification: Plasma
Component: style (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Hugo Pereira Da Costa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-20 22:52 UTC by heinemann
Modified: 2018-11-29 04:51 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description heinemann 2011-05-20 22:52:49 UTC
Application: konversation (1.3.1)
KDE Platform Version: 4.6.3 (4.6.3) "release 1"
Qt Version: 4.7.3
Operating System: Linux 2.6.38.6-29-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:  Netsplitt -> Asked to accept
the Key -> Accept -> crash.

It's like https://bugs.kde.org/show_bug.cgi?id=263194, but now I accept the Key permanet. And I use KDE 4.6.3 (openSuSE 11.4 with Tumbleweed)

The crash can be reproduced some of the time.

-- Backtrace:
Application: Konversation (konversation), signal: Aborted
[Current thread is 1 (Thread 0x7f6d74855760 (LWP 2837))]

Thread 2 (Thread 0x7f6d5e308700 (LWP 15696)):
#0  0x00007f6d6fa458fe in __lll_lock_wait_private () from /lib64/libc.so.6
#1  0x00007f6d6f9def2e in _L_lock_9927 () from /lib64/libc.so.6
#2  0x00007f6d6f9dd2d1 in free () from /lib64/libc.so.6
#3  0x00007f6d6aee1e08 in ?? () from /lib64/libglib-2.0.so.0
#4  0x00007f6d712d75ea in QEventDispatcherGlib::~QEventDispatcherGlib (this=<value optimized out>, __in_chrg=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:373
#5  0x00007f6d712d7739 in QEventDispatcherGlib::~QEventDispatcherGlib (this=0xbdc700, __in_chrg=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:401
#6  0x00007f6d711c23b4 in QThreadPrivate::finish (arg=0xd3ad70) at thread/qthread_unix.cpp:356
#7  0x00007f6d711c309d in ~__pthread_cleanup_class (arg=0xd3ad70) at /usr/include/pthread.h:535
#8  QThreadPrivate::start (arg=0xd3ad70) at thread/qthread_unix.cpp:279
#9  0x00007f6d6e1f3a3f in start_thread () from /lib64/libpthread.so.0
#10 0x00007f6d6fa3867d in clone () from /lib64/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f6d74855760 (LWP 2837)):
[KCrash Handler]
#6  0x00007f6d6f997ab5 in raise () from /lib64/libc.so.6
#7  0x00007f6d6f998fb6 in abort () from /lib64/libc.so.6
#8  0x00007f6d6f9d2dd3 in __libc_message () from /lib64/libc.so.6
#9  0x00007f6d6f9d83b6 in malloc_printerr () from /lib64/libc.so.6
#10 0x00007f6d6f9dd2dc in free () from /lib64/libc.so.6
#11 0x00007f6d712c4768 in operator= (this=0xf2c8a8) at ../../src/corelib/tools/qlist.h:430
#12 QList<QObject*>::clear (this=0xf2c8a8) at ../../src/corelib/tools/qlist.h:752
#13 0x00007f6d712bea4f in QObjectPrivate::deleteChildren (this=0xf2c890) at kernel/qobject.cpp:1957
#14 0x00007f6d712c3782 in QObject::~QObject (this=0xb7af30, __in_chrg=<value optimized out>) at kernel/qobject.cpp:946
#15 0x00007f6d660d700e in ?? () from /usr/lib64/kde4/plugins/styles/oxygen.so
#16 0x00007f6d712c03a8 in QObject::event (this=0xb7af30, e=<value optimized out>) at kernel/qobject.cpp:1200
#17 0x00007f6d703fc144 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#18 0x00007f6d704046fa in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x00007f6d71c0f006 in KApplication::notify (this=0x7fffc8bedd50, receiver=0xb7af30, event=0xd61570) at /usr/src/debug/kdelibs-4.6.3/kdeui/kernel/kapplication.cpp:311
#20 0x00007f6d712ac47c in QCoreApplication::notifyInternal (this=0x7fffc8bedd50, receiver=0xb7af30, event=0xd61570) at kernel/qcoreapplication.cpp:731
#21 0x00007f6d712afc75 in sendEvent (receiver=0x0, event_type=0, data=0x85e200) at kernel/qcoreapplication.h:215
#22 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x85e200) at kernel/qcoreapplication.cpp:1372
#23 0x00007f6d712d7093 in sendPostedEvents (s=0x8981c0) at kernel/qcoreapplication.h:220
#24 postEventSourceDispatch (s=0x8981c0) at kernel/qeventdispatcher_glib.cpp:277
#25 0x00007f6d6aee5bd3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#26 0x00007f6d6aee63b0 in ?? () from /lib64/libglib-2.0.so.0
#27 0x00007f6d6aee6650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#28 0x00007f6d712d722f in QEventDispatcherGlib::processEvents (this=0x863890, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#29 0x00007f6d704a1bae in ?? () from /usr/lib64/libQtGui.so.4
#30 0x00007f6d712ab8d2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#31 0x00007f6d712abae5 in QEventLoop::exec (this=0x7fffc8bedca0, flags=...) at kernel/qeventloop.cpp:201
#32 0x00007f6d712aff2b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008
#33 0x000000000046ce6c in _start ()

Reported using DrKonqi
Comment 1 Eike Hein 2011-06-27 11:18:08 UTC
Just noticed that the backtrace involves Oxygen, reassigning ...
Comment 2 Hugo Pereira Da Costa 2011-06-27 11:52:43 UTC
Need to install debug symbols for kde-workspace.
Nothing I can do otherwise.
Comment 3 Andrew Crouthamel 2018-10-29 22:34:57 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2018-11-13 14:32:45 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
mark the bug 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 5 Bug Janitor Service 2018-11-29 04:51:30 UTC
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!