[Akonadi] [Bug 486350] New: KMail akonadi_maildir_resource crashes on manual update

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=486350

Bug ID: 486350
   Summary: KMail akonadi_maildir_resource crashes on manual
update
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: akonadi_maildir_resource (5.24.5 (23.08.5))

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.1.12-060112-generic x86_64
Windowing System: X11
Distribution: Ubuntu 24.04 LTS
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
When Kmail is configured with a lot of accounts (> 4), a lot of filters (>20)
and large mail dirs a manual check causes sometimes the crash of
akonadi_maildir_resource.
Restarting the akonadi_maildir_resource helps.

It seems there is a null pointer used (receiver=0x0) which is not checked:
#26 0x7f5aa94db94b in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55bd091cbf30) at
kernel/qcoreapplication.cpp:1821

I think this happens as race condition.

The crash can be reproduced sometimes.

-- Backtrace:
Application: christoph.thiele...@gmx.de (akonadi_maildir_resource), signal:
Segmentation fault

[KCrash Handler]
#4  0x7f5aaa09ce99 in QHash::findNode
(ahp=0x0, akey=..., this=0x40) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:945
#5  QHash::contains (akey=..., this=0x40) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:920
#6  Akonadi::AttributeStorage::hasAttribute (this=0x40, type=...) at
/usr/src/akonadi-4:23.08.5-0ubuntu3/src/core/attributestorage.cpp:69
#7  0x7f5aaa0bb570 in Akonadi::Collection::hasAttribute
(this=this@entry=0x55bd0944d5d0, type=...) at
/usr/src/akonadi-4:23.08.5-0ubuntu3/src/core/collection.cpp:163
#8  0x7f5aaa442980 in
Akonadi::Collection::hasAttribute
(this=0x55bd0944d5d0) at
/usr/src/akonadi-4:23.08.5-0ubuntu3/src/core/collection.h:595
#9  (anonymous namespace)::sortCollectionsForSync (l=..., r=...) at
/usr/src/akonadi-4:23.08.5-0ubuntu3/src/agentbase/resourcebase.cpp:855
#10 0x7f5aaa447290 in __gnu_cxx::__ops::_Iter_comp_iter::operator()::iterator,
QTypedArrayData::iterator> (__it2=..., __it1=...,
this=) at /usr/include/c++/13/bits/predefined_ops.h:158
#11 std::__unguarded_partition::iterator,
__gnu_cxx::__ops::_Iter_comp_iter > (__comp=..., __pivot=..., __last=...,
__first=...) at /usr/include/c++/13/bits/stl_algo.h:1880
#12
std::__unguarded_partition_pivot::iterator,
__gnu_cxx::__ops::_Iter_comp_iter > (__comp=..., __last=..., __first=...) at
/usr/include/c++/13/bits/stl_algo.h:1899
#13 std::__introsort_loop::iterator, int,
__gnu_cxx::__ops::_Iter_comp_iter > (__first=..., __last=...,
__depth_limit=, __comp=__comp@entry=...) at
/usr/include/c++/13/bits/stl_algo.h:1930
#14 0x7f5aaa4408d2 in
std::__sort::iterator,
__gnu_cxx::__ops::_Iter_comp_iter > (__comp=..., __last=..., __first=...) at
/usr/include/c++/13/bits/stl_algo.h:1947
#15 std::sort::iterator, bool
(*)(Akonadi::Collection const&, Akonadi::Collection const&)> (__first=...,
__last=..., __comp=0x7f5aaa442850 <(anonymous
namespace)::sortCollectionsForSync(Akonadi::Collection const&,
Akonadi::Collection const&)>) at /usr/include/c++/13/bits/stl_algo.h:4894
#16 Akonadi::ResourceBasePrivate::slotLocalListDone (this=0x55bd0942ca20,
job=) at
/usr/src/akonadi-4:23.08.5-0ubuntu3/src/agentbase/resourcebase.cpp:897
#17 0x7f5aa9512e16 in QtPrivate::QSlotObjectBase::call (a=0x7fff9c665c90,
r=0x55bd0942ca20, this=0x55bd09c61e40) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#18 doActivate (sender=0x55bd09c53200, signal_index=6,
argv=0x7fff9c665c90) at kernel/qobject.cpp:3925
#19 0x7f5aa950b697 in QMetaObject::activate
(sender=sender@entry=0x55bd09c53200, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff9c665c90)
at kernel/qobject.cpp:3985
#20 0x7f5aaa2cd266 in KJob::result (this=this@entry=0x55bd09c53200,
_t1=, _t1@entry=0x55bd09c53200, _t2=...) at
/usr/src/kcoreaddons-5.115.0-0ubuntu5/obj-x86_64-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#21 0x7f5aaa2d30eb in KJob::finishJob (this=0x55bd09c53200,
emitResult=) at
/usr/src/kcoreaddons-5.115.0-0ubuntu5/src/lib/jobs/kjob.cpp:98
#22 0x7f5aa9506343 in QObject::event (this=0x55bd09c53200,
e=0x55bd09a66070) at kernel/qobject.cpp:1347
#23 0x7f5aa996bd45 in QApplicationPrivate::notify_helper (this=, receiver=0x55bd09c53200, e=0x55bd09a66070) at
kernel/qapplication.cpp:3640
#24 0x7f5aa94d8118 in QCoreApplication::notifyInternal2
(receiver=0x55bd09c53200, event=0x55bd09a66070) at
kernel/qcoreapplication.cpp:1064
#25 0x7f5aa94d8332 in 

[Akonadi] [Bug 479806] New: maildir ressource crashes

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=479806

Bug ID: 479806
   Summary: maildir ressource crashes
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Kubuntu
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: akonadi_maildir_resource (5.20.3 (22.04.3))

Qt Version: 5.15.3
Frameworks Version: 5.104.0
Operating System: Linux 6.1.12-060112-generic x86_64
Windowing System: X11
Distribution: Ubuntu 22.04.3 LTS
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
I have a maildir ressource which crashes regulary when it is processing the
mails in it.

The crash can be reproduced every time.

-- Backtrace:
Application: christoph.thiele...@gmx.de (akonadi_maildir_resource), signal:
Segmentation fault

[KCrash Handler]
#4  0x7f45238c84da in Akonadi::Item::remoteId() const () at
/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#5  0x7f4523b8c98a in  () at
/lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5
#6  0x7f4522cf1793 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f45238da729 in Akonadi::Monitor::itemRemoved(Akonadi::Item const&)
() at /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#8  0x7f45238eb949 in
Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification
const&, QVector const&, Akonadi::Collection const&,
Akonadi::Collection const&) () at
/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#9  0x7f45238eca19 in
Akonadi::MonitorPrivate::emitNotification(QSharedPointer
const&) () at /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#10 0x7f452389d8e3 in
Akonadi::ChangeRecorderPrivate::emitNotification(QSharedPointer
const&) () at /lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#11 0x7f45238e9f7a in Akonadi::MonitorPrivate::flushPipeline() () at
/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#12 0x7f45238ea3dd in Akonadi::MonitorPrivate::dataAvailable() () at
/lib/x86_64-linux-gnu/libKF5AkonadiCore.so.5abi2
#13 0x7f4522cf1793 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f4522cf17c8 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f45237a60c0 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#16 0x7f45237abf9b in KJob::finishJob(bool) () at
/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#17 0x7f4522ce741e in QObject::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x7f452316c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x7f4522cb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f4522cbcf27 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f4522d13a67 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f4520dc7d3b in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7f4520e1d258 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7f4520dc53e3 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f4522d130b8 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x7f4522cb875b in
QEventLoop::exec(QFlags) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7f4522cc0cf4 in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x55946cf6e144 in  ()
#29 0x7f459d90 in __libc_start_call_main
(main=main@entry=0x55946cf6d780, argc=argc@entry=3,
argv=argv@entry=0x7fffd1c39c08) at ../sysdeps/nptl/libc_start_call_main.h:58
#30 0x7f459e40 in __libc_start_main_impl (main=0x55946cf6d780, argc=3,
argv=0x7fffd1c39c08, init=, fini=,
rtld_fini=, stack_end=0x7fffd1c39bf8) at ../csu/libc-start.c:392
#31 0x55946cf6e555 in  ()
[Inferior 1 (process 19292) detached]

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 283682] KMail duplicates filtered messages

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=283682

Christoph Thielecke  changed:

   What|Removed |Added

 CC||criss...@gmx.de

--- Comment #232 from Christoph Thielecke  ---
Still valid in akonadi 21.12.3 on Kubuntu 22.04.

I think akonadi should automatically handle this problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 445747] On select a email Kmail shows "Unable to retrieve item from ressource: [LRCONFLICT]

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=445747

--- Comment #1 from Christoph Thielecke  ---
Created attachment 143730
  --> https://bugs.kde.org/attachment.cgi?id=143730=edit
Warning displayed on status bar.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 445747] New: On select a email Kmail shows "Unable to retrieve item from ressource: [LRCONFLICT]

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=445747

Bug ID: 445747
   Summary: On select a email Kmail shows "Unable to retrieve item
from ressource: [LRCONFLICT]
   Product: kmail2
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
  Target Milestone: ---

SUMMARY
***
When selecting a specific email on a akonadi maildir ressource, kmail shows
"Unable to retrieve item from ressource: [LRCONFLICT] Ressource
akonadi_maildir_ressource_14 tries to modify item 325379 () (in collection 54)
with dirty payload, aborting STORE."
***


STEPS TO REPRODUCE
1. Open folder on akonadi maildir ressource
2. Select specific email

OBSERVED RESULT
kmail shows "Unable to retrieve item from ressource: [LRCONFLICT] Ressource
akonadi_maildir_ressource_14 tries to modify item 325379 () (in collection 54)
with dirty payload, aborting STORE." and the content of mail is not shown
(stays on content previous.

EXPECTED RESULT
Email content is displayed, no warning.

SOFTWARE/OS VERSIONS
Kmail version: Version 5.18.1 (21.08.1)
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
It seems clearing the cache/reindexing using akonadiconsole helps for a while.
I think there is a bug in akonadi maildir ressource causing wrong database
entries.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 415245] New: Create Maildir ressource on valid maildir could result in not showing mails

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=415245

Bug ID: 415245
   Summary: Create Maildir ressource on valid maildir could result
in not showing mails
   Product: Akonadi
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
  Target Milestone: ---

I have the problem found, when I adding a new maildir ressource for a maildir
located in my home directory (e.g. ~/MailStore/Account2), the ressource will
added but no mails are shown in ressource.

STEPS TO REPRODUCE
1. Copy maildir to home dir somewhere (e.g. ~/MailStore/Account2)
2. create new maildir ressource for the maildir copied (e.g.
~/MailStore/Account2)

OBSERVED RESULT
The ressource is added but its shown empty (no mail or folder).

A interesting thing is, that sometimes it works when I let create it on desired
location (e.g. ~/.local/share/akonadi_maildir_resource_2). When that works
fine, remove the created directory and replace the folder by a symbolic link to
the desired maildir it found the mails and folders.

Also, I can't rename the resource name (I guess it takes the name from folder
but that seem to work only on creation.

EXPECTED RESULT
The ressource is added and it shows contents (mails and folders).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.3.0-24-lowlatency #26~18.04.2-Ubuntu SMP PREEMPT Tue Nov 26
14:39:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
KDE Plasma Version: 5.12.9.1-0ubuntu0.1build1~ubuntu18.04~ppa1
KDE Frameworks Version: 5.47.0-0ubuntu1~ubuntu18.04~ppa1
Qt Version: 5.9.5

ADDITIONAL INFORMATION
Starting akonadi using "akonadictl start" shows:
org.kde.pim.akonadicontrol: "AgentManager::agentInstanceSynchronizeCollection" 
Agent instance  "akonadi_maildir_resource_2"  has no resource interface!
org.kde.pim.akonadiserver: "Cannot connect to agent instance with identifier
'akonadi_maildir_resource_2', error message: ''

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 408340] New: Kmail crashed on opening folder

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=408340

Bug ID: 408340
   Summary: Kmail crashed on opening folder
   Product: kmail2
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
  Target Milestone: ---

Application: kmail (5.7.3)

