[Bug 294441] kmail stays in offline mode, unable to send emails

2012-02-24 Thread Nenad Mikša
https://bugs.kde.org/show_bug.cgi?id=294441


Nenad Mikša dodoentertainm...@gmail.com changed:

   What|Removed |Added

 CC||dodoentertainm...@gmail.com




--- Comment #5 from Nenad Mikša DoDoEntertainment gmail com  2012-02-24 
14:31:57 ---
Same problem here with KDE 4.8.

However, it is possible to send mail. After clicking 'send' your mail goes to
your local outbox folder. Then you have to right click the outbox folder and
choose send queued messages. KMail will ask you if you want to go online, you
click go online (or whatever it's written) and your mail will be dispatched.

But this is only a workaround...

-- 
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 238361] kmail external editor composer setting not active right away

2012-02-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=238361


Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||WONTFIX




--- Comment #2 from Laurent Montel montel kde org  2012-02-24 15:03:28 ---
It's normal because otherwise we can overwrite text
I will close it as wontfix

-- 
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 294752] New: kmail crashes on exit

2012-02-24 Thread Helio Chissini de Castro
https://bugs.kde.org/show_bug.cgi?id=294752

   Summary: kmail crashes on exit
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS/Version: Linux
Status: NEW
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: he...@kde.org


Application: kmail (4.9 pre)
KDE Platform Version: 4.8.00 (4.8.0) (Compiled from sources)
Qt Version: 4.8.0
Operating System: Linux 3.2.6-3.fc16.x86_64 x86_64
Distribution: Fedora release 16 (Verne)

-- Information about the crash:
Just close application, self compiled with qt 4.8
Other KDE application not presents same behavior.

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 0x7fc21353c840 (LWP 10666))]

Thread 2 (Thread 0x7fc208291700 (LWP 10669)):
#0  0x00389bc0bae5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc217e28dd7 in WTF::TCMalloc_PageHeap::scavengerThread() () from
/opt/qt4/lib/libQtWebKit.so.4
#2  0x7fc217e283ac in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /opt/qt4/lib/libQtWebKit.so.4
#3  0x00389bc07d90 in start_thread () from /lib64/libpthread.so.0
#4  0x00389b4ef48d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc21353c840 (LWP 10666)):
[KCrash Handler]
#6  0x00389b436285 in raise () from /lib64/libc.so.6
#7  0x00389b437b9b in abort () from /lib64/libc.so.6
#8  0x7fc21cc21813 in qt_message_output (msgType=QtFatalMsg, buf=0x4cda9b8
Fatal Error: Accessed global static 'KernelPrivate *sInstance()' after
destruction. Defined at /code/kdesrc/kde/kdepim/mailcommon/mailkernel.cpp:53)
at /code/kdesrc/qt-copy/src/corelib/global/qglobal.cpp:2252
#9  0x7fc21cc21986 in qt_message(QtMsgType, const char *, typedef
__va_list_tag __va_list_tag *) (msgType=QtFatalMsg, msg=0x7fc21b0036a0 Fatal
Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d,
ap=0x7fff5252a6f8) at /code/kdesrc/qt-copy/src/corelib/global/qglobal.cpp:2298
#10 0x7fc21cc22116 in qFatal (msg=0x7fc21b0036a0 Fatal Error: Accessed
global static '%s *%s()' after destruction. Defined at %s:%d) at
/code/kdesrc/qt-copy/src/corelib/global/qglobal.cpp:2481
#11 0x7fc21afb608f in operator- (this=optimized out) at
/code/kdesrc/kde/kdepim/mailcommon/mailkernel.cpp:53
#12 MailCommon::Kernel::self () at
/code/kdesrc/kde/kdepim/mailcommon/mailkernel.cpp:69
#13 0x7fc21afa92e9 in MailCommon::FolderCollection::writeConfig
(this=0x2f43220) at /code/kdesrc/kde/kdepim/mailcommon/foldercollection.cpp:200
#14 0x7fc21afa9d11 in MailCommon::FolderCollection::~FolderCollection
(this=0x2f43220, __in_chrg=optimized out) at
/code/kdesrc/kde/kdepim/mailcommon/foldercollection.cpp:81
#15 0x7fc21afa9da9 in MailCommon::FolderCollection::~FolderCollection
(this=0x2f43220, __in_chrg=optimized out) at
/code/kdesrc/kde/kdepim/mailcommon/foldercollection.cpp:83
#16 0x7fc21afaa366 in deref (value=0x2f43220, d=0x2f36ed0) at
/opt/qt4/include/QtCore/qsharedpointer_impl.h:342
#17 deref (this=optimized out) at
/opt/qt4/include/QtCore/qsharedpointer_impl.h:336
#18 ~ExternalRefCount (this=optimized out, __in_chrg=optimized out) at
/opt/qt4/include/QtCore/qsharedpointer_impl.h:401
#19 ~QSharedPointer (this=optimized out, __in_chrg=optimized out) at
/opt/qt4/include/QtCore/qsharedpointer_impl.h:466
#20 QMaplong long, QSharedPointerMailCommon::FolderCollection ::freeData
(this=optimized out, x=0x2ce6030) at /opt/qt4/include/QtCore/qmap.h:651
#21 0x00389b439d4d in __cxa_finalize () from /lib64/libc.so.6
#22 0x7fc21af4f646 in __do_global_dtors_aux () from
/opt/kde/lib/libmailcommon.so.4
#23 0x7fff5252ab60 in ?? ()
#24 0x7fff5252b2e0 in ?? ()
#25 0x7fc21aff7c51 in _fini () from /opt/kde/lib/libmailcommon.so.4
#26 0x7fff5252b2e0 in ?? ()
#27 0x00389b00f79d in _dl_fini () from /lib64/ld-linux-x86-64.so.2
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Reported using DrKonqi

