Application: ktp-contactlist (0.6.1) KDE Platform Version: 4.10.3 Qt Version: 4.8.4 Operating System: Linux 3.8.0-23-generic x86_64 Distribution: Ubuntu 13.04 -- Information about the crash: - What I was doing when the application crashed: Clicking the Instant Messaging Prescence in the system tray should bring up KDE IM Contacts, instead a crash is reported. This happens about half the time when clicking on the icon. The crash can be reproduced sometimes. -- Backtrace: Application: KDE Telepathy Contact List (ktp-contactlist), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #5 QWidget::setMaximumSize (this=this@entry=0xb82df0, maxw=16777215, maxh=maxh@entry=28) at kernel/qwidget.cpp:4068 #6 0x00007f690ce92d42 in QWidget::setMaximumHeight (this=0xb82df0, h=28) at kernel/qwidget.cpp:4209 #7 0x0000000000441401 in GlobalPresenceChooser::repositionOverlays (this=this@entry=0xa9cd40) at /build/buildd/ktp-contact-list-0.6.1/global-presence-chooser.cpp:411 #8 0x000000000044156d in onConnectionStatusChanged (this=0xa9cd40, connectionStatus=<optimized out>) at /build/buildd/ktp-contact-list-0.6.1/global-presence-chooser.cpp:401 #9 GlobalPresenceChooser::onConnectionStatusChanged (this=0xa9cd40, connectionStatus=<optimized out>) at /build/buildd/ktp-contact-list-0.6.1/global-presence-chooser.cpp:398 #10 0x0000000000444170 in GlobalPresenceChooser::GlobalPresenceChooser (this=0xa9cd40, parent=<optimized out>) at /build/buildd/ktp-contact-list-0.6.1/global-presence-chooser.cpp:191 #11 0x00000000004408ba in Ui_MainWindow::setupUi (this=this@entry=0xb4f730, MainWindow=MainWindow@entry=0xb4f700) at /build/buildd/ktp-contact-list-0.6.1/obj-x86_64-linux-gnu/ui_main-widget.h:55 #12 0x000000000043e3ef in MainWidget::MainWidget (this=0xb4f700, parent=<optimized out>) at /build/buildd/ktp-contact-list-0.6.1/main-widget.cpp:84 #13 0x000000000041bfb0 in main (argc=1, argv=0x7fff840e10d8) at /build/buildd/ktp-contact-list-0.6.1/main.cpp:59 Reported using DrKonqi
Fixed in 0.6.2 *** This bug has been marked as a duplicate of bug 319040 ***