[Bug 289831] New: Kontact crash after closing kontact with crashed korganizer

2011-12-26 Thread Johann-Nikolaus Andreae
https://bugs.kde.org/show_bug.cgi?id=289831

   Summary: Kontact crash after closing kontact with crashed
korganizer
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: johann-nikolaus.andr...@nacs.de


Application: kontact (4.8 rc1)
KDE Platform Version: 4.7.95 (4.8 RC1 (4.7.95) release 3
Qt Version: 4.8.0
Operating System: Linux 3.1.0-1.2-desktop x86_64
Distribution: openSUSE 12.1 (x86_64)

-- Information about the crash:
- What I was doing when the application crashed:
Korganizer was crashed (Bug 289830).
Kontact still running.
To use korganizer in kontact closing kontact for restart.
kontact crash.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0x7ffdbe8a1760 (LWP 5501))]

Thread 3 (Thread 0x7ffda62ea700 (LWP 5503)):
#0  0x7ffdb66a2e6c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7ffdbb0c8c12 in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x7ffdbba671a0) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495
#2  0x7ffdbb0c8c49 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at
../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618
#3  0x7ffdb669ef05 in start_thread () from /lib64/libpthread.so.0
#4  0x7ffdbbdb853d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ffda59d1700 (LWP 5504)):
#0  0x7ffdbbdaf423 in poll () from /lib64/libc.so.6
#1  0x7ffdb618fa98 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7ffdb618ff59 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ffdbc526946 in QEventDispatcherGlib::processEvents (this=0x7727b0,
flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426
#4  0x7ffdbc4f6672 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#5  0x7ffdbc4f68c7 in QEventLoop::exec (this=0x7ffda59d0e20, flags=...) at
kernel/qeventloop.cpp:204
#6  0x7ffdbc3f7537 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#7  0x7ffdbc3fa55b in QThreadPrivate::start (arg=0x771dc0) at
thread/qthread_unix.cpp:298
#8  0x7ffdb669ef05 in start_thread () from /lib64/libpthread.so.0
#9  0x7ffdbbdb853d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ffdbe8a1760 (LWP 5501)):
[KCrash Handler]
#6  0x7ffdbbd13d95 in raise () from /lib64/libc.so.6
#7  0x7ffdbbd152ab in abort () from /lib64/libc.so.6
#8  0x7ffdbbd4dece in __libc_message () from /lib64/libc.so.6
#9  0x7ffdbbd53c06 in malloc_printerr () from /lib64/libc.so.6
#10 0x7ffdb8b72ded in qDeleteAllQListNode*::const_iterator
(end=optimized out, begin=optimized out) at
/usr/include/QtCore/qalgorithms.h:322
#11 qDeleteAllQListNode*  (c=...) at /usr/include/QtCore/qalgorithms.h:330
#12 Akonadi::EntityTreeModel::~EntityTreeModel (this=0xce6ee0,
__in_chrg=optimized out) at
/usr/src/debug/kdepimlibs-4.7.95/akonadi/entitytreemodel.cpp:79
#13 0x7ffdb8b72e79 in Akonadi::EntityTreeModel::~EntityTreeModel
(this=0xce6ee0, __in_chrg=optimized out) at
/usr/src/debug/kdepimlibs-4.7.95/akonadi/entitytreemodel.cpp:83
#14 0x7ffdbc509e05 in QObjectPrivate::deleteChildren (this=0xc46c40) at
kernel/qobject.cpp:1917
#15 0x7ffdbc51006c in QObject::~QObject (this=0xc85820,
__in_chrg=optimized out) at kernel/qobject.cpp:927
#16 0x7ffd60f765ed in KMKernel::~KMKernel (this=0xc85820,
__in_chrg=optimized out) at
/usr/src/debug/kdepim-4.7.95/kmail/kmkernel.cpp:226
#17 0x7ffd60f76759 in KMKernel::~KMKernel (this=0xc85820,
__in_chrg=optimized out) at
/usr/src/debug/kdepim-4.7.95/kmail/kmkernel.cpp:236
#18 0x7ffd612dbd45 in KMailPart::~KMailPart (this=0x8e13b0,
__in_chrg=optimized out, __vtt_parm=optimized out) at
/usr/src/debug/kdepim-4.7.95/kmail/kmail_part.cpp:138
#19 0x7ffd612dbe39 in KMailPart::~KMailPart (this=0x8e13b0,
__in_chrg=optimized out, __vtt_parm=optimized out) at
/usr/src/debug/kdepim-4.7.95/kmail/kmail_part.cpp:140
#20 0x7ffdbe09420e in KontactInterface::Plugin::~Plugin (this=0xa660f0,
__vtt_parm=optimized out, __in_chrg=optimized out) at
/usr/src/debug/kdepimlibs-4.7.95/kontactinterface/plugin.cpp:90
#21 0x7ffd621734ef in KMailPlugin::~KMailPlugin (this=0xa660f0,
__in_chrg=optimized out, __vtt_parm=optimized out) at
/usr/src/debug/kdepim-4.7.95/kontact/plugins/kmail/kmail_plugin.cpp:159
#22 0x7ffd62173519 in KMailPlugin::~KMailPlugin (this=0xa660f0,
__in_chrg=optimized out, __vtt_parm=optimized out) at
/usr/src/debug/kdepim-4.7.95/kontact/plugins/kmail/kmail_plugin.cpp:163
#23 0x7ffdbe4cc107 in Kontact::MainWindow::~MainWindow (this=0x76cda0,
__in_chrg=optimized out, __vtt_parm=optimized out) at
/usr/src/debug/kdepim-4.7.95/kontact/src/mainwindow.cpp:288
#24 0x7ffdbe4cc269 in 

[Bug 289832] New: kmail show wrong mail

2011-12-26 Thread Johann-Nikolaus Andreae
https://bugs.kde.org/show_bug.cgi?id=289832

   Summary: kmail show wrong mail
   Product: kmail2
   Version: Git (master)
  Platform: openSUSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
AssignedTo: kdepim-bugs@kde.org
ReportedBy: johann-nikolaus.andr...@nacs.de


Version:   Git (master) (using Devel) 
OS:Linux

After deliting one mail the mail disapeard from the list.
clicking on the next mail there ist no contend of the mail.
the mail after the next mail has the content of the next mail.

This is happend in quickview an open the mail.

Restart kontact fix the list until deliting the next mail.

