[kmail2] [Bug 442884] DSN not working
https://bugs.kde.org/show_bug.cgi?id=442884 --- Comment #5 from dharman --- Any news about this issue? Currently it's not working yet. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 452825] "Request delivery confirmation" not working
https://bugs.kde.org/show_bug.cgi?id=452825 --- Comment #1 from dharman --- Any news about this issue? Currently it's not working yet. I think it's a regression, because with older version kmail the confirmation was workings. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 --- Comment #39 from dharman --- (In reply to Daniel Ziltener from comment #38) > Is anyone interested in baking a cake or throwing a party for this bug's > upcoming 9th or 10th birthday? It spent its entire life without a caretaker, > and I am sure it would enjoy spending some time with friendly people. I'm very so sorry, but I suspect kmail doesn't have developers that love it. Not only are there bugs like this, but also untreated regressions like delivery confirmation request. ;-( -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 452825] "Request delivery confirmation" not working
https://bugs.kde.org/show_bug.cgi?id=452825 dharman changed: What|Removed |Added CC||dhar...@10100.to -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 339214] Starting KMail gives message "Could not create collection trash resourceId: 3 [MailCommon::Kernel::createDefaultCollectionDone, MailCommon::Kernel::emergencyExit]
https://bugs.kde.org/show_bug.cgi?id=339214 dharman changed: What|Removed |Added CC||dhar...@10100.to -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 442884] DSN not working
https://bugs.kde.org/show_bug.cgi?id=442884 dharman changed: What|Removed |Added Version|5.13.3 |5.20.3 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 442884] DSN not working
https://bugs.kde.org/show_bug.cgi?id=442884 --- Comment #4 from dharman --- Is there any news about this regression? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 334213] Stuck "Mail filter agent" progressbar
https://bugs.kde.org/show_bug.cgi?id=334213 dharman changed: What|Removed |Added CC||dhar...@10100.to -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 442884] DSN not working
https://bugs.kde.org/show_bug.cgi?id=442884 dharman changed: What|Removed |Added CC||dhar...@10100.to Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from dharman --- I used Kmail 5.19.3(21.12.3) in Kubuntu 20.04 and DSN was working. After a new installation of Kubuntu 22.04 that has Kmail 5.20.3 (22.04.3) it dosn't woks again. I think it's a regression bug. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 316153] can't move or delete messages in imap inbox
https://bugs.kde.org/show_bug.cgi?id=316153 dharman changed: What|Removed |Added CC||dhar...@10100.to --- Comment #49 from dharman --- (In reply to eiapopeia13 from comment #43) > (In reply to Yasin Zähringer from comment #33) > > While investigating a different issue I found a workaround (which however > > does not address the root cause): > > start the akonadi console, select the browser tab and find the affected > > inbox. Right click on it and select folder properties. Now you find a tab > > called ACL and where probably all check boxes are deselected. I checked all > > boxes except the two boxes of the second row (link,unlink) because a > > subfolder also had these boxes unchecked. After I restarted KMail, I was > > finally able to move mails again. > > This worked for me too. (Kubuntu 16.04, Plasma 5, KMail 5.1.3) > Thank you! This seems fixing the problem in Kubuntu 22.04 too. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 401398] Kmail store sent email locally which is unexpected and unwanted
https://bugs.kde.org/show_bug.cgi?id=401398 dharman changed: What|Removed |Added CC||dhar...@10100.to --- Comment #1 from dharman --- (In reply to Freek from comment #0) > Created attachment 116499 [details] > Kmail setting where one should have been able to set a custom sent folder > > SUMMARY > Kmail store my sent email in a local folder instead of imap > > STEPS TO REPRODUCE > 1. Configure imap > 2. Sent email > > OBSERVED RESULT > Email is unfindable on all your other clients because kmail put it outside > your imap system. > > > EXPECTED RESULT > Email is in imap sent folder > > SOFTWARE/OS VERSIONS > Windows: > MacOS: > Linux/KDE Plasma: KDE Neon kmail2 5.9.3 > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > ADDITIONAL INFORMATION > > I found this > https://userbase.kde.org/KMail/ > FAQs_Hints_and_Tips#Store_sent_mails_in_a_special_folder that told me to set > the sent folder manually, but I don't have that setting, see attachment. > Anyway, who wants their sent folder local??? > > By the way I can't select 5.9.3 yet from the Version menu on this page :) I've the same problem...I've see your attachment, but seems it not corresponds to what you said. Instead, I think tath the problem is related to the configuration of identity (where you can store the "sent email destination folder". Is it correct? I'm using: - KDE NEON User edition - KMail 5.13.3 (19.12.3) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 416016] Akonadi can no longer start : /run/user/1000/akonadi problem
https://bugs.kde.org/show_bug.cgi?id=416016
--- Comment #6 from dharman ---
(In reply to Bruno Patri from comment #5)
> This is an issue with apparmor and Ubuntu. Everything works if the apparmor
> profile usr.bin.akonadiserver is disabled.
>
> It seems that the apparmor profile provided in the KDE Neon package
> akonadi-server needs at least a line to allow read and write in /run/user :
>
> owner /{,var/}run/user/@{uid}/akonadi** rwk,
>
> Not that this line is present in the master branch :
> https://cgit.kde.org/akonadi.git/tree/apparmor/usr.bin.akonadiserver
It works for me...thank you!
--
You are receiving this mail because:
You are the assignee for the bug.
[Akonadi] [Bug 416016] Akonadi can no longer start : /run/user/1000/akonadi problem
https://bugs.kde.org/show_bug.cgi?id=416016 dharman changed: What|Removed |Added CC||dhar...@10100.to --- Comment #3 from dharman --- (In reply to Christoph Feck from comment #2) > Plasma is unrelated to KDEPIM. Which other packages besides Plasma did you > update? Anything SQL database related? I've the same identical problem. I'm using KDE Neon LTE User edition and apply all suggested update everyday. I've nomore additional repositories but nextcloud-client one. After an upgrade (as suggested and processed by discover) from Plasma 5.17.4 to 5.17.5 and a normal reboot, Akonadi refused to start. Nothing else. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 395711] Since last Update kmail didn't load external images anymore
https://bugs.kde.org/show_bug.cgi?id=395711 dharman changed: What|Removed |Added CC||dhar...@10100.to --- Comment #5 from dharman --- I can confirm this bug. I'm using KDE neon Just an additional info: using the described workaround on "INBOX" the external resources are loaded. Re-enabling the checkbox, the external resources continue to be enabled. Different behavior in subfolders, where resources are loaded only with workaround applied -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 319171] Infinite popup message when imap connection error
https://bugs.kde.org/show_bug.cgi?id=319171 dharman dhar...@datashit.net changed: What|Removed |Added Summary|Infinite popup message when |Infinite popup message when |connection error|imap connection error -- 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 319171] New: Infinite popup message when connection error
https://bugs.kde.org/show_bug.cgi?id=319171 Bug ID: 319171 Summary: Infinite popup message when connection error Classification: Unclassified Product: Akonadi Version: 4.10 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: IMAP resource Assignee: er...@kde.org Reporter: dhar...@datashit.net CC: kdepim-bugs@kde.org, vkra...@kde.org First of all: sorry but I'm italian and so, many received messages are in my language. Anyway...when I try to connect to the IMAP server to retrieve messages but it's unable to receive new connections because too many already exists (dovecot server), I receive (correctly) an alert box that say: -- Il server dell'account «MyAccount» ha rifiutato il nome utente e la password forniti. Vuoi modificare le impostazioni, riprovare nuovamente ad accedere, o non fare nulla? Login failed, server replied: A03 NO Maximum number of connections from user+IP exceeded ( mail_max_userip_connections ) -- This happens too much. I receive infinite number of popup box (Approximatively 100. After that, I've rebooted my pc) All alert boxes are identical and I'm no more able to proceed to use my pc. Reproducible: Always Steps to Reproduce: 1. Connect with hostA (my andoid phone in push mode) to the IMAP server and occupies all the available connections 2. Open Kmail (to trigger akonadi) and try to dowload the messages 3. Done Actual Results: You receive the infinite alert boxes reporting the unavailability to connect Expected Results: A single box reporting the error. Full stop. (Better can be to use kde notification system) -- 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 309403] New: Kontact crash when quit
https://bugs.kde.org/show_bug.cgi?id=309403 Bug ID: 309403 Severity: crash Version: 4.9.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crash when quit Classification: Unclassified OS: Linux Reporter: dhar...@datashit.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9.2) KDE Platform Version: 4.9.2 Qt Version: 4.8.3 Operating System: Linux 3.5.0-17-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: - What I was doing when the application crashed: With preview panel showing a html message, I closed kontact. The window disappeared and after less than a second, it crashed The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f89ac8c77c0 (LWP 15465))] Thread 3 (Thread 0x7f89a4e72700 (LWP 15466)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f89bde39b2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f89bde39c39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f89b9388e9a in start_thread (arg=0x7f89a4e72700) at pthread_create.c:308 #4 0x7f89beb64cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 2 (Thread 0x7f8956ec1700 (LWP 15471)): #0 0x7f89beb59303 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f89b8eb9d84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f89b8eb9ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f89bf2d9c16 in QEventDispatcherGlib::processEvents (this=0x7f8958c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f89bf2aa2bf in QEventLoop::processEvents (this=this@entry=0x7f8956ec0d90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f89bf2aa548 in QEventLoop::exec (this=0x7f8956ec0d90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f89bf1abb10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f89bf28a9af in QInotifyFileSystemWatcherEngine::run (this=0x1bd8100) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f89bf1aeaec in QThreadPrivate::start (arg=0x1bd8100) at thread/qthread_unix.cpp:338 #9 0x7f89b9388e9a in start_thread (arg=0x7f8956ec1700) at pthread_create.c:308 #10 0x7f89beb64cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f89ac8c77c0 (LWP 15465)): [KCrash Handler] #6 0x7f89b746d627 in lockInline (this=0x1b80338) at /usr/include/qt4/QtCore/qmutex.h:187 #7 QMutexLocker (m=0x1b80338, this=synthetic pointer) at /usr/include/qt4/QtCore/qmutex.h:109 #8 Nepomuk::Resource::~Resource (this=0x7f893c0012d0, __in_chrg=optimized out) at ../../nepomuk/core/resource.cpp:142 #9 0x7f89b746d8d9 in Nepomuk::Resource::~Resource (this=0x7f893c0012d0, __in_chrg=optimized out) at ../../nepomuk/core/resource.cpp:147 #10 0x7f89bf2bc1ca in QMetaCallEvent::~QMetaCallEvent (this=0x7f893c0031a0, __in_chrg=optimized out) at kernel/qobject.cpp:509 #11 0x7f89bf2bc239 in QMetaCallEvent::~QMetaCallEvent (this=0x7f893c0031a0, __in_chrg=optimized out) at kernel/qobject.cpp:518 #12 0x7f89bf2afb6f in QCoreApplication::removePostedEvents (receiver=optimized out, eventType=0) at kernel/qcoreapplication.cpp:1669 #13 0x7f89bf2bf7ab in QObjectPrivate::~QObjectPrivate (this=0x1d4d9e0, __in_chrg=optimized out) at kernel/qobject.cpp:171 #14 0x7f89bf2bf819 in QObjectPrivate::~QObjectPrivate (this=0x1d4d9e0, __in_chrg=optimized out) at kernel/qobject.cpp:186 #15 0x7f89bf2c1ffc in cleanup (pointer=optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62 #16 ~QScopedPointer (this=0x19e3e58, __in_chrg=optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100 #17 QObject::~QObject (this=0x19e3e50, __in_chrg=optimized out) at kernel/qobject.cpp:817 #18 0x7f89b7473399 in Nepomuk::ResourceWatcher::~ResourceWatcher (this=0x19e3e50, __in_chrg=optimized out) at ../../nepomuk/core/resourcewatcher.cpp:81 #19 0x7f89bf2be182 in QObjectPrivate::deleteChildren (this=this@entry=0x1b80cf0) at kernel/qobject.cpp:1908 #20 0x7f89bf2c1fc6 in QObject::~QObject (this=0x1ae1430, __in_chrg=optimized out) at kernel/qobject.cpp:927 #21 0x7f89b7461b29 in Nepomuk::ResourceManager::~ResourceManager (this=0x1ae1430, __in_chrg=optimized out) at ../../nepomuk/core/resourcemanager.cpp:289 #22 0x7f89bf2be182 in QObjectPrivate::deleteChildren (this=this@entry=0x14cb340) at kernel/qobject.cpp:1908 #23 0x7f89bf2c1fc6 in
[Bug 286307] Kmail crash (QNetworkAccessHttpBackend::replyDownloadMetaData, QNetworkAccessHttpBackend::qt_static_metacall, QObject::event)
https://bugs.kde.org/show_bug.cgi?id=286307 dharman dhar...@datashit.net changed: What|Removed |Added CC|dhar...@datashit.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
[Bug 296613] New: Kontact crash switching beetween emails
https://bugs.kde.org/show_bug.cgi?id=296613 Bug ID: 296613 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crash switching beetween emails Classification: Unclassified OS: Linux Reporter: dhar...@datashit.net Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.0) KDE Platform Version: 4.8.1 (4.8.1) Qt Version: 4.8.0 Operating System: Linux 3.0.0-16-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: 1)Select new unread email 2)Select another unread email 3)Sometimes (frequently but not always) Kontact crash! -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb773f730 (LWP 27175))] Thread 4 (Thread 0xb5ca9b70 (LWP 27177)): #0 0x00d70416 in __kernel_vsyscall () #1 0x00bcca5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x0023809c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0x073af883 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0x073af99f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0x00bc8d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0x0022a46e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 3 (Thread 0xb5380b70 (LWP 27178)): #0 0x00d65d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x04885e35 in do_gettime (frac=0xb5380030, sec=0xb5380028) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x0496fb56 in QTimerInfoList::updateCurrentTime (this=0x8435274) at kernel/qeventdispatcher_unix.cpp:343 #4 0x0496feaa in QTimerInfoList::timerWait (this=0x8435274, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #5 0x0496e6c3 in timerSourcePrepareHelper (src=optimized out, timeout=0xb538011c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x0288188c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x02882637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x02882c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x0496f217 in QEventDispatcherGlib::processEvents (this=0x8433a30, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0x0493ad6d in QEventLoop::processEvents (this=0xb53802b0, flags=...) at kernel/qeventloop.cpp:149 #11 0x0493b009 in QEventLoop::exec (this=0xb53802b0, flags=...) at kernel/qeventloop.cpp:204 #12 0x048249dc in QThread::exec (this=0x8433640) at thread/qthread.cpp:501 #13 0x04824acb in QThread::run (this=0x8433640) at thread/qthread.cpp:568 #14 0x04827e70 in QThreadPrivate::start (arg=0x8433640) at thread/qthread_unix.cpp:298 #15 0x00bc8d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #16 0x0022a46e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 2 (Thread 0xb229fb70 (LWP 27246)): #0 0x0288188c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0x02882637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0x02882c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x0496f217 in QEventDispatcherGlib::processEvents (this=0x9034b28, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x0493ad6d in QEventLoop::processEvents (this=0xb229f280, flags=...) at kernel/qeventloop.cpp:149 #5 0x0493b009 in QEventLoop::exec (this=0xb229f280, flags=...) at kernel/qeventloop.cpp:204 #6 0x048249dc in QThread::exec (this=0x8623730) at thread/qthread.cpp:501 #7 0x049182dd in QInotifyFileSystemWatcherEngine::run (this=0x8623730) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x04827e70 in QThreadPrivate::start (arg=0x8623730) at thread/qthread_unix.cpp:298 #9 0x00bc8d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #10 0x0022a46e in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 1 (Thread 0xb773f730 (LWP 27175)): [KCrash Handler] #7 0x05918f0d in QNetworkAccessHttpBackend::replyDownloadMetaData (this=0xa4a6300, hm=) at access/qnetworkaccesshttpbackend.cpp:827 #8 0x059afd0d in QNetworkAccessHttpBackend::qt_static_metacall (_o=0xa4a6300, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xae914068) at .moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91 #9 0x0494e461 in QMetaCallEvent::placeMetaCall (this=0xae914020, object=0xa4a6300) at kernel/qobject.cpp:525 #10 0x049574db in QObject::event (this=0xa4a6300, e=0xae914020) at kernel/qobject.cpp:1195 #11 0x00eab844 in notify_helper (e=0xae914020, receiver=0xa4a6300, this=0x82da538) at kernel/qapplication.cpp:4555 #12
