kopete crashed with SIGSEGV in KIO::TransferJob::isErrorPage()

Bug #408086 reported by desert rover on 2009-08-02
58
This bug affects 9 people
Affects Status Importance Assigned to Milestone
KDE Network
Unknown
High
kdenetwork (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: kdenetwork

kopete just crashed. Was running firefox 3.5.1 and karmic kola

ProblemType: Crash
Architecture: amd64
Date: Sun Aug 2 12:20:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kopete
NonfreeKernelModules: nvidia
Package: kopete 4:4.2.98-0ubuntu2
ProcCmdline: /usr/bin/kopete -caption Kopete
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SegvAnalysis:
 Segfault happened at: 0x7fea5033d604 <_ZNK3KIO11TransferJob11isErrorPageEv+4>: movzbl 0xbd(%rax),%eax
 PC (0x7fea5033d604) ok
 source "0xbd(%rax)" (0x000000dd) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kdenetwork
StacktraceTop:
 KIO::TransferJob::isErrorPage() const ()
 ?? () from /usr/lib/libkyahoo.so.1
 ?? () from /usr/lib/libkyahoo.so.1
 QMetaObject::activate(QObject*, int, int, void**) ()
 KJob::result(KJob*) () from /usr/lib/libkdecore.so.5
Title: kopete crashed with SIGSEGV in KIO::TransferJob::isErrorPage()
Uname: Linux 2.6.31-4-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

desert rover (desertrover) wrote :

StacktraceTop:KIO::FileUndoManager::undo (this=0x1cdaec0)
QMapData::shared_null ()
?? ()
?? ()
resetCodecConverterStateHelper (state=0x1a44850)

Changed in kdenetwork (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugs.kde.org/show_bug.cgi?id=200186

visibility: private → public
Changed in kdenetwork (Ubuntu):
importance: Medium → Low
status: New → Triaged
Changed in kdenetwork:
status: Unknown → Confirmed
summary: - kopete crashed while running firefox
+ kopete crashed with SIGSEGV in KIO::TransferJob::isErrorPage()
Changed in kdenetwork (Ubuntu):
importance: Low → Medium
Download full text (6.5 KiB)

Application: kopete (1.0.0)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
I opened Kopete, as it began its mass of notifications, it crashed. it does this often, i dont think it was the notifications that did it.

 -- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
[Current thread is 1 (Thread 0xb781c730 (LWP 31791))]

Thread 2 (Thread 0xb5024b70 (LWP 31792)):
#0 0x00119344 in __pthread_mutex_unlock_usercnt (mutex=0xa260e3c, decr=<value optimized out>) at pthread_mutex_unlock.c:52
#1 0x00ae1be6 in pthread_mutex_unlock (mutex=0xa260e3c) at forward.c:184
#2 0x067c0ab8 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#3 0x067c0ee9 in ?? () from /lib/libglib-2.0.so.0
#4 0x067c14b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5 0x0142d60f in QEventDispatcherGlib::processEvents (this=0xa2c0568, flags=...) at kernel/qeventdispatcher_glib.cpp:414
#6 0x01400059 in QEventLoop::processEvents (this=0xb5024270, flags=) at kernel/qeventloop.cpp:149
#7 0x014004aa in QEventLoop::exec (this=0xb5024270, flags=...) at kernel/qeventloop.cpp:201
#8 0x012fc5a8 in QThread::exec (this=0xa35c8f8) at thread/qthread.cpp:487
#9 0x013dfc1b in QInotifyFileSystemWatcherEngine::run (this=0xa35c8f8) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x012ff32e in QThreadPrivate::start (arg=0xa35c8f8) at thread/qthread_unix.cpp:248
#11 0x0011596e in start_thread (arg=0xb5024b70) at pthread_create.c:300
#12 0x00ad4a4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb781c730 (LWP 31791)):
[KCrash Handler]
#6 0x0033609a in KIO::TransferJob::isErrorPage (this=0xa5d8098) at ../../kio/kio/job.cpp:1183
#7 0x01bf6dc9 in YABTask::qt_metacall (this=0xa5d8098, _c=172566896, _id=10, _a=0xbfb405f8) at ./yabtask.moc:83
#8 0x01406c9a in QMetaObject::metacall (object=0xa5d8098, cl=3216246264, idx=10, argv=0xbfb405f8) at kernel/qmetaobject.cpp:237
#9 0x014153d5 in QMetaObject::activate (sender=0xa492970, m=0x803c88, local_signal_index=3, argv=0xbfb405f8) at kernel/qobject.cpp:3293
#10 0x00695183 in KJob::result (this=0xa492970, _t1=0xa492970) at ./kjob.moc:194
#11 0x006954e8 in KJob::emitResult (this=0xa492970) at ../../kdecore/jobs/kjob.cpp:312
#12 0x0033ef30 in KIO::SimpleJob::slotFinished (this=0xa492970) at ../../kio/kio/job.cpp:486
#13 0x0033f96d in KIO::TransferJob::slotFinished (this=0xa492970) at ../../kio/kio/job.cpp:1058
#14 0x0033d343 in KIO::TransferJob::qt_metacall (this=0xa492970, _c=QMetaObject::InvokeMetaMethod, _id=47, _a=0xbfb4088c) at ./jobclasses.moc:367
#15 0x01406c9a in QMetaObject::metacall (object=0xa492970, cl=3216246264, idx=47, argv=0xbfb4088c) at kernel/qmetaobject.cpp:237
#16 0x014153d5 in QMetaObject::activate (sender=0xa39b7d8, m=0x4edf44, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3293
#17 0x00409707 in KIO::SlaveInterface::finished (this=0xa39b7d8) at ./slaveinterface.moc:171
#18 0x0040ca2d in KIO::SlaveInterface::dispatch (this=0xa39b7d8, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#19 0x00409bc3 in KIO::SlaveInterface::dispatch...

Read more...

*** Bug 250587 has been marked as a duplicate of this bug. ***

*** Bug 249623 has been marked as a duplicate of this bug. ***

*** Bug 251306 has been marked as a duplicate of this bug. ***

*** Bug 251633 has been marked as a duplicate of this bug. ***

Can you run "kdebugdialog", search for kopete or yahoo and select all yahoo-related debug areas (as for me, it is 14180 and 14181); and then run kopete using "kopete >kopete.log 2>&1" command and attach kopete.log when it will crash with this backtrace? Thanks in advance.

*** Bug 252770 has been marked as a duplicate of this bug. ***

*** Bug 252880 has been marked as a duplicate of this bug. ***

SVN commit 1181622 by poboiko:

Add null pointer check
CCBUG: 250586

 M +1 -1 yabtask.cpp

WebSVN link: http://websvn.kde.org/?view=rev&revision=1181622

SVN commit 1181623 by poboiko:

Backporting commit 1181622
Add null pointer check
CCBUG: 250586

 M +1 -1 yabtask.cpp

WebSVN link: http://websvn.kde.org/?view=rev&revision=1181623

Please check KDE SC 4.5.2 which will be released 5th October (or subversion trunk, if you want). If it won't be fixed there, please reopen this bug. I cannot test because this bug isn't seem to be reproducible for me.

We already tagged 4.5.2 before your commit, so make that 4.5.3.

*** Bug 253407 has been marked as a duplicate of this bug. ***

*** Bug 200186 has been marked as a duplicate of this bug. ***

Created attachment 52540
New crash information added by DrKonqi

kopete (1.0.80) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:

Startup of kopete in Ubuntu Maverick with all updates installed (October 15, 2010).

-- Backtrace (Reduced):
#6 0x00007f9c4824aec4 in KIO::TransferJob::isErrorPage (this=0x1f82470) at ../../kio/kio/job.cpp:1236
#7 0x00007f9c2eec0f91 in YABTask::slotResult (this=0x2609ce0, job=0x1f52920) at ../../../../../kopete/protocols/yahoo/libkyahoo/yabtask.cpp:116
#8 0x00007f9c2eec19e5 in YABTask::qt_metacall (this=0x2609ce0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff9d0321f0) at ./yabtask.moc:83
[...]
#10 0x00007f9c47782712 in KJob::result (this=0x1f82470, _t1=0x1f52920) at ./kjob.moc:194
#11 0x00007f9c477829b0 in KJob::emitResult (this=0x1f52920) at ../../kdecore/jobs/kjob.cpp:312

Changed in kdenetwork:
status: Confirmed → Unknown

*** Bug 256036 has been marked as a duplicate of this bug. ***

This is reported as fixed in version 4.5.3 but I'm still getting arbitrary crashes in kopete, see bug 256036.

I will send the requested log file the next time it crashes.

Created attachment 53148
possible fix

Could anyone (who have this bug) compile kopete with attached patch and check if it fixes this bug? I can't reproduce it, so I can't test it :(

*** Bug 256114 has been marked as a duplicate of this bug. ***

Created attachment 53154
possible fix

I was totally wrong about previous fixes. Looks like the problem is that YABTask overrides TransferJob's default slotResult and slotData functions. And because of it, slotResult calls twice (first call is in TransferJob, second - because of signal), and it makes some problems. So maybe renaming these functions in YABTask will help. Please, can anyone check my guess with attached patch?

*** Bug 254723 has been marked as a duplicate of this bug. ***

*** Bug 256537 has been marked as a duplicate of this bug. ***

*** Bug 256076 has been marked as a duplicate of this bug. ***

Created attachment 53315
Useful kopete.log related to this crash (from bug 256076)

*** Bug 256578 has been marked as a duplicate of this bug. ***

*** Bug 256539 has been marked as a duplicate of this bug. ***

*** Bug 256972 has been marked as a duplicate of this bug. ***

*** Bug 257019 has been marked as a duplicate of this bug. ***

*** Bug 256543 has been marked as a duplicate of this bug. ***

Created attachment 53530
New crash information added by DrKonqi

kopete (1.0.80) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:
Had just logged in. Kopete was connecting to my accounts.
- Custom settings of the application:
Five accounts: MSN, Jabber, ICQ, AIM, YIM

-- Backtrace (Reduced):
#6 0x00007fe721325ec4 in KIO::TransferJob::isErrorPage (this=0x255d350) at ../../kio/kio/job.cpp:1236
#7 0x00007fe707028f91 in YABTask::slotResult (this=0x1bfca40, job=0x242dc20) at ../../../../../kopete/protocols/yahoo/libkyahoo/yabtask.cpp:116
#8 0x00007fe7070299e5 in YABTask::qt_metacall (this=0x1bfca40, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff6dd09df0) at ./yabtask.moc:83
[...]
#10 0x00007fe72085d712 in KJob::result (this=0x255d350, _t1=0x242dc20) at ./kjob.moc:194
#11 0x00007fe72085d9b0 in KJob::emitResult (this=0x242dc20) at ../../kdecore/jobs/kjob.cpp:312

[Comment from a bug triager]
From bug 257393:
-- Information about the crash:
Went into suspend and went somewhere else with a different wifi network. coming
out of suspend kopete woke up and tried to connect before the wireless
reconnected to the different network and immediately crashed.

*** Bug 257393 has been marked as a duplicate of this bug. ***

*** Bug 258309 has been marked as a duplicate of this bug. ***

*** Bug 258404 has been marked as a duplicate of this bug. ***

*** Bug 259030 has been marked as a duplicate of this bug. ***

*** Bug 259637 has been marked as a duplicate of this bug. ***

*** Bug 260770 has been marked as a duplicate of this bug. ***

[Comment from a bug triager]
From bug 259030 (KDE SC 4.6beta1):

[KCrash Handler]
#7 0xb746d59a in KIO::TransferJob::isErrorPage (this=0x941f5d0) at
../../kio/kio/job.cpp:1247
#8 0xaf2e2129 in YABTask::qt_metacall (this=0x941f5d0, _c=153157680, _id=10,
_a=0xbfcb7a78) at ./yabtask.moc:83
#9 0xb6be98ca in QMetaObject::metacall (object=0x941f5d0, cl=3217783416,
idx=10, argv=0xbfcb7a78) at kernel/qmetaobject.cpp:237
#10 0xb6bfc6ad in QMetaObject::activate (sender=0x9210030, m=0xb6fb5568,
local_signal_index=3, argv=0x1) at kernel/qobject.cpp:3280
#11 0xb6e35183 in KJob::result (this=0x9210030, _t1=0x9210030) at
./kjob.moc:194
#12 0xb6e354e8 in KJob::emitResult (this=0x9210030) at
../../kdecore/jobs/kjob.cpp:312
#13 0xb74768c0 in KIO::SimpleJob::slotFinished (this=0x9210030) at
../../kio/kio/job.cpp:525
#14 0xb747721c in KIO::TransferJob::slotFinished (this=0x9210030) at
../../kio/kio/job.cpp:1118
#15 0xb7474ac3 in KIO::TransferJob::qt_metacall (this=0x9210030,
_c=QMetaObject::InvokeMetaMethod, _id=47, _a=0xbfcb7d2c) at
./jobclasses.moc:367

