[kmail2] [Bug 290774] Kmail cannot send emails : Failed to get D-Bus interface of mailfilteragent.
https://bugs.kde.org/show_bug.cgi?id=290774 Thomas Baag changed: What|Removed |Added CC||tho...@b2ag.de --- Comment #27 from Thomas Baag --- > mv .kde4/share/apps/kmail2 .kde4/share/apps/kmail2.disabled Removing old kde4 settings for kmail 5 fixed this issue for me. Kudos to Prosiedem. -- 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 353987] Incomplete CardDav sync with ownCloud
https://bugs.kde.org/show_bug.cgi?id=353987 nxe...@yahoo.com changed: What|Removed |Added CC||nxe...@yahoo.com --- Comment #3 from nxe...@yahoo.com --- Hi, Using the same setup I can see no contacts in my list. Adding a contact with Kaddressbook correctly syncs with the server. It appears on the server and Kaddressbook. Deleting the contact works correctly too, no matter if deleted on the server or Kaddressbook. No contact added or already on the server will show up in Kaddressbook. Deleting the akonadi config and database as well as anything find "kaddressbook*", kmail, korganiser did not help. I also use kubuntu 15.10, kaddressbook is version 5.0.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
[kleopatra] [Bug 355298] Outlook 2013 hangs after Kleopatra 2.2.0 asks for passphrase when performing signing, encryption, verification, etc.
https://bugs.kde.org/show_bug.cgi?id=355298 gu...@hotmail.com changed: What|Removed |Added Version|git master |2.2.0 --- Comment #3 from gu...@hotmail.com --- You're most welcome, Andre. Thank you for your quick reply, and for taking the time to review my submission. If you need more information please let me know. -- 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
[kleopatra] [Bug 355298] Outlook 2013 hangs after Kleopatra 2.2.0 asks for passphrase when performing signing, encryption, verification, etc.
https://bugs.kde.org/show_bug.cgi?id=355298 --- Comment #2 from Andre Heinecke --- thanks for your report. Although I can't reproduce this It is very interesting that this is reproducable for you. The original issue that Outlook hangs while kleo / gpgol is working is tracked here: https://bugs.gnupg.org/gnupg/issue2136 I intend to fix this in the next months but still the current code should not block indefinitely. chan_05FC <- INPUT FD=1472 KDPipeIODevice::doOpen (0x45eb4e8): created reader (0x45f2290) for fd -1 This looks extremely fishy. fd -1 is an invalid handle. It should open it for fd 1472 I'll have to look at the code a bit to figure out the circumstances under which this could happen. -- 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
[kleopatra] [Bug 355298] Outlook 2013 hangs after Kleopatra 2.2.0 asks for passphrase when performing signing, encryption, verification, etc.
https://bugs.kde.org/show_bug.cgi?id=355298 --- Comment #1 from gu...@hotmail.com --- I forgot to add that using Kleopatra to work with filesystem objects, certificates, etc. works with no issue. The issue only appears when working within Outlook 2013. I just noticed the following as part of the GpgOL log. Notice pipe being closed. Could a problem in GpgOL make it appear that Kleopatra was at fault (restarting Kleopatra gave me control of Outlook message window)? 6531/1772/oomhelp.cpp:get_pa_string: Lookup result: ; 46656/1772/engine-assuan.c:op_assuan_sign: suggested protocol is 1000 46656/1772/engine-assuan.c:op_assuan_sign: using protocol OpenPGP 06703/4120/ERROR/engine-assuan.c:worker_start_write: [ input:3180] write error: The pipe is being closed. (232) 06703/4120/ERROR/engine-assuan.c:async_worker_thread: [status:30E8] GetOverlappedResult failed: The specified network name is no longer available. (64) 06703/1772/engine.c:engine_wait: filter 1D270048 ready: Input/output error 06703/1772/ribbon-callbacks.cpp:do_composer_action: failed rc=553680945 (Input/output error) 06703/1772/engine.c:engine_cancel: filter 1D270048: canceled 06703/1772/ribbon-callbacks.cpp:do_composer_action: leave -- 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
[kleopatra] [Bug 355298] New: Outlook 2013 hangs after Kleopatra 2.2.0 asks for passphrase when performing signing, encryption, verification, etc.
https://bugs.kde.org/show_bug.cgi?id=355298 Bug ID: 355298 Summary: Outlook 2013 hangs after Kleopatra 2.2.0 asks for passphrase when performing signing, encryption, verification, etc. Product: kleopatra Version: git master Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: gu...@hotmail.com CC: kdepim-bugs@kde.org, m...@kde.org Installed Kleopatra as part of GPG4Win (vice Gnu Privacy Assistant - GPA). Kleopatra component allowed me to perform signing and encryption for some time, but has stopped working in the past few months. When attempting to sign, encrypt, or verify messages, I am prompted for a passphrase which I enter and upon submission of the passphrase Outlook 2013 message composition screen hangs immediately (Not Responding in title bar). I initially thought the issue was with GpgOL, but found if I terminate Kleopatra using the task manager, I get control of Outlook again, but have to log out and back in to reproduce (or terminate other running processes associated with Gpg4win). I upgraded to latest release of GPG4Win 2.2.6 and found that the issue persisted with Kleopatra 2.2.0. I am able to work around this by removing and reinstalling Gpg4win and using GPA but wanted to take the time to report this to see if others are affected. I have captured some logs for Kleopatra and other components in case the problem lies with another application component. Reproducible: Always Steps to Reproduce: 1. Create a new message in Outlook 2013. 2. Click the GpgOL tab in the ribbon bar. 3. Attempt to sign or encrypt a message. 4. Enter and submit passphrase. Actual Results: Outlook message editor screen hangs (Outlook message displays Not Responding in Title Bar). Expected Results: Message should be signed or encrypted and display public key in message body. chan_05FC -> OK GPG UI server (Kleopatra/2.2.0-git49bbf03 (2015-08-20)) ready to serve chan_05FC <- GETINFO pid chan_05FC -> D 5024 chan_05FC -> OK chan_05FC <- OPTION window-id=1 chan_05FC -> OK chan_05FC <- RESET chan_05FC -> OK chan_05FC <- [error: Resource temporarily unavailable] chan_05FC <- SESSION 1 GpgOL chan_05FC -> OK chan_05FC <- SENDER -- chan_05FC -> # ok, parsed as "" count_signing_certificates( OpenPGP, ) == 1 count_signing_certificates( CMS, ) == 0 chan_05FC -> S PROTOCOL OpenPGP chan_05FC -> OK chan_05FC <- INPUT FD=1472 KDPipeIODevice::doOpen (0x45eb4e8): created reader (0x45f2290) for fd -1 chan_05FC -> OK chan_05FC <- OUTPUT FD=1416 KDPipeIODevice::doOpen (0x45eb178): created writer (0x45f4af0) for fd -1 chan_05FC -> OK chan_05FC <- SIGN --protocol=OpenPGP 0x45d9270: KDPipeIODevice::readData: data=0x45d0ac0, maxSize=512 KDPipeIODevice::Private::startReaderThread(): locking reader (CONSUMER THREAD) KDPipeIODevice::Private::startReaderThread(): locked reader (CONSUMER THREAD) KDPipeIODevice::Private::startReaderThread(): waiting for hasStarted (CONSUMER THREAD) 0x45f2290: Reader::run: started 0x45f2290: Reader::run: rptr=0, wptr=0 -> numBytes=4096 0x45f2290: Reader::run: trying to read 4096 bytes from fd -1 KDPipeIODevice::Private::startReaderThread(): returned from hasStarted (CONSUMER THREAD) 0x45d9270: KDPipeIODevice::readData: try to lock reader (CONSUMER THREAD) 0x45d9270: KDPipeIODevice::readData: locked reader (CONSUMER THREAD) 0x45d9270: KDPipeIODevice::readData: waiting for bufferNotEmptyCondition (CONSUMER THREAD) -- 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 332358] Regression: Baloo for tags messes up categories/groups when syncing with external collections (e.g. owncloud)
https://bugs.kde.org/show_bug.cgi?id=332358 Paulo changed: What|Removed |Added CC||paulac@gmail.com --- Comment #25 from Paulo --- Hi there, as I could not manage my google contacts with Kontact, I switched to OwnCloud. Unfortunately, even if it is better than previously, there is still a problem with categories/groups : they are not managed ! Moreover I was wondering if the global interface for contacts management will evolve : I found out that the Evolution's one is better (more visual and easier to edit contacts). If I can help, I will be glad to! Opensuse 13.2 / KDE 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
[kmail2] [Bug 349711] KMail 4.14.9 hangs when sending (signed) message
https://bugs.kde.org/show_bug.cgi?id=349711 Axel Braun changed: What|Removed |Added Summary|KMail 4.14.9 hangs when |KMail 4.14.9 hangs when |sending signed message |sending (signed) message -- 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 349711] KMail 4.14.9 hangs when sending signed message
https://bugs.kde.org/show_bug.cgi?id=349711 --- Comment #1 from Axel Braun --- Having had some trouble with the 'hang on send' , my impression is that it is not necessarily related to GPG signature, but has to do with network connectivity - if you have used KDE without network, it is more likely to hang. After killing a hanging KMail and restarting akonadi, turning KMail into offline mode and switching the network physically off with the RF kill switch, I can use KMail sending the mails that previously hang (at least into the send folder). As soon as I turn the network on (KMail still in offline mode), the sending of mails hangs again. Rebooting the PC does not help. Appears in 4.14.10 as well -- 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 348491] Multiple MySQL table structure errors
https://bugs.kde.org/show_bug.cgi?id=348491 Martin Steigerwald changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #10 from Martin Steigerwald --- Sorry, I meant to close it. -- 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 348491] Multiple MySQL table structure errors
https://bugs.kde.org/show_bug.cgi?id=348491 Martin Steigerwald changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #9 from Martin Steigerwald --- Thanks. Closing. To me this deadlock thing still hints at that at some time two mysqld has been running. Well if it works for you now, all the better. Feel free to reopen if you see this again. -- 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 349728] Filter not fully applied before sending messages
https://bugs.kde.org/show_bug.cgi?id=349728 swisscar...@users.sourceforge.net changed: What|Removed |Added CC||swisscarbon@users.sourcefor ||ge.net -- 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 355279] New: Kontact crashes on App Start
https://bugs.kde.org/show_bug.cgi?id=355279 Bug ID: 355279 Summary: Kontact crashes on App Start 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: ewan...@dorfsvald.net Application: kontact (4.13.3) KDE Platform Version: 4.13.3 Qt Version: 4.8.6 Operating System: Linux 3.13.0-68-generic x86_64 Distribution: Ubuntu 14.04.3 LTS -- Information about the crash: - What I was doing when the application crashed: I clicked on the kontact Icon, watch the little waiting icon, then had the crash report assistant. Has been this way every time I launch for two days -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc92c97b800 (LWP 20725))] Thread 7 (Thread 0x7fc90a3c3700 (LWP 20726)): #0 0x7fc929eec12d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fc923968fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc92396930a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc90fda5336 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7fc92398df05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc923e48182 in start_thread (arg=0x7fc90a3c3700) at pthread_create.c:312 #6 0x7fc929ef947d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 6 (Thread 0x7fc909bc2700 (LWP 20727)): #0 0x7fc9239aa61a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc9239aa979 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc923968ed5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc9239690ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc923969129 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc92398df05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fc923e48182 in start_thread (arg=0x7fc909bc2700) at pthread_create.c:312 #7 0x7fc929ef947d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 5 (Thread 0x7fc9093c1700 (LWP 20728)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7fc9239aace5 in g_cond_wait_until () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc92393f1c1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc92393f74b in g_async_queue_timeout_pop () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc92398e956 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc92398df05 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fc923e48182 in start_thread (arg=0x7fc9093c1700) at pthread_create.c:312 #7 0x7fc929ef947d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 4 (Thread 0x7fc8f7eab700 (LWP 20729)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc92772681d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fc927726859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fc923e48182 in start_thread (arg=0x7fc8f7eab700) at pthread_create.c:312 #4 0x7fc929ef947d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7fc89c498700 (LWP 20730)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc92746720d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fc927755fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fc923e48182 in start_thread (arg=0x7fc89c498700) at pthread_create.c:312 #4 0x7fc929ef947d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7fc88cd81700 (LWP 20733)): #0 0x7fc9239688db in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fc923968f52 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc9239690ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc92a6727be in QEventDispatcherGlib::processEvents (this=0x7fc8880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #4 0x7fc92a6440af in QEventLoop::processEvents (this=this@entry=0x7fc88cd80da0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fc92a6443a5 in QEventLoop::exec (this=this@entry=0x7fc88cd80da0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fc92a540c5f in QThread::exec (this=this@entry=0x14c6cd0) at thread/qthread.cpp:537 #7 0x7fc92a625823 in QInotifyFileSystemWatcherEngine::run (this=0x14c6cd0) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7fc92a54332f i
[kmail2] [Bug 355278] New: gmail messages can remain as "ghosts" after deletion
https://bugs.kde.org/show_bug.cgi?id=355278
Bug ID: 355278
Summary: gmail messages can remain as "ghosts" after deletion
Product: kmail2
Version: 4.14.7
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: message list
Assignee: kdepim-bugs@kde.org
Reporter: rjvber...@gmail.com
As reported (elsewhere?) already, there are cases where deleted messages from a
GMail account are not actually deleted at all, and remain as "ghosts",
greyed-out entries in kmail's message list that cannot be selected.
I just discovered that this also happens with entries in the Drafts folder,
after sending them.
Reproducible: Always
Steps to Reproduce:
1. configure a gmail account with the corresponding draft and wastebin ("Bin")
folders
2a. write and send a message
3a. delete any message from the active folder *before* having received the
notification that the message from (2) was sent successfully
OR
2b. compose a message, save it to the Drafts folder
3b. double-click to open it, and then send it.
4. select another folder, and then re-select the previous folder (this may need
to be done a few times)
Actual Results:
The message deleted under 3a. or sent under 3b. will reappear in the list, but
ghosted. It can no longer be selected.
Expected Results:
The message is supposed to have been deleted, so it should not reappear.
- this also applies to selections of multiple messages, in the 4.13 and 4.14
series on both Linux and OS X
- checking via GMail's web interface or a different client, the ghost messages
are indeed not deleted at all
- The effect of 3a. can be undone (*before* selecting another folder) by
hitting undo (^Z), waiting for the message to reappear as "not deleted", and
then deleting it again. After any message sending has completed of course.
- The effect can also be undone in akonadiconsole:
1. go to the folder in the browser tab
2. select the message: its attributes will show "/DELETED"
3. right-click the message, and *move* it to the account's Bin folder
Cleanup is a major feature IMHO, hence the Major severity I assigned to this
ticket.
--
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
