[Bug 158486] Should ask for SMTP password if authentication failed
https://bugs.kde.org/show_bug.cgi?id=158486 Ozan Çağlayan o...@pardus.org.tr changed: What|Removed |Added CC||o...@pardus.org.tr --- Comment #3 from Ozan Çağlayan ozan pardus org tr 2010-06-22 07:47:07 --- Can someone please please please please look in this annoying issue which drives me crazy every time i mistype my password? I don't really get how the developers for such a talented and advanced mail client can even miss that functionality. -- 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 242452] New: Kontact crashed when mail was received
https://bugs.kde.org/show_bug.cgi?id=242452 Summary: Kontact crashed when mail was received Product: kontact Version: 4.4.3 Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: jae...@yahoo.com Application: kontact (4.4.3) KDE Platform Version: 4.4.4 (KDE 4.4.4) Qt Version: 4.6.2 Operating System: Linux 2.6.32.14-127.fc12.i686.PAE i686 Distribution (Platform): Fedora RPMs -- Information about the crash: I was working on website with Kontact in the background. I heard the ding of mail received and then Kontact crashed The crash does not seem to be reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x085edebb in KMail::SearchJob::slotSearchDataSingleMessage (this=0xad4aa18, job=0xadd6a00, data=...) at /usr/src/debug/kdepim-4.4.4/kmail/searchjob.cpp:424 #7 0x085f183a in KMail::SearchJob::qt_metacall (this=0xad4aa18, _c=InvokeMetaMethod, _id=6, _a=0xbfd46990) at /usr/src/debug/kdepim-4.4.4/i686-redhat-linux-gnu/kmail/searchjob.moc:95 #8 0x054f55db in QMetaObject::metacall (object=0xad4aa18, cl=InvokeMetaMethod, idx=18, argv=0xbfd46990) at kernel/qmetaobject.cpp:237 #9 0x055044af in QMetaObject::activate (sender=0xadd6a00, m=0x586df08, local_signal_index=7, argv=0xbfd46990) at kernel/qobject.cpp:3293 #10 0x056e30d0 in KJob::infoMessage (this=0xadd6a00, _t1=0xadd6a00, _t2=..., _t3=...) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kdecore/kjob.moc:208 #11 0x06ee0eb2 in KIO::SimpleJobPrivate::_k_slotSlaveInfoMessage (this=0xac6e720, msg=...) at /usr/src/debug/kdelibs-4.4.4/kio/kio/job.cpp:539 #12 0x06ee39a0 in KIO::SimpleJob::qt_metacall (this=0xadd6a00, _c=InvokeMetaMethod, _id=value optimized out, _a=0xbfd46af8) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kio/jobclasses.moc:178 #13 0x054f55db in QMetaObject::metacall (object=0xadd6a00, cl=InvokeMetaMethod, idx=39, argv=0xbfd46af8) at kernel/qmetaobject.cpp:237 #14 0x055044af in QMetaObject::activate (sender=0xa484650, m=0x70aa9e4, local_signal_index=21, argv=0xbfd46af8) at kernel/qobject.cpp:3293 #15 0x06fa4e74 in KIO::SlaveInterface::infoMessage (this=0xa484650, _t1=...) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kio/slaveinterface.moc:287 #16 0x06fa7f77 in KIO::SlaveInterface::dispatch (this=0xa484650, _cmd=26, rawdata=...) at /usr/src/debug/kdelibs-4.4.4/kio/kio/slaveinterface.cpp:294 #17 0x06fa5864 in KIO::SlaveInterface::dispatch (this=0xa484650) at /usr/src/debug/kdelibs-4.4.4/kio/kio/slaveinterface.cpp:91 #18 0x06f99c28 in KIO::Slave::gotInput (this=0xa484650) at /usr/src/debug/kdelibs-4.4.4/kio/kio/slave.cpp:324 #19 0x06f99e53 in KIO::Slave::qt_metacall (this=0xa484650, _c=InvokeMetaMethod, _id=value optimized out, _a=0xbfd46ddc) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kio/slave.moc:82 #20 0x054f55db in QMetaObject::metacall (object=0xa484650, cl=InvokeMetaMethod, idx=30, argv=0xbfd46ddc) at kernel/qmetaobject.cpp:237 #21 0x055044af in QMetaObject::activate (sender=0xa24ac08, m=0x70a72c0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293 #22 0x06eb0808 in KIO::Connection::readyRead (this=0xa24ac08) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kio/connection.moc:92 #23 0x06eb28ae in KIO::ConnectionPrivate::dequeue (this=0xa4e3b88) at /usr/src/debug/kdelibs-4.4.4/kio/kio/connection.cpp:82 #24 0x06eb29d6 in KIO::Connection::qt_metacall (this=0xa24ac08, _c=InvokeMetaMethod, _id=value optimized out, _a=0xa0e6c00) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kio/connection.moc:79 #25 0x054f55db in QMetaObject::metacall (object=0xa24ac08, cl=InvokeMetaMethod, idx=5, argv=0xa0e6c00) at kernel/qmetaobject.cpp:237 #26 0x054ffbd7 in QMetaCallEvent::placeMetaCall (this=0xab0a808, object=0xa24ac08) at kernel/qobject.cpp:561 #27 0x05500c4e in QObject::event (this=0xa24ac08, e=0xab0a808) at kernel/qobject.cpp:1248 #28 0x0628819c in QApplicationPrivate::notify_helper (this=0x9d65600, receiver=0xa24ac08, e=0xab0a808) at kernel/qapplication.cpp:4304 #29 0x0628e9d6 in QApplication::notify (this=0xbfd47734, receiver=0xa24ac08, e=0xab0a808) at kernel/qapplication.cpp:3708 #30 0x05a3a87b in KApplication::notify (this=0xbfd47734, receiver=0xa24ac08, event=0xab0a808) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302 #31 0x054f0c03 in QCoreApplication::notifyInternal (this=0xbfd47734, receiver=0xa24ac08, event=0xab0a808) at kernel/qcoreapplication.cpp:704 #32 0x054f1ac3 in sendEvent (receiver=0x0, event_type=0, data=0x9d43c68) at kernel/qcoreapplication.h:215 #33 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9d43c68) at kernel/qcoreapplication.cpp:1345 #34 0x054f1c1e in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238 #35 0x05519350
[Bug 242454] New: Kontact crashed when mail was received
https://bugs.kde.org/show_bug.cgi?id=242454 Summary: Kontact crashed when mail was received Product: kontact Version: 4.4.3 Platform: Fedora RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: jae...@yahoo.com Application: kontact (4.4.3) KDE Platform Version: 4.4.4 (KDE 4.4.4) Qt Version: 4.6.2 Operating System: Linux 2.6.32.14-127.fc12.i686.PAE i686 Distribution (Platform): Fedora RPMs -- Information about the crash: I was working on website with Kontact in the background. I heard the ding of mail received and then Kontact crashed The crash does not seem to be reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0x085edebb in KMail::SearchJob::slotSearchDataSingleMessage (this=0xad4aa18, job=0xadd6a00, data=...) at /usr/src/debug/kdepim-4.4.4/kmail/searchjob.cpp:424 #7 0x085f183a in KMail::SearchJob::qt_metacall (this=0xad4aa18, _c=InvokeMetaMethod, _id=6, _a=0xbfd46990) at /usr/src/debug/kdepim-4.4.4/i686-redhat-linux-gnu/kmail/searchjob.moc:95 #8 0x054f55db in QMetaObject::metacall (object=0xad4aa18, cl=InvokeMetaMethod, idx=18, argv=0xbfd46990) at kernel/qmetaobject.cpp:237 #9 0x055044af in QMetaObject::activate (sender=0xadd6a00, m=0x586df08, local_signal_index=7, argv=0xbfd46990) at kernel/qobject.cpp:3293 #10 0x056e30d0 in KJob::infoMessage (this=0xadd6a00, _t1=0xadd6a00, _t2=..., _t3=...) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kdecore/kjob.moc:208 #11 0x06ee0eb2 in KIO::SimpleJobPrivate::_k_slotSlaveInfoMessage (this=0xac6e720, msg=...) at /usr/src/debug/kdelibs-4.4.4/kio/kio/job.cpp:539 #12 0x06ee39a0 in KIO::SimpleJob::qt_metacall (this=0xadd6a00, _c=InvokeMetaMethod, _id=value optimized out, _a=0xbfd46af8) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kio/jobclasses.moc:178 #13 0x054f55db in QMetaObject::metacall (object=0xadd6a00, cl=InvokeMetaMethod, idx=39, argv=0xbfd46af8) at kernel/qmetaobject.cpp:237 #14 0x055044af in QMetaObject::activate (sender=0xa484650, m=0x70aa9e4, local_signal_index=21, argv=0xbfd46af8) at kernel/qobject.cpp:3293 #15 0x06fa4e74 in KIO::SlaveInterface::infoMessage (this=0xa484650, _t1=...) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kio/slaveinterface.moc:287 #16 0x06fa7f77 in KIO::SlaveInterface::dispatch (this=0xa484650, _cmd=26, rawdata=...) at /usr/src/debug/kdelibs-4.4.4/kio/kio/slaveinterface.cpp:294 #17 0x06fa5864 in KIO::SlaveInterface::dispatch (this=0xa484650) at /usr/src/debug/kdelibs-4.4.4/kio/kio/slaveinterface.cpp:91 #18 0x06f99c28 in KIO::Slave::gotInput (this=0xa484650) at /usr/src/debug/kdelibs-4.4.4/kio/kio/slave.cpp:324 #19 0x06f99e53 in KIO::Slave::qt_metacall (this=0xa484650, _c=InvokeMetaMethod, _id=value optimized out, _a=0xbfd46ddc) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kio/slave.moc:82 #20 0x054f55db in QMetaObject::metacall (object=0xa484650, cl=InvokeMetaMethod, idx=30, argv=0xbfd46ddc) at kernel/qmetaobject.cpp:237 #21 0x055044af in QMetaObject::activate (sender=0xa24ac08, m=0x70a72c0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293 #22 0x06eb0808 in KIO::Connection::readyRead (this=0xa24ac08) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kio/connection.moc:92 #23 0x06eb28ae in KIO::ConnectionPrivate::dequeue (this=0xa4e3b88) at /usr/src/debug/kdelibs-4.4.4/kio/kio/connection.cpp:82 #24 0x06eb29d6 in KIO::Connection::qt_metacall (this=0xa24ac08, _c=InvokeMetaMethod, _id=value optimized out, _a=0xa0e6c00) at /usr/src/debug/kdelibs-4.4.4/i686-redhat-linux-gnu/kio/connection.moc:79 #25 0x054f55db in QMetaObject::metacall (object=0xa24ac08, cl=InvokeMetaMethod, idx=5, argv=0xa0e6c00) at kernel/qmetaobject.cpp:237 #26 0x054ffbd7 in QMetaCallEvent::placeMetaCall (this=0xab0a808, object=0xa24ac08) at kernel/qobject.cpp:561 #27 0x05500c4e in QObject::event (this=0xa24ac08, e=0xab0a808) at kernel/qobject.cpp:1248 #28 0x0628819c in QApplicationPrivate::notify_helper (this=0x9d65600, receiver=0xa24ac08, e=0xab0a808) at kernel/qapplication.cpp:4304 #29 0x0628e9d6 in QApplication::notify (this=0xbfd47734, receiver=0xa24ac08, e=0xab0a808) at kernel/qapplication.cpp:3708 #30 0x05a3a87b in KApplication::notify (this=0xbfd47734, receiver=0xa24ac08, event=0xab0a808) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302 #31 0x054f0c03 in QCoreApplication::notifyInternal (this=0xbfd47734, receiver=0xa24ac08, event=0xab0a808) at kernel/qcoreapplication.cpp:704 #32 0x054f1ac3 in sendEvent (receiver=0x0, event_type=0, data=0x9d43c68) at kernel/qcoreapplication.h:215 #33 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9d43c68) at kernel/qcoreapplication.cpp:1345 #34 0x054f1c1e in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238 #35 0x05519350
[Bug 229979] password not asked again if wrong.
https://bugs.kde.org/show_bug.cgi?id=229979 Silver Salonen silver.salo...@gmail.com changed: What|Removed |Added CC||silver.salo...@gmail.com --- Comment #2 from Silver Salonen silver salonen gmail com 2010-06-22 09:55:25 --- I use KDE 4.4.4 on openSUSE 11.2 (x86_64) and I just changed my password in IMAP/SMTP server. After that KMail couldn't send e-mails, because SMTP-authentication failed and it didn't ask for a password again. After restarting KMail, IMAP-auth failed too and I got just a notification that it failed - no asking for a new password. One has to go to configuring IMAP-account and re-set the password there (it's remembered in KWallet in my case). -- 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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]
https://bugs.kde.org/show_bug.cgi?id=169048 Jose getace...@yahoo.es changed: What|Removed |Added CC||getace...@yahoo.es -- 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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]
https://bugs.kde.org/show_bug.cgi?id=169048 --- Comment #27 from Jose getaceres yahoo es 2010-06-22 10:06:50 --- Created an attachment (id=48213) -- (http://bugs.kde.org/attachment.cgi?id=48213) New crash information added by DrKonqi I just defined a filter on an imap acount. Kontact crashed when an e-mail arrived. It doesn't crash always. -- 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 169048] Crashes when applying all filters on IMAP folder [KMail::ActionScheduler::actionMessage, KMail::ActionScheduler::filterMessage]
https://bugs.kde.org/show_bug.cgi?id=169048 --- Comment #28 from Jose getaceres yahoo es 2010-06-22 10:13:13 --- Created an attachment (id=48214) -- (http://bugs.kde.org/attachment.cgi?id=48214) New crash information added by DrKonqi Well, it always happens. The case is that I had a KDE 4.4.4 installation but it was upgraded from KDE 4.0.X to 4.4.4. I had some filters defined in kontact and it never crashed because of them. Then, I renamed the .kde directory because the configuration was messed for some applications and I started with a new .kde folder. I have configured everything but as it was expected, my old filters were forgotten. Now I've defined them again and it has started to crash, which it didn't do before. -- 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 242458] New: Kontact crash while filtering
https://bugs.kde.org/show_bug.cgi?id=242458 Summary: Kontact crash while filtering Product: kontact Version: 4.4.3 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: i...@alvin.be Application: kontact (4.4.3) KDE Platform Version: 4.4.4 (KDE 4.4.4) Qt Version: 4.6.3 Operating System: Linux 2.6.32-22-generic x86_64 Distribution: Ubuntu 10.04 LTS -- Information about the crash: Kontact often crashes while aplying filters to an IMAP folder. In this case, the filter moved a lot of files to the trash. The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7fdb8d8a0780 (LWP 9437))] Thread 2 (Thread 0x7fdb69d11710 (LWP 9587)): #0 0x7fdb8a96ff53 in *__GI___poll (fds=value optimized out, nfds=value optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fdb8349e4a9 in ?? () from /lib/libglib-2.0.so.0 #2 0x7fdb8349e8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x7fdb8bd5a406 in QEventDispatcherGlib::processEvents (this=0x2cc3550, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:414 #4 0x7fdb8bd2f6c2 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #5 0x7fdb8bd2fa9c in QEventLoop::exec (this=0x7fdb69d10d90, flags=) at kernel/qeventloop.cpp:201 #6 0x7fdb8bc3e8db in QThread::exec (this=value optimized out) at thread/qthread.cpp:487 #7 0x7fdb8bd0fdd8 in QInotifyFileSystemWatcherEngine::run (this=0x2e2aa80) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fdb8bc40f95 in QThreadPrivate::start (arg=0x2e2aa80) at thread/qthread_unix.cpp:248 #9 0x7fdb85a159ca in start_thread (arg=value optimized out) at pthread_create.c:300 #10 0x7fdb8a97c6cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7fdb8d8a0780 (LWP 9437)): [KCrash Handler] #5 0x05591400 in ?? () #6 0x7fdb72ef800d in KMail::ImapJob::slotProcessedSize (this=0x78cb380, job=0x5a2ed30, processed=1884) at ../../kmail/imapjob.cpp:688 #7 0x7fdb72ef9852 in KMail::ImapJob::qt_metacall (this=0x78cb380, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff87d43660) at ./imapjob.moc:96 #8 0x7fdb8bd44036 in QMetaObject::activate (sender=0x5a2ed30, m=value optimized out, local_signal_index=value optimized out, argv=0x7fff87d43658) at kernel/qobject.cpp:3295 #9 0x7fdb8c14995b in KJob::processedSize (this=0x5ad7570, _t1=0x5a2ed30, _t2=1884) at ./kjob.moc:243 #10 0x7fdb8c14adf2 in KJob::setProcessedAmount (this=value optimized out, unit=KJob::Bytes, amount=value optimized out) at ../../kdecore/jobs/kjob.cpp:267 #11 0x7fdb894c079a in KIO::TransferJob::sendAsyncData (this=0x5a2ed30, dataForSlave=...) at ../../kio/kio/job.cpp:1118 #12 0x7fdb894c27c9 in KIO::TransferJob::slotDataReq (this=0x5a2ed30) at ../../kio/kio/job.cpp:1174 #13 0x7fdb894c6531 in KIO::TransferJob::qt_metacall (this=0x5a2ed30, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff87d43930) at ./jobclasses.moc:369 #14 0x7fdb8bd44036 in QMetaObject::activate (sender=0x209f8f0, m=value optimized out, local_signal_index=value optimized out, argv=0x7fff87d43658) at kernel/qobject.cpp:3295 #15 0x7fdb89587df5 in KIO::SlaveInterface::dispatch (this=0x209f8f0, _cmd=101, rawdata=...) at ../../kio/kio/slaveinterface.cpp:166 #16 0x7fdb895850d3 in KIO::SlaveInterface::dispatch (this=0x209f8f0) at ../../kio/kio/slaveinterface.cpp:91 #17 0x7fdb89579536 in KIO::Slave::gotInput (this=0x209f8f0) at ../../kio/kio/slave.cpp:324 #18 0x7fdb8957971c in KIO::Slave::qt_metacall (this=0x209f8f0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff87d43d50) at ./slave.moc:82 #19 0x7fdb8bd44036 in QMetaObject::activate (sender=0x2c0d6c0, m=value optimized out, local_signal_index=value optimized out, argv=0x7fff87d43658) at kernel/qobject.cpp:3295 #20 0x7fdb894969d7 in KIO::ConnectionPrivate::dequeue (this=0x2b03de0) at ../../kio/kio/connection.cpp:82 #21 0x7fdb89496afd in KIO::Connection::qt_metacall (this=0x2c0d6c0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x50a39a0) at ./connection.moc:79 #22 0x7fdb8bd40b79 in QObject::event (this=0x2c0d6c0, e=0x7293030) at kernel/qobject.cpp:1248 #23 0x7fdb8b0eac0c in QApplicationPrivate::notify_helper (this=0x1d67020, receiver=0x2c0d6c0, e=0x7293030) at kernel/qapplication.cpp:4302 #24 0x7fdb8b0f10eb in QApplication::notify (this=0x7fff87d44860, receiver=0x2c0d6c0, e=0x7293030) at kernel/qapplication.cpp:4185 #25 0x7fdb8c71a606 in KApplication::notify (this=0x7fff87d44860, receiver=0x2c0d6c0, event=0x7293030) at
[Bug 242460] New: Wrong preview for long mail
https://bugs.kde.org/show_bug.cgi?id=242460 Summary: Wrong preview for long mail Product: kmail Version: 1.13.3 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: messageviewer AssignedTo: kdepim-bugs@kde.org ReportedBy: alpha_one_...@first-world.info Created an attachment (id=48216) -- (http://bugs.kde.org/attachment.cgi?id=48216) screenshot Version: 1.13.3 (using KDE 4.4.4) OS:Linux Hello, For long long mail or mail with long ligne in nowrap (in html) I have end cuted and char show above other char (see the screenshot attached) Reproducible: Always Steps to Reproduce: Very long mail + very long line with nowrap (in html) Actual Results: See the screenshot -- 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 242340] kaddressbook-mobile action flap should contains a create contact button
https://bugs.kde.org/show_bug.cgi?id=242340 Volker Krause vkra...@kde.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #1 from Volker Krause vkrause kde org 2010-06-22 11:15:45 --- SVN commit 1141187 by vkrause: Put similar actions into the action slideout panel as we have in kmail-mobile. BUG: 242340 M +34 -20kaddressbook-mobile.qml WebSVN link: http://websvn.kde.org/?view=revrevision=1141187 -- 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 239871] Linuxtag 2010 blocker meta bug
https://bugs.kde.org/show_bug.cgi?id=239871 Bug 239871 depends on bug 240615, which changed state. Bug 240615 Summary: It's not possible to set up an account via kaddressbook-mobile http://bugs.kde.org/show_bug.cgi?id=240615 What|Old Value |New Value Status|NEW |RESOLVED Resolution||FIXED -- 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 240615] It's not possible to set up an account via kaddressbook-mobile
https://bugs.kde.org/show_bug.cgi?id=240615 Volker Krause vkra...@kde.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #1 from Volker Krause vkrause kde org 2010-06-22 11:25:23 --- SVN commit 1141199 by vkrause: join type arguments for accountwizard correctly BUG: 240615 M +1 -3 kdeclarativemainview.cpp WebSVN link: http://websvn.kde.org/?view=revrevision=1141199 -- 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 242344] Personal Contact folder shows the wron icon
https://bugs.kde.org/show_bug.cgi?id=242344 Volker Krause vkra...@kde.org changed: What|Removed |Added Priority|NOR |LO CC||kdepim-bugs@kde.org, ||vkra...@kde.org Component|general |Contacts resource Product|KAddressbook Mobile |Akonadi --- Comment #1 from Volker Krause vkrause kde org 2010-06-22 12:01:09 --- ETM shows the server icon everywhere, only the resource icon the the agent instance list is different. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 242466] New: RFE: Message viewer should have View - View Source in the menu
https://bugs.kde.org/show_bug.cgi?id=242466 Summary: RFE: Message viewer should have View - View Source in the menu Product: kmail Version: 1.13.3 Platform: Fedora RPMs OS/Version: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: messageviewer AssignedTo: kdepim-bugs@kde.org ReportedBy: cwick...@fedoraproject.org Version: 1.13.3 (using KDE 4.4.4) OS:All The KMail main window has a menu entry View - View Source, but the same entry is lacking in the message viewer. This is inconsistent, every menu entry that applies to a single mail should also be in the message viewer's menu. Reproducible: Always -- 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 242458] Kontact crash while filtering
https://bugs.kde.org/show_bug.cgi?id=242458 Nicolas Lécureuil nlecure...@mandriva.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||nlecure...@mandriva.com Resolution||DUPLICATE --- Comment #1 from Nicolas Lécureuil nlecureuil mandriva com 2010-06-22 13:27:34 --- *** This bug has been marked as a duplicate of bug 195859 *** -- 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 242482] New: Kontact crashed for no apparent reason
https://bugs.kde.org/show_bug.cgi?id=242482 Summary: Kontact crashed for no apparent reason Product: kontact Version: 4.4.3 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: tang...@gmail.com Application: kontact (4.4.3) KDE Platform Version: 4.4.4 (KDE 4.4.4) Qt Version: 4.6.3 Operating System: Linux 2.6.34-020634-generic i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: I noticed the fan was spinning up so I guess it was checking mail or subscriptions. To me it looks like a Qt bug but I have no idea how to decipher backtraces :-/ -- Backtrace: Application: Kontact (kontact), signal: Aborted [Current thread is 1 (Thread 0xb3728990 (LWP 3003))] Thread 4 (Thread 0xad7bcb70 (LWP 3018)): #0 0xb786c430 in __kernel_vsyscall () #1 0xb6057971 in select () at ../sysdeps/unix/syscall-template.S:82 #2 0xb6e05112 in qt_safe_select (nfds=20, fdread=0xaea00810, fdwrite=0xaea00a24, fdexcept=0xaea00c38, orig_timeout=0x0) at kernel/qcore_unix.cpp:143 #3 0xb6e09b59 in QEventDispatcherUNIX::select (this=0xaea004a8, nfds=20, readfds=0xaea00810, writefds=0xaea00a24, exceptfds=0xaea00c38, timeout=0x0) at kernel/qeventdispatcher_unix.cpp:633 #4 0xb6e0a867 in QEventDispatcherUNIXPrivate::doSelect (this=0xaea00718, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:218 #5 0xb6e0b765 in QEventDispatcherUNIX::processEvents (this=0xaea004a8, flags=...) at kernel/qeventdispatcher_unix.cpp:920 #6 0xb6dda759 in QEventLoop::processEvents (this=0xad7bc270, flags=) at kernel/qeventloop.cpp:149 #7 0xb6ddabaa in QEventLoop::exec (this=0xad7bc270, flags=...) at kernel/qeventloop.cpp:201 #8 0xb6cdbfc9 in QThread::exec (this=0x8b4d090) at thread/qthread.cpp:487 #9 0xb6dba1db in QInotifyFileSystemWatcherEngine::run (this=0x8b4d090) at io/qfilesystemwatcher_inotify.cpp:248 #10 0xb6cde97e in QThreadPrivate::start (arg=0x8b4d090) at thread/qthread_unix.cpp:248 #11 0xb454596e in start_thread (arg=0xad7bcb70) at pthread_create.c:300 #12 0xb605ea4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 3 (Thread 0xaaa43b70 (LWP 3063)): #0 0xb786c430 in __kernel_vsyscall () #1 0xb606bd33 in __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:95 #2 0xb6002697 in _L_lock_9637 () from /lib/tls/i686/cmov/libc.so.6 #3 0xb6000ec6 in *__GI___libc_free (mem=0xca9b5a0) at malloc.c:3736 #4 0xb61bd741 in operator delete(void*) () from /usr/lib/libstdc++.so.6 #5 0xb6e0a4e5 in ~QEventDispatcherUNIXPrivate (this=0xca9b5a0, __in_chrg=value optimized out) at kernel/qeventdispatcher_unix.cpp:174 #6 0xb6df2b2c in QScopedPointerDeleterQObjectData::cleanup (this=0xbcd7ba8, __in_chrg=value optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62 #7 ~QScopedPointer (this=0xbcd7ba8, __in_chrg=value optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100 #8 ~QObject (this=0xbcd7ba8, __in_chrg=value optimized out) at kernel/qobject.cpp:992 #9 0xb6dcdc88 in ~QAbstractEventDispatcher (this=0xbcd7ba8, __in_chrg=value optimized out) at kernel/qabstracteventdispatcher.cpp:231 #10 0xb6e09b9a in ~QEventDispatcherUNIX (this=0xbcd7ba8, __in_chrg=value optimized out) at kernel/qeventdispatcher_unix.cpp:628 #11 0xb6cde4ea in QThreadPrivate::finish (arg=0xb6ef2890) at thread/qthread_unix.cpp:284 #12 0xb6cde986 in ~__pthread_cleanup_class (arg=0xb6ef2890) at /usr/include/pthread.h:535 #13 QThreadPrivate::start (arg=0xb6ef2890) at thread/qthread_unix.cpp:253 #14 0xb454596e in start_thread (arg=0xaaa43b70) at pthread_create.c:300 #15 0xb605ea4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xacfbbb70 (LWP 3923)): #0 0xb786c430 in __kernel_vsyscall () #1 0xb606bd33 in __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:95 #2 0xb6002697 in _L_lock_9637 () from /lib/tls/i686/cmov/libc.so.6 #3 0xb6000ec6 in *__GI___libc_free (mem=0xd21fdb8) at malloc.c:3736 #4 0xb61bd741 in operator delete(void*) () from /usr/lib/libstdc++.so.6 #5 0xb6e0a4e5 in ~QEventDispatcherUNIXPrivate (this=0xd21fdb8, __in_chrg=value optimized out) at kernel/qeventdispatcher_unix.cpp:174 #6 0xb6df2b2c in QScopedPointerDeleterQObjectData::cleanup (this=0xbf02c08, __in_chrg=value optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62 #7 ~QScopedPointer (this=0xbf02c08, __in_chrg=value optimized out) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100 #8 ~QObject (this=0xbf02c08, __in_chrg=value optimized out) at kernel/qobject.cpp:992 #9 0xb6dcdc88 in ~QAbstractEventDispatcher (this=0xbf02c08, __in_chrg=value optimized out) at kernel/qabstracteventdispatcher.cpp:231 #10 0xb6e09b9a in ~QEventDispatcherUNIX (this=0xbf02c08,
[Bug 241842] When exporting address book language of field names are mixed
https://bugs.kde.org/show_bug.cgi?id=241842 --- Comment #2 from Martin L ü c h e m Heinrich20 gmx de 2010-06-22 15:15:35 --- Created an attachment (id=48224) -- (http://bugs.kde.org/attachment.cgi?id=48224) difference between header from csv export -- 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 230466] Emails being composed are no longer autosaved, and lost on Kmail/Kontact shutdown.
https://bugs.kde.org/show_bug.cgi?id=230466 Terenyi Balazs tere...@freemail.hu changed: What|Removed |Added CC||tere...@freemail.hu --- Comment #5 from Terenyi Balazs terenyi freemail hu 2010-06-22 15:54:26 --- Same here with kmail 1.13.5, the mails are in the autosave/cur folder but doesn't get opened when kmail (kontact) is restarted. -- 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 242494] New: KMail crashed when deleting multiple mails from an IMAP account
https://bugs.kde.org/show_bug.cgi?id=242494 Summary: KMail crashed when deleting multiple mails from an IMAP account Product: kmail Version: 1.13.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: g.r.v.kr...@gmail.com Application: kmail (1.13.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-22-generic x86_64 Distribution: Ubuntu 10.04 LTS -- Information about the crash: This crash occured when I tried to delete mails one by one. I did this fairly fast so that KMail couldn't keep up with me (not intentionally, it's just the way it went) because when I'd delete a mail, KMail synchronizes the change to the server-side (right?), at which point I already deleted another mail before it finished synchronizing the previous change. This went on for several mails (not that much, I was simply cleaning-up old and pointless mails) and then, suddenly, KMail chrashed. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7fa8a74a2820 (LWP 3070))] Thread 2 (Thread 0x7fa8860c9710 (LWP 3072)): #0 0x7fa8a3faaf53 in *__GI___poll (fds=value optimized out, nfds=value optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fa89b9584a9 in ?? () from /lib/libglib-2.0.so.0 #2 0x7fa89b9588fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x7fa8a4915566 in QEventDispatcherGlib::processEvents (this=0x34981c0, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:414 #4 0x7fa8a48ea992 in QEventLoop::processEvents (this=value optimized out, flags=) at kernel/qeventloop.cpp:149 #5 0x7fa8a48ead6c in QEventLoop::exec (this=0x7fa8860c8cf0, flags=) at kernel/qeventloop.cpp:201 #6 0x7fa8a47f4d59 in QThread::exec (this=value optimized out) at thread/qthread.cpp:487 #7 0x7fa8a48cb178 in QInotifyFileSystemWatcherEngine::run (this=0x349e400) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fa8a47f7775 in QThreadPrivate::start (arg=0x349e400) at thread/qthread_unix.cpp:248 #9 0x7fa8a24019ca in start_thread (arg=value optimized out) at pthread_create.c:300 #10 0x7fa8a3fb76cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7fa8a74a2820 (LWP 3070)): [KCrash Handler] #5 QBasicAtomicInt::ref (this=0x3b40570) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #6 QList (this=0x3b40570) at /usr/include/qt4/QtCore/qlist.h:114 #7 KMail::FolderJob::msgList (this=0x3b40570) at ../../kmail/folderjob.cpp:120 #8 0x7fa8a5ed45e3 in KMAcctImap::ignoreJobsForMessage (this=0x24690a0, msg=0x21dd1f0) at ../../kmail/kmacctimap.cpp:217 #9 0x7fa8a5fe5b77 in KMMoveCommand::execute (this=0x453a100) at ../../kmail/kmcommands.cpp:2192 #10 0x7fa8a5fd734a in KMCommand::slotPostTransfer (this=0x453a100, result=KMCommand::OK) at ../../kmail/kmcommands.cpp:291 #11 0x7fa8a5fe0c83 in KMCommand::qt_metacall (this=0x453a100, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff5a01fa90) at ./kmcommands.moc:93 #12 0x7fa8a5fe0f30 in KMMoveCommand::qt_metacall (this=0x7fff5a01f690, _c=62129520, _id=67, _a=0x8eff10) at ./kmcommands.moc:1971 #13 0x7fa8a48fee3f in QMetaObject::activate (sender=0x453a100, m=value optimized out, local_signal_index=value optimized out, argv=0x8eff10) at kernel/qobject.cpp:3293 #14 0x7fa8a5fd201e in KMCommand::messagesTransfered (this=0x7fff5a01f690, _t1=KMCommand::OK) at ./kmcommands.moc:108 #15 0x7fa8a5fe864c in KMCommand::transferSelectedMsgs (this=0x453a100) at ../../kmail/kmcommands.cpp:389 #16 0x7fa8a5fe8858 in KMCommand::slotStart (this=0x453a100) at ../../kmail/kmcommands.cpp:283 #17 0x7fa8a5fe0c66 in KMCommand::qt_metacall (this=0x453a100, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff5a01fcf0) at ./kmcommands.moc:92 #18 0x7fa8a5fe0f30 in KMMoveCommand::qt_metacall (this=0x7fff5a01f690, _c=62129520, _id=67, _a=0x8eff10) at ./kmcommands.moc:1971 #19 0x7fa8a48fee3f in QMetaObject::activate (sender=0x35addf0, m=value optimized out, local_signal_index=value optimized out, argv=0x8eff10) at kernel/qobject.cpp:3293 #20 0x7fa8a490665f in QSingleShotTimer::timerEvent (this=0x35addf0) at kernel/qtimer.cpp:308 #21 0x7fa8a48fba63 in QObject::event (this=0x35addf0, e=0x7fff5a020450) at kernel/qobject.cpp:1212 #22 0x7fa8a4dbf22c in QApplicationPrivate::notify_helper (this=0x21e26f0, receiver=0x35addf0, e=0x7fff5a020450) at kernel/qapplication.cpp:4300 #23 0x7fa8a4dc56fb in QApplication::notify (this=0x7fff5a0208c0, receiver=0x35addf0, e=0x7fff5a020450) at kernel/qapplication.cpp:4183 #24 0x7fa8a6ec1526 in KApplication::notify (this=0x7fff5a0208c0, receiver=0x35addf0,
[Bug 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=193514 Mark Garrow scun...@cox.net changed: What|Removed |Added CC||scun...@cox.net -- 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 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=193514 --- Comment #110 from Mark Garrow scunizi cox net 2010-06-22 17:54:23 --- Created an attachment (id=48236) -- (http://bugs.kde.org/attachment.cgi?id=48236) New crash information added by DrKonqi Akonadi server does not start before Kontact on boot.. After booting I must Quit Kontact, restart Akonadi server.. then start Kontact to get syncing with google to work.. unfortunately the calandar sync seems to have issues I haven't decyphered yet. -- 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 226783] Do not store password for external mysql server in plaintext
https://bugs.kde.org/show_bug.cgi?id=226783 Matěj Laitl ma...@laitl.cz changed: What|Removed |Added CC||ma...@laitl.cz --- Comment #1 from Matěj Laitl matej laitl cz 2010-06-22 21:29:02 --- Yup, storing it in kwallet would be much more secure while almost equally convenient. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- 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 242520] New: crash while adding a new smtp account
https://bugs.kde.org/show_bug.cgi?id=242520 Summary: crash while adding a new smtp account Product: kontact Version: 4.4.3 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: xtek...@gmail.com Application: kontact (4.4.3) KDE Platform Version: 4.4.4 (KDE 4.4.4) Qt Version: 4.6.3 Operating System: Linux 2.6.32-22-generic i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: crash while adding a new smtp accountcrash while adding a new smtp account -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb778f990 (LWP 31608))] Thread 2 (Thread 0xb3434b70 (LWP 31623)): #0 0x00fae422 in __kernel_vsyscall () #1 0x01d68b86 in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0x020364eb in g_poll () from /lib/libglib-2.0.so.0 #3 0x020290ac in ?? () from /lib/libglib-2.0.so.0 #4 0x020294b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x0113ee6f in QEventDispatcherGlib::processEvents (this=0x9713170, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #6 0x0759 in QEventLoop::processEvents (this=0xb3434270, flags=) at kernel/qeventloop.cpp:149 #7 0x0baa in QEventLoop::exec (this=0xb3434270, flags=...) at kernel/qeventloop.cpp:201 #8 0x01012fc9 in QThread::exec (this=0x98802e8) at thread/qthread.cpp:487 #9 0x010f11db in QInotifyFileSystemWatcherEngine::run (this=0x98802e8) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x0101597e in QThreadPrivate::start (arg=0x98802e8) at thread/qthread_unix.cpp:248 #11 0x00cb696e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #12 0x01d76a4e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb778f990 (LWP 31608)): [KCrash Handler] #6 QBasicAtomicInt::deref (this=0xac02c50, other=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_i386.h:132 #7 QString::operator= (this=0xac02c50, other=...) at tools/qstring.cpp:1281 #8 0x0062a15f in KPIM::ProgressItem::setStatus(QString const) () from /usr/lib/libkdepim.so.4 #9 0xb4646b66 in ?? () from /usr/lib/libkmailprivate.so.4 #10 0xb4647e26 in ?? () from /usr/lib/libkmailprivate.so.4 #11 0x0111847a in QMetaObject::metacall (object=0xa09d858, cl=31458240, idx=13, argv=0xbfe03cd4) at kernel/qmetaobject.cpp:237 #12 0x01126fbb in QMetaObject::activate (sender=0x9f61630, m=0x72a52d0, local_signal_index=0, argv=0xbfe03cd4) at kernel/qobject.cpp:3295 #13 0x070f0c09 in KIO::TransferJob::data (this=0x9f61630, _t1=0x9f61630, _t2=...) at ./jobclasses.moc:388 #14 0x070f3a62 in KIO::TransferJob::slotData (this=0x9f61630, _data=...) at ../../kio/kio/job.cpp:984 #15 0x070f7ae5 in KIO::TransferJob::qt_metacall (this=0x9f61630, _c=QMetaObject::InvokeMetaMethod, _id=48, _a=0xbfe03e68) at ./jobclasses.moc:368 #16 0x0111847a in QMetaObject::metacall (object=0x9f61630, cl=31458240, idx=48, argv=0xbfe03e68) at kernel/qmetaobject.cpp:237 #17 0x01126fbb in QMetaObject::activate (sender=0xac25080, m=0x72a7f44, local_signal_index=0, argv=0xbfe03e68) at kernel/qobject.cpp:3295 #18 0x071c43c3 in KIO::SlaveInterface::data (this=0xac25080, _t1=...) at ./slaveinterface.moc:146 #19 0x071c768f in KIO::SlaveInterface::dispatch (this=0xac25080, _cmd=100, rawdata=...) at ../../kio/kio/slaveinterface.cpp:163 #20 0x071c4763 in KIO::SlaveInterface::dispatch (this=0xac25080) at ../../kio/kio/slaveinterface.cpp:91 #21 0x071b7c28 in KIO::Slave::gotInput (this=0xac25080) at ../../kio/kio/slave.cpp:324 #22 0x071b7e33 in KIO::Slave::qt_metacall (this=0xac25080, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfe0414c) at ./slave.moc:82 #23 0x0111847a in QMetaObject::metacall (object=0xac25080, cl=31458240, idx=30, argv=0xbfe0414c) at kernel/qmetaobject.cpp:237 #24 0x01126fbb in QMetaObject::activate (sender=0xa4a2628, m=0x72a4820, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295 #25 0x070c1bd7 in KIO::Connection::readyRead (this=0xa4a2628) at ./connection.moc:92 #26 0x070c3f8e in KIO::ConnectionPrivate::dequeue (this=0xa29ea18) at ../../kio/kio/connection.cpp:82 #27 0x070c40be in KIO::Connection::qt_metacall (this=0xa4a2628, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xa8c5fe0) at ./connection.moc:79 #28 0x0111847a in QMetaObject::metacall (object=0xa4a2628, cl=31458240, idx=5, argv=0xa8c5fe0) at kernel/qmetaobject.cpp:237 #29 0x01122b46 in QMetaCallEvent::placeMetaCall (this=0xa7e9780, object=0xa4a2628) at kernel/qobject.cpp:561 #30 0x01123c0e in QObject::event (this=0xa4a2628, e=0xa7e9780) at kernel/qobject.cpp:1248 #31 0x0135fe8c in QApplicationPrivate::notify_helper (this=0x943b330, receiver=0xa4a2628, e=0xa7e9780) at kernel/qapplication.cpp:4302 #32 0x01366a0e in QApplication::notify (this=0xbfe04aa4, receiver=0xa4a2628, e=0xa7e9780) at kernel/qapplication.cpp:3706 #33 0x008c1ffa in KApplication::notify (this=0xbfe04aa4,
[Bug 242530] New: Wishlist: have composer warn you if you forgot to add attachments
https://bugs.kde.org/show_bug.cgi?id=242530 Summary: Wishlist: have composer warn you if you forgot to add attachments Product: kmail Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: composer AssignedTo: kdepim-bugs@kde.org ReportedBy: bch...@artic.edu Version: unspecified (using KDE 4.3.2) OS:Linux One of the most common embarrassments for email users around the world is sending an email but forgetting to add important attachments. This leads to rounds of polite but slightly reproachful other emails asking the sender to re-send with the attachment, uncertainty on everyone's part that perhaps their mail client messed up, and general confusion and waste of time and bandwidth. To help reduce this problem, would it be possible to put pre-sending filters into the composer component? This could check for phrases or words which suggest that someone means to attach something, such as I've attached the ... and if it thinks you meant to add an attachment, pop up a little warning before sending. Naturally, add a prominent control to disable this helpful feature, since it will annoy the pants off many users - but for others it may save us from frequently looking like a dope in email to friends and colleagues. Reproducible: Always -- 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
=?windows-1252?Q?Strafbeitr=E4ge_f=FCr_Privat_Krankenversicherte, _es_hat_sich_so_einiges_ge=E4ndert...?=
Oxford Business News Wenn diese E-Mail nicht richtig angezeigt wird, klicken Sie bitte hier. Die Regeln für Privat Krankenversicherte ändern sich ständig. Seit einigen Monate gibt es sogar Strafbeiträge für die Nichteinhaltung der Vorgaben, die auch rückwirkend gelten...mehr Ihr Matthew Holmes (Chefredakteur) Auf den Traffic kommt es an: Mehr Kunden und mehr Umsatz dank professioneller Suchmaschinenoptimierung (SEO) Hand auf's Herz: Schauen Sie bei den Suchergebnissen von Google Co. auf Seite zwei, drei oder noch weiter hinten nach, um eine Antwort auf Ihre Suchanfrage zu bekommen? Wahrscheinlich nicht. mehr... Privat Krankenversicherte aufgepasst! Seit einigen Monaten gibt es sogar Strafbeiträge für die Nichteinhaltung der Vorgaben, die auch rückwirkend gelten. Das heißt, wer die Krankenversicherungspflicht nicht einhält, der wird, mit zum Teil drastischen Strafbeiträgen belegt. Wer keine Krankenversicherung nachweisen kann, wird bis zu 5 Jahre nachbelastet. mehr... Präsentieren Sie Ihr Unternehmen über 1,5 Mio. Geschäftsleuten und Unternehmen! Wollen Sie Ihr Unternehmen über 1,5 Millionen Geschäftsleuten und Unternehmen präsentieren? Und dabei auch gleich Traffic für Ihre Homepage generieren oder noch besser, direkt Anfragen erhalten? mehr... Wie das Bürgerentlastungsgesetz Ihre Altersvorsorge bezahlt… Nach jahrelangen Diskussionen über Gesetzesänderungen, Steueranpassungen und Reformen ist weitestgehend jedem klar, dass die Renten wie Sie vom Staat später ausgezahlt werden, bei weitem nicht ausreichen, um sein Leben zu finanzieren, geschweige denn seinen Lebensstandard zu halten. mehr... Tschüss Brille! Beschlagene Brillengläser, gereizte Augen durch Kontaktlinsen in rauchiger Luft oder in Räumen mit Klimaanlage, umständliche Reinigungsprozeduren und die ständige Suche nach der Brille oder der verlorenen Linse... Sie tragen eine „Sehhilfe und kennen alle Probleme, die damit verbunden sind? mehr... Fahrspaß oder Platzangebot? In Italien kein Gegensatz Sportlich oder familientauglich, praktisch oder elegant - beim Autokauf gibt es unterschiedliche Ansprüche. Doch die Gegensätze nähern sich an. mehr... Damit kriegt jeder sein Fett weg: Drei Richtige für Fitness, Beweglichkeit und viel Spaß Rund drei Viertel der Bevölkerung halten sich an Winston Churchills Maxime „No Sports! Umso wichtiger ist es, immer wieder die positiven Effekte eines regelmäßigen Fitnesstrainings auf Gesundheit, Wohlbefinden und Beweglichkeit zu betonen. mehr... In dieser Ausgabe: Auf den Traffic kommt es an: Mehr Kunden und mehr Umsatz dank professioneller Suchmaschinenoptimierung (SEO) Privat Krankenversicherte aufgepasst! Präsentieren Sie Ihr Unternehmen über 1,5 Mio. Geschäftsleuten und Unternehmen! Wie das Bürgerentlastungsgesetz Ihre Altersvorsorge bezahlt… Tschüss Brille! Fahrspaß oder Platzangebot? In Italien kein Gegensatz Damit kriegt jeder sein Fett weg: Drei Richtige für Fitness, Beweglichkeit und viel Spaß © 2010 Oxford Business News, www.obn24.com Oxford Business News ist eine Publikation der Eureka Consultancy Ltd., 147-155 St John Street, London EC1V 4PY, United Kingdom Wenn Sie keine Newsletter mehr wünschen, dann klicken Sie hier. Um die Zusendung des Newsletters, insbesondere bei Freemail-Diensten wie GMX, WEB.DE oder AOL zu garantieren, bitten wir Sie, unsere Absender-Adresse in Ihr Adressbuch aufzunehmen. Dazu markieren Sie bitte die E-Mail Adresse und kopieren diese in Ihr Adressbuch. Herzlichen Dank! ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 212844] Blank paragraphs in html mail do not display.
https://bugs.kde.org/show_bug.cgi?id=212844 s...@bnt.ca changed: What|Removed |Added CC||s...@bnt.ca -- 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 229213] akonadi only starts successfully the second time 'round
https://bugs.kde.org/show_bug.cgi?id=229213 Nancy Anthracite na...@anthracite.name changed: What|Removed |Added CC||na...@anthracite.name --- Comment #3 from Nancy Anthracite nancy anthracite name 2010-06-23 02:39:17 --- I am having the same problem with 4.4.4 and prior versions as well. He is the akonadi error report that comes up the first time you start Kontact Test 1: SUCCESS Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system. File content of '/home/nancy/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL SizeThreshold=4096 ExternalPayload=false [QMYSQL] Name=akonadi User= Password= Options=UNIX_SOCKET=/home/nancy/.local/share/akonadi/db_misc/mysql.socket ServerPath=/usr/sbin/mysqld StartServer=true Host= [Debug] Tracer=null Test 2: SUCCESS MySQL server found. Details: You currently have configured Akonadi to use the MySQL server '/usr/sbin/mysqld'. Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld', its locations varies depending on the distribution. Test 3: SUCCESS MySQL server is executable. Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.47-1 for debian-linux-gnu on i486 ((Debian)) Test 4: ERROR MySQL server log contains errors. Details: The MySQL server error log file apos;a href='/home/nancy/.local/share/akonadi/db_data/mysql.err'/home/nancy/.local/share/akonadi/db_data/mysql.err/aapos; contains errors. File content of '/home/nancy/.local/share/akonadi/db_data/mysql.err': 100622 19:22:46 [Note] Plugin 'FEDERATED' is disabled. 100622 19:22:47 InnoDB: Started; log sequence number 0 127206153 100622 19:22:47 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them 100622 19:22:47 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 100622 19:22:47 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.1.47-1-log' socket: '/home/nancy/.local/share/akonadi/db_misc/mysql.socket' port: 0 (Debian) Test 5: SUCCESS MySQL server default configuration found. Details: The default configuration for the MySQL server was found and is readable at a href='/etc/akonadi/mysql-global.conf'/etc/akonadi/mysql-global.conf/a. File content of '/etc/akonadi/mysql-global.conf': # # Global Akonadi MySQL server settings, # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf # # Based on advice by Kris Köhntopp k...@mysql.com # [mysqld] skip_grant_tables skip_networking # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled #sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat #sql_mode=strict_trans_tables # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # case-insensitive table names, avoids trouble on windows lower_case_table_names=1 character_set_server=latin1 collation_server=latin1_general_ci table_cache=200 thread_cache_size=3 log_bin=mysql-bin expire_logs_days=3 #sync_bin_log=0 # error log file name, relative to datadir log_error=mysql.err log_warnings=2 # log all queries, useful for debugging but generates an enormous amount of data #log=mysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) #log_slow_queries=mysql.slow #long_query_time=1 # log queries not using indices, debug only, disable for production use #log_queries_not_using_indexes=1 # maximum blob size max_allowed_packet=32M max_connections=256 # makes sense when having the same query multiple times # makes no sense with prepared statements and/or transactions query_cache_type=0 query_cache_size=0 innodb_file_per_table=1 innodb_log_buffer_size=1M innodb_additional_mem_pool_size=1M # messure database size and adjust # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in (mysql, information_schema); innodb_buffer_pool_size=80M # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like inno%, show global variables) innodb_log_file_size=64M
[Bug 229213] akonadi only starts successfully the second time 'round
https://bugs.kde.org/show_bug.cgi?id=229213 --- Comment #4 from Nancy Anthracite nancy anthracite name 2010-06-23 02:40:45 --- I am having the same problem with 4.4.4 and prior versions as well. He is the akonadi error report that comes up the first time you start Kontact Test 1: SUCCESS Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system. File content of '/home/nancy/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL SizeThreshold=4096 ExternalPayload=false [QMYSQL] Name=akonadi User= Password= Options=UNIX_SOCKET=/home/nancy/.local/share/akonadi/db_misc/mysql.socket ServerPath=/usr/sbin/mysqld StartServer=true Host= [Debug] Tracer=null Test 2: SUCCESS MySQL server found. Details: You currently have configured Akonadi to use the MySQL server '/usr/sbin/mysqld'. Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld', its locations varies depending on the distribution. Test 3: SUCCESS MySQL server is executable. Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.47-1 for debian-linux-gnu on i486 ((Debian)) Test 4: ERROR MySQL server log contains errors. Details: The MySQL server error log file apos;a href='/home/nancy/.local/share/akonadi/db_data/mysql.err'/home/nancy/.local/share/akonadi/db_data/mysql.err/aapos; contains errors. File content of '/home/nancy/.local/share/akonadi/db_data/mysql.err': 100622 19:22:46 [Note] Plugin 'FEDERATED' is disabled. 100622 19:22:47 InnoDB: Started; log sequence number 0 127206153 100622 19:22:47 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them 100622 19:22:47 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 100622 19:22:47 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.1.47-1-log' socket: '/home/nancy/.local/share/akonadi/db_misc/mysql.socket' port: 0 (Debian) Test 5: SUCCESS MySQL server default configuration found. Details: The default configuration for the MySQL server was found and is readable at a href='/etc/akonadi/mysql-global.conf'/etc/akonadi/mysql-global.conf/a. File content of '/etc/akonadi/mysql-global.conf': # # Global Akonadi MySQL server settings, # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf # # Based on advice by Kris Köhntopp k...@mysql.com # [mysqld] skip_grant_tables skip_networking # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled #sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat #sql_mode=strict_trans_tables # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # case-insensitive table names, avoids trouble on windows lower_case_table_names=1 character_set_server=latin1 collation_server=latin1_general_ci table_cache=200 thread_cache_size=3 log_bin=mysql-bin expire_logs_days=3 #sync_bin_log=0 # error log file name, relative to datadir log_error=mysql.err log_warnings=2 # log all queries, useful for debugging but generates an enormous amount of data #log=mysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) #log_slow_queries=mysql.slow #long_query_time=1 # log queries not using indices, debug only, disable for production use #log_queries_not_using_indexes=1 # maximum blob size max_allowed_packet=32M max_connections=256 # makes sense when having the same query multiple times # makes no sense with prepared statements and/or transactions query_cache_type=0 query_cache_size=0 innodb_file_per_table=1 innodb_log_buffer_size=1M innodb_additional_mem_pool_size=1M # messure database size and adjust # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in (mysql, information_schema); innodb_buffer_pool_size=80M # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like inno%, show global variables) innodb_log_file_size=64M innodb_flush_log_at_trx_commit=2 Test 6: SKIP MySQL server custom configuration not available. Details: The custom configuration for the MySQL server was not found but is optional. Test 7: SUCCESS MySQL server configuration is
[Bug 229213] akonadi only starts successfully the second time 'round
https://bugs.kde.org/show_bug.cgi?id=229213 --- Comment #5 from Nancy Anthracite nancy anthracite name 2010-06-23 02:41:17 --- I am having the same problem with 4.4.4 and prior versions as well. He is the akonadi error report that comes up the first time you start Kontact Test 1: SUCCESS Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system. File content of '/home/nancy/.config/akonadi/akonadiserverrc': [%General] Driver=QMYSQL SizeThreshold=4096 ExternalPayload=false [QMYSQL] Name=akonadi User= Password= Options=UNIX_SOCKET=/home/nancy/.local/share/akonadi/db_misc/mysql.socket ServerPath=/usr/sbin/mysqld StartServer=true Host= [Debug] Tracer=null Test 2: SUCCESS MySQL server found. Details: You currently have configured Akonadi to use the MySQL server '/usr/sbin/mysqld'. Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld', its locations varies depending on the distribution. Test 3: SUCCESS MySQL server is executable. Details: MySQL server found: /usr/sbin/mysqld Ver 5.1.47-1 for debian-linux-gnu on i486 ((Debian)) Test 4: ERROR MySQL server log contains errors. Details: The MySQL server error log file apos;a href='/home/nancy/.local/share/akonadi/db_data/mysql.err'/home/nancy/.local/share/akonadi/db_data/mysql.err/aapos; contains errors. File content of '/home/nancy/.local/share/akonadi/db_data/mysql.err': 100622 19:22:46 [Note] Plugin 'FEDERATED' is disabled. 100622 19:22:47 InnoDB: Started; log sequence number 0 127206153 100622 19:22:47 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them 100622 19:22:47 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 100622 19:22:47 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.1.47-1-log' socket: '/home/nancy/.local/share/akonadi/db_misc/mysql.socket' port: 0 (Debian) Test 5: SUCCESS MySQL server default configuration found. Details: The default configuration for the MySQL server was found and is readable at a href='/etc/akonadi/mysql-global.conf'/etc/akonadi/mysql-global.conf/a. File content of '/etc/akonadi/mysql-global.conf': # # Global Akonadi MySQL server settings, # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf # # Based on advice by Kris Köhntopp k...@mysql.com # [mysqld] skip_grant_tables skip_networking # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled #sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat #sql_mode=strict_trans_tables # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # case-insensitive table names, avoids trouble on windows lower_case_table_names=1 character_set_server=latin1 collation_server=latin1_general_ci table_cache=200 thread_cache_size=3 log_bin=mysql-bin expire_logs_days=3 #sync_bin_log=0 # error log file name, relative to datadir log_error=mysql.err log_warnings=2 # log all queries, useful for debugging but generates an enormous amount of data #log=mysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) #log_slow_queries=mysql.slow #long_query_time=1 # log queries not using indices, debug only, disable for production use #log_queries_not_using_indexes=1 # maximum blob size max_allowed_packet=32M max_connections=256 # makes sense when having the same query multiple times # makes no sense with prepared statements and/or transactions query_cache_type=0 query_cache_size=0 innodb_file_per_table=1 innodb_log_buffer_size=1M innodb_additional_mem_pool_size=1M # messure database size and adjust # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in (mysql, information_schema); innodb_buffer_pool_size=80M # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like inno%, show global variables) innodb_log_file_size=64M innodb_flush_log_at_trx_commit=2 Test 6: SKIP MySQL server custom configuration not available. Details: The custom configuration for the MySQL server was not found but is optional. Test 7: SUCCESS MySQL server configuration is
