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

2019-02-26 Thread 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

2018-10-31 Thread 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

2018-01-05 Thread 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

2017-01-09 Thread 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

2017-01-09 Thread 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

2016-09-27 Thread 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

2016-09-25 Thread 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

2016-09-24 Thread 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

2016-09-24 Thread 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

2014-07-07 Thread 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

2014-04-30 Thread 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

2014-04-26 Thread 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

2014-04-17 Thread 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

2014-04-17 Thread 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

2014-04-14 Thread 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

2014-04-14 Thread 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

2014-04-14 Thread 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

2014-04-14 Thread 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

2014-03-10 Thread 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

2014-03-08 Thread 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

2014-02-26 Thread 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

2014-02-26 Thread 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

2014-02-26 Thread 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

2014-01-28 Thread 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

2014-01-26 Thread 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

2014-01-02 Thread 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

2013-12-12 Thread 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

2013-12-04 Thread 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

2013-08-20 Thread 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