[kontact] [Bug 406202] New: Kontact crashes on exit
https://bugs.kde.org/show_bug.cgi?id=406202 Bug ID: 406202 Summary: Kontact crashes on exit Product: kontact Version: 5.10.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: matth...@heizmann.name Target Milestone: --- Application: kontact (5.10.3) (Compiled from sources) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.27-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: Not a new problem, occurred in preceding versions of Kontact The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe2e4c30980 (LWP 5847))] Thread 29 (Thread 0x7fe15e0bd700 (LWP 5967)): #0 0x7fe2e16950a3 in poll () from /lib64/libc.so.6 #1 0x7fe2db4ff436 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe2db4ff55c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe2e2213f1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fe2e21c4653 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe2e203e016 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fe2e2046f5a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7fe178b97700 (LWP 5950)): #0 0x7fe2dd415169 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe2d2ac38d7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fe2d2ac4e37 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fe2d2ac4f22 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fe2d2ac9fa1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fe2d2acb529 in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fe2d2ad5f41 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7fe19285c700 (LWP 5894)): #0 0x7fe2e16950a3 in poll () from /lib64/libc.so.6 #1 0x7fe2db4ff436 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe2db4ff55c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe2e2213f1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fe2e21c4653 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe2e203e016 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fe2e2046f5a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7fe193cbc700 (LWP 5892)): #0 0x7fe2e1690990 in read () from /lib64/libc.so.6 #1 0x7fe2db544af0 in g_wakeup_acknowledge () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe2db4fef0f in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe2db4ff3e0 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe2db4ff55c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fe2e2213f1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fe2e21c4653 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe2e203e016 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7fe2e2046f5a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #9 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #10 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7fe1a67c8700 (LWP 5876)): #0 0x7fe2e16b057b in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7fe2e16b274c in __fprintf_chk () from /lib64/libc.so.6 #2 0x7fe2c8e62ff0 in event_logv_.part () from /usr/lib64/libevent-2.1.so.6 #3 0x7fe2c8e631dc in event_warn () from /usr/lib64/libevent-2.1.so.6 #4 0x7fe2c8e648e4 in epoll_dispatch () from /usr/lib64/libevent-2.1.so.6 #5 0x7fe2c8e5a6d5 in event_base_loop () from /usr/lib64/libevent-2.1.so.6 #6
[kontact] [Bug 403417] New: kontact crashed after akonadictl restart
https://bugs.kde.org/show_bug.cgi?id=403417 Bug ID: 403417 Summary: kontact crashed after akonadictl restart Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: matth...@heizmann.name Target Milestone: --- Application: kontact (5.9.3) (Compiled from sources) Qt Version: 5.11.3 Frameworks Version: 5.52.0 Operating System: Linux 4.19.14-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I executed akonadictl restart - Unusual behavior I noticed: akonadiserver was consuming 25% of my memory -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4e1647f800 (LWP 24877))] Thread 34 (Thread 0x7f4c94b3b700 (LWP 18812)): #0 0x7f4e0ce10ea4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f4e0cdcaf96 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4e0cdcb0ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4e13a7a12b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f4e13a2611a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f4e13888aea in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f4e1389254f in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7f4e0ecc396a in start_thread () from /lib64/libpthread.so.0 #8 0x7f4e12f0c1af in clone () from /lib64/libc.so.6 Thread 33 (Thread 0x7f4cacbc4700 (LWP 18811)): #0 0x7f4e12f005d3 in poll () from /lib64/libc.so.6 #1 0x7f4e0cdcafd9 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4e0cdcb0ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4e13a7a12b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f4e13a2611a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f4e13888aea in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f4e1389254f in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7f4e0ecc396a in start_thread () from /lib64/libpthread.so.0 #8 0x7f4e12f0c1af in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7f4cc3dba700 (LWP 18787)): #0 0x7f4e0ecca8aa in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4e0445e8d7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f4e0445fe37 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f4e0445ff22 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f4e04464fa1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f4e0446633f in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f4e04470f41 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f4e0ecc396a in start_thread () from /lib64/libpthread.so.0 #8 0x7f4e12f0c1af in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f4cbaf13700 (LWP 18786)): #0 0x7f4e0ecca8aa in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4e0445e8d7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f4e0445fe37 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f4e0445ff22 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f4e04464fa1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f4e04466529 in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f4e04470f41 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f4e0ecc396a in start_thread () from /lib64/libpthread.so.0 #8 0x7f4e12f0c1af in clone () from /lib64/libc.so.6 Thread 30 (Thread 0x7f4cdb7fe700 (LWP 18785)): #0 0x7f4e0ecca8aa in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4e0445e8d7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f4e0445fe37 in
[Akonadi] [Bug 284527] Error when changing an imap folder's identity (Unknown command SETANNOTATION)
https://bugs.kde.org/show_bug.cgi?id=284527 --- Comment #19 from Matthias Heizmann matth...@heizmann.name --- Thank to some help of Alexander I was able to use his workaround. A few comments for others that run into the same problem. While creating the kolab ressource manually using the Raw Socket - you have to have the ressource already created in the usual way (I deleted it after I reading the debugging output) - do not paste the ROLLBACK command, but paste COMMIT instead - do not reboot after these steps, otherwise the kolab ressource is gone again. You set the content type to inode/directory in Folder Properties Internals (Yes, where it says Do not even think about chaning anything in here!) -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 284527] Error when changing an imap folder's identity (Unknown command SETANNOTATION)
https://bugs.kde.org/show_bug.cgi?id=284527 Matthias Heizmann matth...@heizmann.name changed: What|Removed |Added CC||matth...@heizmann.name --- Comment #18 from Matthias Heizmann matth...@heizmann.name --- I have the same problem with KDE SC 4.11.1 and akonadi-server-1.10.2-r1 I would like to use Alexanders workaround, but I failed. As Alexander suggested I had a look at the debugger and saw the following lines (you see them e.g., if you try to add the kolab calendar via korganizer) 0x825880 0 LOGIN akonadi_kolabproxy_resource akonadi_kolabproxy_resource (0x825880) 0 OK User logged in akonadi_kolabproxy_resource (0x825880) 1 CAPABILITY (NOTIFY 2) akonadi_kolabproxy_resource (0x825880) 1 OK CAPABILITY completed akonadi_kolabproxy_resource (0x825880) 2 RESSELECT akonadi_kolabproxy_resource akonadi_kolabproxy_resource (0x825880) 2 OK akonadi_kolabproxy_resource selected ... (I omit the succeeding lines, because they are not relevant for my question) Afterwards I executed the following commands in the Raw Socket tab. 0 LOGIN akonadi_kolabproxy_resource 1 CAPABILITY (NOTIFY 2) 2 RESSELECT akonadi_kolabproxy_resource However, now I got a different output (last line is different) 0x87a0e0 0 LOGIN akonadi_kolabproxy_resource akonadi_kolabproxy_resource (0x87a0e0) 0 OK User logged in akonadi_kolabproxy_resource (0x87a0e0) 1 CAPABILITY (NOTIFY 2) akonadi_kolabproxy_resource (0x87a0e0) 1 OK CAPABILITY completed akonadi_kolabproxy_resource (0x87a0e0) 2 RESSELECT akonadi_kolabproxy_resource akonadi_kolabproxy_resource (0x87a0e0) 2 NO akonadi_kolabproxy_resource is not a valid resource identifier What can I do to add the parent collection and set its content type inode/directory? -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 306576] New: Kolab Plugin Crashed, while updating address book folder
https://bugs.kde.org/show_bug.cgi?id=306576 Bug ID: 306576 Severity: crash Version: 4.9 Priority: NOR CC: kdepim-bugs@kde.org Assignee: kdepim-bugs@kde.org Summary: Kolab Plugin Crashed, while updating address book folder Classification: Unclassified OS: Linux Reporter: matth...@heizmann.name Hardware: Gentoo Packages Status: UNCONFIRMED Component: Kolab Resource Product: Akonadi Application: akonadi_kolabproxy_resource (4.9) KDE Platform Version: 4.9.1 Qt Version: 4.8.2 Operating System: Linux 3.5.3-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: Since I removed and added my IMAP server, Kaddressbook does not show any contacts in my Kolab adress book. I had this problem before, usually I have to click Update Address Book Folder after adding a Kolab adress book to Kaddressbook. However, since KDE SC 4.9 the Kolab plugin crashed if I do so. - What I was doing when the application crashed: Opend Kaddressbook, selected Kolab adress book, clicked Update Address Book Folder. The crash can be reproduced every time. -- Backtrace: Application: Kolab of type Kolab Groupware Server (akonadi_kolabproxy_resource), signal: Segmentation fault [KCrash Handler] #6 KMime::Content::headerKMime::Headers::ContentTransferEncoding (this=0x0, create=true) at /var/tmp/portage/kde-base/kdepimlibs-4.9.1/work/kdepimlibs-4.9.1/kmime/kmime_content.h:833 #7 0x7fafe519463b in KMime::Content::decodedContent (this=0x0) at /var/tmp/portage/kde-base/kdepimlibs-4.9.1/work/kdepimlibs-4.9.1/kmime/kmime_content.cpp:374 #8 0x7fafe7c52a5c in Kolab::getPicture (pictureAttachmentName=optimized out, data=optimized out, type=...) at /var/tmp/portage/net-libs/libkolab-0.2.0/work/libkolab-0.2.0/kolabformat/v2helpers.h:83 #9 0x7fafe7c53ef6 in Kolab::addresseeFromKolab (xmlData=optimized out, data=...) at /var/tmp/portage/net-libs/libkolab-0.2.0/work/libkolab-0.2.0/kolabformat/v2helpers.h:123 #10 0x7fafe7c5a135 in Kolab::KolabObjectReader::parseMimeMessage (this=0x7fffe11365c0, msg=...) at /var/tmp/portage/net-libs/libkolab-0.2.0/work/libkolab-0.2.0/kolabformat/kolabobject.cpp:161 #11 0x7fafe7c5b2c4 in Kolab::KolabObjectReader::KolabObjectReader (this=0x7fffe11365c0, msg=...) at /var/tmp/portage/net-libs/libkolab-0.2.0/work/libkolab-0.2.0/kolabformat/kolabobject.cpp:76 #12 0x00427fb6 in AddressBookHandler::translateItems (this=0x8682e0, items=optimized out) at /var/tmp/portage/kde-base/kdepim-runtime-4.9.1/work/kdepim-runtime-4.9.1/resources/kolabproxy/addressbookhandler.cpp:45 #13 0x0041731b in KolabProxyResource::retrieveItemFetchDone (this=0x7c81a0, job=optimized out) at /var/tmp/portage/kde-base/kdepim-runtime-4.9.1/work/kdepim-runtime-4.9.1/resources/kolabproxy/kolabproxyresource.cpp:247 #14 0x7fafe6d60832 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #15 0x7fafe71ea392 in KJob::result(KJob*) () from /usr/lib64/libkdecore.so.5 #16 0x7fafe71ea3d0 in KJob::emitResult() () from /usr/lib64/libkdecore.so.5 #17 0x7fafe6d5fc56 in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #18 0x7fafe60d1e14 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #19 0x7fafe60d691d in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #20 0x7fafe77f48d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #21 0x7fafe6d4af8c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #22 0x7fafe6d4e580 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4 #23 0x7fafe6d7a103 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #24 0x7fafe02284b3 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #25 0x7fafe02287f8 in ?? () from /usr/lib64/libglib-2.0.so.0 #26 0x7fafe02288b4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #27 0x7fafe6d7a29f in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #28 0x7fafe617804e in ?? () from /usr/lib64/qt4/libQtGui.so.4 #29 0x7fafe6d49ce2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #30 0x7fafe6d49f9d in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #31 0x7fafe6d4ea1b in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #32 0x7fafe8ceb916 in Akonadi::ResourceBase::init (r=0x7c81a0) at /var/tmp/portage/kde-base/kdepimlibs-4.9.1/work/kdepimlibs-4.9.1/akonadi/resourcebase.cpp:451 #33 0x00414248 in initKolabProxyResource (argv=optimized out, argc=optimized out) at
[Bug 305296] Kolab Calendar Resource Missing
https://bugs.kde.org/show_bug.cgi?id=305296 --- Comment #3 from Matthias Heizmann matth...@heizmann.name --- I installed the necessay packages. The Kolab Groupware Resource is available. Unfortunatly I was not yet able to solve my problem. When ich click in Korganizer add Calendar (resp. in Kaddressbook add Address Book). The option Kolab Groupware Server is grayed out, like it would have been already added. Additionally, as before: - If I select in Kmail my calendar folder on the IMAP server and click Folder Properties, set Folder contents to Calendar, a window with the following message pops up. You have configured this folder to contain groupware information. This means that this folder will disappear once the configuration dialog is closed. Up to here this is the behaviour I expected. However actually nothing happens, the folder does not disappear (not even after a restart), no new calendar appears in Korganizer. 1. Maybe the calendar resource is already added but for some reason not visible in Korganzier. 2. Maybe the calendar resource is not added but for some reason also not addable. How can I find our what the real reason is? -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 305296] New: Kolab Calendar Resource Missing
https://bugs.kde.org/show_bug.cgi?id=305296 Bug ID: 305296 Severity: normal Version: 4.9 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Kolab Calendar Resource Missing Classification: Unclassified OS: Linux Reporter: matth...@heizmann.name Hardware: Gentoo Packages Status: UNCONFIRMED Component: IMAP resource Product: Akonadi I did an update from KdeSC 4.8.5 to 4.9.0. A few days later I realized that my new calendar entrys in a Kolab calendar resource are not synced back to the IMAP server. I wanted to solve this problem in a quick and dirty way and did the following: 1. I copyied all calendar entrys not synced to the server to a calendar myEmergencyBackup.ics is a local file. 2. I deleted ~/.local/share/* and ~/.kde4/share/configakonadi* 3. I started kmail and set up my IMAP server again All calendars in Korganizer are gone (I expected this). However I am not able to add the calendar via Kolab resource again. - If I click in Korganizer Add Calendar I can select from a list containing the following. BirthdaysAnniversaries, DAV groupware resource, ICal Calendar File, KAlarm Calendar File, KAlarm Directory, KDE Caendar (traditional), Knut, Open-Xcahnge Groupwar Server. There is no Kolab resource. - If I select in Kmail my calendar folder on the IMAP server and click Folder Properties, set Folder contents to Calendar, a window with the following message pops up. You have configured this folder to contain groupware information. This means that this folder will disappear once the configuration dialog is closed. Up to here this is the behaviour I expected. However actually nothing happens, the folder does not disappear (not even after a restart), no new calendar appears in Korganizer. I think most annoying ist not that this happend, but that there was no error message that infomed about the problem. If you have some idea which useful information I can provide, please let me know. I guess a brute force solution for me is to delete the whole ~/.kde4 directory. Do you have a more sophisticated advice which config files I should delete in order to be able to configure a new Kolab calendar resource? Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 305296] Kolab Calendar Resource Missing
https://bugs.kde.org/show_bug.cgi?id=305296 --- Comment #1 from Matthias Heizmann matth...@heizmann.name --- I just found out that for KdeSC 4.9.0 the kolab client is not installed by default in Gentoo. I guess that is my problem. I should change this bug report to There should be an error message if the plugins needed for some resource are missing -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
