[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=222878

boris.big...@hotmail.com changed:

   What|Removed |Added

 CC||boris.big...@hotmail.com

--- Comment #40 from boris.big...@hotmail.com ---
Still happens with kontact 5.10.2 using kde frameworks 5.55.0.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Till Schäfer]

https://bugs.kde.org/show_bug.cgi?id=222878

Till Schäfer  changed:

   What|Removed |Added

Version|5.4.0   |5.9.2

--- Comment #39 from Till Schäfer  ---
still valid on 5.9.2 with frameworks 5.51.0 and qt 5.11.2

in the meanwhile for everybody frustrated to type killall kontact every few
hours: here is a script to detect and kill hanging kmail instances. I have just
added it to my kontact.desktop file, such that kontact just starts and does not
wait for the hanging instance. 


#!/bin/bash

pid=$(pidof kontact)

if [[ $pid != "" ]]; then 
echo "Running KMail instance found: $pid"
windowsofpid=$(xdotool search --pid $pid)
if [[ $windowsofpid == "" ]]; then
echo "Hanging KMail instance found. Killing..."
kdialog --passivepopup "Hanging KMail instance found: $pid.
Killing ..." 5 --title "Kill Hanging Kontact Script"
kill $pid
fi
fi

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Frank van Zuetphen]

https://bugs.kde.org/show_bug.cgi?id=222878

Frank van Zuetphen  changed:

   What|Removed |Added

 CC||i...@vz-it.de

--- Comment #38 from Frank van Zuetphen  ---
Yes, this bug is still present.


Debian 8
kontact 4.14.1
akonadi-server 1.13.0

Cheers,

Frank

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Till Schäfer]

https://bugs.kde.org/show_bug.cgi?id=222878

Till Schäfer  changed:

   What|Removed |Added

Version|5.3.1   |5.4.0

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Jan-Matthias Braun]

https://bugs.kde.org/show_bug.cgi?id=222878

Jan-Matthias Braun  changed:

   What|Removed |Added

 CC||jan_br...@gmx.net

--- Comment #37 from Jan-Matthias Braun  ---
And another (rather short) one for kontact 16.12.0

(gdb) bt
#0  0x7f15af07199d in poll () from /lib64/libc.so.6
#1  0x7f15a8041266 in g_main_context_iterate.isra.42.lto_priv () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f15a7fc8a3c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f15acd8e7af in QEventDispatcherGlib::processEvents (this=0x1236fd0,
flags=...) at kernel/qeventdispatcher_glib.cpp:423
#4  0x7f15acd3a7ba in QEventLoop::exec (this=this@entry=0x7fffa171af30,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f15acd42bfd in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1261
#6  0x00404203 in main (argc=, argv=) at
/var/tmp/portage/kde-apps/kontact-16.12.0/work/kontact-16.12.0/src/main.cpp:227

Cheers,

Jan

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Denis Kurz via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=222878

Denis Kurz  changed:

   What|Removed |Added

 CC||kde...@posteo.de

--- Comment #36 from Denis Kurz  ---
I run into this at least once per day, too. PIM 5.3.1, Framworks 5.26.
Backtrace of zombie kontact:

[New LWP 16622]
[New LWP 16583]
[New LWP 16580]
[New LWP 16573]
[New LWP 16559]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x003344e0868d in pthread_join (threadid=139922306430720,
thread_return=0x0) at pthread_join.c:90
90  pthread_join.c: Datei oder Verzeichnis nicht gefunden.