*** Bug 260901 has been marked as a duplicate of this bug. ***

*** Bug 261431 has been marked as a duplicate of this bug. ***

Created attachment 55346
New crash information added by DrKonqi

Kopete crashed while it was idle for several days. It probably relogged in several times due to disconnects from my internet provider.

*** Bug 262362 has been marked as a duplicate of this bug. ***

Created attachment 56405
New crash information added by DrKonqi

kopete (1.0.80) on KDE Platform 4.5.95 (4.6 RC2) using Qt 4.7.1

- What I was doing when the application crashed:

Opensuse 11.4 factory - KDE SC 4.6 RC2 - Yahoo is configured - login - does not always happen but regularily

-- Backtrace (Reduced):
#6 KIO::TransferJob::isErrorPage (this=0xc05f70) at /usr/src/debug/kdelibs-4.5.95/kio/kio/job.cpp:1247
#7 0x00007f5d84ad0cc3 in YABTask::slotResult (this=0xbf9700, job=0x926700) at /usr/src/debug/kdenetwork-4.5.95/kopete/protocols/yahoo/libkyahoo/yabtask.cpp:116
#8 0x00007f5d84ad16df in YABTask::qt_metacall (this=0xbf9700, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff403d650) at /usr/src/debug/kdenetwork-4.5.95/build/kopete/protocols/yahoo/libkyahoo/yabtask.moc:83
[...]
#10 0x00007f5d9f2ea362 in KJob::result (this=<value optimized out>, _t1=0x926700) at /usr/src/debug/kdelibs-4.5.95/build/kdecore/kjob.moc:194
#11 0x00007f5d9f2ea3a0 in KJob::emitResult (this=0x926700) at /usr/src/debug/kdelibs-4.5.95/kdecore/jobs/kjob.cpp:312