Reproducible: Sometimes

Steps to Reproduce:
Delete some mail from local folder (POP).


Expected Results:  
List points to right mail.

OS: Linux (x86_64) release 3.1.0-1.2-desktop
Compiler: gcc

-- 
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 289844] Akregator forgets pane sizes when launched as part of the KDE session

2011-12-26 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=289844


Christoph Feck christ...@maxiom.de changed:

   What|Removed |Added

  Component|general |general
Version|4.7 |unspecified
 AssignedTo|unassigned-b...@kde.org |kdepim-bugs@kde.org
Product|kde |akregator




-- 
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 289848] New: Kmail 2 extremly slow while syncing and crashes on exit

2011-12-26 Thread Uriel.home
https://bugs.kde.org/show_bug.cgi?id=289848

   Summary: Kmail 2 extremly slow while syncing and crashes on
exit
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: uriel.h...@gmx.net


Application: kontact (4.7.3)
KDE Platform Version: 4.7.3 (4.7.3)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-15-generic-pae i686
Distribution: Ubuntu 11.10

-- Information about the crash:
Additional information: Kmail is extremly slow and do not finish the syncing
process. Most of the mails will not be shown when I select one mail from the
list. After closing the app the bugtracker appears after a while ('bout two
minutes). So Kmail is unusable this way.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0xb2803730 (LWP 4730))]

Thread 4 (Thread 0xb1377b70 (LWP 4731)):
#0  0xb789b424 in __kernel_vsyscall ()
#1  0xb3dc9a5c in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:169
#2  0xb622acfc in __pthread_cond_wait (cond=0xb60f3430, mutex=0xb60f3418) at
forward.c:139
#3  0xb59d2883 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xb59d299f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb3dc5d31 in start_thread (arg=0xb1377b70) at pthread_create.c:304
#6  0xb621d0ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 3 (Thread 0xb0a4eb70 (LWP 4736)):
#0  0xb3da8d10 in __GI_clock_gettime (clock_id=1, tp=0xb0a4e098) at
../sysdeps/unix/clock_gettime.c:116
#1  0xb6f3b7d5 in do_gettime (frac=0xb0a4e090, sec=0xb0a4e088) at
tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0xb700e4b6 in QTimerInfoList::updateCurrentTime (this=0x862cbec) at
kernel/qeventdispatcher_unix.cpp:339
#4  0xb700e086 in timerSourceCheckHelper (src=0x862cbb8) at
kernel/qeventdispatcher_glib.cpp:150
#5  timerSourceCheckHelper (src=0x862cbb8) at
kernel/qeventdispatcher_glib.cpp:144
#6  0xb3ceef24 in g_main_context_check () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb3cef8f0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb3cefc2a in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb700db37 in QEventDispatcherGlib::processEvents (this=0x862b270,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#10 0xb6fde1dd in QEventLoop::processEvents (this=0xb0a4e2c0, flags=...) at
kernel/qeventloop.cpp:149
#11 0xb6fde421 in QEventLoop::exec (this=0xb0a4e2c0, flags=...) at
kernel/qeventloop.cpp:201
#12 0xb6ee190b in QThread::exec (this=0x862ac50) at thread/qthread.cpp:498
#13 0xb6ee19fb in QThread::run (this=0x862ac50) at thread/qthread.cpp:565
#14 0xb6ee47b3 in QThreadPrivate::start (arg=0x862ac50) at
thread/qthread_unix.cpp:331
#15 0xb3dc5d31 in start_thread (arg=0xb0a4eb70) at pthread_create.c:304
#16 0xb621d0ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 2 (Thread 0xae018b70 (LWP 4980)):
#0  0xb3da8d10 in __GI_clock_gettime (clock_id=1, tp=0xae018008) at
../sysdeps/unix/clock_gettime.c:116
#1  0xb6f3b7d5 in do_gettime (frac=0xae018000, sec=0xae017ff8) at
tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0xb700e4b6 in QTimerInfoList::updateCurrentTime (this=0x8e02934) at
kernel/qeventdispatcher_unix.cpp:339
#4  0xb700e80a in QTimerInfoList::timerWait (this=0x8e02934, tm=...) at
kernel/qeventdispatcher_unix.cpp:442
#5  0xb700d053 in timerSourcePrepareHelper (src=optimized out,
timeout=0xae01810c) at kernel/qeventdispatcher_glib.cpp:136
#6  0xb700d0ed in timerSourcePrepare (source=0x8e02900, timeout=optimized
out) at kernel/qeventdispatcher_glib.cpp:169
#7  0xb3cee88c in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#8  0xb3cef637 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb3cefc2a in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb700db37 in QEventDispatcherGlib::processEvents (this=0x91d5fa0,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#11 0xb6fde1dd in QEventLoop::processEvents (this=0xae018290, flags=...) at
kernel/qeventloop.cpp:149
#12 0xb6fde421 in QEventLoop::exec (this=0xae018290, flags=...) at
kernel/qeventloop.cpp:201
#13 0xb6ee190b in QThread::exec (this=0x8c16d30) at thread/qthread.cpp:498
#14 0xb6fbee2d in QInotifyFileSystemWatcherEngine::run (this=0x8c16d30) at
io/qfilesystemwatcher_inotify.cpp:248
#15 0xb6ee47b3 in QThreadPrivate::start (arg=0x8c16d30) at
thread/qthread_unix.cpp:331
#16 0xb3dc5d31 in start_thread (arg=0xae018b70) at pthread_create.c:304
#17 0xb621d0ce in 

[Bug 289854] New: KMail crashes when adding a shortcut and using it

2011-12-26 Thread neikokz+kbugs
https://bugs.kde.org/show_bug.cgi?id=289854

   Summary: KMail crashes when adding a shortcut and using it
   Product: kmail2
   Version: 4.8
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: UI
AssignedTo: kdepim-bugs@kde.org
ReportedBy: neikokz+kb...@gmail.com


Version:   4.8 (using KDE 4.7.3) 
OS:Linux

KMail crashes when adding a shortcut and using it.

Reproducible: Always

Steps to Reproduce:
(Taking into account you already have a mail account with folders added)
1- Right click a folder.
2- Right click Mark all mails as read.
3- Click Configure shortcut.
4- Add a shortcut (I added Ctrl+R personally, I don't know whether it will
crash with other combinations as well).
5- OK
6- Hit the shortcut.

