Bug 378012 - Crash when going online
Summary: Crash when going online
Status: RESOLVED NOT A BUG
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2017-03-24 11:18 UTC by OlafLostViking
Modified: 2017-04-04 20:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description OlafLostViking 2017-03-24 11:18:43 UTC
Application: kopete (1.11.3)

Qt Version: 5.8.0
Frameworks Version: 5.32.0
Operating System: Linux 4.10.4-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:

On a freshly rebooted computer, I went online with Kopete. KWallet asked for the password, Kopete went online with some accounts and then crashed.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f863da52840 (LWP 2184))]

Thread 3 (Thread 0x7f861ee7f700 (LWP 3395)):
#0  0x00007f8639cf767d in poll () at /usr/lib/libc.so.6
#1  0x00007f86359647a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x00007f86359648bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#3  0x00007f863b4c9f8e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#4  0x00007f863b49843f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#5  0x00007f863b4987a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#6  0x00007f863b386779 in QThread::exec() () at /usr/lib/libQtCore.so.4
#7  0x00007f86252a32b8 in  () at /usr/lib/kde4/kopete_jabber.so
#8  0x00007f863b38904a in  () at /usr/lib/libQtCore.so.4
#9  0x00007f86372c62e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x00007f8639d0154f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f861f680700 (LWP 3394)):
#0  0x00007ffdb119f939 in  ()
#1  0x00007ffdb119fbc5 in clock_gettime ()
#2  0x00007f8639d0e826 in clock_gettime () at /usr/lib/libc.so.6
#3  0x00007f863b3e3a85 in  () at /usr/lib/libQtCore.so.4
#4  0x00007f863b4cae15 in  () at /usr/lib/libQtCore.so.4
#5  0x00007f863b4c963c in  () at /usr/lib/libQtCore.so.4
#6  0x00007f863b4c9705 in  () at /usr/lib/libQtCore.so.4
#7  0x00007f8635963c8d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0
#8  0x00007f86359646cb in  () at /usr/lib/libglib-2.0.so.0
#9  0x00007f86359648bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#10 0x00007f863b4c9f8e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#11 0x00007f863b49843f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#12 0x00007f863b4987a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#13 0x00007f8624e4d453 in QCA::SyncThread::run() () at /usr/lib/libqca.so.2
#14 0x00007f863b38904a in  () at /usr/lib/libQtCore.so.4
#15 0x00007f86372c62e7 in start_thread () at /usr/lib/libpthread.so.0
#16 0x00007f8639d0154f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f863da52840 (LWP 2184)):
[KCrash Handler]
#6  0x00007f863cbe16a0 in  () at /usr/lib/libkopete.so.4
#7  0x00007f863cbe157f in  () at /usr/lib/libkopete.so.4
#8  0x00007f863cbe15e9 in  () at /usr/lib/libkopete.so.4
#9  0x00007f863b4b1f44 in QObjectPrivate::deleteChildren() () at /usr/lib/libQtCore.so.4
#10 0x00007f863b4b459c in QObject::~QObject() () at /usr/lib/libQtCore.so.4
#11 0x00007f863bf74c09 in KNotification::~KNotification() () at /usr/lib/libkdeui.so.5
#12 0x00007f863b4b3a58 in QObject::event(QEvent*) () at /usr/lib/libQtCore.so.4
#13 0x00007f863a542f2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQtGui.so.4
#14 0x00007f863a549e3c in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQtGui.so.4
#15 0x00007f863bf4932a in KApplication::notify(QObject*, QEvent*) () at /usr/lib/libkdeui.so.5
#16 0x00007f863b499b6d in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib/libQtCore.so.4
#17 0x00007f863b49d046 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQtCore.so.4
#18 0x00007f863b4c9dfe in  () at /usr/lib/libQtCore.so.4
#19 0x00007f86359645a7 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#20 0x00007f8635964810 in  () at /usr/lib/libglib-2.0.so.0
#21 0x00007f86359648bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#22 0x00007f863b4c9f6e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#23 0x00007f863a5ebed6 in  () at /usr/lib/libQtGui.so.4
#24 0x00007f863b49843f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#25 0x00007f863b4987a5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4
#26 0x00007f863b49e209 in QCoreApplication::exec() () at /usr/lib/libQtCore.so.4
#27 0x0000000000413f65 in  ()
#28 0x00007f8639c35511 in __libc_start_main () at /usr/lib/libc.so.6
#29 0x000000000041474a in _start ()

Reported using DrKonqi
Comment 1 Pali Rohár 2017-03-26 09:54:51 UTC
(In reply to OlafLostViking from comment #0)
> The crash does not seem to be reproducible.

This is really hard to debug...

> Thread 1 (Thread 0x7f863da52840 (LWP 2184)):
> [KCrash Handler]
> #6  0x00007f863cbe16a0 in  () at /usr/lib/libkopete.so.4
> #7  0x00007f863cbe157f in  () at /usr/lib/libkopete.so.4
> #8  0x00007f863cbe15e9 in  () at /usr/lib/libkopete.so.4

Also there are missing function names to do any investigation. Without debug symbols such report is unusable.
Comment 2 OlafLostViking 2017-03-28 10:09:19 UTC
Dear Pali,

actually I only sent this via Dr Konqi, which said the bt would be useful. So, since I don't have any further details and I also cannot reproduce it reliably, the report should probably be closed.

Thanks!