[kmail2] [Bug 223034] cannot send mail to distribution list
https://bugs.kde.org/show_bug.cgi?id=223034 Alex Ball changed: What|Removed |Added CC||a.b...@ukoln.ac.uk -- 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 323915] New: Wish: new mail notifications should indicate the account when more than one is configured
https://bugs.kde.org/show_bug.cgi?id=323915 Bug ID: 323915 Summary: Wish: new mail notifications should indicate the account when more than one is configured Classification: Unclassified Product: kmail2 Version: 4.11 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: a.b...@ukoln.ac.uk With the detailed new mail notifications, when more than one mail is received the notification says something like "2 new messages received in Inbox". When more than one account is configured, this is ambiguous. Worse, if the received mails come from more than one account, the message can appear contradictory: "2 new messages received in Inbox. One new message received in Inbox." My wish is for the message to disambiguate from which account the mails were received, when more than one account is configured. Reproducible: Always Steps to Reproduce: 1. Set up multiple email accounts 2. Enable detailed new mail notifications 3. Receive new emails from more than one account, within the same mail check Actual Results: Notification pops up with text similar to the following: "2 new messages received in Inbox. One new message received in Inbox." Expected Results: Notification pops up with text similar to the following: "2 new messages received in Inbox (Home). One new message received in Inbox (Work)." Here I've suggested putting the account name in parentheses after the folder name, but you may have a better solution. -- 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 283020] Store Kmail Tags in IMAP flags, like Thunderbird
https://bugs.kde.org/show_bug.cgi?id=283020 Alex Ball changed: What|Removed |Added CC||a.b...@ukoln.ac.uk -- 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 286929] New: Akregator crashes when built-in browser tab is closed
https://bugs.kde.org/show_bug.cgi?id=286929 Summary: Akregator crashes when built-in browser tab is closed Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: a.b...@ukoln.ac.uk Application: kontact (4.7.3) KDE Platform Version: 4.7.3 (4.7.3) Qt Version: 4.7.4 Operating System: Linux 3.0.0-12-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I had followed a link in a blog post, opening the Web page in a new Akregator tab. Having finished reading, I clicked the icon to close the current tab, and the entire application crashed. On next start, the session was correctly restored, but closing the tab by any method (keyboard shortcut, context menu) caused the crash again. I am currently working around this problem by not restoring the previous session after the crash. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb7745730 (LWP 5014))] Thread 6 (Thread 0xb69fdb70 (LWP 5015)): #0 0x00110416 in __kernel_vsyscall () #1 0x04bfca5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x002dbcfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0x02ab6883 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0x02ab699f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0x04bf8d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0x002ce0ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 5 (Thread 0xb60d4b70 (LWP 5016)): #0 0x002dbf18 in pthread_mutex_lock () from /lib/i386-linux-gnu/libc.so.6 #1 0x042578bb in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0x04258637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x04258c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x00d08b37 in QEventDispatcherGlib::processEvents (this=0x92a04e8, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x00cd91dd in QEventLoop::processEvents (this=0xb60d42c0, flags=...) at kernel/qeventloop.cpp:149 #6 0x00cd9421 in QEventLoop::exec (this=0xb60d42c0, flags=...) at kernel/qeventloop.cpp:201 #7 0x00bdc90b in QThread::exec (this=0x9299ba8) at thread/qthread.cpp:498 #8 0x00bdc9fb in QThread::run (this=0x9299ba8) at thread/qthread.cpp:565 #9 0x00bdf7b3 in QThreadPrivate::start (arg=0x9299ba8) at thread/qthread_unix.cpp:331 #10 0x04bf8d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #11 0x002ce0ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 4 (Thread 0xaf461b70 (LWP 5029)): #0 0x08e42d10 in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0x00c367d5 in do_gettime (frac=0xaf461000, sec=0xaf460ff8) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0x00d094b6 in QTimerInfoList::updateCurrentTime (this=0xb53cfdc) at kernel/qeventdispatcher_unix.cpp:339 #4 0x00d0980a in QTimerInfoList::timerWait (this=0xb53cfdc, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0x00d08053 in timerSourcePrepareHelper (src=, timeout=0xaf46110c) at kernel/qeventdispatcher_glib.cpp:136 #6 0x00d080ed in timerSourcePrepare (source=0xb53cfa8, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #7 0x0425788c in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0x04258637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0x04258c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #10 0x00d08b37 in QEventDispatcherGlib::processEvents (this=0x9b6a738, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0x00cd91dd in QEventLoop::processEvents (this=0xaf461290, flags=...) at kernel/qeventloop.cpp:149 #12 0x00cd9421 in QEventLoop::exec (this=0xaf461290, flags=...) at kernel/qeventloop.cpp:201 #13 0x00bdc90b in QThread::exec (this=0x9a095f0) at thread/qthread.cpp:498 #14 0x00cb9e2d in QInotifyFileSystemWatcherEngine::run (this=0x9a095f0) at io/qfilesystemwatcher_inotify.cpp:248 #15 0x00bdf7b3 in QThreadPrivate::start (arg=0x9a095f0) at thread/qthread_unix.cpp:331 #16 0x04bf8d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #17 0x002ce0ce in clone () from /lib/i386-linux-gnu/libc.so.6 Backtrace stopped: Not enough registers or memory available to unwind further Thread 3 (Thread 0xb2694b70 (LWP 5048)): #0 0x00110416 in __kernel_vsyscall () #1 0x04bfca5c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x002dbcfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xad
[Bug 128357] Crash after hovering the mouse over an URL [KMMessage::bodyPart, AttachmentURLHandler::statusBarMessage, KMail::URLHandlerManager::statusBarMessage, KMReaderWin::slotUrlOn]
https://bugs.kde.org/show_bug.cgi?id=128357 --- Comment #56 from Alex Ball 2011-05-27 15:31:07 --- Created an attachment (id=60385) --> (http://bugs.kde.org/attachment.cgi?id=60385) New crash information added by DrKonqi kontact (4.4.10) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.2 - What I was doing when the application crashed: Viewing an email, and about to click on an embedded URL (I guess that counts as hovering). I'm providing this report firstly to indicate that the problem still exists in KDESC 4.6.3 and secondly because the backtrace looked somewhat different to those already provided. -- Backtrace (Reduced): #6 0x7f74395f4d1f in c_str (aDwBodyPart=0x2bd9e40, aPart=0x38504a8, withBody=true) at ../../mimelib/mimelib/string.h:618 #7 partId (aDwBodyPart=0x2bd9e40, aPart=0x38504a8, withBody=true) at ../../mimelib/mimelib/msgcmp.h:259 #8 KMMessage::bodyPart (aDwBodyPart=0x2bd9e40, aPart=0x38504a8, withBody=true) at ../../kmail/kmmessage.cpp:2677 #9 0x7f74398d1981 in msgPart (this=, url=..., w=) at ../../kmail/partNode.h:103 #10 (anonymous namespace)::AttachmentURLHandler::statusBarMessage (this=, url=..., w=) at ../../kmail/urlhandlermanager.cpp:688 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 128357] Crash after hovering the mouse over an URL [KMMessage::bodyPart, AttachmentURLHandler::statusBarMessage, KMail::URLHandlerManager::statusBarMessage, KMReaderWin::slotUrlOn]
https://bugs.kde.org/show_bug.cgi?id=128357 Alex Ball changed: What|Removed |Added CC||a.b...@ukoln.ac.uk -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 267797] Kmail doesn't connect to kwallet any more
https://bugs.kde.org/show_bug.cgi?id=267797 Alex Ball changed: What|Removed |Added CC||a.b...@ukoln.ac.uk --- Comment #9 from Alex Ball 2011-05-12 10:50:17 --- I can confirm this for KMail 1.13.6 (Kontact 4.4.10) on KDE 4.6.3 (Kubuntu 11.04 64-bit). My first IMAP account (set up back on KDE 4.4.2) behaves as expected, but with my second IMAP account (set up a few days ago) I got the message that KWallet was unavailable when setting up the account, and having declined the option to have KMail store it in its own configuration files, I got asked for the password every time I started Kontact, and the error about KWallet not being available every time I closed it. However, I have managed to workaround the problem (touch wood) using the first account as a template. With Kontact/KMail closed: 1. Open ~/.kde/share/config/kmailrc. 2. Locate the configuration block for the offending account and change 'store-passwd=false' to 'store-passwd=true' (and save). 3. Note the numeric identity for the account at the start of that configuration block (say, Account 1234567890) 4. Open up KDE Wallet Manager, and the default wallet 5. Find the entry 'kmail', select 'Passwords' and right-click or press Ins to add new entry. 6. Name the entry after the numeric account identity (e.g. account-123457890) and add the password (and save). I presume this means that KMail now has a problem with writing passwords to KWallet, and won't change the 'store-passwd' setting until it has, but that it has no trouble reading from KWallet. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 270183] New: Kontact crashed when Network Manager settings altered
https://bugs.kde.org/show_bug.cgi?id=270183 Summary: Kontact crashed when Network Manager settings altered Product: kontact Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: a.b...@ukoln.ac.uk Application: kontact (4.4.9) KDE Platform Version: 4.6.1 (4.6.1) Qt Version: 4.7.0 Operating System: Linux 2.6.35-28-generic i686 Distribution: Ubuntu 10.10 -- Information about the crash: - What I was doing when the application crashed: For reasons I won't go into, I deleted the active wireless connection using the Network Management plasmoid, with a view to recreating it. Kontact was running at the time, and immediately after the connection was deleted, it crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb7704730 (LWP 8377))] Thread 3 (Thread 0xb14b9b70 (LWP 8396)): #0 0x00a3bfa1 in pthread_mutex_unlock () from /lib/libc.so.6 #1 0x03e9d870 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #2 0x020df59f in QEventDispatcherGlib::processEvents (this=0x9288e28, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #3 0x020af609 in QEventLoop::processEvents (this=0xb14b9270, flags=) at kernel/qeventloop.cpp:149 #4 0x020afa8a in QEventLoop::exec (this=0xb14b9270, flags=...) at kernel/qeventloop.cpp:201 #5 0x01fabb7e in QThread::exec (this=0x92b7898) at thread/qthread.cpp:490 #6 0x0208e35b in QInotifyFileSystemWatcherEngine::run (this=0x92b7898) at io/qfilesystemwatcher_inotify.cpp:248 #7 0x01faedf9 in QThreadPrivate::start (arg=0x92b7898) at thread/qthread_unix.cpp:266 #8 0x01a7fcc9 in start_thread () from /lib/libpthread.so.0 #9 0x00a2e69e in clone () from /lib/libc.so.6 Thread 2 (Thread 0xb2e07b70 (LWP 8534)): #0 0x0095d416 in __kernel_vsyscall () #1 0x01a844dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0x00a3bd9d in pthread_cond_wait () from /lib/libc.so.6 #3 0xaeac73a5 in ?? () from /usr/lib/libQtWebKit.so.4 #4 0xaeac7481 in ?? () from /usr/lib/libQtWebKit.so.4 #5 0x01a7fcc9 in start_thread () from /lib/libpthread.so.0 #6 0x00a2e69e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb7704730 (LWP 8377)): [KCrash Handler] #7 QMutex::lock (this=0xc) at thread/qmutex.cpp:151 #8 0x070a91a6 in QNetworkConfigurationManagerPrivate::configurationRemoved (this=0x99d15a8, ptr=) at bearer/qnetworkconfigmanager_p.cpp:313 #9 0x0710bd08 in QNetworkConfigurationManagerPrivate::qt_metacall (this=0x99d15a8, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbf968ad8) at .moc/release-shared/moc_qnetworkconfigmanager_p.cpp:105 #10 0x020b68ca in QMetaObject::metacall (object=0x99d15a8, cl=3214314200, idx=12, argv=0xbf968ad8) at kernel/qmetaobject.cpp:237 #11 0x020c96ad in QMetaObject::activate (sender=0x967dde0, m=0x714a504, local_signal_index=1, argv=0xc) at kernel/qobject.cpp:3280 #12 0x070ac253 in QBearerEngine::configurationRemoved (this=0x967dde0, _t1=...) at .moc/release-shared/moc_qbearerengine_p.cpp:101 #13 0x049807aa in QNetworkManagerEngine::parseConnection (this=0x967dde0, service=..., settingsPath=..., map=...) at qnetworkmanagerengine.cpp:740 #14 0x049814b4 in QNetworkManagerEngine::newConnection (this=0x967dde0, path=..., settings=0x0) at qnetworkmanagerengine.cpp:419 #15 0x04989976 in QNetworkManagerEngine::qt_metacall (this=0x967dde0, _c=QMetaObject::InvokeMetaMethod, _id=15, _a=0xbf968e28) at .moc/release-shared/moc_qnetworkmanagerengine.cpp:109 #16 0x020b68ca in QMetaObject::metacall (object=0x967dde0, cl=3214314200, idx=15, argv=0xbf968e28) at kernel/qmetaobject.cpp:237 #17 0x020c96ad in QMetaObject::activate (sender=0x92a7248, m=0x49939d8, local_signal_index=0, argv=0xc) at kernel/qobject.cpp:3280 #18 0x04988cb3 in QNetworkManagerSettings::newConnection (this=0x92a7248, _t1=...) at .moc/release-shared/moc_qnetworkmanagerservice.cpp:490 #19 0x049892fb in QNetworkManagerSettings::qt_metacall (this=0x92a7248, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf968f8c) at .moc/release-shared/moc_qnetworkmanagerservice.cpp:478 #20 0x008e59dc in QDBusConnectionPrivate::deliverCall (this=0x967fe00, object=0x92a7248, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:919 #21 0x008f11f7 in QDBusCallDeliveryEvent::placeMetaCall (this=0x9e98f78, object=0x92a7248) at qdbusintegrator_p.h:103 #22 0x020c36a2 in QObject::event (this=0x92a7248, e=0x0) at kernel/qobject.cpp:1219 #23 0x010dcfdc in QApplicationPrivate::notify_helper (this=0x8bc4530, receiver=0x92a7248, e=0x9e98f78) at kernel/qapplication.cpp:4396 #24 0x010e304e in QApplication::notify (this=0xbf969854, receiver=0x92a7248, e=0x9e98f78) at kernel/qapplication.cpp:3798 #25 0x005347da in KApplication::notify (this=0xbf969854, receiver=0x92a7248, event=0x9e98f78) at ../../kdeui/kernel/kapplication.cpp:311 #26 0x020b0b3b in QCor