Created attachment 56410
New crash information added by DrKonqi

kopete (1.0.80) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:

Logged in to the PC. Kopete was connecting to each protocol, and then decided to crash.

-- Backtrace (Reduced):
#6 0x00007f3ab445fec4 in KIO::TransferJob::isErrorPage (this=0x1385fd0) at ../../kio/kio/job.cpp:1236
#7 0x00007f3a9a15cf91 in YABTask::slotResult (this=0x1448df0, job=0x19c3f60) at ../../../../../kopete/protocols/yahoo/libkyahoo/yabtask.cpp:116
#8 0x00007f3a9a15d9e5 in YABTask::qt_metacall (this=0x1448df0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffffd8ddeb0) at ./yabtask.moc:83
[...]
#10 0x00007f3ab3997712 in KJob::result (this=0x1385fd0, _t1=0x19c3f60) at ./kjob.moc:194
#11 0x00007f3ab39979b0 in KJob::emitResult (this=0x19c3f60) at ../../kdecore/jobs/kjob.cpp:312

Created attachment 56419
New crash information added by DrKonqi

kopete (1.0.80) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed:

Logged in to the computer. Kopete started up, then crashed as it tried to sign in to my accounts.

-- Backtrace (Reduced):
#6 0x00007f1bb8c93ec4 in KIO::TransferJob::isErrorPage (this=0x2a2ce90) at ../../kio/kio/job.cpp:1236
#7 0x00007f1b9e990f91 in YABTask::slotResult (this=0x2a2bd80, job=0x2b76230) at ../../../../../kopete/protocols/yahoo/libkyahoo/yabtask.cpp:116
#8 0x00007f1b9e9919e5 in YABTask::qt_metacall (this=0x2a2bd80, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff391427d0) at ./yabtask.moc:83
[...]
#10 0x00007f1bb81cb712 in KJob::result (this=0x2a2ce90, _t1=0x2b76230) at ./kjob.moc:194
#11 0x00007f1bb81cb9b0 in KJob::emitResult (this=0x2b76230) at ../../kdecore/jobs/kjob.cpp:312