KMail will crash, but only the first time the shortcut is used, the next times
you use it it won't crash.

Actual Results:  
.

Expected Results:  
.

-- 
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 289855] New: kontact crash after quitting

2011-12-26 Thread Andreas K . Huettel
https://bugs.kde.org/show_bug.cgi?id=289855

   Summary: kontact crash after quitting
   Product: kontact
   Version: unspecified
  Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: dilfri...@gentoo.org


Application: kontact (4.8 rc1)
KDE Platform Version: 4.7.95 (4.8 RC1 (4.7.95) (Compiled from sources)
Qt Version: 4.8.0
Operating System: Linux 3.0.6-gentoo x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
Quitting kontact

- Unusual behavior I noticed:
kmail part was not displaying my inbox content (folder looked empty, but the
e-mails were visible in akonadiconsole browser) - wanted to restart kontct to
see if this fixes the problem

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0x7fbffee0b760 (LWP 1206))]

Thread 3 (Thread 0x7fbfe6fba700 (LWP 1207)):
#0  pthread_cond_wait () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7fbffb60d0b4 in scavengerThread (this=0x7fbffbffa100) at
wtf/FastMalloc.cpp:2495
#2  WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7fbffbffa100) at
wtf/FastMalloc.cpp:1618
#3  0x7fbff6c8cd5c in start_thread (arg=0x7fbfe6fba700) at
pthread_create.c:301
#4  0x7fbffc34a2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7fbfe67b9700 (LWP 1208)):
#0  0x7fbffc341513 in *__GI___poll (fds=optimized out, nfds=optimized
out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7fbff5cecdf3 in g_main_context_poll (n_fds=1, fds=0x212b0a0,
timeout=-1, context=0x212ad20, priority=optimized out) at gmain.c:3402
#2  g_main_context_iterate (context=0x212ad20, block=1, dispatch=1,
self=optimized out) at gmain.c:3084
#3  0x7fbff5ced2c1 in g_main_context_iteration (context=0x212ad20,
may_block=1) at gmain.c:3152
#4  0x7fbffd75b316 in QEventDispatcherGlib::processEvents (this=0x212ae10,
flags=optimized out) at kernel/qeventdispatcher_glib.cpp:426
#5  0x7fbffd72afd2 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#6  0x7fbffd72b28d in QEventLoop::exec (this=0x7fbfe67b8e20, flags=...) at
kernel/qeventloop.cpp:204
#7  0x7fbffd627d48 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#8  0x7fbffd62a3cb in QThreadPrivate::start (arg=0x212a4c0) at
thread/qthread_unix.cpp:298
#9  0x7fbff6c8cd5c in start_thread (arg=0x7fbfe67b9700) at
pthread_create.c:301
#10 0x7fbffc34a2dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7fbffee0b760 (LWP 1206)):
[KCrash Handler]
#6  0x7fbffc2a5925 in *__GI_raise (sig=optimized out) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x7fbffc2a6da6 in *__GI_abort () at abort.c:92
#8  0x7fbffc2e0ae3 in __libc_message (do_abort=2, fmt=0x7fbffc3be7a8 ***
glibc detected *** %s: %s: 0x%s ***\n) at
../sysdeps/unix/sysv/linux/libc_fatal.c:186
#9  0x7fbffc2e5f76 in malloc_printerr (action=3, str=0x7fbffc3bb9a4
free(): invalid pointer, ptr=optimized out) at malloc.c:6283
#10 0x7fbff90c9960 in qDeleteAllQListNode*::const_iterator (begin=...,
end=...) at /usr/include/qt4/QtCore/qalgorithms.h:322
#11 0x7fbff90c9082 in qDeleteAllQListNode*  (c=optimized out) at
/usr/include/qt4/QtCore/qalgorithms.h:330
#12 Akonadi::EntityTreeModel::~EntityTreeModel (this=0x244aef0,
__in_chrg=optimized out) at
/var/tmp/portage/kde-base/kdepimlibs-4.7.95/work/kdepimlibs-4.7.95/akonadi/entitytreemodel.cpp:79
#13 0x7fbff90c9159 in Akonadi::EntityTreeModel::~EntityTreeModel
(this=0x244aef0, __in_chrg=optimized out) at
/var/tmp/portage/kde-base/kdepimlibs-4.7.95/work/kdepimlibs-4.7.95/akonadi/entitytreemodel.cpp:83
#14 0x7fbffd73f204 in QObjectPrivate::deleteChildren (this=0x23feaa0) at
kernel/qobject.cpp:1908
#15 0x7fbffd742af0 in QObject::~QObject (this=0x23e5010,
__in_chrg=optimized out) at kernel/qobject.cpp:927
#16 0x7fbfa2f6a0ae in KMKernel::~KMKernel (this=0x23e5010,
__in_chrg=optimized out) at
/var/tmp/portage/kde-base/kmail-4.7.95/work/kmail-4.7.95/kmail/kmkernel.cpp:226
#17 0x7fbfa2f6a1d9 in KMKernel::~KMKernel (this=0x23e5010,
__in_chrg=optimized out) at
/var/tmp/portage/kde-base/kmail-4.7.95/work/kmail-4.7.95/kmail/kmkernel.cpp:236
#18 0x7fbfa32ba687 in KMailPart::~KMailPart (this=0x227f9b0,
__in_chrg=optimized out, __vtt_parm=optimized out) at
/var/tmp/portage/kde-base/kmail-4.7.95/work/kmail-4.7.95/kmail/kmail_part.cpp:138
#19 0x7fbfa32ba779 in KMailPart::~KMailPart (this=0x227f9b0,
__in_chrg=optimized out, __vtt_parm=optimized out) at
/var/tmp/portage/kde-base/kmail-4.7.95/work/kmail-4.7.95/kmail/kmail_part.cpp:140
#20 0x7fbffe600a6e in KontactInterface::Plugin::~Plugin (this=0x2254810,

[Bug 201770] irregular and sometimes unpredictable behaviour in message list when selecting and deleting messages

2011-12-26 Thread Falk Krönert
https://bugs.kde.org/show_bug.cgi?id=201770





