Bug 266887 - KMail2 process doesn't quit if it was restored at KDE startup.
Summary: KMail2 process doesn't quit if it was restored at KDE startup.
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2011-02-22 14:14 UTC by Christophe Marin
Modified: 2018-09-19 14:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Marin 2011-02-22 14:14:16 UTC
Steps:

- Configure KDE to 'restore the previous session'
- Launch KMail,
- logout / login
KMail is restored:

# ps x |grep kmail
25095 ?        Sl     0:03 kmail -session 10e875756b000129837994300000242810038_1298379993_111083

However, file/quit in KMail doesn't stop the process (the window and tray icon are gone but the process is still there)


(gdb) thread apply all bt

Thread 2 (Thread 0x7f24e851d700 (LWP 25191)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f24f5d3d084 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#2  0x00007f24ffa47a3f in start_thread (arg=0x7f24e851d700) at pthread_create.c:297
#3  0x00007f2501be367d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f2504823760 (LWP 25095)):
#0  0x00007f2501bdcc73 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f25031c092a in qt_safe_select (nfds=16, fdread=0x65d410, fdwrite=0x65d6a8, fdexcept=0x65d940, orig_timeout=0x7fff1f987cd0) at kernel/qcore_unix.cpp:92
#2  0x00007f25031c596d in QEventDispatcherUNIXPrivate::doSelect (this=0x65d250, flags=..., timeout=0x7fff1f987cd0) at kernel/qeventdispatcher_unix.cpp:219
#3  0x00007f25031c6bcf in QEventDispatcherUNIX::processEvents (this=0x6113f0, flags=...) at kernel/qeventdispatcher_unix.cpp:933
#4  0x00007f250260abac in QEventDispatcherX11::processEvents (this=0x6113f0, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#5  0x00007f2503198052 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f2503198265 in QEventLoop::exec (this=0x7fff1f987fa0, flags=...) at kernel/qeventloop.cpp:201
#7  0x00007f250319c6ab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#8  0x0000000000403486 in main (argc=3, argv=0x7fff1f988278) at /kde/src/KDE/kdepim/kmail/main.cpp:145
Comment 1 Sergio Martins 2011-04-11 01:14:06 UTC
My kmail doesn't even restore, so i can't test this.
Comment 2 Chao Feng 2013-02-24 06:39:40 UTC
I can not reproduce it in Kmail 4.10. Do you still have this issue?
Comment 3 Andrew Crouthamel 2018-09-19 14:42:11 UTC
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.