[kmail2] [Bug 335820] New: Unable to move mails from an imported folder to another one: Unable to retrieve item from resource: Invalid item retrieved
https://bugs.kde.org/show_bug.cgi?id=335820 Bug ID: 335820 Summary: Unable to move mails from an imported folder to another one: Unable to retrieve item from resource: Invalid item retrieved Classification: Unclassified Product: kmail2 Version: 4.13.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: renda.kr...@gmail.com I have a Local Folders resource in Akonadi used in KMail. Akonadi runs in a separate MySQL/MariaDB database. After importing thousands of mails from Thunderbird I tried to reorganize them a bit. Unfortunately, I'm unable to move a lot mails (not all) from an the imported folders to another one create new in KMail. It fails with a messagebox: "Unable to retrieve item from resource: Invalid item retrieved". From the user's point of view, I cannot recognize any problem with the original mail to move, no broken header, all intact. After some search, I'm able to find single mails which break this move action, but I don't know what is so special about them compared against the mails I moved successfully. Maybe one of you guys can give me a hint what else information could be useful for analyzing this. Reproducible: Sometimes Steps to Reproduce: 1. Import a folder structure from Thunderbird (I had 1 or more mails there) 2. Create another target folder structure in KMail under Local Folders 3. Move mails in several folders to the newly created folders Actual Results: "Unable to retrieve item from resource: Invalid item retrieved" during moving several mails in several folders Expected Results: Moving should succeed. -- 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
[kmail2] [Bug 326874] Local folder offline
https://bugs.kde.org/show_bug.cgi?id=326874 --- Comment #3 from Salvo "LtWorf" Tomaselli --- I migrated to an IMAP server+fetchmail. It is unreasonable to expect that I'd keep around for this many months those resources that wouldn't let me access my emails easily. -- 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
[knotes] [Bug 334357] knotes migration fails if akonadi is not running
https://bugs.kde.org/show_bug.cgi?id=334357 Wolfgang Bauer changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #5 from Wolfgang Bauer --- (In reply to comment #4) > This is definitely fixed in the 4.13.1 version, you should upgrade. This indeed seems to be fixed in 4.13.1, I cannot reproduce it any more. To be clear though, this bug report was about the migration timing out when Akonadi was not running already. The migration not working at all is Bug#333640. -- 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 335235] kmail & akonadi: imap resource cannot be accessed
https://bugs.kde.org/show_bug.cgi?id=335235 --- Comment #4 from hemathor --- thanks for answering! i tried the imap log and it seems to be an acl problem. the log sais: C: A000361 GETACL "Drafts" S: A000361 BAD Error in IMAP command GETACL: ACLs disabled. C: A000362 MYRIGHTS "Drafts" S: A000362 BAD Error in IMAP command MYRIGHTS: ACLs disabled. and so on for several subfolders. then: S: * BYE Too many invalid IMAP commands. X which is strange, since (a) it worked before flawlessly with the exact same imap account until i set up a kde environment from scratch, (b) i enabled the acl plugin in the dovecot imap configuration file, and (c) all other accounts don't seem to have that problem if you need anything else, pleas let me know greetings... -- 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
[kmail2] [Bug 326874] Local folder offline
https://bugs.kde.org/show_bug.cgi?id=326874 Khumba changed: What|Removed |Added CC||kde-bugs-68...@khumba.net --- Comment #2 from Khumba --- Does it work to open akonadiconsole and re-enable Local Folders manually (Right-click on Local Folders in akonadiconsole > Toggle Online/Offline)? Or is the resource continually being disabled? Also make sure that the Mail Dispatcher Agent is running, I think that needs to be online for mail to send. -- 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 335795] New: IMAP namespace support is incomplete/insufficient on large imap accounts
https://bugs.kde.org/show_bug.cgi?id=335795 Bug ID: 335795 Summary: IMAP namespace support is incomplete/insufficient on large imap accounts Classification: Unclassified Product: Akonadi Version: 4.13 Platform: unspecified OS: All Status: UNCONFIRMED Severity: grave Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: rjvber...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org I run an imap server on my main workstation, allowing me to archive email no matter from what computer I'm doing that. Those archives live under ~/Mail/Archives, and an imap client not ignoring everything above that path will spend a very long time indexing ~ (I had to kill and delete the resource when it hogged the whole computer after I let it run for about 2h). I've skimmed through a few discussions on kmail's approach to the "imap prefix path" most email readers support, and while I tend to agree that if namespaces are the standards compliant way to do things they should be used, I also think the implementation isn't without flaws. Let's ignore the fact that the current imap configuration dialog doesn't even mention namespaces (presumably replaced by server-side subscriptions?). The real gripe I have is that I apparently have to let the imap process index the full server-side contents before I can point it to the appropriate root folder (Mail/Archives). And it's not just an omission in the GUI: I tried simulating the required actions with a small imap account, and observed that apparently all mailboxes (folders) under the root are listed explicitly in the configuration file, rather than only the root folder. Which in my book is not using a namespace as any addition (new folder) will have to be added manually to the selection (requiring another lengthy indexing step). I'd suggest reinstating a simple "prefix path" feature that can be specified (= typed in) even before the first connection to a new imap account. It's only a single text entry field, and internally it could perfectly well be translated into the appropriate namespace magic. Reproducible: Always Steps to Reproduce: 1. set up an imap server on a workstation 2. Use Thunderbird, Apple's Mail.app, sylpheed, pine, just about any MUA to set up an email archive on that imap server, connecting with your work/home account on that, for instance under Mail/Archives (= ~/Mail/Archives) 3. Define an akonadi imap resource pointing to that same IMAP server, using the same login credentials 4. Sit back and wait ... Actual Results: A synchronisation step will be triggered that can take hours to complete if the user home directory (the "~" namespace) contains a large amount of files and folders, of which only 1 is relevant for the imap resource (Mail/Archives, and the mbox files contained therein). Expected Results: Given additional configuration options, either to specify a path prefix or to alter the namespace queried, or both (as Thunderbird does). I don't have direct experience using imap namespaces, but if they don't allow to specify the path to where the mailboxes are (to be) stored, an additional mechanism should be implemented. Again, just about any other email client allows to do that. Following standards nice, but it should not become a case of form over function. I'm marking this bug as "grave", because it requires serious workarounds if one is obliged to work with an imap server as outlined above. -- 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
[kmail2] [Bug 334170] IMAP accounts are always switched online at startup
https://bugs.kde.org/show_bug.cgi?id=334170 RJVB changed: What|Removed |Added CC||rjvber...@gmail.com --- Comment #1 from RJVB --- I concur, while it is a good idea to offline resources when quitting kmail, the very least would be to store and restore the state they had. That way, an account that was taken offline manually will remain so across restarts until it is onlined manually again. Note that this is how OS X's Mail.app works, and there too it is a setting that completes the account-specific settings whether and how often checks for new mail ought to be done. -- 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
[akregator] [Bug 312197] Increasing font size causes horizontal spacing errors
https://bugs.kde.org/show_bug.cgi?id=312197 --- Comment #3 from beojan --- Created attachment 87009 --> https://bugs.kde.org/attachment.cgi?id=87009&action=edit Shows bug with no size increase -- 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
[akregator] [Bug 312197] Increasing font size causes horizontal spacing errors
https://bugs.kde.org/show_bug.cgi?id=312197 beojan changed: What|Removed |Added CC||beo...@gmail.com --- Comment #2 from beojan --- This bug is not specific to increasing font size, and does not seem to be limited to any specific feed. It is simply more noticeable with some fonts than with others, and it appears to be unnoticeable with the default font settings gjditchfield has. It is especially noticeable with Droid Sans size 10. See attached screenshot. -- 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
[kdepim] [Bug 335793] New: messagecomposertest is unstable due to timing
https://bugs.kde.org/show_bug.cgi?id=335793 Bug ID: 335793 Summary: messagecomposertest is unstable due to timing Classification: Unclassified Product: kdepim Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: messagecomposer Assignee: kdepim-bugs@kde.org Reporter: aa...@kde.org See http://build.kde.org/view/KDE%20SC%20stable/job/kdepim_stable/1929/testReport/junit/%28root%29/TestSuite/messagecomposer_messagefactorytest/ - Resent-Date: Wed, 04 Jun 2014 11:47:21 + + Resent-Date: Wed, 04 Jun 2014 11:47:20 + It would be cool if it could be fixed not to have this kind of time based unstability -- 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
[kmail2] [Bug 287804] KMail use wrong encoding when initial fill the reply content
https://bugs.kde.org/show_bug.cgi?id=287804 Alexander D changed: What|Removed |Added CC||adb...@gmail.com --- Comment #8 from Alexander D --- same bug in version 4.12.4 with KDE 4.11.3 os: linux(debian) -- 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
[kmail2] [Bug 335781] New: KMail crash when answering to complex email
https://bugs.kde.org/show_bug.cgi?id=335781 Bug ID: 335781 Summary: KMail crash when answering to complex email Classification: Unclassified Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: tulan.kan...@gmail.com Application: kmail (4.12.5) KDE Platform Version: 4.12.5 Qt Version: 4.8.6 Operating System: Linux 3.14.4-200.fc20.x86_64 x86_64 Distribution: "Fedora release 20 (Heisenbug)" -- Information about the crash: - What I was doing when the application crashed: try to answer to HTML email with attached ZIP file to multiple recipients The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f4469629900 (LWP 2005))] Thread 4 (Thread 0x7f441cab3700 (LWP 2199)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x003ffa0bc1bd in JSC::BlockAllocator::blockFreeingThreadMain() () from /lib64/libQtWebKit.so.4 #2 0x003ffa3aea86 in WTF::wtfThreadEntryPoint(void*) () from /lib64/libQtWebKit.so.4 #3 0x003881c07f33 in start_thread (arg=0x7f441cab3700) at pthread_create.c:309 #4 0x0038814f4ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f4417b55700 (LWP 2200)): #0 0x00388408a2ea in g_mutex_get_impl () from /lib64/libglib-2.0.so.0 #1 0x00388408a5c9 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #2 0x0038840495a9 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x0038840496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x003d7c9b5af6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtCore.so.4 #5 0x003d7c98595f in QEventLoop::processEvents(QFlags) () from /lib64/libQtCore.so.4 #6 0x003d7c985cad in QEventLoop::exec(QFlags) () from /lib64/libQtCore.so.4 #7 0x003d7c879e8f in QThread::exec() () from /lib64/libQtCore.so.4 #8 0x003d7c87c6bf in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #9 0x003881c07f33 in start_thread (arg=0x7f4417b55700) at pthread_create.c:309 #10 0x0038814f4ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f4403cd8700 (LWP 4068)): #0 0x0038814ea9dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x0038840495b4 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x0038840496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x003d7c9b5af6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtCore.so.4 #4 0x003d7c98595f in QEventLoop::processEvents(QFlags) () from /lib64/libQtCore.so.4 #5 0x003d7c985cad in QEventLoop::exec(QFlags) () from /lib64/libQtCore.so.4 #6 0x003d7c879e8f in QThread::exec() () from /lib64/libQtCore.so.4 #7 0x003d7c9662e3 in QInotifyFileSystemWatcherEngine::run() () from /lib64/libQtCore.so.4 #8 0x003d7c87c6bf in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #9 0x003881c07f33 in start_thread (arg=0x7f4403cd8700) at pthread_create.c:309 #10 0x0038814f4ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f4469629900 (LWP 2005)): [KCrash Handler] #5 0x00310ae2c1b3 in QList::~QList() () from /lib64/libQtGui.so.4 #6 0x00310ae422f1 in QTextOption::operator=(QTextOption const&) () from /lib64/libQtGui.so.4 #7 0x00310ae6d849 in QTextDocumentLayoutPrivate::layoutBlock(QTextBlock const&, int, QTextBlockFormat const&, QTextLayoutStruct*, int, int, QTextBlockFormat const*) () from /lib64/libQtGui.so.4 #8 0x00310ae759f3 in QTextDocumentLayoutPrivate::layoutFlow(QTextFrame::iterator, QTextLayoutStruct*, int, int, QFixed) () from /lib64/libQtGui.so.4 #9 0x00310ae71004 in QTextDocumentLayoutPrivate::layoutCell(QTextTable*, QTextTableCell const&, QFixed, int, int, QTextTableData*, QFixed, bool) () from /lib64/libQtGui.so.4 #10 0x00310ae71b1c in QTextDocumentLayoutPrivate::layoutTable(QTextTable*, int, int, QFixed) () from /lib64/libQtGui.so.4 #11 0x00310ae73fd9 in QTextDocumentLayoutPrivate::layoutFrame(QTextFrame*, int, int, QFixed, QFixed, QFixed) () from /lib64/libQtGui.so.4 #12 0x00310ae74a30 in QTextDocumentLayoutPrivate::layoutFrame(QTextFrame*, int, int, QFixed) () from /lib64/libQtGui.so.4 #13 0x00310ae75f98 in QTextDocumentLayoutPrivate::layoutFlow(QTextFrame::iterator, QTextLayoutStruct*, int, int, QFixed) () from /lib64/libQtGui.so.4 #14 0x00310ae7433d in QTextDocumentLayoutPrivate::layoutFrame(QTextFrame*, int, int, QFixed, QFixed, QF
[kmail2] [Bug 335778] New: KMail crash
https://bugs.kde.org/show_bug.cgi?id=335778 Bug ID: 335778 Summary: KMail crash Classification: Unclassified Product: kmail2 Version: 4.13 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mmachakowi...@gmail.com Application: kmail (4.13) KDE Platform Version: 4.13.0 Qt Version: 4.8.6 Operating System: Linux 3.13.0-27-generic x86_64 Distribution: Ubuntu 14.04 LTS -- Information about the crash: - What I was doing when the application crashed:hitting "check mail" button,crashing constantly after checking mail. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f75a4b1d800 (LWP 10555))] Thread 6 (Thread 0x7f757dd6f700 (LWP 10558)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f759642981d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f7596429859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f759f800182 in start_thread (arg=0x7f757dd6f700) at pthread_create.c:312 #4 0x7f75a1f7330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7f753cbcf700 (LWP 10559)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f759616a20d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f7596458fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f759f800182 in start_thread (arg=0x7f753cbcf700) at pthread_create.c:312 #4 0x7f75a1f7330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7f7537bff700 (LWP 10560)): #0 0x7f7599f8a62d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f7599f8a9b9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7599f480f0 in g_main_context_acquire () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7599f48ea5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7599f490ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f75a290a7be in QEventDispatcherGlib::processEvents (this=0x7f7538c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x7f75a28dc0af in QEventLoop::processEvents (this=this@entry=0x7f7537bfede0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f75a28dc3a5 in QEventLoop::exec (this=this@entry=0x7f7537bfede0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f75a27d8c5f in QThread::exec (this=) at thread/qthread.cpp:537 #9 0x7f75a27db32f in QThreadPrivate::start (arg=0x137a100) at thread/qthread_unix.cpp:349 #10 0x7f759f800182 in start_thread (arg=0x7f7537bff700) at pthread_create.c:312 #11 0x7f75a1f7330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f75363ef700 (LWP 10561)): #0 0x7f7599f8a635 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f7599f8a989 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7599f48a6c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7599f48f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7599f490ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f75a290a7be in QEventDispatcherGlib::processEvents (this=0x7f75280008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #6 0x7f75a28dc0af in QEventLoop::processEvents (this=this@entry=0x7f75363eeda0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f75a28dc3a5 in QEventLoop::exec (this=this@entry=0x7f75363eeda0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f75a27d8c5f in QThread::exec (this=this@entry=0x1906360) at thread/qthread.cpp:537 #9 0x7f75a28bd823 in QInotifyFileSystemWatcherEngine::run (this=0x1906360) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x7f75a27db32f in QThreadPrivate::start (arg=0x1906360) at thread/qthread_unix.cpp:349 #11 0x7f759f800182 in start_thread (arg=0x7f75363ef700) at pthread_create.c:312 #12 0x7f75a1f7330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f7535997700 (LWP 10562)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f758c3edffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7f758c3ee039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7f759f800182 in start_thread (arg=0x7f7535997700) at pthread_create.c:312 #4 0x7f75a1f7330d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f75a4b1
[Akonadi] [Bug 335776] IMAP agent crashes frequently
https://bugs.kde.org/show_bug.cgi?id=335776
Christian Mollekopf changed:
What|Removed |Added
CC||mollek...@kolabsys.com
--- Comment #1 from Christian Mollekopf ---
Can you check in the debug output if the online state changed just before it
crashed?
You should see a message in doSetOnline ("online="),
--
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
[kaddressbook] [Bug 335651] Query Server don't use bindDN and password connect to server
https://bugs.kde.org/show_bug.cgi?id=335651 Sandro Knauß changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.13.2 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||imlibs/0a23465bc5ea2ba74e96 ||824670c71dc93cf80e32 --- Comment #1 from Sandro Knauß --- Git commit 0a23465bc5ea2ba74e96824670c71dc93cf80e32 by Sandro Knauß. Committed on 01/06/2014 at 15:42. Pushed by knauss into branch 'KDE/4.13'. Use credentials in the "Edit Host" window to query LDAP Server. If the server needs authentification to connect, the "Query Server" to get the namingcontexts should use the credentials. Related: bug 118496 FIXED-IN: 4.13.2 M +6-13 kldap/ldapconfigwidget.cpp http://commits.kde.org/kdepimlibs/0a23465bc5ea2ba74e96824670c71dc93cf80e32 -- 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
[kaddressbook] [Bug 287242] Empty error window when querying an ldap server
https://bugs.kde.org/show_bug.cgi?id=287242 Sandro Knauß changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||m...@sandroknauss.de Version Fixed In||4.14 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||imlibs/ac7cd652903aec90985b ||49a24a43c4b026978364 --- Comment #3 from Sandro Knauß --- Git commit ac7cd652903aec90985b49a24a43c4b026978364 by Sandro Knauß. Committed on 03/06/2014 at 15:17. Pushed by knauss into branch 'master'. Fix 287242 - Empty error window when querying an ldap server Showing a standard error text, when no one is returned from job. FIXED-IN: 4.14 REVIEW: 118502 M +5-1kldap/ldapconfigwidget.cpp http://commits.kde.org/kdepimlibs/ac7cd652903aec90985b49a24a43c4b026978364 -- 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 328421] Refactor session related codepaths to use jobs
https://bugs.kde.org/show_bug.cgi?id=328421 Christian Mollekopf changed: What|Removed |Added Priority|NOR |LO Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- 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 335235] kmail & akonadi: imap resource cannot be accessed
https://bugs.kde.org/show_bug.cgi?id=335235 Christian Mollekopf changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #3 from Christian Mollekopf --- For the "Too many invalid IMAP commands." problem we would probably need a imap log. You can find here http://techbase.kde.org/Projects/PIM/Akonadi/Debug_IMAP how to obtain one. -- 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