Qt Version: 5.9.5
Frameworks Version: 5.47.0
Operating System: Linux 4.18.0-17-generic x86_64
Distribution: Ubuntu 18.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I started kmail and selected a folder with unread mail. It opens the folder
(show contents on list) but on display the mail content it crashed.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f923bc88b80 (LWP 3025))]

Thread 28 (Thread 0x7f9161d7c700 (LWP 3096)):
#0  0x7f922e67d9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f921fddffb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f922e67d9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f921fddff68, cond=0x7f921fddff90) at pthread_cond_wait.c:502
#2  0x7f922e67d9f3 in __pthread_cond_wait (cond=0x7f921fddff90,
mutex=0x7f921fddff68) at pthread_cond_wait.c:655
#3  0x7f921fae95f4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f921fae9639 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7f922e6776db in start_thread (arg=0x7f9161d7c700) at
pthread_create.c:463
#6  0x7f9238d8788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7f91631fc700 (LWP 3084)):
#0  0x7f9238d760b4 in __GI___libc_read (fd=88, buf=0x7f91631fb810,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7f922ca662d0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f922ca210b7 in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f922ca21570 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f922ca216dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f92396c390b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f92396689ea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f923948722a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f923948c16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f922e6776db in start_thread (arg=0x7f91631fc700) at
pthread_create.c:463
#10 0x7f9238d8788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7f91957fa700 (LWP 3060)):
#0  0x7f9238d7abf9 in __GI___poll (fds=0x7f9174007030, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f921c49a481 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7f921c48be40 in pa_mainloop_poll () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f921c48c4d0 in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f921c48c560 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f921c49a3c9 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f9213ac8318 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#7  0x7f922e6776db in start_thread (arg=0x7f91957fa700) at
pthread_create.c:463
#8  0x7f9238d8788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 25 (Thread 0x7f9195ffb700 (LWP 3059)):
#0  0x7f9238d966ac in __lll_lock_wait_private () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1  0x7f9238d98474 in ___fprintf_chk (fp=0x7f92390538b0
<_IO_stdfile_2_lock>, flag=1, format=0x7f921a51a6a8 "[%s] %s\n") at
fprintf_chk.c:30
#2  0x7f921a5029ad in event_logv_ () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#3  0x7f921a502b44 in event_warn () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#4  0x7f921a50446c in  () at /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#5  0x7f921a4fa114 in event_base_loop () at
/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6
#6  0x7f92234e9ab9 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f92234e5da8 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f922350277b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f922351a4d6 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7f92235165eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#11 0x7f922e6776db in start_thread (arg=0x7f9195ffb700) at
pthread_create.c:463
#12 0x7f9238d8788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 24 (Thread 0x7f91967fc700 (LWP 

[kmail2] [Bug 408145] New: CRash on selecting folder with unread mail

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=408145

Bug ID: 408145
   Summary: CRash on selecting folder with unread mail
   Product: kmail2
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
  Target Milestone: ---

Application: kmail (5.7.3)

Qt Version: 5.9.5
Frameworks Version: 5.47.0
Operating System: Linux 4.18.0-17-generic x86_64
Distribution: Ubuntu 18.04.2 LTS

-- Information about the crash:
I opened kmail and i downloaded new mail from POP3 server. Some mail was moved
into sub folder by filter rule. I clicked on that folder and kmail crashed.

-- 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 0x7f92185e9b80 (LWP 4728))]

Thread 29 (Thread 0x7f90b666c700 (LWP 5643)):
#0  0x7f920afdeed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7f90b666b8c0, expected=0, futex_word=0x7f90a8006df0) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f920afdeed9 in __pthread_cond_wait_common (abstime=0x7f90b666b980,
mutex=0x7f90a8006da0, cond=0x7f90a8006dc8) at pthread_cond_wait.c:533
#2  0x7f920afdeed9 in __pthread_cond_timedwait (cond=0x7f90a8006dc8,
mutex=0x7f90a8006da0, abstime=0x7f90b666b980) at pthread_cond_wait.c:667
#3  0x7f9215dee468 in QWaitConditionPrivate::wait_relative(unsigned long)
(time=3, this=0x7f90a8006da0) at thread/qwaitcondition_unix.cpp:133
#4  0x7f9215dee468 in QWaitConditionPrivate::wait(unsigned long)
(time=3, this=0x7f90a8006da0) at thread/qwaitcondition_unix.cpp:141
#5  0x7f9215dee468 in QWaitCondition::wait(QMutex*, unsigned long)
(this=this@entry=0x7f90a8006ab0, mutex=mutex@entry=0x7f90a8003fb0, time=3)
at thread/qwaitcondition_unix.cpp:215
#6  0x7f9215dea53d in QThreadPoolThread::run() (this=0x7f90a8006aa0) at
thread/qthreadpool.cpp:144
#7  0x7f9215ded17d in QThreadPrivate::start(void*) (arg=0x7f90a8006aa0) at
thread/qthread_unix.cpp:368
#8  0x7f920afd86db in start_thread (arg=0x7f90b666c700) at
pthread_create.c:463
#9  0x7f92156e888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7f90b8688700 (LWP 5637)):
#0  0x7f920afde9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x564aafdf0b68) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f920afde9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x564aafdf0b18, cond=0x564aafdf0b40) at pthread_cond_wait.c:502
#2  0x7f920afde9f3 in __pthread_cond_wait (cond=0x564aafdf0b40,
mutex=0x564aafdf0b18) at pthread_cond_wait.c:655
#3  0x7f91ffe79c95 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f91ffe7a177 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f91ffe7af11 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f91ffe775eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f920afd86db in start_thread (arg=0x7f90b8688700) at
pthread_create.c:463
#8  0x7f92156e888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7f9139f2f700 (LWP 5636)):
#0  0x7f920afde9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f91fc740fb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f920afde9f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f91fc740f68, cond=0x7f91fc740f90) at pthread_cond_wait.c:502
#2  0x7f920afde9f3 in __pthread_cond_wait (cond=0x7f91fc740f90,
mutex=0x7f91fc740f68) at pthread_cond_wait.c:655
#3  0x7f91fc44a5f4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f91fc44a639 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7f920afd86db in start_thread (arg=0x7f9139f2f700) at
pthread_create.c:463
#6  0x7f92156e888f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7f9141e06700 (LWP 5617)):
#0  0x7f92156dbbf9 in __GI___poll (fds=0x7f913c001cb0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f92093825c9 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f92093826dc in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f92160249bb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f913c000cc0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f9215fc9a1a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f9141e05a20, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7f9215de823a in QThread::exec() (this=) at
thread/qthread.cpp:515
#6  0x7f9215ded17d in QThreadPrivate::start(void*) (arg=0x564ab2b4e6a0) at
thread/qthread_unix.cpp:368
#7  0x7f920afd86db in start_thread 

[kontact] [Bug 397124] New: Can't select contact at contact list (on click nothing happens)

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=397124

Bug ID: 397124
   Summary: Can't select contact at contact list (on click nothing
happens)
   Product: kontact
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: contacts
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
  Target Milestone: ---

Created attachment 114283
  --> https://bugs.kde.org/attachment.cgi?id=114283=edit
Screen shot of kaddressbook with marker

I open kaddressbook to lookup contact data. If I click on a contact entry (see
red area on attached image), nothing happens instead of showing the details of
selected contact.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 395868] Akonadi server crashed on mail read change

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=395868

--- Comment #1 from Christoph Thielecke  ---
Created attachment 113571
  --> https://bugs.kde.org/attachment.cgi?id=113571=edit
backtrace

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 395868] New: Akonadi server crashed on mail read change

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=395868

Bug ID: 395868
   Summary: Akonadi server crashed on mail read change
   Product: Akonadi
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
  Target Milestone: ---

Application: akonadiserver (5.7.3)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-20-generic x86_64
Distribution: Ubuntu 18.04 LTS

-- Information about the crash:
I resume KDE and click for refresh mail (fetch all ressources).
After mail was fetched I switched to folder with new mail and jump to new
unread mail using keyboard shortcut (+ on numpad). That worked for some mails
but then it crashed :(

-- Backtrace:

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 395253] High cpu usage of mysql server used by akonadi / akonadiserver

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=395253

Christoph Thielecke  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 395253] New: High cpu usage of mysql server used by akonadi / akonadiserver

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=395253

Bug ID: 395253
   Summary: High cpu usage of mysql server used by akonadi /
akonadiserver
   Product: Akonadi
   Version: 5.7.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
  Target Milestone: ---

Created attachment 113217
  --> https://bugs.kde.org/attachment.cgi?id=113217=edit
query debugger at akonadiconsole with strange queries

I noticed high cpu usage (75-80%) of mysql server used by akonadi for long time
(more then 2 hours). on Intel(R) Core(TM) i7 CPU   Q 840  @ 1.87GHz
(quadcore). The akonadiserver itself  uses 30-35% of cpu.

Something went wrong with akonadi. 

The query debugger at akonadiconsole also shows strange queries (see attaches
screenshot).


akonadiserver version: 5.7.3 (part of 17.12.3)

Here is akonadi's mysql config:
# cat ~/.local/share/akonadi/mysql.conf | egrep -v -e ';' -e '#' -e '^$'
[mysqld]
character_set_server=utf8
collation_server=utf8_general_ci
default_storage_engine=innodb
innodb_buffer_pool_size=128M
innodb_file_per_table=1
innodb_flush_log_at_trx_commit=2
innodb_log_buffer_size=1M
innodb_log_file_size=64M
log_error=mysql.err
log_warnings=2
lower_case_table_names=1
max_allowed_packet=32M
max_connections=256
query_cache_size=0
query_cache_type=0
skip_grant_tables
skip_networking
table_open_cache=200
thread_cache_size=3
wait_timeout=31536000
key_buffer_size=16K
secure_file_priv=
sql_mode=NO_ENGINE_SUBSTITUTION
innodb-read-io-threads=1
innodb-write-io-threads=1
[client]
default-character-set=utf8
# end of mysql config #

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 394419] New: Kmail crashed on exit

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=394419

Bug ID: 394419
   Summary: Kmail crashed on exit
   Product: kmail2
   Version: 5.7.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
  Target Milestone: ---

Application: kmail (5.7.3)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-20-generic x86_64
Distribution: Ubuntu 18.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I sent a mail and got notification it was sent. After some minutes I noticed in
tree at outbox that it shows 1 new message in it. I went there but the folder
is empty. The number of unread messages in this folder (1) still remains. After
this I decided to quit kmail and then it crashed.

- Unusual behavior I noticed:

-- 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 0x7f7b3b87fbc0 (LWP 7687))]