-- 
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 14242] import procmail filters

2012-02-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=14242





--- Comment #7 from Laurent Montel montel kde org  2012-02-24 15:53:06 ---
I started to implement load procmail filter in 4.9

-- 
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 283682] KMail duplicates filtered messages

2012-02-24 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=283682





--- Comment #14 from Milian Wolff mail milianw de  2012-02-24 16:02:23 ---
rightclick on (some) of my target folders in akonadiconsole shows that they all
have a remote identifier set.

I note though, that the situation has improved, I don't get as many duplicated
emails anymore as I used to before. I'll see whehter I can reproduce it at all,
maybe this is actually fixed in recent git?

-- 
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 98765] Filter logging is deactivated everytime KMail is restarted

2012-02-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=98765


Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||mon...@kde.org
 Resolution||FIXED




--- Comment #6 from Laurent Montel montel kde org  2012-02-24 16:35:44 ---
Fixed in 4.8.1

-- 
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 283682] KMail duplicates filtered messages

2012-02-24 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=283682


Christian Trippe christiande...@web.de changed:

   What|Removed |Added

 CC||christiande...@web.de




--- Comment #15 from Christian Trippe christiandehne web de  2012-02-24 
18:46:27 ---
*** Bug 282296 has been marked as a duplicate of this bug. ***

-- 
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 282296] mails appear twice in .local/share/akonadi/file_db_data

2012-02-24 Thread Christian Trippe
https://bugs.kde.org/show_bug.cgi?id=282296


Christian Trippe christiande...@web.de changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||DUPLICATE




--- Comment #4 from Christian Trippe christiandehne web de  2012-02-24 
18:46:27 ---
This only happens for filtered messages. So probably a bug with kmails filters,
so this is probably a dup of bug 283682

*** This bug has been marked as a duplicate of bug 283682 ***

-- 
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 133252] Auto expire: Mark messages read on moving to the archive folder during expire run

2012-02-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=133252


Laurent Montel mon...@kde.org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
   Version Fixed In||4.8.1
 Resolution||FIXED




--- Comment #4 from Laurent Montel montel kde org  2012-02-24 18:47:32 ---
Git commit 809871582e940fd0a92196266d7ad9159fdb376c by Montel Laurent.
Committed on 24/02/2012 at 19:46.
Pushed by mlaurent into branch 'master'.

Fix Bug 133252 - Auto expire: Mark messages read on moving to the archive
folder during expire run

FIXED-IN: 4.8.1

M  +28   -4mailcommon/expirejob.cpp
M  +2-1mailcommon/expirejob.h

http://commits.kde.org/kdepim/809871582e940fd0a92196266d7ad9159fdb376c

-- 
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 133252] Auto expire: Mark messages read on moving to the archive folder during expire run

2012-02-24 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=133252





