Bug 90741 - crashes kopete when trying to connect
Summary: crashes kopete when trying to connect
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: WinPopup Plugin (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2004-10-04 09:40 UTC by Nick Blackledge
Modified: 2018-10-21 05:10 UTC (History)
0 users

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 Nick Blackledge 2004-10-04 09:40:07 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    SuSE RPMs
OS:                Linux

With the winpopup plugin enabled kopete will always crash after about 20 seconds. It says it is impossible to complete a backtrace but it thinks libpthread_db.so is to blame for some reason.

When I try to run kpopup I can actually get some backtrace information out of it which may be somehow related to the winpopup error as they are similar programs.

I hope this is helpful.

/* Begin Backtrace */

(no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 1091354784 (LWP 6406)]
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in ?? ()
#0  0xffffe410 in ?? ()
#1  0xbfffd75c in ?? ()
#2  0x00000000 in ?? ()
#3  0x00000000 in ?? ()
#4  0x40e8ae63 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#5  0x4040af32 in KCrash::defaultCrashHandler ()
   from /opt/kde3/lib/libkdecore.so.4
#6  <signal handler called>
#7  0x08051b00 in Make_Popup::sendPopup ()
#8  0x08051b7f in Make_Popup::qt_invoke ()
#9  0x407cb4ce in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x407cbc76 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#11 0x40b12dcc in QButton::clicked () from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x40861509 in QButton::mouseReleaseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#13 0x40800df9 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x40769fef in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x4076c1c8 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x404540e4 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#17 0x40705753 in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x40704345 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40718a85 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x40781a31 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x4076b84f in QApplication::enter_loop ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x4095b892 in QDialog::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x08053318 in KPopup::newPopup ()
#24 0x08054111 in KPopup::qt_invoke ()
#25 0x407cb4ce in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x407cbafd in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x40264600 in KToolBar::clicked () from /opt/kde3/lib/libkdeui.so.4
#28 0x4026474e in KToolBar::qt_emit () from /opt/kde3/lib/libkdeui.so.4
#29 0x407cb501 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x407cbafd in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0x401d10c0 in KToolBarButton::clicked () from /opt/kde3/lib/libkdeui.so.4
#32 0x401d11f9 in KToolBarButton::slotClicked ()
   from /opt/kde3/lib/libkdeui.so.4
#33 0x401d3044 in KToolBarButton::qt_invoke () from /opt/kde3/lib/libkdeui.so.4
#34 0x407cb4ce in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0x407cbc76 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0x40b12dcc in QButton::clicked () from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0x40861509 in QButton::mouseReleaseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#38 0x40800df9 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#39 0x40769fef in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#40 0x4076c1c8 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#41 0x404540e4 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#42 0x40705753 in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#43 0x40704345 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#44 0x40718a85 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#45 0x40781a31 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#46 0x40781876 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#47 0x4076b8df in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#48 0x08056484 in main ()


/* End Backtrace */
Comment 1 Gav Wood 2004-10-04 11:28:46 UTC
> With the winpopup plugin enabled kopete will always crash after about 20
> seconds. It says it is impossible to complete a backtrace but it thinks
> libpthread_db.so is to blame for some reason.
>
> When I try to run kpopup I can actually get some backtrace information out
> of it which may be somehow related to the winpopup error as they are
> similar programs.
>
> I hope this is helpful.

well, thanks for trying...

unless someone recoded it without me knowing, the winpopup plugin is not at 
all connected to kpopup, thus the backtrace isn't must use.

in any case the problem is most likely due to the fact the winpopup is:
a) out of date with respect to the new kopete api
b) built for samba 2 (and i suspect you're using samba 3)

(a) can be fixed relatively easily from what i understand, it's just i haven't 
had nearly the time to do it. (b) is probably easily fixable, though to do it 
"correctly" the plugin would have to be rewritten since i believe samba3 has 
a libsamba that makes sending messages simple.

gav

Comment 2 Matt Rogers 2009-03-06 06:05:32 UTC
There have been a lot of changes to the winpopup plugin throughout the years (and this is a very old report). Are you still using Kopete with Winpopup? If so, does it still crash?
Comment 3 Andrew Crouthamel 2018-09-19 04:39:20 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 4 Andrew Crouthamel 2018-10-21 05:10:13 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!