Thread 26 (Thread 0x7f7ad9b80700 (LWP 12032)):
#0  0x7f7b2e2709f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x56022e295bc8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f7b2e2709f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x56022e295b78, cond=0x56022e295ba0) at pthread_cond_wait.c:502
#2  0x7f7b2e2709f3 in __pthread_cond_wait (cond=0x56022e295ba0,
mutex=0x56022e295b78) at pthread_cond_wait.c:655
#3  0x7f7b23051c95 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f7b23052177 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f7b23052f11 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f7b2304f5eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f7b2e26a6db in start_thread (arg=0x7f7ad9b80700) at
pthread_create.c:463
#8  0x7f7b3897a88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 25 (Thread 0x7f79e39ec700 (LWP 10280)):
#0  0x7f7b2e2709f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x56022e295bcc) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f7b2e2709f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x56022e295b78, cond=0x56022e295ba0) at pthread_cond_wait.c:502
#2  0x7f7b2e2709f3 in __pthread_cond_wait (cond=0x56022e295ba0,
mutex=0x56022e295b78) at pthread_cond_wait.c:655
#3  0x7f7b23051c95 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f7b23052177 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f7b23052f11 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f7b2304f5eb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f7b2e26a6db in start_thread (arg=0x7f79e39ec700) at
pthread_create.c:463
#8  0x7f7b3897a88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 24 (Thread 0x7f7a69626700 (LWP 10176)):
#0  0x7f7b2e2709f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x7f7b1f91cfb8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f7b2e2709f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x7f7b1f91cf68, cond=0x7f7b1f91cf90) at pthread_cond_wait.c:502
#2  0x7f7b2e2709f3 in __pthread_cond_wait (cond=0x7f7b1f91cf90,
mutex=0x7f7b1f91cf68) at pthread_cond_wait.c:655
#3  0x7f7b1f6265f4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#4  0x7f7b1f626639 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#5  0x7f7b2e26a6db in start_thread (arg=0x7f7a69626700) at
pthread_create.c:463
#6  0x7f7b3897a88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 23 (Thread 0x7f7a6b6ce700 (LWP 10173)):
#0  0x7f7b389896e0 in __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:59
#1  0x7f7b389690a5 in __GI___libc_read (fd=88, buf=0x7f7a6b6cd7d0,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#2  0x7f7b2c599960 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7b2c554f27 in g_main_context_check () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f7b2c5553e0 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f7b2c4c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f7b392bb90b in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7f7a64000cc0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x7f7b392609ea in
QEventLoop::exec(QFlags)
(this=this@entry=0x7f7a6b6cd9e0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#8  0x7f7b3907f22a in QThread::exec() (this=) at
thread/qthread.cpp:515
#9  0x7f7b3908416d in QThreadPrivate::start(void*) (arg=0x560231d3dd30) at
thread/qthread_unix.cpp:368

[Akonadi] [Bug 328172] mixed maildir resource has wrong description

[Christoph Thielecke via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=328172

--- Comment #6 from Christoph Thielecke <criss...@gmx.de> ---
Still valid at Version 5.1.3 (KDE Frameworks 5.23.0):

"KMail-Mailordner"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 359762] New: Crash at click on subfolder of kmail maildir

[Christoph Thielecke via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359762

Bug ID: 359762
   Summary: Crash at click on subfolder of kmail maildir
   Product: Akonadi
   Version: 4.13
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: akonadiconsole
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

Application: akonadiconsole (0.99)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 4.0.1-040001-generic x86_64
Distribution: Ubuntu 14.04.4 LTS

-- Information about the crash:
I started akonadi-console to reindex the contents of a kmail maildir. It
started but when I did click or right click on a subfolder of the maildir, it
crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Akonadi Console (akonadiconsole), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f56a93a5800 (LWP 4171))]

Thread 5 (Thread 0x7f5684723700 (LWP 4174)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f569fbb681d in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f569fbb6859 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f569c399182 in start_thread (arg=0x7f5684723700) at
pthread_create.c:312
#4  0x7f56a41d947d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f56434a3700 (LWP 4175)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f569f8f720d in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f569fbe5fd6 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f569c399182 in start_thread (arg=0x7f56434a3700) at
pthread_create.c:312
#4  0x7f56a41d947d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f5642164700 (LWP 4176)):
#0  0x7f56a41cc12d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f569ad02fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f569ad030ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f56a4b687ce in QEventDispatcherGlib::processEvents
(this=0x7f56340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f56a4b3a0af in QEventLoop::processEvents
(this=this@entry=0x7f5642163da0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f56a4b3a3a5 in QEventLoop::exec (this=this@entry=0x7f5642163da0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f56a4a36c5f in QThread::exec (this=this@entry=0x10093f0) at
thread/qthread.cpp:537
#7  0x7f56a4b1b823 in QInotifyFileSystemWatcherEngine::run (this=0x10093f0)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7f56a4a3932f in QThreadPrivate::start (arg=0x10093f0) at
thread/qthread_unix.cpp:349
#9  0x7f569c399182 in start_thread (arg=0x7f5642164700) at
pthread_create.c:312
#10 0x7f56a41d947d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f5641219700 (LWP 4180)):
#0  0x7f56a41cc12d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f569ad02fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f569ad030ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f56a4b687ce in QEventDispatcherGlib::processEvents
(this=0x7f5638000900, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x7f56a4b3a0af in QEventLoop::processEvents
(this=this@entry=0x7f5641218de0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f56a4b3a3a5 in QEventLoop::exec (this=this@entry=0x7f5641218de0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f56a4a36c5f in QThread::exec (this=) at
thread/qthread.cpp:537
#7  0x7f56a4a3932f in QThreadPrivate::start (arg=0xc6ebf0) at
thread/qthread_unix.cpp:349
#8  0x7f569c399182 in start_thread (arg=0x7f5641219700) at
pthread_create.c:312
#9  0x7f56a41d947d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f56a93a5800 (LWP 4171)):
[KCrash Handler]
#6  KMime::Headers::Date::dateTime (this=0x0) at
../../kmime/kmime_headers.cpp:1524
#7  0x0042a101 in AkonadiBrowserSortModel::lessThan (this=, left=..., right=...) at ../../akonadiconsole/akonadibrowsermodel.cpp:372
#8  0x7f56a5d2343b in operator() (r2=0, r1=,
this=0x7ffebaf70c10) at itemviews/qsortfilterproxymodel.cpp:103
#9  qUpperBoundHelper
(lessThan=..., value=@0x1477f88: 2, end=0x1477f84, begin=0x1477f80) at
../../include/QtCore/../../src/corelib/tools/qalgorithms.h:499
#10 qUpperBound

[Akonadi] [Bug 346066] New: crash on click on subfolder of kmail folder ressource

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=346066

Bug ID: 346066
   Summary: crash on click on subfolder of kmail folder ressource
   Product: Akonadi
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: akonadiconsole
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

I have the problem that I cant read some messages from kmail folder ressource
cant retrieve item. For that I started akonadi-console to clear akonadi cache
and let resync it.

I selected the kmail folder ressource and it shows some subfolders. After click
on a subfolder akondi-console crashed.

akonadi version: 0.99 running on kde 4.14.2

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 346067] New: crash on click on subfolder of kmail folder ressource

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=346067

Bug ID: 346067
   Summary: crash on click on subfolder of kmail folder ressource
   Product: Akonadi
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: akonadiconsole
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

I have the problem that I cant read some messages from kmail folder ressource
cant retrieve item. For that I started akonadi-console to clear akonadi cache
and let resync it.

I selected the kmail folder ressource and it shows some subfolders. After click
on a subfolder akondi-console crashed.

akonadi version: 0.99 running on kde 4.14.2

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[akregator] [Bug 341872] New: crash at viewing a flash video inside website

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=341872

Bug ID: 341872
   Summary: crash at viewing a flash video inside website
   Product: akregator
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

Application: akregator (4.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.18.0-031800-lowlatency x86_64
Distribution: Ubuntu 14.04.1 LTS

-- Information about the crash:
I tried to view a video embedded on an website opened for a news article. It
crashed as start to play. The used rending engine is webkit.

-- Backtrace:
Application: Akregator (akregator), signal: Aborted
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7fe126cce800 (LWP 27485))]

Thread 17 (Thread 0x7fe100ad8700 (LWP 27494)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe1091eb81d in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7fe1091eb859 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) ()
from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7fe11ea4e182 in start_thread (arg=0x7fe100ad8700) at
pthread_create.c:312
#4  0x7fe123870efd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 16 (Thread 0x7fe0beed3700 (LWP 27495)):
#0  0x7fe11e3bf61a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fe11e3bf9a9 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe11e37d680 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe11e37df03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fe11e37e0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fe12512e7be in QEventDispatcherGlib::processEvents
(this=0x7fe0b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7fe1251000af in QEventLoop::processEvents
(this=this@entry=0x7fe0beed2de0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7fe1251003a5 in QEventLoop::exec (this=this@entry=0x7fe0beed2de0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7fe124ffcc5f in QThread::exec (this=optimized out) at
thread/qthread.cpp:537
#9  0x7fe124fff32f in QThreadPrivate::start (arg=0x26e5f10) at
thread/qthread_unix.cpp:349
#10 0x7fe11ea4e182 in start_thread (arg=0x7fe0beed3700) at
pthread_create.c:312
#11 0x7fe123870efd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 15 (Thread 0x7fe0bd821700 (LWP 27507)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe108f2c20d in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7fe10921afd6 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7fe11ea4e182 in start_thread (arg=0x7fe0bd821700) at
pthread_create.c:312
#4  0x7fe123870efd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 14 (Thread 0x7fe09616c700 (LWP 27561)):
#0  0x7fe123863bad in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fe11e37dfe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fe11e37e0ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fe12512e7be in QEventDispatcherGlib::processEvents
(this=0x7fe098c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7fe1251000af in QEventLoop::processEvents
(this=this@entry=0x7fe09616bda0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fe1251003a5 in QEventLoop::exec (this=this@entry=0x7fe09616bda0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fe124ffcc5f in QThread::exec (this=this@entry=0x3720300) at
thread/qthread.cpp:537
#7  0x7fe1250e1823 in QInotifyFileSystemWatcherEngine::run (this=0x3720300)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7fe124fff32f in QThreadPrivate::start (arg=0x3720300) at
thread/qthread_unix.cpp:349
#9  0x7fe11ea4e182 in start_thread (arg=0x7fe09616c700) at
pthread_create.c:312
#10 0x7fe123870efd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 13 (Thread 0x7fe083fa1700 (LWP 27995)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fe09b0d248c in ?? () from
/usr/lib/flashplugin-installer/libflashplayer.so
#2  0x7fe09ad1bc60 in ?? () from
/usr/lib/flashplugin-installer/libflashplayer.so
#3  0x7fe09b0d26ec in ?? () from
/usr/lib/flashplugin-installer/libflashplayer.so
#4  0x7fe09b0d2c3e in ?? () from
/usr/lib/flashplugin-installer/libflashplayer.so
#5  

[akregator] [Bug 341872] crash at viewing a flash video inside website

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=341872

--- Comment #1 from Christoph Thielecke criss...@gmx.de ---
Steps to reproduce:
1. install and choose webkit as rending engine for konqueror, install flash
(11.2.202.425)
2. add n42 news feed (http://feeds.n24.de/n24/homepage)
3. open article Freier Fall und Looping - Die halsbrecherischste Wasserrutsche
der Welt
4. try to play video in the middle of page (flash video)

System is Kubuntu Trusty (64bit).

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

[akregator] [Bug 338692] New: crash on close

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=338692

Bug ID: 338692
   Summary: crash on close
   Product: akregator
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

Application: akregator (4.14)
KDE Platform Version: 4.14.0
Qt Version: 4.8.6
Operating System: Linux 3.13.0-35-generic x86_64
Distribution: Ubuntu 14.04.1 LTS

-- Information about the crash:
I ran akregator for a while and open some articles using the webkit part. Then
I close the application and it crashed.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f9ce3324800 (LWP 7979))]

Thread 4 (Thread 0x7f9cbcd3d700 (LWP 7980)):
#0  update_get_addr (ti=0x7f9ce1abba50) at dl-tls.c:758
#1  0x7f9ce1653044 in get_thread_data () at thread/qthread_unix.cpp:188
#2  QThreadData::current () at thread/qthread_unix.cpp:219
#3  0x7f9ce1783af5 in postEventSourcePrepare (s=0x7f9cb8001350,
timeout=0x7f9cbcd3cbe4) at kernel/qeventdispatcher_glib.cpp:263
#4  0x7f9cda9d668d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f9cda9d6f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f9cda9d70ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f9ce17837be in QEventDispatcherGlib::processEvents
(this=0x7f9cb80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#8  0x7f9ce17550af in QEventLoop::processEvents
(this=this@entry=0x7f9cbcd3cda0, flags=...) at kernel/qeventloop.cpp:149
#9  0x7f9ce17553a5 in QEventLoop::exec (this=this@entry=0x7f9cbcd3cda0,
flags=...) at kernel/qeventloop.cpp:204
#10 0x7f9ce1651c5f in QThread::exec (this=this@entry=0x1030f30) at
thread/qthread.cpp:537
#11 0x7f9ce1736823 in QInotifyFileSystemWatcherEngine::run (this=0x1030f30)
at io/qfilesystemwatcher_inotify.cpp:265
#12 0x7f9ce165432f in QThreadPrivate::start (arg=0x1030f30) at
thread/qthread_unix.cpp:349
#13 0x7f9cdb0a7182 in start_thread (arg=0x7f9cbcd3d700) at
pthread_create.c:312
#14 0x7f9cdfec5fbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f9cb6ea3700 (LWP 8074)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9cc589a81d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f9cc589a859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f9cdb0a7182 in start_thread (arg=0x7f9cb6ea3700) at
pthread_create.c:312
#4  0x7f9cdfec5fbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f9cb4ada700 (LWP 8076)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9cc55db20d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f9cc58c9fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f9cdb0a7182 in start_thread (arg=0x7f9cb4ada700) at
pthread_create.c:312
#4  0x7f9cdfec5fbd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f9ce3324800 (LWP 7979)):
[KCrash Handler]
#6  0x7f9ce176a607 in isSignalConnected (signal_index=7, this=0x9) at
kernel/qobject_p.h:237
#7  QMetaObject::activate (sender=0xf40800, m=m@entry=0x7f9ce2a33760
Akregator::Frame::staticMetaObject,
local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fff95c89160)
at kernel/qobject.cpp:3444
#8  0x7f9ce281a782 in Akregator::Frame::signalCompleted (this=optimized
out, _t1=0xf40800) at moc_frame.cpp:200
#9  0x7f9ce28115b8 in Akregator::Frame::slotSetState (this=optimized out,
state=state@entry=Akregator::Frame::Completed) at
../../../akregator/src/frame.cpp:94
#10 0x7f9cc7d471f7 in Akregator::MainWidget::slotFetchingStopped
(this=0xe3d150) at ../../../akregator/src/mainwidget.cpp:808
#11 0x7f9ce176a87a in QMetaObject::activate (sender=sender@entry=0xd1f3a0,
m=m@entry=0x7f9ce2a337e0 Akregator::FetchQueue::staticMetaObject,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at
kernel/qobject.cpp:3539
#12 0x7f9ce281a363 in Akregator::FetchQueue::signalStopped
(this=this@entry=0xd1f3a0) at moc_fetchqueue.cpp:126
#13 0x7f9ce2811039 in Akregator::FetchQueue::slotAbort
(this=this@entry=0xd1f3a0) at ../../../akregator/src/fetchqueue.cpp:68
#14 0x7f9ce28110aa in Akregator::FetchQueue::~FetchQueue (this=0xd1f3a0,
__in_chrg=optimized out) at ../../../akregator/src/fetchqueue.cpp:50
#15 0x7f9ce289 in Akregator::FetchQueue::~FetchQueue (this=0xd1f3a0,
__in_chrg=optimized out) at ../../../akregator/src/fetchqueue.cpp:53
#16 0x7f9ce28100d9 in 

[kmail2] [Bug 336859] New: kmail becomes unsable on moving a lot of msg (~8000) for a longer time ( 5 min)

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=336859

Bug ID: 336859
   Summary: kmail becomes unsable on moving a lot of msg (~8000)
for a longer time ( 5 min)
Classification: Unclassified
   Product: kmail2
   Version: 4.13.1
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

When moving a lot of messages (~8000) from mixed maildir ressource to maildir
ressource mail responds very slow. This means it freezes for a while, then gui
was refreshed and again. This effect seems to be same on opening a maildir
ressource folder containing a lot of messages or marking all messages in this
folder.


Reproducible: Always

Steps to Reproduce:
1. go to a folder containing a lot of msg ( 5000)
2. select all
3. right click - move msg to other maildir ressource folder
Actual Results:  
- files are moved but gui hangs during move process for longer time 

Expected Results:  
- gui should be stay in usable state on messages move is in processs

I moved from mixed maildir ressource to maildir ressource.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 336867] New: Big memory footprint on big mixed maildir ressource

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=336867

Bug ID: 336867
   Summary: Big memory footprint on big mixed maildir ressource
Classification: Unclassified
   Product: kmail2
   Version: 4.13.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

I have a mixed maildir ressoure where kmail sys that size of it (and its
subfolders) is about 4.6GB. There is also another maildir ressource conatining
1.2G of data. 

The used memory of kmail is around 740MB (RES). I think this is too much.

Reproducible: Always

Actual Results:  
High memory footprint

Expected Results:  
Lower footprint

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 336868] New: crash on deleting mixed-maildir ressource folder

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=336868

Bug ID: 336868
   Summary: crash on deleting mixed-maildir ressource folder
Classification: Unclassified
   Product: kmail2
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

Application: kmail (4.13.2)
KDE Platform Version: 4.13.2
Qt Version: 4.8.6
Operating System: Linux 3.13.0-30-generic x86_64
Distribution: Ubuntu 14.04 LTS

-- Information about the crash:
I have a bigger mixed maildir ressource (~1.8G) and deleted some folders.
Mostly this wiorks but on latest one I deleted I got a 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 0x7f821880f800 (LWP 5422))]

