Bug 144094 - crash on rejoining IRC chat as server unavailable
Summary: crash on rejoining IRC chat as server unavailable
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: IRC Plugin (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2007-04-11 21:54 UTC by Elmar Stellnberger (AT/K)
Modified: 2018-10-27 02:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
backtrace (1.77 KB, text/plain)
2007-04-11 21:54 UTC, Elmar Stellnberger (AT/K)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar Stellnberger (AT/K) 2007-04-11 21:54:13 UTC
Version:           0.12.4 (using KDE 3.5.6 "release 64.1" , openSUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.16.21-0.25-default

After powersave had interrupted an open IRC channel session by suspending to ram trying to reopen that session has induced a crash. The server (irc.freenode.net) must have been unavailable that time since Kopete could not even connect after a restart(quit&start) for a longer period of time.
Comment 1 Elmar Stellnberger (AT/K) 2007-04-11 21:54:47 UTC
Created attachment 20238 [details]
backtrace
Comment 2 Michel Hermier 2007-04-14 10:16:00 UTC
Un-attach the stack trace, (so the automatic duplicate bug process can find it)

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1239787856 (LWP 11306)]
[KCrash handler]
#6  0xb7a58c5c in KSSL::write () from /opt/kde3/lib/libkio.so.4
#7  0xb44a7613 in KSSLSocket::writeBlock ()
   from /opt/kde3/lib/kde3/kopete_irc.so
#8  0xb44a2590 in KIRC::Message::writeRawMessage ()
   from /opt/kde3/lib/kde3/kopete_irc.so
#9  0xb44a26ee in KIRC::Message::writeMessage ()
   from /opt/kde3/lib/kde3/kopete_irc.so
#10 0xb448eecf in KIRC::Engine::writeMessage ()
   from /opt/kde3/lib/kde3/kopete_irc.so
#11 0xb445c7cc in IRCChannelContact::slotUpdateInfo ()
   from /opt/kde3/lib/kde3/kopete_irc.so
#12 0xb4467a21 in IRCChannelContact::qt_invoke ()
   from /opt/kde3/lib/kde3/kopete_irc.so
#13 0xb6f6b1fd in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0xb6f6be5d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0xb72a7509 in QTimer::timeout () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb6f8ea2f in QTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb6f0bc67 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0xb6f0ca31 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0xb75f4743 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#20 0xb6f00e06 in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0xb6ebabb0 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb6f22a88 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb6f2291e in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb6f0b81f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x0807e3eb in main ()
Comment 3 Andrew Perepechko 2008-01-16 18:06:59 UTC
I have exactly the same Kopete crash (with the same stack trace) every time my Internet connection is broken.

Currently I am using Kopete 0.12.7 (Using KDE 3.5.8 "release 25" OpenSUSE 11.0), but this also happens with previous versions of Kopete.
Comment 4 Christoph Feck 2013-09-12 21:45:24 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Comment 5 Andrew Crouthamel 2018-09-24 02:08: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 set the bug status 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 6 Andrew Crouthamel 2018-10-27 02:17:13 UTC
Dear Bug Submitter,

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!