[kontact] [Bug 385123] New: Kontact crashes when selecting an e-mail recipient from contacts
https://bugs.kde.org/show_bug.cgi?id=385123 Bug ID: 385123 Summary: Kontact crashes when selecting an e-mail recipient from contacts Product: kontact Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: talm...@acm.org Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-35-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: This happens the first time I compose e-mail after logging in or a reboot and attempt to choose a recipient from my contacts. Kontact crashes when I click the "Select..." button in the e-mail composition dialog. When I restart Kontact and compose a new e-mail message, it doesn't crash when I select the recipient from my contacts. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa74b2ea100 (LWP 2824))] Thread 33 (Thread 0x7fa64d85a700 (LWP 17117)): #0 0x7ffefc08da01 in clock_gettime () #1 0x7fa747fd7506 in __GI___clock_gettime (clock_id=1, tp=0x7fa64d8599e0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7fa748977c41 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fa748af3d39 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa748af42e5 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa748af568e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa73f3f6a6d in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fa73f3f749b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fa73f3f768c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7fa748af60bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fa748a9fbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fa7488cdf83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fa7488d2c38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fa7411c56da in start_thread (arg=0x7fa64d85a700) at pthread_create.c:456 #14 0x7fa747fc8d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 32 (Thread 0x7fa64c858700 (LWP 17115)): #0 0x7fa747fbcd8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa73f3f7576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa73f3f768c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa748af60bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa748a9fbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa7488cdf83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa7488d2c38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa7411c56da in start_thread (arg=0x7fa64c858700) at pthread_create.c:456 #8 0x7fa747fc8d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 31 (Thread 0x7fa64f7fe700 (LWP 23015)): #0 0x7fa747fbcd8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fa73f3f7576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa73f3f768c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa748af60bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa748a9fbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa7488cdf83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa7488d2c38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fa7411c56da in start_thread (arg=0x7fa64f7fe700) at pthread_create.c:456 #8 0x7fa747fc8d7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 30 (Thread 0x7fa64700 (LWP 23013)): #0 0x7fa73f43cef4 in g_mutex_unlock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa73f3f64be in g_main_context_acquire () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa73f3f7425 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa73f3f768c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa748af60bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa748a9fbea in QEventLoop::exec(QFlags) () at
[kontact] [Bug 328224] Kontact has crashed when fetching e-mail via IMAP
https://bugs.kde.org/show_bug.cgi?id=328224 --- Comment #3 from David Talmage talm...@acm.org --- Created attachment 93209 -- https://bugs.kde.org/attachment.cgi?id=93209action=edit New crash information added by DrKonqi kontact (4.14.6) on KDE Platform 4.14.6 using Qt 4.8.6 - What I was doing when the application crashed: I started Kontact from the application menu. My Kontact fetches mail from my IMAP server on startup. -- Backtrace (Reduced): #6 0x7f14875c0267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x7f14875c1eca in __GI_abort () at abort.c:89 [...] #11 0x7f142147dfff in operator- (this=optimized out) at ../../mailcommon/kernel/mailkernel.cpp:58 #12 MailCommon::Kernel::self () at ../../mailcommon/kernel/mailkernel.cpp:75 #13 0x7f14214c8a13 in MailCommon::FolderCollection::writeConfig (this=this@entry=0x1526e70) at ../../mailcommon/folder/foldercollection.cpp:218 -- 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 328224] Kontact has crashed when fetching e-mail via IMAP
https://bugs.kde.org/show_bug.cgi?id=328224 David Talmage talm...@acm.org changed: What|Removed |Added CC||talm...@acm.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 333391] New: Configuring Kontact causes it to crash
https://bugs.kde.org/show_bug.cgi?id=91 Bug ID: 91 Summary: Configuring Kontact causes it to crash Classification: Unclassified Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: talm...@acm.org Application: kontact (4.13 rc) KDE Platform Version: 4.12.97 Qt Version: 4.8.4 Operating System: Linux 3.11.0-20-generic x86_64 Distribution: Ubuntu 13.10 -- Information about the crash: - What I was doing when the application crashed: I was looking at the summary page. I selected Settings - Configure Contact. This is repeatable since today with the Kubuntu update of akonadi+mysql. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7fca724107c0 (LWP 3532))] Thread 6 (Thread 0x7fca52eeb700 (LWP 3533)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fca6d1bb1cd in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fca6d1bb209 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fca698dbf6e in start_thread (arg=0x7fca52eeb700) at pthread_create.c:311 #4 0x7fca6f98e9cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 5 (Thread 0x7fca125e8700 (LWP 3534)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fca6cefbbbd in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fca6d1eaa76 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fca698dbf6e in start_thread (arg=0x7fca125e8700) at pthread_create.c:311 #4 0x7fca6f98e9cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7fca07740700 (LWP 3539)): #0 0x7fca6f981f7d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fca694036a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fca694037ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fca701079ee in QEventDispatcherGlib::processEvents (this=0x7fca08c0, flags=...) at kernel/qeventdispatcher_glib.cpp:435 #4 0x7fca700d95ef in QEventLoop::processEvents (this=this@entry=0x7fca0773fdb0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fca700d98e5 in QEventLoop::exec (this=this@entry=0x7fca0773fdb0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fca6ffd888f in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #7 0x7fca6ffdaf2f in QThreadPrivate::start (arg=0xb9c8d0) at thread/qthread_unix.cpp:338 #8 0x7fca698dbf6e in start_thread (arg=0x7fca07740700) at pthread_create.c:311 #9 0x7fca6f98e9cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7fca05b8b700 (LWP 3544)): #0 0x7fca6f99cc70 in pthread_mutex_unlock (mutex=0x7fc9f8000a60) at forward.c:194 #1 0x7fca694433d1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fca69402fbb in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fca69403612 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fca694037ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fca701079ee in QEventDispatcherGlib::processEvents (this=0x7fc9f80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:435 #6 0x7fca700d95ef in QEventLoop::processEvents (this=this@entry=0x7fca05b8ad70, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fca700d98e5 in QEventLoop::exec (this=this@entry=0x7fca05b8ad70, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fca6ffd888f in QThread::exec (this=this@entry=0x2aca070) at thread/qthread.cpp:542 #9 0x7fca700bad13 in QInotifyFileSystemWatcherEngine::run (this=0x2aca070) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x7fca6ffdaf2f in QThreadPrivate::start (arg=0x2aca070) at thread/qthread_unix.cpp:338 #11 0x7fca698dbf6e in start_thread (arg=0x7fca05b8b700) at pthread_create.c:311 #12 0x7fca6f98e9cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7fc9f7593700 (LWP 3551)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fca0969206b in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7fca096920a9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7fca698dbf6e in start_thread (arg=0x7fc9f7593700) at
[kontact] [Bug 326135] New: Kontact crashes on Counter Proposal response to a meeting request
https://bugs.kde.org/show_bug.cgi?id=326135 Bug ID: 326135 Summary: Kontact crashes on Counter Proposal response to a meeting request Classification: Unclassified Product: kontact Version: 4.11.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: talm...@acm.org Application: kontact (4.11.2) KDE Platform Version: 4.11.2 Qt Version: 4.8.4 Operating System: Linux 3.8.0-31-generic x86_64 Distribution: Ubuntu 13.04 -- Information about the crash: - What I was doing when the application crashed: I clicked on the Counter Proposal button. Then Kontact crashed The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7fe489eca7c0 (LWP 29423))] Thread 5 (Thread 0x7fe46b8ef700 (LWP 29424)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe484d26585 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fe484d265d9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fe4814a8f8e in start_thread (arg=0x7fe46b8ef700) at pthread_create.c:311 #4 0x7fe487458e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7fe42afec700 (LWP 29425)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fe484a6ca09 in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fe484d54cee in WTF::wtfThreadEntryPoint(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fe4814a8f8e in start_thread (arg=0x7fe42afec700) at pthread_create.c:311 #4 0x7fe487458e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7fe41c7d5700 (LWP 29428)): #0 0x7fe48744c3cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fe480fd61dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe480fd6304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe487bd1036 in QEventDispatcherGlib::processEvents (this=0x7fe4140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fe487ba138f in QEventLoop::processEvents (this=this@entry=0x7fe41c7d4d90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fe487ba1618 in QEventLoop::exec (this=this@entry=0x7fe41c7d4d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fe487aa3410 in QThread::exec (this=this@entry=0x262c6e0) at thread/qthread.cpp:542 #7 0x7fe487b82edf in QInotifyFileSystemWatcherEngine::run (this=0x262c6e0) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x7fe487aa5bec in QThreadPrivate::start (arg=0x262c6e0) at thread/qthread_unix.cpp:338 #9 0x7fe4814a8f8e in start_thread (arg=0x7fe41c7d5700) at pthread_create.c:311 #10 0x7fe487458e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7fe41b538700 (LWP 29430)): #0 0x7fe48744c3cd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fe480fd61dc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe480fd6304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe487bd1036 in QEventDispatcherGlib::processEvents (this=0x7fe40c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fe487ba138f in QEventLoop::processEvents (this=this@entry=0x7fe41b537dc0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fe487ba1618 in QEventLoop::exec (this=this@entry=0x7fe41b537dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fe487aa3410 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #7 0x7fe487aa5bec in QThreadPrivate::start (arg=0x2100d90) at thread/qthread_unix.cpp:338 #8 0x7fe4814a8f8e in start_thread (arg=0x7fe41b538700) at pthread_create.c:311 #9 0x7fe487458e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7fe489eca7c0 (LWP 29423)): [KCrash Handler] #6 0x7fe429446657 in Akonadi::ITIPHandler::processiTIPMessage (this=0x109b3c70, receiver=..., iCal=..., action=...) at ../../../akonadi/calendar/itiphandler.cpp:160 #7 0x7fe429448172 in Akonadi::ITIPHandler::Private::onLoadFinished (this=0xc693dd0, success=optimized out, errorMessage=...) at ../../../akonadi/calendar/itiphandler_p.cpp:82 #8 0x7fe487bb70ef in QMetaObject::activate (sender=0x15d75e20, m=m@entry=0x7fe42969df00 Akonadi::FetchJobCalendar::staticMetaObject, local_signal_index=local_signal_index@entry=0,
[Akonadi] [Bug 319540] google calendar with akonadi DAV crashes on the kde login
https://bugs.kde.org/show_bug.cgi?id=319540 David Talmage talm...@acm.org changed: What|Removed |Added CC||talm...@acm.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
[Akonadi] [Bug 319540] google calendar with akonadi DAV crashes on the kde login
https://bugs.kde.org/show_bug.cgi?id=319540 --- Comment #6 from David Talmage talm...@acm.org --- Created attachment 79974 -- https://bugs.kde.org/attachment.cgi?id=79974action=edit New crash information added by DrKonqi akonadi_davgroupware_resource (4.10) on KDE Platform 4.10.2 using Qt 4.8.4 - What I was doing when the application crashed: I started Kontact. I typed my password so that akonadi could access my company Zimbra server. -- Backtrace (Reduced): #6 0x00445154 in DavGroupwareResource::retrieveItem (this=0x25d3500, item=...) at ../../../../resources/dav/resource/davgroupwareresource.cpp:315 #7 0x7fdbeadd9f45 in Akonadi::ResourceBasePrivate::slotPrepareItemRetrievalResult (this=0x25d9db0, job=optimized out) at ../../akonadi/resourcebase.cpp:783 #8 0x7fdbeadda37a in Akonadi::ResourceBase::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at ./moc_resourcebase.cpp:141 [...] #10 0x7fdbeb697162 in KJob::result (this=this@entry=0x265b4a0, _t1=_t1@entry=0x265b4a0) at ./kjob.moc:208 #11 0x7fdbeb6971a0 in KJob::emitResult (this=0x265b4a0) at ../../kdecore/jobs/kjob.cpp:318 -- 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 288364] Retrieving Folder Contents hanging without showing content
https://bugs.kde.org/show_bug.cgi?id=288364 --- Comment #25 from David Talmage talm...@acm.org --- In Kmail, I deleted the IMAP account with the problem. Then I created the account again. The problem disappeared. -- 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 288364] Retrieving Folder Contents hanging without showing content
https://bugs.kde.org/show_bug.cgi?id=288364 David Talmage talm...@acm.org changed: What|Removed |Added CC||talm...@acm.org --- Comment #23 from David Talmage talm...@acm.org --- This happens to me in Kmail 4.8.3 on Kubuntu 12.04. It just started happening yesterday. I think there was an update to Kmail two days ago. Switching to an empty folder and back to my inbox doesn't help. -- 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
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
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
