[Bug 251704] kmail2 does not allow creation of new top-level folder
https://bugs.kde.org/show_bug.cgi?id=251704 --- Comment #10 from András Manţia --- Note that the original issue was reported for mixedmaildir and not for IMAP. Please do not mix that. OTOH I can assure that creation of toplevel folders works fine for maildir. -- 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 298164] New: Newly created mixedmaildir accounts do not show up
https://bugs.kde.org/show_bug.cgi?id=298164 Bug ID: 298164 Severity: normal Version: unspecified Priority: NOR CC: kram...@kde.org Assignee: kdepim-bugs@kde.org Summary: Newly created mixedmaildir accounts do not show up Classification: Unclassified OS: Linux Reporter: aman...@kde.org Hardware: Compiled Sources Status: NEW Component: Mixed Maildir resource Product: Akonadi User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.8.2 Safari/534.34 Build Identifier: Create a new mixedmaildir account, point to a not existing folder, so it creates it. Accept. The newly created account folder is not visible in KMail, so you can't move mails to it. It appears in akonadiconsole. Note, this works for maildir, so I still assume the problem is on the resource side. Reproducible: Always -- 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 251704] kmail2 does not allow creation of new top-level folder
https://bugs.kde.org/show_bug.cgi?id=251704 --- Comment #9 from Jon Skanes --- (In reply to comment #8) > This is a pretty serious assumption made about IMAP. I will never roll out > kmail2/akonadi until this is addressed. My reasons are detailed in this > related bug: https://bugs.kde.org/show_bug.cgi?id=292418 > > Please take this issue seriously. I'm not about to take on the headache of > educating my users as to why they can do it on just about every other device > or piece of software and not in kmail2! F.Y.I: KDE 4.8.2 on Kubuntu Oneric from official Kubuntu PPAs. -- 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 251704] kmail2 does not allow creation of new top-level folder
https://bugs.kde.org/show_bug.cgi?id=251704 Jon Skanes changed: What|Removed |Added CC||j...@skanes.ca --- Comment #8 from Jon Skanes --- This is a pretty serious assumption made about IMAP. I will never roll out kmail2/akonadi until this is addressed. My reasons are detailed in this related bug: https://bugs.kde.org/show_bug.cgi?id=292418 Please take this issue seriously. I'm not about to take on the headache of educating my users as to why they can do it on just about every other device or piece of software and not in kmail2! -- 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 298119] KWallet mandatory
https://bugs.kde.org/show_bug.cgi?id=298119 --- Comment #4 from Philip Nystromer --- If you are not motivated, or have time to fix bugs, then mayby you should leave the bug fixing to someone else? Especially if you are tired to read about users wishes. -- 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 298121] akonadi_agent_launcher claims 1.7GB of 2GB memory - system stalls
https://bugs.kde.org/show_bug.cgi?id=298121 --- Comment #3 from Philip Nystromer --- The first bug, seems recent and identical to mine. But I can not see how the s econd bug (289277) relates to my problem? -- 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 292418] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=292418 Jon Skanes changed: What|Removed |Added CC||j...@skanes.ca --- Comment #6 from Jon Skanes --- This issue is a killer for me. I cannot consider KDE with current kmail/akonadi for general use until this is addressed. Changing and then enforcing a no top level folder policy for more then a few users is unacceptable. Every other device and application I have seen in use on my server are fine with it and use it by default. My users have a long history of working with top level folders. Educating them all just for the sake of KDE is never going to happen. It seems to me akonadi is making assumptions about IMAP which have no basis in the standard. I don't know much about akonadi, however, I know enough to notice it does work fine with preexisting top level folders and doesn't seem bothered when they are created by other means. Is it really that difficult to add folder creation? This has been open far too long considering it grossly subverts the IMAP standards. -- 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 298148] New: Repeated crashes
https://bugs.kde.org/show_bug.cgi?id=298148 Bug ID: 298148 Severity: crash Version: 4.8 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Repeated crashes Classification: Unclassified OS: Linux Reporter: k...@kitterman.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.8) KDE Platform Version: 4.8.2 (4.8.2) Qt Version: 4.8.1 Operating System: Linux 3.2.0-23-generic-pae i686 Distribution: Ubuntu precise (development branch) -- Information about the crash: - What I was doing when the application crashed: I wasn't actually paying attention to Kontact/Kmail when the crashes happen. This has been happening all day. I tried stopping akonadi and restarting it, but still got the crash. -- Backtrace: Application: Akonadi Resource (akonadi_imap_resource), signal: Aborted Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [KCrash Handler] #7 0xb77ad424 in __kernel_vsyscall () #8 0xb56d81ef in raise () from /lib/i386-linux-gnu/libc.so.6 #9 0xb56db835 in abort () from /lib/i386-linux-gnu/libc.so.6 #10 0xb591a13d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #11 0xb5917ed3 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #12 0xb5917f0f in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #13 0xb591805e in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #14 0xb591867f in operator new(unsigned int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #15 0xb5659ae6 in Akonadi::NotificationMessage::NotificationMessage() () from /usr/lib/libakonadiprotocolinternals.so.1 #16 0xb75c78ac in loadFrom (device=, this=) at ../../akonadi/changerecorder_p.h:142 #17 Akonadi::ChangeRecorderPrivate::loadNotifications (this=0x8e36a88) at ../../akonadi/changerecorder_p.h:123 #18 0xb75c4472 in Akonadi::ChangeRecorder::setConfig (this=0x6, settings=0x0) at ../../akonadi/changerecorder.cpp:50 #19 0xb75a09a4 in Akonadi::AgentBasePrivate::init (this=0x8e1b618) at ../../akonadi/agentbase.cpp:216 #20 0xb75a16f3 in Akonadi::AgentBase::AgentBase (this=0x8e1d5f8, d=0x8e1b618, id=...) at ../../akonadi/agentbase.cpp:518 #21 0xb768a699 in Akonadi::ResourceBase::ResourceBase (this=0x8e1d5f8, id=...) at ../../akonadi/resourcebase.cpp:297 #22 0x0805a964 in ImapResource::ImapResource (this=0x8e1d5f8, id=...) at ../../../resources/imap/imapresource.cpp:95 #23 0x0805e3cc in Akonadi::ResourceBase::init (argc=3, argv=0xbf96e5d4) at /usr/include/akonadi/resourcebase.h:180 #24 0x080586ab in main (argc=3, argv=0xbf96e5d4) at ../../../resources/imap/imapresource.cpp:607 Possible duplicates by query: bug 285381. Reported using DrKonqi -- 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 298141] New: kontact crashes when moving a folder in kmail
https://bugs.kde.org/show_bug.cgi?id=298141 Bug ID: 298141 Severity: crash Version: 4.8.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact crashes when moving a folder in kmail Classification: Unclassified OS: Linux Reporter: aben...@its.caltech.edu Hardware: Fedora RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.1) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.3.1-3.fc16.x86_64 x86_64 Distribution: "Fedora release 16 (Verne)" -- Information about the crash: - What I was doing when the application crashed: Attempting to move a folder into another folder in my local (maildir) mail folders. Crash happens if I attempt to move the folder by dragging it, or by using the right-click menu to move it. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x2ba460852300 (LWP 20197))] Thread 5 (Thread 0x2ba46c491700 (LWP 20198)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x0034c37b86ec in WTF::TCMalloc_PageHeap::scavengerThread (this=0x34c417cc20) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x0034c37b8819 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x003732607d90 in start_thread (arg=0x2ba46c491700) at pthread_create.c:309 #4 0x003731af0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 4 (Thread 0x2ba46c7aa700 (LWP 20199)): #0 0x003731ae85c3 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x003734644fd8 in g_main_context_poll (n_fds=1, fds=0x2ba4700013e0, priority=, timeout=6906, context=0x2ba479a0) at gmain.c:3402 #2 g_main_context_iterate (context=0x2ba479a0, block=, dispatch=1, self=) at gmain.c:3084 #3 0x00373464549c in g_main_context_iteration (context=0x2ba479a0, may_block=1) at gmain.c:3152 #4 0x003d79da7dc6 in QEventDispatcherGlib::processEvents (this=0x2ba478c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #5 0x003d79d78182 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #6 0x003d79d783d7 in QEventLoop::exec (this=0x2ba46c7a9d40, flags=...) at kernel/qeventloop.cpp:204 #7 0x003d79c78b27 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x003d79c7bb6b in QThreadPrivate::start (arg=0x802060) at thread/qthread_unix.cpp:298 #9 0x003732607d90 in start_thread (arg=0x2ba46c7aa700) at pthread_create.c:309 #10 0x003731af0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x2ba4b9ce0700 (LWP 10158)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x003d79c7bfdf in wait (time=3, this=0x3cc9f80) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x3cc9f28, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x003d79c6f5af in QThreadPoolThread::run (this=0x3cdc8d0) at concurrent/qthreadpool.cpp:141 #4 0x003d79c7bb6b in QThreadPrivate::start (arg=0x3cdc8d0) at thread/qthread_unix.cpp:298 #5 0x003732607d90 in start_thread (arg=0x2ba4b9ce0700) at pthread_create.c:309 #6 0x003731af0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x2ba4bb3f4700 (LWP 10160)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 #1 0x003d79c7bfdf in wait (time=3, this=0x3c3a210) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x4468e48, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x003d79c6f5af in QThreadPoolThread::run (this=0x4468ea0) at concurrent/qthreadpool.cpp:141 #4 0x003d79c7bb6b in QThreadPrivate::start (arg=0x4468ea0) at thread/qthread_unix.cpp:298 #5 0x003732607d90 in start_thread (arg=0x2ba4bb3f4700) at pthread_create.c:309 #6 0x003731af0f5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x2ba460852300 (LWP 20197)): [KCrash Handler] #6 QModelIndex (other=, this=0x7fff2de184f0) at ../../src/corelib/kernel/qabstractitemmodel.h:65 #7 QSortFilterProxyModel::parent (this=0xcbced0, child=) at itemviews/qsortfilterproxymodel.cpp:1659 #8 0x0034bd40e8fa in parent (this=0x7fff2de18540) at /usr/include/QtCore/qabstractitemmodel.h:393 #9 KIdentityProxyModel::parent (this=0x3b6d2e0, child=) at /usr/src/debug/kdelibs-4.8.1/kdeui/itemviews/kidentityproxymodel.cpp:358 #10 0x0034bd40e8fa in parent (this=0x7fff2de185a0) at /usr/include/Q
[Bug 298136] New: notification about "connection to server lost" should be more tolerant
https://bugs.kde.org/show_bug.cgi?id=298136 Bug ID: 298136 Severity: wishlist Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: notification about "connection to server lost" should be more tolerant Classification: Unclassified OS: Linux Reporter: m.w...@web.de Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) rekonq Safari/534.34 Build Identifier: I quite often receive a notification about the connection to the server been lost. This happens for example when I move from cable connection to wifi and vica versa. Or when the internet connection is slow and the connection to the server ist lost for a moment. The problem about this is that when the notification has arrived, the connection has already been reestablished and is quite useless and is distracting. I would suggest to show the notification only when the connection is lost and can not be reestablished within a certain time frame. I do not know what is reasonable, may be 5 or 10 seconds. In this case the notification would only be shown when it really matters, when it is likely that the reason for the interruption will last longer. Reproducible: Always Actual Results: - Expected Results: - - -- 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 298121] akonadi_agent_launcher claims 1.7GB of 2GB memory - system stalls
https://bugs.kde.org/show_bug.cgi?id=298121 Jörg Schaible changed: What|Removed |Added CC||joerg.schai...@gmx.de --- Comment #2 from Jörg Schaible --- Look into https://bugs.kde.org/show_bug.cgi?id=294447 and https://bugs.kde.org/show_bug.cgi?id=289277 -- 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 297678] Selecting multiple folders caused a crash
https://bugs.kde.org/show_bug.cgi?id=297678 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Resolution|--- |DUPLICATE --- Comment #2 from Laurent Montel --- *** This bug has been marked as a duplicate of bug 284742 *** -- 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 284742] Kmail crashed selecting several folders
https://bugs.kde.org/show_bug.cgi?id=284742 Laurent Montel changed: What|Removed |Added CC||bugzi...@s-and-j.co.uk --- Comment #4 from Laurent Montel --- *** Bug 297678 has been marked as a duplicate of this bug. *** -- 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 298119] KWallet mandatory
https://bugs.kde.org/show_bug.cgi?id=298119 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #3 from Laurent Montel --- I very tired to read mail as "After 8 years of happy KDE usage I am now on the verge to abandon KDE alltogether if this is not fixed soon. " if you are not happy use an other "DE" I don't have time to fix all bugs and I tired to read it. So Ok perhaps it's a bug, perhaps you don't like it but I am not motivate to fix bug where guy are all the time not happy... -- 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 298128] New: Kontact crashes after crash of korgac
https://bugs.kde.org/show_bug.cgi?id=298128 Bug ID: 298128 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crashes after crash of korgac Classification: Unclassified OS: Linux Reporter: p...@flipp-w.de Hardware: Debian testing Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.4.11) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.2.0-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (wheezy) -- Information about the crash: By starting Kontact and waiting for a few minutes, the korganizer reminder (korgac) crashes reproducibly. From time to time Kontact itself crashes as well afterwards. This is happening since I sync my calendar and addressbook via kdepim-caldav (1.2.0-1) and kdepim-carddav (0.3.0-1) to an OwnCloud 3.0 server. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7f56e2503475 in *__GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f56e25066f0 in *__GI_abort () at abort.c:92 #8 0x7f56e253d26b in __libc_message (do_abort=, fmt=) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189 #9 0x7f56e25be077 in *__GI___fortify_fail (msg=0x7f56e261bd48 "longjmp causes uninitialized stack frame") at fortify_fail.c:32 #10 0x7f56e25be009 in longjmp_chk () at ../sysdeps/unix/sysv/linux/x86_64/longjmp_chk.S:86 #11 0x7f56e25bdf73 in __longjmp_chk (env=0x7f56c3afece0, val=1) at ../setjmp/longjmp.c:40 #12 0x7f56c38a5195 in alarmfunc (sig=) at hostip.c:515 #13 #14 0x7f56e259ecc3 in *__GI___poll (fds=, nfds=, timeout=999) at ../sysdeps/unix/sysv/linux/poll.c:87 #15 0x7f56dbf875d8 in g_main_context_poll (n_fds=9, fds=0x15abf80, timeout=999, context=0x7b2480, priority=) at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c:3391 #16 g_main_context_iterate (context=0x7b2480, block=, dispatch=1, self=) at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c:3071 #17 0x7f56dbf87a99 in g_main_context_iteration (context=0x7b2480, may_block=1) at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c:3139 #18 0x7f56e2ceae2f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #19 0x7f56e3752eee in QGuiEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQtGui.so.4 #20 0x7f56e2cbf492 in QEventLoop::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #21 0x7f56e2cbf68f in QEventLoop::exec(QFlags) () from /usr/lib/libQtCore.so.4 #22 0x7f56e2cc3837 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #23 0x004038ac in main (argc=1, argv=0x7fffb16ad708) at ../../../kontact/src/main.cpp:226 This bug may be a duplicate of or related to bug 272236. Possible duplicates by query: bug 281476, bug 272236. Reported using DrKonqi -- 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 298083] Duplicate message conflict due to "Mark selected message as read after" option when opening a message
https://bugs.kde.org/show_bug.cgi?id=298083 --- Comment #4 from p...@gmx.com --- Thx for this fast fix! Regards PiNy -- 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 298124] Filtered mails are not deleted from pop3 server
https://bugs.kde.org/show_bug.cgi?id=298124 Sebastien ROHAUT changed: What|Removed |Added Version|unspecified |4.8.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
[Bug 298124] New: Filtered mails are not deleted from pop3 server
https://bugs.kde.org/show_bug.cgi?id=298124 Bug ID: 298124 Severity: normal Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Filtered mails are not deleted from pop3 server Classification: Unclassified OS: Linux Reporter: sebastien.roh...@free.fr Hardware: Fedora RPMs Status: UNCONFIRMED Component: filtering Product: kmail2 User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.162 Safari/535.19 Build Identifier: Hi I created a filter to automatically move some mail in a folder, Mail is filtered form its subject containing '[Pacemaker]' and moved to a folder named pacemaker. When a mail is received, it's moved. But when I change folder and come back to my inbox folder, mail is received again, and again, and again. So it seems a filtered mail is not deleted from pop3 server. If I remove the filter, the mail is received juste once. Reproducible: Always Steps to Reproduce: 1. Use pop3 account (default values : mails are deleted from server) 2. Create a filter => move to a folder 3. send yourself a mail corresponding to the filter 4. mail is coming again, and again, and again... Actual Results: Mail received multiple times. Expected Results: Mail received just once and deleted from pop server KMail 4.8.2, Fedora core 16. -- 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 223038] kaddressbook come up empty & unusable though it is has been configured & usable for years!
https://bugs.kde.org/show_bug.cgi?id=223038 Martin van Es changed: What|Removed |Added CC||b...@mrvanes.com --- Comment #3 from Martin van Es --- I've had the same problem and solved it by deleting any configuration file (not addressbooks) I could find for kaddressbook. Probably due to some unresolvable legacy settings from earlier versions? $ find -name kaddr* ./.kde/share/config/kaddressbookrc ./.kde/share/config/kaddressbookmigratorrc $ find -name kaddr* -delete (check output first!!) -- 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 298121] akonadi_agent_launcher claims 1.7GB of 2GB memory - system stalls
https://bugs.kde.org/show_bug.cgi?id=298121 --- Comment #1 from Philip Nystromer --- Sorry, akonadi is not installed (deprecated in version 4.7 I presume) My akonadi components are thus: akonadi-server 1.7.1 akonadiconsole 4.7.4 -- 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 298119] KWallet mandatory
https://bugs.kde.org/show_bug.cgi?id=298119 --- Comment #2 from Philip Nystromer --- Franz, Thanks for your considerate tip. But I do not want to type my password for each kde session. I log into my kde-session using a password. And that should be enough. No more password typing after that, for the applications I have configured with passwords. Please. -- 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 298121] New: akonadi_agent_launcher claims 1.7GB of 2GB memory - system stalls
https://bugs.kde.org/show_bug.cgi?id=298121 Bug ID: 298121 Severity: major Version: 4.7 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: akonadi_agent_launcher claims 1.7GB of 2GB memory - system stalls Classification: Unclassified OS: Linux Reporter: philip.nystro...@telia.com Hardware: Gentoo Packages Status: UNCONFIRMED Component: general Product: Akonadi Efter logging into KDE4 my system becomes sluggish for at least 10 - 15 minutes. The problem seems to be that akonadi_agent_launcher claims 1.7GB of my 2GB memory. During the first minute after login akonadi_agent_launcher rapidly claims more and more RAM until 85-90% of my RAM is consumed. During these 10-15 minutes my hard disk is frantically active and my system is in practice not usable. The parent process to akonadi_agent_launcher is akonadi_control. My akonadi component versions are: akonadi 4.4.11.1 akonadi-server 1.7.1 akonadiconsole 4.7.4 -- 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 298119] KWallet mandatory
https://bugs.kde.org/show_bug.cgi?id=298119 Franz Fellner changed: What|Removed |Added CC||alpine.art...@googlemail.co ||m --- Comment #1 from Franz Fellner --- Then configure kwallet to fit your needs. Go to the settings dialog, there are a few options, when to close kwallet. You can tell kwallet to never close, so you have to type your kwallet-password only once for each kde-session. -- 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 298083] Duplicate message conflict due to "Mark selected message as read after" option when opening a message
https://bugs.kde.org/show_bug.cgi?id=298083 --- Comment #3 from Laurent Montel --- Git commit 0cb710fa5941b3f2aa0b618358aedb7f6911fd11 by Montel Laurent. Committed on 14/04/2012 at 16:13. Pushed by mlaurent into branch 'KDE/4.8'. Fix Bug 298083 - Duplicate message conflict due to "Mark selected message as read after" option when opening a message Use a static list of item. So don't call twice markmessage as read FIXED-IN: 4.8.3 (cherry picked from commit 96e0aebc909496e982b627f555610dc4973fc5c1) M +5-2messageviewer/markmessagereadhandler.cpp http://commits.kde.org/kdepim/0cb710fa5941b3f2aa0b618358aedb7f6911fd11 -- 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 298083] Duplicate message conflict due to "Mark selected message as read after" option when opening a message
https://bugs.kde.org/show_bug.cgi?id=298083 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.8.3 Resolution|--- |FIXED --- Comment #2 from Laurent Montel --- Git commit 96e0aebc909496e982b627f555610dc4973fc5c1 by Montel Laurent. Committed on 14/04/2012 at 16:13. Pushed by mlaurent into branch 'master'. Fix Bug 298083 - Duplicate message conflict due to "Mark selected message as read after" option when opening a message Use a static list of item. So don't call twice markmessage as read FIXED-IN: 4.8.3 M +5-2messageviewer/markmessagereadhandler.cpp http://commits.kde.org/kdepim/96e0aebc909496e982b627f555610dc4973fc5c1 -- 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 298119] New: KWallet mandatory
https://bugs.kde.org/show_bug.cgi?id=298119 Bug ID: 298119 Severity: normal Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: KWallet mandatory Classification: Unclassified OS: Linux Reporter: philip.nystro...@telia.com Hardware: Gentoo Packages Status: UNCONFIRMED Component: config dialog Product: kmail2 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/533.3 (KHTML, like Gecko) konqueror/4.7.4 Safari/533.3 Build Identifier: I recently upgraded from KDE 4.4 to 4.7, which includes KMail2 I found that I could no longer can configure passwords to my e-mail accounts in KMail2 itself. I am forced to use KWallet. This is not acceptable. I do not want to use KWallet. I am extremely annoyed by having to re-type my password every now and then, when KWallet pops up and asks for it. After 8 years of happy KDE usage I am now on the verge to abandon KDE alltogether if this is not fixed soon. I suggest that developers implement handling of passwords as they were in versions before KMail2 (i.e. it is possible to configure passwords per e-mail account in the KMail2 application itself) and that the storage of passwords is made as safe as state of the art provides. There has to be a choice if one wants to use KWallet or not. Reproducible: Always I run Kmail 4.7.4-r1 -- 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 298083] Duplicate message conflict due to "Mark selected message as read after" option when opening a message
https://bugs.kde.org/show_bug.cgi?id=298083 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I confirm it Will look at -- 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 295700] After upgrade to 4.8.1: QMYSQL3 is unable to execute statement due to BINLOG_FORMAT = STATEMENT
https://bugs.kde.org/show_bug.cgi?id=295700 --- Comment #5 from Franz Häuslschmid --- (In reply to comment #3) > What MySQL server version are you using? MySQL tells me: ~> /usr/sbin/mysqld --version /usr/sbin/mysqld Ver 5.5.16 for Linux on x86_64 (Source distribution) -- 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 297696] Clang needs QHash Templates in Parenthesis
https://bugs.kde.org/show_bug.cgi?id=297696 Volker Krause changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Volker Krause --- Git commit 2ddfb99ecfb8a9c569466c84e9e2362609211ba3 by Volker Krause. Committed on 14/04/2012 at 15:08. Pushed by vkrause into branch '1.7'. Build with Clang. (cherry picked from commit 1ce93440f9dbfcd01a3f4c9f120e82a7dfb2) M +2-2server/src/nepomuk/queryserviceclient.h http://commits.kde.org/akonadi/2ddfb99ecfb8a9c569466c84e9e2362609211ba3 -- 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 295700] After upgrade to 4.8.1: QMYSQL3 is unable to execute statement due to BINLOG_FORMAT = STATEMENT
https://bugs.kde.org/show_bug.cgi?id=295700 Volker Krause changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Volker Krause --- Git commit 8f6eb20aaa854224a6d4070ee2459290ec431576 by Volker Krause. Committed on 14/04/2012 at 14:50. Pushed by vkrause into branch 'master'. Set the MySQL binlog format explicitly. The combination of the transaction isolation level we use and the default binlog format doesn't work. Newer MySQL versions (>= 5.5 apparently) automatically switch to a supported format, older ones just fail. We don't actually enable the binlog, nor do we need it, so I don't really know why it's on for some users in the first place. M +5-0server/src/storage/mysql-global.conf http://commits.kde.org/akonadi/8f6eb20aaa854224a6d4070ee2459290ec431576 -- 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 295700] After upgrade to 4.8.1: QMYSQL3 is unable to execute statement due to BINLOG_FORMAT = STATEMENT
https://bugs.kde.org/show_bug.cgi?id=295700 Volker Krause changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||vkra...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #3 from Volker Krause --- What MySQL server version are you using? -- 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 261612] should tell me that the server address is not an SMTP server
https://bugs.kde.org/show_bug.cgi?id=261612 --- Comment #2 from Alexander van Loon --- To be honest I don't know, but I suspected that if a mail client sends some requests to an SMTP server, for example credentials to log in, the SMTP server should answer that request according to the SMTP protocol. If that is not the case, doesn't that lead to the conclusion that either the address is invalid, the server at that address is not an SMTP server, or that the SMTP server at that address is temporarily down. If it's not possible to determine that it's not an SMTP server, maybe the error message could be made more helpful: 'The server could not be contacted at this address, verify if the address is correct or try again later' or something like that. -- 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 297541] kaddressbook doesn't handle line breaks correctly in the notes field.
https://bugs.kde.org/show_bug.cgi?id=297541 --- Comment #5 from Divan Santana --- KDE devs, I can provide a Zimbra account for testing without a problem or any other information needed to help. Thanks for the efforts. -- 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 297678] Selecting multiple folders caused a crash
https://bugs.kde.org/show_bug.cgi?id=297678 Sebastien ROHAUT changed: What|Removed |Added CC||sebastien.roh...@free.fr --- Comment #1 from Sebastien ROHAUT --- I confirm this bug. In general Kmail seems to have many segfaults problems when manipulating folders. -- 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 297858] KMail crashes when moving a folder
https://bugs.kde.org/show_bug.cgi?id=297858 Sebastien ROHAUT changed: What|Removed |Added CC||sebastien.roh...@free.fr --- Comment #2 from Sebastien ROHAUT --- I confirm this bug. In 4.8.1 and 4.8.2. Doesn't crash if i move messages only. Crash When moving folders. -- 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 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."
https://bugs.kde.org/show_bug.cgi?id=246027 --- Comment #13 from Christophe Giboudeaux --- # qdbus | grep -C5 org.kde.pim.SpecialCollections org.kde.StatusNotifierItem-27845-1 :1.742 org.freedesktop.Akonadi.Agent.akonadi_imap_resource_1 org.freedesktop.Akonadi.Resource.akonadi_imap_resource_1 org.kde.akonadi_imap_resource_1-32487 org.kde.pim.SpecialCollections :1.743 :1.744 org.freedesktop.Akonadi.Agent.akonadi_imap_resource_2 org.freedesktop.Akonadi.Resource.akonadi_imap_resource_2 org.kde.akonadi_imap_resource_2-32515 -- 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 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."
https://bugs.kde.org/show_bug.cgi?id=246027 Christophe Giboudeaux changed: What|Removed |Added Version|2.0.89 |4.8 -- 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 246027] Kmail stoped with: KMail encountered a fatal error and will terminate now. The error was: Timeout trying to get lock."
https://bugs.kde.org/show_bug.cgi?id=246027 Christophe Giboudeaux changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #12 from Christophe Giboudeaux --- Valid in master I tried removing the Akonadi & Nepomuk data (including the config files) and restarting from scratch 3 dimap accounts added in akonadiconsole, the mail sync worked without issue, the nepomuk data are still being reindexed. Attaching gdb gives this: #6 0x7f418de15157 in QEventLoop::exec (this=0x7fffbf36c2f0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f418e817506 in QDialog::exec() () from /usr/lib64/libQtGui.so.4 #8 0x7f418f610619 in KMessageBox::createKMessageBox (dialog=0xf5f2d0, icon=..., text=..., strlist=..., ask=..., checkboxReturn=0x0, options=..., details= ..., notifyType=QMessageBox::Critical) at /kde/src/kdelibs/kdeui/dialogs/kmessagebox.cpp:344 #9 0x7f418f60f29d in KMessageBox::createKMessageBox (dialog=0xf5f2d0, icon=QMessageBox::Critical, text=..., strlist=..., ask=..., checkboxReturn=0x0, options=..., details=...) at /kde/src/kdelibs/kdeui/dialogs/kmessagebox.cpp:159 #10 0x7f418f613012 in KMessageBox::errorListWId (parent_id=0, text=..., strlist=..., caption=..., options=...) at /kde/src/kdelibs/kdeui/dialogs/kmessagebox.cpp:854 #11 0x7f418f612cb6 in KMessageBox::error (parent=0x0, text=..., caption=..., options=...) at /kde/src/kdelibs/kdeui/dialogs/kmessagebox.cpp:821 #12 0x7f4189da5a31 in MailCommon::Kernel::emergencyExit (this=0xa118d0, reason=...) at /kde/src/pim/kdepim/mailcommon/mailkernel.cpp:210 #13 0x7f4189da577e in MailCommon::Kernel::createDefaultCollectionDone (this=0xa118d0, job=0xcecf00) at /kde/src/pim/kdepim/mailcommon/mailkernel.cpp:173 #14 0x7f4189da6cee in MailCommon::Kernel::qt_static_metacall (_o=0xa118d0, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7fffbf36cca0) at /kde/build/pim/kdepim/mailcommon/mailkernel.moc:59 #15 0x7f418de29fe1 in QMetaObject::activate (sender=0xcecf00, m=, local_signal_index=, argv=0x7fffbf36cca0) at kernel/qobject.cpp:3556 #16 0x7f418f22be23 in KJob::result (this=0xcecf00, _t1=0xcecf00) at /kde/build/kdelibs/kdecore/kjob.moc:208 #17 0x7f418f22b2e7 in KJob::emitResult (this=0xcecf00) at /kde/src/kdelibs/kdecore/jobs/kjob.cpp:318 #18 0x7f418a2d6dd2 in Akonadi::SpecialCollectionsRequestJobPrivate::lockResult (this=0xcfafe0, job=0xb64040) at /kde/src/pim/kdepimlibs/akonadi/specialcollectionsrequestjob.cpp:121 #19 0x7f418a2d8ac5 in Akonadi::SpecialCollectionsRequestJob::qt_static_metacall (_o=0xcecf00, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffbf36cee0) at /kde/build/pim/kdepimlibs/akonadi/specialcollectionsrequestjob.moc:55 #20 0x7f418de29fe1 in QMetaObject::activate (sender=0xb64040, m=, local_signal_index=, argv=0x7fffbf36cee0) at kernel/qobject.cpp:3556 #21 0x7f418f22be23 in KJob::result (this=0xb64040, _t1=0xb64040) at /kde/build/kdelibs/kdecore/kjob.moc:208 #22 0x7f418f22b2e7 in KJob::emitResult (this=0xb64040) at /kde/src/kdelibs/kdecore/jobs/kjob.cpp:318 #23 0x7f418a2d4bbf in Akonadi::GetLockJob::Private::timeout (this=0x9e1420) at /kde/src/pim/kdepimlibs/akonadi/specialcollectionshelperjobs.cpp:610 #24 0x7f418a2d53b6 in Akonadi::GetLockJob::qt_static_metacall (_o=0xb64040, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7fffbf36d090) at /kde/build/pim/kdepimlibs/akonadi/specialcollectionshelperjobs_p.moc:211 #25 0x7f418de29fe1 in QMetaObject::activate (sender=0x951d90, m=, local_signal_index=, argv=0x0) at kernel/qobject.cpp:3556 -- 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 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 --- Comment #127 from torsten.nordh...@abwesend.de --- Created attachment 70374 --> https://bugs.kde.org/attachment.cgi?id=70374&action=edit New crash information added by DrKonqi kontact (4.8.2) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1 - What I was doing when the application crashed: Returned from acpi standby, restored Kontact Window from minimized window list entry, then read a mail. After selecting another mail, Kontact crashed. -- Backtrace (Reduced): #6 QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x357fb30, hm=..., sc=, rp=..., pu=, db=..., contentLength=-1) at access/qnetworkaccesshttpbackend.cpp:827 #7 0x7fb2b4490709 in QNetworkAccessHttpBackend::qt_static_metacall (_o=0x357fb30, _c=, _id=, _a=) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #8 0x7fb2b9584446 in QObject::event (this=0x357fb30, e=) at kernel/qobject.cpp:1195 #9 0x7fb2b9f5f894 in notify_helper (e=0x7fb23400a8e0, receiver=0x357fb30, this=0x1c9ea80) at kernel/qapplication.cpp:4559 #10 QApplicationPrivate::notify_helper (this=0x1c9ea80, receiver=0x357fb30, e=0x7fb23400a8e0) at kernel/qapplication.cpp:4531 -- 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 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 torsten.nordh...@abwesend.de changed: What|Removed |Added CC||torsten.nordhoff@abwesend.d ||e -- 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 298108] New: Cannot add a flux rss with right click > open with akregator
https://bugs.kde.org/show_bug.cgi?id=298108 Bug ID: 298108 Severity: normal URL: http://forum.kde.org/viewtopic.php?f=18&t=98403 Version: 1.6.6 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Cannot add a flux rss with right click > open with akregator Classification: Unclassified OS: Linux Reporter: dgl...@gmail.com Hardware: Mageia RPMs Status: UNCONFIRMED Component: general Product: akregator User-Agent: Mozilla/5.0 (compatible; Konqueror/4.6; Linux) KHTML/4.6.5 (like Gecko) Mageia/4.6.5-1.6.mga1 Build Identifier: In many sites there are links with a .atom link. I click on the link and i choose "Open with Akregator" But i dont have it in my RSS flux in akregator after this action If i copy the link and after i open akregator > Flux > add flux, it insert the flux in my RSS list in Akregator. An example is here: http://linuxfr.org/users/coin--2/journaux/disparition-des-flux-rss click on the "Suivre le flux des commentaires" at the bottom of the page or directly on the link: http://linuxfr.org/nodes/90266/comments.atom Reproducible: Always Steps to Reproduce: 1. Clic on the url http://linuxfr.org/nodes/90266/comments.atom in the bottom of the page http://linuxfr.org/users/coin--2/journaux/disparition-des-flux-rss 2. Open with Akregator Actual Results: 3. It does not insert it as a flux in akregator. Akregator just opens without perform any action Expected Results: Insert the flux in the list with the followed flux with the default settings or open the insert dialog to confirm the importation My browser is konqueror -- 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