Thread 7 (Thread 0x7f81ef47d700 (LWP 5425)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f820a10f81d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f820a10f859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f821342f182 in start_thread (arg=0x7f81ef47d700) at
pthread_create.c:312
#4  0x7f8215b6e30d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7f81ae2eb700 (LWP 5426)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8209e5020d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x7f820a13efd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x7f821342f182 in start_thread (arg=0x7f81ae2eb700) at
pthread_create.c:312
#4  0x7f8215b6e30d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 0x7f81ad382700 (LWP 5429)):
#0  0x7f8215b60fbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f820dbf0fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f820dbf10ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f82164fd7be in QEventDispatcherGlib::processEvents
(this=0x7f81a8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x7f82164cf0af in QEventLoop::processEvents
(this=this@entry=0x7f81ad381de0, flags=...) at kernel/qeventloop.cpp:149
#5  0x7f82164cf3a5 in QEventLoop::exec (this=this@entry=0x7f81ad381de0,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7f82163cbc5f in QThread::exec (this=optimized out) at
thread/qthread.cpp:537
#7  0x7f82163ce32f in QThreadPrivate::start (arg=0x169d340) at
thread/qthread_unix.cpp:349
#8  0x7f821342f182 in start_thread (arg=0x7f81ad382700) at
pthread_create.c:312
#9  0x7f8215b6e30d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 4 (Thread 0x7f81a734e700 (LWP 5430)):
#0  0x7f8215b5f6bd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f820dc31c20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f820dbf0b14 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f820dbf0f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f820dbf10ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f82164fd7be in QEventDispatcherGlib::processEvents
(this=0x7f819c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7f82164cf0af in QEventLoop::processEvents
(this=this@entry=0x7f81a734dda0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f82164cf3a5 in QEventLoop::exec (this=this@entry=0x7f81a734dda0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f82163cbc5f in QThread::exec (this=this@entry=0x199bd70) at
thread/qthread.cpp:537
#9  0x7f82164b0823 in QInotifyFileSystemWatcherEngine::run (this=0x199bd70)
at io/qfilesystemwatcher_inotify.cpp:265
#10 0x7f82163ce32f in QThreadPrivate::start (arg=0x199bd70) at
thread/qthread_unix.cpp:349
#11 0x7f821342f182 in start_thread (arg=0x7f81a734e700) at
pthread_create.c:312
#12 0x7f8215b6e30d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f8197975700 (LWP 8005)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f820005bffb in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7f820005c039 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7f821342f182 in start_thread (arg=0x7f8197975700) at
pthread_create.c:312
#4  0x7f8215b6e30d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f81958ed700 (LWP 8561)):
#0  0x7f8215b5f6bd in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f820dc31c20 in ?? () from 

[akregator] [Bug 334610] New: switch to new message caused crash

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=334610

Bug ID: 334610
   Summary: switch to new message caused crash
Classification: Unclassified
   Product: akregator
   Version: 4.13
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

Application: akregator (4.13)
KDE Platform Version: 4.13.0
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic i686
Distribution: Ubuntu 14.04 LTS

-- Information about the crash:
I was reading new using akgregator (which uses the webkit part for display) and
after switching to another message it crashed.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xb3198a40 (LWP 4666))]

Thread 5 (Thread 0xa9a7cb40 (LWP 4667)):
#0  0xb5eefaf4 in pthread_mutex_lock (mutex=0xa9100558) at forward.c:192
#1  0xb4762100 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb471c879 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb471d2df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb471d528 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb62d195f in QEventDispatcherGlib::processEvents (this=0xa9100468,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0xb62a0823 in QEventLoop::processEvents (this=this@entry=0xa9a7c258,
flags=...) at kernel/qeventloop.cpp:149
#7  0xb62a0b49 in QEventLoop::exec (this=this@entry=0xa9a7c258, flags=...) at
kernel/qeventloop.cpp:204
#8  0xb618d23d in QThread::exec (this=this@entry=0xa1fa8f0) at
thread/qthread.cpp:537
#9  0xb6280c44 in QInotifyFileSystemWatcherEngine::run (this=0xa1fa8f0) at
io/qfilesystemwatcher_inotify.cpp:265
#10 0xb618fb6f in QThreadPrivate::start (arg=0xa1fa8f0) at
thread/qthread_unix.cpp:349
#11 0xb4802f70 in start_thread (arg=0xa9a7cb40) at pthread_create.c:312
#12 0xb5ee270e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 4 (Thread 0xa84ffb40 (LWP 4690)):
#0  0xb7742424 in __kernel_vsyscall ()
#1  0xb4806d4b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb5eef8ec in __pthread_cond_wait (cond=0xaf2a0cb0
WTF::pageheap_memory+20720, mutex=0xaf2a0c98 WTF::pageheap_memory+20696) at
forward.c:149
#3  0xaea289ac in WTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xaea289ff in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xb4802f70 in start_thread (arg=0xa84ffb40) at pthread_create.c:312
#6  0xb5ee270e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 3 (Thread 0xa7bf1b40 (LWP 4691)):
#0  0xb480518a in __GI___pthread_mutex_lock (mutex=0xa7200558) at
../nptl/pthread_mutex_lock.c:125
#1  0xb5eefaf4 in pthread_mutex_lock (mutex=0xa7200558) at forward.c:192
#2  0xb4762100 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb471c9bd in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb471d2df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb471d528 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb62d195f in QEventDispatcherGlib::processEvents (this=0xa7200468,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#7  0xb62a0823 in QEventLoop::processEvents (this=this@entry=0xa7bf1288,
flags=...) at kernel/qeventloop.cpp:149
#8  0xb62a0b49 in QEventLoop::exec (this=this@entry=0xa7bf1288, flags=...) at
kernel/qeventloop.cpp:204
#9  0xb618d23d in QThread::exec (this=this@entry=0xa99d7f0) at
thread/qthread.cpp:537
#10 0xb618d38b in QThread::run (this=0xa99d7f0) at thread/qthread.cpp:604
#11 0xb618fb6f in QThreadPrivate::start (arg=0xa99d7f0) at
thread/qthread_unix.cpp:349
#12 0xb4802f70 in start_thread (arg=0xa7bf1b40) at pthread_create.c:312
#13 0xb5ee270e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 2 (Thread 0xa71ffb40 (LWP 4692)):
#0  0xb7742424 in __kernel_vsyscall ()
#1  0xb4806d4b in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb5eef8ec in __pthread_cond_wait (cond=0xa7c557dc, mutex=0xa7c557c4) at
forward.c:149
#3  0xaea579f3 in WTF::ThreadCondition::wait(WTF::Mutex) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#4  0xae733574 in JSC::BlockAllocator::blockFreeingThreadMain() () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#5  0xaea3e7c6 in WTF::threadEntryPoint(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#6  0xaea57369 in WTF::wtfThreadEntryPoint(void*) () from
/usr/lib/i386-linux-gnu/libQtWebKit.so.4
#7  0xb4802f70 in start_thread (arg=0xa71ffb40) at pthread_create.c:312
#8  

[kmail2] [Bug 333344] New: useless conflict dialog for read/unread messages showed

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=44

Bug ID: 44
   Summary: useless conflict dialog for read/unread messages
showed
Classification: Unclassified
   Product: kmail2
   Version: 4.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: folders
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

When I read a message and kmail wants to moved it later by filter it can
happen, that the read status has changed. In this case kmail shows a useless
dialog by claiming about the read status. Please omit this dialog in this case
because this is not a real conflict for the user. See attachment.

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 333344] useless conflict dialog for read/unread messages showed

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=44

--- Comment #1 from Christoph Thielecke criss...@gmx.de ---
Created attachment 86054
  -- https://bugs.kde.org/attachment.cgi?id=86054action=edit
