[Bug 241929] Debian creates invalid mime attachment when attaching file with enter in filename
https://bugs.kde.org/show_bug.cgi?id=241929 --- Comment #1 from Robert Wohlrab 2010-06-16 22:21:48 --- Created an attachment (id=48062) --> (http://bugs.kde.org/attachment.cgi?id=48062) Tar with example file with enter in filename -- 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 241929] New: Debian creates invalid mime attachment when attaching file with enter in filename
https://bugs.kde.org/show_bug.cgi?id=241929 Summary: Debian creates invalid mime attachment when attaching file with enter in filename Product: kmail Version: 1.13.3 Platform: Debian unstable OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: robert.wohl...@gmx.de Created an attachment (id=48061) --> (http://bugs.kde.org/attachment.cgi?id=48061) Mail created by kmail Version: 1.13.3 OS:Linux I attached simple file with an enter in the filename in kmails composer and noticed that the resulting mails always have a complete destroyed mime attachment. I attach a test.mbox with such an email created by kmail and a test_enter.tar which has an example file included with an enter in its filename Reproducible: Didn't try Steps to Reproduce: 1. open kmail 2. press "new" 3. attach file with enter in filename 4. press message -> "save as draft" (send would also work, but this is easier for an local test) 5. Go into your drafts folder 6. open mail you send 7. press right mouse on the attachment symbol 8. click on "open with..." 9. open it with kate Actual Results: The file you attached now starts with something like: %2Etxt Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*=us-ascii''test %2Etxt and after that there is the actual file data Expected Results: Just get the file data without that scrambled mime header stuff -- 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 235837] Freezes when changing date of item in todo
https://bugs.kde.org/show_bug.cgi?id=235837 --- Comment #2 from Robert Wohlrab 2010-04-30 20:11:03 --- Sry, forgot to click on summary first - it also happens with ical resource if i follow the steps as described above. -- 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 235837] Freezes when changing date of item in todo
https://bugs.kde.org/show_bug.cgi?id=235837 --- Comment #1 from Robert Wohlrab 2010-04-30 20:09:31 --- It doesn't seem to happen when I use akonadis ical resource, but when I use kolab or traditional resource -- 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 235837] New: Freezes when changing date of item in todo
https://bugs.kde.org/show_bug.cgi?id=235837 Summary: Freezes when changing date of item in todo Product: kontact Version: 4.4.2 Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: robert.wohl...@gmx.de Version: 4.4.2 (using KDE 4.4.2) OS:Linux Installed from:Debian testing/unstable Packages Steps: * open kontact * open summary * open to-do list * change date of item (was 2010-05-07 and changed it to 2010-05-06) When clicking on ok it will freeze the whole program. CPU idles. I use akonadi to store my calender, but it seems to be independend on the actual data storage in akonadi. backtrace: #0 0x00310bac0633 in *__GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00310de42299 in g_main_context_poll (context=, block=, dispatch=, self=) at /tmp/buildd/glib2.0-2.24.0/glib/gmain.c:2904 #2 g_main_context_iterate (context=, block=, dispatch=, self=) at /tmp/buildd/glib2.0-2.24.0/glib/gmain.c:2586 #3 0x00310de426ec in IA__g_main_context_iteration (context=, may_block=) at /tmp/buildd/glib2.0-2.24.0/glib/gmain.c:2654 #4 0x0031123a7373 in QEventDispatcherGlib::processEvents (this=, flags=) at kernel/qeventdispatcher_glib.cpp:412 #5 0x003d8d4a73de in QGuiEventDispatcherGlib::processEvents (this=, flags=) at kernel/qguieventdispatcher_glib.cpp:204 #6 0x00311237c842 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #7 0x00311237cc1c in QEventLoop::exec (this=, flags=) at kernel/qeventloop.cpp:201 #8 0x003d8e101c46 in KJob::exec (this=) at ../../kdecore/jobs/kjob.cpp:204 #9 0x7fe72e870c9c in SDSummaryWidget::updateView (this=0x3464f10) at ../../../../kontact/plugins/specialdates/sdsummarywidget.cpp:219 #10 0x7fe72e874430 in SDSummaryWidget::qt_metacall (this=0x3464f10, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff8b755b30) at ./sdsummarywidget.moc:79 #11 0x003112390c4f in QMetaObject::activate (sender=, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3293 #12 0x003d9427764c in KCal::Calendar::qt_metacall (this=, _c=, _id=, _a=) at ./calendar.moc:82 #13 0x003d942d74b0 in KCal::CalendarResources::qt_metacall (this=, _c=, _id=, _a=) at ./calendarresources.moc:85 #14 0x003112390c4f in QMetaObject::activate (sender=, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3293 #15 0x003d942c978f in KCal::ResourceCalendar::resourceChanged (this=, _t1=) at ./resourcecalendar.moc:123 #16 0x7fe72c405da8 in KCal::ResourceAkonadi::Private::incidenceChanged (this=0x1e08660, incidencePtr=..., subResourceIdentifier=) at ../../../kresources/kcal/resourceakonadi_p.cpp:395 #17 0x7fe72c406524 in KCal::ResourceAkonadi::Private::qt_metacall (this=0x1e08660, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff8b755f70) at ./resourceakonadi_p.moc:82 #18 0x003112390c4f in QMetaObject::activate (sender=, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3293 #19 0x7fe72c40cb7a in SubResource::incidenceChanged (this=0x22a0780, _t1=, _t2=) at ./subresource.moc:99 #20 0x7fe72c40d9e3 in SubResource::itemChanged (this=0x7fe724008c20, item=...) at ../../../kresources/kcal/subresource.cpp:147 #21 0x7fe72c421b77 in SubResourceBase::changeItem (this=0x7fe724008c20, item=...) at ../../../kresources/shared/subresourcebase.cpp:156 #22 0x7fe72c407be6 in SubResourceModel::itemChanged (this=0x1e086c8, item=...) at ../../../kresources/shared/subresourcemodel.h:205 #23 0x7fe72c411b40 in AbstractSubResourceModel::qt_metacall (this=0x1e086c8, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff8b7562a0) at ./abstractsubresourcemodel.moc:109 #24 0x003112390c4f in QMetaObject::activate (sender=, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3293 #25 0x003d91b0e7e7 in Akonadi::Monitor::itemChanged (this=, _t1=, _t2=) at ./monitor.moc:160 #26 0x003d91b10d1f in Akonadi::MonitorPrivate::emitItemNotification (this=, msg=, item=, collection=, collectionDest=) at ../../akonadi/monitor_p.cpp:327 #27 0x003d91b11833 in Akonadi::MonitorPrivate::emitNotification (this=, msg=) at ../../akonadi/monitor_p.cpp:196 #28 0x003d91b11a33 in Akonadi::MonitorPrivate::dataAvailable (this=) at ../../akonadi/monitor_p.cpp:205 #29 0x003d91b0e843 in Akonadi::Monitor::qt_metacall (this=, _c=, _id=, _a=) at ./monitor.moc:148 #30 0x003112390c4f in QMetaObject::activate (sender=, m=, local_signal_index=, argv=) at kernel/qobject.cpp:3293 #31 0x003d91a8a220 in Akonadi::EntityCache::fetchResult(KJob*) () from /usr/lib/libakonadi-kde.so.4 #32 0x003d91abc8a3 in Akonadi::EntityCacheBase::qt_metacall (this=, _c=, _id=, _a=) at ./entitycache_p.moc:77 #33 0x003112390c4f in QMetaObject::activate (sender=, m=, local_signal_index=, argv=
[Bug 232678] Crashes when filtering messages on imap
https://bugs.kde.org/show_bug.cgi?id=232678 --- Comment #3 from Robert Wohlrab 2010-03-30 13:13:55 --- Ok, I changed my first rule from "doing nothing" to "Move into gmail/inbox" and now it doesn't crash anymore -- 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 232678] Crashes when filtering messages on imap
https://bugs.kde.org/show_bug.cgi?id=232678 --- Comment #2 from Robert Wohlrab 2010-03-30 13:05:21 --- It doesn't seem to happen when I receive a message in the cyrus2.2 imapd. My first configuration was pop3 on the intranet server and imap with the gmail server. But since the configuration of the intranet server was changed, I have to use imap on them. I had never such problems when the the intranet server was pop3 - but it confuses me that it crashes now when the filter runs on the gmail imap stuff (or better: should stop to process the filter list when it runs over the first filter rule). I can recreate the crash without any problems when I receive a message on gmail, but not with the intranet/cyrus2.2 imap -- 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 232678] Crashes when filtering messages on imap
https://bugs.kde.org/show_bug.cgi?id=232678 --- Comment #1 from Robert Wohlrab 2010-03-30 12:59:11 --- Just build everything with debug and -O0. Program received signal SIGSEGV, Segmentation fault. 0x7784e8a0 in KMail::ActionScheduler::actionMessage (this=0x1868fa0, res=KMFilterAction::GoOn) at ../../kmail/actionscheduler.cpp:675 675 action->processAsync( msg ); Just received a message on gmail imap and that is the backtrace: #0 0x7784e8a0 in KMail::ActionScheduler::actionMessage (this=0x1868fa0, res=KMFilterAction::GoOn) at ../../kmail/actionscheduler.cpp:675 action = 0x41 msg = 0x69d6a0 #1 0x7784e6ad in KMail::ActionScheduler::filterMessage (this=0x1868fa0) at ../../kmail/actionscheduler.cpp:648 No locals. #2 0x778505aa in KMail::ActionScheduler::qt_metacall (this=0x1868fa0, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffd3d0) at ./actionscheduler.moc:124 No locals. #3 0x0039e1f66df2 in QMetaObject::activate (sender=, from_signal_index=, to_signal_index=, argv=) at kernel/qobject.cpp:3112 previousSender = method = currentSender = Could not find the frame base for "QMetaObject::activate(QObject*, int, int, void**)". Simple backtrace: #0 0x7784e8a0 in KMail::ActionScheduler::actionMessage (this=0x1868fa0, res=KMFilterAction::GoOn) at ../../kmail/actionscheduler.cpp:675 #1 0x7784e6ad in KMail::ActionScheduler::filterMessage (this=0x1868fa0) at ../../kmail/actionscheduler.cpp:648 #2 0x778505aa in KMail::ActionScheduler::qt_metacall (this=0x1868fa0, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0x7fffd3d0) at ./actionscheduler.moc:124 #3 0x0039e1f66df2 in QMetaObject::activate (sender=, from_signal_index=, to_signal_index=, argv=) at kernel/qobject.cpp:3112 #4 0x0039e1f61353 in QObject::event (this=, e=) at kernel/qobject.cpp:1074 #5 0x0039e25d801d in QApplicationPrivate::notify_helper (this=, receiver=, e=) at kernel/qapplication.cpp:4065 #6 0x0039e25e007a in QApplication::notify (this=, receiver=, e=) at kernel/qapplication.cpp:4030 #7 0x0039e4a22de6 in KApplication::notify (this=, receiver=, event=) at ../../kdeui/kernel/kapplication.cpp:302 #8 0x0039e1f51c9c in QCoreApplication::notifyInternal (this=, receiver=, event=) at kernel/qcoreapplication.cpp:610 #9 0x0039e1f7e2c6 in QCoreApplication::sendEvent (this=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #10 QTimerInfoList::activateTimers (this=) at kernel/qeventdispatcher_unix.cpp:580 #11 0x0039e1f7a658 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:184 #12 idleTimerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:231 #13 0x003ce243b90e in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #14 0x003ce243f2c8 in ?? () from /lib/libglib-2.0.so.0 #15 0x003ce243f3f0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #16 0x0039e1f7a39c in QEventDispatcherGlib::processEvents (this=, flags=) at kernel/qeventdispatcher_glib.cpp:407 #17 0x0039e266ef1f in QGuiEventDispatcherGlib::processEvents (this=, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #18 0x0039e1f50562 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #19 0x0039e1f50934 in QEventLoop::exec (this=, flags=) at kernel/qeventloop.cpp:201 #20 0x0039e1f52ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #21 0x0040364b in main (argc=2, argv=0x7fffe078) at ../../kmail/main.cpp:146 -- 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 232678] New: Crashes when filtering messages on imap
https://bugs.kde.org/show_bug.cgi?id=232678 Summary: Crashes when filtering messages on imap Product: kmail Version: 1.12.4 Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: robert.wohl...@gmx.de Version: 1.12.4 (using KDE 4.3.4) OS:Linux Installed from:Debian testing/unstable Packages I have two different imap servers. One is gmail and the other one is a intranet server with cyrus2.2. My filter settings first check if the mail is from the imap account at gmail. If this is true then we stop processing there (just a check for >= 0 bytes and in advanced tab that we only do that for gmai-imap). The other filter just check for different criterias to sort them in the right folders - like spam assasin and clamav. Now I get a mail from gmail imap and kmail crashes with following backtrace: Program received signal SIGSEGV, Segmentation fault. #0 KMail::ActionScheduler::actionMessage (this=, res=) at ../../kmail/actionscheduler.cpp:675 action = msg = #1 0x003694207e09 in KMail::ActionScheduler::filterMessage (this=) at ../../kmail/actionscheduler.cpp:648 No locals. #2 0x0036942081c4 in KMail::ActionScheduler::qt_metacall (this=, _c=, _id=, _a=) at ./actionscheduler.moc:124 No locals. #3 0x0039e1f66df2 in QMetaObject::activate (sender=, from_signal_index=, to_signal_index=, argv=) at kernel/qobject.cpp:3112 previousSender = method = currentSender = Could not find the frame base for "QMetaObject::activate(QObject*, int, int, void**)". Or the longer (non "bt-full): #0 KMail::ActionScheduler::actionMessage (this=, res=) at ../../kmail/actionscheduler.cpp:675 #1 0x003694207e09 in KMail::ActionScheduler::filterMessage (this=) at ../../kmail/actionscheduler.cpp:648 #2 0x0036942081c4 in KMail::ActionScheduler::qt_metacall (this=, _c=, _id=, _a=) at ./actionscheduler.moc:124 #3 0x0039e1f66df2 in QMetaObject::activate (sender=, from_signal_index=, to_signal_index=, argv=) at kernel/qobject.cpp:3112 #4 0x0039e1f61353 in QObject::event (this=, e=) at kernel/qobject.cpp:1074 #5 0x0039e25d801d in QApplicationPrivate::notify_helper (this=, receiver=, e=) at kernel/qapplication.cpp:4065 #6 0x0039e25e007a in QApplication::notify (this=, receiver=, e=) at kernel/qapplication.cpp:4030 #7 0x0039e4a22de6 in KApplication::notify (this=, receiver=, event=) at ../../kdeui/kernel/kapplication.cpp:302 #8 0x0039e1f51c9c in QCoreApplication::notifyInternal (this=, receiver=, event=) at kernel/qcoreapplication.cpp:610 #9 0x0039e1f7e2c6 in QCoreApplication::sendEvent (this=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #10 QTimerInfoList::activateTimers (this=) at kernel/qeventdispatcher_unix.cpp:580 #11 0x0039e1f7a658 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:184 #12 idleTimerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:231 #13 0x003ce243b90e in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #14 0x003ce243f2c8 in ?? () from /lib/libglib-2.0.so.0 #15 0x003ce243f3f0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #16 0x0039e1f7a39c in QEventDispatcherGlib::processEvents (this=, flags=) at kernel/qeventdispatcher_glib.cpp:407 #17 0x0039e266ef1f in QGuiEventDispatcherGlib::processEvents (this=, flags=) at kernel/qguieventdispatcher_glib.cpp:202 #18 0x0039e1f50562 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #19 0x0039e1f50934 in QEventLoop::exec (this=, flags=) at kernel/qeventloop.cpp:201 #20 0x0039e1f52ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #21 0x00402fa9 in main (argc=, argv=) at ../../kmail/main.cpp:146 -- 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 198415] New: kmail cannot set tags through filter
https://bugs.kde.org/show_bug.cgi?id=198415 Summary: kmail cannot set tags through filter Product: kmail Version: 1.11.4 Platform: Debian testing OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: robert.wohl...@gmx.de Version: 1.11.4 (using KDE 4.2.4) OS:Linux Installed from:Debian testing/unstable Packages I wanted to set tags automatically when I receive messages to remove my old folder based structure (which is is too unflexible). The problem is that I can only mark messages through the filter. This list doesn't show my tags but stuff like ham, important and so on. It would also be nice to mark messages with the same tags used in my kaddressbook for people... or be able to scan a message through an external program which produces a list of tags which is added to the message. -- 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
