[akregator] [Bug 358586] New: akregator crash after startup (after system crash)
https://bugs.kde.org/show_bug.cgi?id=358586 Bug ID: 358586 Summary: akregator crash after startup (after system crash) Product: akregator Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: msch...@gentoo.org Application: akregator (5.1.2) Qt Version: 5.5.1 Operating System: Linux 4.1.6-gentoo x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: - What I was doing when the application crashed: My Laptop went out of battery, so I had to restart. Akregator asks to restore session, I choose "YES", then click on some feed in the feedlist. Before the list appears: kaboom! -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f40bcd1e880 (LWP 4292))] Thread 6 (Thread 0x7f40ba7b2700 (LWP 4293)): #0 0x7f40d596f64d in poll () from /lib64/libc.so.6 #1 0x7f40cd40dac2 in poll (__timeout=-1, __nfds=1, __fds=0x7f40ba7b1c40) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0xbedfb0, cond=cond@entry=0xbedff0, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459 #3 0x7f40cd40f72f in xcb_wait_for_event (c=0xbedfb0) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693 #4 0x7f40bc913c89 in QXcbEventReader::run (this=0xbfc110) at qxcbconnection.cpp:1229 #5 0x7f40d61f34f2 in QThreadPrivate::start (arg=0xbfc110) at thread/qthread_unix.cpp:331 #6 0x7f40cf9e2444 in start_thread () from /lib64/libpthread.so.0 #7 0x7f40d59786ad in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f40b3dc0700 (LWP 4310)): #0 0x7f40d596f64d in poll () from /lib64/libc.so.6 #1 0x7f40cde46f1c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f40ac0013c0, timeout=8849, context=0x7f40ac0009b0) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f40ac0009b0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3835 #3 0x7f40cde4702c in g_main_context_iteration (context=0x7f40ac0009b0, may_block=1) at /var/tmp/portage/dev-libs/glib-2.46.2-r1/work/glib-2.46.2/glib/gmain.c:3901 #4 0x7f40d63ee03c in QEventDispatcherGlib::processEvents (this=0x7f40ac0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #5 0x7f40d639f27a in QEventLoop::exec (this=this@entry=0x7f40b3dbfd40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f40d61eea84 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7f40d61f34f2 in QThreadPrivate::start (arg=0xdb27c0) at thread/qthread_unix.cpp:331 #8 0x7f40cf9e2444 in start_thread () from /lib64/libpthread.so.0 #9 0x7f40d59786ad in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f40a6990700 (LWP 4312)): #0 0x7f40d596b62d in read () from /lib64/libc.so.6 #1 0x7f40c5be3f45 in ?? () from /usr/lib64/libnvidia-tls.so.346.96 #2 0x7f40be304cd1 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-7.1.so #3 0x7f40c057c16e in pa_mainloop_prepare () from /usr/lib64/libpulse.so.0 #4 0x7f40c057cbe0 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #5 0x7f40c057cca0 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #6 0x7f40c058b016 in ?? () from /usr/lib64/libpulse.so.0 #7 0x7f40be332d38 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-7.1.so #8 0x7f40cf9e2444 in start_thread () from /lib64/libpthread.so.0 #9 0x7f40d59786ad in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f408700 (LWP 4316)): #0 0x7f40be321f60 in pa_pstream_unref () from /usr/lib64/pulseaudio/libpulsecommon-7.1.so #1 0x7f40be3224b3 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-7.1.so #2 0x7f40be322d1a in ?? () from /usr/lib64/pulseaudio/libpulsecommon-7.1.so #3 0x7f40c057c7f7 in pa_mainloop_dispatch () from /usr/lib64/libpulse.so.0 #4 0x7f40c057cbfc in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #5 0x7f40c057cca0 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #6 0x7f40c058b016 in ?? () from /usr/lib64/libpulse.so.0 #7 0x7f40be332d38 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-7.1.so #8 0x7f40cf9e2444 in start_thread () from /lib64/libpthread.so.0 #9 0x7f40d59786ad in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f408ebfd700 (LWP 4320)): #0 0x7f40cf9e83b8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f40d61f3b58 in QWaitConditionPrivate::wait_relative (time=3, this=0x125be50) at
[Akonadi] [Bug 331038] New: Crash of dav groupware resource after resume from s2r
https://bugs.kde.org/show_bug.cgi?id=331038 Bug ID: 331038 Summary: Crash of dav groupware resource after resume from s2r Classification: Unclassified Product: Akonadi Version: 4.12 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: msch...@gentoo.org Application: akonadi_davgroupware_resource (4.12) KDE Platform Version: 4.12.2 (Compiled from sources) Qt Version: 4.8.5 Operating System: Linux 3.12.7-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: This crash happened right after resuming from suspend to ram The crash can be reproduced sometimes. -- Backtrace: Application: sys4 vom Typ DAV-Groupware-Ressource (akonadi_davgroupware_resource), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. To enable execution of this file add add-auto-load-safe-path /usr/lib64/gcc/x86_64-pc-linux-gnu/4.8.2/libstdc++.so.6.0.18-gdb.py line to your configuration file /home/mschiff/.gdbinit. To completely disable this security protection add set auto-load safe-path / line to your configuration file /home/mschiff/.gdbinit. For more information about this security protection see the Auto-loading safe path section in the GDB manual. E.g., run from the shell: info (gdb)Auto-loading safe path [KCrash Handler] #6 0x2b44c44ee1f9 in raise () from /lib64/libc.so.6 #7 0x2b44c44ef558 in abort () from /lib64/libc.so.6 #8 0x2b44c05bf0b4 in qt_message_output (msgType=msgType@entry=QtFatalMsg, buf=optimized out) at global/qglobal.cpp:2323 #9 0x2b44c05bf219 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, msg=msg@entry=0x2b44c072c8e0 ASSERT failure in %s: \%s\, file %s, line %d, ap=ap@entry=0x7fff25d2f6d8) at global/qglobal.cpp:2369 #10 0x2b44c05bfa9c in qFatal (msg=msg@entry=0x2b44c072c8e0 ASSERT failure in %s: \%s\, file %s, line %d) at global/qglobal.cpp:2552 #11 0x2b44c05bfb0a in qt_assert_x (where=where@entry=0x2b44c214c848 ResourceBase::collectionsRetrieved(), what=what@entry=0x2b44c214c7f8 Calling collectionsRetrieved() although no collection retrieval is in progress, file=file@entry=0x2b44c214c4b8 /var/tmp/portage/kde-base/kdepimlibs-4.12.49./work/kdepimlibs-4.12.49./akonadi/resourcebase.cpp, line=line@entry=695) at global/qglobal.cpp:2026 #12 0x2b44c209fae0 in Akonadi::ResourceBase::collectionsRetrieved (this=this@entry=0x1f56100, collections=...) at /var/tmp/portage/kde-base/kdepimlibs-4.12.49./work/kdepimlibs-4.12.49./akonadi/resourcebase.cpp:692 #13 0x00448416 in DavGroupwareResource::onRetrieveCollectionsFinished (this=0x1f56100, job=optimized out) at /var/tmp/portage/kde-base/kdepim-runtime-4.12.49./work/kdepim-runtime-4.12.49./resources/dav/resource/davgroupwareresource.cpp:525 #14 0x2b44c06de828 in QMetaObject::activate (sender=sender@entry=0x40b7e10, m=m@entry=0x2b44c1a285c0 KJob::staticMetaObject, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff25d2fbe0) at kernel/qobject.cpp:3547 #15 0x2b44c1681312 in KJob::result (this=this@entry=0x40b7e10, _t1=_t1@entry=0x40b7e10) at /var/tmp/portage/kde-base/kdelibs-4.12.49./work/kdelibs-4.12.49._build/kdecore/kjob.moc:207 #16 0x2b44c1681350 in KJob::emitResult (this=this@entry=0x40b7e10) at /var/tmp/portage/kde-base/kdelibs-4.12.49./work/kdelibs-4.12.49./kdecore/jobs/kjob.cpp:318 #17 0x0041a890 in DavCollectionsMultiFetchJob::davJobFinished (this=0x40b7e10, job=0x394d130) at /var/tmp/portage/kde-base/kdepim-runtime-4.12.49./work/kdepim-runtime-4.12.49./resources/dav/common/davcollectionsmultifetchjob.cpp:60 #18 0x2b44c06de828 in QMetaObject::activate (sender=sender@entry=0x394d130, m=m@entry=0x2b44c1a285c0 KJob::staticMetaObject, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff25d2fd60) at kernel/qobject.cpp:3547 #19 0x2b44c1681312 in KJob::result (this=this@entry=0x394d130, _t1=_t1@entry=0x394d130) at /var/tmp/portage/kde-base/kdelibs-4.12.49./work/kdelibs-4.12.49._build/kdecore/kjob.moc:207 #20 0x2b44c1681350 in KJob::emitResult (this=this@entry=0x394d130) at /var/tmp/portage/kde-base/kdelibs-4.12.49./work/kdelibs-4.12.49./kdecore/jobs/kjob.cpp:318 #21 0x00415605 in DavCollectionsFetchJob::collectionsFetchFinished (this=0x394d130, job=optimized out) at /var/tmp/portage/kde-base/kdepim-runtime-4.12.49./work/kdepim-runtime-4.12.49./resources/dav/common/davcollectionsfetchjob.cpp:304 #22 0x2b44c06de828 in QMetaObject::activate (sender=sender@entry=0x25efd10, m=m@entry=0x2b44c1a285c0 KJob::staticMetaObject, local_signal_index=local_signal_index@entry=3,
[Akonadi] [Bug 325287] dav resource often crashes maybe because flaky internet connection
https://bugs.kde.org/show_bug.cgi?id=325287 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added CC||msch...@gentoo.org -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 325287] dav resource often crashes maybe because flaky internet connection
https://bugs.kde.org/show_bug.cgi?id=325287 --- Comment #1 from Marc Schiffbauer msch...@gentoo.org --- Created attachment 84746 -- https://bugs.kde.org/attachment.cgi?id=84746action=edit New crash information added by DrKonqi akonadi_davgroupware_resource (4.12) on KDE Platform 4.12.0 using Qt 4.8.5 - What I was doing when the application crashed: This still happens. To reproduce you can try to just restart NetworkManager which will disconnect and reconnect your wifi connection. DAV crashes on reconnecttghen most of the time. -- Backtrace (Reduced): #11 0x7f5b17e87b0a in qt_assert_x (where=where@entry=0x7f5b16669b32 createItemSyncInstance, what=what@entry=0x7f5b16669538 Calling items retrieval methods although no item retrieval is in progress, file=file@entry=0x7f5b16669458 /var/tmp/portage/kde-base/kdepimlibs-4.12.49./work/kdepimlibs-4.12.49./akonadi/resourcebase.cpp, line=line@entry=167) at global/qglobal.cpp:2026 #12 0x7f5b165bb366 in createItemSyncInstanceIfMissing (this=0x2462da0) at /var/tmp/portage/kde-base/kdepimlibs-4.12.49./work/kdepimlibs-4.12.49./akonadi/resourcebase.cpp:166 #13 Akonadi::ResourceBase::itemsRetrievedIncremental (this=this@entry=0x23b5490, changedItems=..., removedItems=...) at /var/tmp/portage/kde-base/kdepimlibs-4.12.49./work/kdepimlibs-4.12.49./akonadi/resourcebase.cpp:1053 #14 0x0044b4cd in DavGroupwareResource::onRetrieveItemsFinished (this=0x23b5490, job=optimized out) at /var/tmp/portage/kde-base/kdepim-runtime-4.12.49./work/kdepim-runtime-4.12.49./resources/dav/resource/davgroupwareresource.cpp:600 [...] #16 0x7f5b16f3ff02 in KJob::result (this=this@entry=0x2afed90, _t1=_t1@entry=0x2afed90) at /var/tmp/portage/kde-base/kdelibs-4.12.49./work/kdelibs-4.12.49._build/kdecore/kjob.moc:207 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 325777] New: imap resource crash with flaky wifi connection
https://bugs.kde.org/show_bug.cgi?id=325777 Bug ID: 325777 Summary: imap resource crash with flaky wifi connection Classification: Unclassified Product: Akonadi Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: er...@kde.org Reporter: msch...@gentoo.org CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.11) KDE Platform Version: 4.11.2 (Compiled from sources) Qt Version: 4.8.4 Operating System: Linux 3.9.11-gentoo-r1 x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: This crash seems still not fixed, happened today with current 4.11 branch. -- Backtrace: Application: Privat vom Typ IMAP-E-Mail-Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f8d3c03f780 (LWP 15875))] Thread 5 (Thread 0x7f8d20e9b700 (LWP 16167)): #0 0x7f8d36852fc9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f8d36814a6b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8d3681524e in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8d36815454 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8d3b435806 in QEventDispatcherGlib::processEvents (this=0x7f8d180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7f8d3b40635f in QEventLoop::processEvents (this=this@entry=0x7f8d20e9ae70, flags=...) at kernel/qeventloop.cpp:149 #6 0x7f8d3b4065e8 in QEventLoop::exec (this=this@entry=0x7f8d20e9ae70, flags=...) at kernel/qeventloop.cpp:204 #7 0x7f8d3b30a330 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #8 0x7f8d3b30caac in QThreadPrivate::start (arg=0xf79b30) at thread/qthread_unix.cpp:338 #9 0x7f8d37181f3b in start_thread () from /lib64/libpthread.so.0 #10 0x7f8d378ed26d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f8d2920c700 (LWP 16340)): #0 0x7f8d36852d89 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f8d36852ff9 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8d36814a53 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8d3681524e in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8d36815454 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f8d3b435806 in QEventDispatcherGlib::processEvents (this=0x7f8d240197d0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f8d3b40635f in QEventLoop::processEvents (this=this@entry=0x7f8d2920be70, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f8d3b4065e8 in QEventLoop::exec (this=this@entry=0x7f8d2920be70, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f8d3b30a330 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #9 0x7f8d3b30caac in QThreadPrivate::start (arg=0xfc8e30) at thread/qthread_unix.cpp:338 #10 0x7f8d37181f3b in start_thread () from /lib64/libpthread.so.0 #11 0x7f8d378ed26d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f8d28a0b700 (LWP 20652)): #0 0x7f8d36852d75 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f8d36852fc9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8d36814f36 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8d36815398 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8d36815454 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f8d3b435806 in QEventDispatcherGlib::processEvents (this=0x7f8d1c052ad0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f8d3b40635f in QEventLoop::processEvents (this=this@entry=0x7f8d28a0ae70, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f8d3b4065e8 in QEventLoop::exec (this=this@entry=0x7f8d28a0ae70, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f8d3b30a330 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #9 0x7f8d3b30caac in QThreadPrivate::start (arg=0xf1ec10) at thread/qthread_unix.cpp:338 #10 0x7f8d37181f3b in start_thread () from /lib64/libpthread.so.0 #11 0x7f8d378ed26d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f8d177fe700 (LWP 21584)): #0 0x7f8d37184085 in pthread_mutex_lock () from /lib64/libpthread.so.0 #1 0x7f8d36852fd1 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #2 0x7f8d368144ae in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #3 0x7f8d36815204 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f8d36815454 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f8d3b435806 in QEventDispatcherGlib::processEvents (this=0x7f8d0800d150, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6
[Akonadi] [Bug 325287] New: imap resource often crashes maybe because flaky internet connection
https://bugs.kde.org/show_bug.cgi?id=325287 Bug ID: 325287 Summary: imap resource often crashes maybe because flaky internet connection Classification: Unclassified Product: Akonadi Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: msch...@gentoo.org Application: akonadi_davgroupware_resource (4.11) KDE Platform Version: 4.11.1 (Compiled from sources) Qt Version: 4.8.4 Operating System: Linux 3.9.11-gentoo-r1 x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: When having a flaky internet connection (WLAN with very poor signal) the akonadi imap resource crashes every now and then. The crash can be reproduced sometimes. -- Backtrace: Application: sys4 vom Typ DAV-Groupware-Ressource (akonadi_davgroupware_resource), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [KCrash Handler] #6 0x7f7401b23545 in raise () from /lib64/libc.so.6 #7 0x7f7401b249c8 in abort () from /lib64/libc.so.6 #8 0x7f740595d6b4 in qt_message_output (msgType=msgType@entry=QtFatalMsg, buf=optimized out) at global/qglobal.cpp:2323 #9 0x7f740595d828 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, msg=msg@entry=0x7f7405ac4a18 ASSERT failure in %s: \%s\, file %s, line %d, ap=ap@entry=0x7fffaa3bd548) at global/qglobal.cpp:2369 #10 0x7f740595d9bc in qFatal (msg=msg@entry=0x7f7405ac4a18 ASSERT failure in %s: \%s\, file %s, line %d) at global/qglobal.cpp:2552 #11 0x7f740595d9ea in qt_assert_x (where=where@entry=0x7f7404167894 createItemSyncInstance, what=what@entry=0x7f74041671e8 Calling items retrieval methods although no item retrieval is in progress, file=file@entry=0x7f7404166f78 /var/tmp/portage/kde-base/kdepimlibs-4.11.49./work/kdepimlibs-4.11.49./akonadi/resourcebase.cpp, line=line@entry=171) at global/qglobal.cpp:2026 #12 0x7f74040c1526 in Akonadi::ResourceBasePrivate::createItemSyncInstanceIfMissing (this=0x20bb6d0) at /var/tmp/portage/kde-base/kdepimlibs-4.11.49./work/kdepimlibs-4.11.49./akonadi/resourcebase.cpp:170 #13 0x7f74040bc4c5 in Akonadi::ResourceBase::itemsRetrievedIncremental (this=this@entry=0x20bee90, changedItems=..., removedItems=...) at /var/tmp/portage/kde-base/kdepimlibs-4.11.49./work/kdepimlibs-4.11.49./akonadi/resourcebase.cpp:1091 #14 0x004486e0 in DavGroupwareResource::onRetrieveItemsFinished (this=0x20bee90, job=optimized out) at /var/tmp/portage/kde-base/kdepim-runtime-4.11.49./work/kdepim-runtime-4.11.49./resources/dav/resource/davgroupwareresource.cpp:600 #15 0x7f7405a768e4 in QMetaObject::activate (sender=sender@entry=0x25aca70, m=m@entry=0x7f7404dcc4c0 KJob::staticMetaObject, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fffaa3bdab0) at kernel/qobject.cpp:3539 #16 0x7f7404a292d2 in KJob::result (this=this@entry=0x25aca70, _t1=_t1@entry=0x25aca70) at /var/tmp/portage/kde-base/kdelibs-4.11.49./work/kdelibs-4.11.49._build/kdecore/kjob.moc:208 #17 0x7f7404a29310 in KJob::emitResult (this=this@entry=0x25aca70) at /var/tmp/portage/kde-base/kdelibs-4.11.49./work/kdelibs-4.11.49./kdecore/jobs/kjob.cpp:318 #18 0x00426215 in DavItemsListJob::davJobFinished (this=0x25aca70, job=optimized out) at /var/tmp/portage/kde-base/kdepim-runtime-4.11.49./work/kdepim-runtime-4.11.49./resources/dav/common/davitemslistjob.cpp:193 #19 0x7f7405a768e4 in QMetaObject::activate (sender=sender@entry=0x3d95040, m=m@entry=0x7f7404dcc4c0 KJob::staticMetaObject, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fffaa3bdff0) at kernel/qobject.cpp:3539 #20 0x7f7404a292d2 in KJob::result (this=this@entry=0x3d95040, _t1=_t1@entry=0x3d95040) at /var/tmp/portage/kde-base/kdelibs-4.11.49./work/kdelibs-4.11.49._build/kdecore/kjob.moc:208 #21 0x7f7404a29310 in KJob::emitResult (this=this@entry=0x3d95040) at /var/tmp/portage/kde-base/kdelibs-4.11.49./work/kdelibs-4.11.49./kdecore/jobs/kjob.cpp:318 #22 0x7f74044fefa2 in KIO::SimpleJob::slotFinished (this=this@entry=0x3d95040) at /var/tmp/portage/kde-base/kdelibs-4.11.49./work/kdelibs-4.11.49./kio/kio/job.cpp:496 #23 0x7f74044ff425 in KIO::TransferJob::slotFinished (this=this@entry=0x3d95040) at /var/tmp/portage/kde-base/kdelibs-4.11.49./work/kdelibs-4.11.49./kio/kio/job.cpp:1099 #24 0x7f74044d9f6a in KIO::DavJob::slotFinished (this=0x3d95040) at /var/tmp/portage/kde-base/kdelibs-4.11.49./work/kdelibs-4.11.49./kio/kio/davjob.cpp:138 #25 0x7f7405a768e4 in QMetaObject::activate (sender=sender@entry=0x224b3f0,
[kmail2] [Bug 314010] kmail composer regression: Cursor jumps to end of line after every keypress
https://bugs.kde.org/show_bug.cgi?id=314010 --- Comment #23 from Marc Schiffbauer msch...@gentoo.org --- Update from my side: Seems to be fixed for me in 4.11, atm I cannot reproduce it anymore and I could 100% with latest 4.10 -- 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 316107] big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 --- Comment #7 from Marc Schiffbauer msch...@gentoo.org --- Bump: This problem still exists in current 4.11 branch -- 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 319131] kmail preview pane hangs on Retrieving... when leaving email with ICS attachment
https://bugs.kde.org/show_bug.cgi?id=319131 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added CC||msch...@gentoo.org --- Comment #3 from Marc Schiffbauer msch...@gentoo.org --- It *seems* that this fixes my long standing problem with kmail described in bug 316107 , and maybe bug 301178 and bug 311184 I will see if it happens again in the next couple of days or not -- 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 316107] big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 --- Comment #6 from Marc Schiffbauer msch...@gentoo.org --- The problem with too many (dead) concurrent connections seems to be gone or not happening as often as it used to, but the message display problems still exists in current 4.11 branch. Any news on this? Maybe these bugs *may* be related (please do not mark as duplicate): bug #301178 and bug #311184 -- 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 314010] kmail composer regression: Cursor jumps to end of line after every keypress
https://bugs.kde.org/show_bug.cgi?id=314010 --- Comment #19 from Marc Schiffbauer msch...@gentoo.org --- I dont think its related to ldap -- 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 322772] New: kmail should treat attached text/plain files named *.asc in signed and/or encrypted mails as mime type application/pgp-keys
https://bugs.kde.org/show_bug.cgi?id=322772 Bug ID: 322772 Summary: kmail should treat attached text/plain files named *.asc in signed and/or encrypted mails as mime type application/pgp-keys Classification: Unclassified Product: kmail2 Version: 4.11 rc2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: msch...@gentoo.org I assume that this is not a bug in kmail at all, as attached plaintext keys should be marked as application/pgp-keys instead of text/plain. But in reality there are Encryption gateways out there which attach peoples pgp-keys as text/plain However, to increase interoperability and usability it might be good to some more intelligence: Would it be complicated to implement if kmail checked the file-extension of an attachement and if the message is signed and/or encryped, and if a text/plain part is detected with a filename like *.asc, then handle that part if it was application/pgp-keys? That way one could just import the key by klicking on it... Ideas? Reproducible: Always -- 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 322772] kmail should treat attached text/plain files named *.asc in signed and/or encrypted mails as mime type application/pgp-keys
https://bugs.kde.org/show_bug.cgi?id=322772 --- Comment #2 from Marc Schiffbauer msch...@gentoo.org --- Hi Laurent, done! Thx. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 322414] New: akonadi_davgroupware_resource crash on startup
https://bugs.kde.org/show_bug.cgi?id=322414 Bug ID: 322414 Summary: akonadi_davgroupware_resource crash on startup Classification: Unclassified Product: Akonadi Version: 4.10 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: msch...@gentoo.org Application: akonadi_davgroupware_resource (4.10) KDE Platform Version: 4.10.95 (Compiled from sources) Qt Version: 4.8.4 Operating System: Linux 3.9.7-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: I got this crash right after kde startup. I happens often after login but not every time. -- Backtrace: Application: MCS vom Typ DAV-Groupware-Ressource (akonadi_davgroupware_resource), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [KCrash Handler] #6 0x7fc3c57e4545 in raise () from /lib64/libc.so.6 #7 0x7fc3c57e59c8 in abort () from /lib64/libc.so.6 #8 0x7fc3c96216c4 in qt_message_output (msgType=msgType@entry=QtFatalMsg, buf=optimized out) at global/qglobal.cpp:2323 #9 0x7fc3c9621838 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, msg=msg@entry=0x7fc3c9788948 ASSERT: \%s\ in file %s, line %d, ap=ap@entry=0x7fffc2ccdb08) at global/qglobal.cpp:2369 #10 0x7fc3c96219cc in qFatal (msg=msg@entry=0x7fc3c9788948 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2552 #11 0x7fc3c9621a16 in qt_assert (assertion=assertion@entry=0x7fc3c7e0db85 !localNode-processed, file=file@entry=0x7fc3c7e0d800 /var/tmp/portage/kde-base/kdepimlibs-4.11.49./work/kdepimlibs-4.11.49./akonadi/collectionsync.cpp, line=line@entry=306) at global/qglobal.cpp:2018 #12 0x7fc3c7cf8c43 in Akonadi::CollectionSync::Private::processPendingRemoteNodes (this=this@entry=0x20acc50, _localRoot=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.11.49./work/kdepimlibs-4.11.49./akonadi/collectionsync.cpp:306 #13 0x7fc3c7cfceac in execute (this=0x20acc50) at /var/tmp/portage/kde-base/kdepimlibs-4.11.49./work/kdepimlibs-4.11.49./akonadi/collectionsync.cpp:525 #14 Akonadi::CollectionSync::Private::localCollectionFetchResult (this=0x20acc50, job=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.11.49./work/kdepimlibs-4.11.49./akonadi/collectionsync.cpp:184 #15 0x7fc3c7cf2a19 in qt_static_metacall (_a=0x7fffc2cce220, _id=1, _o=0x1dd2af0, _c=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.11.49./work/kdepimlibs-4.11.49._build/akonadi/moc_collectionsync_p.cpp:59 #16 Akonadi::CollectionSync::qt_static_metacall (_o=0x1dd2af0, _c=optimized out, _id=optimized out, _a=0x7fffc2cce220) at /var/tmp/portage/kde-base/kdepimlibs-4.11.49./work/kdepimlibs-4.11.49._build/akonadi/moc_collectionsync_p.cpp:52 #17 0x7fc3c973b854 in QMetaObject::activate (sender=sender@entry=0x20cc130, m=m@entry=0x7fc3c8a894c0 KJob::staticMetaObject, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fffc2cce220) at kernel/qobject.cpp:3539 #18 0x7fc3c86e6292 in KJob::result (this=this@entry=0x20cc130, _t1=_t1@entry=0x20cc130) at /var/tmp/portage/kde-base/kdelibs-4.11.49./work/kdelibs-4.11.49._build/kdecore/kjob.moc:208 #19 0x7fc3c86e62d0 in KJob::emitResult (this=0x20cc130) at /var/tmp/portage/kde-base/kdelibs-4.11.49./work/kdelibs-4.11.49./kdecore/jobs/kjob.cpp:318 #20 0x7fc3c973ad4e in QObject::event (this=0x20cc130, e=optimized out) at kernel/qobject.cpp:1194 #21 0x7fc3c624efec in QApplicationPrivate::notify_helper (this=this@entry=0x1d78cf0, receiver=receiver@entry=0x20cc130, e=e@entry=0x20dfa70) at kernel/qapplication.cpp:4562 #22 0x7fc3c6253411 in QApplication::notify (this=this@entry=0x7fffc2ccebf0, receiver=receiver@entry=0x20cc130, e=e@entry=0x20dfa70) at kernel/qapplication.cpp:4423 #23 0x7fc3c6f6c1e6 in KApplication::notify (this=0x7fffc2ccebf0, receiver=0x20cc130, event=0x20dfa70) at /var/tmp/portage/kde-base/kdelibs-4.11.49./work/kdelibs-4.11.49./kdeui/kernel/kapplication.cpp:311 #24 0x7fc3c972658e in QCoreApplication::notifyInternal (this=0x7fffc2ccebf0, receiver=receiver@entry=0x20cc130, event=event@entry=0x20dfa70) at kernel/qcoreapplication.cpp:946 #25 0x7fc3c9729ea9 in sendEvent (event=0x20dfa70, receiver=0x20cc130) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #26 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1d4b1f0) at kernel/qcoreapplication.cpp:1570 #27 0x7fc3c972a113 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1463 #28 0x7fc3c9754683 in sendPostedEvents () at
[kmail2] [Bug 314010] kmail composer regression: Cursor jumps to end of line after every keypress
https://bugs.kde.org/show_bug.cgi?id=314010 --- Comment #15 from Marc Schiffbauer msch...@gentoo.org --- For me this is fixed in current 4.11 branch -- 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 321787] crash while starting external application to view an attachment
https://bugs.kde.org/show_bug.cgi?id=321787 --- Comment #4 from Marc Schiffbauer msch...@gentoo.org --- I still need to check our desktop file. But please rethink this: The desktop is a small textfile which can be ok or not. Or it may be outdated for example. Do you really think its acceptable that kmail will *crash* if such a desktop file is broken? I still cinsider this a bug, because expected behavior may be an informational Message about that (best case) or opening the external program juts not working (worst case), but not a crash of kmail. What do you think? -- 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 321787] crash while starting external application to view an attachment
https://bugs.kde.org/show_bug.cgi?id=321787 --- Comment #6 from Marc Schiffbauer msch...@gentoo.org --- Montel, I appreciate your clarification, thanks! I overlooked that its an Q_ASSERT actually. -- 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 321927] autoconfig support not working properly
https://bugs.kde.org/show_bug.cgi?id=321927 --- Comment #2 from Marc Schiffbauer msch...@gentoo.org --- Wow, this was quick. Works like a charm now thanks Montel! -- 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 321927] New: autoconfig support not working properly
https://bugs.kde.org/show_bug.cgi?id=321927 Bug ID: 321927 Summary: autoconfig support not working properly Classification: Unclassified Product: kmail2 Version: 4.10.5 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-bugs@kde.org Reporter: msch...@gentoo.org kmail has an autoconfig feature that can use the mozilla autoconfig protocol to configure email accounts. However this feature does not work properly. I tried to configure my email account but kmail failed to autoconfigure it. I am using automx to serve the autoconfig service. You can use http://automx.org for testing the feature. Reproducible: Always Steps to Reproduce: 1. Start Tools - Account Wizard 2. Enter aut...@automx.org as mail address and automx as password 3. Click Next Actual Results: kmail will fail to configure the account Expected Results: kmail should query the correct DNS records and find the service that will serve all data required to configure account data -- 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 321787] New: crash while starting external application to view an attachment
https://bugs.kde.org/show_bug.cgi?id=321787 Bug ID: 321787 Summary: crash while starting external application to view an attachment Classification: Unclassified Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: msch...@gentoo.org Application: kmail (4.10.5) KDE Platform Version: 4.10.4 (Compiled from sources) Qt Version: 4.8.4 Operating System: Linux 3.9.7-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: I got an email with a .pps-File attached. By clicking on the attachement I am asked what to do and I click the Open with LibreOffice Impress - kaboom! The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7fd71302e780 (LWP 20742))] Thread 3 (Thread 0x7fd6f28d1700 (LWP 20746)): #0 0x7fd70e115cec in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd703a63ded in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7fd703a63ef9 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7fd70e111f3b in start_thread () from /lib64/libpthread.so.0 #4 0x7fd7102f226d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fd6f1fd0700 (LWP 20747)): #0 0x7fd7102e85dd in poll () from /lib64/libc.so.6 #1 0x7fd7083066a6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fd7083067d4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fd710c76836 in QEventDispatcherGlib::processEvents (this=0x7fd6ec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fd710c472df in QEventLoop::processEvents (this=this@entry=0x7fd6f1fcfe70, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fd710c47568 in QEventLoop::exec (this=this@entry=0x7fd6f1fcfe70, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fd710b4ab40 in QThread::exec (this=optimized out) at thread/qthread.cpp:542 #7 0x7fd710b4dabc in QThreadPrivate::start (arg=0x299a610) at thread/qthread_unix.cpp:338 #8 0x7fd70e111f3b in start_thread () from /lib64/libpthread.so.0 #9 0x7fd7102f226d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fd71302e780 (LWP 20742)): [KCrash Handler] #6 0x7fd71023c545 in raise () from /lib64/libc.so.6 #7 0x7fd71023d9c8 in abort () from /lib64/libc.so.6 #8 0x7fd710b436c4 in qt_message_output (msgType=msgType@entry=QtFatalMsg, buf=optimized out) at global/qglobal.cpp:2323 #9 0x7fd710b43838 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, msg=msg@entry=0x7fd710caa948 ASSERT: \%s\ in file %s, line %d, ap=ap@entry=0x7fffcfb47138) at global/qglobal.cpp:2369 #10 0x7fd710b439cc in qFatal (msg=msg@entry=0x7fd710caa948 ASSERT: \%s\ in file %s, line %d) at global/qglobal.cpp:2552 #11 0x7fd710b43a16 in qt_assert (assertion=assertion@entry=0x7fd70d0dc499 supportedProtocols.isEmpty(), file=file@entry=0x7fd70d0dbcd0 /var/tmp/portage/kde-base/kdelibs-4.10.49./work/kdelibs-4.10.49./kio/kio/krun.cpp, line=line@entry=377) at global/qglobal.cpp:2018 #12 0x7fd70cfe68c3 in supportedProtocols (_service=...) at /var/tmp/portage/kde-base/kdelibs-4.10.49./work/kdelibs-4.10.49./kio/kio/krun.cpp:377 #13 0x7fd70cfeb917 in resolveURLs (_service=..., _urls=...) at /var/tmp/portage/kde-base/kdelibs-4.10.49./work/kdelibs-4.10.49./kio/kio/krun.cpp:742 #14 KRun::run (_service=..., _urls=..., window=0x0, tempFiles=false, suggestedFileName=..., asn=...) at /var/tmp/portage/kde-base/kdelibs-4.10.49./work/kdelibs-4.10.49./kio/kio/krun.cpp:1007 #15 0x7fd7091b51cb in MessageViewer::ViewerPrivate::attachmentOpenWith(KMime::Content*, KSharedPtrKService) () from /usr/lib64/libmessageviewer.so.4 #16 0x7fd7091be7a1 in MessageViewer::ViewerPrivate::openAttachment(KMime::Content*, QString const) () from /usr/lib64/libmessageviewer.so.4 #17 0x7fd70919c5ec in (anonymous namespace)::AttachmentURLHandler::handleClick(KUrl const, MessageViewer::ViewerPrivate*) const () from /usr/lib64/libmessageviewer.so.4 #18 0x7fd70919eed8 in MessageViewer::URLHandlerManager::handleClick(KUrl const, MessageViewer::ViewerPrivate*) const () from /usr/lib64/libmessageviewer.so.4 #19 0x7fd7091ad1e2 in MessageViewer::ViewerPrivate::slotUrlOpen(QUrl const) () from /usr/lib64/libmessageviewer.so.4 #20 0x7fd7091c253a in MessageViewer::ViewerPrivate::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libmessageviewer.so.4 #21 0x7fd710c5cd4e in QObject::event (this=0x2985110, e=optimized out) at kernel/qobject.cpp:1194 #22 0x7fd71117ffec in
[kmail2] [Bug 314010] kmail composer regression: Cursor jumps to end of line after every keypress
https://bugs.kde.org/show_bug.cgi?id=314010 --- Comment #12 from Marc Schiffbauer msch...@gentoo.org --- For me this is still reproducable using todays KDE/4.10 branch -- 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 316107] big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 --- Comment #4 from Marc Schiffbauer msch...@gentoo.org --- I am still having these issues everyday. And when it takes too long to display my mail or I am short of time (which happens quite too often) I login to my webmail (same server, same imap service) and read mail there because that is faster at least for one of my accounts (Which is configured to NOT cache offline copies) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 318064] crash after dav server got unreachable
https://bugs.kde.org/show_bug.cgi?id=318064 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Marc Schiffbauer msch...@gentoo.org --- Wow ;-) Many thanks Grégory! This fix seems to be a big leap forward... * The crashes *seem* to have gone (I will repopen if not) * No more Error-Message-Window flooding on connection problems -Marc -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 318064] New: crash after dav server got unreachable
https://bugs.kde.org/show_bug.cgi?id=318064 Bug ID: 318064 Summary: crash after dav server got unreachable Classification: Unclassified Product: Akonadi Version: 4.10 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: DAV Resource Assignee: kdepim-bugs@kde.org Reporter: msch...@gentoo.org Application: akonadi_davgroupware_resource (4.10) KDE Platform Version: 4.10.2 (Compiled from sources) Qt Version: 4.8.4 Operating System: Linux 3.8.3-gentoo-r1 x86_64 Distribution: NAME=Gentoo -- Information about the crash: the dav ressource tends to crash very often on connection errors. This time the server was shut down, then the resource crashed -- Backtrace: Application: sys4 vom Typ DAV-Groupware-Ressource (akonadi_davgroupware_resource), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [KCrash Handler] #6 0x7fc6f5244545 in raise () from /lib64/libc.so.6 #7 0x7fc6f52459c8 in abort () from /lib64/libc.so.6 #8 0x7fc6f8fe66c4 in qt_message_output (msgType=msgType@entry=QtFatalMsg, buf=optimized out) at global/qglobal.cpp:2323 #9 0x7fc6f8fe6838 in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, msg=0x7fc6f914d948 ASSERT: \%s\ in file %s, line %d, ap=ap@entry=0x7fff4aebac88) at global/qglobal.cpp:2369 #10 0x7fc6f8fe69cc in qFatal (msg=optimized out) at global/qglobal.cpp:2552 #11 0x7fc6f7715257 in Akonadi::ItemCreateJob::ItemCreateJob (this=0x1e1f9b0, item=..., collection=..., parent=0x1e08c90) at /var/tmp/portage/kde-base/kdepimlibs-4.10.49./work/kdepimlibs-4.10.49./akonadi/itemcreatejob.cpp:57 #12 0x7fc6f772a1c6 in Akonadi::ItemSync::Private::createLocalItem (this=0x3257b30, item=...) at /var/tmp/portage/kde-base/kdepimlibs-4.10.49./work/kdepimlibs-4.10.49./akonadi/itemsync.cpp:114 #13 0x7fc6f772b6c3 in Akonadi::ItemSync::Private::processItems (this=this@entry=0x3257b30) at /var/tmp/portage/kde-base/kdepimlibs-4.10.49./work/kdepimlibs-4.10.49./akonadi/itemsync.cpp:335 #14 0x7fc6f772be00 in Akonadi::ItemSync::Private::execute (this=this@entry=0x3257b30) at /var/tmp/portage/kde-base/kdepimlibs-4.10.49./work/kdepimlibs-4.10.49./akonadi/itemsync.cpp:291 #15 0x7fc6f772c5d5 in Akonadi::ItemSync::Private::slotLocalListDone (this=0x3257b30, job=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.10.49./work/kdepimlibs-4.10.49./akonadi/itemsync.cpp:271 #16 0x7fc6f9100854 in QMetaObject::activate (sender=0x1ae1450, m=optimized out, local_signal_index=optimized out, argv=0x7fff4aebb180) at kernel/qobject.cpp:3539 #17 0x7fc6f80ab9a2 in KJob::result (this=this@entry=0x1ae1450, _t1=_t1@entry=0x1ae1450) at /var/tmp/portage/kde-base/kdelibs-4.10.49./work/kdelibs-4.10.49._build/kdecore/kjob.moc:208 #18 0x7fc6f80ab9e0 in KJob::emitResult (this=0x1ae1450) at /var/tmp/portage/kde-base/kdelibs-4.10.49./work/kdelibs-4.10.49./kdecore/jobs/kjob.cpp:318 #19 0x7fc6f90ffd4e in QObject::event (this=0x1ae1450, e=optimized out) at kernel/qobject.cpp:1194 #20 0x7fc6f5cae964 in notify_helper (e=0x1d17080, receiver=0x1ae1450, this=0x1687200) at kernel/qapplication.cpp:4562 #21 QApplicationPrivate::notify_helper (this=0x1687200, receiver=0x1ae1450, e=0x1d17080) at kernel/qapplication.cpp:4534 #22 0x7fc6f5cb3681 in QApplication::notify (this=0x7fff4aebbba0, receiver=0x1ae1450, e=0x1d17080) at kernel/qapplication.cpp:3944 #23 0x7fc6f69f00d6 in KApplication::notify (this=0x7fff4aebbba0, receiver=0x1ae1450, event=0x1d17080) at /var/tmp/portage/kde-base/kdelibs-4.10.49./work/kdelibs-4.10.49./kdeui/kernel/kapplication.cpp:311 #24 0x7fc6f90eb58e in QCoreApplication::notifyInternal (this=0x7fff4aebbba0, receiver=receiver@entry=0x1ae1450, event=event@entry=0x1d17080) at kernel/qcoreapplication.cpp:946 #25 0x7fc6f90eeea9 in sendEvent (event=0x1d17080, receiver=0x1ae1450) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #26 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x165e7c0) at kernel/qcoreapplication.cpp:1570 #27 0x7fc6f9119683 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #28 postEventSourceDispatch (s=0x1687d50) at kernel/qeventdispatcher_glib.cpp:279 #29 0x7fc6f4d2b3c3 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #30 0x7fc6f4d2b710 in ?? () from /usr/lib64/libglib-2.0.so.0 #31 0x7fc6f4d2b7d4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #32 0x7fc6f9119816 in QEventDispatcherGlib::processEvents (this=0x165fc80, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #33 0x7fc6f5d51c3e in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=...) at
[kmail2] [Bug 316107] New: big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 Bug ID: 316107 Summary: big regression: kmail IMAP connection and message display problems Classification: Unclassified Product: kmail2 Version: 4.10 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: msch...@gentoo.org (I use current 4.10 branch of kdepim) I guess somewhere between 4.10-beta and 4.10.0 some severe connection problems have been introduced for IMAP resources. It seems existing imap connections will not be reused which leads to many open IMAP connections until the server refuses new connections. I use kmail to read IMAP mail from a dovecot server which allows a max of 10 concurrent user+ip connections in default config. I now often get a popup message showing a dovecot error message that this connection limit is exceeded. Increasing this limit to 20 later 30 did not help! I also noticed that since some weeks (three or so) kmail often takes a lot of time to show a message that has been selected in the message list. It takes around 10-20 seconds until a message is actually shown very often. I guess this is due to the connection problem also... Today it was even worse: kmail again hit the connection limit (30 connections) and the imap resource has been set to Offline by kmail. Then I set it back online via File-Work Offline, then File-work online which lead to a LOOP in which IMAP-resource messages were popping up as fast as possible telling me about the connection problem and my system was getting slower and slower It did not stop opening new popup messages and I had to manually kill -9 kmail to not let my whole system die... Reproducible: Always Steps to Reproduce: please see above. AKonadi is version 1.9.0, kdepim is current 4.10 branch -- 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 314010] kmail composer regression: Cursor jumps to end of line after every keypress
https://bugs.kde.org/show_bug.cgi?id=314010 --- Comment #4 from Marc Schiffbauer msch...@gentoo.org --- Hi Laurent, any news on this? In current kmail its almost impossible to edit the recipient of an email manually. Can you reproduce this? Thanks -Marc -- 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 314010] kmail composer regression: Cursor jumps to end of line after every keypress
https://bugs.kde.org/show_bug.cgi?id=314010 --- Comment #6 from Marc Schiffbauer msch...@gentoo.org --- No, I have: * default vcard adressbook * CardDAV Resource * Google Contacts Resource But I think I found out how to reproduce: right click on the addressfield and set Textcompletion to drop down (or similar, german locale here) If I set this to something other it works fine here too -Marc -- 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 314010] kmail composer regression: Cursor jumps to end of line after every keypress
https://bugs.kde.org/show_bug.cgi?id=314010 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Version|4.10 pre|4.10 Resolution|FIXED |--- --- Comment #2 from Marc Schiffbauer msch...@gentoo.org --- Hi Laurent, thanks for looking into it! Sorry, but for me its not fixed :-/ I just have built and tested current 4.10 branch. resetting to unconfirmed -- 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 314010] New: kmail composer regression: Cursor jumps to end of line after every keypress
https://bugs.kde.org/show_bug.cgi?id=314010 Bug ID: 314010 Summary: kmail composer regression: Cursor jumps to end of line after every keypress Classification: Unclassified Product: kmail2 Version: 4.10 pre Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: msch...@gentoo.org When editing an email address in the To: field of the composer the cursor always jumos to the end of line which makes it very hard to enter/change an email address Reproducible: Always Steps to Reproduce: 1. create new mail 2. enter some text in the To: Lineedit 3. move cursor in the middle of the text 4. press backspace Actual Results: cursor jumps to end of lineedit Expected Results: cursor shouls never be moved automatically This seems to be a regression introduced in the 4.10 RCs somewhere -- 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 314010] kmail composer regression: Cursor jumps to end of line after every keypress
https://bugs.kde.org/show_bug.cgi?id=314010 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added Keywords||regression, usability -- 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 310990] New: Akonadi resources crash after every resum from suspend to ram.
https://bugs.kde.org/show_bug.cgi?id=310990 Bug ID: 310990 Severity: crash Version: 4.9 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: Akonadi resources crash after every resum from suspend to ram. Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.9) KDE Platform Version: 4.9.3 (Compiled from sources) Qt Version: 4.8.3 Operating System: Linux 3.6.6-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: This is really annoying. Is it also causing data loss? I dont know. But various akonadi resources are crashing every time I wake up my computer from suspend to ram. The crash can be reproduced every time. -- Backtrace: Application: Becon vom Typ IMAP-E-Mail-Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f191913a780 (LWP 13515))] Thread 2 (Thread 0x7f1906007700 (LWP 23782)): #0 0x7f191494f2ad in poll () from /lib64/libc.so.6 #1 0x7f19138925f6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1913892724 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1918526be6 in QEventDispatcherGlib::processEvents (this=0x7f18f8003200, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f19184f6ab2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f19184f6d07 in QEventLoop::exec (this=0x7f1906006dc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f19183f5ef7 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f191714506c in KIMAP::SessionThread::run (this=0x21e8160) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./kimap/sessionthread.cpp:181 #8 0x7f19183f8f3c in QThreadPrivate::start (arg=0x21e8160) at thread/qthread_unix.cpp:338 #9 0x7f19141faea7 in start_thread () from /lib64/libpthread.so.0 #10 0x7f1914957eed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f191913a780 (LWP 13515)): [KCrash Handler] #6 0x7f191850d3a5 in QObject::connect (sender=0x266afc0, signal=0x47a5f0 2stateChanged(KIMAP::Session::State,KIMAP::Session::State), receiver=0x218c210, method=0x47a530 1onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State), type=Qt::AutoConnection) at kernel/qobject.cpp:2551 #7 0x0045d150 in SessionPool::onPasswordRequestDone (this=0x218c210, resultType=optimized out, password=...) at /var/tmp/portage/kde-base/kdepim-runtime-4.9.49./work/kdepim-runtime-4.9.49./resources/imap/sessionpool.cpp:335 #8 0x0045ea8c in SessionPool::qt_static_metacall (_o=0x218c210, _c=optimized out, _id=9, _a=0x7fffe28e4d60) at /var/tmp/portage/kde-base/kdepim-runtime-4.9.49./work/kdepim-runtime-4.9.49._build/resources/imap/sessionpool.moc:94 #9 0x7f191850bbc9 in QMetaObject::activate (sender=0x2174300, m=optimized out, local_signal_index=optimized out, argv=0x7fffe28e4d60) at kernel/qobject.cpp:3547 #10 0x004489d1 in PasswordRequesterInterface::done (this=optimized out, _t1=0, _t2=...) at /var/tmp/portage/kde-base/kdepim-runtime-4.9.49./work/kdepim-runtime-4.9.49._build/resources/imap/passwordrequesterinterface.moc:118 #11 0x00424f33 in SettingsPasswordRequester::onPasswordRequestCompleted (this=0x2174300, password=..., userRejected=false) at /var/tmp/portage/kde-base/kdepim-runtime-4.9.49./work/kdepim-runtime-4.9.49./resources/imap/settingspasswordrequester.cpp:89 #12 0x7f191850bbc9 in QMetaObject::activate (sender=0x2195340, m=optimized out, local_signal_index=optimized out, argv=0x7fffe28e4f40) at kernel/qobject.cpp:3547 #13 0x00423711 in Settings::passwordRequestCompleted (this=optimized out, _t1=..., _t2=false) at /var/tmp/portage/kde-base/kdepim-runtime-4.9.49./work/kdepim-runtime-4.9.49._build/resources/imap/settings.moc:124 #14 0x00423758 in Settings::requestPassword (this=0x2195340) at /var/tmp/portage/kde-base/kdepim-runtime-4.9.49./work/kdepim-runtime-4.9.49./resources/imap/settings.cpp:114 #15 0x0045baa3 in SessionPool::connect (this=0x218c210, account=optimized out) at /var/tmp/portage/kde-base/kdepim-runtime-4.9.49./work/kdepim-runtime-4.9.49./resources/imap/sessionpool.cpp:102 #16 0x004195fc in ImapResource::startConnect (this=0x20a1080) at /var/tmp/portage/kde-base/kdepim-runtime-4.9.49./work/kdepim-runtime-4.9.49./resources/imap/imapresource.cpp:218 #17 0x0041da07 in ImapResource::qt_static_metacall (_o=0x20a1080, _c=optimized out, _id=15, _a=0x7fffe28e53d0) at
[Bug 293633] KMail asked for an IMAP password, entered and crashed
https://bugs.kde.org/show_bug.cgi?id=293633 --- Comment #17 from Marc Schiffbauer msch...@gentoo.org --- Please bum this bug to 4.9.4 if its really the same bug its there now nearly 10 months -- 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 293633] KMail asked for an IMAP password, entered and crashed
https://bugs.kde.org/show_bug.cgi?id=293633 --- Comment #19 from Marc Schiffbauer msch...@gentoo.org --- For me the resource agents are crashing on every resum from suspend to ram (current 4.9) -- 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 310077] New: Crash of DAV Groupware resource right after wakeup from suspend-to-ram
https://bugs.kde.org/show_bug.cgi?id=310077 Bug ID: 310077 Severity: crash Version: 4.9 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Crash of DAV Groupware resource right after wakeup from suspend-to-ram Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: DAV Resource Product: Akonadi Application: akonadi_davgroupware_resource (4.9) KDE Platform Version: 4.9.3 (Compiled from sources) Qt Version: 4.8.3 Operating System: Linux 3.6.6-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: This crash happens quitie often right after my computer woke up after suspend to ram. Maybe the network connection is not yet ready again when akonadi tries to access a remote resource. -- Backtrace: Application: sys4 vom Typ DAV-Groupware-Ressource (akonadi_davgroupware_resource), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [KCrash Handler] #6 0x7fb8822f1fa5 in raise () from /lib64/libc.so.6 #7 0x7fb8822f341b in abort () from /lib64/libc.so.6 #8 0x7fb886119694 in qt_message_output (msgType=optimized out, buf=optimized out) at global/qglobal.cpp:2266 #9 0x7fb88611980f in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7fb886286068 ASSERT: \%s\ in file %s, line %d, ap=0x7fff21f741a8) at global/qglobal.cpp:2312 #10 0x7fb8861199bc in qFatal (msg=optimized out) at global/qglobal.cpp:2495 #11 0x7fb8847b58a8 in Akonadi::CollectionSync::Private::processPendingRemoteNodes (this=0x249c340, _localRoot=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./akonadi/collectionsync.cpp:284 #12 0x7fb8847b8c4c in Akonadi::CollectionSync::Private::execute (this=0x249c340) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./akonadi/collectionsync.cpp:490 #13 0x7fb8847ae63c in localCollectionFetchResult (job=optimized out, this=0x249c340) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./akonadi/collectionsync.cpp:178 #14 Akonadi::CollectionSync::qt_static_metacall (_o=optimized out, _c=optimized out, _id=1, _a=0x7fff21f74920) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49._build/akonadi/collectionsync_p.moc:59 #15 0x7fb886236bc9 in QMetaObject::activate (sender=0x242e530, m=optimized out, local_signal_index=optimized out, argv=0x7fff21f74920) at kernel/qobject.cpp:3547 #16 0x7fb8851cfd12 in KJob::result (this=optimized out, _t1=0x242e530) at /var/tmp/portage/kde-base/kdelibs-4.9.49./work/kdelibs-4.9.49._build/kdecore/kjob.moc:208 #17 0x7fb8851cfd50 in KJob::emitResult (this=0x242e530) at /var/tmp/portage/kde-base/kdelibs-4.9.49./work/kdelibs-4.9.49./kdecore/jobs/kjob.cpp:318 #18 0x7fb88623bd96 in QObject::event (this=0x242e530, e=optimized out) at kernel/qobject.cpp:1195 #19 0x7fb882d577b4 in notify_helper (e=0x2426a50, receiver=0x242e530, this=0x218a130) at kernel/qapplication.cpp:4557 #20 QApplicationPrivate::notify_helper (this=0x218a130, receiver=0x242e530, e=0x2426a50) at kernel/qapplication.cpp:4529 #21 0x7fb882d5c4d1 in QApplication::notify (this=0x7fff21f75330, receiver=0x242e530, e=0x2426a50) at kernel/qapplication.cpp:3939 #22 0x7fb883aa5e56 in KApplication::notify (this=0x7fff21f75330, receiver=0x242e530, event=0x2426a50) at /var/tmp/portage/kde-base/kdelibs-4.9.49./work/kdelibs-4.9.49./kdeui/kernel/kapplication.cpp:311 #23 0x7fb886222f5c in QCoreApplication::notifyInternal (this=0x7fff21f75330, receiver=0x242e530, event=0x2426a50) at kernel/qcoreapplication.cpp:915 #24 0x7fb8862267ba in sendEvent (event=0x2426a50, receiver=0x242e530) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=optimized out, data=0x2161380) at kernel/qcoreapplication.cpp:1539 #26 0x7fb886251763 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236 #27 postEventSourceDispatch (s=optimized out) at kernel/qeventdispatcher_glib.cpp:279 #28 0x7fb881ddc313 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #29 0x7fb881ddc660 in ?? () from /usr/lib64/libglib-2.0.so.0 #30 0x7fb881ddc724 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #31 0x7fb886251b7f in QEventDispatcherGlib::processEvents (this=0x2162be0, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #32 0x7fb882dfa9de in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #33 0x7fb886221ab2 in QEventLoop::processEvents (this=optimized out, flags=...) at
[Bug 310077] Crash of DAV Groupware resource right after wakeup from suspend-to-ram
https://bugs.kde.org/show_bug.cgi?id=310077 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added CC||msch...@gentoo.org -- 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 310077] Crash of DAV Groupware resource right after wakeup from suspend-to-ram
https://bugs.kde.org/show_bug.cgi?id=310077 --- Comment #1 from Marc Schiffbauer msch...@gentoo.org --- Created attachment 75240 -- https://bugs.kde.org/attachment.cgi?id=75240action=edit New crash information added by DrKonqi akonadi_davgroupware_resource (4.9) on KDE Platform 4.9.3 using Qt 4.8.3 - What I was doing when the application crashed: It crashed again when I told Dr. konqi to Start the application again. So this might not only be related to sstem wakeup somehow. -- Backtrace (Reduced): #11 0x7f549887d8a8 in Akonadi::CollectionSync::Private::processPendingRemoteNodes (this=0x19ed5b0, _localRoot=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./akonadi/collectionsync.cpp:284 #12 0x7f5498880c4c in Akonadi::CollectionSync::Private::execute (this=0x19ed5b0) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./akonadi/collectionsync.cpp:490 #13 0x7f549887663c in localCollectionFetchResult (job=optimized out, this=0x19ed5b0) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./akonadi/collectionsync.cpp:178 #14 Akonadi::CollectionSync::qt_static_metacall (_o=optimized out, _c=optimized out, _id=1, _a=0x7fff73a95880) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49._build/akonadi/collectionsync_p.moc:59 [...] #16 0x7f5499297d12 in KJob::result (this=optimized out, _t1=0x1939600) at /var/tmp/portage/kde-base/kdelibs-4.9.49./work/kdelibs-4.9.49._build/kdecore/kjob.moc:208 -- 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 233671] Only syncs one of several google calendars connected to the same account
https://bugs.kde.org/show_bug.cgi?id=233671 --- Comment #21 from Marc Schiffbauer msch...@gentoo.org --- Please, which is now the officail Akonadi Google Resource? Where can I find it? There have been several approaches in the past that tried to implement an akonadi connection to the google services and I am a bit confused now which one you are talking about. Thanks! -- 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 233671] Only syncs one of several google calendars connected to the same account
https://bugs.kde.org/show_bug.cgi?id=233671 --- Comment #23 from Marc Schiffbauer msch...@gentoo.org --- OK, I think a found it. I had not enabled it in my kdepim-resources package. Now enabled. and: amazing! Works like a charm now! Thanks -- 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 298837] kmail does not re-ask for SMTP password if it has been entered wrong
https://bugs.kde.org/show_bug.cgi?id=298837 --- Comment #1 from Marc Schiffbauer msch...@gentoo.org --- Any news on this? Its really a PITA if you mistype your SMTP password when sending a mail. Kmail will keep trying to use th wrong password instead of asking the user again. -Marc -- 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 305248] kmail often crashes when hitting l (lower L) for a list reply
https://bugs.kde.org/show_bug.cgi?id=305248 --- Comment #12 from Marc Schiffbauer msch...@gentoo.org --- Hi Laurent, ok, it does not crash anymore. Great! Is it intened that the To: Header is empty after trying list-reply to this mail? I gues this is because the Follow-Up Header could not be read. How about a warning to the user, that the Header could not be parsed correctly? Or use all addresses that could be read and just strip invalid addresses? -- 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 305248] kmail often crashes when hitting l (lower L) for a list reply
https://bugs.kde.org/show_bug.cgi?id=305248 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #7 from Marc Schiffbauer msch...@gentoo.org --- Today I got the same crash again. IIRC the bug was in pasring of Mail-Followup-To: Header The crash mail from today has a Header in following format: Mail-Followup-To: f...@bar.com, baz@, s...@address.de, anot...@domain.de Please notice the wrong email-Adress in the first line. May that be the cause kmail crashes? -- 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 305248] kmail often crashes when hitting l (lower L) for a list reply
https://bugs.kde.org/show_bug.cgi?id=305248 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added CC||msch...@gentoo.org -- 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 305248] kmail often crashes when hitting l (lower L) for a list reply
https://bugs.kde.org/show_bug.cgi?id=305248 --- Comment #9 from Marc Schiffbauer msch...@gentoo.org --- Created attachment 73568 -- https://bugs.kde.org/attachment.cgi?id=73568action=edit New crash information added by DrKonqi kmail (4.9.1) on KDE Platform 4.9.00 using Qt 4.8.2 Here is the BT for the new crash. DrKonqui thinks its the same bug... -- Backtrace (Reduced): #11 0x7fd58229e928 in MessageCore::StringUtil::mailboxFrom7BitString(QByteArray const) () from /usr/lib64/libmessagecore.so.4 #12 0x7fd581fcbc46 in MessageComposer::MessageFactory::createReply() () from /usr/lib64/libmessagecomposer.so.4 #13 0x7fd587d70dfb in KMReplyCommand::execute (this=0x8e39cd0) at /var/tmp/portage/kde-base/kmail-4.9.49./work/kmail-4.9.49./kmail/kmcommands.cpp:833 #14 0x7fd587d6fd21 in KMCommand::slotPostTransfer (this=0x8e39cd0, result=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.9.49./work/kmail-4.9.49./kmail/kmcommands.cpp:268 [...] #16 0x7fd587d6fa0e in KMCommand::messagesTransfered (this=optimized out, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.9.49./work/kmail-4.9.49._build/kmail/kmcommands.moc:117 -- 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 304389] Message search gives no feedback
https://bugs.kde.org/show_bug.cgi?id=304389 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added CC||msch...@gentoo.org --- Comment #1 from Marc Schiffbauer msch...@gentoo.org --- I can confirm that for current 4.9 branch. I just discovered the same thing. If you search something and no results are in the list you never know if its still searching or not. What I would propose, as soon as the Search Button is pressed: * Disable the search button * Enable the Stop button * Show some animated Progress Icon somewhere (perhaps on the search button?) , perhaps similar to what Firefox shows in a Tab as lonng as a page is loading... -Marc -- 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 305248] New: kmail often crashes when hitting l (lower L) for a list reply
https://bugs.kde.org/show_bug.cgi?id=305248 Bug ID: 305248 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail often crashes when hitting l (lower L) for a list reply Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.9) KDE Platform Version: 4.9.00 (Compiled from sources) Qt Version: 4.8.2 Operating System: Linux 3.5.1-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: It happened reproducable yesterday, then sudenly it worked again. Today after restarting kmail, I wanted to do a list reply, hit l and kaboom. The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f0445807780 (LWP 30410))] Thread 3 (Thread 0x7f0425a94700 (LWP 30414)): #0 0x7f0440857dcc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f043690c38c in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f043690c4b9 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7f0440853ec6 in start_thread () from /lib64/libpthread.so.0 #4 0x7f0442a6b9bd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f0425193700 (LWP 30415)): #0 0x7f0442a62da3 in poll () from /lib64/libc.so.6 #1 0x7f043ac8a456 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f043ac8a584 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f04433f24e6 in QEventDispatcherGlib::processEvents (this=0x7f0428c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f04433c22a2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f04433c24f7 in QEventLoop::exec (this=0x7f0425192e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f04432c2f27 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f04432c5f2b in QThreadPrivate::start (arg=0x1143d50) at thread/qthread_unix.cpp:307 #8 0x7f0440853ec6 in start_thread () from /lib64/libpthread.so.0 #9 0x7f0442a6b9bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f0445807780 (LWP 30410)): [KCrash Handler] #6 0x7f04429bab15 in raise () from /lib64/libc.so.6 #7 0x7f04429bbf8b in abort () from /lib64/libc.so.6 #8 0x7f04432bb6c4 in qt_message_output (msgType=optimized out, buf=optimized out) at global/qglobal.cpp:2260 #9 0x7f04432bb83f in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7f04434269c8 ASSERT: \%s\ in file %s, line %d, ap=0x7fff8ead2d78) at global/qglobal.cpp:2306 #10 0x7f04432bb9ec in qFatal (msg=optimized out) at global/qglobal.cpp:2489 #11 0x7f043ea06827 in MessageCore::StringUtil::mailboxFrom7BitString(QByteArray const) () from /usr/lib64/libmessagecore.so.4 #12 0x7f043e733b96 in MessageComposer::MessageFactory::createReply() () from /usr/lib64/libmessagecomposer.so.4 #13 0x7f0d793b in KMReplyCommand::execute (this=0x13c10160) at /var/tmp/portage/kde-base/kmail-4.9.49./work/kmail-4.9.49./kmail/kmcommands.cpp:833 #14 0x7f0d6861 in KMCommand::slotPostTransfer (this=0x13c10160, result=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.9.49./work/kmail-4.9.49./kmail/kmcommands.cpp:268 #15 0x7f04433d7409 in QMetaObject::activate (sender=0x13c10160, m=optimized out, local_signal_index=optimized out, argv=0x7fff8ead3810) at kernel/qobject.cpp:3547 #16 0x7f0d654e in KMCommand::messagesTransfered (this=optimized out, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kmail-4.9.49./work/kmail-4.9.49._build/kmail/kmcommands.moc:117 #17 0x7f0daad1 in KMCommand::slotJobFinished (this=0x13c10160) at /var/tmp/portage/kde-base/kmail-4.9.49./work/kmail-4.9.49./kmail/kmcommands.cpp:378 #18 0x7f04433d7409 in QMetaObject::activate (sender=0x119d94a0, m=optimized out, local_signal_index=optimized out, argv=0x7fff8ead3a00) at kernel/qobject.cpp:3547 #19 0x7f0444b9ea22 in KJob::result (this=optimized out, _t1=0x119d94a0) at /var/tmp/portage/kde-base/kdelibs-4.9.49./work/kdelibs-4.9.49._build/kdecore/kjob.moc:208 #20 0x7f0444b9ea60 in KJob::emitResult (this=0x119d94a0) at /var/tmp/portage/kde-base/kdelibs-4.9.49./work/kdelibs-4.9.49./kdecore/jobs/kjob.cpp:318 #21 0x7f04433dc5d6 in QObject::event (this=0x119d94a0, e=optimized out) at kernel/qobject.cpp:1195 #22 0x7f04438f46a4 in notify_helper (e=0x14819990, receiver=0x119d94a0, this=0x10b9e10) at kernel/qapplication.cpp:4551 #23 QApplicationPrivate::notify_helper (this=0x10b9e10, receiver=0x119d94a0, e=0x14819990) at
[Bug 303951] imap resource crahes everytime it wants to fetch mail
https://bugs.kde.org/show_bug.cgi?id=303951 --- Comment #4 from Marc Schiffbauer msch...@gentoo.org --- Update: I could isolate the message that is causing the crash. And I have put that message into a seperate folder now (via webmail) The Problem seems to be, that the IMAP resource agent cannot handle (at least) a special IMAP error case. The message has some error on the IMAP side, so the expected behavior of akonadi/kmail would be to display some sort of error like IMAP Message could not be fetched or something like that instead of crashing. I tested with Thunderbird: I just does not show the message. In webmail I can see that there is a message in the folder, but when I click on it to read it I get an error NO_SUCH_BLOB. The IMAP response *seems* to be: No such blob: mailbox=6, item=713444, change=1095509 (according to some details of that error shown in webmail) -- 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 305248] kmail often crashes when hitting l (lower L) for a list reply
https://bugs.kde.org/show_bug.cgi?id=305248 --- Comment #2 from Marc Schiffbauer msch...@gentoo.org --- Yeah seems to be mail specific... just tested again. One one of the mails it always crashes when hitting l -- 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 305248] kmail often crashes when hitting l (lower L) for a list reply
https://bugs.kde.org/show_bug.cgi?id=305248 --- Comment #4 from Marc Schiffbauer msch...@gentoo.org --- I will send you a pm -- 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 303951] imap resource crahes everytime it wants to fetch mail
https://bugs.kde.org/show_bug.cgi?id=303951 --- Comment #3 from Marc Schiffbauer msch...@gentoo.org --- Any news on this? ATM this affects a subfolder which I can easly unsubscribe so that the imap resource agent stops to crash constantly. But I am a bit worried that if that happens to my INBOX it will make kmail completely unusable for me. -- 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 303951] imap resource crahes everytime it wants to fetch mail
https://bugs.kde.org/show_bug.cgi?id=303951 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added Hardware|Compiled Sources|Gentoo Packages Version|4.8 |4.9 --- Comment #1 from Marc Schiffbauer msch...@gentoo.org --- Updated. This crash occurs on 4.9 final as well. Is there any other info I can provide so this annoying bug can be fixed soon? -- 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 303951] imap resource crahes everytime it wants to fetch mail
https://bugs.kde.org/show_bug.cgi?id=303951 --- Comment #2 from Marc Schiffbauer msch...@gentoo.org --- More Info: I found out that the crash always happens when the agent is syncing a specific folder. I tried to unsubscribe that folder (serverside) and voila: No more crashes. After subscribing to it again, syncing that folder started (cache seemed to be cleaned already because the folder was empty now) and after syncing some hundret mails it crashes again. So I assume that I have one special mail object in that folder that makes the agent crash. I tried to narrow this down using the integrated debugger of akonadiconsole, but I cannot find anything about the crash there. -- 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 303951] New: imap resource crahes everytime it wants to fetch mail
https://bugs.kde.org/show_bug.cgi?id=303951 Bug ID: 303951 Severity: crash Version: 4.8 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: imap resource crahes everytime it wants to fetch mail Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.8) KDE Platform Version: 4.8.97 (Compiled from sources) Qt Version: 4.8.2 Operating System: Linux 3.4.4-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: I get a crash every few minutes when the resource tries to get mail (at least is this what I assume...) I have four imap resources configures, this crash seems to happen only with one of them -- Backtrace: Application: MCS vom Typ IMAP-E-Mail-Server (akonadi_imap_resource), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7fe20080e780 (LWP 9729))] Thread 3 (Thread 0x7fe1ed8cb700 (LWP 9732)): #0 0x7fe1fafad418 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fe1faf7347a in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe1faf735b4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe1ffc014e6 in QEventDispatcherGlib::processEvents (this=0x7fe1e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fe1ffbd12a2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fe1ffbd14f7 in QEventLoop::exec (this=0x7fe1ed8cade0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fe1ffad1f27 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7fe1fe822dec in KIMAP::SessionThread::run (this=0x1fbb9b0) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./kimap/sessionthread.cpp:181 #8 0x7fe1ffad4f2b in QThreadPrivate::start (arg=0x1fbb9b0) at thread/qthread_unix.cpp:307 #9 0x7fe1fb8dbec6 in start_thread () from /lib64/libpthread.so.0 #10 0x7fe1fc0369bd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe1ed0ca700 (LWP 9931)): #0 0x7fe1fc02dda3 in poll () from /lib64/libc.so.6 #1 0x7fe1faf73486 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe1faf735b4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe1ffc014e6 in QEventDispatcherGlib::processEvents (this=0x7fe1e00029b0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fe1ffbd12a2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fe1ffbd14f7 in QEventLoop::exec (this=0x7fe1ed0c9de0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fe1ffad1f27 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7fe1fe822dec in KIMAP::SessionThread::run (this=0x200a950) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./kimap/sessionthread.cpp:181 #8 0x7fe1ffad4f2b in QThreadPrivate::start (arg=0x200a950) at thread/qthread_unix.cpp:307 #9 0x7fe1fb8dbec6 in start_thread () from /lib64/libpthread.so.0 #10 0x7fe1fc0369bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fe20080e780 (LWP 9729)): [KCrash Handler] #6 0x7fe1fbf85b15 in raise () from /lib64/libc.so.6 #7 0x7fe1fbf86f8b in abort () from /lib64/libc.so.6 #8 0x7fe1fbf7ebfe in ?? () from /lib64/libc.so.6 #9 0x7fe1fbf7eca2 in __assert_fail () from /lib64/libc.so.6 #10 0x7fe1e58d08f0 in boost::shared_ptrKMime::Message::operator-() const [clone .isra.14] [clone .part.15] () from /usr/lib64/kde4/akonadi_serializer_mail.so #11 0x7fe1e58d767a in Akonadi::SerializerPluginMail::serialize(Akonadi::Item const, QByteArray const, QIODevice, int) () from /usr/lib64/kde4/akonadi_serializer_mail.so #12 0x7fe2002f1b5b in Akonadi::ItemSerializer::serialize (item=..., label=..., data=..., version=@0x71695a9c: 1) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./akonadi/itemserializer.cpp:126 #13 0x7fe2002f1bf9 in Akonadi::ItemSerializer::serialize (item=..., label=..., data=..., version=@0x71695a9c: 1) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./akonadi/itemserializer.cpp:116 #14 0x7fe2002e2f41 in Akonadi::ItemCreateJob::doStart (this=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./akonadi/itemcreatejob.cpp:85 #15 0x7fe2002fde56 in Akonadi::JobPrivate::startQueued (this=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./akonadi/job.cpp:153 #16 0x7fe1ffbeb5d6 in QObject::event (this=0x20ce240, e=optimized out) at kernel/qobject.cpp:1195 #17
[Bug 303687] New: kmail crash after removing IMAP resource
https://bugs.kde.org/show_bug.cgi?id=303687 Bug ID: 303687 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail crash after removing IMAP resource Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.9 rc2) KDE Platform Version: 4.8.97 (Compiled from sources) Qt Version: 4.8.2 Operating System: Linux 3.4.4-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: This crash happend when clicking OK after removing one of my offline IMAP resources -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f8336585780 (LWP 14542))] Thread 3 (Thread 0x7f83167b9700 (LWP 14548)): #0 0x7f83315fadcc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f832766c38c in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f832766c4b9 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7f83315f6ec6 in start_thread () from /lib64/libpthread.so.0 #4 0x7f833380e9bd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f83146b8700 (LWP 14549)): #0 0x7f8333805da3 in poll () from /lib64/libc.so.6 #1 0x7f832b9fc486 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f832b9fc5b4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f83341954e6 in QEventDispatcherGlib::processEvents (this=0x7f830c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f83341652a2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f83341654f7 in QEventLoop::exec (this=0x7f83146b7e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f8334065f27 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f8334068f2b in QThreadPrivate::start (arg=0x19152b0) at thread/qthread_unix.cpp:307 #8 0x7f83315f6ec6 in start_thread () from /lib64/libpthread.so.0 #9 0x7f833380e9bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f8336585780 (LWP 14542)): [KCrash Handler] #6 0x7f833375db15 in raise () from /lib64/libc.so.6 #7 0x7f833375ef8b in abort () from /lib64/libc.so.6 #8 0x7f833405e6c4 in qt_message_output (msgType=optimized out, buf=optimized out) at global/qglobal.cpp:2260 #9 0x7f833405e83f in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7f83341c99c8 ASSERT: \%s\ in file %s, line %d, ap=0x7fff7d9c7508) at global/qglobal.cpp:2306 #10 0x7f833405e9ec in qFatal (msg=optimized out) at global/qglobal.cpp:2489 #11 0x7f832fd1bfdc in Akonadi::CollectionStatisticsDelegate::paint (this=optimized out, painter=0x7fff7d9c8090, option=..., index=...) at /var/tmp/portage/kde-base/kdepimlibs-4.9.49./work/kdepimlibs-4.9.49./akonadi/collectionstatisticsdelegate.cpp:234 #12 0x7f8334bdc7df in QTreeView::drawRow (this=0x15b7120, painter=0x7fff7d9c8090, option=..., index=...) at itemviews/qtreeview.cpp:1717 #13 0x7f8334bdf952 in QTreeView::drawTree (this=0x15b7120, painter=0x7fff7d9c8090, region=...) at itemviews/qtreeview.cpp:1470 #14 0x7f8334be02d0 in QTreeView::paintEvent (this=0x15b7120, event=0x7fff7d9c8dd0) at itemviews/qtreeview.cpp:1275 #15 0x7f83346e7feb in QWidget::event (this=0x15b7120, event=0x7fff7d9c8dd0) at kernel/qwidget.cpp:8517 #16 0x7f8334a84f36 in QFrame::event (this=0x15b7120, e=0x7fff7d9c8dd0) at widgets/qframe.cpp:557 #17 0x7f8334b99a0b in QAbstractItemView::viewportEvent (this=0x15b7120, event=0x7fff7d9c8dd0) at itemviews/qabstractitemview.cpp:1644 #18 0x7f8334be1be5 in QTreeView::viewportEvent (this=0x15b7120, event=0x7fff7d9c8dd0) at itemviews/qtreeview.cpp:1257 #19 0x7f83341668c6 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=optimized out, receiver=0x1323240, event=0x7fff7d9c8dd0) at kernel/qcoreapplication.cpp:1025 #20 0x7f833469766f in notify_helper (e=0x7fff7d9c8dd0, receiver=0x1323240, this=0x129ef80) at kernel/qapplication.cpp:4547 #21 QApplicationPrivate::notify_helper (this=0x129ef80, receiver=0x1323240, e=0x7fff7d9c8dd0) at kernel/qapplication.cpp:4523 #22 0x7f833469c438 in QApplication::notify (this=0x7fff7d9cc580, receiver=0x1323240, e=0x7fff7d9c8dd0) at kernel/qapplication.cpp:4412 #23 0x7f8335f2c36d in KApplication::notify (this=0x7fff7d9cc580, receiver=0x1323240, event=0x7fff7d9c8dd0) at /var/tmp/portage/kde-base/kdelibs-4.9.49./work/kdelibs-4.9.49./kdeui/kernel/kapplication.cpp:311 #24 0x7f833416674c in QCoreApplication::notifyInternal (this=0x7fff7d9cc580, receiver=0x1323240, event=0x7fff7d9c8dd0) at kernel/qcoreapplication.cpp:915 #25 0x7f83346e3c10 in
[Bug 260761] akonadi fails to parse date on some rfc822 messages
https://bugs.kde.org/show_bug.cgi?id=260761 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|FIXED |--- --- Comment #10 from Marc Schiffbauer msch...@gentoo.org --- Thanks for your patch, but this bug is not fixed by that -- 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 297364] kmail2 crash on local unsubscription of some folders
https://bugs.kde.org/show_bug.cgi?id=297364 --- Comment #2 from Marc Schiffbauer msch...@gentoo.org --- Either its fixed or hard to reproduce. But while testing I noticed another bug with local subscriptions: I managed it to have folders locally subscribed but not shown in the folderlist... To reproduce: (with every subscribe / unsubscribe i mean local subscriptions set via RMB menu-local subscriptions) 1. Have a subfolder with some subfolders (here it is lists with one folder for every mailing list), all subscribed (default) 2. unsubscribe only lists, not the subfolders: as expected, lists+subfolders disappear 3. subscribe lists again: ERROR: lists is shown again, but none of the subfolders (but they were checked in subscirbe dialog) to fix this I have to manually uncheck (unsubscribe) all subfolders of lists, hit Apply, then check them again, Apply -- 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 303103] moving mail between imap accounts (dnd): nothing happens
https://bugs.kde.org/show_bug.cgi?id=303103 --- Comment #3 from Marc Schiffbauer msch...@gentoo.org --- Thanks Montel for the update. But there is still no feedback to the user or progress info -- 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 303103] New: moving mail between imap accounts (dnd): nothing happens
https://bugs.kde.org/show_bug.cgi?id=303103 Bug ID: 303103 Severity: normal Version: 4.9 pre Priority: NOR Assignee: kdepim-bugs@kde.org Summary: moving mail between imap accounts (dnd): nothing happens Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Gentoo Packages Status: UNCONFIRMED Component: folders Product: kmail2 I just realized that moving mails between two different imap accounts does not work. You can drag one or more mails and you can drop them over another imap accounts folder. But nothing happens then. If this was a supported feature, ist broken. Ifnot please make kmail show a different mouse pointer over different imap folder so that the user can realise that this is not possible. Reproducible: Always -- 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 303103] moving mail between imap accounts (dnd): nothing happens
https://bugs.kde.org/show_bug.cgi?id=303103 --- Comment #1 from Marc Schiffbauer msch...@gentoo.org --- As it seems now, I was not entirely correct. Akonadi indeed now seems to do something. And after a kmail crash and restart, mails seem to have been partly moved. So the real problem was that there was absolutely no feedback to the user (to me in the UI) that something is actually happening. What I wanted to do was moving all mails from a folder A in IMAP account A to another folder B in IMAP account B. So I marked all mails in folder A and moved them to folder B using dnd. Maybe I tried that two times because there was no feedback. Then I tried to move the whole folder A via dnd from account A to account B. Again no feedback. Now my akonadi database creates a lot of load on my system and kmail shows that the folder seems to have been moved. But its empty. OTOH mails are now appearing in the folder where I moved them to with my first try. So it all seems to work somehow, but giving absolutely no feedback to the user for an action that can take ages if you try to move tons of mail and/or have a slow internet connection seems like a real problem to me. BTW: Keep up the good work! kmail is really evolving and getting more usable! -- 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 302855] New: kmail2 crash while selecting IMAP inbox
https://bugs.kde.org/show_bug.cgi?id=302855 Bug ID: 302855 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail2 crash while selecting IMAP inbox Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.9 rc1) KDE Platform Version: 4.8.95 (4.8.95) (Compiled from sources) Qt Version: 4.8.2 Operating System: Linux 3.4.4-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: This crash happened when I clicked on the inbox of one of my IMAP acounts after starting kmail -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7fdb61fee780 (LWP 5506))] Thread 4 (Thread 0x7fdb42225700 (LWP 5513)): #0 0x7fdb5d05cdcc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdb530dd38c in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7fdb530dd4b9 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7fdb5d058ec6 in start_thread () from /lib64/libpthread.so.0 #4 0x7fdb5f2789bd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fdb41924700 (LWP 5514)): #0 0x7fdb5f26fda3 in poll () from /lib64/libc.so.6 #1 0x7fdb5746d486 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fdb5746d5b4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fdb5fbff4e6 in QEventDispatcherGlib::processEvents (this=0x7fdb3c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fdb5fbcf2a2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fdb5fbcf4f7 in QEventLoop::exec (this=0x7fdb41923e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fdb5facff27 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7fdb5fad2f2b in QThreadPrivate::start (arg=0x1dcdb10) at thread/qthread_unix.cpp:307 #8 0x7fdb5d058ec6 in start_thread () from /lib64/libpthread.so.0 #9 0x7fdb5f2789bd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fdaf9da4700 (LWP 5604)): #0 0x7fdb5d05d14e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fdb5fad338f in wait (time=3, this=0x1eaba50) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x1eac0d8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7fdb5fac682f in QThreadPoolThread::run (this=0x1f83130) at concurrent/qthreadpool.cpp:141 #4 0x7fdb5fad2f2b in QThreadPrivate::start (arg=0x1f83130) at thread/qthread_unix.cpp:307 #5 0x7fdb5d058ec6 in start_thread () from /lib64/libpthread.so.0 #6 0x7fdb5f2789bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fdb61fee780 (LWP 5506)): [KCrash Handler] #6 0x7fdb5f1c7b15 in raise () from /lib64/libc.so.6 #7 0x7fdb5f1c8f8b in abort () from /lib64/libc.so.6 #8 0x7fdb5fac86c4 in qt_message_output (msgType=optimized out, buf=optimized out) at global/qglobal.cpp:2260 #9 0x7fdb5fac883f in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7fdb5fc339c8 ASSERT: \%s\ in file %s, line %d, ap=0x7fff277477f8) at global/qglobal.cpp:2306 #10 0x7fdb5fac89ec in qFatal (msg=optimized out) at global/qglobal.cpp:2489 #11 0x7fdb619564a2 in KIdentityProxyModel::mapSelectionToSource (this=0x1d29190, selection=...) at /var/tmp/portage/kde-base/kdelibs-4.9.49./work/kdelibs-4.9.49./kdeui/itemviews/kidentityproxymodel.cpp:272 #12 0x7fdb5ac7eb3b in MessageList::Pane::Private::mapSelectionToSource(QItemSelection const) const () from /usr/lib64/libmessagelist.so.4 #13 0x7fdb5ac7ec3b in MessageList::Pane::Private::onSelectionChanged(QItemSelection const, QItemSelection const) () from /usr/lib64/libmessagelist.so.4 #14 0x7fdb5fbe4409 in QMetaObject::activate (sender=0x17bac30, m=optimized out, local_signal_index=optimized out, argv=0x7fff27747e60) at kernel/qobject.cpp:3547 #15 0x7fdb6065c217 in QItemSelectionModel::selectionChanged (this=optimized out, _t1=..., _t2=...) at .moc/release-shared/moc_qitemselectionmodel.cpp:166 #16 0x7fdb60661fe4 in QItemSelectionModel::emitSelectionChanged (this=0x17bac30, newSelection=..., oldSelection=...) at itemviews/qitemselectionmodel.cpp:1544 #17 0x7fdb60662f61 in QItemSelectionModel::select (this=0x17bac30, selection=..., command=...) at itemviews/qitemselectionmodel.cpp:1110 #18 0x7fdb6064d603 in QTreeViewPrivate::select (this=0x1d06e70, topIndex=..., bottomIndex=..., command=...) at itemviews/qtreeview.cpp:3704 #19 0x7fdb6064e352 in QTreeView::setSelection (this=optimized out, rect=..., command=...) at
[Bug 302303] kmail2-4.8.90 does not restore custom email account order on startup
https://bugs.kde.org/show_bug.cgi?id=302303 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Marc Schiffbauer msch...@gentoo.org --- Since RC1 ist working her fine now too. So I will close this bug as it seems to be fixed already. -- 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 302303] New: kmail2-4.8.90 does not restore custom email account order on startup
https://bugs.kde.org/show_bug.cgi?id=302303 Bug ID: 302303 Severity: normal Version: 4.9 pre Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail2-4.8.90 does not restore custom email account order on startup Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Gentoo Packages Status: UNCONFIRMED Component: folders Product: kmail2 In kmail settings, account setup, you can choose a custom order in which the various email accounts appear in the folderlist. After setting this and hitting OK this works fine. However if you restart kmail, the old, original account order is in place again. This does NOT seem as a config issue, it seems kmail just does not read that setting on startup because if you enter the config dialog again and hit OK without changing anything, custom reordering will happen immediately to the order I have configured previously. Reproducible: Always Steps to Reproduce: 1. Have several email accounts 2. change order, hit OK - check that order is now different 4. restart kmail - order is in original state again 6. enter config dialog again, hit OK - account orderis changed again to desired setting Actual Results: Wrong account order on startup Expected Results: Configured order of accounts on startup -- 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 301629] New: akonadi_imap_resource crashed after aborting connect in ssl-cert dialog
https://bugs.kde.org/show_bug.cgi?id=301629 Bug ID: 301629 Severity: crash Version: 4.8 Priority: NOR CC: kdepim-bugs@kde.org, vkra...@kde.org Assignee: er...@kde.org Summary: akonadi_imap_resource crashed after aborting connect in ssl-cert dialog Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: IMAP resource Product: Akonadi Application: akonadi_imap_resource (4.8) KDE Platform Version: 4.8.90 (4.8.90) (Compiled from sources) Qt Version: 4.8.2 Operating System: Linux 3.3.8-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: A dialog popped up warning me about an invalid ssl-cert for the IMAP connection. I aborted this by clicking the Abort button. Then this crash occured -- Backtrace: Application: MCS vom Typ IMAP-E-Mail-Server (akonadi_imap_resource), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f05c3631780 (LWP 10190))] Thread 2 (Thread 0x7f05a9348700 (LWP 11242)): #0 0x7f05beebbda3 in poll () from /lib64/libc.so.6 #1 0x7f05bde01486 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f05bde015b4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f05c2a504e6 in QEventDispatcherGlib::processEvents (this=0x7f059c001b70, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f05c2a202a2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f05c2a204f7 in QEventLoop::exec (this=0x7f05a9347de0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f05c2920f27 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f05c1670dbc in KIMAP::SessionThread::run (this=0xf84be0) at /var/tmp/portage/kde-base/kdepimlibs-4.8.90/work/kdepimlibs-4.8.90/kimap/sessionthread.cpp:181 #8 0x7f05c2923f2b in QThreadPrivate::start (arg=0xf84be0) at thread/qthread_unix.cpp:307 #9 0x7f05be524ec6 in start_thread () from /lib64/libpthread.so.0 #10 0x7f05beec49bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f05c3631780 (LWP 10190)): [KCrash Handler] #6 0x7f05bee13b15 in raise () from /lib64/libc.so.6 #7 0x7f05bee14f8b in abort () from /lib64/libc.so.6 #8 0x7f05c29196c4 in qt_message_output (msgType=optimized out, buf=optimized out) at global/qglobal.cpp:2260 #9 0x7f05c291983f in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7f05c2a849c8 ASSERT: \%s\ in file %s, line %d, ap=0x7fffcb2fb458) at global/qglobal.cpp:2306 #10 0x7f05c29199ec in qFatal (msg=optimized out) at global/qglobal.cpp:2489 #11 0x7f05c166da82 in KIMAP::SessionPrivate::jobDone (this=0xf89170, job=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.8.90/work/kdepimlibs-4.8.90/kimap/session.cpp:176 #12 0x7f05c2a35409 in QMetaObject::activate (sender=0xd0c090, m=optimized out, local_signal_index=optimized out, argv=0x7fffcb2fb6a0) at kernel/qobject.cpp:3547 #13 0x7f05bf7dcf92 in KJob::result (this=optimized out, _t1=0xd0c090) at /var/tmp/portage/kde-base/kdelibs-4.8.90/work/kdelibs-4.8.90_build/kdecore/kjob.moc:208 #14 0x7f05bf7dcfd5 in KJob::emitResult (this=0xd0c090) at /var/tmp/portage/kde-base/kdelibs-4.8.90/work/kdelibs-4.8.90/kdecore/jobs/kjob.cpp:318 #15 0x7f05c1666837 in KIMAP::LoginJobPrivate::sslResponse (this=0xd0ae70, response=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.8.90/work/kdepimlibs-4.8.90/kimap/loginjob.cpp:507 #16 0x7f05c2a35409 in QMetaObject::activate (sender=0xf89170, m=optimized out, local_signal_index=optimized out, argv=0x7fffcb2fb870) at kernel/qobject.cpp:3547 #17 0x7f05c166d82f in KIMAP::SessionPrivate::encryptionNegotiationResult (this=optimized out, _t1=false) at /var/tmp/portage/kde-base/kdepimlibs-4.8.90/work/kdepimlibs-4.8.90_build/kimap/session_p.moc:108 #18 0x7f05c2a3a5d6 in QObject::event (this=0xf89170, e=optimized out) at kernel/qobject.cpp:1195 #19 0x7f05c1dce6a4 in notify_helper (e=0x7f059c022f50, receiver=0xf89170, this=0xa271b0) at kernel/qapplication.cpp:4551 #20 QApplicationPrivate::notify_helper (this=0xa271b0, receiver=0xf89170, e=0x7f059c022f50) at kernel/qapplication.cpp:4523 #21 0x7f05c1dd33c1 in QApplication::notify (this=0x7fffcb2fe2d0, receiver=0xf89170, e=0x7f059c022f50) at kernel/qapplication.cpp:3933 #22 0x7f05bfdf57ed in KApplication::notify (this=0x7fffcb2fe2d0, receiver=0xf89170, event=0x7f059c022f50) at /var/tmp/portage/kde-base/kdelibs-4.8.90/work/kdelibs-4.8.90/kdeui/kernel/kapplication.cpp:311 #23 0x7f05c2a2174c in QCoreApplication::notifyInternal (this=0x7fffcb2fe2d0, receiver=0xf89170, event=0x7f059c022f50) at kernel/qcoreapplication.cpp:915 #24
[Bug 260761] akonadi fails to parse date on some rfc822 messages
https://bugs.kde.org/show_bug.cgi?id=260761 --- Comment #6 from Marc Schiffbauer msch...@gentoo.org --- Hi Volker, I just had a look at RFC 5322. Having GMT as Timezone in the Date Header is supported but deprecated. However, those mails I am having Problems with seem to be created by some mail software where they misunderstood the RFC a little bit. ( http://tools.ietf.org/html/rfc5322#page-33 ) The RFC talks about GMT but the double uotes are not part of the real String that can be used. E.g. it should be written as GMT and not GMT. So the example mail is indeed not 100% RFC compatible. However: I really think this kind of header should nevertheless be parsed as expected because real world shows that there *are* mails like this in the peoples mailboxes. So please accept some RFC 5322 obs-zone (with double quotes) as well as without (which should already be the case) *And* mutt for example does not have a problem with those mails... -Marc -- 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 260761] akonadi fails to parse date on some rfc822 messages
https://bugs.kde.org/show_bug.cgi?id=260761 --- Comment #4 from Marc Schiffbauer msch...@gentoo.org --- This bug is still present (4.8.3+ (current 4.8 git branch, akonadi 1.7.2) -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 260761] akonadi fails to parse date on some rfc822 messages
https://bugs.kde.org/show_bug.cgi?id=260761 --- Comment #5 from Marc Schiffbauer msch...@gentoo.org --- Additional note: when kmail is configured to jump to the newest message when selecting a folder it will fail on folders which contain messages with dates that akonadi cannot handle properly and jump to some of those messages with an Unknown date instead (which are listed at the very end of the list). -- 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 277705] KMail 2 crashes if I want to set the message pane to the right
https://bugs.kde.org/show_bug.cgi?id=277705 --- Comment #14 from Marc Schiffbauer msch...@gentoo.org --- Yes please put bt Thanks I only can reproduce the nepomuk feeder crash atm. (Bug 299357) Steps to reproduce: 1. akonadictl stop (wait until 'akonadictl status' tells that its stopped) 2. enable nepomuk 3. akonadictl start - crash -- 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 277705] KMail 2 crashes if I want to set the message pane to the right
https://bugs.kde.org/show_bug.cgi?id=277705 --- Comment #10 from Marc Schiffbauer msch...@gentoo.org --- (In reply to comment #7) ?? do you see this bactrace do you see nepomuk here Please report on good bug report, and not just read it's crash ok it's same for me it's crash. So no nepomuk is not related to this crash. Hi Laurent, Its true that there is nothing about nepomuk in the BT. But it is also true, that this crash only occurs if nepomuk is enabled. BTW: Enabling nepomuk also make akonadi nepomuk feeder and akonadi mail agent crash immediately. Are you interested in those BTs as well? Thanks -Marc -- 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 277705] KMail 2 crashes if I want to set the message pane to the right
https://bugs.kde.org/show_bug.cgi?id=277705 --- Comment #6 from Marc Schiffbauer msch...@gentoo.org --- Confirmed. Disabling nepomuk in systemsettings and killing all nepomuk* processes make me able to use kmail again (current 4.8 branch). Thanks for the hint! -- 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 299355] crash right after starting kmail
https://bugs.kde.org/show_bug.cgi?id=299355 --- Comment #3 from Marc Schiffbauer msch...@gentoo.org --- Hm I did not set something like described in bug 277705, at least I did not change the setting. But I cannot check the current setting as kmail will crash immediately after start. Sure its a duplicate? Is there any workaround so I can use kmail again in any way? -- 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 299355] crash right after starting kmail
https://bugs.kde.org/show_bug.cgi?id=299355 --- Comment #1 from Marc Schiffbauer msch...@gentoo.org --- Update: The crash appears as soon as kmail tries to display a message. Any Idea what I can do about it? -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 282694] crash when removing local folder
https://bugs.kde.org/show_bug.cgi?id=282694 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added CC||msch...@gentoo.org -- 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 282694] crash when removing local folder
https://bugs.kde.org/show_bug.cgi?id=282694 --- Comment #4 from Marc Schiffbauer msch...@gentoo.org --- Created attachment 70919 -- https://bugs.kde.org/attachment.cgi?id=70919action=edit New crash information added by DrKonqi akonadi_maildispatcher_agent (4.8) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1 - What I was doing when the application crashed: I have exactly the same problem here with 4.8.3+ while trying to debug why my kamil always crashes right after startingn it -- Backtrace (Reduced): #11 0x7f8cf714aaf4 in Akonadi::SpecialCollectionsRequestJobPrivate::resourceScanResult (this=0x2215f90, job=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.8.49./work/kdepimlibs-4.8.49./akonadi/specialcollectionsrequestjob.cpp:203 [...] #13 0x7f8cf6276a72 in KJob::result (this=optimized out, _t1=0x21fd930) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49._build/kdecore/kjob.moc:208 #14 0x7f8cf6276ab5 in KJob::emitResult (this=0x21fd930) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49./kdecore/jobs/kjob.cpp:318 #15 0x7f8cf71458a8 in Akonadi::ResourceScanJob::Private::fetchResult (this=0x21c34c0, job=optimized out) at /var/tmp/portage/kde-base/kdepimlibs-4.8.49./work/kdepimlibs-4.8.49./akonadi/specialcollectionshelperjobs.cpp:150 [...] #17 0x7f8cf6276a72 in KJob::result (this=optimized out, _t1=0x223e050) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49._build/kdecore/kjob.moc:208 -- 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 299355] New: crash right after starting kmail
https://bugs.kde.org/show_bug.cgi?id=299355 Bug ID: 299355 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: crash right after starting kmail Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) (Compiled from sources) Qt Version: 4.8.1 Operating System: Linux 3.3.3-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: I selected the INBOX of one of my IMAP accounts, then kmail crashed. Since then I cannot use kmail anymore because it crashes right after startup this the attached BT. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7faf5ecf7780 (LWP 15946))] Thread 5 (Thread 0x7faf3f20b700 (LWP 15951)): #0 0x7faf59d77dcc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7faf5069ca6c in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7faf5069cb99 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7faf59d73ec6 in start_thread () from /lib64/libpthread.so.0 #4 0x7faf5bf9c9bd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7faf3e90a700 (LWP 15952)): #0 0x7faf5bf93da3 in poll () from /lib64/libc.so.6 #1 0x7faf543e43c6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7faf543e44f4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7faf5c923b56 in QEventDispatcherGlib::processEvents (this=0x7faf380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7faf5c8f3c32 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7faf5c8f3e87 in QEventLoop::exec (this=0x7faf3e909e00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7faf5c7f3e97 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7faf5c7f6e9b in QThreadPrivate::start (arg=0x1be6ab0) at thread/qthread_unix.cpp:298 #8 0x7faf59d73ec6 in start_thread () from /lib64/libpthread.so.0 #9 0x7faf5bf9c9bd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7faf3d46a700 (LWP 15953)): #0 0x7faf59d7814e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7faf5c7f72ff in wait (time=3, this=0x1c69f90) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x1c762e8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7faf5c7ea79f in QThreadPoolThread::run (this=0x1c99d80) at concurrent/qthreadpool.cpp:141 #4 0x7faf5c7f6e9b in QThreadPrivate::start (arg=0x1c99d80) at thread/qthread_unix.cpp:298 #5 0x7faf59d73ec6 in start_thread () from /lib64/libpthread.so.0 #6 0x7faf5bf9c9bd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7faf3ca31700 (LWP 15957)): #0 0x7faf59d7814e in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7faf5c7f72ff in wait (time=3, this=0x21ba800) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x1bbe088, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7faf5c7ea79f in QThreadPoolThread::run (this=0x21cd3f0) at concurrent/qthreadpool.cpp:141 #4 0x7faf5c7f6e9b in QThreadPrivate::start (arg=0x21cd3f0) at thread/qthread_unix.cpp:298 #5 0x7faf59d73ec6 in start_thread () from /lib64/libpthread.so.0 #6 0x7faf5bf9c9bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7faf5ecf7780 (LWP 15946)): [KCrash Handler] #6 QBasicAtomicInt::deref (this=0x7faf4dfe2a18) at /usr/include/qt4/QtCore/qatomic_x86_64.h:133 #7 0x7faf5e0db135 in KSharedPtrKTraderParse::ParseTreeBase::~KSharedPtr (this=0x1b92260, __in_chrg=optimized out) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49./kdecore/util/ksharedptr.h:90 #8 0x7faf5e0dbb5e in qThreadStorage_deleteDataKTraderParse::ParsingData (d=0x1b92260) at /usr/include/qt4/QtCore/qthreadstorage.h:97 #9 0x7faf5c7f4e8c in QThreadStorageData::set (this=0x22bee30, p=0x22bfd50) at thread/qthreadstorage.cpp:165 #10 0x7faf5e0db9ed in KTraderParse::parseConstraints (_constr=...) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49./kdecore/services/ktraderparse.cpp:55 #11 0x7faf5e0daddb in KServiceTypeTrader::applyConstraints (lst=..., constraint=...) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49./kdecore/services/kservicetypetrader.cpp:59 #12 0x7faf5e0daf51 in KServiceTypeTrader::defaultOffers (this=optimized out, serviceType=..., constraint=...) at
[Bug 299357] New: nepomuk_feeder crash after starting akonadi
https://bugs.kde.org/show_bug.cgi?id=299357 Bug ID: 299357 Severity: crash Version: 4.8 Priority: NOR CC: vkra...@kde.org Assignee: kdepim-bugs@kde.org Summary: nepomuk_feeder crash after starting akonadi Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: Nepomuk Feeder Agents Product: Akonadi Application: akonadi_nepomuk_feeder (4.8) KDE Platform Version: 4.8.3 (4.8.3) (Compiled from sources) Qt Version: 4.8.1 Operating System: Linux 3.3.3-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: This crash happened right after login and culd be reproduced by starting akonadi via akonadictl start after stopping it via akonadictl stop -- Backtrace: Application: Akonadi Nepomuk Feeder (akonadi_nepomuk_feeder), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [KCrash Handler] #6 0x in ?? () #7 0x7f045a640f14 in KMimeTypeFactory::entryOffset (this=0x7f04540fca10, mimeTypeName=...) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49./kdecore/services/kmimetypefactory.cpp:50 #8 0x7f045a64290d in mimeTypeSycocaServiceOffers (mimeType=...) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49./kdecore/services/kmimetypetrader.cpp:79 #9 0x7f045a642e2c in KMimeTypeTrader::query (this=optimized out, mimeType=..., genericServiceType=..., constraint=...) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49./kdecore/services/kmimetypetrader.cpp:147 #10 0x0040c99e in FeederPluginloader::feederPluginsForMimeType (this=0x627830, mimetype=...) at /var/tmp/portage/kde-base/kdepim-runtime-4.8.49./work/kdepim-runtime-4.8.49./agents/nepomukfeeder/pluginloader.cpp:34 #11 0x0040a465 in Akonadi::indexingDisabled (collection=...) at /var/tmp/portage/kde-base/kdepim-runtime-4.8.49./work/kdepim-runtime-4.8.49./agents/nepomukfeeder/nepomukfeederagent.cpp:76 #12 0x0040a86b in Akonadi::NepomukFeederAgent::itemChanged (this=0x994650, item=..., partIdentifiers=...) at /var/tmp/portage/kde-base/kdepim-runtime-4.8.49./work/kdepim-runtime-4.8.49./agents/nepomukfeeder/nepomukfeederagent.cpp:150 #13 0x7f0459d0ea79 in QMetaObject::activate (sender=0x90f290, m=optimized out, local_signal_index=optimized out, argv=0x7fff0f32e990) at kernel/qobject.cpp:3547 #14 0x7f045a18dbb7 in Akonadi::Monitor::itemChanged (this=optimized out, _t1=..., _t2=...) at /var/tmp/portage/kde-base/kdepimlibs-4.8.49./work/kdepimlibs-4.8.49._build/akonadi/monitor.moc:189 #15 0x7f045a1917fc in Akonadi::MonitorPrivate::emitItemNotification (this=0x992380, msg=..., item=..., collection=..., collectionDest=...) at /var/tmp/portage/kde-base/kdepimlibs-4.8.49./work/kdepimlibs-4.8.49./akonadi/monitor_p.cpp:525 #16 0x7f045a1928c2 in Akonadi::MonitorPrivate::emitNotification (this=0x992380, msg=...) at /var/tmp/portage/kde-base/kdepimlibs-4.8.49./work/kdepimlibs-4.8.49./akonadi/monitor_p.cpp:288 #17 0x7f045a10f8c1 in Akonadi::ChangeRecorderPrivate::emitNotification (this=0x992380, msg=...) at /var/tmp/portage/kde-base/kdepimlibs-4.8.49./work/kdepimlibs-4.8.49./akonadi/changerecorder_p.h:60 #18 0x7f045a19228d in Akonadi::MonitorPrivate::flushPipeline (this=0x992380) at /var/tmp/portage/kde-base/kdepimlibs-4.8.49./work/kdepimlibs-4.8.49./akonadi/monitor_p.cpp:429 #19 0x7f045a1922e9 in Akonadi::MonitorPrivate::dataAvailable (this=0x992380) at /var/tmp/portage/kde-base/kdepimlibs-4.8.49./work/kdepimlibs-4.8.49./akonadi/monitor_p.cpp:438 #20 0x7f0459d0ea79 in QMetaObject::activate (sender=0x956c10, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547 #21 0x7f045a11461b in Akonadi::EntityCacheAkonadi::Item, Akonadi::ItemFetchJob, Akonadi::ItemFetchScope::processResult (this=0x956c10, job=0x9c8fd0) at /var/tmp/portage/kde-base/kdepimlibs-4.8.49./work/kdepimlibs-4.8.49./akonadi/entitycache_p.h:192 #22 0x7f0459d0ea79 in QMetaObject::activate (sender=0x9c8fd0, m=optimized out, local_signal_index=optimized out, argv=0x7fff0f32f0e0) at kernel/qobject.cpp:3547 #23 0x7f045a618a72 in KJob::result (this=optimized out, _t1=0x9c8fd0) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49._build/kdecore/kjob.moc:208 #24 0x7f045a618ab5 in KJob::emitResult (this=0x9c8fd0) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49./kdecore/jobs/kjob.cpp:318 #25 0x7f0459d13c46 in QObject::event (this=0x9c8fd0, e=optimized out) at kernel/qobject.cpp:1195 #26 0x7f04579047c4 in notify_helper (e=0xa3cba0, receiver=0x9c8fd0, this=0x7c7560) at
[Bug 298349] kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?)
https://bugs.kde.org/show_bug.cgi?id=298349 --- Comment #8 from Marc Schiffbauer msch...@gentoo.org --- (In reply to comment #7) in KMail settings, composer, charset.. is Keep original charset ... checked ? Try to uncheck it. I unchecked it. Now it looks correct! Thanks! But: Should we nevertheless consider that a bug? Because when viewing the original mail all looks correct. Only the composer does something to the text that is not entirely correct when this setting is enabled. Or: Why should someone enable that setting? Should it perhaps be removed? -- 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 298837] New: kmail does not re-ask for SMTP password if it has been entered wrong
https://bugs.kde.org/show_bug.cgi?id=298837 Bug ID: 298837 Severity: normal Version: Git (master) Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail does not re-ask for SMTP password if it has been entered wrong Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Other Status: UNCONFIRMED Component: general Product: kmail2 When sending a mail the first time after akonadi/kmail startup I get asked to enter my SMTP password. When I enter the wrong password, sending the message of cource fails. But instead of asking me again for another password, kmail tries again and again with the first password and keeps telling me that the SMTP server would not support PLAIN Auth, which ir wrong. (I use PLAIN Auth via SSL on submission port 587) Reproducible: Always Steps to Reproduce: 1. Have a SMTP Server that requires auth and supports PLAIN auth via submission port 587 using SSL (mayb that error happens with other setups as well, I didi not test) 2. Send a mail so that you will be asked for the password 3. enter a wrong password, you will noct be asked again Actual Results: kmail keeps trying to send the mail using wrong password Expected Results: should correctly detect that the password was wrong and ask the user again. What is a bit strange here for some time now, which I should mention: I have enabled Save password anywhere so kmail/akonadi should remember my SMTP password in kwallet, but in fact it will always ask me the first time after akonadi startup. This is not the case for my IMAP resources, there it always uses the saved password... -- 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 298349] kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?)
https://bugs.kde.org/show_bug.cgi?id=298349 --- Comment #2 from Marc Schiffbauer msch...@gentoo.org --- Created attachment 70646 -- https://bugs.kde.org/attachment.cgi?id=70646action=edit Example email Hello Laurent, please see attached mbox File. I had to anonymize the text. Open with Ctrl-O - Looks correct Hit r to reply: garbled non-ascii chars Thanks for your hard work on kmail! -Marc -- 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 298349] kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?)
https://bugs.kde.org/show_bug.cgi?id=298349 --- Comment #4 from Marc Schiffbauer msch...@gentoo.org --- Created attachment 70647 -- https://bugs.kde.org/attachment.cgi?id=70647action=edit Screenshot showing garbled chars in editor. Hi Laurent, I have the exactly same charset settings. here is a screenshot. What else can I provide? -Marc -- 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 298349] kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?)
https://bugs.kde.org/show_bug.cgi?id=298349 --- Comment #6 from Marc Schiffbauer msch...@gentoo.org --- Thanks! I hope you can find something that may cause this. I don't know whether this is relevant, my locale: LANG=de_DE.UTF-8 LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= -- 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 298336] New: kmail2: crash while moving folder
https://bugs.kde.org/show_bug.cgi?id=298336 Bug ID: 298336 Severity: crash Version: 4.8.2 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail2: crash while moving folder Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) (Compiled from sources) Qt Version: 4.8.1 Operating System: Linux 3.3.0-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: I was using kmail2 (not kontact) and wanted to move two folders into a subfolder (via DnD). One after another. The first worked. And after dropping the second folder over the destination subfolder, kmail crashed. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7fe3fd1497a0 (LWP 10613))] Thread 6 (Thread 0x7fe3dd6f9700 (LWP 10619)): #0 0x7fe3f81ccfdc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe3eeb63a6c in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7fe3eeb63b99 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7fe3f81c8e1c in start_thread () from /lib64/libpthread.so.0 #4 0x7fe3fa3f15ad in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fe3dcdf8700 (LWP 10620)): #0 0x7fe3f81cc18d in pthread_mutex_unlock () from /lib64/libpthread.so.0 #1 0x7fe3f28e52b1 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe3f28aa4a8 in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe3f28ab294 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe3f28ab4f4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fe3fad76b56 in QEventDispatcherGlib::processEvents (this=0x2c40d70, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7fe3fad46c32 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #7 0x7fe3fad46e87 in QEventLoop::exec (this=0x7fe3dcdf7de0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7fe3fac46e97 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #9 0x7fe3fac49e9b in QThreadPrivate::start (arg=0x2c406f0) at thread/qthread_unix.cpp:298 #10 0x7fe3f81c8e1c in start_thread () from /lib64/libpthread.so.0 #11 0x7fe3fa3f15ad in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fe3918b4700 (LWP 11138)): #0 0x7fe3fa3e7f43 in poll () from /lib64/libc.so.6 #1 0x7fe3f28ab3c6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe3f28ab4f4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe3fad76b56 in QEventDispatcherGlib::processEvents (this=0x2fc8a70, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fe3fad46c32 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fe3fad46e87 in QEventLoop::exec (this=0x7fe3918b3db0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fe3fac46e97 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7fe3fad26bef in QInotifyFileSystemWatcherEngine::run (this=0x5241ea0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fe3fac49e9b in QThreadPrivate::start (arg=0x5241ea0) at thread/qthread_unix.cpp:298 #9 0x7fe3f81c8e1c in start_thread () from /lib64/libpthread.so.0 #10 0x7fe3fa3f15ad in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fe37e9c9700 (LWP 11509)): #0 0x7fe3f81cd35b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe3fac4a2ff in wait (time=3, this=0x2cd01e0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x2cd0188, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7fe3fac3d79f in QThreadPoolThread::run (this=0x2cf3e00) at concurrent/qthreadpool.cpp:141 #4 0x7fe3fac49e9b in QThreadPrivate::start (arg=0x2cf3e00) at thread/qthread_unix.cpp:298 #5 0x7fe3f81c8e1c in start_thread () from /lib64/libpthread.so.0 #6 0x7fe3fa3f15ad in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe3842d7700 (LWP 11511)): #0 0x7fe3f81cd35b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe3fac4a2ff in wait (time=3, this=0x3569310) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x3569288, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7fe3fac3d79f in QThreadPoolThread::run (this=0x356a2c0) at concurrent/qthreadpool.cpp:141 #4 0x7fe3fac49e9b in QThreadPrivate::start (arg=0x356a2c0) at thread/qthread_unix.cpp:298 #5 0x7fe3f81c8e1c in start_thread () from /lib64/libpthread.so.0 #6 0x7fe3fa3f15ad in clone () from /lib64/libc.so.6
[Bug 298349] New: kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?)
https://bugs.kde.org/show_bug.cgi?id=298349 Bug ID: 298349 Severity: major Version: Git (master) Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?) Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Gentoo Packages Status: UNCONFIRMED Component: composer Product: kmail2 Hi, this bug has been there in the past and something about it has been fixed. I do not know any bug number, sorry. While this is working most ogf the time time, I just got an email where it still does NOT work. Displaying that email works quite fine for that particular email, but when I hit the reply button, all text that is transferred to the composer as quote is decoded twice or sowmthing like that producing strings like ä for a german a-umlaut (ä) for example. I had a quick look at the mail headers like Content-Type: and the Content-Type of the mime parts. It seems like kmail (-composer?) fails at understanding/decoding special crafted (nested?) mime attachements . I have compared a working mail and a non working mail, which both are quite similar and noticed the following differences: WORKING mail: Header: Content-Type: multipart/mixed; boundary=090808080701020801080608 Body: This is a multi-part message in MIME format. --090808080701020801080608 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable some umlaut: =C3=BC --090808080701020801080608 FAILING mail: === Header: Content-Type: multipart/mixed; boundary4151591153882929492== Body: --===4151591153882929492== Content-Type: multipart/alternative; boundary=GMXBoundary37091334746530755927 --GMXBoundary37091334746530755927 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable some umlaut: =C3=BC --GMXBoundary37091334746530755927 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable spansome umlaut: =C3=BC/span --GMXBoundary37091334746530755927-- --===4151591153882929492== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline some footer --===4151591153882929492==-- Reproducible: Always Actual Results: Non-ascii chars in editor are presented like =C3=BC instead of ä for example for some mails Expected Results: Non-ascii chars in editor are presented like ä properly mutt does it all right -- 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 297364] New: kmail2 crash on local unsubscription of some folders
https://bugs.kde.org/show_bug.cgi?id=297364 Bug ID: 297364 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail2 crash on local unsubscription of some folders Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Compiled Sources Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.2) KDE Platform Version: 4.8.2 (4.8.2) (Compiled from sources) Qt Version: 4.8.1 Operating System: Linux 3.3.0-gentoo x86_64 Distribution: NAME=Gentoo -- Information about the crash: - What I was doing when the application crashed: I did: * right click an imap folder and chose local subscription * situation was: several IMAP folders with child-folders, parent was already locally unsubscribed while children were not * also unchecked child-folders now * click on OK button - crash -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f716653c7a0 (LWP 5825))] Thread 4 (Thread 0x7f71466df700 (LWP 5845)): #0 0x7f71615c0fdc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f7157d50c4c in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7f7157d50d79 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7f71615bce1c in start_thread () from /lib64/libpthread.so.0 #4 0x7f71637e568d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f7145dde700 (LWP 5846)): #0 0x7f71637dc023 in poll () from /lib64/libc.so.6 #1 0x7f715bc9a598 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f715bc9aa49 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f716416ac46 in QEventDispatcherGlib::processEvents (this=0x12fbea0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f716413acb2 in QEventLoop::processEvents (this=optimized out, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f716413af07 in QEventLoop::exec (this=0x7f7145e0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f716403af47 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f716403df4b in QThreadPrivate::start (arg=0x12fba20) at thread/qthread_unix.cpp:298 #8 0x7f71615bce1c in start_thread () from /lib64/libpthread.so.0 #9 0x7f71637e568d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f70ff7db700 (LWP 9629)): #0 0x7f71615c135b in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f716403e3af in wait (time=3, this=0x1374680) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=optimized out, mutex=0x1380ef8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7f716403184f in QThreadPoolThread::run (this=0x13a4b30) at concurrent/qthreadpool.cpp:141 #4 0x7f716403df4b in QThreadPrivate::start (arg=0x13a4b30) at thread/qthread_unix.cpp:298 #5 0x7f71615bce1c in start_thread () from /lib64/libpthread.so.0 #6 0x7f71637e568d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f716653c7a0 (LWP 5825)): [KCrash Handler] #6 0x7f71637363b5 in raise () from /lib64/libc.so.6 #7 0x7f7163737cd3 in abort () from /lib64/libc.so.6 #8 0x7f71640336e4 in qt_message_output (msgType=optimized out, buf=optimized out) at global/qglobal.cpp:2252 #9 0x7f716403385f in qt_message(QtMsgType, const char *, typedef __va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7f716419f0e8 ASSERT: \%s\ in file %s, line %d, ap=0x7fffab66d4f8) at global/qglobal.cpp:2298 #10 0x7f7164033a0c in qFatal (msg=optimized out) at global/qglobal.cpp:2481 #11 0x7f7165edba9e in KSelectionProxyModelPrivate::selectionChanged (this=0x6dd73e0, _selected=..., _deselected=...) at /var/tmp/portage/kde-base/kdelibs-4.8.49./work/kdelibs-4.8.49./kdeui/itemviews/kselectionproxymodel.cpp:1891 #12 0x7f716414faf9 in QMetaObject::activate (sender=0xc253f0, m=optimized out, local_signal_index=optimized out, argv=0x7fffab66d9a0) at kernel/qobject.cpp:3547 #13 0x7f7164bc9217 in QItemSelectionModel::selectionChanged (this=optimized out, _t1=..., _t2=...) at .moc/release-shared/moc_qitemselectionmodel.cpp:166 #14 0x7f7164bcefe4 in QItemSelectionModel::emitSelectionChanged (this=0xc253f0, newSelection=..., oldSelection=...) at itemviews/qitemselectionmodel.cpp:1544 #15 0x7f7164bcff61 in QItemSelectionModel::select (this=0xc253f0, selection=..., command=...) at itemviews/qitemselectionmodel.cpp:1110 #16 0x7f715f2670d2 in MessageList::Pane::Private::onSelectionChanged(QItemSelection const, QItemSelection const) () from /usr/lib64/libmessagelist.so.4 #17 0x7f716414faf9 in QMetaObject::activate (sender=0xc18cd0, m=optimized out, local_signal_index=optimized out, argv=0x7fffab66dfc0) at kernel/qobject.cpp:3547 #18 0x7f7164bc9217 in QItemSelectionModel::selectionChanged
[Bug 296616] New: kmail2: mails available offline if offlinemode is disabled
https://bugs.kde.org/show_bug.cgi?id=296616 Bug ID: 296616 Severity: normal Version: Git (master) Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail2: mails available offline if offlinemode is disabled Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Other Status: UNCONFIRMED Component: misc Product: kmail2 Hi, I have two IMAP Accounts configured. For one the Offline IMAP is enabled and for the other its disabled. Now when I set kmail to offline mode, both accounts do have all mails available. (Status in Accounts dialog where akonadi resources are listet says that its currently Offline below Account name. This might have security implications as mail is locally stored where it should not be. Is this a real bug or do I have a f***ed up setup? I *may* be that I disabled offline for one account after if having initially enabled or the other way around... -- 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 229423] kmail 1.13.1: Online IMAP almost unusable in this version (I did not check other versions)
https://bugs.kde.org/show_bug.cgi?id=229423 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- 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 293233] Its not possible to print a mail properly
https://bugs.kde.org/show_bug.cgi?id=293233 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |FIXED --- Comment #10 from Marc Schiffbauer msch...@gentoo.org --- Works for me in 4.8.1 now! @karaluh: DO you confirm? -- 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 260761] akonadi fails to parse date on some rfc822 messages
https://bugs.kde.org/show_bug.cgi?id=260761 --- Comment #3 from Marc Schiffbauer msch...@gentoo.org --- This Bug is still present (akonadi 1.7.1 / KDE 4.8.1) -- 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 295932] New: Setting Loop in all folders when trying to find unread messages does not work properly
https://bugs.kde.org/show_bug.cgi?id=295932 Bug ID: 295932 Severity: normal Version: Git (master) Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Setting Loop in all folders when trying to find unread messages does not work properly Classification: Unclassified OS: Linux Reporter: msch...@gentoo.org Hardware: Other Status: UNCONFIRMED Component: message list Product: kmail2 Settings - Configure Kmail Misc - Folders - When trying to find unread messages: The setting Loop in all folders does not work properly and instead behaves equal to Loop in current folder. Only difference: With .. all folders it will jump from a folder without unread messages to the next folder with unread messages. The problem is that it will loop in a folder until there are no unread messages anymore, which seems wrong. (I have set kmail to NOT mark messages as read automatically, because I use the unread flag as something like a TODO flag) Expected behavior would be to not loop within a folder when Loop in all folders is set but instead jump to the next folder if last unread message within a folder has been reached. Loop in all folders should not work on top of the per folder Loop within Current folder setting but on top of Do not Loop setting. -Marc -- 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 293233] Its not possible to print a mail properly
https://bugs.kde.org/show_bug.cgi?id=293233 --- Comment #8 from Marc Schiffbauer mschiff gentoo org 2012-03-01 14:40:53 --- Created an attachment (id=69216) -- (http://bugs.kde.org/attachment.cgi?id=69216) Font settings I have set font to 12pt for printing (Bigger than screenfont) -- 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 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 --- Comment #43 from Marc Schiffbauer mschiff gentoo org 2012-02-16 10:52:06 --- (In reply to comment #40) when you move it between two folder you reorde it. That seems not to be possible here. I am trying really hard, but there seems to be no Space between to folders... But it's right there is still dnd menu I will look at to remove it (but it works) Default order is automatic order Why add an other order ? Well, maybe thats only true for local folders? I only use IMAP-Accounts and here the order is just alphabetically and the special folders are not treated differently and moved to the top. And its really annoying to have e.g. the INBOX somewhere betweeen all the other folders. Thanks -Marc -- 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 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 --- Comment #44 from Marc Schiffbauer mschiff gentoo org 2012-02-16 10:54:00 --- Additional note: I just noticed that I am able to reorder folders only for the local folders that I never use here. For IMAP there is no chance to do it. -- 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 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 --- Comment #45 from Marc Schiffbauer mschiff gentoo org 2012-02-16 10:57:47 --- Sorry for the noise: Automatic order for IMAP-Folders IS correct now, sorry! While playing with it the ordering in IMAP accounts was correct after re-applying the auto-order, so it seems I had to switch to manual order and back to auto-order to make kmail do it right now... So what is left, is that no DragNDrop is possible for IMAP-Folders. -- 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 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 --- Comment #52 from Marc Schiffbauer mschiff gentoo org 2012-02-16 13:51:01 --- Hi Laurent, I rebuilt kdepimlibs and kdepim. In IMAP reordering of folders does not work for me. At least with top-level folders. What indeed works is to reorder subfolders within a toplevel-folderin, but it is for example not possible to move the INBOX folder to the first position of the folder list. -Marc -- 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 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 --- Comment #39 from Marc Schiffbauer mschiff gentoo org 2012-02-15 23:44:15 --- Hi Laurent, thanks for looking after that bug. I just tested your new patch. Maybe I am too stupid, but I am not able to reorder Folders in Kmail via Drag and Drop. How is that supposed to work? I right-clicked the Header of the Folder List-Widget and set to manual order by drag and drop at the bottom of the menu, ok. But how to do it? If I drag a folder I can move that folder to somewhere instead of reordering it in the List? I tried holding down Alt-/Shift-/Ctrl-Key while dragging but for that the usual file-DnD actions are in place: Move/Link/Copy etc (How will you do a Link of a Folder in IMAP BTW?) And another issue (That might be woth another bugreport): Why don't you simply have a default folder order where the special folders come first and then any subfolders in the account. I think that way most people will not need the manual order-thingy anymore... Thanks -Marc -- 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 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 --- Comment #34 from Marc Schiffbauer mschiff gentoo org 2012-02-14 12:22:33 --- What worries me a bit is that, there is absolutely no reaction from the devs. Maybe this bug is out of focus? Or there is too much to do. Or a lack of time... Ping $devs. Any news on that issue? Is this PITA too complicated to fix? Would really be cool to have this fixed soon, because it would really greatly improve user experience of kmail. Thanks -Marc -- 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 293233] Its not possible to print a mail properly
https://bugs.kde.org/show_bug.cgi?id=293233 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID | --- Comment #2 from Marc Schiffbauer mschiff gentoo org 2012-02-04 15:03:41 --- Hi Laurent, I am sorry If I did not describe it precise enough: I changed the font setting for printing within the kmail2 settings but this setting has absolutely no effect when printing. Settings - Configure Kmail - Appearance Then Apply To - Printing Output - Liberation Sans, Regular, 12,0 I set it to a 12pt font, but when printing the font stays at a mninimum of perhaps 6pt. -- 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 293233] New: Its not possible to print a mail properly
https://bugs.kde.org/show_bug.cgi?id=293233 Summary: Its not possible to print a mail properly Product: kmail2 Version: 4.8 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: msch...@gentoo.org Version: 4.8 (using Devel) OS:Linux Regardless of the font setting for mail printing the printed font is always very small (6pt?) Reproducible: Always Steps to Reproduce: Print a mail Actual Results: Very small text Expected Results: Printed mail with font as specified in settings -- 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 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 --- Comment #28 from Marc Schiffbauer mschiff gentoo org 2011-12-13 15:56:04 --- Its also still present in 4.8.90 (Beta 2) I vote for changing automatic ordering, so that the special folders are always on top (At least Inbox, Sent, Drafts and Trash) -- 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 280243] KMail ignores mail message templates
https://bugs.kde.org/show_bug.cgi?id=280243 Marc Schiffbauer msch...@gentoo.org changed: What|Removed |Added CC||msch...@gentoo.org --- Comment #11 from Marc Schiffbauer mschiff gentoo org 2011-12-09 13:56:15 --- Additional note from my side (using kmail from KDEPIM 4.8.90): For me at least identity-based templates do not work. I just added another identity to kmail and changed some templates within the identity-config dialog. Then I started a new mail, and switched the identity: The signature is changed correctly on identity change, but the templates to definitly not work. (In the new identity I just added a default greeting for new messages) -Marc -- 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 280243] Support changing templates from within the composer
https://bugs.kde.org/show_bug.cgi?id=280243 --- Comment #13 from Marc Schiffbauer mschiff gentoo org 2011-12-09 14:53:52 --- OK, thanks for the explanation. So this has potential to cause a lot of confusion. I think we can confirm that this IS an issue, right? Users can change templates in identities for nothing, because you can have templates for identities that are NOT the default identity for ANY account. Suggestions to solve the issue (I do not know the code, so please be gentle ;)): * Change the code so that it will be possible to switch the template while the editor is already opened, say if the previous/new message body has not been altered by the user yet. AND/OR * Find a way to make it possible to select identity just before creating a new message or before replying so that processing the template can be done using the identity the user wants. OR * The templates should better be anchored to accounts then, and not to identities at all. OR * The tabs for setting templates should only appear / be enabled if the identity being edited is a default identity for an account. But that might also cause some confusion to the user, so I'd prefer the above suggestions to solve this issue. -- 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 259358] Re-ordering folders via drag drop not working anymore
https://bugs.kde.org/show_bug.cgi?id=259358 --- Comment #24 from Marc Schiffbauer mschiff gentoo org 2011-10-30 23:14:26 --- (In reply to comment #22) I can reorder folder by dnd. but not all is perfect yet. Sorry, I can't. Maybe I am too stupid. How should this work? I can move folders by dnd but I cannot reorder them. My tries to do so always result in folders being moved... -- 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