conflict dialog showing the useless changed read status

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 332178] New: crash on deleting message

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=332178

Bug ID: 332178
   Summary: crash on deleting message
Classification: Unclassified
   Product: Akonadi
   Version: 4.12
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Mixed Maildir resource
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
CC: kram...@kde.org

Application: akonadi_mixedmaildir_resource (4.12)
KDE Platform Version: 4.12.3
Qt Version: 4.8.6
Operating System: Linux 3.11.0-17-generic i686
Distribution: Ubuntu 13.10

-- Information about the crash:
I stepped through the mail folder using keyboard and after some time I want to
delete a message, press del and go ahead. After that a crash dialog shows up.

-- Backtrace:
Application: Mail vom Typ KMail-Mailordner (akonadi_mixedmaildir_resource),
signal: Segmentation fault
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[KCrash Handler]
#7  __memmove_ia32 () at ../sysdeps/i386/i686/multiarch/../memmove.S:76
#8  0xb714f4b2 in memmove (__len=4294966512, __src=optimized out,
__dest=0xb227173f) at /usr/include/i386-linux-gnu/bits/string3.h:57
#9  KMBox::MBox::purge (this=this@entry=0xa820408, deletedEntries=...,
movedEntries=movedEntries@entry=0xbfe7b904) at ../../kmbox/mbox.cpp:386
#10 0x0807feb5 in MBoxContext::purge (this=this@entry=0xa8203f8,
movedEntries=...) at ../../../resources/mixedmaildir/mixedmaildirstore.cpp:180
#11 0x0807bdca in MixedMaildirStore::Private::visit (this=0x843cca8,
job=0xaee4a88) at ../../../resources/mixedmaildir/mixedmaildirstore.cpp:2207
#12 0xb772cae7 in Akonadi::FileStore::StoreCompactJob::accept (this=0xaee4a88,
visitor=0x843cca8) at
../../../../resources/shared/filestore/storecompactjob.cpp:54
#13 0x0807ba2e in MixedMaildirStore::processJob (this=0x8442d70, job=0xaee4a88)
at ../../../resources/mixedmaildir/mixedmaildirstore.cpp:2298
#14 0xb771a24e in Akonadi::FileStore::AbstractLocalStore::Private::processJobs
(this=0x845caf8, jobs=...) at
../../../../resources/shared/filestore/abstractlocalstore.cpp:300
#15 0xb771a312 in Akonadi::FileStore::AbstractLocalStore::qt_static_metacall
(_o=_o@entry=0x8442d70, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=0,
_a=0xbfe7bae8) at ./abstractlocalstore.moc:49
#16 0xb5cdd0e7 in QMetaObject::activate (sender=sender@entry=0x844d5f8,
m=m@entry=0xb7736c24
Akonadi::FileStore::AbstractJobSession::staticMetaObject,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0xbfe7bae8) at
kernel/qobject.cpp:3539
#17 0xb772bb55 in Akonadi::FileStore::AbstractJobSession::jobsReady
(this=0x844d5f8, _t1=...) at ./session_p.moc:98
#18 0xb772bf7b in runNextJob (this=0x8457bd8) at
../../../../resources/shared/filestore/sessionimpls.cpp:142
#19 Akonadi::FileStore::FiFoQueueJobSession::qt_static_metacall
(_o=_o@entry=0x844d5f8, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=0,
_a=0xbfe7bba8) at ./sessionimpls_p.moc:49
#20 0xb5cdd0e7 in QMetaObject::activate (sender=sender@entry=0x8457be0,
m=m@entry=0xb5e33518 QTimer::staticMetaObject,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at
kernel/qobject.cpp:3539
#21 0xb5d2d3a5 in QTimer::timeout (this=this@entry=0x8457be0) at
.moc/release-shared/moc_qtimer.cpp:147
#22 0xb5ce6916 in QTimer::timerEvent (this=0x8457be0, e=0xbfe7bf20) at
kernel/qtimer.cpp:280
#23 0xb5ce154c in QObject::event (this=0x8457be0, e=0xbfe7bf20) at
kernel/qobject.cpp:1156
#24 0xb62227f4 in QApplicationPrivate::notify_helper (this=0x833b830,
receiver=0x8457be0, e=0xbfe7bf20) at kernel/qapplication.cpp:4567
#25 0xb62292d3 in QApplication::notify (this=0xbfe7c1d4,
receiver=receiver@entry=0x8457be0, e=e@entry=0xbfe7bf20) at
kernel/qapplication.cpp:4353
#26 0xb6d731e4 in KApplication::notify (this=0xbfe7c1d4, receiver=0x8457be0,
event=0xbfe7bf20) at ../../kdeui/kernel/kapplication.cpp:311
#27 0xb5cc7e3a in QCoreApplication::notifyInternal (this=0xbfe7c1d4,
receiver=0x8457be0, event=event@entry=0xbfe7bf20) at
kernel/qcoreapplication.cpp:953
#28 0xb5cfa75b in sendEvent (event=0xbfe7bf20, receiver=optimized out) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#29 QTimerInfoList::activateTimers (this=this@entry=0x832c684) at
kernel/qeventdispatcher_unix.cpp:621
#30 0xb5cf7778 in timerSourceDispatch (source=0x832c650) at
kernel/qeventdispatcher_glib.cpp:186
#31 0xb4ed983e in g_main_context_dispatch () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#32 0xb4ed9be8 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#33 0xb4ed9ca8 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#34 0xb5cf79cf in QEventDispatcherGlib::processEvents
(this=this@entry=0x8308d98, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#35 0xb62d75fe in QGuiEventDispatcherGlib::processEvents (this=0x8308d98,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#36 

[kmail2] [Bug 320736] No progress indication for copying/moving email messages/folders

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=320736

Christoph Thielecke criss...@gmx.de changed:

   What|Removed |Added

 CC||criss...@gmx.de

--- Comment #2 from Christoph Thielecke criss...@gmx.de ---
Still present in 4.12.1

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 330895] New: copy mail folder to other folder on other ressource results in empty mails

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=330895

Bug ID: 330895
   Summary: copy mail folder to other folder on other ressource
results in empty mails
Classification: Unclassified
   Product: kmail2
   Version: 4.12.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: folders
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

copy mail folder (mixed maildir ressource) to other folder on other ressource
(mail dir) results in empty mails

Reproducible: Always

Steps to Reproduce:
1. create mixed maildir ressource on maildir containing a lot of mail
2. create maildir ressource on empty maildir
3. let kmail copy a folder from mixed maildir ressource to the maildir
ressource (takes very long time without progress)
Actual Results:  
folder created with mails and size 1 byte in new sub dir of target folder in
file system = Mails lost

Expected Results:  
folder created with mails and real size in cur sub dir of target folder in file
system

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 326399] mail search not possible if indexing is off

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=326399

--- Comment #7 from Christoph Thielecke criss...@gmx.de ---
 As I told you if you disable it you will not have search.
This is definitly a problem to depend a search on indexing. There good reasons
for disable indexing (large maildir, system load). Search on demand (for search
in a specific subfolder and it subfolders makes sense.

For me, searching mails through in a folder using the lineedit quick search
works and searching the index not (only partly result, mail index is still
completed).

Also, microsoft got the clue that search only the index is not useful and
provide fallback for searching files/folders if not indexed. 

Please think about to provide a fallback search without searching the index.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 329947] New: crash a mark a message as spam

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=329947

Bug ID: 329947
   Summary: crash a mark a message as spam
Classification: Unclassified
   Product: Akonadi
   Version: 4.12
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Mixed Maildir resource
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de
CC: kram...@kde.org

Application: akonadi_mixedmaildir_resource (4.12)
KDE Platform Version: 4.12.0
Qt Version: 4.8.4
Operating System: Linux 3.11.0-15-generic i686
Distribution: Ubuntu 13.10

-- Information about the crash:
I had 3 unread messages in the mail folder and jumped to the first one. This
and the second are junk and I clicked mark as spam (which moves the msg to
SPAM folder) 2 times. Then the 2. msg (also junk) was displayed (3.th marked)
and I got a crash dialog displayed.

-- Backtrace:
Application: Mail vom Typ KMail-Mailordner (akonadi_mixedmaildir_resource),
signal: Bus error
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xb4a94740 (LWP 4760))]

Thread 2 (Thread 0xb025eb40 (LWP 8425)):
#0  0xb77c8424 in __kernel_vsyscall ()
#1  0xb59e54d2 in clock_gettime (clock_id=1, tp=0xb025dfc8) at
../sysdeps/unix/clock_gettime.c:115
#2  0xb5c5c3ec in do_gettime (frac=0xb025dfc0, sec=0xb025dfb8) at
tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  0xb5d41fd2 in updateCurrentTime (this=0xaf902074) at
kernel/qeventdispatcher_unix.cpp:354
#5  QTimerInfoList::timerWait (this=0xaf902074, tm=...) at
kernel/qeventdispatcher_unix.cpp:461
#6  0xb5d4067b in timerSourcePrepareHelper (src=optimized out,
timeout=0xb025e0bc) at kernel/qeventdispatcher_glib.cpp:136
#7  0xb5d4070d in timerSourcePrepare (source=0xaf902040, timeout=0xb025e0bc) at
kernel/qeventdispatcher_glib.cpp:169
#8  0xb4f25143 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#9  0xb4f25a5f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0xb4f25ca8 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#11 0xb5d408df in QEventDispatcherGlib::processEvents (this=0xaf900468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#12 0xb5d0f9f3 in QEventLoop::processEvents (this=this@entry=0xb025e228,
flags=...) at kernel/qeventloop.cpp:149
#13 0xb5d0fd19 in QEventLoop::exec (this=this@entry=0xb025e228, flags=...) at
kernel/qeventloop.cpp:204
#14 0xb5bfee3d in QThread::exec (this=this@entry=0x9371340) at
thread/qthread.cpp:542
#15 0xb5cefe14 in QInotifyFileSystemWatcherEngine::run (this=0x9371340) at
io/qfilesystemwatcher_inotify.cpp:265
#16 0xb5c0172f in QThreadPrivate::start (arg=0x9371340) at
thread/qthread_unix.cpp:338
#17 0xb55f1d78 in start_thread (arg=0xb025eb40) at pthread_create.c:311
#18 0xb59d201e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131

