Bug 181457 - Crashes on startup / popup notification
Summary: Crashes on startup / popup notification
Status: RESOLVED DUPLICATE of bug 170376
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-21 04:15 UTC by Abir
Modified: 2009-01-29 23:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
KDE Backtrace (5.71 KB, text/plain)
2009-01-21 04:16 UTC, Abir
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Abir 2009-01-21 04:15:50 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

This is the first time I used Kopete (and KDE). After configuring it to access Google Talk through Jabber, I waited for Kopete to connect. Initially my list was empty, but after a few seconds I got a host of notifications of my friends' statuses and Kopete crashed. 

I am not really very hands-on with Linux, but I believe that KDE managed to acquire a backtrace. Any help on fixing this would be appreciated.

Thanks in advance!
Comment 1 Abir 2009-01-21 04:16:57 UTC
Created attachment 30476 [details]
KDE Backtrace
Comment 2 Pino Toscano 2009-01-21 11:02:23 UTC
Pasting the backtrace:

Application: Kopete (kopete), signal SIGSEGV
(no debugging symbols found)
[...]
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb59ab6c0 (LWP 7151)]
[New Thread 0xb1e4ab90 (LWP 7171)]
(no debugging symbols found)
[...]
(no debugging symbols found)
[KCrash handler]
#6  0xb64f3b56 in memcpy () from /lib/tls/i686/cmov/libc.so.6
#7  0x095033d8 in ?? ()
#8  0xb785b350 in KNetwork::KBufferedSocket::slotWriteActivity ()
   from /usr/lib/libkdecore.so.5
#9  0xb785b180 in KNetwork::KBufferedSocket::qt_metacall ()
   from /usr/lib/libkdecore.so.5
#10 0xb7637a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb76387e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb7672633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#13 0xb763d637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#14 0xb6b048ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#15 0xb6b0c72e in QApplication::notify () from /usr/lib/libQtGui.so.4
#16 0xb7b62b2d in KApplication::notify () from /usr/lib/libkdeui.so.5
#17 0xb7622e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#18 0xb764d70a in ?? () from /usr/lib/libQtCore.so.4
#19 0xb60046f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xb6007da3 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0xb6007f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb764d478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#23 0xb6b9eea5 in ?? () from /usr/lib/libQtGui.so.4
#24 0xb762152a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#25 0xb76216ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#26 0xb7623da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#27 0xb6b04767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#28 0x0808aa6f in _start ()
#0  0xb80f2430 in __kernel_vsyscall ()
Comment 3 Dario Andres 2009-01-29 23:47:57 UTC

*** This bug has been marked as a duplicate of bug 170376 ***