[kopete-bugs] [Bug 179985] New: crash: Program received signal SIGSEGV, Segmentation fault.
Erica
housiemousie2 at suddenlink.net
Thu Jan 8 04:45:14 CET 2009
http://bugs.kde.org/show_bug.cgi?id=179985
Summary: crash: Program received signal SIGSEGV, Segmentation
fault.
Product: kopete
Version: 0.12.7
Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kopete-bugs at kde.org
ReportedBy: housiemousie2 at suddenlink.net
Version: 0.12.7 (using KDE 3.5.10)
OS: Linux
Installed from: Ubuntu Packages
Kubuntu, Hardy Heron, all updates applied. nVidia driver taints kernel,
driver: NVIDIA-Linux-x86-177.82-pkg1, from nVidia web site.
Programs always open:
Ktouch
Thunderbird mail
Amarok
Knetwalk
Usually Firefox is also open.
Kopete plugins:
History
Now Listening
This crash of Kopete does not happen frequently. This last time it took over
24 hours to catch a crash with GDB.
It may be incidental that it most often happens when I am away from my computer
and the machine is sitting idle... since I am often away.
I can not be sure what was happening during those times when I was away, but in
those times when I have been at my machine, it seems to happen after a
disconnect from the Yahoo server, when it is trying to automatically reconnect.
This last time, for which I have the GDB backtrace and nothing else, a white
field was left on my desktop. The white field was non-responsive and did not
go away with a 'Refresh Desktop.' This was new, since before I would get a
window from the crash handler... and no white field.
This white field was the size, shape and placement of the pop up window that
informs the user of mail on the Yahoo server... the placement for the notices
of a disconnect is different... the shape is different for an incoming message.
I'm sorry I can't tell you how to make it fail, I know you don't like to hear
that. But it does not fail every time it tries to reconnect. Sometimes it
will fail while I am in a chat, usually not and with no chats open sitting
idle.
Usually my status message is Idle... because I have done nothing with Kopete
for the required length of time... I have not noticed if setting the status
message manually has had any effect.
With some disconnects I will get a message, something to the effect of, failed
name look up... and while it will not reconnect on it's own, telling it to do
so manually will bring Yahoo back up. Meaning, using the main Kopete window
and clicking any of the various 'buttons'/menus and resetting the status to
Online.
This 'failed name look up' has not caused crashes, but as it is odd behavior
and this behavior started happening about the same time the crashes did, I felt
it worth mentioning.
I left off pages of normal looking entries in the konsole, including only the
last few lines which denoted a problem, the rest is the GDB backtrace results.
kopete: WARNING: KTempFile: Error trying to create /tmp/kde-<MyUserName>/yahoob
uddyicon-XXXXXX.com/msgr/rite_write_: No such file or directory
Transfer ACCEPTED by: PictureNotifierTask
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb607e6c0 (LWP 26287)]
0xb58e0159 in YahooBuddyIconLoader::slotData ()
from /usr/lib/kde3/kopete_yahoo.so
(gdb) thread apply all backtrace
Thread 46 (Thread 0xb56a7b90 (LWP 347)):
#0 0xb7f93410 in __kernel_vsyscall ()
#1 0xb634fdd2 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb6c151d8 in QWaitCondition::wait (this=0x846be14, mutex=0x846be1c,
time=2000) at tools/qwaitcondition_unix.cpp:304
#3 0xb70bcd53 in KNetwork::Internal::KResolverManager::requestData (
this=0x846be08, th=0x9059268, maxWaitTime=2000)
at /build/buildd/kdelibs-3.5.10/./kdecore/network/kresolvermanager.cpp:378
#4 0xb70cacbc in KNetwork::Internal::KResolverThread::run (this=0x9059268)
at /build/buildd/kdelibs-3.5.10/./kdecore/network/kresolvermanager.cpp:271
#5 0xb68c2e47 in QThreadInstance::start (_arg=0x9056474)
at kernel/qthread_unix.cpp:122
#6 0xb634b4fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0xb61a1e5e in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 45 (Thread 0xb4cffb90 (LWP 346)):
#0 0xb7f93410 in __kernel_vsyscall ()
#1 0xb634fdd2 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb6c151d8 in QWaitCondition::wait (this=0x846be14, mutex=0x846be1c,
time=2000) at tools/qwaitcondition_unix.cpp:304
---Type <return> to continue, or q <return> to quit---
#3 0xb70bcd53 in KNetwork::Internal::KResolverManager::requestData (
this=0x846be08, th=0x86618e0, maxWaitTime=2000)
at /build/buildd/kdelibs-3.5.10/./kdecore/network/kresolvermanager.cpp:378
#4 0xb70cacbc in KNetwork::Internal::KResolverThread::run (this=0x86618e0)
at /build/buildd/kdelibs-3.5.10/./kdecore/network/kresolvermanager.cpp:271
#5 0xb68c2e47 in QThreadInstance::start (_arg=0x8cdd1cc)
at kernel/qthread_unix.cpp:122
#6 0xb634b4fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0xb61a1e5e in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 44 (Thread 0xb44feb90 (LWP 345)):
#0 0xb7f93410 in __kernel_vsyscall ()
#1 0xb634fdd2 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb6c151d8 in QWaitCondition::wait (this=0x846be14, mutex=0x846be1c,
time=2000) at tools/qwaitcondition_unix.cpp:304
#3 0xb70bcd53 in KNetwork::Internal::KResolverManager::requestData (
this=0x846be08, th=0x832cd60, maxWaitTime=2000)
at /build/buildd/kdelibs-3.5.10/./kdecore/network/kresolvermanager.cpp:378
#4 0xb70cacbc in KNetwork::Internal::KResolverThread::run (this=0x832cd60)
at /build/buildd/kdelibs-3.5.10/./kdecore/network/kresolvermanager.cpp:271
#5 0xb68c2e47 in QThreadInstance::start (_arg=0x83436bc)
at kernel/qthread_unix.cpp:122
---Type <return> to continue, or q <return> to quit---
#6 0xb634b4fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7 0xb61a1e5e in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 1 (Thread 0xb607e6c0 (LWP 26287)):
#0 0xb58e0159 in YahooBuddyIconLoader::slotData ()
from /usr/lib/kde3/kopete_yahoo.so
#1 0xb58e01c7 in YahooBuddyIconLoader::qt_invoke ()
from /usr/lib/kde3/kopete_yahoo.so
#2 0xb6936704 in QObject::activate_signal (this=0xb33c4020, clist=0xb4d2bb90,
o=0xbffb8290) at kernel/qobject.cpp:2359
#3 0xb7537dcd in KIO::TransferJob::data (this=0xb33c4020, t0=0xb33c4020,
t1=@0xbffb8540) at ./jobclasses.moc:993
#4 0xb7537e38 in KIO::TransferJob::slotData (this=0xb33c4020,
_data=@0xbffb8540) at /build/buildd/kdelibs-3.5.10/./kio/kio/job.cpp:933
#5 0xb757f659 in KIO::TransferJob::qt_invoke (this=0xb33c4020, _id=18,
_o=0xbffb8384) at ./jobclasses.moc:1072
#6 0xb6936704 in QObject::activate_signal (this=0xb31e5fa0, clist=0xb2d908d8,
o=0xbffb8384) at kernel/qobject.cpp:2359
#7 0xb75361ae in KIO::SlaveInterface::data (this=0xb31e5fa0, t0=@0xbffb8540)
at ./slaveinterface.moc:194
#8 0xb757ee89 in KIO::SlaveInterface::dispatch (this=0xb31e5fa0, _cmd=100,
rawdata=@0xbffb8540)
at /build/buildd/kdelibs-3.5.10/./kio/kio/slaveinterface.cpp:234
---Type <return> to continue, or q <return> to quit---
#9 0xb75a0e4a in KIO::SlaveInterface::dispatch (this=0xb31e5fa0)
at /build/buildd/kdelibs-3.5.10/./kio/kio/slaveinterface.cpp:173
#10 0xb7547d7c in KIO::Slave::gotInput (this=0xb31e5fa0)
at /build/buildd/kdelibs-3.5.10/./kio/kio/slave.cpp:300
#11 0xb7576278 in KIO::Slave::qt_invoke (this=0xb31e5fa0, _id=4, _o=0xbffb8640)
at ./slave.moc:113
#12 0xb6936704 in QObject::activate_signal (this=0xb39730f0, clist=0xb2fe31a0,
o=0xbffb8640) at kernel/qobject.cpp:2359
#13 0xb6937051 in QObject::activate_signal (this=0xb39730f0, signal=2,
param=16) at kernel/qobject.cpp:2452
#14 0xb6cc6b99 in QSocketNotifier::activated (this=0xb39730f0, t0=16)
at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#15 0xb6958766 in QSocketNotifier::event (this=0xb39730f0, e=0xbffb8950)
at kernel/qsocketnotifier.cpp:261
#16 0xb68cac36 in QApplication::internalNotify (this=0xbffb8c14,
receiver=0xb39730f0, e=0xbffb8950) at kernel/qapplication.cpp:2638
#17 0xb68cca5f in QApplication::notify (this=0xbffb8c14, receiver=0xb39730f0,
e=0xbffb8950) at kernel/qapplication.cpp:2361
#18 0xb708b9b2 in KApplication::notify (this=0xbffb8c14, receiver=0xb39730f0,
event=0xbffb8950)
at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550
#19 0xb685b28d in QApplication::sendEvent (receiver=0xb39730f0,
event=0xbffb8950) at ../include/qapplication.h:523
---Type <return> to continue, or q <return> to quit---
#20 0xb68bcb4a in QEventLoop::activateSocketNotifiers (this=0x812d1d8)
at kernel/qeventloop_unix.cpp:581
#21 0xb6870630 in QEventLoop::processEvents (this=0x812d1d8, flags=4)
at kernel/qeventloop_x11.cpp:386
#22 0xb68e5f90 in QEventLoop::enterLoop (this=0x812d1d8)
at kernel/qeventloop.cpp:201
#23 0xb68e5c8e in QEventLoop::exec (this=0x812d1d8)
at kernel/qeventloop.cpp:148
#24 0xb68cc7df in QApplication::exec (this=0xbffb8c14)
at kernel/qapplication.cpp:2761
#25 0x0807fc73 in ?? ()
#26 0xb60e1450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#27 0x0806f071 in ?? ()
(gdb)
Hope this helps... and isn't just a bit of weirdness on my machine and hasn't
been a waste of your time.
Thanks and best of luck!
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the kopete-bugs
mailing list