--- Comment #5 from Laurent Montel montel kde org  2012-02-24 18:50:37 ---
Git commit 383a5411ce961d1ff1d6a7350b35d2083401e236 by Montel Laurent.
Committed on 24/02/2012 at 19:46.
Pushed by mlaurent into branch 'KDE/4.8'.

Fix Bug 133252 - Auto expire: Mark messages read on moving to the archive
folder during expire run

FIXED-IN: 4.8.1
(cherry picked from commit 809871582e940fd0a92196266d7ad9159fdb376c)

Conflicts:

mailcommon/expirejob.cpp
mailcommon/expirejob.h

M  +35   -10   mailcommon/expirejob.cpp
M  +17   -16   mailcommon/expirejob.h

http://commits.kde.org/kdepim/383a5411ce961d1ff1d6a7350b35d2083401e236

-- 
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 282296] mails appear twice in .local/share/akonadi/file_db_data

2012-02-24 Thread Hussam Al-Tayeb
https://bugs.kde.org/show_bug.cgi?id=282296





--- Comment #5 from Hussam Al-Tayeb hussam visp net lb  2012-02-24 18:55:59 
---
I still see this bug in latest 4.8 branch from git. Funny thing is it only
happens in mail that doesn't get filtered (stays in inbox folder).

-- 
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 294769] New: Kontact crashes on opening of email

2012-02-24 Thread bgodusky
https://bugs.kde.org/show_bug.cgi?id=294769

   Summary: Kontact crashes on opening of email
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: bgodu...@pcprotechs.com


Application: kontact (4.8.0)
KDE Platform Version: 4.8.00 (4.8.0)
Qt Version: 4.8.0
Operating System: Linux 3.3.0-0.rc4.git1.4.fc17.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
Opened Kontact to cheack mail. Tried to open an email and every time I click on
an email Kontact crashes. Restarted it 3 times each resulting in a crash.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166
16662:movl(%rsp), %edi
[Current thread is 1 (Thread 0x7f70b8b28880 (LWP 1654))]