--- Comment #4 from Falk Krönert FalkKroenert gmx net  2011-12-26 13:32:55 ---
Using Kontact 4.7.4 on KDE 4.7.4 (openSUSE 11.4 64bit) the bug is still
present.
But I can at least narrow it down a bit:
This only happens if you switch to a mail folder via the folder tree without
giving it focus directly (with a mouse click or the tab key). If you then start
shift-selecting mails and delete them, the selection model seems to have been
updated correctly and a random selection of mails is deleted.
Most often this will happen for a spam folder which has no previous read
messages.

-- 
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 289693] Kmail crash on exit

2011-12-26 Thread Colin J Thomson
https://bugs.kde.org/show_bug.cgi?id=289693


Colin J Thomson co...@g6avk.demon.co.uk changed:

   What|Removed |Added

 CC||co...@g6avk.demon.co.uk




-- 
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 283037] Unable to connect to akonadi after laptop resume

2011-12-26 Thread Szymon Stefanek
https://bugs.kde.org/show_bug.cgi?id=283037


Szymon Stefanek pra...@kvirc.net changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1




--- Comment #30 from Szymon Stefanek pragma kvirc net  2011-12-26 17:26:16 ---
This bug persists also in the 4.8 packages (kubuntu).
KMail doesn't show message contents at all: it just sits there with Retrieving
folder contents. In akonadiconsole there is moderate traffic and
mysql+akonadi+resources are taking an average of 200% of CPU (two cores of a
quadcore system).

 2397 pragma20   0  384m 140m 3940 S  135  1.8 549:58.47 mysqld 
20992 pragma20   0  371m 112m  18m S   49  1.4 172:16.93 akonadi_mixedma
20994 pragma20   0  631m 213m  25m S   18  2.7  64:45.17 akonadi_nepomuk

-- 
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 183004] Kmail's threaded view sometimes not sorted correclty

2011-12-26 Thread Roland Leißa
https://bugs.kde.org/show_bug.cgi?id=183004


Roland Leißa sf_k...@web.de changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||FIXED




--- Comment #5 from Roland Leißa sf_knue web de  2011-12-26 17:29:01 ---
Hi Bernd,

I'm currently not using the threaded view anymore (as I'm preferring a flat
view). However, I played a bit with the threaded view again and I didn't
noticed any problems. So I guess you can mark it as fixed.

-- 
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 283037] Unable to connect to akonadi after laptop resume

2011-12-26 Thread Szymon Stefanek
https://bugs.kde.org/show_bug.cgi?id=283037





--- Comment #31 from Szymon Stefanek pragma kvirc net  2011-12-26 17:37:16 ---
Ops.. hit submit too fast. Packages of 4.7.4 and not 4.8.

-- 
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 263153] kmail doesn't allow (or can't?) reply to mails saved in mbox format

2011-12-26 Thread fmonera
https://bugs.kde.org/show_bug.cgi?id=263153


fmon...@gmail.com changed:

   What|Removed |Added

 CC||fmon...@gmail.com




--- Comment #1 from  fmonera gmail com  2011-12-26 18:30:25 ---
It happens here too. It worked in the past versions (I use this feature a lot
in my productivity system).

I am using kmail 4.7.2 from Kubuntu.

-- 
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 289879] New: kmail crashed while reading email

2011-12-26 Thread Alan House
https://bugs.kde.org/show_bug.cgi?id=289879

   Summary: kmail crashed while reading email
   Product: kontact
   Version: unspecified
  Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: alan.ho...@sftdev.com


Application: kontact (4.7.4)
KDE Platform Version: 4.7.4 (4.7.4) (Compiled from sources)
Qt Version: 4.8.0
Operating System: Linux 3.1.6-1.fc16.x86_64 x86_64
Distribution: Fedora release 16 (Verne)

-- Information about the crash:
- What I was doing when the application crashed:

This time it crashes when reading the same email (walgreen's new ad).

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fb2cb533840 (LWP 16956))]

Thread 7 (Thread 0x7fb2beaa3700 (LWP 16957)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165
#1  0x0039ef9973cc in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x39f0390f80) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495
#2  0x0039ef9974f9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at
../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618
#3  0x0039c5e07d90 in start_thread (arg=0x7fb2beaa3700) at
pthread_create.c:309
#4  0x0039c52ef48d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 6 (Thread 0x7fb2be1a2700 (LWP 16958)):
#0  0x0039c52e6af3 in __GI___poll (fds=optimized out, nfds=optimized
out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x0039c7e44f88 in g_main_context_poll (n_fds=1, fds=0x7fb2b80013e0,
priority=optimized out, timeout=2705, context=0x7fb2b80009a0) at gmain.c:3386
#2  g_main_context_iterate (context=0x7fb2b80009a0, block=optimized out,
dispatch=1, self=optimized out) at gmain.c:3068
#3  0x0039c7e4544c in g_main_context_iteration (context=0x7fb2b80009a0,
may_block=1) at gmain.c:3136
#4  0x0039ccfa7db6 in QEventDispatcherGlib::processEvents
(this=0x7fb2b80008c0, flags=optimized out) at
kernel/qeventdispatcher_glib.cpp:426
#5  0x0039ccf78172 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#6  0x0039ccf783c7 in QEventLoop::exec (this=0x7fb2be1a1d40, flags=...) at
kernel/qeventloop.cpp:204
#7  0x0039cce78b27 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#8  0x0039cce7bb6b in QThreadPrivate::start (arg=0xe04170) at
thread/qthread_unix.cpp:298
#9  0x0039c5e07d90 in start_thread (arg=0x7fb2be1a2700) at
pthread_create.c:309
#10 0x0039c52ef48d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 5 (Thread 0x7fb271a18700 (LWP 17163)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216
#1  0x0039cce7bfdf in wait (time=3, this=0x7fb26c005ec0) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=optimized out, mutex=0x7fb26c005e68,
time=3) at thread/qwaitcondition_unix.cpp:158
#3  0x0039cce6f5af in QThreadPoolThread::run (this=0x7fb26c006140) at
concurrent/qthreadpool.cpp:141
#4  0x0039cce7bb6b in QThreadPrivate::start (arg=0x7fb26c006140) at
thread/qthread_unix.cpp:298
#5  0x0039c5e07d90 in start_thread (arg=0x7fb271a18700) at
pthread_create.c:309
#6  0x0039c52ef48d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 4 (Thread 0x7fb270a16700 (LWP 17165)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216
#1  0x0039cce7bfdf in wait (time=3, this=0x7fb26c005ec0) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=optimized out, mutex=0x7fb26c005e68,
time=3) at thread/qwaitcondition_unix.cpp:158
#3  0x0039cce6f5af in QThreadPoolThread::run (this=0x7fb26c00e150) at
concurrent/qthreadpool.cpp:141
#4  0x0039cce7bb6b in QThreadPrivate::start (arg=0x7fb26c00e150) at
thread/qthread_unix.cpp:298
#5  0x0039c5e07d90 in start_thread (arg=0x7fb270a16700) at
pthread_create.c:309
#6  0x0039c52ef48d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 3 (Thread 0x7fb26bdf7700 (LWP 17166)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216
#1  0x0039cce7bfdf in wait (time=3, this=0x7fb26c005ec0) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=optimized out, mutex=0x7fb26c005e68,
time=3) at thread/qwaitcondition_unix.cpp:158
#3  0x0039cce6f5af in QThreadPoolThread::run (this=0x7fb26c0121f0) at
concurrent/qthreadpool.cpp:141
#4  0x0039cce7bb6b in QThreadPrivate::start (arg=0x7fb26c0121f0) at