Thread 1 (Thread 0xb4a94740 (LWP 4760)):
[KCrash Handler]
#7  __memmove_ia32 () at ../sysdeps/i386/i686/multiarch/../memmove.S:76
#8  0xb71964b2 in memmove (__len=545965, __src=optimized out,
__dest=0xb031af54) at /usr/include/i386-linux-gnu/bits/string3.h:57
#9  KMBox::MBox::purge (this=this@entry=0xba897f8, deletedEntries=...,
movedEntries=movedEntries@entry=0xbfaa24c4) at ../../kmbox/mbox.cpp:386
#10 0x0807feb5 in MBoxContext::purge (this=this@entry=0xba897e8,
movedEntries=...) at ../../../resources/mixedmaildir/mixedmaildirstore.cpp:180
#11 0x0807bdca in MixedMaildirStore::Private::visit (this=0x8ff9440,
job=0xb8de630) at ../../../resources/mixedmaildir/mixedmaildirstore.cpp:2207
#12 0xb7772ae7 in Akonadi::FileStore::StoreCompactJob::accept (this=0xb8de630,
visitor=0x8ff9440) at
../../../../resources/shared/filestore/storecompactjob.cpp:54
#13 0x0807ba2e in MixedMaildirStore::processJob (this=0x8ff9080, job=0xb8de630)
at ../../../resources/mixedmaildir/mixedmaildirstore.cpp:2298
#14 0xb776024e in Akonadi::FileStore::AbstractLocalStore::Private::processJobs
(this=0x8ff85f0, jobs=...) at
../../../../resources/shared/filestore/abstractlocalstore.cpp:300
#15 0xb7760312 in Akonadi::FileStore::AbstractLocalStore::qt_static_metacall
(_o=_o@entry=0x8ff9080, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=0,
_a=0xbfaa26a8) at ./abstractlocalstore.moc:50
#16 0xb5d25fc7 in QMetaObject::activate (sender=sender@entry=0x8fec0d8,
m=m@entry=0xb777cc24
Akonadi::FileStore::AbstractJobSession::staticMetaObject,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0xbfaa26a8) at
kernel/qobject.cpp:3539
#17 0xb7771b55 in Akonadi::FileStore::AbstractJobSession::jobsReady
(this=0x8fec0d8, _t1=...) at ./session_p.moc:99
#18 0xb7771f7b in runNextJob (this=0x8ff0298) at
../../../../resources/shared/filestore/sessionimpls.cpp:142
#19 Akonadi::FileStore::FiFoQueueJobSession::qt_static_metacall
(_o=_o@entry=0x8fec0d8, _c=_c@entry=QMetaObject::InvokeMetaMethod, 

[Akonadi] [Bug 329526] New: password cleared if login refused by server

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=329526

Bug ID: 329526
   Summary: password cleared if login refused by server
Classification: Unclassified
   Product: Akonadi
   Version: 4.12
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: POP3 Resource
  Assignee: mcgu...@kde.org
  Reporter: criss...@gmx.de
CC: kdepim-bugs@kde.org, vkra...@kde.org

The password for an pop3 account is cleared when the server refused the account
data. On next request cycle the user have to enter the password again. This
behavior is problematic. There serveral providers which refuses the login when
called to often within a time period or busy. Its very nasty for the user to
enter the password alltimes again if the login has been failed before. I think
the password dialog should be displayed to the user with prefilled password.
Then  the user have the choice to enter a new password or simply hit enter to
use the old password again. Addionally, it could be useful to have a check
option in preferences of the pop3 ressource which allows to ignore login
failitures and dont display the password dialog in that case.

Reproducible: Always

Steps to Reproduce:
1. create a pop3 ressource with account data from web.de (freemail), gmx
(freemail) or t-online
2. request to pull mail fast manually (web.de:  3min, gmx:  30s, t-online: no
time value known, randomly)
Actual Results:  
account data dialog displayed, username filled in, password removed

Expected Results:  
account data dialog displayed, username and password filled in

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

[kmail2] [Bug 326399] mail search not possible if indexing is off

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=326399

Christoph Thielecke criss...@gmx.de changed:

   What|Removed |Added

 Status|RESOLVED|VERIFIED
 Resolution|WONTFIX |REMIND

--- Comment #4 from Christoph Thielecke criss...@gmx.de ---
Search is still not possible in 4.12beta3 when indexing is off. There good
reasons on some cases to turn the indexing off:
- slow cpu
- small memory
- very large maildir/mbox dirs
- search with index does not work correctly
- one or more sub dirs not indexed yet

If a search from user is really requested, then traditional folder search
should be processed, even its slower. This behavior is also implemented in the
windows os, search always works transparently, even the resource is not
indexed.

I think the tradional search should be also available.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 328572] New: mail search not working on maildir

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=328572

Bug ID: 328572
   Summary: mail search not working on maildir
Classification: Unclassified
   Product: kmail2
   Version: 4.12 pre
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: misc
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

Finding mail using the mail search dialog does not work. Nepomuk, mail indexing
is enabled and mails are indexed (took a lot of time).

When you search with rules
From contains part of senders email address
search returned nothing and it gots quickly finished.

Reproducible: Always

Steps to Reproduce:
1. enable nepomuk
2. enable mail indexing
3. search with properties From contains part of senders email address 
Actual Results:  
empty search result

Expected Results:  
display affected mails in list

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 326399] mail search not possible if indexing is off

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=326399

--- Comment #2 from Christoph Thielecke criss...@gmx.de ---
Wrong. Its stated as bug because it is one. Please fix these nasty bugs

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 314354] pop3 account passwords lost

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=314354

--- Comment #3 from Christoph Thielecke criss...@gmx.de ---
It is a bug because passwords are lost on migration.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kmail2] [Bug 326399] New: mail search not possible if indexing is off

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=326399

Bug ID: 326399
   Summary: mail search not possible if indexing is off
Classification: Unclassified
   Product: kmail2
   Version: 4.11.2
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: UI
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

Its not possible to search for mails in folders (maildir) if indexing is
disabled. This is NOT acceptable.

Reproducible: Always

Steps to Reproduce:
1. Create maildir
2. fill in a lot of subfolders/mails
3. turn indexing off
4. try to search in this mail folder
Actual Results:  
stupid error message is shown:
Sie haben die Volltextindizierung von E-Mails ausgeschaltet. Die Suche ist
ohne dieser nicht möglich. Sie können sie in den Systemeinstellungen
einschalten. Bemerken Sie, dass die Suche erst nach einer vollständigen
Indizierung Ihrer E-Mails möglich ist, die einige Zeit in Anspruch nehmen
kann.

Expected Results:  
Searching for mails (slower than indexed mail folders)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 314354] pop3 account passwords lost

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=314354

--- Comment #1 from Christoph Thielecke criss...@gmx.de ---
Still present in 4.11.2
Also: smtp passwords not migrated

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Akonadi] [Bug 314354] New: pop3 account passwords lost

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=314354

Bug ID: 314354
   Summary: pop3 account passwords lost
Classification: Unclassified
   Product: Akonadi
   Version: 4.10
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Migration
  Assignee: kdepim-bugs@kde.org
  Reporter: criss...@gmx.de

I tried to migrate kmail1 settings to kmail2 and got problems for pop3 account
passwords.

Reproducible: Always

Steps to Reproduce:
Migrate kmail1 settings to kmail2 using kmail-migrator
Actual Results:  
migration succeeded but passwords for pop3 accounts not migrated, passwords for
imap accounts are migrated

Expected Results:  
passwords for pop3 accounts migrated too

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 310986] New: crash on clicking on akondi ressorces

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=310986

Bug ID: 310986
  Severity: crash
   Version: 4.9
  Priority: NOR
CC: kdepim-bugs@kde.org, vkra...@kde.org
  Assignee: er...@kde.org
   Summary: crash on clicking on akondi ressorces
Classification: Unclassified
OS: Linux
  Reporter: criss...@gmx.de
  Hardware: Ubuntu Packages
Status: UNCONFIRMED
 Component: IMAP resource
   Product: Akonadi

Application: akonadi_imap_resource (4.9)
KDE Platform Version: 4.9.3
Qt Version: 4.8.3
Operating System: Linux 3.5.0-19-generic i686
Distribution: Ubuntu 12.10

-- Information about the crash:
aknonadi crashed at clicking on akonadi ressources in kde systemsettings.

-- Backtrace:
Application: yfinite vom Typ IMAP-E-Mail-Server (akonadi_imap_resource),
signal: Segmentation fault
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0xb49fd740 (LWP 13735))]

Thread 2 (Thread 0xb20a9b40 (LWP 13737)):
#0  __pthread_mutex_lock (mutex=0xb1700550) at pthread_mutex_lock.c:47
#1  0xb5776864 in pthread_mutex_lock (mutex=0xb1700550) at forward.c:182
#2  0xb54e0ed0 in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb549f536 in g_main_context_prepare () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb549fbff in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb549fe61 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb733b99f in QEventDispatcherGlib::processEvents (this=0xb1700468,
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#7  0xb730826c in QEventLoop::processEvents (this=this@entry=0xb20a9228,
flags=...) at kernel/qeventloop.cpp:149
#8  0xb7308561 in QEventLoop::exec (this=0xb20a9228, flags=...) at
kernel/qeventloop.cpp:204
#9  0xb71f366c in QThread::exec (this=0x8e3ba80) at thread/qthread.cpp:501
#10 0xb72e67bd in QInotifyFileSystemWatcherEngine::run (this=0x8e3ba80) at
io/qfilesystemwatcher_inotify.cpp:248
#11 0xb71f6a58 in QThreadPrivate::start (arg=0x8e3ba80) at
thread/qthread_unix.cpp:338
#12 0xb55cdd4c in start_thread (arg=0xb20a9b40) at pthread_create.c:308
#13 0xb5768d3e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb49fd740 (LWP 13735)):
[KCrash Handler]
#7  0xffc0 in ?? ()
#8  0xb73249ca in QObject::connect (sender=0x90a6ec8, signal=0x80ac6c4
2stateChanged(KIMAP::Session::State,KIMAP::Session::State),
receiver=0x8e040a8, method=0x80ac680
1onSessionStateChanged(KIMAP::Session::State,KIMAP::Session::State),
type=Qt::AutoConnection) at kernel/qobject.cpp:2551
#9  0x0809c178 in SessionPool::onPasswordRequestDone
(this=this@entry=0x8e040a8, resultType=0, password=...) at
../../../resources/imap/sessionpool.cpp:335
#10 0x0809cbdc in SessionPool::qt_static_metacall (_o=0x8e040a8,
_c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf94d4a4) at ./sessionpool.moc:94
#11 0xb7321ed6 in QMetaObject::activate (sender=0x8f0c878, m=0x80aa160
PasswordRequesterInterface::staticMetaObject, local_signal_index=0,
argv=0xbf94d4a4) at kernel/qobject.cpp:3547
#12 0x0808753f in PasswordRequesterInterface::done (this=0x8f0c878, _t1=0,
_t2=...) at ./passwordrequesterinterface.moc:118
#13 0x0806541f in SettingsPasswordRequester::onPasswordRequestCompleted
(this=0x8f0c878, password=..., userRejected=false) at
../../../resources/imap/settingspasswordrequester.cpp:89
#14 0xb7321ed6 in QMetaObject::activate (sender=0x8f126f8, m=0x80a36c0
Settings::staticMetaObject, local_signal_index=0, argv=0xbf94d5d4) at
kernel/qobject.cpp:3547
#15 0x08063f37 in Settings::passwordRequestCompleted
(this=this@entry=0x8f126f8, _t1=..., _t2=_t2@entry=false) at ./settings.moc:124
#16 0x08063f83 in Settings::requestPassword (this=0x8f126f8) at
../../../resources/imap/settings.cpp:114
#17 0x08099d34 in SessionPool::connect (this=0x8e040a8, account=0x9118838) at
../../../resources/imap/sessionpool.cpp:102
#18 0x0805a399 in ImapResource::startConnect (this=this@entry=0x8f0d108) at
../../../resources/imap/imapresource.cpp:218
#19 0x0805e767 in ImapResource::qt_static_metacall (_o=0x8f0d108,
_c=QMetaObject::InvokeMetaMethod, _id=15, _a=0xbf94d844) at
./imapresource.moc:113
#20 0xb731260d in QMetaMethod::invoke (this=0xbf94d974, object=0x8f0d108,
connectionType=Qt::DirectConnection, returnValue=..., val0=..., val1=...,
val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...)
at kernel/qmetaobject.cpp:1664
#21 0xb7314c89 in QMetaObject::invokeMethod (obj=0x8f0d108, member=0x8e2a920
startConnect, type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=...,
val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at
kernel/qmetaobject.cpp:1179
#22 0xb763e2f3 in invokeMethod (val9=..., val8=..., val7=..., val6=...,
val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=optimized
out, obj=optimized out) at /usr/include/qt4/QtCore/qobjectdefs.h:434
#23 

[Bug 289994] New: kmail2 migration failed

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=289994

   Summary: kmail2 migration failed
   Product: kmail2
   Version: 4.8
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Version:   4.8 (using Devel) 
OS:Linux

I upgraded to kde 4.8-rc1 and kmail wants to upgrade on start but it fails and
tells me I should do migrate in console. But this also does not work.

Reproducible: Always

Steps to Reproduce:
Start kmail, it fails and tells to execute kmail-migrator --interactive but
this doesnt work.

Actual Results:  
first error (error msg iss attached. starting kmail-migrator --interactive
gives:
kmail-migrator --interactive
kmail-migrator(19945) main: Migration of kmailrc has already run, not running
it again

Expected Results:  
Migrate to kmail2 and run.

-- 
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 289994] kmail2 migration failed

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=289994





--- Comment #1 from Christoph Thielecke crissi99 gmx de  2011-12-28 10:31:43 
---
Created an attachment (id=67182)
 -- (http://bugs.kde.org/attachment.cgi?id=67182)
First error on first startup of kmail.

First error on first startup of kmail.

-- 
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 289996] New: kmail2 fails on start and exits

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=289996

   Summary: kmail2 fails on start and exits
   Product: kmail2
   Version: 4.8
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Version:   4.8 (using Devel) 
OS:Linux