Thread 6 (Thread 0x7f423c4f8700 (LWP 16559)):
#0  0x0033446e046d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00384580c8f2 in poll (__timeout=-1, __nfds=1, __fds=0x7f423c4f7d00)
at /usr/include/bits/poll2.h:46
#2  _xcb_conn_wait (c=c@entry=0x1f61840, cond=cond@entry=0x1f61880,
vector=vector@entry=0x0, count=count@entry=0x0) at
/var/tmp/portage/x11-libs/libxcb-1.12/work/libxcb-1.12/src/xcb_conn.c:479
#3  0x00384580e6df in xcb_wait_for_event (c=0x1f61840) at
/var/tmp/portage/x11-libs/libxcb-1.12/work/libxcb-1.12/src/xcb_in.c:693
#4  0x7f423d789009 in QXcbEventReader::run (this=0x1f6bef0) at
qxcbconnection.cpp:1325
#5  0x003402ea8cfc in QThreadPrivate::start (arg=0x1f6bef0) at
thread/qthread_unix.cpp:341
#6  0x003344e07444 in start_thread (arg=0x7f423c4f8700) at
pthread_create.c:334
#7  0x0033446e94cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f423917b700 (LWP 16573)):
#0  0x0033446e046d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x003346649f1c in g_main_context_poll (priority=2147483647, n_fds=2,
fds=0x7f422c003020, timeout=-1, context=0x7f422c000990) at
/var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:4135
#2  g_main_context_iterate (context=context@entry=0x7f422c000990,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
/var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3835
#3  0x00334664a02c in g_main_context_iteration (context=0x7f422c000990,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3901
#4  0x003403099b07 in QEventDispatcherGlib::processEvents
(this=0x7f422c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#5  0x00340304b88a in QEventLoop::exec (this=this@entry=0x7f423917add0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x003402ea4544 in QThread::exec (this=this@entry=0x3404282240
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:500
#7  0x003404215235 in QDBusConnectionManager::run (this=0x3404282240
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:189
#8  0x003402ea8cfc in QThreadPrivate::start (arg=0x3404282240 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:341
#9  0x003344e07444 in start_thread (arg=0x7f423917b700) at
pthread_create.c:334
#10 0x0033446e94cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f42335ef700 (LWP 16580)):
#0  0x0033446e046d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x003572895e5a in content::SandboxIPCHandler::Run() () from
/usr/lib64/libQt5WebEngineCore.so.5
#2  0x00357307d61e in base::DelegateSimpleThread::Run() () from
/usr/lib64/libQt5WebEngineCore.so.5
#3  0x00357307d730 in base::SimpleThread::ThreadMain() () from
/usr/lib64/libQt5WebEngineCore.so.5
#4  0x00357307a38f in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x003344e07444 in start_thread (arg=0x7f42335ef700) at
pthread_create.c:334
#6  0x0033446e94cd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f42323e1700 (LWP 16583)):
#0  0x0033446e2163 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x003573042894 in base::(anonymous
namespace)::InotifyReaderCallback(base::(anonymous namespace)::InotifyReader*,
int, int) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x0035730a36b1 in base::debug::TaskAnnotator::RunTask(char const*, char
const*, base::PendingTask const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x0035730523d1 in base::MessageLoop::RunTask(base::PendingTask const&)
() from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x0035730526b1 in
base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) () from
/usr/lib64/libQt5WebEngineCore.so.5
#5  0x0035730530ab in base::MessageLoop::DoWork() () from
/usr/lib64/libQt5WebEngineCore.so.5
#6  0x003573055579 in
base::MessagePumpDefault::Run(base::MessagePump::Delegate*) () from

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Till Schäfer via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=222878

Till Schäfer  changed:

   What|Removed |Added

Version|4.12.2  |5.3.1
 Status|NEEDSINFO   |CONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #35 from Till Schäfer  ---
still valid for 5.3.1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Anthony Messina via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=222878

Anthony Messina  changed:

   What|Removed |Added

 CC|amess...@messinet.com   |

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Denis Kurz via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=222878

Denis Kurz  changed:

   What|Removed |Added

 Status|CONFIRMED   |NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #34 from Denis Kurz  ---
This bug has only been reported for versions before 4.14, which have been
unsupported for at least two years now. Can anyone tell if this bug still
present?

If noone confirms this bug for a Framework-based version of kontact (version
5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in
about three months.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Khumba]

https://bugs.kde.org/show_bug.cgi?id=222878

Khumba kde-bugs-68...@khumba.net changed:

   What|Removed |Added

 CC||kde-bugs-68...@khumba.net

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Alexander Stein]

https://bugs.kde.org/show_bug.cgi?id=222878

--- Comment #33 from Alexander Stein alexander...@web.de ---
Unfortunately this hasn't gone yet :(
Here I have the backtraces of all this existing threads of kontact after
closing it:
(gdb) info threads
  Id   Target Id Frame 
  4Thread 0x7f4f92048700 (LWP 12365) kontact 0x7f4fa1583fdc in
pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
  3Thread 0x7f4f91747700 (LWP 12370) QThread 0x7f4fa6d6213d in poll
() from /lib64/libc.so.6
  2Thread 0x7f4f42601700 (LWP 22120) QInotifyFileSys 0x7f4fa6d6213d