[Bug 289881] New: KMail Import does not show import path other than existing mail dir

2011-12-26 Thread Michael Soibelman
https://bugs.kde.org/show_bug.cgi?id=289881

   Summary: KMail Import does not show import path other than
existing mail dir
   Product: kmail2
   Version: 4.7
  Platform: openSUSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
AssignedTo: kdepim-bugs@kde.org
ReportedBy: michael.soibelm...@gmail.com


Created an attachment (id=67139)
 -- (http://bugs.kde.org/attachment.cgi?id=67139)
snapshot of import dialog

Version:   4.7 (using Devel) 
OS:Linux

Using the import function to import old mail I try to import using 'Import
Kmail MailDirs and Folder Structure'. But when I click the 'folder' icon to
navigate to my old mail folder I only see the new maildirs from this
installation.  I can not navigate out to any other folders.  Only 'Local
Folders' shows up.  No parent directory or any other folder selection is
available.  I've stored my old emails on an external drive and can not navigate
to that.  I can not even navigate to ANY folder outside of 'Local Folders'. 
This is version 4.7.4 on openSUSE-12.1.

Reproducible: Always

Steps to Reproduce:
Try to import but no navigation to anywhere outside of the 'local folders' is
possible.  No '..' to navigate 'up' to parent directory or anywhere outside of
existing folders is possible


Expected Results:  
Show navigation to 'outside' of folders created at installation.

-- 
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 289693] Kmail crash on exit

2011-12-26 Thread Markus S .
https://bugs.kde.org/show_bug.cgi?id=289693


Markus S. marku...@kdemail.net changed:

   What|Removed |Added

 CC||marku...@kdemail.net




-- 
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 289693] Kmail crash on exit

2011-12-26 Thread Markus S .
https://bugs.kde.org/show_bug.cgi?id=289693





--- Comment #2 from Markus S. markus s kdemail net  2011-12-26 20:12:53 ---
Created an attachment (id=67140)
 -- (http://bugs.kde.org/attachment.cgi?id=67140)
New crash information added by DrKonqi

kmail (4.8 rc1) on KDE Platform 4.7.95 (4.8 RC1 (4.7.95) release 3 using Qt
4.8.0

- What I was doing when the application crashed:
Quitting KMail 2 from SC 4.8rc1 as stand-alone application.
So far the crash didn't happen again with Kontact.

-- Backtrace (Reduced):
#12 0xb53b7326 in qDeleteAllQListNode*::const_iterator (end=optimized
out, begin=optimized out) at /usr/include/QtCore/qalgorithms.h:322
#13 qDeleteAllQListNode*  (c=...) at /usr/include/QtCore/qalgorithms.h:330
#14 Akonadi::EntityTreeModel::~EntityTreeModel (this=0x81ee8c0,
__in_chrg=optimized out) at
/usr/src/debug/kdepimlibs-4.7.95/akonadi/entitytreemodel.cpp:79
#15 0xb53b73e2 in Akonadi::EntityTreeModel::~EntityTreeModel (this=0x81ee8c0,
__in_chrg=optimized out) at
/usr/src/debug/kdepimlibs-4.7.95/akonadi/entitytreemodel.cpp:83
#16 0xb6d3b731 in QObjectPrivate::deleteChildren (this=0x82c3820) at
kernel/qobject.cpp:1917

-- 
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 285999] Nepomuk Indexing Agents Have Been Disabled error at startup

2011-12-26 Thread Ekkehard Blanz
https://bugs.kde.org/show_bug.cgi?id=285999


Ekkehard Blanz ekkehard.bl...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1




--- Comment #9 from Ekkehard Blanz Ekkehard Blanz gmail com  2011-12-26 
21:12:45 ---
*** This bug has been confirmed by popular vote. ***

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- 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 289892] New: kmail 4.7.95 crash on startup

2011-12-26 Thread Balcaen John
https://bugs.kde.org/show_bug.cgi?id=289892

   Summary: kmail 4.7.95 crash on startup
   Product: kmail2
   Version: unspecified
  Platform: Mageia RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: balcaen.j...@gmail.com


Application: kmail (4.8 rc1)
KDE Platform Version: 4.7.95 (4.8 RC1 (4.7.95)
Qt Version: 4.7.4
Operating System: Linux 3.2.0-desktop-0.rc7.1.mga2 x86_64
Distribution: Mageia Cauldron

-- Information about the crash:
- What I was doing when the application crashed:
i simply start kmail and notice the crash.
It seems to crash when it start to pull imap folders.
Thoses crashes were not present in 4.7.90

The crash can be reproduced some of the time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
[Current thread is 1 (Thread 0x77f98760 (LWP 27780))]

Thread 3 (Thread 0x7fffd74a7700 (LWP 27784)):
#0  0x73432594 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fffea04aa7c in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x7fffea04aba9 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x7342eb99 in start_thread () from /lib64/libpthread.so.0
#4  0x753d10cd in clone () from /lib64/libc.so.6
#5  0x in ?? ()

Thread 2 (Thread 0x7fffd6ba6700 (LWP 27785)):
#0  0x753c40dd in read () from /lib64/libc.so.6
#1  0x7fffee120baf in read (__nbytes=16, __buf=0x7fffd6ba5ca0,
__fd=optimized out) at /usr/include/bits/unistd.h:45
#2  g_wakeup_acknowledge (wakeup=0x66f5c0) at gwakeup.c:212
#3  0x7fffee0e618d in g_main_context_check (context=0xa9e440,
max_priority=2147483647, fds=0xc1e730, n_fds=1) at gmain.c:2955
#4  0x7fffee0e in g_main_context_iterate (dispatch=1, block=optimized
out, context=0xa9e440, self=optimized out) at gmain.c:3118
#5  g_main_context_iterate (context=0xa9e440, block=optimized out,
dispatch=1, self=optimized out) at gmain.c:3058
#6  0x7fffee0e67f4 in g_main_context_iteration (context=0xa9e440,
may_block=1) at gmain.c:3182
#7  0x75d1eee6 in QEventDispatcherGlib::processEvents (this=0xc25440,
flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424
#8  0x75cf3412 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#9  0x75cf360f in QEventLoop::exec (this=0x7fffd6ba5e20, flags=...) at
kernel/qeventloop.cpp:201
#10 0x75c0af9f in QThread::exec (this=optimized out) at
thread/qthread.cpp:498
#11 0x75c0d9e5 in QThreadPrivate::start (arg=0xbffc90) at
thread/qthread_unix.cpp:331
#12 0x7342eb99 in start_thread () from /lib64/libpthread.so.0
#13 0x753d10cd in clone () from /lib64/libc.so.6
#14 0x in ?? ()

