[Bug 302975] sending queued messages results in mail sending to fail totally
https://bugs.kde.org/show_bug.cgi?id=302975 --- Comment #4 from Silver Salonen --- My point was that in 4.9.4 it works as expected :) -- 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 310819] Some minor quirks in attachment properties dialog (read-only mode)
https://bugs.kde.org/show_bug.cgi?id=310819 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.11 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/376d01d4d40a3f7fecddb1d1 ||6faff05b7809bb4b --- Comment #8 from Laurent Montel --- Git commit 376d01d4d40a3f7fecddb1d16faff05b7809bb4b by Montel Laurent. Committed on 19/12/2012 at 08:32. Pushed by mlaurent into branch 'master'. Fix Bug 310819 - Some minor quirks in attachment properties dialog (read-only mode) FIXED-IN: 4.11 M +1-0messagecore/CMakeLists.txt M +101 -65 messagecore/attachmentpropertiesdialog.cpp A +177 -0messagecore/attachmentpropertiesdialog_readonly.ui http://commits.kde.org/kdepim/376d01d4d40a3f7fecddb1d16faff05b7809bb4b -- 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 292601] Fetch job error on login
https://bugs.kde.org/show_bug.cgi?id=292601 Jarosław Staniek changed: What|Removed |Added Status|RESOLVED|REOPENED CC||stan...@kde.org Resolution|WORKSFORME |--- --- Comment #20 from Jarosław Staniek --- Exactly this error on logout (http://bugsfiles.kde.org/attachment.cgi?id=73344) in OpenSuSE 12.2 Factory, KDE 4.9.4. Dual display. I propose to reopen... How to debug this? -- 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 303109] Message-ID: field of kmail 4.8.4 exposes hostname
https://bugs.kde.org/show_bug.cgi?id=303109 --- Comment #2 from regi.h...@gmx.net --- OK - Found it at last :-) Looked in every place but certainly not in the "Editor-Configuration". Sometimes I think the configuration of KMail is made by the help of a random generator, and maybe not everything that could be translated should be. But I agree the default value should be something else than the local host name. Using the standard domain of the send options would be more plausible, or the configurable host name in the extended send options. Cheers Regi -- 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 274936] search folders always show messages as unread
https://bugs.kde.org/show_bug.cgi?id=274936 --- Comment #6 from Luis Silva --- Search folders still have an unread count equal to the total number of messages found. I am using master, compiled from source. -- 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 303109] Message-ID: field of kmail 4.8.4 exposes hostname
https://bugs.kde.org/show_bug.cgi?id=303109 regi.h...@gmx.net changed: What|Removed |Added CC||regi.h...@gmx.net --- Comment #1 from regi.h...@gmx.net --- (In reply to comment #0) > I found that the Message-ID can be configured, but a default that does not > expose internal data would be better. Hi, I have the problem that some servers flag my messages as spam, because of that local domain part. How and where can it be configured? Regards Regi -- 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 255388] Kmail filters dont work in incoming mail
https://bugs.kde.org/show_bug.cgi?id=255388 --- Comment #73 from elvenfigh...@qip.ru --- I use Kmail 4.9.4. I would like to admit: 1. Go to "Inbox" (or some other) folder 1b. Make sure you have some messages that match filters 2. Select all mails in the foler (e.g. press Ctrl+a) 3. Run message filters (e.g. press Ctrl+j) Expected results: Filters are applied to all selected messages Actual results: Filters are applied only to some messages (sometimes some == 0). I mean that not all (selected) messages that match filters are filtered. -- 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 302975] sending queued messages results in mail sending to fail totally
https://bugs.kde.org/show_bug.cgi?id=302975 Allen Winter changed: What|Removed |Added CC||win...@kde.org --- Comment #3 from Allen Winter --- Silver, Should we reopen this one? -- 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 311910] New: kontact segfaults on exit
https://bugs.kde.org/show_bug.cgi?id=311910 Bug ID: 311910 Severity: crash Version: 4.9.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kontact segfaults on exit Classification: Unclassified OS: Linux Reporter: gor...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9.4) KDE Platform Version: 4.9.4 Qt Version: 4.8.3 Operating System: Linux 3.5.0-19-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: - What I was doing when the application crashed: Just closing kontact - happens even after fresh restart. Happens every time The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f78d086a7c0 (LWP 23195))] Thread 4 (Thread 0x7f78c8adc700 (LWP 23196)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f78e1de1b2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f78e1de1c39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f78dd32be9a in start_thread (arg=0x7f78c8adc700) at pthread_create.c:308 #4 0x7f78e2b0ccbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7f78c81db700 (LWP 23197)): #0 0x7f78e2b01303 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f78dce5cd84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78dce5cea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78e3281c16 in QEventDispatcherGlib::processEvents (this=0x7f78c8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f78e32522bf in QEventLoop::processEvents (this=this@entry=0x7f78c81dadc0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f78e3252548 in QEventLoop::exec (this=0x7f78c81dadc0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f78e3153b10 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f78e3156aec in QThreadPrivate::start (arg=0x227d620) at thread/qthread_unix.cpp:338 #8 0x7f78dd32be9a in start_thread (arg=0x7f78c81db700) at pthread_create.c:308 #9 0x7f78e2b0ccbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x in ?? () Thread 2 (Thread 0x7f787a86b700 (LWP 23200)): #0 0x7f78e2b01303 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f78dce5cd84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f78dce5cea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f78e3281c16 in QEventDispatcherGlib::processEvents (this=0x7f78740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f78e32522bf in QEventLoop::processEvents (this=this@entry=0x7f787a86ad90, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f78e3252548 in QEventLoop::exec (this=0x7f787a86ad90, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f78e3153b10 in QThread::exec (this=) at thread/qthread.cpp:501 #7 0x7f78e32329af in QInotifyFileSystemWatcherEngine::run (this=0x28f5530) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f78e3156aec in QThreadPrivate::start (arg=0x28f5530) at thread/qthread_unix.cpp:338 #9 0x7f78dd32be9a in start_thread (arg=0x7f787a86b700) at pthread_create.c:308 #10 0x7f78e2b0ccbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f78d086a7c0 (LWP 23195)): [KCrash Handler] #6 0x0001 in ?? () #7 0x0040337e in qDeleteAll::const_iterator> (end=..., begin=...) at /usr/include/qt4/QtCore/qalgorithms.h:322 #8 qDeleteAll > (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:330 #9 main (argc=1, argv=0x7fff505e1218) at ../../../kontact/src/main.cpp:220 This bug may be a duplicate of or related to bug 288141. Possible duplicates by query: bug 307373, bug 307140, bug 305591, bug 304826, bug 300135. Reported using DrKonqi -- 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 311905] New: Kmail crash on opening email
https://bugs.kde.org/show_bug.cgi?id=311905 Bug ID: 311905 Severity: crash Version: 4.9.4 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crash on opening email Classification: Unclassified OS: Linux Reporter: crgla...@gmail.com Hardware: openSUSE RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9.4) KDE Platform Version: 4.9.4 "release 5" Qt Version: 4.8.4 Operating System: Linux 3.1.10-1.16-desktop x86_64 Distribution: "openSUSE 12.1 (x86_64)" -- Information about the crash: I was opening an email and Kmail crashed 5 times in a row. I cannot highlight the offending email to delete it without causing a crash. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7fb98df52760 (LWP 25830))] Thread 6 (Thread 0x7fb9757dc700 (LWP 25831)): #0 0x7fb985c84e6c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb98a70df52 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7fb98a70df89 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7fb985c80f05 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb98b45210d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fb974edb700 (LWP 25832)): #0 0x7fff5be6b8de in ?? () #1 0x7fb983748d9a in clock_gettime () from /lib64/librt.so.1 #2 0x7fb98baea264 in do_gettime (frac=0x7fb974edab88, sec=0x7fb974edab80) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7fb98bbc329d in QTimerInfoList::updateCurrentTime (this=0x7fb9700020d0) at kernel/qeventdispatcher_unix.cpp:354 #5 0x7fb98bbc35d3 in QTimerInfoList::timerWait (this=0x7fb9700020d0, tm=...) at kernel/qeventdispatcher_unix.cpp:461 #6 0x7fb98bbc1f0c in timerSourcePrepareHelper (src=, timeout=0x7fb974edac6c) at kernel/qeventdispatcher_glib.cpp:136 #7 0x7fb98bbc1fb5 in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #8 0x7fb985770b72 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #9 0x7fb98577197d in ?? () from /usr/lib64/libglib-2.0.so.0 #10 0x7fb985771fa9 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #11 0x7fb98bbc2a36 in QEventDispatcherGlib::processEvents (this=0x7fb978c0, flags=) at kernel/qeventdispatcher_glib.cpp:426 #12 0x7fb98bb92252 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #13 0x7fb98bb924a7 in QEventLoop::exec (this=0x7fb974edae00, flags=...) at kernel/qeventloop.cpp:204 #14 0x7fb98ba90777 in QThread::exec (this=) at thread/qthread.cpp:542 #15 0x7fb98ba937dc in QThreadPrivate::start (arg=0x7ff510) at thread/qthread_unix.cpp:338 #16 0x7fb985c80f05 in start_thread () from /lib64/libpthread.so.0 #17 0x7fb98b45210d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fb927c8f700 (LWP 26785)): #0 0x7fb985c851eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb98ba93caf in wait (time=3, this=0xe144a0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0xe14b28, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7fb98ba8701f in QThreadPoolThread::run (this=0xe19b50) at concurrent/qthreadpool.cpp:141 #4 0x7fb98ba937dc in QThreadPrivate::start (arg=0xe19b50) at thread/qthread_unix.cpp:338 #5 0x7fb985c80f05 in start_thread () from /lib64/libpthread.so.0 #6 0x7fb98b45210d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fb91700 (LWP 26786)): #0 0x7fb985c851eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb98ba93caf in wait (time=3, this=0x13469d0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x12262b8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7fb98ba8701f in QThreadPoolThread::run (this=0x12263a0) at concurrent/qthreadpool.cpp:141 #4 0x7fb98ba937dc in QThreadPrivate::start (arg=0x12263a0) at thread/qthread_unix.cpp:338 #5 0x7fb985c80f05 in start_thread () from /lib64/libpthread.so.0 #6 0x7fb98b45210d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fb91e41e700 (LWP 26788)): #0 0x7fb985c851eb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb98ba93caf in wait (time=3, this=0x11f2150) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x12096c8, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7fb98ba8701f in QThreadPoolThread::run (this=0x1209850) at concurrent/qthreadpool.cpp:141 #4 0x7fb98ba937dc in QThreadPrivate::start (arg=0x1209850) at thread/qthread_unix.cpp:338 #5 0x7fb985c80f05 in start_thread () from /lib64/libpthread.so.0 #6 0x7fb98b45210d in clone () from /lib64/libc.so.6 T
[Bug 311898] New: Crash when trying to use Time Tracker for first time
https://bugs.kde.org/show_bug.cgi?id=311898 Bug ID: 311898 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Crash when trying to use Time Tracker for first time Classification: Unclassified OS: Linux Reporter: timh...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.5) KDE Platform Version: 4.8.5 (4.8.5) Qt Version: 4.8.1 Operating System: Linux 3.2.0-34-generic-pae i686 Distribution: Zorin OS 6 -- Information about the crash: - What I was doing when the application crashed: I had opened the Time Tracker modual and had just clicked on (I believe ) the New Task button and it crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb21be980 (LWP 8107))] Thread 4 (Thread 0xaf3ffb40 (LWP 8109)): #0 0xb38f0f9f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0xb38f156b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0xb09881ba in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #3 0xb39146b3 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb39c3d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #5 0xb60c7d3e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xadc83b40 (LWP 8110)): #0 0xb779f424 in __kernel_vsyscall () #1 0xb39c796b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0xb60d564c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb584f263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb584f37f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb39c3d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0xb60c7d3e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xad362b40 (LWP 8111)): #0 0xb3715dcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1 #1 0xb632f315 in do_gettime (frac=0xad362040, sec=0xad362038) at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb6419226 in QTimerInfoList::updateCurrentTime (this=0xaca01974) at kernel/qeventdispatcher_unix.cpp:343 #4 0xb6418e16 in timerSourceCheckHelper (src=0xaca01940) at kernel/qeventdispatcher_glib.cpp:150 #5 timerSourceCheckHelper (src=0xaca01940) at kernel/qeventdispatcher_glib.cpp:144 #6 0xb38f0b7b in g_main_context_check () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0xb38f1042 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #8 0xb38f1201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #9 0xb64188e7 in QEventDispatcherGlib::processEvents (this=0xaca00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #10 0xb63e450d in QEventLoop::processEvents (this=0xad362270, flags=...) at kernel/qeventloop.cpp:149 #11 0xb63e47a9 in QEventLoop::exec (this=0xad362270, flags=...) at kernel/qeventloop.cpp:204 #12 0xb62cd94c in QThread::exec (this=0x9814940) at thread/qthread.cpp:501 #13 0xb62cda3b in QThread::run (this=0x9814940) at thread/qthread.cpp:568 #14 0xb62d0de0 in QThreadPrivate::start (arg=0x9814940) at thread/qthread_unix.cpp:298 #15 0xb39c3d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #16 0xb60c7d3e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb21be980 (LWP 8107)): [KCrash Handler] #7 0xa7a88aaf in timetrackerstorage::rawevents (this=0xa494a20) at ../../ktimetracker/timetrackerstorage.cpp:321 #8 0xa7aac7c2 in historydialog::listallevents (this=0xa4b8b98) at ../../ktimetracker/historydialog.cpp:102 #9 0xa7aae242 in historydialog::historydialog (this=0xa4b8b98, parent=0xa48bfe8) at ../../ktimetracker/historydialog.cpp:82 #10 0xa7a8450b in EditTaskDialog::on_edittimespushbutton_clicked (this=0x9cccd68) at ../../ktimetracker/edittaskdialog.cpp:103 #11 0xa7a7ed5d in EditTaskDialog::qt_static_metacall (_o=, _id=, _a=, _c=) at moc_edittaskdialog.cpp:52 #12 0xa7a7ee09 in EditTaskDialog::qt_metacall (this=0x9cccd68, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfae5c78) at moc_edittaskdialog.cpp:91 #13 0xb63ecc9d in metacall (argv=0xbfae5c78, idx=37, cl=QMetaObject::InvokeMetaMethod, object=0x9cccd68) at kernel/qmetaobject.cpp:245 #14 QMetaObject::metacall (object=0x9cccd68, cl=QMetaObject::InvokeMetaMethod, idx=37, argv=0xbfae5c78) at kernel/qmetaobject.cpp:240 #15 0xb63fc9bd in QMetaObject::activate (sender=0xa09b0f0, m=0xb72dd7c8, local_signal_index=2, argv=0xbfae5c78) at kernel/qobject.cpp:3566 #16 0xb708997d in QAbstractButton::clicked (this=0xa09b0f0, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:220 #17 0xb6d7d62d in QAbstractButtonPrivate::emitClicked (this=0xa4b97a8) at widgets/qabstractbutton.cpp:548 #18 0xb6d7ec9b in QAbstractButtonPrivate::click (this=0xa4b97a8) at
[Bug 292249] Screensaver crashes when mouse is move
https://bugs.kde.org/show_bug.cgi?id=292249 --- Comment #8 from exevans.n...@gmail.com --- Created attachment 75904 --> https://bugs.kde.org/attachment.cgi?id=75904&action=edit New crash information added by DrKonqi plasma-overlay (0.0) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1 - What I was doing when the application crashed: The screensaver just started up, and I immediately clicked to continue working. -- Backtrace (Reduced): #7 0x7ff32f3131da in KJob::kill (this=0x2c45d00, verbosity=KJob::EmitResult) at ../../kdecore/jobs/kjob.cpp:111 #8 0x7ff30dc9e5a7 in Akonadi::Session::clear (this=0x29a2160) at ../../akonadi/session.cpp:425 #9 0x7ff30dc9e94b in Akonadi::Session::~Session (this=0x29a2160, __in_chrg=) at ../../akonadi/session.cpp:394 #10 0x7ff30dc9e999 in Akonadi::Session::~Session (this=0x29a2160, __in_chrg=) at ../../akonadi/session.cpp:396 #11 0x7ff32ec1e935 in QObjectPrivate::deleteChildren (this=0x2b0d0d0) at kernel/qobject.cpp:1908 -- 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 292249] Screensaver crashes when mouse is move
https://bugs.kde.org/show_bug.cgi?id=292249 exevans.n...@gmail.com changed: What|Removed |Added CC||exevans.n...@gmail.com -- 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 255388] Kmail filters dont work in incoming mail
https://bugs.kde.org/show_bug.cgi?id=255388 --- Comment #72 from Thomas Arend --- (In reply to comment #71) > Automatic filtering doesn't work on local mbox or maildir accounts. > > I set up a filter to move incoming messages to a different folder. When I > use mailx to send myself a test message, the message appears in the incoming > folder and isn't moved, and nothing shows in the filter log. The filter > works fine when applied manually. > > Reproducible always. Kmail 4.9.4. For me this partly right. I received some hundred mail a day (outputs of cron jobs) and spam. Some mails are filtered some are not. At the moment ~10% of the mails are not filtered. -- 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 311718] QFSFileEngine::open: No file name specified
https://bugs.kde.org/show_bug.cgi?id=311718 Thomas Arend changed: What|Removed |Added CC||tho...@arend-rhb.de --- Comment #2 from Thomas Arend --- Maybe! I don't know but would not be surprised if it is. -- 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 302277] Email stuck in outbox
https://bugs.kde.org/show_bug.cgi?id=302277 aldo-pub...@laposte.net changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #2 from aldo-pub...@laposte.net --- I understand there can be many reasons for failing to send an email, but would it be possible at least to make it much more obvious when something is not working right? Knowing that an email was not sent is often very critical. Why isn't there a configurable notification for this? Note there is already a notification for email transport failure, but I believe here it is different: for some reason Kmail did not even try to send the email, despite of the fact the user pressed "send" button. If kmail is a situation it won't even try to send an email after pressing that button, then this should definitely trigger an alert too. -- 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 311718] QFSFileEngine::open: No file name specified
https://bugs.kde.org/show_bug.cgi?id=311718 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- "Why does akonadieconsole try to open a file hundreds of times without a filename?" because it's a bug ?:) -- 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 311869] New: Clicking messages in the mail list won't show the message content in the message area
https://bugs.kde.org/show_bug.cgi?id=311869 Bug ID: 311869 Severity: major Version: Git (master) Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Clicking messages in the mail list won't show the message content in the message area Classification: Unclassified OS: Linux Reporter: ignat.seme...@blue-systems.com Hardware: Other Status: CONFIRMED Component: general Product: kmail2 I have setup an IMAP account. The message list is loaded correctly, but clicking a message in the message list does not show its contents where it should be shown - below the message list. The message area is empty. Double-clicking a message list item does nothing. 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
