278387 – kopete (4.6.5) crashes soon after resuming from suspend when network is still down

Bug 278387 - kopete (4.6.5) crashes soon after resuming from suspend when network is still down

Summary: kopete (4.6.5) crashes soon after resuming from suspend when network is still...

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	kopete
Classification:	Unmaintained
Component:	general (other bugs)
Version First Reported In:	1.0.80
Platform:	unspecified Linux

Importance:	NOR crash
Target Milestone:	---
Assignee:	Kopete Developers

URL:
Keywords:

Depends on:
Blocks:

Reported:	2011-07-24 12:04 UTC by Silvan Calarco
Modified:	2018-11-29 04:52 UTC (History)
CC List:	0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description Silvan Calarco 2011-07-24 12:04:46 UTC

Application: kopete (1.0.80)
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.3
Operating System: Linux 2.6.38mamba i686

-- Information about the crash:
- What I was doing when the application crashed:

kopete crashes after opening the laptop to resume from suspend.

The crash can be reproduced every time.

-- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:170
	in ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S
[Current thread is 1 (Thread 0xb636fb60 (LWP 14739))]

Thread 5 (Thread 0xb35f4b70 (LWP 14761)):
#0  0x4ef3c567 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x4e155f4b in ?? () from /usr/lib/libQtCore.so.4
#2  0x4e085961 in ?? () from /usr/lib/libQtCore.so.4
#3  0x4f007dfd in start_thread (arg=0xb35f4b70) at pthread_create.c:301
#4  0x4ef4510e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 4 (Thread 0xb0137b70 (LWP 14791)):
#0  0x4e1a0733 in ?? () from /usr/lib/libQtCore.so.4
#1  0x4f315e12 in g_main_context_prepare (context=<value optimized out>, priority=0xb01371ac) at gmain.c:2762
#2  0x4f316d48 in g_main_context_iterate (context=0x8f95118, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3072
#3  0x4f317491 in g_main_context_iteration (context=0x8f95118, may_block=1) at gmain.c:3155
#4  0x4e1a0f5c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#5  0x4e174371 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#6  0x4e17460f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#7  0x410eebaf in QCA::SyncThread::run() () from /usr/lib/libqca.so.2
#8  0x4e085961 in ?? () from /usr/lib/libQtCore.so.4
#9  0x4f007dfd in start_thread (arg=0xb0137b70) at pthread_create.c:301
#10 0x4ef4510e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 3 (Thread 0xaf937b70 (LWP 14792)):
#0  0x4ef3876c in __poll (fds=0x8fb0738, nfds=1, timeout=2283) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x4f326934 in g_poll (fds=0x8fb0738, nfds=1, timeout=2283) at gpoll.c:132
#2  0x4f3170c0 in g_main_context_poll (context=0x8d80120, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3405
#3  g_main_context_iterate (context=0x8d80120, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3087
#4  0x4f317491 in g_main_context_iteration (context=0x8d80120, may_block=1) at gmain.c:3155
#5  0x4e1a0f5c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#6  0x4e174371 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#7  0x4e17460f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#8  0xb23788a1 in XMPP::SyncThread::run() () from /opt/kde/lib/kde4/kopete_jabber.so
#9  0x4e085961 in ?? () from /usr/lib/libQtCore.so.4
#10 0x4f007dfd in start_thread (arg=0xaf937b70) at pthread_create.c:301
#11 0x4ef4510e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 2 (Thread 0xae937b70 (LWP 17493)):
[KCrash Handler]
#6  __libc_res_nquery (statp=0xae937df4, name=0x8b5af88 "login.icq.com", class=1, type=62321, answer=0xae936280 "\002", anslen=2048, answerp=0xae936abc, answerp2=0xae936ab8, nanswerp2=0xae936ab4, resplen2=0xae936ab0) at res_query.c:263
#7  0x4f5bda2d in __libc_res_nquerydomain (statp=0xae937df4, name=<value optimized out>, domain=0x0, class=1, type=62321, answer=0xae936280 "\002", anslen=2048, answerp=0xae936abc, answerp2=0xae936ab8, nanswerp2=0xae936ab4, resplen2=0xae936ab0) at res_query.c:578
#8  0x4f5bdeaa in __libc_res_nsearch (statp=0xae937df4, name=0x8b5af88 "login.icq.com", class=1, type=62321, answer=0xae936280 "\002", anslen=2048, answerp=0xae936abc, answerp2=0xae936ab8, nanswerp2=0xae936ab4, resplen2=0xae936ab0) at res_query.c:378
#9  0xb0185fe1 in _nss_dns_gethostbyname4_r (name=0x8b5af88 "login.icq.com", pat=0xae936c24, buffer=0x8f567f8 "\377\002", buflen=1024, errnop=0xae936c20, herrnop=0xae936c10, ttlp=0x0) at nss_dns/dns-host.c:314
#10 0x4ef250b0 in gaih_inet (name=0x8b5af88 "login.icq.com", service=<value optimized out>, req=0xae936cf8, pai=0xae936d64, naddrs=0xae936d54) at ../sysdeps/posix/getaddrinfo.c:848
#11 0x4ef28e79 in getaddrinfo (name=0x8b5af88 "login.icq.com", service=<value optimized out>, hints=0xae936cf8, pai=0xae93722c) at ../sysdeps/posix/getaddrinfo.c:2393
#12 0x4fa671f1 in ?? () from /usr/lib/libQtNetwork.so.4
#13 0x4fa5bd79 in ?? () from /usr/lib/libQtNetwork.so.4
#14 0x4e07a7b4 in ?? () from /usr/lib/libQtCore.so.4
#15 0x4e085961 in ?? () from /usr/lib/libQtCore.so.4
#16 0x4f007dfd in start_thread (arg=0xae937b70) at pthread_create.c:301
#17 0x4ef4510e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 1 (Thread 0xb636fb60 (LWP 14739)):
#0  pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:170
#1  0x4e086074 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#2  0x4e079e6e in ?? () from /usr/lib/libQtCore.so.4
#3  0x4e07ad83 in QThreadPool::waitForDone() () from /usr/lib/libQtCore.so.4
#4  0x4fa5b0e7 in ?? () from /usr/lib/libQtNetwork.so.4
#5  0x4fa5bebd in ?? () from /usr/lib/libQtNetwork.so.4
#6  0x4fa5c19d in ?? () from /usr/lib/libQtNetwork.so.4
#7  0x4fa5c1eb in ?? () from /usr/lib/libQtNetwork.so.4
#8  0x4ee8b48f in __run_exit_handlers (status=1) at exit.c:78
#9  exit (status=1) at exit.c:100
#10 0x4e4ad8e8 in ?? () from /usr/lib/libQtGui.so.4
#11 0xb6b904fc in KApplication::xioErrhandler (this=0xbfb178d4, dpy=0x8864808) at /usr/src/debug/kdelibs-4.6.5/kdeui/kernel/kapplication.cpp:419
#12 0xb6b90534 in kde_xio_errhandler (dpy=0x8864808) at /usr/src/debug/kdelibs-4.6.5/kdeui/kernel/kapplication.cpp:126
#13 0x4f187f0d in _XIOError () from /usr/lib/libX11.so.6
#14 0x4f185875 in _XEventsQueued () from /usr/lib/libX11.so.6
#15 0x4f176495 in XEventsQueued () from /usr/lib/libX11.so.6
#16 0x4e4e6706 in ?? () from /usr/lib/libQtGui.so.4
#17 0x4f315e12 in g_main_context_prepare (context=<value optimized out>, priority=0xbfb176cc) at gmain.c:2762
#18 0x4f316d48 in g_main_context_iterate (context=0x884a208, block=1, dispatch=1, self=<value optimized out>) at gmain.c:3072
#19 0x4f317491 in g_main_context_iteration (context=0x884a208, may_block=1) at gmain.c:3155
#20 0x4e1a0f24 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#21 0x4e4e688b in ?? () from /usr/lib/libQtGui.so.4
#22 0x4e174371 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#23 0x4e17460f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#24 0x4e178f00 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#25 0x4e43a4a9 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#26 0x0805947e in main ()

Possible duplicates by query: bug 275291.

Reported using DrKonqi

Comment 1 Andrew Crouthamel 2018-10-29 22:24:46 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 2 Bug Janitor Service 2018-11-13 14:34:03 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 3 Bug Janitor Service 2018-11-29 04:52:55 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!