Thread 1 (Thread 0x77f98760 (LWP 27780)):
[KCrash Handler]
#6  Akonadi::CollectionStatisticsDelegate::paint (this=optimized out,
painter=0x7fff9790, option=..., index=...) at
/usr/src/debug/kdepimlibs-4.7.95/akonadi/collectionstatisticsdelegate.cpp:223
#7  0x7670996b in QListView::paintEvent (this=0xd149e0, e=optimized
out) at itemviews/qlistview.cpp:1044
#8  0x762320e8 in QWidget::event (this=0xd149e0, event=0x7fffa470)
at kernel/qwidget.cpp:8441
#9  0x765d6716 in QFrame::event (this=0xd149e0, e=0x7fffa470) at
widgets/qframe.cpp:557
#10 0x766e690b in QAbstractItemView::viewportEvent (this=0xd149e0,
event=0x7fffa470) at itemviews/qabstractitemview.cpp:1628
#11 0x75cf4398 in
QCoreApplicationPrivate::sendThroughObjectEventFilters (this=optimized out,
receiver=0xcec870, event=0x7fffa470) at kernel/qcoreapplication.cpp:902
#12 0x761e1a2f in notify_helper (e=0x7fffa470, receiver=0xcec870,
this=0x66dfd0) at kernel/qapplication.cpp:4477
#13 QApplicationPrivate::notify_helper (this=0x66dfd0, receiver=0xcec870,
e=0x7fffa470) at kernel/qapplication.cpp:4453
#14 0x761e68f1 in QApplication::notify (this=0x7fffd690,
receiver=0xcec870, e=0x7fffa470) at kernel/qapplication.cpp:4360
#15 0x77927b46 in KApplication::notify (this=0x7fffd690,
receiver=0xcec870, event=0x7fffa470) at
/usr/src/debug/kdelibs-4.7.95/kdeui/kernel/kapplication.cpp:311
#16 0x75cf420c in QCoreApplication::notifyInternal
(this=0x7fffd690, receiver=0xcec870, event=0x7fffa470) at
kernel/qcoreapplication.cpp:787
#17 0x7622eff6 in sendSpontaneousEvent (event=0x7fffa470,
receiver=0xcec870) at ../../src/corelib/kernel/qcoreapplication.h:218
#18 QWidgetPrivate::drawWidget (this=0xd02390, pdev=0xb89c08, rgn=...,
offset=..., flags=4, sharedPainter=0x0, backingStore=0xb50f30) at
kernel/qwidget.cpp:5528
#19 0x7622fbd0 in QWidgetPrivate::paintSiblingsRecursive
(this=0xd0d850, pdev=0xb89c08, siblings=..., index=optimized out, rgn=...,
offset=..., 

[Bug 289892] kmail 4.7.95 crash on startup

2011-12-26 Thread Balcaen John
https://bugs.kde.org/show_bug.cgi?id=289892





--- Comment #1 from Balcaen John balcaen john gmail com  2011-12-27 00:22:59 
---
Not sure if it's related but i also noticed once a crash of the maildispatcher
agent

-- 
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 289892] kmail 4.7.95 crash on startup

2011-12-26 Thread Balcaen John
https://bugs.kde.org/show_bug.cgi?id=289892





--- Comment #2 from Balcaen John balcaen john gmail com  2011-12-27 00:26:04 
---
oups, i click too fast :/
I also noticed from the command line this : 

kmail2(28019)/kdepimlibs (mailtransport): Could not access Outbox.

-- 
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 289893] New: Kontact 4.7 krash on exit - every time (what in the world is going on with kontact).

2011-12-26 Thread Alan House
https://bugs.kde.org/show_bug.cgi?id=289893

   Summary: Kontact 4.7 krash on exit - every time (what in the
world is going on with kontact).
   Product: kontact
   Version: unspecified
  Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: alan.ho...@sftdev.com


Application: kontact (4.7.4)
KDE Platform Version: 4.7.4 (4.7.4) (Compiled from sources)
Qt Version: 4.8.0
Operating System: Linux 3.1.6-1.fc16.x86_64 x86_64
Distribution: Fedora release 16 (Verne)

-- Information about the crash:
- What I was doing when the application crashed:

Every time Kontact exits (even closing the task) causes a crash (k-rash). how
do I get the update if this is fixed?

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f01c9d55840 (LWP 17647))]