I confirm the bug still exists in kopete 1.0.80 with KDE 4.5.95 (4.6 RC2)

*** Bug 263866 has been marked as a duplicate of this bug. ***

Created attachment 56868
New crash information added by DrKonqi

kopete (1.0.80) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.0

- What I was doing when the application crashed:

- Unusual behavior I noticed: Crash happened after reconnecting (automatically) when network conntection was lost before.

-- Backtrace (Reduced):
#7 0xb72d0dca in KIO::TransferJob::isErrorPage (this=0xc575b30) at ../../kio/kio/job.cpp:1247
#8 0xaf2f3119 in YABTask::qt_metacall (this=0xc575b30, _c=264944448, _id=10, _a=0xbfcf1518) at ./yabtask.moc:83
[...]
#11 0xb6c90da3 in KJob::result (this=0xfcabb40, _t1=0xfcabb40) at ./kjob.moc:194
#12 0xb6c91108 in KJob::emitResult (this=0xfcabb40) at ../../kdecore/jobs/kjob.cpp:312
#13 0xb72da0f0 in KIO::SimpleJob::slotFinished (this=0xfcabb40) at ../../kio/kio/job.cpp:525

Changed in kdenetwork:
importance: Unknown → High
status: Unknown → Invalid

[Comment from a bug triager]
From bug 265849 (KDE SC 4.5.1):
-- Information about the crash:
I was open Kopete, and after a session, i change the status to offline. At the
new change of the status to online, the software is crashed