After failed migration kmail2 doesnt want to start anymore.

Reproducible: Always

Steps to Reproduce:
Start kmail2 after failed migration.

Actual Results:  
It gives the following error message:
In KMail ist ein schwerwiegender Fehler aufgetreten. Das Programm wird beendet.
Die Fehlermeldung lautet:
Fehler beim Einholen der Ressourcen-Collection.

After closing the error msgbox it closes.

Expected Results:  
Starting 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 289999] New: adding remote note ressource not possible

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=28

   Summary: adding remote note ressource not possible
   Product: kontact
   Version: 4.8.x
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: notes
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Version:   4.8.x (using Devel) 
OS:Linux

Adding a remote notes ressource not possible anymore. I used remote notes via
xmlrpc on egroupware. Access is now lost :(
I have access to the remote notes on kde 3.5.10.

Reproducible: Always

Steps to Reproduce:
Try to add a remote note ressource (eGroupware server via xmlrpc)

Actual Results:  
Entry not listed anymore

Expected Results:  
Entry for adding remote ressource should be there

-- 
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 290009] New: selecting unread messages folder from kmail2 dock does not jump to first unread message

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=290009

   Summary: selecting unread messages folder from kmail2 dock does
not jump to first unread message
   Product: kmail2
   Version: 4.8
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Version:   4.8 (using Devel) 
OS:Linux

I have tray enabled (kmail) and there a new msg. so i right clicked and select
'new messages in' - 'folder with new msg', it opens the folder but does not
jump to the first unrtead message

Reproducible: Always

Steps to Reproduce:
enably tray (always on), let a message arrive, right click on tray icon, select
'new messages in' - 'folder with new msg'

Actual Results:  
simply opens the folder

Expected Results:  
jump to first unread message

-- 
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 284249] New: kontact crashed on close

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=284249

   Summary: kontact crashed on close
   Product: kontact
   Version: 4.4.10
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Application: kontact (4.4.10)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-11-generic i686
Distribution: Ubuntu 11.04

-- Information about the crash:
Kontact was started automaticlly on kde start. But after it was started, I want
to close it an click Fil - close but after that it crashed.

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

Thread 2 (Thread 0xb4b25b70 (LWP 4033)):
#0  0x00efd416 in __kernel_vsyscall ()
#1  0x05053f76 in __poll (fds=0xa6c9b10, nfds=3, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:87
#2  0x07c9284b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x07c821af in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x07c8292b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x0388a304 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0x07cab2df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x03c4de99 in start_thread (arg=0xb4b25b70) at pthread_create.c:304
#8  0x0506273e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb773f950 (LWP 4007)):
[KCrash Handler]
#7  0xb558c314 in KMFolderImap::slotListResult (this=0xa956b08,
subfolderNames=..., subfolderPaths=..., subfolderMimeTypes=...,
subfolderAttributes=..., jobData=...) at ../../kmail/kmfolderimap.cpp:789
#8  0xb558dd40 in KMFolderImap::qt_metacall (this=0xa956b08,
_c=QMetaObject::InvokeMetaMethod, _id=21, _a=0xbfbbbd98) at
./kmfolderimap.moc:182
#9  0x008896ba in QMetaObject::metacall (object=0xa956b08,
cl=QMetaObject::InvokeMetaMethod, idx=57, argv=0xbfbbbd98) at
kernel/qmetaobject.cpp:237
#10 0x008994ff in QMetaObject::activate (sender=0xb835b28, m=0xb59c68d4,
local_signal_index=0, argv=0xbfbbbd98) at kernel/qobject.cpp:3287
#11 0xb5478506 in KMail::ListJob::receivedFolders (this=0xb835b28, _t1=...,
_t2=..., _t3=..., _t4=..., _t5=...) at ./listjob.moc:97
#12 0xb547a6dd in KMail::ListJob::slotListResult (this=0xb835b28,
job=0xaf965e0) at ../../kmail/listjob.cpp:181
#13 0xb547a827 in KMail::ListJob::qt_metacall (this=0xb835b28,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0xbfbbbf48) at
./listjob.moc:83
#14 0x008896ba in QMetaObject::metacall (object=0xb835b28,
cl=QMetaObject::InvokeMetaMethod, idx=13, argv=0xbfbbbf48) at
kernel/qmetaobject.cpp:237
#15 0x008994ff in QMetaObject::activate (sender=0xaf965e0, m=0x37b508,
local_signal_index=3, argv=0xbfbbbf48) at kernel/qobject.cpp:3287
#16 0x0021c443 in KJob::result (this=0xaf965e0, _t1=0xaf965e0) at
./kjob.moc:194
#17 0x0021c498 in KJob::emitResult (this=0xaf965e0) at
../../kdecore/jobs/kjob.cpp:312
#18 0x01a8c7bb in KIO::SimpleJob::slotFinished (this=0xaf965e0) at
../../kio/kio/job.cpp:494
#19 0x01a8f8de in KIO::ListJob::slotFinished (this=0xaf965e0) at
../../kio/kio/job.cpp:2661
#20 0x01a9340e in KIO::ListJob::qt_metacall (this=0xaf965e0,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0xbfbbc19c) at
./jobclasses.moc:821
#21 0x008896ba in QMetaObject::metacall (object=0xaf965e0,
cl=QMetaObject::InvokeMetaMethod, idx=43, argv=0xbfbbc19c) at
kernel/qmetaobject.cpp:237
#22 0x008994ff in QMetaObject::activate (sender=0xb17a828, m=0x1c145a4,
local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3287
#23 0x01b3dac7 in KIO::SlaveInterface::finished (this=0xb17a828) at
./slaveinterface.moc:171
#24 0x01b408f7 in KIO::SlaveInterface::dispatch (this=0xb17a828, _cmd=104,
rawdata=...) at ../../kio/kio/slaveinterface.cpp:172
#25 0x01b3d373 in KIO::SlaveInterface::dispatch (this=0xb17a828) at
../../kio/kio/slaveinterface.cpp:88
#26 0x01b2f428 in KIO::Slave::gotInput (this=0xb17a828) at
../../kio/kio/slave.cpp:344
#27 0x01b2fc93 in KIO::Slave::qt_metacall (this=0xb17a828,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0xbfbbc4ac) at
./slave.moc:82
#28 0x008896ba in QMetaObject::metacall (object=0xb17a828,
cl=QMetaObject::InvokeMetaMethod, idx=30, argv=0xbfbbc4ac) at
kernel/qmetaobject.cpp:237
#29 0x008994ff in QMetaObject::activate (sender=0xb164238, m=0x1c11320,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3287
#30 0x01a59227 in KIO::Connection::readyRead (this=0xb164238) at
./connection.moc:92
#31 0x01a59a46 in KIO::ConnectionPrivate::dequeue (this=0xac23710) at
../../kio/kio/connection.cpp:82
#32 0x01a59af6 in KIO::Connection::qt_metacall (this=0xb164238,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0xb475c58) at
./connection.moc:79
#33 0x008896ba in QMetaObject::metacall (object=0xb164238,
cl=QMetaObject::InvokeMetaMethod, idx=5, 

[Bug 280090] New: kmail crashed at start

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=280090

   Summary: kmail crashed at start
   Product: kmail2
   Version: 4.8 pre
  Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Application: kmail (4.8 pre)
KDE Platform Version: 4.7.41 (4.7.41 (KDE 4.8 = 20110807) (Compiled from
sources)
Qt Version: 4.7.1
Operating System: Linux 3.0.0 x86_64
Distribution: Debian GNU/Linux 5.0.8 (lenny)

-- Information about the crash:
I tried to start kmail but it crashed. The used version is from git.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 0 (LWP 3959)]

Thread 2 (Thread 0x40d56950 (LWP 3963)):
#0  0x7fc239630d29 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/libpthread.so.0
#1  0x7fc231dc96ca in WTF::TCMalloc_PageHeap::scavengerThread () from
/home/kde-devel/qt4/lib/libQtWebKit.so.4
#2  0x7fc231dc9753 in WTF::TCMalloc_PageHeap::runScavengerThread () from
/home/kde-devel/qt4/lib/libQtWebKit.so.4
#3  0x7fc23962cfc7 in start_thread () from /lib/libpthread.so.0
#4  0x7fc238bfd64d in clone () from /lib/libc.so.6
#5  0x in ?? ()

Thread 1 (Thread 0x7fc23fb8a740 (LWP 3959)):
[KCrash Handler]
#6  0x7fc23a8705e2 in QScopedPointerQObjectData,
QScopedPointerDeleterQObjectData ::data (this=0x8) at
../../include/QtCore/../../../../qt-copy/src/corelib/tools/qscopedpointer.h:135
#7  0x7fc23a869e11 in qGetPtrHelperQScopedPointerQObjectData,
QScopedPointerDeleterQObjectData   (p=@0x8) at
../../include/QtCore/../../../../qt-copy/src/corelib/global/qglobal.h:2338
#8  0x7fc23a87061d in QAction::d_func (this=0x0) at
../../include/QtGui/../../../../qt-copy/src/gui/kernel/qaction.h:67
#9  0x7fc23a86c20b in QAction::setText (this=0x0, text=@0x7fffcc0096d0) at
/home/kde-devel/kdesvn/qt-copy/src/gui/kernel/qaction.cpp:814
#10 0x7fc23e98e621 in KMMainWidget::updateFolderMenu (this=0x6a14a0) at
/home/kde-devel/kdesvn/kdepim/kmail/kmmainwidget.cpp:3839
#11 0x7fc23e995350 in KMMainWidget::setupActions (this=0x6a14a0) at
/home/kde-devel/kdesvn/kdepim/kmail/kmmainwidget.cpp:3426
#12 0x7fc23e997b44 in KMMainWidget (this=0x6a14a0, parent=value optimized
out, aGUIClient=0x6a7390, actionCollection=value optimized out, config={d =
0x7fffcc00b430})
at /home/kde-devel/kdesvn/kdepim/kmail/kmmainwidget.cpp:246
#13 0x7fc23e8e4bfb in KMMainWin (this=0x6a7330) at
/home/kde-devel/kdesvn/kdepim/kmail/kmmainwin.cpp:63
#14 0x7fc23e947027 in KMKernel::openReader (this=0x7fffcc00d4e0,
onlyCheck=false) at /home/kde-devel/kdesvn/kdepim/kmail/kmkernel.cpp:552
#15 0x7fc23e94e148 in KMKernel::action (this=0x7fffcc00d4e0, mailto=value
optimized out, check=208, to=@0x7fffcc00bbf0, cc=@0x7fffcc00bbe0,
bcc=@0x7fffcc00bbd0, subj=@0x7fffcc00bbc0, 
body=@0x7fffcc00bbb0, messageFile=@0x7fffcc00b7b0,
attachURLs=@0x7fffcc00bb90, customHeaders=@0x7fffcc00bba0) at
/home/kde-devel/kdesvn/kdepim/kmail/kmkernel.cpp:1288
#16 0x7fc23e94f372 in KMKernel::handleCommandLine (this=0x7fffcc00d4e0,
noArgsOpensReader=true) at /home/kde-devel/kdesvn/kdepim/kmail/kmkernel.cpp:471
#17 0x00403872 in KMailApplication::newInstance (this=0x7fffcc00d5c0)
at /home/kde-devel/kdesvn/kdepim/kmail/main.cpp:85
#18 0x7fc23f694de2 in KUniqueApplicationAdaptor::newInstance
(this=0x834e80, asn_id=value optimized out, args=@0x8c73f0)
at /home/kde-devel/kdesvn/kdelibs/kdeui/kernel/kuniqueapplication.cpp:442
#19 0x7fc23f694e86 in KUniqueApplicationAdaptor::qt_metacall
(this=0x834e80, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fffcc00bf40)
at /home/kde-devel/kdesvn/build/kdelibs/kdeui/kuniqueapplication_p.moc:81
#20 0x7fc239dda7e1 in QDBusConnectionPrivate::deliverCall (this=0x64c290,
object=0x834e80, msg=@0xaeaea0, metaTypes=@0x7fffcc00c198, slotIdx=4)
at /home/kde-devel/kdesvn/qt-copy/src/dbus/qdbusintegrator.cpp:919
#21 0x7fc239ddb8a8 in QDBusConnectionPrivate::activateCall (this=0x64c290,
object=0x834e80, flags=337, msg=@0xaeaea0) at
/home/kde-devel/kdesvn/qt-copy/src/dbus/qdbusintegrator.cpp:822
#22 0x7fc239ddd993 in QDBusConnectionPrivate::activateObject
(this=0x64c290, node=@0xaeae78, msg=@0xaeaea0, pathStartPos=16) at
/home/kde-devel/kdesvn/qt-copy/src/dbus/qdbusintegrator.cpp:1379
#23 0x7fc239dddc00 in QDBusActivateObjectEvent::placeMetaCall
(this=0xaeae30) at
/home/kde-devel/kdesvn/qt-copy/src/dbus/qdbusintegrator.cpp:1493
#24 0x7fc239a2fd52 in QObject::event (this=0x7fffcc00d5c0, e=0xaeae30) at
/home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qobject.cpp:1219
#25 0x7fc239a13b59 in QCoreApplication::event (this=0x7fffcc00d5c0,
e=0xaeae30) at
/home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qcoreapplication.cpp:1561
#26 0x7fc23a87bc3f in QApplication::event (this=0x7fffcc00d5c0, e=0xaeae30)
at 