Thread 10 (Thread 0x7f70ad6c9700 (LWP 1655)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166
#1  0x003c77f7e685 in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x3c78952740) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495
#2  0x003c77f7e6e9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at
../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618
#3  0x003d30e07d14 in start_thread (arg=0x7f70ad6c9700) at
pthread_create.c:309
#4  0x003d30af105d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 9 (Thread 0x7f70acdb0700 (LWP 1656)):
#0  0x003d30ae85af in __GI___poll (fds=optimized out, nfds=optimized
out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x003d30647824 in g_main_context_poll (n_fds=1, fds=0x7f70a80029c0,
timeout=5801, context=0x7f70a80009a0, priority=optimized out) at gmain.c:3412
#2  g_main_context_iterate (context=context@entry=0x7f70a80009a0,
block=block@entry=1, dispatch=dispatch@entry=1, self=error reading variable:
Unhandled dwarf expression opcode 0xfa) at gmain.c:3113
#3  0x003d30647944 in g_main_context_iteration (context=0x7f70a80009a0,
may_block=1) at gmain.c:3179
#4  0x003d397a2976 in QEventDispatcherGlib::processEvents
(this=0x7f70a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x003d3977382f in QEventLoop::processEvents
(this=this@entry=0x7f70acdafd20, flags=...) at kernel/qeventloop.cpp:149
#6  0x003d39773ab8 in QEventLoop::exec (this=0x7f70acdafd20, flags=...) at
kernel/qeventloop.cpp:204
#7  0x003d39678588 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#8  0x003d3967b4cb in QThreadPrivate::start (arg=0x212cc20) at
thread/qthread_unix.cpp:298
#9  0x003d30e07d14 in start_thread (arg=0x7f70acdb0700) at
pthread_create.c:309
#10 0x003d30af105d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 8 (Thread 0x7f7063de8700 (LWP 1667)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:218
#1  0x003d3967b927 in wait (time=3, this=0x276c5e0) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=optimized out, mutex=0x276c588, time=3) at
thread/qwaitcondition_unix.cpp:158
#3  0x003d3966f1af in QThreadPoolThread::run (this=0x277e470) at
concurrent/qthreadpool.cpp:141
#4  0x003d3967b4cb in QThreadPrivate::start (arg=0x277e470) at
thread/qthread_unix.cpp:298
#5  0x003d30e07d14 in start_thread (arg=0x7f7063de8700) at
pthread_create.c:309
#6  0x003d30af105d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 7 (Thread 0x7f7062bc2700 (LWP 1674)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:218
#1  0x003d3967b927 in wait (time=3, this=0x26512f0) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=optimized out, mutex=0x2c74548, time=3) at
thread/qwaitcondition_unix.cpp:158
#3  0x003d3966f1af in QThreadPoolThread::run (this=0x2c724d0) at
concurrent/qthreadpool.cpp:141
#4  0x003d3967b4cb in QThreadPrivate::start (arg=0x2c724d0) at
thread/qthread_unix.cpp:298
#5  0x003d30e07d14 in start_thread (arg=0x7f7062bc2700) at
pthread_create.c:309
#6  0x003d30af105d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 6 (Thread 0x7f7061aa0700 (LWP 1676)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:218
#1  0x003d3967b927 in wait (time=3, this=0x2dbd350) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=optimized out, mutex=0x2dc3018, time=3) at

[Bug 294770] New: KMail crash on opening email

2012-02-24 Thread bgodusky
https://bugs.kde.org/show_bug.cgi?id=294770

   Summary: KMail crash on opening email
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: bgodu...@pcprotechs.com


Application: kmail (4.8.0)
KDE Platform Version: 4.8.00 (4.8.0)
Qt Version: 4.8.0
Operating System: Linux 3.3.0-0.rc4.git1.4.fc17.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
Surfing the web with firefox. Opened KMail to check email. Tried to open a
newly recieved email and double clicked it to open it and KMail crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166
16662:movl(%rsp), %edi
[Current thread is 1 (Thread 0x7fb6b9879880 (LWP 1799))]

Thread 8 (Thread 0x7fb6ad90e700 (LWP 1803)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:218
#1  0x003d3967b927 in wait (time=3, this=0x118a060) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=optimized out, mutex=0x118a008, time=3) at
thread/qwaitcondition_unix.cpp:158
#3  0x003d3966f1af in QThreadPoolThread::run (this=0x119c990) at
concurrent/qthreadpool.cpp:141
#4  0x003d3967b4cb in QThreadPrivate::start (arg=0x119c990) at
thread/qthread_unix.cpp:298
#5  0x003d30e07d14 in start_thread (arg=0x7fb6ad90e700) at
pthread_create.c:309
#6  0x003d30af105d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 7 (Thread 0x7fb6a7fff700 (LWP 1810)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166
#1  0x003c77f7e685 in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x3c78952740) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495
#2  0x003c77f7e6e9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at
../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618
#3  0x003d30e07d14 in start_thread (arg=0x7fb6a7fff700) at
pthread_create.c:309
#4  0x003d30af105d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 6 (Thread 0x7fb6a77fe700 (LWP 1811)):
#0  0x003d30ae85af in __GI___poll (fds=optimized out, nfds=optimized
out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x003d30647824 in g_main_context_poll (n_fds=1, fds=0x7fb69c0029c0,
timeout=3093, context=0x7fb69c0009a0, priority=optimized out) at gmain.c:3412
#2  g_main_context_iterate (context=context@entry=0x7fb69c0009a0,
block=block@entry=1, dispatch=dispatch@entry=1, self=error reading variable:
Unhandled dwarf expression opcode 0xfa) at gmain.c:3113
#3  0x003d30647944 in g_main_context_iteration (context=0x7fb69c0009a0,
may_block=1) at gmain.c:3179
#4  0x003d397a2976 in QEventDispatcherGlib::processEvents
(this=0x7fb69c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x003d3977382f in QEventLoop::processEvents
(this=this@entry=0x7fb6a77fdd20, flags=...) at kernel/qeventloop.cpp:149
#6  0x003d39773ab8 in QEventLoop::exec (this=0x7fb6a77fdd20, flags=...) at
kernel/qeventloop.cpp:204
#7  0x003d39678588 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#8  0x003d3967b4cb in QThreadPrivate::start (arg=0x1626cc0) at
thread/qthread_unix.cpp:298
#9  0x003d30e07d14 in start_thread (arg=0x7fb6a77fe700) at
pthread_create.c:309
#10 0x003d30af105d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 5 (Thread 0x7fb6a5ae0700 (LWP 1812)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:218
#1  0x003d3967b927 in wait (time=3, this=0x1689fc0) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=optimized out, mutex=0x168b928, time=3) at
thread/qwaitcondition_unix.cpp:158
#3  0x003d3966f1af in QThreadPoolThread::run (this=0x169f3e0) at
concurrent/qthreadpool.cpp:141
#4  0x003d3967b4cb in QThreadPrivate::start (arg=0x169f3e0) at
thread/qthread_unix.cpp:298
#5  0x003d30e07d14 in start_thread (arg=0x7fb6a5ae0700) at
pthread_create.c:309
#6  0x003d30af105d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 4 (Thread 0x7fb65bfff700 (LWP 1814)):
#0  0x7fff0a1ff8f4 in ?? ()
#1  0x003d3160410d in __GI_clock_gettime (clock_id=optimized out,
tp=optimized out) at ../sysdeps/unix/clock_gettime.c:116
#2  0x003d396d0e74 in do_gettime (frac=0x7fb65bffea88, sec=0x7fb65bffea80)
at tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  