in poll () from /lib64/libc.so.6
* 1Thread 0x7f4fa99db780 (LWP 11840) kontact 0x7f4fa6d6213d in poll
() from /lib64/libc.so.6
(gdb) bt
#0  0x7f4fa6d6213d in poll () from /lib64/libc.so.6
#1  0x7f4fa05366bc in g_main_context_poll (n_fds=11, fds=0x56d72d0,
timeout=15012, context=0x22430b0, priority=optimized out) at
/var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:4007
#2  g_main_context_iterate (context=context@entry=0x22430b0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at
/var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3708
#3  0x7f4fa05367ec in g_main_context_iteration (context=0x22430b0,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3774
#4  0x7f4fa828e10e in QEventDispatcherGlib::processEvents (this=0x223e680,
flags=...) at kernel/qeventdispatcher_glib.cpp:427
#5  0x7f4fa75c5126 in QGuiEventDispatcherGlib::processEvents
(this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#6  0x7f4fa825ba2f in QEventLoop::processEvents
(this=this@entry=0x7fff27fd22c0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f4fa825bd0d in QEventLoop::exec (this=this@entry=0x7fff27fd22c0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f4fa8261d2b in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1221
#9  0x7f4fa75158bc in QApplication::exec () at kernel/qapplication.cpp:3823
#10 0x004039d9 in main (argc=3, argv=0x7fff27fd25a8) at
/var/tmp/portage/kde-base/kontact-4.13.0/work/kontact-4.13.0/kontact/src/main.cpp:219
(gdb) thread 2
[Switching to thread 2 (Thread 0x7f4f42601700 (LWP 22120))]
#0  0x7f4fa6d6213d in poll () from /lib64/libc.so.6
(gdb) bt
#0  0x7f4fa6d6213d in poll () from /lib64/libc.so.6
#1  0x7f4fa05366bc in g_main_context_poll (n_fds=2, fds=0x7f4f3c0029b0,
timeout=-1, context=0x7f4f3c0009a0, priority=optimized out)
at
/var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:4007
#2  g_main_context_iterate (context=context@entry=0x7f4f3c0009a0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out)
at
/var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3708
#3  0x7f4fa05367ec in g_main_context_iteration (context=0x7f4f3c0009a0,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3774
#4  0x7f4fa828e10e in QEventDispatcherGlib::processEvents
(this=0x7f4f3c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#5  0x7f4fa825ba2f in QEventLoop::processEvents
(this=this@entry=0x7f4f42600e20, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f4fa825bd0d in QEventLoop::exec (this=this@entry=0x7f4f42600e20,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7f4fa8149f96 in QThread::exec (this=this@entry=0x2d8d280) at
thread/qthread.cpp:536
#8  0x7f4fa823b1f8 in QInotifyFileSystemWatcherEngine::run (this=0x2d8d280)
at io/qfilesystemwatcher_inotify.cpp:256
#9  0x7f4fa814c4dc in QThreadPrivate::start (arg=0x2d8d280) at
thread/qthread_unix.cpp:338
#10 0x7f4fa1580033 in start_thread () from /lib64/libpthread.so.0
#11 0x7f4fa6d6bf0d in clone () from /lib64/libc.so.6
(gdb) thread 3
[Switching to thread 3 (Thread 0x7f4f91747700 (LWP 12370))]
#0  0x7f4fa6d6213d in poll () from /lib64/libc.so.6
(gdb) bt
#0  0x7f4fa6d6213d in poll () from /lib64/libc.so.6
#1  0x7f4fa05366bc in g_main_context_poll (n_fds=1, fds=0x7f4f8c0029c0,
timeout=-1, context=0x7f4f8c0009a0, priority=optimized out)
at
/var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:4007
#2  g_main_context_iterate (context=context@entry=0x7f4f8c0009a0,
block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out)
at
/var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3708
#3  0x7f4fa05367ec in g_main_context_iteration (context=0x7f4f8c0009a0,
may_block=1) at
/var/tmp/portage/dev-libs/glib-2.38.2-r1/work/glib-2.38.2/glib/gmain.c:3774
#4  0x7f4fa828e0e3 in QEventDispatcherGlib::processEvents
(this=0x7f4f8c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f4fa825ba2f in QEventLoop::processEvents
(this=this@entry=0x7f4f91746e60, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f4fa825bd0d in QEventLoop::exec (this=this@entry=0x7f4f91746e60,
flags=...) at kernel/qeventloop.cpp:204
#7  

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Colin J Thomson]

https://bugs.kde.org/show_bug.cgi?id=222878

Colin J Thomson co...@g6avk.demon.co.uk changed:

   What|Removed |Added

 CC|co...@g6avk.demon.co.uk |

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Till Schäfer]

https://bugs.kde.org/show_bug.cgi?id=222878

--- Comment #31 from Till Schäfer till2.schae...@uni-dortmund.de ---
this is also fixed for me. no more killall kontact ;-)

gentoo linux + kmail 4.13.0 + akonadi server 1.12.1

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Laurent RINEAU]

https://bugs.kde.org/show_bug.cgi?id=222878

--- Comment #32 from Laurent RINEAU laurent.rineau__...@normalesup.org ---
I use 4.13 - Fedora20, and I still have the DrKonqi popup, about a crash of
Kontact, when I quit my KDE session. I do not know if that is the same bug. The
issue is that, when I quit the session, the DrKonqi is killed before I have
time to get the stack trace and fill a bug report. Do you see a way to debug my
issue?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[piedro]

https://bugs.kde.org/show_bug.cgi?id=222878

piedro piedro.kul...@googlemail.com changed:

   What|Removed |Added

 CC||piedro.kul...@googlemail.co
   ||m

--- Comment #27 from piedro piedro.kul...@googlemail.com ---
same here on arch and KDE 4.12.4 

p.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Eugene Shalygin]

https://bugs.kde.org/show_bug.cgi?id=222878

--- Comment #28 from Eugene Shalygin eugene.shalygin+bugzilla@gmail.com 
---
The problem seems to be fixed in KDEPim 4.12.97/Akonadi server 1.12

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[piedro]