Thread 3 (Thread 0x7f01bd2c5700 (LWP 17648)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165
#1  0x0039ef9973cc in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x39f0390f80) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495
#2  0x0039ef9974f9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=optimized out) at
../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618
#3  0x0039c5e07d90 in start_thread (arg=0x7f01bd2c5700) at
pthread_create.c:309
#4  0x0039c52ef48d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7f01bc9c4700 (LWP 17649)):
#0  0x7fffe3bff98f in clock_gettime ()
#1  0x0039c66041f1 in __GI_clock_gettime (clock_id=1, tp=0x7f01bc9c3b00) at
../sysdeps/unix/clock_gettime.c:100
#2  0x0039cced22e4 in do_gettime (frac=0x7f01bc9c3b18, sec=0x7f01bc9c3b10)
at tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  0x0039ccfa84bd in QTimerInfoList::updateCurrentTime
(this=0x7f01b80020d0) at kernel/qeventdispatcher_unix.cpp:343
#5  0x0039ccfa81d1 in timerSourceCheckHelper (src=optimized out) at
kernel/qeventdispatcher_glib.cpp:150
#6  timerSourceCheckHelper (src=optimized out) at
kernel/qeventdispatcher_glib.cpp:144
#7  0x0039c7e44754 in g_main_context_check (context=0x7f01b80009a0,
max_priority=2147483647, fds=optimized out, n_fds=optimized out) at
gmain.c:2943
#8  0x0039c7e44fa2 in g_main_context_iterate (context=0x7f01b80009a0,
block=optimized out, dispatch=1, self=optimized out) at gmain.c:3070
#9  0x0039c7e4544c in g_main_context_iteration (context=0x7f01b80009a0,
may_block=1) at gmain.c:3136
#10 0x0039ccfa7db6 in QEventDispatcherGlib::processEvents
(this=0x7f01b80008c0, flags=optimized out) at
kernel/qeventdispatcher_glib.cpp:426
#11 0x0039ccf78172 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#12 0x0039ccf783c7 in QEventLoop::exec (this=0x7f01bc9c3d40, flags=...) at
kernel/qeventloop.cpp:204
#13 0x0039cce78b27 in QThread::exec (this=optimized out) at
thread/qthread.cpp:501
#14 0x0039cce7bb6b in QThreadPrivate::start (arg=0x1a5cfa0) at
thread/qthread_unix.cpp:298
#15 0x0039c5e07d90 in start_thread (arg=0x7f01bc9c4700) at
pthread_create.c:309
#16 0x0039c52ef48d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f01c9d55840 (LWP 17647)):
[KCrash Handler]
#6  0x0039f088686f in MailCommon::FolderTreeWidget::selectedCollections
(this=0x23fd480) at
/usr/src/debug/kdepim-4.7.4/mailcommon/foldertreewidget.cpp:237
#7  0x0039f0d2da1e in KMMainWidget::updateFolderMenu (this=0x2431a00) at
/usr/src/debug/kdepim-4.7.4/kmail/kmmainwidget.cpp:3843
#8  0x0039f0d3d093 in KMMainWidget::slotEndCheckFetchCollectionsDone
(this=0x2431a00, job=optimized out) at
/usr/src/debug/kdepim-4.7.4/kmail/kmmainwidget.cpp:437
#9  0x0039f0d3d8b8 in KMMainWidget::slotEndCheckMail (this=0x2431a00) at
/usr/src/debug/kdepim-4.7.4/kmail/kmmainwidget.cpp:390
#10 0x0039f0d40ec5 in KMMainWidget::qt_static_metacall (_o=0x2431a00,
_c=optimized out, _id=optimized out, _a=0x7fffe3b071a0) at
/usr/src/debug/kdepim-4.7.4/x86_64-redhat-linux-gnu/kmail/kmmainwidget.moc:350
#11 0x0039ccf8ccd1 in QMetaObject::activate (sender=0x22aca60, m=optimized
out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547
#12 0x0039f0cef25c in KMKernel::slotProgressItemCompletedOrCanceled
(this=0x22aca60, item=optimized out) at
/usr/src/debug/kdepim-4.7.4/kmail/kmkernel.cpp:1702
#13 0x0039f0cf91ea in KMKernel::qt_static_metacall (_o=0x22aca60,
_c=optimized out, _id=optimized out, _a=0x7fffe3b07470) at
/usr/src/debug/kdepim-4.7.4/x86_64-redhat-linux-gnu/kmail/kmkernel.moc:185
#14 

[Bug 271712] akonadi takes up 100% CPU load on an otherwise idling KDESC

2011-12-26 Thread Szymon Stefanek
https://bugs.kde.org/show_bug.cgi?id=271712





--- Comment #7 from Szymon Stefanek pragma kvirc net  2011-12-27 01:34:28 ---
The bug is still present in the kubuntu 4.7.90 (4.8 beta2) packages.

-- 
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 240287] kontact freezes when replying to messages with embedded HTML

2011-12-26 Thread Bernd Oliver Sünderhauf
https://bugs.kde.org/show_bug.cgi?id=240287


Bernd Oliver Sünderhauf pan...@kriko.org changed:

   What|Removed |Added

 CC||pan...@kriko.org




--- Comment #4 from Bernd Oliver Sünderhauf pancho kriko org  2011-12-27 
02:38:40 ---
This should be fixed now, or did I miss something?
At least I can't replicate it using kmail2 (4.8).

-- 
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 289878] KMail does not keep selected message in different sorting modes

2011-12-26 Thread Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=289878


Christoph Feck christ...@maxiom.de changed:

   What|Removed |Added

 CC||christ...@maxiom.de
  Component|general |message list
Version|4.6 |unspecified
 AssignedTo|unassigned-b...@kde.org |kdepim-bugs@kde.org
Product|kde |kmail2




-- 
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 289895] New: Reply using HTML: text-align property stripped off

2011-12-26 Thread Bernd Oliver Sünderhauf
https://bugs.kde.org/show_bug.cgi?id=289895

   Summary: Reply using HTML: text-align property stripped off
   Product: kmail2
   Version: 4.8
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: pan...@kriko.org


Version:   4.8
OS:Linux

When replying, the following (quoted-printable) HTML paragraph :
  P style=3DTEXT-ALIGN: centerFoo/P
is stripped off the text-align property, just as well as the following (8bit)
table cell (created by PHPMailer):
  td valign=top style=text-align: center; font-size: 12px;Bar/td

Reproducible: Didn't try

Steps to Reproduce:
1. Create an email using HTML with CSS styles
2. Send it to yourself.
3. Reply using Kmail2.
4. View source

Actual Results:  
Paragraphs resp. table cell are standard-aligned (left)

Expected Results:  
They should be centered.

-- 
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 208778] KMail crash while reading email.

2011-12-26 Thread Matthew Dawson
https://bugs.kde.org/show_bug.cgi?id=208778


Matthew Dawson matt...@mjdsystems.ca changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||WORKSFORME