[Bug 294772] New: Akonadi IMAP/maildir resource agent writes extensively for long period after deleting a several thousand e-mails

2012-02-24 Thread Christian Burger
https://bugs.kde.org/show_bug.cgi?id=294772

   Summary: Akonadi IMAP/maildir resource agent writes extensively
for long period after deleting a several thousand
e-mails
   Product: kmail2
   Version: 4.7
  Platform: Gentoo Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: christian.bur...@gmail.com


Created an attachment (id=69073)
 -- (http://bugs.kde.org/attachment.cgi?id=69073)
decompressed about 2 megabytes of strace log

Version:   4.7 (using KDE 4.7.4) 
OS:Linux

I am using Akonadi 1.6.2 and KMail 4.7.4 on a Gentoo platform. I deleted
several thousand files in an IMAP folder (with activated disconnected feature)
and another thousand files in my local trash folder. This resulted in heavy
disk I/O about 15-20 MBytes/sec for at least 15 minutes, probably longer.

$ dstat 
total-cpu-usage -dsk/total- -net/total- ---paging-- ---system--
usr sys idl wai hiq siq| read  writ| recv  send|  in   out | int   csw
 22  10  41  26   0   0| 443k 6371k|   0 0 |   0 0 | 598   704
 38  46   0  16   0   1|   037M|   0 0 |   0 0 |1718   731
 18  17   0  64   0   1|   014M|   0 0 |   0 0 | 739   659
 28  30   0  41   0   1|   026M|   0 0 |   0 0 |1319   545
 19  22   0  58   0   0|   018M|   0 0 |   0 0 | 919   407
 23  24   0  52   0   1|   017M|   0 0 |   0 0 | 889   614
 23  23   0  53   0   1|   019M|   0 0 |   0 0 | 868   604
 29  23   0  48   0   0|   019M|   0 0 |   0 0 | 980   501
  9   7   0  83   0   1|   0  4880k|   0 0 |   0 0 | 259   171
 11   8   0  81   0   0|   0  5140k|   0 0 |   0 0 | 313   587
 17  12   0  71   0   0|   010M|   0 0 |   0 0 | 521   337
  6   5   0  89   0   0|   0  2262k|   0 0 |   0 0 | 222   270
 12   8   0  80   0   0|   0  5392k|   0 0 |   0 0 | 374   598

I traced the culprits to the Akonadi processes associated with the mail folders
from where I deleted the mails: 

Both processes were truncating (down to zero) and writing one file each over
and over again:

1.
process as shown in ps: /usr/bin/akonadi_agent_launcher
akonadi_maildir_resource akonadi_maildir_resource_2
path to heavy i/o file:
~/.config/akonadi/agent_config_akonadi_maildir_resource_2_changes.dat

2.
ps: /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_12
path: ~/.config/akonadi/agent_config_akonadi_imap_resource_12_changes.dat 

At the beginning (at least the moment when I realized something was wrong) the
latter file was about 200 KBytes and the former about 2 MBytes. The file size
was shrinking each truncate/write cycle by a small amount (around 1
kilobytes/sec). I see no need for I/O of that magnitude, just because I deleted
a huge bunch of obsolete e-mails.

Just tried to reproduce the problem and it seems that pretty much any huge
change to a mail folder will have this effect. I copied an IMAP folder of a
thousand e-mails to my local mail folder and the fun begun.

Using a SSD I am pretty sure that this behaviour will shorten the lifespan of
my disk unneccessarily. By now I have migrated the problematic files
temporarily to a classic hard disk and will stay away from huge changes in my
mail folders without a hard disk at hand.

PS: I thought Linux's disk cache would take care of situations like that, but
my HDD LED is flickering like crazy.

Reproducible: Always

Steps to Reproduce:
either
delete a huge number (more than 1000) of e-mails from one folder
or
copy a huge number of e-mails from a IMAP folder to a local mail folder

Actual Results:  
seemingly unnecessary I/O

Expected Results:  
much less I/O

I have attached an unfiltered strace from one of the processes going wild.

Maybe bug #293175 is related to mine, but the information given there is too
little to be sure.

-- 
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 194591] Adding Feed to Akregator Causes Crash [Article::title, Private, ArticleModel, SelectionController::articleHeadersAvailable]