[Bug 256138] New: add possibility to set the color of a note

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=256138

   Summary: add possibility to set the color of a note
   Product: knotes
   Version: 0.9.15
  Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Version:   0.9.15 (using Devel) 
OS:Linux

It would be nice if there is a option for setting a category for the note. Each
category should be able to define a own color for it. the color should be used
in the note title background (or whoole note) and also displayed in the popup
menu at systray.

Reproducible: Always




OS: Linux (i686) release 2.6.35-22-generic
Compiler: cc

-- 
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 256137] New: add option for sort order in notes list

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=256137

   Summary: add option for sort order in notes list
   Product: knotes
   Version: 0.9.15
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Version:   0.9.15 (using Devel) 
OS:Linux

It would be nice to have a option how the notes will be sorted in the popup
menu. Currently they sorted by date but it would be nice to change the order
for example by node title

Reproducible: Always

Steps to Reproduce:
click left on knotes entry in system tray

Actual Results:  
popup with notes are shown in date sort order

Expected Results:  
popup with notes are shown in userdefined sort order

OS: Linux (i686) release 2.6.35-22-generic
Compiler: cc

-- 
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 254870] New: search option for searching for note title

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=254870

   Summary: search option for searching for note title
   Product: knotes
   Version: unspecified
  Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Version:   unspecified (using Devel) 
OS:Linux

It would be nice if the search function has an option to search for titles.
This should be different action in menu because the default search function
searches only for content

Reproducible: Always




OS: Linux (i686) release 2.6.36-rc6
Compiler: Target: i486-linux-gnu

-- 
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 253933] New: add context menu entry 'display note in panel'

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=253933

   Summary: add context menu entry 'display note in panel'
   Product: knotes
   Version: unspecified
  Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Version:   unspecified (using Devel) 
OS:Linux

It would be nice to have a context menu entry 'display note in panel' for quick
access to enable displaying note in window list. The entry should be in the
context menu shown if the user clicks right on the title bar

Reproducible: Always

Steps to Reproduce:
do right click on the title bar on new created note

Actual Results:  
context menu is shown but no entry 'display note in panel'

Expected Results:  
context menu is shown entry 'display note in panel' is shown too

OS: Linux (i686) release 2.6.36-rc6
Compiler: Target: i486-linux-gnu

-- 
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 253252] New: add option for repeating notifaction

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=253252

   Summary: add option for repeating notifaction
   Product: knotes
   Version: 0.9.15
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Version:   0.9.15 (using KDE 4.5.1) 
OS:Linux

It would be nice if I can specify a notification and let repeat it (minutely,
hourly, daily, weekly). This is very useful for let you remain things you have
daily to do for example.
It should not hard to implement.

Reproducible: Always




OS: Linux (i686) release 2.6.36-rc6
Compiler: Target: i486-linux-gnu

-- 
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 253252] add option for repeating notification

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=253252


Christoph Thielecke criss...@gmx.de changed:

   What|Removed |Added

Summary|add option for repeating|add option for repeating
   |notifaction |notification




-- 
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 253252] add option for repeating notification

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=253252





--- Comment #1 from Christoph Thielecke crissi99 gmx de  2010-10-04 19:49:17 
---
montly ar daily too ;)

-- 
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 242328] New: kmail mainwindow will not displayed after restoring via systray icon

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=242328

   Summary: kmail mainwindow will not displayed after restoring
via systray icon
   Product: kmail
   Version: 1.9.52
  Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: GUI
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Version:   1.9.52 (using Devel) 
OS:Linux

If kmail is hidden by clicking at systray icon and restoring by clicking again
the kmail systray icon kmail mainwindow is not shown. I got only the task entry
back. If I click on the task entry it shows me the mainwindow then.

Reproducible: Always

Steps to Reproduce:
if the sytray icon is always shown and i klick on it it hides kmail - good. if
i click again - entry in taskbar is shown again - good, but the kmail window
is not shown (only the task entry)

Actual Results:  
mainwindow is not shown after restore.

Expected Results:  
Show the mainwindow after restoring action from systray icon.

OS: Linux (i686) release 2.6.34
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 221764] New: restoring minimized kmail from dock fails

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=221764

   Summary: restoring minimized kmail from dock fails
   Product: kmail
   Version: 1.13.0
  Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Version:   1.13.0 (using 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1)), compiled
sources)
Compiler:  gcc
OS:Linux (i686) release 2.6.31

I enabled the dock icon in systray and tell to show that icon always. By
clicking on the dock icon, kmail minimizes how expected. But further clicking
causes nothing. Left click should restore kmail, right click should give
preferences.

-- 
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 216533] New: crash on changing name of new creates note

[Christoph Thielecke]

https://bugs.kde.org/show_bug.cgi?id=216533

   Summary: crash on changing name of new creates note
   Product: knotes
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: criss...@gmx.de


Application that crashed: knotes
Version of the application: 3.9
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-15-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
I connect a egroupware ressource to knotes. If I create a new note and change
the name knotes will crashes.

 -- Backtrace:
Application: KNotes (knotes), signal: Segmentation fault
[KCrash Handler]
#6  0xb7f953ec in KCal::IncidenceBase::uid (this=0xa74ce80) at
/usr/include/qt4/QtCore/qstring.h:711
#7  0x08077fac in KNote::noteId (this=0xa74d2c0) at
/build/buildd/kdepim-4.3.2/knotes/knote.cpp:203
#8  0x0805f269 in KNotesApp::updateNoteActions (this=0x9f061e0) at
/build/buildd/kdepim-4.3.2/knotes/knotesapp.cpp:667
#9  0x0806118a in KNotesApp::qt_metacall (this=0x9f061e0,
_c=QMetaObject::InvokeMetaMethod, _id=19, _a=0xbfe97220) at
/build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/knotes/knotesapp.moc:132
#10 0xb66a31b8 in QMetaObject::activate (sender=0xa74f0f0,
from_signal_index=29, to_signal_index=29, argv=0xbfe97220) at
kernel/qobject.cpp:3113
#11 0xb66a3e42 in QMetaObject::activate (sender=0xa74f0f0, m=0x808dd34,
local_signal_index=2, argv=0xbfe97220) at kernel/qobject.cpp:3187
#12 0x08077d85 in KNote::sigNameChanged (this=0xa74f0f0, _...@0xbfe972c0) at
/build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/knotes/knote.moc:164
#13 0x0807a309 in KNote::setName (this=0xa74f0f0, na...@0xbfe972c0) at
/build/buildd/kdepim-4.3.2/knotes/knote.cpp:231
#14 0x0807f0c3 in KNote::slotRename (this=0xa74f0f0) at
/build/buildd/kdepim-4.3.2/knotes/knote.cpp:307
#15 0x0805faa0 in KNotesApp::createNote (this=0x9f061e0, journal=0xa7c31a0) at
/build/buildd/kdepim-4.3.2/knotes/knotesapp.cpp:605
#16 0x08061163 in KNotesApp::qt_metacall (this=0x9f061e0,
_c=QMetaObject::InvokeMetaMethod, _id=22, _a=0xbfe97470) at
/build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/knotes/knotesapp.moc:135
#17 0xb66a31b8 in QMetaObject::activate (sender=0x9f7ec28, from_signal_index=4,
to_signal_index=4, argv=0xbfe97470) at kernel/qobject.cpp:3113
#18 0xb66a3e42 in QMetaObject::activate (sender=0x9f7ec28, m=0x808b560,
local_signal_index=0, argv=0xbfe97470) at kernel/qobject.cpp:3187
#19 0x0806abd5 in KNotesResourceManager::sigRegisteredNote (this=0x9f7ec28,
_t1=0xa7c31a0) at
/build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/knotes/resourcemanager.moc:84
#20 0x0806af43 in KNotesResourceManager::registerNote (this=0x9f7ec28,
resource=0x9fd2400, journal=0xa7c31a0) at
/build/buildd/kdepim-4.3.2/knotes/resourcemanager.cpp:101
#21 0x0806c3f5 in KNotesResourceManager::addNewNote (this=0x9f7ec28,
journal=0xa7c31a0) at /build/buildd/kdepim-4.3.2/knotes/resourcemanager.cpp:90
#22 0x08060ea1 in KNotesApp::newNote (this=0x9f061e0, na...@0xbfe97564,
te...@0xbfe97560) at /build/buildd/kdepim-4.3.2/knotes/knotesapp.cpp:278
#23 0x08061345 in KNotesApp::qt_metacall (this=0x9f061e0,
_c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfe9765c) at
/build/buildd/kdepim-4.3.2/obj-i486-linux-gnu/knotes/knotesapp.moc:112
#24 0xb66a31b8 in QMetaObject::activate (sender=0x9f62360, from_signal_index=5,
to_signal_index=6, argv=0xbfe9765c) at kernel/qobject.cpp:3113
#25 0xb66a35f0 in QMetaObject::activate (sender=0x9f62360, m=0xb73b9e48,
from_local_signal_index=1, to_local_signal_index=2, argv=0xbfe9765c) at
kernel/qobject.cpp:3207
#26 0xb6b4a6c1 in QAction::triggered (this=0x9f62360, _t1=false) at
.moc/release-shared/moc_qaction.cpp:236
#27 0xb6b4bc3f in QAction::activate (this=0x9f62360, event=QAction::Trigger) at
kernel/qaction.cpp:1160
#28 0xb6f9d0e4 in QMenuPrivate::activateCausedStack (this=0x9f77358,
causedsta...@0xbfe97738, action=0x9f62360, action_e=QAction::Trigger,
self=true) at widgets/qmenu.cpp:967
#29 0xb6fa383b in QMenuPrivate::activateAction (this=0x9f77358,
action=0x9f62360, action_e=QAction::Trigger, self=value optimized out) at
widgets/qmenu.cpp:1060
#30 0xb6fa4382 in QMenu::mouseReleaseEvent (this=0x9ec7320, e=0xbfe97d78) at
widgets/qmenu.cpp:2254
#31 0xb76d4e15 in KMenu::mouseReleaseEvent (this=0x9ec7320, e=0xbfe97d78) at
/build/buildd/kde4libs-4.3.2/kdeui/widgets/kmenu.cpp:456
#32 0xb6ba7973 in QWidget::event (this=0x9ec7320, event=0xbfe97d78) at
kernel/qwidget.cpp:7549
#33 0xb6fa6639 in QMenu::event (this=0x9ec7320, e=0xbfe97d78) at
widgets/qmenu.cpp:2353
#34 0xb6b50d3c in QApplicationPrivate::notify_helper (this=0x9ec8b70,
receiver=0x9ec7320, e=0xbfe97d78) at kernel/qapplication.cpp:4056
#35 0xb6b599b1 in QApplication::notify (this=0xbfe996e0, receiver=0x9ec7320,
e=0xbfe97d78) at kernel/qapplication.cpp:3758
#36 0xb75ec49d in