[Bug 307402] crash when attaching a directory
https://bugs.kde.org/show_bug.cgi?id=307402 --- Comment #2 from Michael Monnerie --- Depends on what "big" is for you: 29628KB, 92 files. I don't understand the question "did you have access to data ?". I normally have access to my data, if you mean that. Anyway, is there a way to switch back to the old behaviour so when I enter a directory in the attach dialog I'm not asked "attach dir?" but instead just change into that dir and show me it's files? -- 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 307551] Kontact crash at close
https://bugs.kde.org/show_bug.cgi?id=307551 Jekyll Wu changed: What|Removed |Added Component|general |general Version|unspecified |4.9 Assignee|kdepim-bugs@kde.org |nepomuk-b...@kde.org Product|kontact |nepomuk -- 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 307551] New: Kontact crash at close
https://bugs.kde.org/show_bug.cgi?id=307551 Bug ID: 307551 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crash at close Classification: Unclassified OS: Linux Reporter: wyxkno...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.9) KDE Platform Version: 4.9.00 Qt Version: 4.8.1 Operating System: Linux 3.2.0-29-generic x86_64 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Every time I close Kontact at the end of the day it crash. I use the whole day and at the endo of the day when I leave I close contact and in background crash and sometime when I tried to open again there are a zombie process in background and I have to kill all kontact to be able to open again 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 0x7f061f5357c0 (LWP 8234))] Thread 3 (Thread 0x7f0602ab1700 (LWP 8235)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f061bd2cdec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f061bd2cf19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f06171dce9a in start_thread (arg=0x7f0602ab1700) at pthread_create.c:308 #4 0x7f061ca5e4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 2 (Thread 0x7f05b4c52700 (LWP 8240)): #0 0x7fffe7f9070a in ?? () #1 0x7fffe7f90959 in ?? () #2 0x7f061554015d in __GI_clock_gettime (clock_id=, tp=) at ../sysdeps/unix/clock_gettime.c:116 #3 0x7f061d0fbbb4 in do_gettime (frac=0x7f05b4c51b58, sec=0x7f05b4c51b50) at tools/qelapsedtimer_unix.cpp:123 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #5 0x7f061d1d3b8d in QTimerInfoList::updateCurrentTime (this=0x7f05b0002660) at kernel/qeventdispatcher_unix.cpp:343 #6 0x7f061d1d3ec3 in QTimerInfoList::timerWait (this=0x7f05b0002660, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #7 0x7f061d1d297c in timerSourcePrepareHelper (src=, timeout=0x7f05b4c51c2c) at kernel/qeventdispatcher_glib.cpp:136 #8 0x7f061d1d2a25 in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #9 0x7f0616d0f846 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f0616d0ff5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f0616d10164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f061d1d3426 in QEventDispatcherGlib::processEvents (this=0x7f05b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #13 0x7f061d1a2c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #14 0x7f061d1a2ed7 in QEventLoop::exec (this=0x7f05b4c51d90, flags=...) at kernel/qeventloop.cpp:204 #15 0x7f061d0a1fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #16 0x7f061d1829ff in QInotifyFileSystemWatcherEngine::run (this=0x13ca2b0) at io/qfilesystemwatcher_inotify.cpp:248 #17 0x7f061d0a4fcb in QThreadPrivate::start (arg=0x13ca2b0) at thread/qthread_unix.cpp:298 #18 0x7f06171dce9a in start_thread (arg=0x7f05b4c52700) at pthread_create.c:308 #19 0x7f061ca5e4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #20 0x in ?? () Thread 1 (Thread 0x7f061f5357c0 (LWP 8234)): [KCrash Handler] #6 0x7f06152bc082 in lockInline (this=0x136adb8) at /usr/include/qt4/QtCore/qmutex.h:187 #7 QMutexLocker (m=0x136adb8, this=) at /usr/include/qt4/QtCore/qmutex.h:109 #8 Nepomuk::Resource::~Resource (this=0x7f05a0008eb0, __in_chrg=) at ../../nepomuk/core/resource.cpp:142 #9 0x7f06152bc309 in Nepomuk::Resource::~Resource (this=0x7f05a0008eb0, __in_chrg=) at ../../nepomuk/core/resource.cpp:147 #10 0x7f061d1b48a9 in QMetaCallEvent::~QMetaCallEvent (this=0x7f05a0009420, __in_chrg=) at kernel/qobject.cpp:509 #11 0x7f061d1b4909 in QMetaCallEvent::~QMetaCallEvent (this=0x7f05a0009420, __in_chrg=) at kernel/qobject.cpp:518 #12 0x7f061d1a83ff in QCoreApplication::removePostedEvents (receiver=0x1557090, eventType=0) at kernel/qcoreapplication.cpp:1630 #13 0x7f061d1ba4cb in QObjectPrivate::~QObjectPrivate (this=0x155e810, __in_chrg=) at kernel/qobject.cpp:171 #14 0x7f061d1ba549 in QObjectPrivate::~QObjectPrivate (this=0x155e810, __in_chrg=) at kernel/qobject.cpp:186 #15 0x7f061d1bcbd0 in cleanup (pointer=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:62 #16 ~QScopedPointer (this=0x1557098, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:100 #
[Bug 307548] New: kmail2 does not update mail after piping mail throught a script
https://bugs.kde.org/show_bug.cgi?id=307548 Bug ID: 307548 Severity: major Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail2 does not update mail after piping mail throught a script Classification: Unclassified OS: Linux Reporter: tho...@arend-rhb.de Hardware: Other Status: UNCONFIRMED Component: filtering Product: kmail2 I have a script to change all occurrences of octet-stream to pkcs7-mime. The filter log says that the filter was applied. I saved the input and output via "tee" in to files. Every thing looked as it should. octet-stream was changed to pkcs7-mime, but the message is not updated. Even in akonadiconsole the log entry says that the message was stored successfully. Reproducible: Always Steps to Reproduce: 1. Pipe message through a filter which modiefies parts of the header. 2. 3. Actual Results: Old message is not replaced by new message. Expected Results: Old message should be replaced by the output of the filter. -- 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 298136] notification about "connection to server lost" should be more tolerant
https://bugs.kde.org/show_bug.cgi?id=298136 Beat Wolf changed: What|Removed |Added CC||asran...@fryx.ch -- 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 300351] Annoying notifications "Connection to server lost", multiple KWallet requests to re-connect
https://bugs.kde.org/show_bug.cgi?id=300351 Beat Wolf changed: What|Removed |Added CC||asran...@fryx.ch -- 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 307536] New: Edit->Copy Email just puts the akonadi url into the clipboard
https://bugs.kde.org/show_bug.cgi?id=307536 Bug ID: 307536 Severity: minor Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Edit->Copy Email just puts the akonadi url into the clipboard Classification: Unclassified OS: Linux Reporter: craig.mag...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: commands and actions Product: kmail2 When I selected Copy Email I was expecting it to copy the e-mail contents to the clipboard, but when I pasted it, instead of getting the e-mail contents I just got the akonadi url. Reproducible: Always Steps to Reproduce: 1. Select an e-mail 2. Click Edit->Copy Email 3. Paste to a text editor or even the desktop Actual Results: It will paste the akonadi url for the e-mail. Expected Results: I was expecting it to paste the body of the e-mail. -- 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 307519] Klicking the searchbar does not remove focus from message list
https://bugs.kde.org/show_bug.cgi?id=307519 --- Comment #3 from qqq...@gmeyer.df-kunde.de --- Wow, 1 hour from reporting to fixing :D Thanks! -- 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 294548] Keyboard navigation does no work with unread mails
https://bugs.kde.org/show_bug.cgi?id=294548 David Faure changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from David Faure --- Git commit 21cd990881fd3bf0cf10061a2aab24edf2efe7a4 by David Faure. Committed on 27/09/2012 at 18:29. Pushed by dfaure into branch 'KDE/4.9'. Fix synchronization between favorites view and folder tree in kmail. 1) ensure one slot doesn't call the other; the old blockSignals was meant to do that, but that was wrong of course (the action manager doesn't emit signals, it's connected to them) 2) set the current index in the folder tree, not just the selection, so that keyboard navigation is more predictable, but more importantly so that kmail is informed of the new current folder, and updates actions appropriately. M +28 -6akonadi/standardactionmanager.cpp -- 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 288364] "Retrieving Folder Contents" hanging without showing content
https://bugs.kde.org/show_bug.cgi?id=288364 Nick Ladis changed: What|Removed |Added CC||ndla...@otenet.gr -- 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 307521] Kmail crash frequently
https://bugs.kde.org/show_bug.cgi?id=307521 --- Comment #2 from Laurent Montel --- Do you try to config a smtp account or a sendmail or an akonadi account ? If you can send me in private message your ~/.kde*/share/config/mailtransports Thanks -- 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 307521] Kmail crash frequently
https://bugs.kde.org/show_bug.cgi?id=307521 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- So you try to edit transport ? #7 0x7f7222dc95a4 in ?? () from /usr/lib/libmailtransport.so.4 #8 0x7f7222dab12d in MailTransport::TransportManager::configureTransport(MailTransport::Transport*, QWidget*) () from /usr/lib/libmailtransport.so.4 #9 0x7f7222dd0de6 in MailTransport::TransportManagementWidget::Private::editClicked() () from /usr/lib/libmailtransport.so.4 ? -- 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 307519] Klicking the searchbar does not remove focus from message list
https://bugs.kde.org/show_bug.cgi?id=307519 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.9.2 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/d3a706d05a6063717a78e694 ||182323b92a07a546 --- Comment #2 from Laurent Montel --- Git commit d3a706d05a6063717a78e694182323b92a07a546 by Montel Laurent. Committed on 28/09/2012 at 13:11. Pushed by mlaurent into branch 'KDE/4.9'. Fix Bug 307519 - Klicking the searchbar does not remove focus from message list FIXED-IN: 4.9.2 M +1-1kmail/kmmainwidget.cpp M +8-0messagelist/core/widgetbase.cpp M +2-0messagelist/core/widgetbase.h M +9-0messagelist/pane.cpp M +2-0messagelist/pane.h M +0-1messagelist/widget.cpp http://commits.kde.org/kdepim/d3a706d05a6063717a78e694182323b92a07a546 -- 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 307519] Klicking the searchbar does not remove focus from message list
https://bugs.kde.org/show_bug.cgi?id=307519 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I confirm it. Fixed now -- 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 307521] New: Kmail crash frequently
https://bugs.kde.org/show_bug.cgi?id=307521 Bug ID: 307521 Severity: crash Version: 4.8.5 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kmail crash frequently Classification: Unclassified OS: Linux Reporter: meconiot...@gmail.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kmail2 Application: kmail (4.8.5) KDE Platform Version: 4.8.5 (4.8.5) Qt Version: 4.8.1 Operating System: Linux 3.2.0-31-generic x86_64 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Try to send a mail, Kde is greath but this client doesn't work never I have 4 mail account and there isn't a simple method to have all 4 working on it. Btw This thime has crashed when i try to send the first mail on a clean install The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f722a5df7c0 (LWP 1891))] Thread 4 (Thread 0x7f720826a700 (LWP 1899)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f721c8c9dec in WTF::TCMalloc_PageHeap::scavengerThread (this=0x7f721d292de0) at wtf/FastMalloc.cpp:2495 #2 0x7f721c8c9f19 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at wtf/FastMalloc.cpp:1618 #3 0x7f7225402e9a in start_thread (arg=0x7f720826a700) at pthread_create.c:308 #4 0x7f72279334bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7f7207969700 (LWP 1900)): #0 0x7f7220211320 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f72202115c9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f72201d5aee in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f72201d5fd6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f72201d6164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f72282be426 in QEventDispatcherGlib::processEvents (this=0x7f7208c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f722828dc82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f722828ded7 in QEventLoop::exec (this=0x7f7207968dc0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f722818cfa7 in QThread::exec (this=) at thread/qthread.cpp:501 #9 0x7f722818ffcb in QThreadPrivate::start (arg=0x178b8c0) at thread/qthread_unix.cpp:298 #10 0x7f7225402e9a in start_thread (arg=0x7f7207969700) at pthread_create.c:308 #11 0x7f72279334bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 2 (Thread 0x7f7204b35700 (LWP 1907)): #0 0x7f722540605d in __pthread_mutex_unlock_usercnt (mutex=, decr=) at pthread_mutex_unlock.c:52 #1 __pthread_mutex_unlock (mutex=0x7f71b4000a60) at pthread_mutex_unlock.c:290 #2 0x7f72202115d1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f72201d57e2 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f72201d5f5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f72201d6164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f72282be426 in QEventDispatcherGlib::processEvents (this=0x7f71b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x7f722828dc82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #8 0x7f722828ded7 in QEventLoop::exec (this=0x7f7204b34d90, flags=...) at kernel/qeventloop.cpp:204 #9 0x7f722818cfa7 in QThread::exec (this=) at thread/qthread.cpp:501 #10 0x7f722826d9ff in QInotifyFileSystemWatcherEngine::run (this=0x1942ae0) at io/qfilesystemwatcher_inotify.cpp:248 #11 0x7f722818ffcb in QThreadPrivate::start (arg=0x1942ae0) at thread/qthread_unix.cpp:298 #12 0x7f7225402e9a in start_thread (arg=0x7f7204b35700) at pthread_create.c:308 #13 0x7f72279334bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #14 0x in ?? () Thread 1 (Thread 0x7f722a5df7c0 (LWP 1891)): [KCrash Handler] #6 0x7f7228bcf9fc in QLineEdit::text (this=0x24470f0) at widgets/qlineedit.cpp:380 #7 0x7f7222dc95a4 in ?? () from /usr/lib/libmailtransport.so.4 #8 0x7f7222dab12d in MailTransport::TransportManager::configureTransport(MailTransport::Transport*, QWidget*) () from /usr/lib/libmailtransport.so.4 #9 0x7f7222dd0de6 in MailTransport::TransportManagementWidget::Private::editClicked() () from /usr/lib/libmailtransport.so.4 #10 0x7f72282a3281 in QMetaObject::activate (sender=0x266baf0, m=, local_signal_index=, argv=0x7fff849cc510) at kernel/qobject.cpp:35
[Bug 307519] New: Klicking the searchbar does not remove focus from message list
https://bugs.kde.org/show_bug.cgi?id=307519 Bug ID: 307519 Severity: normal Version: 4.9.1 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Klicking the searchbar does not remove focus from message list Classification: Unclassified OS: Linux Reporter: qqq...@gmeyer.df-kunde.de Hardware: Archlinux Packages Status: UNCONFIRMED Component: message list Product: kmail2 Please look at the Steps to reproduce. Reproducible: Always Steps to Reproduce: 1. click an email in message list 2. click into search field 3. Filter for some string in the subject of the clicked email 4. hit enter Actual Results: the selected email is opened in a separate window Expected Results: nothing, Reasoning: consistency: In many search fields all over the web hitting "ENTER" means "start searching". Using it for opening the highlighted emails leads to many involuntary email-openings (at least for me) -- 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 307515] kmail crashed after klicking on imap account
https://bugs.kde.org/show_bug.cgi?id=307515 --- Comment #1 from b...@gmx.at --- after deleting /tmp/kdecache-* and restarting kde, kmail now starts on the first try (with only one process). -- 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 307515] kmail crashed after klicking on imap account
https://bugs.kde.org/show_bug.cgi?id=307515 b...@gmx.at changed: What|Removed |Added CC||b...@gmx.at -- 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 307515] New: kmail crashed after klicking on imap account
https://bugs.kde.org/show_bug.cgi?id=307515 Bug ID: 307515 Severity: crash Version: 4.8.5 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail crashed after klicking on imap account Classification: Unclassified OS: Linux Reporter: b...@gmx.at Hardware: Ubuntu Packages Status: NEW Component: general Product: kmail2 Application: kmail (4.8.5) KDE Platform Version: 4.8.5 (4.8.5) Qt Version: 4.8.1 Operating System: Linux 3.2.0-31-generic x86_64 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: kmail often does not show a window when opend for the first time. mostly i start it several times until a window appears. this time i just forgot about it. when the window suddenly appeared all accounts were retracted. i clicked on one account (in the folder list) to see the folders. kmail crash. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb9889037c0 (LWP 4491))] Thread 4 (Thread 0x7fb9663c8700 (LWP 11755)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fb97abf1dec in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fb97abf1f19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fb98372ae9a in start_thread (arg=0x7fb9663c8700) at pthread_create.c:308 #4 0x7fb985c5b4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7fb965ac7700 (LWP 11756)): #0 0x7fff07fff8de in ?? () #1 0x7fb97d57b15d in __GI_clock_gettime (clock_id=, tp=) at ../sysdeps/unix/clock_gettime.c:116 #2 0x7fb98650ebb4 in do_gettime (frac=0x7fb965ac6ba8, sec=0x7fb965ac6ba0) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7fb9865e6b8d in QTimerInfoList::updateCurrentTime (this=0x7fb960002860) at kernel/qeventdispatcher_unix.cpp:343 #5 0x7fb9865e6ec3 in QTimerInfoList::timerWait (this=0x7fb960002860, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #6 0x7fb9865e597c in timerSourcePrepareHelper (src=, timeout=0x7fb965ac6c5c) at kernel/qeventdispatcher_glib.cpp:136 #7 0x7fb97e4fd846 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fb97e4fdf5b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7fb97e4fe164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7fb9865e6426 in QEventDispatcherGlib::processEvents (this=0x7fb968c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #11 0x7fb9865b5c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #12 0x7fb9865b5ed7 in QEventLoop::exec (this=0x7fb965ac6dc0, flags=...) at kernel/qeventloop.cpp:204 #13 0x7fb9864b4fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #14 0x7fb9864b7fcb in QThreadPrivate::start (arg=0xe13c50) at thread/qthread_unix.cpp:298 #15 0x7fb98372ae9a in start_thread (arg=0x7fb965ac7700) at pthread_create.c:308 #16 0x7fb985c5b4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #17 0x in ?? () Thread 2 (Thread 0x7fb91cdf5700 (LWP 17976)): #0 0x7fb97e4fe155 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb9865e6426 in QEventDispatcherGlib::processEvents (this=0x7fb918c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #2 0x7fb9865b5c82 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #3 0x7fb9865b5ed7 in QEventLoop::exec (this=0x7fb91cdf4d90, flags=...) at kernel/qeventloop.cpp:204 #4 0x7fb9864b4fa7 in QThread::exec (this=) at thread/qthread.cpp:501 #5 0x7fb9865959ff in QInotifyFileSystemWatcherEngine::run (this=0x120f930) at io/qfilesystemwatcher_inotify.cpp:248 #6 0x7fb9864b7fcb in QThreadPrivate::start (arg=0x120f930) at thread/qthread_unix.cpp:298 #7 0x7fb98372ae9a in start_thread (arg=0x7fb91cdf5700) at pthread_create.c:308 #8 0x7fb985c5b4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #9 0x in ?? () Thread 1 (Thread 0x7fb9889037c0 (LWP 4491)): [KCrash Handler] #6 QMutex::lock (this=0xf09ee8) at thread/qmutex.cpp:153 #7 0x7fb977ee30fa in ?? () from /usr/lib/libsopranoclient.so.1 #8 0x7fb977ee31c9 in ?? () from /usr/lib/libsopranoclient.so.1 #9 0x7fb9864b5f9d in QThreadStorageData::set (this=0xe430a0, p=0x11ce220) at thread/qthreadstorage.cpp:165 #10 0x7fb977ee0bef in ?? () from /usr/lib/libsopranoclient.so.1 #11 0x7fb977ee0c59 in ?? () from /usr/lib/libsopranoclient.so.1 #12 0x7fb977ee022a in Soprano::Client::LocalSocketClient::connect(QString const&) () from /usr/lib/libsopranoclient.so.1 #13 0x7fb97ef3ff2e in init (for
[Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 --- Comment #40 from j.d...@netcologne.de --- I could verify my theory: - switched off all filters - in inbox - about 50 old mails reappeared w/o being moved by filters - really deleted these mails ( + ) - in inbox - no old mails showed up again (q.e.d) -- 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 306856] No reference to mail in the filter log
https://bugs.kde.org/show_bug.cgi?id=306856 Laurent Montel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.10 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/c3ab534d099f4b5da439d5c5 ||59df661e36e0e049 --- Comment #2 from Laurent Montel --- Git commit c3ab534d099f4b5da439d5c559df661e36e0e049 by Montel Laurent. Committed on 28/09/2012 at 09:19. Pushed by mlaurent into branch 'master'. Fix Bug 306856 - No reference to mail in the filter log FIXED-IN: 4.10 I just added when we start to log a message which display "subject"/"date"/"from" For me it will enough M +8-1mailfilteragent/filtermanager.cpp http://commits.kde.org/kdepim/c3ab534d099f4b5da439d5c559df661e36e0e049 -- 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