2012-02-24 Thread Sebastián Ramírez
https://bugs.kde.org/show_bug.cgi?id=194591





--- Comment #109 from Sebastián Ramírez teo78 adinet com uy  2012-02-25 
01:13:22 ---
Created an attachment (id=69080)
 -- (http://bugs.kde.org/attachment.cgi?id=69080)
New crash information added by DrKonqi

akregator (4.7.2) on KDE Platform 4.7.2 (4.7.2) release 5 using Qt 4.7.4

- What I was doing when the application crashed:

I surf in new feeds and crash at normal use.

-- Backtrace (Reduced):
#6  0xb75ae8b4 in Akregator::Article::title (this=0x84bbf30) at
/usr/src/debug/kdepim-4.7.2/akregator/src/article.cpp:375
#7  0xb2635177 in Akregator::ArticleModel::Private::Private (this=0x8648398,
articles_=..., qq=0x0) at
/usr/src/debug/kdepim-4.7.2/akregator/src/articlemodel.cpp:76
#8  0xb263538b in Akregator::ArticleModel::ArticleModel (this=0x8450270,
articles=..., parent=0x0) at
/usr/src/debug/kdepim-4.7.2/akregator/src/articlemodel.cpp:79
#9  0xb263bae9 in Akregator::SelectionController::articleHeadersAvailable
(this=0x8271da0, job=0x84c3c30) at
/usr/src/debug/kdepim-4.7.2/akregator/src/selectioncontroller.cpp:212
#10 0xb263be25 in Akregator::SelectionController::qt_metacall (this=0x8271da0,
_c=QMetaObject::InvokeMetaMethod, _id=optimized out, _a=0xbfe044b8) at
/usr/src/debug/kdepim-4.7.2/build/akregator/src/selectioncontroller.moc:92

-- 
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 291171] Spam filtering breaks HTML / multipart mail headers on POP3 accounts

2012-02-24 Thread Szymon Stefanek
https://bugs.kde.org/show_bug.cgi?id=291171





--- Comment #8 from Szymon Stefanek pragma kvirc net  2012-02-25 01:57:12 ---
Another bit of information.
The Content-Type header is NOT broken by the spamc executable.
I have written a wrapper for it that saves the input and the output
on disk. In both I find the correct Content-Type.

-- 
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 271826] kmail does not handle message encoding properly on replies (base64 encoded multipart message)

2012-02-24 Thread sabik
https://bugs.kde.org/show_bug.cgi?id=271826


sabik j...@baum.com.au changed:

   What|Removed |Added

 CC||j...@baum.com.au




--- Comment #6 from sabik jiri baum com au  2012-02-25 04:48:56 ---
I seem to be affected by the same problem.

My messages are 8bit-encoded, and the parts are iso-latin-2, but otherwise
similar: multipart/alternative outer layer, inner layers text/plain;
charset=ISO-8859-2; format=flowed and text/html; charset=ISO-8859-2). When I
hit r for reply, the text is decoded to utf-8 but then shown in iso-latin-2.

There seems to be some interaction with the Keep original charset option, but
even when it's off, for encrypted e-mails, the problem still occurs when
replying to the whole e-mail - but not when the text is selected (so that only
the selected part is quoted).

So the work-around ends up being (a) turning off Keep original charset
(Settings | Composer | Charset) and (b) selecting the text of encrypted e-mails
before hitting r for reply.

-- 
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 271826] kmail does not handle message encoding properly on replies (base64 encoded multipart message)

2012-02-24 Thread sabik
https://bugs.kde.org/show_bug.cgi?id=271826


sabik j...@baum.com.au changed:

   What|Removed |Added

 CC||p...@baum.com.au




-- 
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