--- Comment #5 from Matthew Dawson matthew mjdsystems ca  2011-12-27 04:10:02 
---
Since I've yet to reproduce this on any recent kmail version, and with kmail 2
completely redoing the whole stack (and probably fixing this bug), I'm marking
it works for me for now.  If anyone else still has this issue on a recent
version of kmail, feel free to reopen 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 289896] New: Reply mail: additional body part stripped off

2011-12-26 Thread Bernd Oliver Sünderhauf
https://bugs.kde.org/show_bug.cgi?id=289896

   Summary: Reply mail: additional body part stripped off
   Product: kmail2
   Version: 4.8
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
AssignedTo: kdepim-bugs@kde.org
ReportedBy: pan...@kriko.org


Created an attachment (id=67144)
 -- (http://bugs.kde.org/attachment.cgi?id=67144)
Document structure with additional body part

Version:   4.8 (using Devel) 
OS:Linux

I received a (Thunderbird/9.0 created) MIME mail that consisted of an
additional plain text body part added after an attached PDF file, which is a
signature appended by the listserver.
Replying to this mail strips off the additional body part.

Reproducible: Always

Steps to Reproduce:
Reply to such a mail

Actual Results:  
The additional body part is missing

Expected Results:  
It should have been included into the quoted text of both the HTML and the
plain text version

-- 
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 289896] Reply mail: additional body part stripped off

2011-12-26 Thread Bernd Oliver Sünderhauf
https://bugs.kde.org/show_bug.cgi?id=289896





--- Comment #1 from Bernd Oliver Sünderhauf pancho kriko org  2011-12-27 
04:22:10 ---
Note:
- that this happens both if replying as HTML or not.
- that Thunderbird correctly includes the additional signature part into the
main body part

-- 
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 289829] Reply using HTML: Quoted plain text alternative isn't prefixed

2011-12-26 Thread Bernd Oliver Sünderhauf
https://bugs.kde.org/show_bug.cgi?id=289829





--- Comment #1 from Bernd Oliver Sünderhauf pancho kriko org  2011-12-27 
04:37:30 ---
Actually the plain text version doesn't only miss the quote signs  but also
loses all formatting.
Usually some transcription takes place to preserve at least some of the
formatting such as:
- append http://test.de for links
- wrap bold text in stars (*)
- wrap italics text in slashes (/)
- wrap underlined text in underscores (_)
- transcribe list items to stars resp. ordinal numbers
so at display time some of the formatting can be restored.

Actually Kmail does have the functionality to do so when replying to a
text-only message - buggy but better than nothing.

-- 
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 289898] New: Reply using HTML: links are styled underlined

2011-12-26 Thread Bernd Oliver Sünderhauf
https://bugs.kde.org/show_bug.cgi?id=289898

   Summary: Reply using HTML: links are styled underlined
   Product: kmail2
   Version: 4.8
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
AssignedTo: kdepim-bugs@kde.org
ReportedBy: pan...@kriko.org


Version:   4.8 (using Devel) 
OS:Linux

When replying a HTML message, a simple a href=xyzFoo/a link is
unnecessarily styled with underlining and a specified color:
a href=xyzspan style= text-decoration: underline;
color:#0057ae;Foo/span/a

Reproducible: Always

Steps to Reproduce:
Create a simple HTML email with a link

Actual Results:  
The link is added some styling properties

Expected Results:  
It should be just left as is

-- 
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 289901] New: Conflict Resolution Dialog is hard to understand and to get rid of

2011-12-26 Thread Szymon Stefanek
https://bugs.kde.org/show_bug.cgi?id=289901

   Summary: Conflict Resolution Dialog is hard to understand and
to get rid of
   Product: kmail2
   Version: 4.8
  Platform: Ubuntu Packages
OS/Version: Linux
Status: NEW
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: pra...@kvirc.net


Version:   4.8 (using Devel) 
OS:Linux

For a common user the conflict resolution dialog is senseless and rather
scary. I myself (not a newbie) have no clue on which modification should be
choosen each time and in fact I pick totally at random. In real non-developer
world conflicts should either be impossibile or be resolved automatically.

With large modifications (like apply all filters to a large set of messages)
the dialog may pop up several times: there should eventually be a always pick
this choice and don't ask me again option.

Reproducible: Sometimes

Steps to Reproduce:
Apply a large set of filters to a large number of messages. Browse around while
the filtering agent is doing his job. Apply other filters, delete messages
etc... the conflict resolution dialog will eventually popup.

Actual Results:  
Conflict Resolution Dialog appears.

Expected Results:  
No conflict... or conflict automatically resolved.

-- 
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 204485] base64-encoded parts are unfilterable

2011-12-26 Thread Bernd Oliver Sünderhauf
https://bugs.kde.org/show_bug.cgi?id=204485


Bernd Oliver Sünderhauf pan...@kriko.org changed:

   What|Removed |Added

 CC||pan...@kriko.org




--- Comment #4 from Bernd Oliver Sünderhauf pancho kriko org  2011-12-27 
06:21:18 ---
There's many bugs left, but at least this one seems to be fixed in kmail2 (4.8)

-- 
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 285599] nonvisible thread of kmail crashes while kde logout

2011-12-26 Thread MK
https://bugs.kde.org/show_bug.cgi?id=285599


MK bugs...@kkk-web.de changed:

   What|Removed |Added

 CC||bugs...@kkk-web.de




-- 
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 285599] nonvisible thread of kmail crashes while kde logout

2011-12-26 Thread MK
https://bugs.kde.org/show_bug.cgi?id=285599





--- Comment #3 from MK bugs m1 kkk-web de  2011-12-27 06:46:34 ---
Created an attachment (id=67148)
 -- (http://bugs.kde.org/attachment.cgi?id=67148)
New crash information added by DrKonqi

kmail (4.7.3) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4

- What I was doing when the application crashed:

shutting down kde while kmail was still starting

-- Backtrace (Reduced):
#6  0x7ff5907f13a5 in __GI_raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x7ff5907f4b0b in __GI_abort () at abort.c:92
[...]
#11 0x7ff59175b64e in QWidgetPrivate::QWidgetPrivate (this=0x29e1880,
version=263940) at kernel/qwidget.cpp:314
#12 0x7ff591bcacaa in QDialogPrivate (this=0x29e1880) at
../../include/QtGui/private/../../../src/gui/dialogs/qdialog_p.h:77
#13 QDialog::QDialog (this=0x28fc860, parent=0x0, f=optimized out) at
dialogs/qdialog.cpp:260

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