From bug 266459 (KDE SC 4.6.0):
- What I was doing when the application crashed:
kopete was just running in systray, connected to
jabber,gtalk,icq,skype,facebook,msn.
My internet connection here is flacky so wicd keeps reconnecting very ofthen
(once in 1-4 minutes).
No issues with kopete lately, setting status to offline and back online works
ok, it's not the case probably.

From bug 267318 (KDE SC 4.6.0):
- What I was doing when the application crashed:
just reconnected on wifi from suspend and kopete crashed suddenly.

*** Bug 265847 has been marked as a duplicate of this bug. ***

*** Bug 265849 has been marked as a duplicate of this bug. ***

*** Bug 266459 has been marked as a duplicate of this bug. ***

*** Bug 267313 has been marked as a duplicate of this bug. ***

*** Bug 267318 has been marked as a duplicate of this bug. ***

Has anybody here tested the possible in comment #19? I do not have a yahoo account to test it myself.

*** Bug 270710 has been marked as a duplicate of this bug. ***

*** Bug 271809 has been marked as a duplicate of this bug. ***

Changed in kdenetwork:
importance: High → Unknown
status: Invalid → Unknown
Changed in kdenetwork:
importance: Unknown → High
status: Unknown → New

*** Bug 280929 has been marked as a duplicate of this bug. ***

*** Bug 276651 has been marked as a duplicate of this bug. ***

*** Bug 280183 has been marked as a duplicate of this bug. ***

Hello from the KDE Bugsquad!

Unfortunately, Yahoo has discontinued the Yahoo Messenger service, and the code has been removed from Kopete.

Thus, I am closing this bug as "UNMAINTAINED" since it will no longer be fixable, or able to operate due to Yahoo.

Wow. Are you kidding me? It took you 8 years and a week to do nothing? I'm sure glad I'm not using this software anymore. And I wouldn't wonder if no one would want to file any bug against it..

Changed in kdenetwork:
status: New → Unknown
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.