https://bugs.kde.org/show_bug.cgi?id=222878

--- Comment #29 from piedro piedro.kul...@googlemail.com ---
That sounds great, I am using Arch as mentioned, is it save to update yet?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Colin J Thomson]

https://bugs.kde.org/show_bug.cgi?id=222878

--- Comment #30 from Colin J Thomson co...@g6avk.demon.co.uk ---
Seems fixed now, 4.13 - Fedora20

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Eugene Shalygin]

https://bugs.kde.org/show_bug.cgi?id=222878

Eugene Shalygin eugene.shalygin+bugzilla@gmail.com changed:

   What|Removed |Added

 CC||eugene.shalygin+bugzilla.kd
   ||e...@gmail.com

--- Comment #26 from Eugene Shalygin eugene.shalygin+bugzilla@gmail.com 
---
Problem with KMail still exists in 4.12.80

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Johannes Huber]

https://bugs.kde.org/show_bug.cgi?id=222878

Johannes Huber j...@gentoo.org changed:

   What|Removed |Added

 CC||j...@gentoo.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Till Schäfer]

https://bugs.kde.org/show_bug.cgi?id=222878

Till Schäfer till2.schae...@uni-dortmund.de changed:

   What|Removed |Added

 CC||till2.schaefer@uni-dortmund
   ||.de

--- Comment #24 from Till Schäfer till2.schae...@uni-dortmund.de ---
same here on gentoo with kde 4.12.2

i guess this is a kmail problem, because kmail shows the same symptoms on my
system. 

i opened a gentoo bug before: https://bugs.gentoo.org/show_bug.cgi?id=498066


~ $ kmail --nofork
Fontconfig warning: /etc/fonts/conf.d/50-user.conf, line 14: reading
configurations from ~/.fonts.conf is deprecated.
kmail2(8690) KDirWatch::removeDir: doesn't know
/home/till/.kde4/share/apps/messageviewer/themes/ 
kmail2(8690) KDirWatch::removeDir: doesn't know
/usr/share/apps/messageviewer/themes/ 
kmail2(8690): lastUpdate - conversion of -4713,1,1,0,0,0 to QDateTime
failed 
kmail2(8690): lastUpdate - conversion of -4713,1,1,0,0,0 to QDateTime
failed 
kmail2(8690)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
kmail2(8690)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:

^C
--

the last two lines are printed after quit. but nothing special pops up. is
there a way to get more information?

this bug only affects one off my two machines. however i cant tell the
difference. 


strace after process quit:

$ strace -p 4119
Process 4119 attached
restart_syscall(... resuming interrupted call ...) = 0
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN},
{fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=15, events=POLLIN}, {fd=16,
events=POLLIN}, {fd=27, events=POLLIN}, {fd=22, events=POLLIN}], 9, 1708) = 0
(Timeout)
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN},
{fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=15, events=POLLIN}, {fd=16,
events=POLLIN}, {fd=27, events=POLLIN}, {fd=22, events=POLLIN}], 9, 59998) = 1
([{fd=7, revents=POLLIN}])
recvfrom(7, \v\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0,
4096, 0, NULL, NULL) = 32
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN},
{fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=15, events=POLLIN}, {fd=16,
events=POLLIN}, {fd=27, events=POLLIN}, {fd=22, events=POLLIN}], 9, 50960) = 1
([{fd=7, revents=POLLIN}])
recvfrom(7, \v\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0..., 4096, 0, NULL, NULL) = 64
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN},
{fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=15, events=POLLIN}, {fd=16,
events=POLLIN}, {fd=27, events=POLLIN}, {fd=22, events=POLLIN}], 9, 50945) = 1
([{fd=7, revents=POLLIN}])
recvfrom(7,
\34\0\317\243\234\0\0\0_\1\0\0\6`\273\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0,
4096, 0, NULL, NULL) = 32
recvfrom(7,
\34\0\317\243\234\0\0\0_\1\0\0\6`\273\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0...,
4096, 0, NULL, NULL) = 64
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN},
{fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=15, events=POLLIN}, {fd=16,
events=POLLIN}, {fd=27, events=POLLIN}, {fd=22, events=POLLIN}], 9, 50945) = 1
([{fd=7, revents=POLLIN}])
recvfrom(7,
\34\0\317\243\234\0\0\0\226\1\0\0\7`\273\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0...,
4096, 0, NULL, NULL) = 64
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
recvfrom(7, 0x1b138b4, 4096, 0, 0, 0)   = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN}, {fd=8, events=POLLIN}, {fd=7, events=POLLIN},
{fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=15, events=POLLIN}, {fd=16,
events=POLLIN}, 

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Till Schäfer]

https://bugs.kde.org/show_bug.cgi?id=222878

--- Comment #25 from Till Schäfer till2.schae...@uni-dortmund.de ---
@alexander stein or any admin: can you please adjust the version affected to
4.12.2

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Michael Palimaka]

https://bugs.kde.org/show_bug.cgi?id=222878

Michael Palimaka kensing...@gentoo.org changed:

   What|Removed |Added

 CC||kensing...@gentoo.org
Version|4.3 |4.12.2

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Russ Fineman]

https://bugs.kde.org/show_bug.cgi?id=222878

Russ Fineman upsc...@nwi.net changed:

   What|Removed |Added

 CC||upsc...@nwi.net

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Anthony Messina]

https://bugs.kde.org/show_bug.cgi?id=222878

Anthony Messina amess...@messinet.com changed:

   What|Removed |Added

 CC||amess...@messinet.com

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[kaeslaek]

https://bugs.kde.org/show_bug.cgi?id=222878

kaesl...@schafmail.de changed:

   What|Removed |Added

 CC||kaesl...@schafmail.de

--- Comment #23 from kaesl...@schafmail.de ---
Same here on Fedora 20, using 2 IMAP accounts and 2 pop. Have to kill kontakt
to start it again

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Laurent RINEAU]

https://bugs.kde.org/show_bug.cgi?id=222878

Laurent RINEAU laurent.rineau__...@normalesup.org changed:

   What|Removed |Added

 CC||Laurent.Rineau__kde@normale
   ||sup.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Colin J Thomson]

https://bugs.kde.org/show_bug.cgi?id=222878

Colin J Thomson co...@g6avk.demon.co.uk changed:

   What|Removed |Added

 CC||co...@g6avk.demon.co.uk

--- Comment #22 from Colin J Thomson co...@g6avk.demon.co.uk ---
I have started to see this since updating to 4.11.95/97 on Fedora 20

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

[Dennis Schridde]

https://bugs.kde.org/show_bug.cgi?id=222878

--- Comment #21 from Dennis Schridde devuran...@gmx.net ---
Persists with 4.11.0, but it seems only on the first run it will get stuck
without a visible window after closing it. When I kill it and then restart it,
it can be closed without further problems.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Dennis Schridde]

https://bugs.kde.org/show_bug.cgi?id=222878

Dennis Schridde devuran...@gmx.net changed:

   What|Removed |Added

 CC||devuran...@gmx.net

--- Comment #20 from Dennis Schridde devuran...@gmx.net ---
Still appears with Akonadi (akonadi-server-1.7.1) and Kontact / KDE 4.8.1.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Andre Heinecke]

https://bugs.kde.org/show_bug.cgi?id=222878


Andre Heinecke aheine...@intevation.de changed:

   What|Removed |Added

 CC||mephi...@gmx.net




--- Comment #19 from Andre Heinecke aheinecke intevation de  2011-07-17 
10:56:58 ---
*** Bug 276185 has been marked as a duplicate of this bug. ***

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Andre Heinecke]

https://bugs.kde.org/show_bug.cgi?id=222878





--- Comment #16 from Andre Heinecke aheinecke intevation de  2011-07-16 
11:43:09 ---
Created an attachment (id=61916)
 -- (http://bugs.kde.org/attachment.cgi?id=61916)
kill -11 of hanging kontact process without kdepim-runtime installed

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Andre Heinecke]

https://bugs.kde.org/show_bug.cgi?id=222878


Andre Heinecke aheine...@intevation.de changed:

   What|Removed |Added

 CC||aheine...@intevation.de




--- Comment #17 from Andre Heinecke aheinecke intevation de  2011-07-16 
11:43:57 ---
I do not know if this is related but i've accidentally started kontact without
kdepim-runtime installed and then i could reproduce this behavior 100%
You start Kontact, close it and the process is still around.

I've killed it with -11 (sigsev) to get a backtrace but i do not find it
paticluary useful maybe someone can see something from it so it's attached. In
Comment #16

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[David Talmage]

https://bugs.kde.org/show_bug.cgi?id=222878





--- Comment #18 from David Talmage talmage acm org  2011-07-16 12:19:55 ---
This happens with kdepim-runtime installed, too.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Christophe Giboudeaux]

https://bugs.kde.org/show_bug.cgi?id=222878


Christophe Giboudeaux cgiboude...@gmx.com changed:

   What|Removed |Added

  Attachment #61916|application/octet-stream|text/plain
  mime type||




-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Leonardo La Malfa]

https://bugs.kde.org/show_bug.cgi?id=222878


Leonardo La Malfa lamalfaleona...@gmail.com changed:

   What|Removed |Added

 CC|lamalfaleona...@gmail.com   |




-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Christophe Giboudeaux]

https://bugs.kde.org/show_bug.cgi?id=222878


Christophe Giboudeaux cgiboude...@gmx.com changed:

   What|Removed |Added

 CC||lamalfaleona...@gmail.com




--- Comment #13 from Christophe Giboudeaux cgiboudeaux gmx com  2011-07-14 
12:43:42 ---
*** Bug 242308 has been marked as a duplicate of this bug. ***

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Mike Vaughn]

https://bugs.kde.org/show_bug.cgi?id=222878





--- Comment #14 from Mike Vaughn mike vaughn 83 gmail com  2011-07-14 
14:13:09 ---
Still happening (although *maybe* slightly less consistently) on KDE SC 4.6.5
with KDE-PIM/KMail 4.6.0.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Alexander Stein]

https://bugs.kde.org/show_bug.cgi?id=222878





--- Comment #15 from Alexander Stein alexander stein informatik tu-chemnitz 
de  2011-07-14 16:42:33 ---
I still observed this running Kontact 4.6.1 now. But eventually I get a crash
report. Seems to be related to KNode somehow.

Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f3dd9684760 (LWP 3862))]

Thread 2 (Thread 0x7f3dc3412700 (LWP 3863)):
#0  0x7f3dd191c85c in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f3dd5fa4eac in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/qt4/libQtWebKit.so.4
#2  0x7f3dd5fa4ee9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib64/qt4/libQtWebKit.so.4
#3  0x7f3dd1917dba in start_thread () from /lib64/libpthread.so.0
#4  0x7f3dd6a9e02d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f3dd9684760 (LWP 3862)):
[KCrash Handler]
#6  parent (this=0x177c220) at
../../include/QtCore/../../src/corelib/kernel/qobject.h:250
#7  parentWidget (this=0x177c220) at
../../include/QtGui/../../src/gui/kernel/qwidget.h:1022
#8  QWidget::window (this=0x177c220) at kernel/qwidget.cpp:4255
#9  0x7f3dba9a0fd4 in KNAccountManager::wallet () at
/tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knaccountmanager.cpp:250
#10 0x7f3dba9a4d89 in KNServerInfo::readPassword (this=0x25f5a40) at
/tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knserverinfo.cpp:167
#11 0x7f3dba9a58c8 in KNServerInfo::readConf (this=0x25f5a40, conf=...) at
/tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knserverinfo.cpp:66
#12 0x7f3dba9a66f6 in KNNntpAccount::readInfo (this=0x25f5a10,
confPath=...) at
/tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knnntpaccount.cpp:110
#13 0x7f3dba9a2657 in KNAccountManager::loadAccounts (this=value optimized
out) at
/tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knaccountmanager.cpp:73
#14 0x7f3dba9a2a68 in KNAccountManager::KNAccountManager (this=0x203b440,
gm=value optimized out, parent=value optimized out) at
/tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knaccountmanager.cpp:40
#15 0x7f3dbaa24b8d in KNGlobals::accountManager (this=0x175c0b0) at
/tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/knglobals.cpp:113
#16 0x7f3dba9a7e44 in KNGroupManager::checkAll (this=0x133b4f0, id=1,
silent=true) at
/tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1/knode/kngroupmanager.cpp:587
#17 0x7f3dba9a6448 in KNNntpAccountIntervalChecking::qt_metacall
(this=0x1a83b20, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out,
_a=value optimized out) at
/tmp/portage/kde-base/knode-4.6.1/work/knode-4.6.1_build/knode/knnntpaccount.moc:73
#18 0x7f3dd71e45ea in QMetaObject::activate (sender=0x14f1770, m=value
optimized out, local_signal_index=value optimized out, argv=0x6) at
kernel/qobject.cpp:3278
#19 0x7f3dd71dc999 in QObject::event (this=0x14f1770, e=0x0) at
kernel/qobject.cpp:1181
#20 0x7f3dd7bcd2fc in QApplicationPrivate::notify_helper (this=0xead4d0,
receiver=0x14f1770, e=0x7fffed2a36a0) at kernel/qapplication.cpp:4462
#21 0x7f3dd7bd5627 in QApplication::notify (this=0x7fffed2a39f0,
receiver=0x14f1770, e=0x7fffed2a36a0) at kernel/qapplication.cpp:4341
#22 0x7f3dd89dc730 in KApplication::notify (this=0x7fffed2a39f0,
receiver=0x14f1770, event=0x7fffed2a36a0) at
/tmp/portage/kde-base/kdelibs-4.6.5/work/kdelibs-4.6.5/kdeui/kernel/kapplication.cpp:311
#23 0x7f3dd71c9deb in QCoreApplication::notifyInternal
(this=0x7fffed2a39f0, receiver=0x14f1770, event=0x7fffed2a36a0) at
kernel/qcoreapplication.cpp:731
#24 0x7f3dd71fcd1a in sendEvent (this=0xebb380) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#25 QTimerInfoList::activateTimers (this=0xebb380) at
kernel/qeventdispatcher_unix.cpp:604
#26 0x7f3dd71f9a34 in timerSourceDispatch (source=value optimized out) at
kernel/qeventdispatcher_glib.cpp:184
#27 0x7f3dd13bdcf9 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#28 0x7f3dd13c2238 in g_main_context_iterate () from
/usr/lib64/libglib-2.0.so.0
#29 0x7f3dd13c23de in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#30 0x7f3dd71f971e in QEventDispatcherGlib::processEvents (this=0xeabcf0,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:422
#31 0x7f3dd7c8bd46 in QGuiEventDispatcherGlib::processEvents
(this=0x177c220, flags=value optimized out) at
kernel/qguieventdispatcher_glib.cpp:204
#32 0x7f3dd71c89f2 in QEventLoop::processEvents (this=value optimized
out, flags=) at kernel/qeventloop.cpp:149
#33 0x7f3dd71c8dbd in QEventLoop::exec (this=0x7fffed2a3960, flags=) at
kernel/qeventloop.cpp:201
#34 0x7f3dd71cb65b in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1008
#35 0x00403e6a in main (argc=value optimized out, argv=value
optimized out) at

[Bug 222878] kontact process does not exit after closing kontact window in every case

[David Talmage]

https://bugs.kde.org/show_bug.cgi?id=222878


David Talmage talm...@acm.org changed:

   What|Removed |Added

 CC||talm...@acm.org




--- Comment #12 from David Talmage talmage acm org  2011-06-13 21:49:43 ---
I experience this bug with Kubuntu 11.04 and Kontact 4.4.10.  I have four
e-mail accounts open: POP3 to gmail, two IMAP accounts to my ISP, and one
disconnected IMAP to a Kolab server on localhost.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Christophe Giboudeaux]

https://bugs.kde.org/show_bug.cgi?id=222878


Christophe Giboudeaux cgiboude...@gmx.com changed:

   What|Removed |Added

 CC||claudio.barbi...@gmail.com




--- Comment #11 from Christophe Giboudeaux cgiboudeaux gmx com  2011-04-06 
16:18:11 ---
*** Bug 252840 has been marked as a duplicate of this bug. ***

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Peter Muehlenpfordt]

https://bugs.kde.org/show_bug.cgi?id=222878


Peter Muehlenpfordt bugsea...@fantasymail.de changed:

   What|Removed |Added

 CC||bugsea...@fantasymail.de




--- Comment #9 from Peter Muehlenpfordt bugsearch fantasymail de  2011-03-09 
08:04:39 ---
I can confirm this bug for Kubuntu 10.04 (but as I remember, it happens since
Kubuntu switched to KDE 4).
The kontact process hangs any time my dsl router reconnects while kontact is
running and I quit it after this reconnect. Before restarting kontact I have to
kill the process.
My System: Kubuntu 10.04 / KDE 4.5.1 / Kontact 4.4.6 using IMAP.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Peter Muehlenpfordt]

https://bugs.kde.org/show_bug.cgi?id=222878


Peter Muehlenpfordt bugsea...@fantasymail.de changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1




--- Comment #10 from Peter Muehlenpfordt bugsearch fantasymail de  2011-03-09 
08:09:06 ---
*** This bug has been confirmed by popular vote. ***

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Alessandro Rossini]

https://bugs.kde.org/show_bug.cgi?id=222878


Alessandro Rossini m...@alessandrorossini.org changed:

   What|Removed |Added

 CC||m...@alessandrorossini.org




--- Comment #7 from Alessandro Rossini me alessandrorossini org  2010-06-06 
18:09:47 ---
I can confirm the bug.

Version:   4.4.3 (using KDE 4.4.3)
OS:GNU/Linux
Installed from:Ubuntu Packages

Best regards.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[jamese]

https://bugs.kde.org/show_bug.cgi?id=222878





--- Comment #8 from jamese james ellis gmail com  2010-06-07 02:39:12 ---
There is a similar bug reported in Bugzilla but I can't find it right now. One
commenter suggested converting IMAP accounts to Disconnected IMAP.

I tried it and it reduces the possibility of Kontact hanging around after
quitting (I had to remove my IMAP account and add new dIMAP accounts) but
doesn't work so well if you have Gmail account over IMAP.. I don't really want
to download my 6GB gmail account or whatever size it is now, which is why
IMAP/Gmail is so cool.

If you're not connecting to Gmail over IMAP or have a small Gmail account, then
try out Disconnected IMAP and see how it goes.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[jamese]

https://bugs.kde.org/show_bug.cgi?id=222878





--- Comment #6 from jamese james ellis gmail com  2010-05-10 09:03:16 ---
Any news on this bug? still happening in 4.4.3. It makes kontact nearly
unusable, especially if you switch network connections  suspend/wake up a
notebook a lot.
Anyone without knowledge of the killall command would give up.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[jamese]

https://bugs.kde.org/show_bug.cgi?id=222878


jamese james.el...@gmail.com changed:

   What|Removed |Added

 CC||james.el...@gmail.com




--- Comment #5 from jamese james ellis gmail com  2010-04-09 01:57:11 ---
Me too, Kontact does not close sometimes on exit (Quit) either by selecting
Quit from the File menu or right clicking the taskbar icon and selecting Quit.
There seem to be be heap of kio imap process lying around with kontact also in
the process list.

I have all IMAP account + one localhost account.

Doing an strace on Kontact reveals it seems to be doing nothing:


$ strace -p6415
Process 6415 attached - interrupt to quit
restart_syscall(... resuming interrupted call ...) = 1
read(9,
x\0C\262\1\0\0\2\0\300\7\1\0\0\0G\267\216\2F\267\216\2\210\310\331\277\0\253\242\210...,
4096) = 64
read(9, 0x9db8150, 4096)= -1 EAGAIN (Resource temporarily
unavailable)
read(9, 0x9db8150, 4096)= -1 EAGAIN (Resource temporarily
unavailable)
read(9, 0x9db8150, 4096)= -1 EAGAIN (Resource temporarily
unavailable)
read(9, 0x9db8150, 4096)= -1 EAGAIN (Resource temporarily
unavailable)
clock_gettime(CLOCK_MONOTONIC, {42907, 466073884}) = 0
read(9, 0x9db8150, 4096)= -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN}, {fd=10, events=POLLIN}, {fd=9, events=POLLIN},
{fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=71,
events=POLLIN}, {fd=106, events=POLLIN}, {fd=41, events=POLLIN}], 9, 28315) = 1
([{fd=9, revents=POLLIN}])
clock_gettime(CLOCK_MONOTONIC, {42907, 699954333}) = 0
read(9,
\34:C\262\1\0\0\266\1\0\0001\270\216\2\0\0\0\0\254\310\331\277\1\0\0\0\0\0@...,
4096) = 64
read(9, 0x9db8150, 4096)= -1 EAGAIN (Resource temporarily
unavailable)
read(9, 0x9db8150, 4096)= -1 EAGAIN (Resource temporarily
unavailable)
clock_gettime(CLOCK_MONOTONIC, {42907, 700111406}) = 0
read(9, 0x9db8150, 4096)= -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN}, {fd=10, events=POLLIN}, {fd=9, events=POLLIN},
{fd=5, events=POLLIN}, {fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=71,
events=POLLIN}, {fd=106, events=POLLIN}, {fd=41, events=POLLIN}], 9, 28081^C
unfinished ...
Process 6415 detached


It's a royal pain, as to get things working again I have to kill the process or
even kill -KILL the process. It's been going on for a few versions now as well.

Using Kubuntu KDE 4.4.2

Thanks!

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[KS Augustin]

https://bugs.kde.org/show_bug.cgi?id=222878


KS Augustin ksaugus...@gmail.com changed:

   What|Removed |Added

 CC||ksaugus...@gmail.com




--- Comment #4 from KS Augustin ksaugustin gmail com  2010-03-23 11:00:07 ---
Since everyone else is doing it, so shall I! Yep, having this problem on
Mandriva 2010 with Kontact on KDE 4.3. It's a pain having to kill the process
manually. I have IMAP accounts but no lost connections, no messages still in
the queue. I make sure everything is clean before I shut down at the end of the
day. This one is really bugging (heh) me.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Mike Vaughn]

https://bugs.kde.org/show_bug.cgi?id=222878


Mike Vaughn contras...@gmail.com changed:

   What|Removed |Added

 CC||contras...@gmail.com




--- Comment #3 from Mike Vaughn contrast83 gmail com  2010-01-31 15:54:42 ---
I just wanted to chime in and say I've been experiencing this same problem for
quite some time on Kubuntu, in both the 4.3 and new 4.4 branch. From what I can
tell, it occurs even when there are no lost connections to my IMAP accounts
(assuming there would be some error message informing me of such). It'd be
great to see this fixed soon; Kontact is one of my favorite applications to
show off to new users, but a bug like this presents quite a hurdle for most of
them. :-\

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Vytautas]

https://bugs.kde.org/show_bug.cgi?id=222878


Vytautas v...@azuolas.org changed:

   What|Removed |Added

 CC||v...@azuolas.org




--- Comment #1 from Vytautas vylu azuolas org  2010-01-27 10:06:08 ---
Do you have IMAP accounts in kmail? 

I have the same behavior on debian unstable with kde 4.3.4. I guess, it may be
related to bug https://bugs.kde.org/show_bug.cgi?id=186936, because kontact on
my system leaves processes after exit only after connection loss.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 222878] kontact process does not exit after closing kontact window in every case

[Alexander Stein]

https://bugs.kde.org/show_bug.cgi?id=222878





--- Comment #2 from Alexander Stein alexander stein informatik tu-chemnitz de 
 2010-01-27 19:56:25 ---
(In reply to comment #1)
 Do you have IMAP accounts in kmail? 
 
 I have the same behavior on debian unstable with kde 4.3.4. I guess, it may be
 related to bug https://bugs.kde.org/show_bug.cgi?id=186936, because kontact on
 my system leaves processes after exit only after connection loss.

Yes, I'm using (2) IMAP accounts. But I can't stay whether I got connection
losses or not.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs