[kmail2] [Bug 460020] New: kmail crashes when running over xpra while using dosbox

[kavol]

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

Bug ID: 460020
   Summary: kmail crashes when running over xpra while using
dosbox
Classification: Applications
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz
  Target Milestone: ---

Application: kmail (5.20.3 (22.04.3))
 (Compiled from sources)
Qt Version: 5.15.5
Frameworks Version: 5.96.0
Operating System: Linux 5.15.69-gentoo x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.25.5 [KCrashBackend]

-- Information about the crash:
I'm running kmail from another machine via xpra/ssh session.
When I start dosbox in fullscreen, sometimes starting a game switches
resolution multiple times, making dosbox going forth and back from fullscreen
to windowed.
Kmail crashes reliably during these wild screen changes. (Simple screen change
during dosbox startup/close isn't enough to trigger the crash.)

The crash can be reproduced sometimes.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7  0x7f4a64426ecf in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8  0x7f4a643db6a2 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9  0x7f4a643c6469 in __GI_abort () at abort.c:79
#10 0x7f4a6441b278 in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7f4a6454d7be "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#11 0x7f4a644309da in malloc_printerr (str=str@entry=0x7f4a6454b1e1
"free(): invalid pointer") at malloc.c:5664
#12 0x7f4a6443256c in _int_free (av=, p=,
have_lock=0) at malloc.c:4439
#13 0x7f4a644350bf in __GI___libc_free (mem=) at
malloc.c:3391
#14 0x7f4a642e20ef in QTypedArrayData::deallocate(QArrayData*) (data=) at
/usr/include/qt5/QtCore/qarraydata.h:237
#15 QString::~QString() (this=0x7ffd6d0f5700, __in_chrg=) at
/usr/include/qt5/QtCore/qstring.h:1311
#16 QString::~QString() (this=0x7ffd6d0f5700, __in_chrg=) at
/usr/include/qt5/QtCore/qstring.h:1311
#17 KToolTipHelperPrivate::handleToolTipEvent(QWidget*, QHelpEvent*)
(this=0x55b4271b3550, watchedWidget=, helpEvent=0x7ffd6d0f5ae0)
at
/var/tmp/portage/kde-frameworks/kxmlgui-5.96.0/work/kxmlgui-5.96.0/src/ktooltiphelper.cpp:210
#18 0x7f4a64a34d21 in
QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*, QEvent*)
(event=, receiver=, this=) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qcoreapplication.cpp:1172
#19 QCoreApplicationPrivate::sendThroughApplicationEventFilters(QObject*,
QEvent*) (this=this@entry=0x55b426c35e70,
receiver=receiver@entry=0x55b429a6cc80, event=event@entry=0x7ffd6d0f5ae0) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qcoreapplication.cpp:1157
#20 0x7f4a653f2758 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=0x55b426c35e70, receiver=0x55b429a6cc80, e=0x7ffd6d0f5ae0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/widgets/kernel/qapplication.cpp:3608
#21 0x7f4a64a35068 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55b429a6cc80, event=0x7ffd6d0f5ae0) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qcoreapplication.cpp:1064
#22 0x7f4a65798506 in QSystemTrayIconSys::event(QEvent*)
(this=0x55b429a6c150, e=0x7ffd6d0f5ae0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/widgets/util/qsystemtrayicon_x11.cpp:154
#23 0x7f4a653f271f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x55b426c35e70, receiver=receiver@entry=0x55b429a6c150,
e=e@entry=0x7ffd6d0f5ae0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/widgets/kernel/qapplication.cpp:3637
#24 0x7f4a653fb040 in QApplication::notify(QObject*, QEvent*)
(this=, receiver=0x55b429a6c150, e=0x7ffd6d0f5ae0) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/widgets/kernel/qapplication.cpp:3303
#25 0x7f4a64a35068 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55b429a6c150, event=0x7ffd6d0f5ae0) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/kernel/qcoreapplication.cpp:1064
#26 0x7f4a653f80e9 in QApplication::event(QEvent*) (this=0x7ffd6d0f6370,
e=0x7ffd6d0f5c00) at
/var/tmp/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/widgets/kernel/qapplication.cpp:1901
#27 0x0

[kmail2] [Bug 448445] New: kmail crash on exit

[kavol]

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

Bug ID: 448445
   Summary: kmail crash on exit
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz
  Target Milestone: ---

Application: kmail (5.18.3 (21.08.3))

Qt Version: 5.15.2
Frameworks Version: 5.89.0
Operating System: Linux 5.15.13-200.fc35.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 35 (Thirty Five)
DrKonqi: 5.23.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
I've just closed kmail.
I believe some imap sync was in progress in the background.
The backtrace and circumstances look quite similar to the referenced bug
400601.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6  operator==(QString const&, QString const&) (s1=..., s2=...) at
text/qstring.cpp:3432
#7  0x7f7c6b4fe850 in KStatusNotifierItem::setToolTipSubTitle(QString
const&) (this=this@entry=0x559de328f490, subTitle=...) at
/usr/src/debug/kf5-knotifications-5.89.0-1.fc35.x86_64/src/kstatusnotifieritem.cpp:420
#8  0x7f7c75092606 in KMail::KMSystemTray::updateToolTip(int)
(this=0x559de328f490, count=) at
/usr/src/debug/kmail-21.08.3-1.fc35.x86_64/src/kmsystemtray.cpp:255
#9  0x7f7c7509285e in
KMail::UnityServiceManager::unreadMail(QAbstractItemModel const*, QModelIndex
const&) (this=, model=0x559de2b95800, parentIndex=) at
/usr/src/debug/kmail-21.08.3-1.fc35.x86_64/src/unityservicemanager.cpp:89
#10 0x7f7c7509285e in
KMail::UnityServiceManager::unreadMail(QAbstractItemModel const*, QModelIndex
const&) (this=, model=0x559de2b95800, parentIndex=) at
/usr/src/debug/kmail-21.08.3-1.fc35.x86_64/src/unityservicemanager.cpp:89
#11 0x7f7c750951d9 in KMail::UnityServiceManager::initListOfCollection()
(this=0x559de2bc1f70) at
/usr/src/debug/kmail-21.08.3-1.fc35.x86_64/src/unityservicemanager.cpp:111
#12 0x7f7c6c0853e9 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd2254b950, r=, this=0x559de2bcd590) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate(QObject*, int, void**) (sender=0x559de2b6b390,
signal_index=23, argv=0x7ffd2254b950) at kernel/qobject.cpp:3886
#14 0x7f7c6c080367 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=,
local_signal_index=local_signal_index@entry=20, argv=argv@entry=0x7ffd2254b950)
at kernel/qobject.cpp:3946
#15 0x7f7c69f2b45b in Akonadi::Monitor::collectionStatisticsChanged(long
long, Akonadi::CollectionStatistics const&) (this=,
_t1=, _t2=) at
/usr/src/debug/kf5-akonadi-server-21.08.3-1.fc35.x86_64/redhat-linux-build/src/core/KF5AkonadiCore_autogen/include/moc_monitor.cpp:1004
#16 0x7f7c69f3565a in
Akonadi::MonitorPrivate::slotStatisticsChangedFinished(KJob*)
(this=0x559de2b0e610, job=0x559df323a8a0) at
/usr/src/debug/kf5-akonadi-server-21.08.3-1.fc35.x86_64/src/core/monitor_p.cpp:657
#17 0x7f7c6c0853e9 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd2254bae0, r=, this=0x559df0e31a80) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#18 doActivate(QObject*, int, void**) (sender=0x559df323a8a0,
signal_index=6, argv=0x7ffd2254bae0) at kernel/qobject.cpp:3886
#19 0x7f7c6c080367 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x559df323a8a0, m=,
local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffd2254bae0)
at kernel/qobject.cpp:3946
#20 0x7f7c6d0d5450 in KJob::result(KJob*, KJob::QPrivateSignal)
(this=this@entry=0x559df323a8a0, _t1=, _t1@entry=0x559df323a8a0,
_t2=...) at
/usr/src/debug/kf5-kcoreaddons-5.89.0-1.fc35.x86_64/redhat-linux-build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#21 0x7f7c6d0d9abb in KJob::finishJob(bool) (this=0x559df323a8a0,
emitResult=) at
/usr/src/debug/kf5-kcoreaddons-5.89.0-1.fc35.x86_64/src/lib/jobs/kjob.cpp:98
#22 0x7f7c6c07bf49 in QObject::event(QEvent*) (this=0x559df323a8a0,
e=0x559de453e280) at kernel/qobject.cpp:1314
#23 0x7f7c6cb26443 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x559df323a8a0, e=0x559de453e280) at
kernel/qapplication.cpp:3632
#24 0x7f7c6c0517d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x559df323a8a0, event=0x559de453e280) at
kernel/qcoreapplication.cpp:1064
#25 0x7f7c6c054d46 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x559de27a76a0) at
kernel/qcoreapplication.cpp:1821
#26 0x7f7c6c0a3117 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer)

[kaddressbook] [Bug 447567] New: kaddressbook does not display nickname

[kavol]

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

Bug ID: 447567
   Summary: kaddressbook does not display nickname
   Product: kaddressbook
   Version: 5.18.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz
CC: to...@kde.org
  Target Milestone: ---

SUMMARY
Despite I have filed in nicknames for several contacts and made my custom style
which includes contact.nickName, the nicknames are not displayed.

Note that these are actually two problems together - 1) the default style does
not include nickname although this is quite important information and the style
includes (almost?) everything else; 2) the nickname is not displayed even if
the style includes it.

STEPS TO REPRODUCE
1. run kaddressbook in default configuration
2. edit some contact, add a nickname into the respective field
3. choose the contact, stare at the screen
4. quit kaddressbook
5. copy the default template into ~/.local/share/kaddressbook/viewertemplates/
6. rename the template (the directory and in theme.desktop)
7. edit contact_embedded.html, add "{{ contact.nickName }}" somewhere, e.g.
after {{ contact.realName }}, and change the font color to something
distinctive (e.g. append color="red" after size="+2") so that you know that the
new style got applied and you see where the change happened
8. run kaddressbook, choose the new style
9. choose the contact with the nickname set, stare at the screen

OBSERVED RESULT
3. & 9. no nickname displayed

EXPECTED RESULT
3. nickname displayed
9. nickname displayed in red

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 21.08.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
looking into sources, according to sec/printing/grantlee/README.themes,
(contact.)nickName is the correct name of the field (and grepping the sources,
"nickName" appears in this form in src/importexport/contactfields.cpp, just
like e.g. realName appears in the code elsewhere)

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

[kmail2] [Bug 439064] New: filter created on To wrongly matches also Delivered-To

[kavol]

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

Bug ID: 439064
   Summary: filter created on To wrongly matches also Delivered-To
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz
  Target Milestone: ---

I'm receiving lots of emails that are not directed to me, yet I want to process
them somehow. For some purposes, I need to filter out email where I am not on
the list of recipients. Trying to make negative filter on "To" with my address
fails, because the filter rules wrongly matches "Delivered-To".

STEPS TO REPRODUCE
1. have your address subscribed somewhere from where you get some emails with
your address in "To:" field and some sent to BCC or so, with your address not
included in "To:" but included in "Delivered-To:"
2. create an filter in kmail with a rule "To:" "does not contain"
"youraddr...@example.com"
3. apply the filter on a message which does not contain your address in "To"
(but it is present in "Delivered-To")

OBSERVED RESULT
the message is not matched, the filter action is ignored

EXPECTED RESULT
the message is matched and the filter action performed on it

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 34
(available in About System)
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
kmail-20.12.2-1.fc34.x86_64

ADDITIONAL INFORMATION
also Envelope-To might suffer from the same, but I haven't tested it

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

[kmail2] [Bug 402855] kmail crashed after weird message about folder deletion

[kavol]

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

kavol  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |UNMAINTAINED

--- Comment #2 from kavol  ---
I just hate these boilerplate messages ... how can I test when the problem
happened itself?

couldn't you just write that you have no resources to look at the backtrace and
examine potential issues in the code, and close the bug as unmaintained
yourself?

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

[kmail2] [Bug 290787] KMail shown "Unknown" date when Date field exist

[kavol]

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

kavol  changed:

   What|Removed |Added

Version|1.99.0  |5.11.3
 CC||ka...@seznam.cz

--- Comment #25 from kavol  ---
(In reply to bib from comment #24)
> This is starting to become the "longest bug". 7 years and counting.
> 
> It still happens with 5.10.3.

I started hitting this too :-(

kmail 5.11.3

unknown dates in emails look like this:

Date: Thu, 07 Nov 2019 17:04:17, -0500


note that this is probably duplicate of bug 288943 but that one looks more dead
than this, so commenting here ...

also bug 319906 might be duplicate

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

[kmail2] [Bug 402855] New: kmail crashed after weird message about folder deletion

[kavol]

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

Bug ID: 402855
   Summary: kmail crashed after weird message about folder
deletion
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz
  Target Milestone: ---

Application: kmail (5.9.3)
 (Compiled from sources)
Qt Version: 5.11.1
Frameworks Version: 5.52.0
Operating System: Linux 4.14.83-gentoo x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
After some time of leaving the computer idle, an error message appeared. It
said something like that I have deleted the folder associated with the POP3
account and that the account will now store incoming mail into inbox.
That is nonsene - a) I couldn't have deleted anything while not touching the
computer, b) the local inbox was the only target dir configured for the POP3
account, so the message basically says that it will use the deleted folder ...
which, in fact, didn't get deleted.
After clicking okay in that dialogue, kmail crashed.

- Unusual behavior I noticed:

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

Thread 26 (Thread 0x7ff93bfff700 (LWP 13785)):
#0  0x7ff9a3b678da in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7ff999089d47 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7ff99908b2a7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7ff99908b392 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7ff999090411 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7ff999091999 in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7ff99909c3b1 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7ff9a3b609aa in start_thread () from /lib64/libpthread.so.0
#8  0x7ff9ae11315f in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7ff8e71ad700 (LWP 13142)):
#0  0x7ff9a3b678da in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7ff999089d47 in base::ConditionVariable::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7ff99908b2a7 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7ff99908b392 in base::WaitableEvent::TimedWait(base::TimeDelta
const&) () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7ff999090411 in
base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7ff999091999 in base::internal::SchedulerWorker::Thread::ThreadMain()
() from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7ff99909c3b1 in base::(anonymous namespace)::ThreadFunc(void*) ()
from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7ff9a3b609aa in start_thread () from /lib64/libpthread.so.0
#8  0x7ff9ae11315f in clone () from /lib64/libc.so.6

Thread 24 (Thread 0x7ff8f1847700 (LWP 4038)):
#0  0x7ff9a3b675ac in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7ff9941b2224 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/libQt5Script.so.5
#2  0x7ff9941b2269 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /usr/lib64/libQt5Script.so.5
#3  0x7ff9a3b609aa in start_thread () from /lib64/libpthread.so.0
#4  0x7ff9ae11315f in clone () from /lib64/libc.so.6

Thread 23 (Thread 0x7ff8f35f5700 (LWP 4025)):
#0  0x7ff9ae1075f3 in poll () from /lib64/libc.so.6
#1  0x7ff9a1c8d069 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7ff9a1c8d17c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7ff9aea6355b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7ff9aea0fe2a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7ff9ae875b2a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7ff9ae87f3ff in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7ff9a3b609aa in start_thread () from /lib64/libpthread.so.0
#8  0x7ff9ae11315f in clone () from /lib64/libc.so.6

Thread 22 (Thread 0x7ff921ffb700 (LWP 4001)):
#0  0x7ff9a3b678da in pthread_cond_timedwait@@GLIBC_2.3.2 () fro

[kaddressbook] [Bug 402472] New: kaddressbook doesn't show any contacts

[kavol]

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

Bug ID: 402472
   Summary: kaddressbook doesn't show any contacts
   Product: kaddressbook
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz
CC: to...@kde.org
  Target Milestone: ---

Created attachment 117067
  --> https://bugs.kde.org/attachment.cgi?id=117067&action=edit
screenshot of the problem

Somewhen during upgrades, my contacts got lost - or to be precise, the ability
of kmail to autocomplete addresses from contacts. (I don't know when that
happened as the autocomplete still works with recent addresses so I haven't
noticed until the address I needed wasn't among recently used ...)

Trying to fix that, I've opened kaddressbook to check the contact and
eventually fix that, but I saw nothing and could fix nothing because there is
nothing to configure in kaddressbook.

So I went to akonadiconsole to find there is no contacts agent. So I have added
the one for vcf file and pointed it to the good old 'std.vcf' file.

Hooray, now autocomplete/search by name in kmail works for all the contacts ...

But I cannot (easily) edit them, as none of them are shown in kaddressbook.
(Well, via akonadiconsole I can edit anything ...)

However, kaddressbook obviously works with the vcf agent, as I can add a
contact, it shows 'std.vcf' in a dropdown selecting where to store the new
contact, and if I save it, it gets added to the 'std.vcf' file.

The appended screenshot shows a contact selected in akonadiconsole, so the
agent obviously works, but at the same time no contacts are shown in
kaddressbook ...

STEPS TO REPRODUCE
1. add a vcf file resource to akonadi
2. open kaddressbook
3. add a contact to that vcf

OBSERVED RESULT
you cannot see the freshly added contact in kaddressbook
examining the vcf file, you see the contact got added into it

EXPECTED RESULT
the new contact shows in kaddressbook
(and of course it is added to the file)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION

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

[kdepim] [Bug 342015] cannot compile libkdepim without baloo

[kavol]

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

--- Comment #8 from kavol  ---
(In reply to Christophe Giboudeaux from comment #6)
> As it's still not clear to you: Baloo is mandatory for kdepimlibs.

that part is clear to me just by looking at the code, however correctness of
the code cannot be proved by referencing itself

> That's not a bug.

why?

as already said, the code contradicts to what was said how it should behave

so the code not doing what it should do according to its developer is not a bug
because ...?

(In reply to Christophe Giboudeaux from comment #7)
> It's the gentoo build system that changes it to optional.

oops, I apologize, you're right ... I must have mistaken directories when
examining the sources and I didn't have any suspicion as there isn't any such
patch and I hadn't realized it can get changed elsewhere; running it through
diff I see the REQUIRED => OPTIONAL change now ... sorry :-(

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

[kdepim] [Bug 342015] cannot compile libkdepim without baloo

[kavol]

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

--- Comment #4 from kavol  ---
(In reply to Laurent Montel from comment #3)
...
> Baloo developper has created this patch.
> So it was required and there is never optional so no it's not a bug.
> Perhaps you need a feature but it's not a bug because never supported.

ahem, sorry, but I still do not follow ...

there is a discrepancy between the statement and the actual code

so one of them is wrong - "buggy"

and as the statement is part of a broader discussion, not just a random
thought, I'd say the bug is in the code and not in the statement

it's not a feature in the sense of "new functionality", it is a problem with
already existing code

so probably reassigning this to the actual author of the code to make it
compliant with what he says the code should do would be better than just
closing the bugreport with something like "he coded it this way so it should be
so" - if I get your words right

(if not, I apologise; also, I don't know much about processes in this bugzilla
instance, if the assignee is tied to the component and cannot be changed or
whatever ... I just present my POV which doesn't have to be best due to missing
context)

> So I will look at for kf5

cool, thanks

> but not for 4.14. I will not break all for it.
> If you don't want it. remove akonadi_baloo_indexer.

ok, I guess I can live with that as long as `rm /usr/bin/baloo*` doesn't break
anything I use

...
> I don't know why it reported it as optional but it's not my problem.
> If you want to open a bug report about it, report to kdelibs

ok, bug 342477

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

[kdepim] [Bug 342015] cannot compile libkdepim without baloo

[kavol]

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

kavol  changed:

   What|Removed |Added

 Resolution|INVALID |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #2 from kavol  ---
(In reply to Laurent Montel from comment #1)
> It was not optional
> => so it's not a bug.

ahem, I've referenced a comment from *Baloo developer* who says that Baloo
should be uninstallable

that implies that the compilation should not depend on it; either as a direct
implication (if the "uninstallability" is excercised before the compilation)
and either as indirect implication (if compiled with Baloo and then it gets
removed, you'd get executables broken due to missing libraries)

so in no way I can see how this could _not_ be a bug


> "
>   find_package(Baloo 4.14.0 QUIET CONFIG)
>   set_package_properties(Baloo PROPERTIES DESCRIPTION "The Baloo libraries"
> URL "http://www.kde.org"; TYPE REQUIRED PURPOSE "Baloo provides search
> capabilities in KMail and Akonadi")
> "
> => it's required

then, in addition, there's some bug with cmake if the configure phase output
lists it  in the section of optional and not required packages ... feel free to
open a new report for it

the full detection output is as follows:


-- The following OPTIONAL packages have been found:

 * Perl
 * KdepimLibs (required version >= 4.14.3) , The KDEPIM libraries ,
<http://www.kde.org>
 * Boost (required version >= 1.34.0) , Boost C++ Libraries ,
<http://www.boost.org>
   Boost is required for building most KDEPIM applications
 * Akonadi (required version >= 1.12.90) , Akonadi server libraries ,
<http://pim.kde.org/akonadi>
   Akonadi is required to build KDEPIM
 * ZLIB , The Zlib compression library , <http://www.zlib.net>
 * Gpgme
 * Threads
 * PkgConfig
 * OpenSSL
 * Grantlee (required version >= 0.3.0) , The Grantlee Template System ,
<http://www.gitorious.org/grantlee/pages/Home>
   Grantlee is requires for kmail and templating, theming for KJots,
KaddressBook, KNotes and MessageViewer(KMail).
 * Xsltproc , XSLT processor from libxslt
   Required to generate D-Bus interfaces.
 * QJSON , QJSON , <http://qjson.sourceforge.net/>
   Qt library for handling JSON data
 * LibKGAPI2 (required version >= 2.2.0) , KDE-based library for accessing
various Google services , <https://projects.kde.org/libkgapi>
   LibKGAPI is required to build Google Drive Storage Service
 * Assuan2

-- The following RECOMMENDED packages have been found:

 * QGpgme , The QGpgMe library , <http://www.kde.org>
   QGpgME is required to build KMail, KOrganizer and Kleopatra

-- The following REQUIRED packages have been found:

 * Automoc4
 * Phonon (required version >= 4.3.80)
 * KDE4Internal
 * KDE4 (required version >= 4.13.0)
 * X11
 * Qt4

-- The following OPTIONAL packages have not been found:

 * Baloo (required version >= 4.14.0) , The Baloo libraries ,
<http://www.kde.org>
   Baloo provides search capabilities in KMail and Akonadi
 * Prison , The Prison library , <http://projects.kde.org/prison>
   Needed to show mobile barcodes of your contacts

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

[kdepim] [Bug 342015] New: cannot compile libkdepim without baloo

[kavol]

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

Bug ID: 342015
   Summary: cannot compile libkdepim without baloo
   Product: kdepim
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: libkdepim
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz

I don't want Baloo on my system. Reading some references, it should be doable -
e.g. bug 332195 comment 13 says it should be possible to uninstall. When trying
to compile libkdepim, cmake says:


-- The following OPTIONAL packages have not been found:

 * Baloo (required version >= 4.14.0) , The Baloo libraries ,

   Baloo provides search capabilities in KMail and Akonadi


... it even shouts at me that Baloo is "OPTINAL". But then the compilation
fails with:

[  2%] Building CXX object
libkdepim/CMakeFiles/kdepim.dir/addressline/addresseelineedit.o
cd
/var/tmp/portage/kde-base/kdepim-common-libs-4.14.3/work/kdepim-common-libs-4.14.3_build/libkdepim
&& /usr/lib64/ccache/bin/x86_64-pc-linux-gnu-g++ 
-DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=56 -DKDEPIM_STORAGESERVICE_GDRIVE
-DKDE_DEFAULT_DEBUG_AREA=5300 -DKDE_DEPRECATED_WARNINGS -DMAKE_KDEPIM_LIB
-DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_STL
-DQT_USE_QSTRINGBUILDER -D_BSD_SOURCE -D_REENTRANT -D_XOPEN_SOURCE=500 
-DQT_NO_DEBUG -DNDEBUG -O2 -pipe -march=native -ggdb  -Wnon-virtual-dtor
-Wno-long-long -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith
-Wformat-security -fno-exceptions -DQT_NO_EXCEPTIONS -fno-check-new -fno-common
-Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden
-fvisibility-inlines-hidden -fexceptions -UQT_NO_EXCEPTIONS -fPIC
-I/var/tmp/portage/kde-base/kdepim-common-libs-4.14.3/work/kdepim-common-libs-4.14.3_build/libkdepim
-I/var/tmp/portage/kde-base/kdepim-common-libs-4.14.3/work/kdepim-common-libs-4.14.3/libkdepim
-I/var/tmp/portage/kde-base/kdepim-common-libs-4.14.3/work/kdepim-common-libs-4.14.3
-I/var/tmp/portage/kde-base/kdepim-common-libs-4.14.3/work/kdepim-common-libs-4.14.3_build
-I/usr/include/KDE -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtXml
-I/usr/include/qt4/QtWebKit -I/usr/include/qt4/QtUiTools
-I/usr/include/qt4/QtTest -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql
-I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript
-I/usr/include/qt4/QtOpenGL -I/usr/include/qt4/QtNetwork
-I/usr/include/qt4/QtMultimedia -I/usr/include/qt4/QtDesigner
-I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtDBus
-I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui
-I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt
-I/usr/share/qt4/mkspecs/default -I/usr/include/qt4-D_GNU_SOURCE
-D_LARGEFILE64_SOURCE -o CMakeFiles/kdepim.dir/addressline/addresseelineedit.o
-c
/var/tmp/portage/kde-base/kdepim-common-libs-4.14.3/work/kdepim-common-libs-4.14.3/libkdepim/addressline/addresseelineedit.cpp
/var/tmp/portage/kde-base/kdepim-common-libs-4.14.3/work/kdepim-common-libs-4.14.3/libkdepim/addressline/addresseelineedit.cpp:42:40:
fatal error: baloo/pim/contactcompleter.h: No such file or directory
 #include 
^
compilation terminated.


Despite the fact that the top-level cmakelists fails the check for Baloo, the
cmakelists from the added subdirectory 'libkdepim' doesn't make use of the
result of the check and just hardcodes Baloo-specific options and tries to
compile code that unconditionally depends on Baloo headers ...

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 320529] maildir resource not working

[kavol]

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

--- Comment #1 from kavol  ---
(In reply to comment #0)
> # rpm -qf /usr/lib64/kde4/akonadi_maildir_resource.so
> kdepim-runtime-4.10.3-3.fc19.x86_64
> 
> ... going to try downgrade

damn, nothing older available for F19 :-/

-- 
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 320529] New: maildir resource not working

[kavol]

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

Bug ID: 320529
   Summary: maildir resource not working
Classification: Unclassified
   Product: Akonadi
   Version: 4.10
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz

I am unable to access emails in a local maildir.
I've tried to remove the maildir resource via akonadiconsole - it gets re-added
again, but still does not work.

This blocks me from using kmail alltogether, even for IMAP, because
1) once I try to access the local folders, kmail refuses to work even with
messagess in the IMAP account, but
2) even if I try to avoid accessing local folders, I can't use the IMAP account
as deleting messages tries to move them into local trash, and sending an email
tries to put it into local outgoing ...

Reproducible: Always

Steps to Reproduce:
1. run kmail
2. access a local folder which is not empty
3. try to select a message

4. run akonadiconsole
5. switch to browser tab
6. choose some local folder
Actual Results:  
2. you see the list of messages
3. you get "Stahuje se obsah složky" and "Prosím čekejte ..." and it sits there
forever
("Downloading folder content" and "Please wait" or something like that)
from this point on, the "please wait" message is shown for any folder/message

6. unlike in kmail, you don't even get the list of messages - it just shows the
"working/waiting" animated icon next to the folder name forever

Expected Results:  
3. you see the contents of the email

6. you see the list of messages

# rpm -qf /usr/lib64/kde4/akonadi_maildir_resource.so
kdepim-runtime-4.10.3-3.fc19.x86_64

... going to try downgrade

-- 
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 320525] akonadi insist on creating duplicate local maildir agent

[kavol]

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

--- Comment #1 from kavol  ---
one more note ... looking into configuration, the agents created as even have
this:

Path[$e]=$HOME/.local/share/akonadi_maildir_resource_2
Path[$e]=$HOME/.local/share/akonadi_maildir_resource_4
etc.

while the odd ones have
Path[$e]=$HOME/.local/share/local-mail

(which is the correct location)

-- 
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 320526] New: akonadiconsole crash

[kavol]

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

Bug ID: 320526
   Summary: akonadiconsole crash
Classification: Unclassified
   Product: Akonadi
   Version: 0.99
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: akonadiconsole
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz

Application: akonadiconsole (0.99)
KDE Platform Version: 4.10.3
Qt Version: 4.8.4
Operating System: Linux 3.9.4-300.fc19.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

I was browsing agent list in akonadiconsole.

I've rightclicked local mail to get options but it got unresponsive - the menu
did not appear. So I've tried to close akonadiconsole by clicking the windows
close button - at the very same moment the context menu appeared, and
akonadiconsole crashed right afterwards.

Note that there is quite a long list of possible duplicates but I wasn't able
to find any good similarities, I'd be interested why DrKonqi thinks these
should be duplicate ...

-- Backtrace:
Application: Akonadi Console (akonadiconsole), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fdbe37798c0 (LWP 17004))]

Thread 4 (Thread 0x7fdbd7d69700 (LWP 17012)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x003fc24c9abd in WTF::TCMalloc_PageHeap::scavengerThread
(this=) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:2571
#2  0x003fc24c9af9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:1767
#3  0x00366de07c53 in start_thread (arg=0x7fdbd7d69700) at
pthread_create.c:308
#4  0x00366d6f4ecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7fdbd6998700 (LWP 17015)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x003fc220b3fd in JSC::BlockAllocator::blockFreeingThreadMain
(this=0x7fdbd74d2398) at
/usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#2  0x003fc24f9316 in WTF::wtfThreadEntryPoint (param=0xb18ac0) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196
#3  0x00366de07c53 in start_thread (arg=0x7fdbd6998700) at
pthread_create.c:308
#4  0x00366d6f4ecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7fdbd5585700 (LWP 17083)):
#0  0x00367168703a in g_mutex_get_impl (mutex=0x7fdb89e0) at
gthread-posix.c:121
#1  0x003671687319 in g_mutex_unlock (mutex=mutex@entry=0x7fdb89e0) at
gthread-posix.c:229
#2  0x003671647830 in g_main_context_prepare
(context=context@entry=0x7fdb89e0, priority=priority@entry=0x7fdbd5584be8)
at gmain.c:3326
#3  0x0036716480b3 in g_main_context_iterate
(context=context@entry=0x7fdb89e0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3681
#4  0x00367164829c in g_main_context_iteration (context=0x7fdb89e0,
may_block=1) at gmain.c:3762
#5  0x003fb39a6cd6 in QEventDispatcherGlib::processEvents
(this=0x7fdb8900, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x003fb3978bdf in QEventLoop::processEvents
(this=this@entry=0x7fdbd5584d20, flags=...) at kernel/qeventloop.cpp:149
#7  0x003fb3978ed5 in QEventLoop::exec (this=this@entry=0x7fdbd5584d20,
flags=...) at kernel/qeventloop.cpp:204
#8  0x003fb387862f in QThread::exec (this=) at
thread/qthread.cpp:542
#9  0x003fb387accf in QThreadPrivate::start (arg=0xcd3140) at
thread/qthread_unix.cpp:338
#10 0x00366de07c53 in start_thread (arg=0x7fdbd5585700) at
pthread_create.c:308
#11 0x00366d6f4ecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7fdbe37798c0 (LWP 17004)):
[KCrash Handler]
#6  0x00366d635819 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00366d636f28 in __GI_abort () at abort.c:90
#8  0x00366d675b57 in __libc_message (do_abort=do_abort@entry=2,
fmt=fmt@entry=0x366d77da88 "*** Error in `%s': %s: 0x%s ***\n") at
../sysdeps/unix/sysv/linux/libc_fatal.c:196
#9  0x00366d67cef8 in malloc_printerr (ptr=,
str=0x366d77b171 "free(): invalid pointer", action=3) at malloc.c:4916
#10 _int_free (av=0x366d9b9780 , p=, have_lock=0) at
malloc.c:3768
#11 0x003fb3990388 in QObjectPrivate::deleteChildren
(this=this@entry=0xb33d70) at kernel/qobject.cpp:1907
#12 0x003fb52140c7 in QWidget::~QWidget (this=0xb33890,
__in_chrg=) at kernel/qwidget.cpp:1681
#13 0x00421003 in ~AgentWidget (this=0xb33890, __in_chrg=) at /usr/src/debug/kdepim-4.10.3/akonadiconsole/agentwidget.h:34
#1

[Akonadi] [Bug 320525] New: akonadi insist on creating duplicate local maildir agent

[kavol]

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

Bug ID: 320525
   Summary: akonadi insist on creating duplicate local maildir
agent
Classification: Unclassified
   Product: Akonadi
   Version: 4.10
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz

I have troubles with kmail - it freezes(*) trying to display anything from
local folders.

(*) I mean it doesn't display the selected email body, and after that, it
refuses to display any email from any other folder. It isn't "freeze" in the
sense that I couldn't do anything, it just stops displaying emails. After
quitting and starting kmail again, I can display any of emails on IMAP, but
once I try to display something from the local folders, it "freezes" again.

So I've tried some magic via akonadiconsole (like switching the particular
resource online/offline, checking the configuration etc.) This did not help.

On some subsequent akonadiconsole start, I've noticed in the browser that there
are two sets of the same local folders. Switching to agents listing, I've
noticed there are two "Maildir" resources, identified
akonadi_maildir_resource_0 and akonadi_maildir_resource_1. So I've removed the
second one.

But that led to creating another agent named "Lokální složky" identified
akonadi_maildir_resource_2.

So I've removed that one and got another "Lokální složky" identified
akonadi_maildir_resource_3. Hm, interesting, on next akonadiconsole start the
name got changed to "Maildir".

So I've removed that one and ... guess what I got?

Note that after each removal, akonadi starts spitting out messages like this
until its restart:

akonadi_maildispatcher_agent(15988)/libakonadi: Resource id's don't match: 
"akonadi_maildir_resource_2" "akonadi_maildir_resource_1" 


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 320524] New: akonadiconsole crashed after removing an agent

[kavol]

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

Bug ID: 320524
   Summary: akonadiconsole crashed after removing an agent
Classification: Unclassified
   Product: Akonadi
   Version: 0.99
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: akonadiconsole
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz

Application: akonadiconsole (0.99)
KDE Platform Version: 4.10.3
Qt Version: 4.8.4
Operating System: Linux 3.9.4-300.fc19.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

I've removed maildir resource, then wanted to close akonadiconsole. It didn't
react, instead I got standard kwin question about killing the unresponsive
window. I left it for a while then it crashed.

-- Backtrace:
Application: Akonadi Console (akonadiconsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fb20709d8c0 (LWP 16397))]

Thread 4 (Thread 0x7fb1fbe8e700 (LWP 16400)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x003fc24c9abd in WTF::TCMalloc_PageHeap::scavengerThread
(this=) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:2571
#2  0x003fc24c9af9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:1767
#3  0x00366de07c53 in start_thread (arg=0x7fb1fbe8e700) at
pthread_create.c:308
#4  0x00366d6f4ecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7fb1baabb700 (LWP 16401)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x003fc220b3fd in JSC::BlockAllocator::blockFreeingThreadMain
(this=0x7fb1fb5f7398) at
/usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#2  0x003fc24f9316 in WTF::wtfThreadEntryPoint (param=0x265f640) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196
#3  0x00366de07c53 in start_thread (arg=0x7fb1baabb700) at
pthread_create.c:308
#4  0x00366d6f4ecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7fb1b96a8700 (LWP 16406)):
#0  0x00366de09b11 in __GI___pthread_mutex_lock (mutex=0x7fb1ac000aa0) at
pthread_mutex_lock.c:95
#1  0x0036716872f1 in g_mutex_lock (mutex=) at
gthread-posix.c:210
#2  0x003671648085 in g_main_context_iterate
(context=context@entry=0x7fb1ac0009e0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3668
#3  0x00367164829c in g_main_context_iteration (context=0x7fb1ac0009e0,
may_block=1) at gmain.c:3762
#4  0x003fb39a6cd6 in QEventDispatcherGlib::processEvents
(this=0x7fb1ac000900, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x003fb3978bdf in QEventLoop::processEvents
(this=this@entry=0x7fb1b96a7d20, flags=...) at kernel/qeventloop.cpp:149
#6  0x003fb3978ed5 in QEventLoop::exec (this=this@entry=0x7fb1b96a7d20,
flags=...) at kernel/qeventloop.cpp:204
#7  0x003fb387862f in QThread::exec (this=) at
thread/qthread.cpp:542
#8  0x003fb387accf in QThreadPrivate::start (arg=0x2753c20) at
thread/qthread_unix.cpp:338
#9  0x00366de07c53 in start_thread (arg=0x7fb1b96a8700) at
pthread_create.c:308
#10 0x00366d6f4ecd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7fb20709d8c0 (LWP 16397)):
[KCrash Handler]
#6  QList (l=..., this=0x7fffc5d3f350) at ../../src/corelib/tools/qlist.h:122
#7  QItemSelection (this=0x7fffc5d3f350) at itemviews/qitemselectionmodel.h:231
#8  QItemSelectionModel::selection (this=this@entry=0x26e23b0) at
itemviews/qitemselectionmodel.cpp:1508
#9  0x003fb570f204 in QItemSelectionModel::selectedRows
(this=this@entry=0x26e23b0, column=column@entry=0) at
itemviews/qitemselectionmodel.cpp:1452
#10 0x003fbe384103 in safeSelectedRows (selectionModel=0x26e23b0) at
/usr/src/debug/kdepimlibs-4.10.3/akonadi/standardactionmanager.cpp:164
#11 0x003fbe38d435 in
Akonadi::StandardActionManager::Private::updateActions (this=0x2a16170) at
/usr/src/debug/kdepimlibs-4.10.3/akonadi/standardactionmanager.cpp:463
#12 0x003fbe3862b9 in clipboardChanged (mode=,
this=) at
/usr/src/debug/kdepimlibs-4.10.3/akonadi/standardactionmanager.cpp:502
#13 Akonadi::StandardActionManager::qt_static_metacall (_o=,
_id=, _a=, _c=) at
/usr/src/debug/kdepimlibs-4.10.3/x86_64-redhat-linux-gnu/akonadi/moc_standardactionmanager.cpp:144
#14 0x003fb398dadc in QMetaObject::activate (sender=0x24417d0,
m=m@entry=0x3fb5c8c080 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffc5d3f760)
at kernel/qobject.cpp:3539
#15 0x003fb580970e in QClipboar

[Akonadi] [Bug 317743] Akonadi Console crash at exit

[kavol]

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

--- Comment #2 from kavol  ---
Created attachment 80209
  --> https://bugs.kde.org/attachment.cgi?id=80209&action=edit
New crash information added by DrKonqi

akonadiconsole (0.99) on KDE Platform 4.10.3 using Qt 4.8.4

- What I was doing when the application crashed:

I've just run akonadiconsole to verify current status. I switched between agent
list and the browser, unfolded the local folders hierarchy and tried to exit -
it crashed on exit.

- Unusual behavior I noticed:

I have troubles with local mail storage. After trying to remove and readd the
agent, on subsequent akonadiconsole run (which ended in this crash), the local
folders were shown twice in the browser, while only one agent instance existed
...

-- Backtrace (Reduced):
#6  0x003fb570c606 in QItemSelectionModel::hasSelection() const () from
/lib64/libQtGui.so.4
#7  0x003fb702bea9 in
KSelectionProxyModelPrivate::sourceRowsAboutToBeInserted (this=0x2067a20,
parent=..., start=0, end=0) at
/usr/src/debug/kdelibs-4.10.3/kdeui/itemviews/kselectionproxymodel.cpp:984
[...]
#9  0x003fb39d7834 in QAbstractItemModel::rowsAboutToBeInserted(QModelIndex
const&, int, int) () from /lib64/libQtCore.so.4
#10 0x003fb39708b5 in QAbstractItemModel::beginInsertRows(QModelIndex
const&, int, int) () from /lib64/libQtCore.so.4
#11 0x003fbe30498f in Akonadi::EntityTreeModelPrivate::monitoredItemAdded
(this=0x2061eb0, item=..., collection=...) at
/usr/src/debug/kdepimlibs-4.10.3/akonadi/entitytreemodel_p.cpp:1069

-- 
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 317743] Akonadi Console crash at exit

[kavol]

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

kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz

-- 
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 319574] New: kmail crashed after closing and reopening

[kavol]

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

Bug ID: 319574
   Summary: kmail crashed after closing and reopening
Classification: Unclassified
   Product: kmail2
   Version: 4.10.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz

Application: kmail (4.10.2)
KDE Platform Version: 4.10.2
Qt Version: 4.8.4
Operating System: Linux 3.8.11-200.fc18.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

I've accidentally closed kmail by hitting Ctrl+Q while the main window was
active.
Right after that I've realised the mistake, hit Alt+F2 to show krunner then
entered "kmail" and hit Enter - but instead of kmail I got DrKonqi ...

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fd9aba93880 (LWP 9517))]

Thread 4 (Thread 0x7fd997dfc700 (LWP 9572)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165
#1  0x0033f8a169bd in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x33f9401d00 ) at wtf/FastMalloc.cpp:2495
#2  0x0033f8a16ac9 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=) at wtf/FastMalloc.cpp:1618
#3  0x0033cf807d15 in start_thread (arg=0x7fd997dfc700) at
pthread_create.c:308
#4  0x0033cf0f248d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 3 (Thread 0x7fd9975eb700 (LWP 9573)):
#0  0x0033cf0e99ad in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x0033d3047d24 in g_main_context_poll (priority=2147483647, n_fds=1,
fds=0x7fd9900027c0, timeout=5100, context=0x7fd999a0) at gmain.c:3584
#2  g_main_context_iterate (context=context@entry=0x7fd999a0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3285
#3  0x0033d3047e44 in g_main_context_iteration (context=0x7fd999a0,
may_block=1) at gmain.c:3351
#4  0x0033d91a5fa6 in QEventDispatcherGlib::processEvents
(this=0x7fd998c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x0033d91765ef in QEventLoop::processEvents
(this=this@entry=0x7fd9975ead00, flags=...) at kernel/qeventloop.cpp:149
#6  0x0033d9176878 in QEventLoop::exec (this=0x7fd9975ead00, flags=...) at
kernel/qeventloop.cpp:204
#7  0x0033d9078980 in QThread::exec (this=) at
thread/qthread.cpp:542
#8  0x0033d907b95c in QThreadPrivate::start (arg=0x2edd330) at
thread/qthread_unix.cpp:338
#9  0x0033cf807d15 in start_thread (arg=0x7fd9975eb700) at
pthread_create.c:308
#10 0x0033cf0f248d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 2 (Thread 0x7fd9958bf700 (LWP 9782)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:217
#1  0x0033d907be17 in wait (time=3, this=0x2f15bf0) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=, mutex=0x2f93b98, time=3) at
thread/qwaitcondition_unix.cpp:158
#3  0x0033d906f69f in QThreadPoolThread::run (this=0x30479d0) at
concurrent/qthreadpool.cpp:141
#4  0x0033d907b95c in QThreadPrivate::start (arg=0x30479d0) at
thread/qthread_unix.cpp:338
#5  0x0033cf807d15 in start_thread (arg=0x7fd9958bf700) at
pthread_create.c:308
#6  0x0033cf0f248d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 1 (Thread 0x7fd9aba93880 (LWP 9517)):
[KCrash Handler]
#6  0x0033d90c0896 in QString::operator== (this=0x33dd757b90
, other=...) at tools/qstring.cpp:2192
#7  0x0033ded5f1b4 in KStatusNotifierItem::setToolTipSubTitle
(this=0x3064a70, subTitle=...) at
/usr/src/debug/kdelibs-4.10.2/kdeui/notifications/kstatusnotifieritem.cpp:419
#8  0x0033fd0e1c9f in KMail::KMSystemTray::unreadMail
(this=this@entry=0x3064a70, model=model@entry=0x278bfa0, parentIndex=...) at
/usr/src/debug/kdepim-4.10.2/kmail/kmsystemtray.cpp:392
#9  0x0033fd0e1b30 in KMail::KMSystemTray::unreadMail
(this=this@entry=0x3064a70, model=model@entry=0x278bfa0, parentIndex=...) at
/usr/src/debug/kdepim-4.10.2/kmail/kmsystemtray.cpp:385
#10 0x0033fd0e1e73 in KMail::KMSystemTray::initListOfCollection
(this=0x3064a70) at /usr/src/debug/kdepim-4.10.2/kmail/kmsystemtray.cpp:351
#11 0x0033fd0ee970 in KMKernel::toggleSystemTray (this=0x7fff06cbad70) at
/usr/src/debug/kdepim-4.10.2/kmail/kmkernel.cpp:2064
#12 0x0033fd140557 in KMMainWidget::readConfig (this=this@entry=0x3b2a8e0)
at /usr/src/debug/kdepim-4.10.2/kmail/kmmainwidget.cpp:979
#13 0x0033fd140a60 in KMMainWidget::KMMainWidget (this=0x3b2a8e0,
parent=, aGUIClient=0x2ebf3d0, actionCollection=,
config=...) at /usr/src/debug/kdepim-4.10.2/kmail/kmmainwidget.cpp:267

[kmail2] [Bug 312302] KMail2 crashes while forwarding mail

[kavol]

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

--- Comment #8 from kavol  ---
Created attachment 79540
  --> https://bugs.kde.org/attachment.cgi?id=79540&action=edit
New crash information added by DrKonqi

kmail (4.10.2) on KDE Platform 4.10.2 using Qt 4.8.4

- What I was doing when the application crashed:

still valid using the newer version 4.10.2

-- Backtrace (Reduced):
#6  0x00391a043e44 in KMime::Content::parent (this=0x27d4eb0) at
/usr/src/debug/kdepimlibs-4.10.2/kmime/kmime_content.cpp:952
#7  0x00391a046fe7 in KMime::Content::addContent (this=0x2f99550,
c=0x27d4eb0, prepend=false) at
/usr/src/debug/kdepimlibs-4.10.2/kmime/kmime_content.cpp:582
#8  0x003e3ec17546 in TemplateParser::TemplateParser::createMultipartMixed
(this=this@entry=0x7fff049ca900, ac=..., textPart=textPart@entry=0x330c930) at
/usr/src/debug/kdepim-4.10.2/templateparser/templateparser.cpp:1298
#9  0x003e3ec1b850 in
TemplateParser::TemplateParser::addProcessedBodyToMessage
(this=this@entry=0x7fff049ca900, plainBody=..., htmlBody=...) at
/usr/src/debug/kdepim-4.10.2/templateparser/templateparser.cpp:1275
#10 0x003e3ec1bc44 in TemplateParser::TemplateParser::processWithTemplate
(this=0x7fff049ca900, tmpl=...) at
/usr/src/debug/kdepim-4.10.2/templateparser/templateparser.cpp:1187

-- 
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 319047] New: Support content type message/partial (RFC 2046) reassembling messages

[kavol]

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

Bug ID: 319047
   Summary: Support content type message/partial (RFC 2046)
reassembling messages
Classification: Unclassified
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: ka...@seznam.cz
CC: an...@kde.org, ba...@opensolutions.ie,
ka...@seznam.cz, k...@carewolf.com, mon...@kde.org,
pancho...@riseup.net, psychon...@nothingisreal.com

there were additional comments to the original bug, including reference to the
requested testcase, but seems none of the interested users has the right to
reopen, so cloning ...

+++ This bug was initially created as a clone of Bug #67516 +++

Version:(using KDE KDE 3.1.3)
Installed from:Compiled From Sources
OS:  Linux

When I receive a message that has been split into multiple message by the
senders system, KMail does not reassemble the partial messages into one whole
message.

This seems to be covered by RFC 2046.

Headers of a message I received are:

MIME-version: 1.0
Content-type: message/partial;
  number=1;
  id="0hnz035n0ps...@mentat.ucd.ie"
Content-type: message/partial; id="0hnz088cdpf...@mentat.ucd.ie"; number=1

and:

MIME-version: 1.0
Content-type: message/partial;
  id="0hnz088cdpf...@mentat.ucd.ie";
  number=2;
  total=2

and:

MIME-version: 1.0
Content-type: message/partial;
  total=2;
  number=2;
  id="0hnz035n0ps...@mentat.ucd.ie"

-- 
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 312302] KMail2 crashes while forwarding mail

[kavol]

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

kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz

-- 
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 312302] KMail2 crashes while forwarding mail

[kavol]

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

--- Comment #7 from kavol  ---
Created attachment 79002
  --> https://bugs.kde.org/attachment.cgi?id=79002&action=edit
New crash information added by DrKonqi

kmail (4.10.1) on KDE Platform 4.10.1 using Qt 4.8.4

- What I was doing when the application crashed:

I've tried to forward (inline) an email with two jpegs. KMail crashed right
after choosing the menu entry to forward.

-- Backtrace (Reduced):
#6  0x00384b843e44 in KMime::Content::parent (this=0x2b0a940) at
/usr/src/debug/kdepimlibs-4.10.1/kmime/kmime_content.cpp:952
#7  0x00384b846fe7 in KMime::Content::addContent (this=0x1f8e0f0,
c=0x2b0a940, prepend=false) at
/usr/src/debug/kdepimlibs-4.10.1/kmime/kmime_content.cpp:582
#8  0x003864017546 in TemplateParser::TemplateParser::createMultipartMixed
(this=this@entry=0x72955320, ac=..., textPart=textPart@entry=0x217e6a0) at
/usr/src/debug/kdepim-4.10.1/templateparser/templateparser.cpp:1298
#9  0x00386401b850 in
TemplateParser::TemplateParser::addProcessedBodyToMessage
(this=this@entry=0x72955320, plainBody=..., htmlBody=...) at
/usr/src/debug/kdepim-4.10.1/templateparser/templateparser.cpp:1275
#10 0x00386401bc44 in TemplateParser::TemplateParser::processWithTemplate
(this=0x72955320, tmpl=...) at
/usr/src/debug/kdepim-4.10.1/templateparser/templateparser.cpp:1187

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

[kavol]

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

--- Comment #13 from kavol  ---
Created attachment 78623
  --> https://bugs.kde.org/attachment.cgi?id=78623&action=edit
New crash information added by DrKonqi

kmail (4.10.1) on KDE Platform 4.10.1 using Qt 4.8.4

- What I was doing when the application crashed:

I've closed kmail as it was somehow unresponsive. Then I've stopped akonadi
("akonadictl stop") as it usually helps in such cases. Then I've trie to start
kmail and it crashed immediately.

Note that I've closed kmail via menu, there may have been some processes left
...

-- Backtrace (Reduced):
#6  0x7f5649e8c16b in KStatusNotifierItem::setStatus (this=0x241c5e0,
status=KStatusNotifierItem::Active) at
/usr/src/debug/kdelibs-4.10.1/kdeui/notifications/kstatusnotifieritem.cpp:161
#7  0x7f56490f1cfd in KMail::KMSystemTray::setMode (this=0x241c5e0,
newMode=0) at /usr/src/debug/kdepim-4.10.1/kmail/kmsystemtray.cpp:161
#8  0x7f56490ff8e6 in KMKernel::toggleSystemTray (this=0x7fffa30a5de0) at
/usr/src/debug/kdepim-4.10.1/kmail/kmkernel.cpp:2063
#9  0x7f56491514d7 in KMMainWidget::readConfig (this=this@entry=0x22965f0)
at /usr/src/debug/kdepim-4.10.1/kmail/kmmainwidget.cpp:979
#10 0x7f56491519e0 in KMMainWidget::KMMainWidget (this=0x22965f0,
parent=, aGUIClient=0x2c27c20, actionCollection=,
config=...) at /usr/src/debug/kdepim-4.10.1/kmail/kmmainwidget.cpp:267

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

[kavol]

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

--- Comment #8 from kavol  ---
Created attachment 78599
  --> https://bugs.kde.org/attachment.cgi?id=78599&action=edit
New crash information added by DrKonqi

kmail (4.10.1) on KDE Platform 4.10.1 using Qt 4.8.4

- What I was doing when the application crashed:

I've closed kmail as it was somehow unresponsive. Then I've stopped akonadi
("akonadictl stop") as it usually helps in such cases. Then I've trie to start
kmail and it crashed immediately.

Note that I've closed kmail via menu, there may have been some processes left
...

-- Backtrace (Reduced):
#6  0x7f5649e8c16b in KStatusNotifierItem::setStatus (this=0x241c5e0,
status=KStatusNotifierItem::Active) at
/usr/src/debug/kdelibs-4.10.1/kdeui/notifications/kstatusnotifieritem.cpp:161
#7  0x7f56490f1cfd in KMail::KMSystemTray::setMode (this=0x241c5e0,
newMode=0) at /usr/src/debug/kdepim-4.10.1/kmail/kmsystemtray.cpp:161
#8  0x7f56490ff8e6 in KMKernel::toggleSystemTray (this=0x7fffa30a5de0) at
/usr/src/debug/kdepim-4.10.1/kmail/kmkernel.cpp:2063
#9  0x7f56491514d7 in KMMainWidget::readConfig (this=this@entry=0x22965f0)
at /usr/src/debug/kdepim-4.10.1/kmail/kmmainwidget.cpp:979
#10 0x7f56491519e0 in KMMainWidget::KMMainWidget (this=0x22965f0,
parent=, aGUIClient=0x2c27c20, actionCollection=,
config=...) at /usr/src/debug/kdepim-4.10.1/kmail/kmmainwidget.cpp:267

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

[kavol]

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

kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz

-- 
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 302750] Akonadi IMAP resource crashed on logout

[kavol]

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

--- Comment #9 from kavol  ---
Created attachment 78463
  --> https://bugs.kde.org/attachment.cgi?id=78463&action=edit
New crash information added by DrKonqi

akonadi_imap_resource (4.10) on KDE Platform 4.10.1 using Qt 4.8.4

- What I was doing when the application crashed:

I've just tried to log out, and DrKonqi appeared ...

-- Backtrace (Reduced):
#7  0x7ff840869bd3 in ~Task (this=0x7a11c2d0, __in_chrg=) at /usr/src/debug/kdepimlibs-4.10.1/akonadi/resourcescheduler_p.h:67
#8  Akonadi::ResourceBase::cancelTask (this=this@entry=0x1a296b0) at
/usr/src/debug/kdepimlibs-4.10.1/akonadi/resourcebase.cpp:861
#9  0x7ff840869d39 in Akonadi::ResourceBase::cancelTask (this=0x1a296b0,
msg=...) at /usr/src/debug/kdepimlibs-4.10.1/akonadi/resourcebase.cpp:889
#10 0x0041e8cb in ResourceState::cancelTask (this=0x1a2b480,
errorString=...) at
/usr/src/debug/kdepim-runtime-4.10.1/resources/imap/resourcestate.cpp:390
#11 0x004453a1 in ResourceTask::cancelTask (this=0x1ba71a0,
errorString=...) at
/usr/src/debug/kdepim-runtime-4.10.1/resources/imap/resourcetask.cpp:285

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

[Akonadi] [Bug 302750] Akonadi IMAP resource crashed on logout

[kavol]

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

kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz

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

[Bug 67516] Support content type message/partial (RFC 2046) reassembling messages

[kavol]

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

--- Comment #8 from kavol  ---
(In reply to comment #5)
> I've never seen such partial messages...

great, and I've never had any music in MusePack or WavePack or some other
formats that are supported by Qmmp - yet it hadn't prevented me from
translating the respective plugins when I was working on Qmmp translation to
Czech, and it doesn't prevent me from building these plugins (and resolving any
build issues associated with them) when maintaining the Qmmp package in Fedora
...

> Kavol, could you please post an example?

no, because 10 MiB attachments are not allowed here

(In reply to comment #7)
> Yes, I remember and found some evidence that they are still produced by
> recent Outlook versions. However, these days they seem to be mostly used for
> obfuscating malware, because split up attachments can't be checked by
> antivirus software.

please do more research

these days, they are *still* produced by multipurpose office machines when
sending large emails (bix scans and faxes converted to emails)

> The security problems are so large that even Exchange Server 2007 blocks
> them, as well as Qmail and probably more mail servers and antivirus
> software. Finally, US-CERT explicitely warns from automatically reassembling
> the partial messages (https://www.kb.cert.org/vuls/id/836088) and proposes
> rejecting partial messages.

ahem, isn't this a bit incomplete?

- US-CERT mentions blocking this type as one of *four* possible solutions ...

btw, isn't a reference to a document that is more than ten years old a bit
inappropriate when you are talking about "these days"?

> So if some really stable code

I'm just sad that kmail team hadn't demanded "really stable code" also when
transitioning to Akonadi ...

> with secure logics and a foolproof UI existed,
> we might want to think about it.
> But it doesn't,

yes, this is the point of this RFE that we, the humble users, are asking you,
the mighty developers, to write it ...

btw, I really do not understand what do you mean by demanding a code that has
its own UI? - kmail is *the* UI, what do you need is the backend which will
compose the parts into one message ...

as for the UI, you even have a solid basis in kmail for this - it could be the
same like when kmail is asking about displaying html content or reading the
external links

> and the demand has been ceasing,

[Citation needed]

I still need this when receiving large attachments from our office machine;
meanwhile, the number of people employed in the same office, thus using the
same machine, has grown ...

> so I think it's really not worth the hassle.
> Therefore I'm marking this WONTFIX.

hm, what would it take to reconsider?

-- 
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 308545] New: kmail crash after stopping akonadiserver

[kavol]

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

Bug ID: 308545
  Severity: crash
   Version: 4.9.2
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: kmail crash after stopping akonadiserver
Classification: Unclassified
OS: Linux
  Reporter: ka...@seznam.cz
  Hardware: Fedora RPMs
Status: UNCONFIRMED
 Component: general
   Product: kmail2

Application: kmail (4.9.2)
KDE Platform Version: 4.9.2
Qt Version: 4.8.2
Operating System: Linux 3.6.1-1.fc17.x86_64 x86_64
Distribution: "Fedora release 17 (Beefy Miracle)"

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

Akonadi got unrensponsive, I could not display contents of any folder, all I
got was the rotating "wait" symbol, so I decided to stop Akonadiserver and
start it again.
After stopping, kmail showed some error message about inability to access
something, and after clicking ok in that dialogue window, it crashed.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7faf40fc3880 (LWP 32431))]

Thread 3 (Thread 0x7faf339f5700 (LWP 32442)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166
#1  0x003c0981677d in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x3c0a200980) at wtf/FastMalloc.cpp:2495
#2  0x003c09816889 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=) at wtf/FastMalloc.cpp:1618
#3  0x003b36407d14 in start_thread (arg=0x7faf339f5700) at
pthread_create.c:309
#4  0x003b35cf167d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7faf330dc700 (LWP 32443)):
#0  0x003b35ce8bcf in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x003b38c47af4 in g_main_context_poll (n_fds=1, fds=0x7faf2c0029c0,
timeout=7786, context=0x7faf2c0009a0, priority=) at gmain.c:3440
#2  g_main_context_iterate (context=context@entry=0x7faf2c0009a0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
gmain.c:3141
#3  0x003b38c47c14 in g_main_context_iteration (context=0x7faf2c0009a0,
may_block=1) at gmain.c:3207
#4  0x003bfeda44e6 in QEventDispatcherGlib::processEvents
(this=0x7faf2c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x003bfed7510f in QEventLoop::processEvents
(this=this@entry=0x7faf330dbd20, flags=...) at kernel/qeventloop.cpp:149
#6  0x003bfed75398 in QEventLoop::exec (this=0x7faf330dbd20, flags=...) at
kernel/qeventloop.cpp:204
#7  0x003bfec78650 in QThread::exec (this=) at
thread/qthread.cpp:501
#8  0x003bfec7b5eb in QThreadPrivate::start (arg=0x19b0c90) at
thread/qthread_unix.cpp:307
#9  0x003b36407d14 in start_thread (arg=0x7faf330dc700) at
pthread_create.c:309
#10 0x003b35cf167d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7faf40fc3880 (LWP 32431)):
[KCrash Handler]
#6  0x003b35c35925 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x003b35c370d8 in __GI_abort () at abort.c:91
#8  0x003bfec71234 in qt_message_output (msgType=msgType@entry=QtFatalMsg,
buf=) at global/qglobal.cpp:2260
#9  0x003bfec713e8 in qt_message(QtMsgType, const char *, typedef
__va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg,
msg=0x3c01991dd0 "Fatal Error: Accessed global static '%s *%s()' after
destruction. Defined at %s:%d", ap=ap@entry=0x7fffa5e966f8) at
global/qglobal.cpp:2306
#10 0x003bfec71574 in qFatal (msg=) at
global/qglobal.cpp:2489
#11 0x003c018fdc3f in operator-> (this=) at
/usr/src/debug/kdelibs-4.9.2/kdeui/widgets/kmainwindow.cpp:214
#12 operator* (this=) at
/usr/src/debug/kdelibs-4.9.2/kdeui/widgets/kmainwindow.cpp:214
#13 KMainWindow::memberList () at
/usr/src/debug/kdelibs-4.9.2/kdeui/widgets/kmainwindow.cpp:1176
#14 0x003c13eecc84 in KMKernel::dumpDeadLetters (this=0x7eaf) at
/usr/src/debug/kdepim-4.9.2/kmail/kmkernel.cpp:1332
#15 0x003c13eecff7 in kmCrashHandler (sigId=) at
/usr/src/debug/kdepim-4.9.2/kmail/kmkernel.cpp:1176
#16 0x003c018a51c8 in KCrash::defaultCrashHandler (sig=6) at
/usr/src/debug/kdelibs-4.9.2/kdeui/util/kcrash.cpp:307
#17 
#18 0x003b35c35925 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#19 0x003b35c370d8 in __GI_abort () at abort.c:91
#20 0x003bfec71234 in qt_message_output (msgType=msgType@entry=QtFatalMsg,
buf=) at global/qglobal.cpp:2260
#21 0x003bfec713e8 in qt_message(QtMsgType, const char *, typedef
__va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg,
msg=0x3c12b1bb28 "Fatal Error: Accessed global static '%s *%s()' after
destruction. Defined at %s:%d", ap=ap@entry=0x7fffa5e97158) at
global/qglobal.cpp:2306
#22 0x003bfec71574 in qFatal (msg=) at
global/qglo

[Bug 306330] searching folder list hides contents of the chosen folder

[kavol]

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

--- Comment #1 from kavol  ---
Created attachment 73699
  --> https://bugs.kde.org/attachment.cgi?id=73699&action=edit
problem screenshot

-- 
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 306330] New: searching folder list hides contents of the chosen folder

[kavol]

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

Bug ID: 306330
  Severity: normal
   Version: 4.8.5
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: searching folder list hides contents of the chosen
folder
Classification: Unclassified
OS: Linux
  Reporter: ka...@seznam.cz
  Hardware: Gentoo Packages
Status: UNCONFIRMED
 Component: UI
   Product: kmail2

Recently, I've found that I have too many folders to browse the tree structure
manually and I have activated the search box. I've been using this mainly for
sorting emails - moving (by mouse drag) resolved issues from the inbox, which I
use as a kind of ToDo list, to the appropriate "archive" folder.
You may find this workflow obscure, but it has worked for me for years. Now,
right after simplifying it with the search box, the first update has broken it
- when I start typing to search, the contents of the selected folder (the
inbox) gets hidden, so I don't see the message which I want to drag to the
destination folder, thus I cannot move it.

Reproducible: Always

Steps to Reproduce:
1. activate quicksearch field in folder list
nastavení (settings) => vzhled (appearance?) => uspořádání (layout?) => seznam
složek/zobrazovat pole pro rychlé hledání (folder list/show quicksearch?)
2. select some folder that is not empty so that you see list of messages in
that folder
3. select some message from that folder so that you see the contents of the
message
4. start typing in the folder quicksearch box
Actual Results:  
the messages shown and the contents of the selected message disappear

Expected Results:  
the contents of the selected folder & message are shown until you explicitly
select different ones (e.g. by clicking on something that has been found via
the quicksearch)

-- 
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 305280] Kmail crashes wyle moving a folder to the parant folder

[kavol]

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

--- Comment #4 from kavol  ---
Created attachment 73682
  --> https://bugs.kde.org/attachment.cgi?id=73682&action=edit
New crash information added by DrKonqi

kmail (4.8.5) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.2

- What I was doing when the application crashed:

I've moved (via mouse drag) a folder to another folder. Then I've moved another
folder to the same destination folder and kmail crashed instantly on finishing
the move (releasing the mouse button).

-- Backtrace (Reduced):
#6  QModelIndex (other=..., this=0x7fff90b42390) at
../../include/QtCore/../../src/corelib/kernel/qabstractitemmodel.h:65
#7  QSortFilterProxyModel::parent (this=0xffcb70, child=) at
itemviews/qsortfilterproxymodel.cpp:1659
#8  0x7f905e458ddf in parent (this=0x7fff90b423e0) at
/usr/include/qt4/QtCore/qabstractitemmodel.h:393
#9  KIdentityProxyModel::parent (this=0x194e9c0, child=...) at
/var/tmp/portage/kde-base/kdelibs-4.8.5/work/kdelibs-4.8.5/kdeui/itemviews/kidentityproxymodel.cpp:359
#10 0x7f9055eda3eb in parent (this=0x7fff90b42470) at
/usr/include/qt4/QtCore/qabstractitemmodel.h:393

-- 
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 305280] Kmail crashes wyle moving a folder to the parant folder

[kavol]

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

kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz

-- 
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 292523] kmail crashes on viewing html mail

[kavol]

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

--- Comment #9 from kavol  ---
(In reply to comment #8)
> FWIW, I am running 4.8.4 (64-bit) and I'm still having problems with KMail
> crashing on HTML messages. If I have problems with the next version of KMail
> I'll report it and reopen this ticket. Count on it!

does your kmail crash trying to view the message attached to this bugreport?

- if not, I guess it'd be better to open a new bug rather than to reopen this
one

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

[Bug 292523] kmail crashes on viewing html mail

[kavol]

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

--- Comment #7 from kavol  ---
ok, the reproducer does not crash kmail any more, tried with 4.8.3

-- 
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 302301] DATA LOSS! kmail crashed after trying to move messagess and the source imap folder got all contents deleted

[kavol]

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

--- Comment #2 from kavol  ---
hm, I don't see 4.8.5 on the release schedule ...
http://techbase.kde.org/Schedules/KDE4/4.8_Release_Schedule

-- 
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 302301] New: DATA LOSS! kmail crashed after trying to move messagess and the source imap folder got all contents deleted

[kavol]

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

Bug ID: 302301
  Severity: crash
   Version: 4.8.3
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: DATA LOSS! kmail crashed after trying to move
messagess and the source imap folder got all contents
deleted
Classification: Unclassified
OS: Linux
  Reporter: ka...@seznam.cz
  Hardware: Gentoo Packages
Status: UNCONFIRMED
 Component: general
   Product: kmail2

Application: kmail (4.8.3)
KDE Platform Version: 4.8.3 (4.8.3)
Qt Version: 4.8.1
Operating System: Linux 3.2.12-gentoo x86_64
Distribution: "Gentoo Base System release 2.1"

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

I've tried to move a few messages from an IMAP folder to a local folder via
mouse drag.
When I've tried to drop the messages onto the destination folder, it didn't
react to mouse release and the cursor stayed overimposed with the messages
symbol.
While holding the cursor over the target folder, I've tried to click.
KMail crashed immediatelly.
Checking the IMAP server via web interface, I've found that the folder got
completely emptied.
I've immediately backed up the remnants in the cache
~/.local/share/akonadi/file_db_data and after a few minutes the files
corresponding to messages in that folder disappeared from the cache.
Unfortunately, not all of the messages were in the cache when I did the backup,
so I've LOST MESSAGES PERMANENTLY - no, they are NOT present in the target
local folder, however the few messages I've tried to move are there.

Note that DrKonqi suggests a lot duplicates, however two things that look quite
different
- all the other crashes talk about moving folders, I've just moved messages
- I haven't found any mention of data loss in other cases

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f1013452760 (LWP 2537))]

Thread 4 (Thread 0x7f0ff2feb700 (LWP 2592)):
#0  pthread_cond_wait () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7f1005735514 in scavengerThread (this=0x7f10060f10c0) at
wtf/FastMalloc.cpp:2495
#2  WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f10060f10c0) at
wtf/FastMalloc.cpp:1618
#3  0x7f100e57ad0c in start_thread (arg=0x7f0ff2feb700) at
pthread_create.c:301
#4  0x7f1010760bed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 3 (Thread 0x7f0ff26ea700 (LWP 2595)):
#0  0x7f1010757d13 in *__GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7f100902eb84 in g_main_context_poll (n_fds=1, fds=0x7f0fec0013d0,
timeout=-1, context=0x7f0fec000990, priority=) at gmain.c:3402
#2  g_main_context_iterate (context=0x7f0fec000990, block=1, dispatch=1,
self=) at gmain.c:3084
#3  0x7f100902f041 in g_main_context_iteration (context=0x7f0fec000990,
may_block=1) at gmain.c:3152
#4  0x7f10110e1106 in QEventDispatcherGlib::processEvents
(this=0x7f0fec0008b0, flags=) at
kernel/qeventdispatcher_glib.cpp:426
#5  0x7f10110b0f92 in QEventLoop::processEvents (this=,
flags=...) at kernel/qeventloop.cpp:149
#6  0x7f10110b1245 in QEventLoop::exec (this=0x7f0ff26e9e20, flags=...) at
kernel/qeventloop.cpp:204
#7  0x7f1010faf0e8 in QThread::exec (this=) at
thread/qthread.cpp:501
#8  0x7f1010fb175b in QThreadPrivate::start (arg=0xb674e0) at
thread/qthread_unix.cpp:298
#9  0x7f100e57ad0c in start_thread (arg=0x7f0ff26ea700) at
pthread_create.c:301
#10 0x7f1010760bed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7f0ff0a6c700 (LWP 7623)):
#0  pthread_cond_timedwait () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216
#1  0x7f1010fb25d2 in wait (time=3, this=0x2305b40) at
thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=, mutex=0x2318ae8, time=3) at
thread/qwaitcondition_unix.cpp:158
#3  0x7f1010fa5d9f in QThreadPoolThread::run (this=0x2319d30) at
concurrent/qthreadpool.cpp:141
#4  0x7f1010fb175b in QThreadPrivate::start (arg=0x2319d30) at
thread/qthread_unix.cpp:298
#5  0x7f100e57ad0c in start_thread (arg=0x7f0ff0a6c700) at
pthread_create.c:301
#6  0x7f1010760bed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f1013452760 (LWP 2537)):
[KCrash Handler]
#6  QModelIndex (other=..., this=0x7fffd5ef8220) at
../../include/QtCore/../../src/corelib/kernel/qabstractitemmodel.h:65
#7  QSortFilterProxyModel::parent (this=0xa07630, child=) at
itemviews/qsortfilterproxymodel.cpp:1659
#8  0x7f1012e0d8df in parent (this=0x7fffd5ef8270) at
/usr/include/qt4/QtCore/qabstractitemmodel.h:393
#9  KIdentityProxyModel::parent (this=0x13a3310, child=...) at
/var/tmp/portage/kde-base/kdelibs-4.8.3/work/kdelibs-4.8.3/kdeui/itemviews/kidentityproxymodel.cpp:358
#10 0x7f1012e0d8df in parent (th

[Bug 301794] New: kmail crashed on startup

[kavol]

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

Bug ID: 301794
  Severity: crash
   Version: 4.8.3
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: kmail crashed on startup
Classification: Unclassified
OS: Linux
  Reporter: ka...@seznam.cz
  Hardware: Fedora RPMs
Status: UNCONFIRMED
 Component: general
   Product: kmail2

Application: kmail (4.8.3)
KDE Platform Version: 4.8.3 (4.8.3)
Qt Version: 4.8.2
Operating System: Linux 3.3.7-1.fc17.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

It just crashed on startup. It looks like the old error which is marked as
fixed, hence opening a new bug for the new version.

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

Thread 5 (Thread 0x7f81b976f700 (LWP 912)):
#0  0x7f81dbfd4d03 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x7f81dcc09182 in QProcessManager::run (this=0x7f81dcf803c0) at
io/qprocess_unix.cpp:245
#2  0x7f81dcb2f5eb in QThreadPrivate::start (arg=0x7f81dcf803c0) at
thread/qthread_unix.cpp:307
#3  0x7f81dd75ed14 in start_thread (arg=0x7f81b976f700) at
pthread_create.c:309
#4  0x7f81dbfdb99d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 4 (Thread 0x7f81b3fff700 (LWP 1244)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166
#1  0x7f81d509977d in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f81d5a839a0) at wtf/FastMalloc.cpp:2495
#2  0x7f81d5099889 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=) at wtf/FastMalloc.cpp:1618
#3  0x7f81dd75ed14 in start_thread (arg=0x7f81b3fff700) at
pthread_create.c:309
#4  0x7f81dbfdb99d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 3 (Thread 0x7f81b37fe700 (LWP 1245)):
#0  0x7f81dbfd2eef in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x7f81d0ef69b4 in g_main_context_poll (n_fds=1, fds=0x7f81ac0027c0,
timeout=7823, context=0x7f81ac0009a0, priority=) at gmain.c:3440
#2  g_main_context_iterate (context=context@entry=0x7f81ac0009a0,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3141
#3  0x7f81d0ef6ad4 in g_main_context_iteration (context=0x7f81ac0009a0,
may_block=1) at gmain.c:3207
#4  0x7f81dcc58506 in QEventDispatcherGlib::processEvents
(this=0x7f81ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x7f81dcc2913f in QEventLoop::processEvents
(this=this@entry=0x7f81b37fdd20, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f81dcc293c8 in QEventLoop::exec (this=0x7f81b37fdd20, flags=...) at
kernel/qeventloop.cpp:204
#7  0x7f81dcb2c650 in QThread::exec (this=) at
thread/qthread.cpp:501
#8  0x7f81dcb2f5eb in QThreadPrivate::start (arg=0xe9cdc0) at
thread/qthread_unix.cpp:307
#9  0x7f81dd75ed14 in start_thread (arg=0x7f81b37fe700) at
pthread_create.c:309
#10 0x7f81dbfdb99d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7f81b0eb7700 (LWP 1251)):
[KCrash Handler]
#6  lockInline (this=0x65007200636568) at /usr/include/QtCore/qmutex.h:187
#7  QMutexLocker (m=0x65007200636568, this=0x7f81b0eb6450) at
/usr/include/QtCore/qmutex.h:109
#8  Soprano::Error::ErrorCache::clearError (this=this@entry=0x12abf90) at
/usr/src/debug/soprano-2.7.6/soprano/error.cpp:238
#9  0x7f81dd4c4ab0 in Soprano::Error::ErrorCache::setError (this=0x12abf90,
error=...) at /usr/src/debug/soprano-2.7.6/soprano/error.cpp:225
#10 0x7f81d2917f0c in Soprano::Client::DBusModel::executeQuery
(this=0x12abf80, query=..., language=, userQueryLanguage=...) at
/usr/src/debug/soprano-2.7.6/client/dbus/dbusmodel.cpp:112
#11 0x7f81dfe617b5 in Nepomuk::MainModel::executeQuery (this=0xe5c470,
query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...)
at /usr/src/debug/kdelibs-4.8.3/nepomuk/core/nepomukmainmodel.cpp:212
#12 0x7f81dfe56cda in Nepomuk::ResourceData::load
(this=this@entry=0x7f8168002df0) at
/usr/src/debug/kdelibs-4.8.3/nepomuk/core/resourcedata.cpp:427
#13 0x7f81dfe57841 in Nepomuk::ResourceData::property (this=0x7f8168002df0,
uri=...) at /usr/src/debug/kdelibs-4.8.3/nepomuk/core/resourcedata.cpp:268
#14 0x7f81dfe6b3f3 in Nepomuk::Resource::property (this=0x7f81b0eb6cb0,
uri=...) at /usr/src/debug/kdelibs-4.8.3/nepomuk/core/resource.cpp:301
#15 0x7f81d8997c7a in MessageCore::NepomukResourceRetrieverRunnable::run
(this=0x142bd90) at
/usr/src/debug/kdepim-4.8.3/messagecore/asyncnepomukresourceretriever.cpp:47
#16 0x7f81dcb2327d in QThreadPoolThread:

[Bug 300860] New: can't clear cache - wrong capitalisation

[kavol]

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

Bug ID: 300860
  Severity: normal
   Version: unspecified
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: can't clear cache - wrong capitalisation
Classification: Unclassified
OS: Linux
  Reporter: ka...@seznam.cz
  Hardware: Other
Status: UNCONFIRMED
 Component: akonadiconsole
   Product: Akonadi

I can't see some older messages in KMail and in Akonadiconsole browser. I've
tried to use "Synchronise folder recursively" function but it did not help.
Then I've tried to clear the cache, but this has failed.

Reproducible: Always

Steps to Reproduce:
1. run akonadiconsole
2. go to browser tab, rightclick on some collection
3. choose Clear Akonadi Cache
Actual Results:  
an error window appears, saying:

Table 'akonadi.pimitemtable' doesn't exist QMYSQL: Unable to execute query

Expected Results:  
no error, cache cleared, problems magically fixed

going to db browser/db console I can see there is "PimItemTable" not
"pimitemtable"

I've also found that there were some changes to capitalisation in bug #220007
however it seems this wasn't fixed in all places ...

-- 
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 290710] Crash after quitting Kontact while the summary widget wasn't fully loaded

[kavol]

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

--- Comment #3 from kavol  ---
Created attachment 70807
  --> https://bugs.kde.org/attachment.cgi?id=70807&action=edit
New crash information added by DrKonqi

korganizer (4.8.3- ()) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1

- What I was doing when the application crashed:

started korganizer from the systray then quickly closed it

-- Backtrace (Reduced):
#6  KJob::kill (this=0x2c02510, verbosity=KJob::EmitResult) at
/usr/src/debug/kdelibs-4.8.3/kdecore/jobs/kjob.cpp:111
#7  0x7f3b350a2357 in Akonadi::Session::clear (this=this@entry=0x2741c30)
at /usr/src/debug/kdepimlibs-4.8.3/akonadi/session.cpp:425
#8  0x7f3b350a25e4 in Akonadi::Session::~Session (this=0x2741c30,
__in_chrg=) at
/usr/src/debug/kdepimlibs-4.8.3/akonadi/session.cpp:394
#9  0x7f3b350a2629 in Akonadi::Session::~Session (this=0x2741c30,
__in_chrg=) at
/usr/src/debug/kdepimlibs-4.8.3/akonadi/session.cpp:396
#10 0x0034f7b87f32 in QObjectPrivate::deleteChildren
(this=this@entry=0x273ad20) at kernel/qobject.cpp:1908

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

[Bug 290710] Crash after quitting Kontact while the summary widget wasn't fully loaded

[kavol]

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

kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz

-- 
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 295546] Crash on exit after shutting akonadiserver down

[kavol]

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

--- Comment #1 from kavol  ---
Created attachment 69809
  --> https://bugs.kde.org/attachment.cgi?id=69809&action=edit
New crash information added by DrKonqi

kmail (4.8.1) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

- What I was doing when the application crashed:

I was deleting larger number of emails at a time.
During that, akonadi stopped action - the emails weren't moved to trash any
longer, and I could not display any email.
I've restarted akonadiserver via akonadiconsole, and the action resumed -
emails sheduled to be deleted were moving to trash again, and I could browse
other emails.
Meanwhile, I got some popups about conflicts which I've resolved by taking the
left (the only difference was in SEEN flag and timestamp).
Then akonadi stopped responding again.
I've restarted akonadiserver for the second time, and after a few seconds kmail
crashed.

-- Backtrace (Reduced):
#7  QSharedDataPointer (o=..., this=0x7fffe3de3120) at
/usr/include/QtCore/qshareddata.h:93
#8  assignEntityPrivate (one=..., other=...) at
/usr/src/debug/kdepimlibs-4.8.1/akonadi/entity.cpp:49
#9  0x003607e80854 in Akonadi::Entity::Entity (this=0x7fffe3de3160,
other=) at /usr/src/debug/kdepimlibs-4.8.1/akonadi/entity.cpp:56
#10 0x003607eefef5 in Akonadi::ConflictHandler::useLocalItem
(this=0x19e5be0) at
/usr/src/debug/kdepimlibs-4.8.1/akonadi/conflicthandling/conflicthandler.cpp:102
#11 0x003607ef00a8 in Akonadi::ConflictHandler::resolve (this=0x19e5be0) at
/usr/src/debug/kdepimlibs-4.8.1/akonadi/conflicthandling/conflicthandler.cpp:85

-- 
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 295546] Crash on exit after shutting akonadiserver down

[kavol]

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

kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz

-- 
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 295615] kmail crashes trying to edit subject/message body with some dictionary languages set in identity properties

[kavol]

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

--- Comment #10 from kavol  ---
cool, thanks guys!

-- 
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 295615] kmail crashes trying to edit subject/message body with some dictionary languages set in identity properties

[kavol]

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

kavol  changed:

   What|Removed |Added

Summary|kmail crashed after hitting |kmail crashes trying to
   |reply   |edit subject/message body
   ||with some dictionary
   ||languages set in identity
   ||properties

--- Comment #7 from kavol  ---
this problem seems to go away if you set a generic language instead of
country-specific variant within identity properties

I had "Anglický (Spojené království)" and after setting this to "Český" the
problem went away

I can re-trigger this problem by selecting any other option than "Český" - i.e.
all those in the "Language (country)" form

for more examples see bug #295759 comment #2 and comment #3

-- 
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 295759] Kontact crash when wrting new mail

[kavol]

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

kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz

--- Comment #7 from kavol  ---
(In reply to comment #3)
> Could the error be caused by a migration which forgot to update KMail's
> identity settings?

no, the error is caused by bad programming practices

you can work around the bug by setting "Norsk (bokmål)" instead of "Norsk
(bokmål) (Norge)" - but if you manually switch back to "Norsk (bokmål) (Norge)"
you'll see the bug again ... you can hardly accuse the migration process in
this case if you just select something within the configuration dialogue

btw, this is duplicate of bug #295615

-- 
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 295615] kmail crashed after hitting reply

[kavol]

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

--- Comment #6 from kavol  ---
Created attachment 69579
  --> https://bugs.kde.org/attachment.cgi?id=69579&action=edit
better log (with --track-origins=yes)

-- 
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 295615] kmail crashed after hitting reply

[kavol]

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

--- Comment #5 from kavol  ---
note that downgrading to kdepim 4.8.0 doesn't help the issue - the crash seems
to come from kdelibs (I haven't tried to downgrade also kdelibs yet due to
dependency hell)

-- 
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 295615] kmail crashed after hitting reply

[kavol]

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

--- Comment #4 from kavol  ---
Created attachment 69577
  --> https://bugs.kde.org/attachment.cgi?id=69577&action=edit
valgrind log from the crash

$ valgrind --log-file=kmail.log kmail
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
kmail2(1642): No language dictionaries for the language :  "cs" 

kmail2(1642): No language dictionaries for the language :  "cs" 

loaded the Generic plugin 
kmail2(1642)/kdepimlibs (mailtransport): Could not access Outbox. 
$ kmail2(1642): No language dictionaries for the language :  "cs" 

kmail2(1642): No language dictionaries for the language :  "cs" 

Enchant dict for "en_GB" 0x8006bd0 
*** KMail got signal 11 (Exiting)

-- 
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 287476] akonadi_maildir_resource trashes maildir with senseless directories

[kavol]

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

--- Comment #6 from kavol  ---
(In reply to comment #5)
> The current design requires that you have at least an outbox marked as such
> (sent-mail might also be needed). Might be that it needs to be also a local
> folder, but I;m not 100% sure of this. Otherwise you can't send mail.

hm, btw, shouldn't that be a property of the "mailtransport agent"?

- RFE for adding that configuration option, where to store the outgoing mail?

>  If you already have one set up correctly and you import another maildir, it
> will not add the folders.

well, despite the fact that "set up correctly" is as clear as mud, the problem
is if the order matters - you can't tell the resource migrator which order to
use, for example

not to mention that in practice, it doesn't work as expected - as I have those
folders on IMAP, yet still I get them created when adding local maildir ...

(well, I should use past tense, I haven't tested this with 4.8.1 - I don't want
to break my current setup in any way :-))

>  Unfortunately marking something as outbox is not trivial, there is no user
> GUI for that. 

see above, let's file RFE then - or is that a work in progress already?

btw, thinking about that, maybe it'd be better to have it per identity, not a
global setting ...

>  So I think here we have two problems:
> 1) it is hard to mark something as a special folder
> (inbox/outbox/sent-mail/trash/etc) from within the UI

I've found I can do that via editing the properties in Akonadiconsole ... but
there is no list what attributes I can use (oh, am I supposed to read the
source code?)

however, to be honest, I really do not understand the idea behind that

in KMail identities configuration, I can assign folders to serve some special
purpose for that identity - why not rely on this? why to have the folder role
defined as an attribute of the folder itself when it can have different role
for different identities (in theory ... :-))?

and where the role property gets used?
=> well, the answer to this also answers a question for which component to file
a RFE to be able to manage the folder properties this way?
(like if I choose something as a sent-mail folder, for example, in kmail
identity properties, then it should get marked
SpecialCollectionAttribute=sent-mail automagically ... the problem is the other
way round, if I unselect the folder in favour of another, should it get the
attribute removed?)

> 2) if the app runs in a different locale, it will not recognize the english
> named folders and will create new ones instead.

sounds like another RFE material ...

then names of subdirectories within the maildir should be in English, while it
should translate to folder names according to the locale being used - unless
the user renames the folder manually ... in that case, if the folder is one of
the standard ones then the user should be asked whether to rename also the
underlying directory name or just change the alias

-- 
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 295615] kmail crashed after hitting reply

[kavol]

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

--- Comment #3 from kavol  ---
Created attachment 69530
  --> https://bugs.kde.org/attachment.cgi?id=69530&action=edit
New crash information added by DrKonqi

kmail (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

- What I was doing when the application crashed:

I've tried to write a new e-mail, and kmail crashes when trying to write
subject line

-- Backtrace (Reduced):
#6  0x0038896abfb3 in eventFilter (e=0x7fffacd28fa0, o=0x15b7130,
this=0x1ea2b50) at
/usr/src/debug/kdelibs-4.8.1/kdeui/sonnet/highlighter.cpp:355
#7  Sonnet::Highlighter::eventFilter (this=0x1ea2b50, o=0x15b7130,
e=0x7fffacd28fa0) at
/usr/src/debug/kdelibs-4.8.1/kdeui/sonnet/highlighter.cpp:337
#8  0x0031687791d8 in
QCoreApplicationPrivate::sendThroughObjectEventFilters (this=,
receiver=0x15b7130, event=0x7fffacd28fa0) at kernel/qcoreapplication.cpp:986
#9  0x00316b7c995f in notify_helper (e=0x7fffacd28fa0, receiver=0x15b7130,
this=0x1027460) at kernel/qapplication.cpp:4546
#10 QApplicationPrivate::notify_helper (this=0x1027460, receiver=0x15b7130,
e=0x7fffacd28fa0) at kernel/qapplication.cpp:4522

-- 
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 295615] kmail crashed after hitting reply

[kavol]

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

kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz

-- 
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 295615] New: kmail crashed after hitting reply

[kavol]

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

Bug ID: 295615
  Severity: crash
   Version: 4.8
  Priority: NOR
  Assignee: kdepim-bugs@kde.org
   Summary: kmail crashed after hitting reply
Classification: Unclassified
OS: Linux
  Reporter: ka...@seznam.cz
  Hardware: Other
Status: UNCONFIRMED
 Component: composer
   Product: kmail2

SSIA

... oh, and the DrKonqi vs new bugs.kde.org issue is still unfixed

Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7ff8137fb840 (LWP 2564))]

Thread 3 (Thread 0x7ff804c6e700 (LWP 2575)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165
#1  0x00332fdb86ec in WTF::TCMalloc_PageHeap::scavengerThread
(this=0x333077cc20) at ../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:2495
#2  0x00332fdb8819 in WTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../../../Source/JavaScriptCore/wtf/FastMalloc.cpp:1618
#3  0x00315e607d90 in start_thread (arg=0x7ff804c6e700) at
pthread_create.c:309
#4  0x00315def0f5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7ff804355700 (LWP 2576)):
#0  0x00315dee85c3 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x003160e44fd8 in g_main_context_poll (n_fds=1, fds=0x7ff7fc0013e0,
priority=, timeout=6884, context=0x7ff7fc0009a0) at gmain.c:3402
#2  g_main_context_iterate (context=0x7ff7fc0009a0, block=,
dispatch=1, self=) at gmain.c:3084
#3  0x003160e4549c in g_main_context_iteration (context=0x7ff7fc0009a0,
may_block=1) at gmain.c:3152
#4  0x0031687a7dc6 in QEventDispatcherGlib::processEvents
(this=0x7ff7fc0008c0, flags=) at
kernel/qeventdispatcher_glib.cpp:426
#5  0x003168778182 in QEventLoop::processEvents (this=,
flags=...) at kernel/qeventloop.cpp:149
#6  0x0031687783d7 in QEventLoop::exec (this=0x7ff804354d40, flags=...) at
kernel/qeventloop.cpp:204
#7  0x003168678b27 in QThread::exec (this=) at
thread/qthread.cpp:501
#8  0x00316867bb6b in QThreadPrivate::start (arg=0x16167e0) at
thread/qthread_unix.cpp:298
#9  0x00315e607d90 in start_thread (arg=0x7ff804355700) at
pthread_create.c:309
#10 0x00315def0f5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7ff8137fb840 (LWP 2564)):
[KCrash Handler]
#6  0x00316878a3c4 in QObject::killTimer (this=0x746be90, id=1) at
kernel/qobject.cpp:1603
#7  0x003168796271 in stop (this=0x746be90) at kernel/qtimer.cpp:266
#8  QTimer::stop (this=0x746be90) at kernel/qtimer.cpp:263
#9  0x00316879628f in QTimer::start (this=0x746be90) at
kernel/qtimer.cpp:216
#10 0x0038896abfc4 in eventFilter (e=0x7a1326e0, o=0x1ce4570,
this=0xba0a580) at
/usr/src/debug/kdelibs-4.8.1/kdeui/sonnet/highlighter.cpp:356
#11 Sonnet::Highlighter::eventFilter (this=0xba0a580, o=0x1ce4570,
e=0x7a1326e0) at
/usr/src/debug/kdelibs-4.8.1/kdeui/sonnet/highlighter.cpp:337
#12 0x0031687791d8 in
QCoreApplicationPrivate::sendThroughObjectEventFilters (this=,
receiver=0x1ce4570, event=0x7a1326e0) at kernel/qcoreapplication.cpp:986
#13 0x00316b7c995f in notify_helper (e=0x7a1326e0, receiver=0x1ce4570,
this=0xb916a0) at kernel/qapplication.cpp:4546
#14 QApplicationPrivate::notify_helper (this=0xb916a0, receiver=0x1ce4570,
e=0x7a1326e0) at kernel/qapplication.cpp:4522
#15 0x00316b7ceede in QApplication::notify (this=,
receiver=, e=0x7a1326e0) at kernel/qapplication.cpp:3991
#16 0x003889651d56 in KApplication::notify (this=0x7a1336b0,
receiver=0x1ce4570, event=0x7a1326e0) at
/usr/src/debug/kdelibs-4.8.1/kdeui/kernel/kapplication.cpp:311
#17 0x00316877904c in QCoreApplication::notifyInternal
(this=0x7a1336b0, receiver=0x1ce4570, event=0x7a1326e0) at
kernel/qcoreapplication.cpp:876
#18 0x00316b868719 in QKeyMapper::sendKeyEvent (keyWidget=0x1ce4570,
grab=, type=QEvent::KeyPress, code=16777249, modifiers=...,
text=..., autorepeat=false, count=1, nativeScanCode=105,
nativeVirtualKey=65508, nativeModifiers=16) at kernel/qkeymapper_x11.cpp:1866
#19 0x00316b868b8b in QKeyMapperPrivate::translateKeyEvent (this=0xd09360,
keyWidget=0x1ce4570, event=0x7a1331c0, grab=false) at
kernel/qkeymapper_x11.cpp:1836
#20 0x00316b844ce4 in QApplication::x11ProcessEvent (this=0x7a1336b0,
event=0x7a1331c0) at kernel/qapplication_x11.cpp:3534
#21 0x00316b86c97c in x11EventSourceDispatch (s=0xb97840, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#22 0x003160e44acd in g_main_dispatch (context=0xb95de0) at gmain.c:2441
#23 g_main_context_dispatch (context=0xb95de0) at gmain.c:3011
#24 0x003160e452c8 in g_main_context_iterate (context=0xb95de0,
block=, dispatch=1, self=)

[Bug 292523] kmail crashes on viewing html mail

[kavol]

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





--- Comment #4 from kavol   2012-02-05 15:47:28 ---
(In reply to comment #2)
> Gentoo ? compile from scratch ? What is your compile option ?

not sure what do you mean ... the use flags are as follows:

[ebuild   R] kde-base/kmail-4.7.4-r1 USE="handbook kontact (-aqua) -debug
-test" 0 kB

and emerge info:

kika ~ # emerge --info
Portage 2.1.10.44 (default/linux/amd64/10.0/desktop/kde, gcc-4.5.3,
glibc-2.14.1-r2, 3.2.1-gentoo-r2 x86_64)
=
System uname:
Linux-3.2.1-gentoo-r2-x86_64-Intel-R-_Core-TM-2_CPU_T5500_@_1.66GHz-with-gentoo-2.1
Timestamp of tree: Sun, 05 Feb 2012 10:00:01 +
ccache version 3.1.6 [enabled]
app-shells/bash:  4.2_p20
dev-java/java-config: 2.1.11-r3
dev-lang/python:  2.7.2-r3, 3.1.4-r3, 3.2.2
dev-util/ccache:  3.1.6
dev-util/cmake:   2.8.7-r1
dev-util/pkgconfig:   0.26
sys-apps/baselayout:  2.1
sys-apps/openrc:  0.9.8.4
sys-apps/sandbox: 2.5
sys-devel/autoconf:   2.13, 2.68
sys-devel/automake:   1.11.2-r1
sys-devel/binutils:   2.22-r1
sys-devel/gcc:4.5.3-r2
sys-devel/gcc-config: 1.5-r2
sys-devel/libtool:2.4.2
sys-devel/make:   3.82-r3
sys-kernel/linux-headers: 3.2 (virtual/os-headers)
sys-libs/glibc:   2.14.1-r2
Repositories: gentoo
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* -@EULA AdobeFlash-10 AdobeFlash-10.1 dlj-1.1 googleearth"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe -ggdb"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt
/var/lib/hsqldb"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild
/etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=native -O2 -pipe -ggdb"
DISTDIR="/usr/portage/distfiles"
FEATURES="assume-digests binpkg-logs ccache collision-protect distlocks
ebuild-locks fixlafiles news parallel-fetch protect-owned sandbox sfperms
splitdebug strict unknown-features-warn unmerge-logs unmerge-orphans userfetch"
FFLAGS=""
GENTOO_MIRRORS="http://distfiles.gentoo.org";
LANG="sk_SK.UTF-8"
LC_ALL="sk_SK.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
LINGUAS="cs en sk"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --stats --timeout=180 --exclude=/distfiles
--exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X a52 aac accessibility acpi alsa amd64 amr amrnb amrwb bash-completion
berkdb branding bzip2 cairo cdda cddb cdr cli consolekit cracklib crypt css
cups cxx dbus declarative dga dmi dri dts dv dvd dvdnav dvdr emboss encode exif
fam ffmpeg flac fortran ftp gdbm gdu gif iconv imlib ipv6 java javascript
jingle jpeg jpeg2k kde kdehiddenvisibility kipi laptop lcms libnotify logrotate
mad mikmod mmap mmx mng modules mp2 mp3 mp4 mpeg mplayer mudflap multilib
ncurses nls no-old-linux nptl nptlonly nsplugin offensive ogg openexr opengl
openmp pam pango pch pcre pda pdf phonon plasma pmu png policykit ppds pppd
qt3support qt4 readline rtc sdl seamonkey semantic-desktop session smp sound
spell srt sse sse2 ssl ssse3 startup-notification svg symlink sysfs tcpd theora
tiff timidity truetype udev unicode upnp usb vcd vorbis wicd wifi x264 xcb
xcomposite xine xml xorg xscreensaver xulrunner xv xvid xvmc zlib"
ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x
ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3
trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw
asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa
lfloat linear meter mmap_emul mulaw multi null plug rate route share shm
softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon
authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile
authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock
deflate dir disk_cache env expires ext_filter file_cache filter headers include
info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif
speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi
words flow plan stage tables krita karbon braindump" CAMERAS="ptp2"
COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog"
ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin
garmi

[Bug 293033] New: Reply-To overrides From when replying to sender/all

[kavol]

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

   Summary: Reply-To overrides From when replying to sender/all
   Product: kmail2
   Version: 4.8
  Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz


Version:   4.8 (using KDE 4.8.0) 
OS:Linux

If an incoming email has Reply-To set, like for example:

From: Sender Name 
To: list for announcements 
Reply-To: discussion_l...@example.com

trying to reply to the author (from) sets To address to the Reply-To address
instead of the author's address, i.e. "discussion_l...@example.com" instead of
"n...@example.com"

Also when trying to use the "reply to all" feature, the sender address is
omitted, i.e. the list of addresses does NOT contain "n...@example.com"

There is no way to send the answer to the sender and not to Reply-To address
except for deleting the prefilled address from the reply and entering the
sender's address manually.

Reproducible: Always

Steps to Reproduce:
see above, get an email with Reply-To set

1. hit "r" on it and examine the message being composed
2. hit "a" on it ...
3. hit "shift+A" on it ...

Actual Results:  
1. "To" is set to "Reply-To" address - this is correct
2. "To" is set to "Reply-To" and "To" addresses
3. "To" is set to "Reply-To" address

Expected Results:  
1. the same - "To" is set to reply-to address
2. "To" is set to "Reply-To" and "From" addresses
3. "To" is set to "From" address

While it may arguable if the case 2. should include also the original "To",
i.e. using really all concerned addresses and not just a subset (when
"Reply-To" serves as a replacement of "To"), the most important thing is that
cases 1. and 3. have to differ. The "reply to author" function is chosen
explicitly when the reply should go to the sender, overriding the implicit
mechanism of chosing the address in standard reply.

Note that this has worked as expected until kmail 4.7.4, it got broken in
4.8.0.

p.s. my case is using this with mailinglist where other headers that I haven't
mentioned like "List-Post" may have some influence - if an exact reproducer
message is needed, I'll try to refine some

-- 
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 283954] Only resources can modify remote revisions

[kavol]

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


kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz




--- Comment #7 from kavol   2012-01-31 17:55:04 ---
note that I've just hit this issue (same as comment #2, editing an event twice)
with korganizer 4.8.0

-- 
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 292523] kmail crashes on viewing html mail

[kavol]

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





--- Comment #1 from kavol   2012-01-26 21:43:01 ---
Created an attachment (id=68210)
 --> (http://bugs.kde.org/attachment.cgi?id=68210)
the message causing the crash

-- 
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 292523] New: kmail crashes on viewing html mail

[kavol]

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

   Summary: kmail crashes on viewing html mail
   Product: kmail2
   Version: unspecified
  Platform: Compiled Sources
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz


Application: kmail (4.7.4)
KDE Platform Version: 4.7.4 (4.7.4) (Compiled from sources)
Qt Version: 4.7.4
Operating System: Linux 3.1.6-gentoo x86_64
Distribution: "Gentoo Base System release 2.0.3"

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

simply selecting the email is enough, kmail crashes before displaying the
contents

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f1048dcd760 (LWP 29574))]

Thread 3 (Thread 0x7f102a487700 (LWP 29578)):
#0  pthread_cond_wait () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7f103b6060f4 in scavengerThread (this=0x7f103be27f20) at
wtf/FastMalloc.cpp:2378
#2  WTF::TCMalloc_PageHeap::runScavengerThread (context=0x7f103be27f20) at
wtf/FastMalloc.cpp:1497
#3  0x7f1043fc2c5c in start_thread (arg=0x7f102a487700) at
pthread_create.c:301
#4  0x7f104614afcd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 2 (Thread 0x7f1029b86700 (LWP 29579)):
#0  0x7fffc57ff8b6 in ?? ()
#1  0x7f103dbe3833 in *__GI_clock_gettime (clock_id=1, tp=0x7f1029b85b70)
at ../sysdeps/unix/clock_gettime.c:100
#2  0x7f10469e6d42 in do_gettime (frac=, sec=) at tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  0x7f1046aa9a5d in QTimerInfoList::updateCurrentTime (this=0x192d6b0) at
kernel/qeventdispatcher_unix.cpp:339
#5  0x7f1046aa9de5 in QTimerInfoList::timerWait (this=0x192d6b0, tm=...) at
kernel/qeventdispatcher_unix.cpp:442
#6  0x7f1046aa884c in timerSourcePrepareHelper (src=,
timeout=0x7f1029b85c9c) at kernel/qeventdispatcher_glib.cpp:136
#7  0x7f1046aa88f5 in timerSourcePrepare (source=,
timeout=) at kernel/qeventdispatcher_glib.cpp:169
#8  0x7f103eb545e6 in g_main_context_prepare (context=0x193bf20,
priority=0x7f1029b85d0c) at gmain.c:2762
#9  0x7f103eb55409 in g_main_context_iterate (context=0x193bf20, block=1,
dispatch=1, self=) at gmain.c:3069
#10 0x7f103eb55a41 in g_main_context_iteration (context=0x193bf20,
may_block=1) at gmain.c:3152
#11 0x7f1046aa9066 in QEventDispatcherGlib::processEvents (this=0x193be30,
flags=) at kernel/qeventdispatcher_glib.cpp:424
#12 0x7f1046a7d422 in QEventLoop::processEvents (this=,
flags=...) at kernel/qeventloop.cpp:149
#13 0x7f1046a7d664 in QEventLoop::exec (this=0x7f1029b85e20, flags=...) at
kernel/qeventloop.cpp:201
#14 0x7f1046993744 in QThread::exec (this=) at
thread/qthread.cpp:498
#15 0x7f1046995f95 in QThreadPrivate::start (arg=0x1913c10) at
thread/qthread_unix.cpp:331
#16 0x7f1043fc2c5c in start_thread (arg=0x7f1029b86700) at
pthread_create.c:301
#17 0x7f104614afcd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f1048dcd760 (LWP 29574)):
[KCrash Handler]
#6  get (this=) at ../JavaScriptCore/wtf/RefPtr.h:58
#7  world (this=) at bindings/js/JSDOMGlobalObject.h:68
#8  currentWorld (exec=0x7f1026929758) at bindings/js/DOMWrapperWorld.h:70
#9  domObjectWrapperMapFor (exec=0x7f1026929758) at
bindings/js/JSDOMBinding.h:332
#10 WebCore::getCachedDOMObjectWrapper (exec=0x7f1026929758,
objectHandle=0x7f10266e7870) at bindings/js/JSDOMBinding.cpp:144
#11 0x7f103ae93ebb in WebCore::toJS (exec=0x7f1026929758,
globalObject=0x7f1028680080, collection=0x7f10266e7870) at
bindings/js/JSHTMLCollectionCustom.cpp:137
#12 0x7f103aaf5a19 in WebCore::jsDocumentApplets (exec=0x7f1026929758,
slotBase=) at generated/JSDocument.cpp:488
#13 0x7f103aba63ce in getValue (propertyName=,
exec=, this=) at
../JavaScriptCore/runtime/PropertySlot.h:78
#14 getStaticValueDescriptor
(descriptor=..., propertyName=..., thisObj=0x7f10286829c0,
table=0x7f103be1bdb0, exec=0x20f8298) at ../JavaScriptCore/runtime/Lookup.h:280
#15 WebCore::JSHTMLDocument::getOwnPropertyDescriptor (this=0x7f10286829c0,
exec=0x20f8298, propertyName=..., descriptor=...) at
generated/JSHTMLDocument.cpp:187
#16 0x7f103b5a9160 in JSC::JSObject::propertyIsEnumerable (this=, exec=, propertyName=) at
runtime/JSObject.cpp:410
#17 0x7f103b314164 in JSC::Bindings::convertValueToQVariant
(exec=0x20f8298, value=..., hint=, distance=0x7fffc56c35e4,
visitedObjects=0x7fffc56c69f0, recursionLimit=192) at
bridge/qt/qt_runtime.cpp:347
#18 0x7f103b31419c in JSC::Bindings::convertValueToQVariant
(exec=0x20f8298, value=..., hint=, distance=0x7fffc56c3e64,
visitedObjects=0x7fffc56c69f0, recursionLimit=193) at
bridge/qt/qt_runtime.cpp:349
#19 0x7f103b31419c in JSC::Bindings::convertValueTo

[Bug 67516] KMail does not seem to suppost the RFC 2046 standard for content type: message/partial. (at least partial messages I receive are not reassembled)

[kavol]

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





--- Comment #4 from kavol   2011-12-08 16:41:21 ---
(In reply to comment #3)
> What's the status of this?
> 
> Reassigning to kmail2, please Bruce, Barry and kavol update this bug report
> against KMail2. Thanks in advance!

now I'm on KDE 4.7.3

I've got one series of such messages in my inbox, and I still see it as six
separate messages and kmail is still unable to combine them to allow me to see
the original message which was split

-- 
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 287476] akonadi_maildir_resource trashes maildir with senseless directories

[kavol]

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


kavol  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|INVALID |




--- Comment #4 from kavol   2011-11-29 11:18:08 ---
(In reply to comment #3)
> you can't. It's by default.

defaults can be changed

what is the reasoning to create cruft on users systems and to force users to
look at that cruft, and not just to look at it but also let the cruft obstruct
the work with useful data?

why to create those directories on startup and not only when they are really
needed (possibly warning/asking user about them missing and the creation)?


my usecase is that I use IMAP, I have my inbox/outbox/sent folders on the IMAP
server, I do not use the local ones by default

yet still I want local maildir to serve as an archive, so I add it to kmail
(akonadi) too - but I want to manage the contents of the archive myself, I
really do not want any software to bother me by creating subdirectories that I
do not want to use (or see at all)

btw, what if I switch locale, I'd have another set of directories created? - so
I'll possibly (if I'd use the default folders) get data scattered in different
places just because of different locale, making them inaccessible with another
locale setting?

-- 
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 287476] akonadi_maildir_resource trashes maildir with senseless directories

[kavol]

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


kavol  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|INVALID |




--- Comment #2 from kavol   2011-11-28 14:08:08 ---
(In reply to comment #1)
> it's translated by default. So you can't have no translated special local
> folder.

you don't get the point

I do not care which language it is in

I do not want these directories to be created at all

-- 
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 287477] New: kmail does not put messages to folders configured within identity properties

[kavol]

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

   Summary: kmail does not put messages to folders configured
within identity properties
   Product: kmail2
   Version: unspecified
  Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz


Version:   unspecified (using KDE 4.7.3) 
OS:Linux

When I send an email, it is put into a folder named "Odeslaná pošta" instead of
"sent-mail" as configured.

Reproducible: Always

Steps to Reproduce:
switch to Czech locale (I use this, but I bet it works also with other locales)

configure local maildir resource in akonadi settings

start kmail

(if the following folders do not exist, create them)

configure your identity to use
"Lokální složky/sent-mail"
"Lokální složky/drafts"
"Lokální složky/templates"
for the respective purposes

try to send an email

Actual Results:  
the copy of the sent email is placed into "Lokální složky/Odeslaná pošta"

Expected Results:  
the copy of the sent email is placed into "Lokální složky/sent-mail"

note that the folder "Odeslaná pošta" cannot be removed

see also Bug 287476

$ rpm -qf /usr/bin/kmail
kdepim-4.7.3-1.fc16.x86_64

-- 
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 287476] New: akonadi_maildir_resource trashes maildir with senseless directories

[kavol]

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

   Summary: akonadi_maildir_resource trashes maildir with
senseless directories
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Maildir Resource
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz


Version:   unspecified (using KDE 4.7.3) 
OS:Linux

After configuring maildir resource, the mail directory gets trashed with
subdirectories like "Koncepty", "Koš", "Odeslaná pošta", "Odchozí", "Příchozí",
"Šablony".

I don't want these.

Stopping akonadi, removing the directories manually, and restarting akonadi
leads to the same - these directories are recreated immediately on akonadi
start.

Reproducible: Always

Steps to Reproduce:
switch to Czech locale (I bet it works with any locale, I just use Czech thus
the names listed in this reproducer are in Czech)

add "Maildir" resource (it appears like "Lokální složky" in the list)

configure it to use some existing maildir, e.g. ~/.kde/share/apps/kmail/mail

ls -1 ~/.kde/share/apps/kmail/mail

Actual Results:  
archiv
drafts
inbox
Koncepty
Koš
mine
misc
Odeslaná pošta
Odchozí
outbox
projects
Příchozí
sent-mail
Šablony
templates
trash


Expected Results:  
archiv
drafts
inbox
mine
misc
outbox
projects
sent-mail
templates
trash


$ rpm -qf /usr/lib64/kde4/akonadi_maildir_resource.so
kdepim-runtime-4.7.3-1.fc16.x86_64

-- 
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 270736] Kmail crash while viewing mail

[kavol]

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





--- Comment #1 from kavol   2011-11-14 16:04:13 ---
Created an attachment (id=65662)
 --> (http://bugs.kde.org/attachment.cgi?id=65662)
New crash information added by DrKonqi

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

- What I was doing when the application crashed:

I used the quicksearch then clicked on a chosen message, but the message text
haven't appeared. Then I rightclicked the message and chosen to edit it. A
dialogue appeared saying something like "transferring the message", hanging for
ages. I've cancelled it and closed kmail, then I got DrKonqi report.

-- Backtrace (Reduced):
#6  0x7f452ecb73b4 in KProgressDialog::wasCancelled (this=0x4599be0) at
/usr/src/debug/kdelibs-4.7.3/kdeui/dialogs/kprogressdialog.cpp:126
#7  0x7f452e0d1bd3 in KMCommand::slotJobFinished (this=0x30ac1e0) at
/usr/src/debug/kdepim-4.7.3/kmail/kmcommands.cpp:354
[...]
#9  0x7f452e745cf2 in KJob::result (this=, _t1=0x45b7a40) at
/usr/src/debug/kdelibs-4.7.3/x86_64-redhat-linux-gnu/kdecore/kjob.moc:208
#10 0x7f452e745d30 in KJob::emitResult (this=0x45b7a40) at
/usr/src/debug/kdelibs-4.7.3/kdecore/jobs/kjob.cpp:312
#11 0x7f452c43de00 in Akonadi::JobPrivate::handleResponse (this=, tag=..., data=...) at /usr/src/debug/kdepimlibs-4.7.3/akonadi/job.cpp:66

-- 
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 270736] Kmail crash while viewing mail

[kavol]

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


kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz




-- 
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 158455] Crash after renaming folder with subfolder

[kavol]

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





--- Comment #6 from kavol   2010-11-30 13:47:43 ---
(In reply to comment #5)
> However, I also tried it against the trunk version (r1201549), and it seems to
> have been fixed there.

um, ping me when it gets released in Fedora or Gentoo, I'll find you a new way
to break it then :-)

well ... I remember hearing about some OpenSUSE KDE preview images for qemu,
but I can't find anything useful - new enough right now, could you point me to
some binaries I can test? - I don't feel like pulling out of svn and compiling
trunk myself ...

-- 
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 158455] Crash after renaming folder with subfolder

[kavol]

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


kavol  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |




--- Comment #4 from kavol   2010-11-28 10:52:52 ---
I cannot confirm this fixed completely in KMail 1.13.5 (using KDE 4.4.5)

To test this, I tried a few steps that don't invoke DrKonqi, but still lead to
KMail quitting unexpectedly:

1. Within local folders, create a folder "příliš"
2. Create new subfolder "žluťoučký"
3. Rename "příliš" to "kůň"
4. Try to move a message to "žluťoučký"

you get:

KMail encountered a fatal error and will terminate now.
The error was:
Message could not be added to the folder, possibly disk space is low.

-- 
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 254991] New: can't undo file association

[kavol]

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

   Summary: can't undo file association
   Product: kmail
   Version: 1.13.5
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz


Version:   1.13.5 (using KDE 4.5.2) 
OS:Linux

while opening an attachment, I've accidentaly clicked the checkbox "always use
this action" (or something like that)

I wanted to undo this, to be asked to choose the action, whether to open or
save, next time, but I haven't found a way to do this

at first, I've tried to search kmail settings without success

then I tried the systemsettings module for file associations, but I just
couldn't find any corresponding association to remove

then, as the action is now opening the attachment in kwrite, I've tried to
search files in ~/.kde for "kwrite" but I haven't found any relevant occurence

then I tried go through the 200 KBs of kmailrc, but I haven't found any
suspicious option there either ...

Reproducible: Didn't try




OS: Linux (x86_64) release 2.6.35.6-45.fc14.x86_64
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 226282] kontact crash after strtup problem

[kavol]

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





--- Comment #14 from kavol   2010-09-14 10:16:37 ---
Created an attachment (id=51630)
 --> (http://bugs.kde.org/attachment.cgi?id=51630)
New crash information added by DrKonqi

kmail asked me for opening kdewallet, but before entering the password, due to
some unresponsiveness I've issued killall kmail, which led to the crash

-- 
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 226282] kontact crash after strtup problem

[kavol]

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


kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz




-- 
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 185820] kMail does not terminate after quitting it

[kavol]

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





--- Comment #7 from kavol   2010-08-17 13:15:50 ---
(In reply to comment #6)
> I'm not able to reproduce using KDE 4.4.5.
> 
> Please reopen if someone is able to reproduce in KDE 4.4.5 or more recent.

not sure if this is completely fixed ... even after 'kmail' process
disappearing, I still have running processes like these:

kavol 9630  9449  0 11:02 ?00:00:00 kdeinit4: kio_imap4 [kdeinit]
imap local:/tmp/ksocket-kavol/klauncherMT9450.slave-socket
local:/tmp/ksocket-kavol/kmailTm9444.slave-socket
kavol 9881  9449  0 13:02 ?00:00:00 kdeinit4: kio_pop3 [kdeinit]
pop3s local:/tmp/ksocket-kavol/klauncherMT9450.slave-socket
local:/tmp/ksocket-kavol/kmaillQ9444.slave-socket
kavol 9894  9449  0 13:03 ?00:00:00 kdeinit4: kio_file [kdeinit]
file local:/tmp/ksocket-kavol/klauncherMT9450.slave-socket
local:/tmp/ksocket-kavol/kmailwA9444.slave-socket

- not to mention tons of akonadi/dbus/nepomuk ballast ...

however, I don't have the rights to reopen this

-- 
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 243252] autosaved messages deleted before saved again, getting lost forever

[kavol]

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


kavol  changed:

   What|Removed |Added

Summary|messages being composed not |autosaved messages deleted
   |autosaved   |before saved again, getting
   ||lost forever




--- Comment #3 from kavol   2010-07-14 13:05:45 ---
Denis, Nancy - if you can find the message within the autosave directory then
please take a look at the bug #230466, I think that one is your case

meanwhile, after some experimenting ... the initial bug description is not
correct, and also the subject - what really happens to me and how to reproduce:

1. start kmail
2. set some autosave time like e.g. 5 minutes
3. create a new message, write some text into it
4. wait until the message gets saved, check the
~/.kde4/share/apps/kmail/autosave/cur directory
5. kill kmail
6. check ~/.kde4/share/apps/kmail/autosave/cur directory - the autosaved
message is still there
6. start kmail
7. the new message may or may not appear in the editor, depending whether you
hit bug #230466

if the message does not appear in the editor:
8. the chance is that you can find the autosaved message in the
~/.kde4/share/apps/kmail/autosave/cur directory

if the message appears in the editor:
8. the autosaved message disappears from the
~/.kde4/share/apps/kmail/autosave/cur directory
9. kill kmail before the autosave timeout is reached
10. boom, you've just lost all your work, the message is not stored anywhere

eventually, you can hit bug #230466 in the way that the message is not opened
in the editor AND the message gets deleted anyways

what needs to be changed - the message should not be deleted from the autosave
directory before a new copy is saved, otherwise the crash/network
disconnect/power failure/whatever can hit the time frame when there is no copy
of the message stored on a harddisk

I'd also suggest autosaving immediately after the new message creation and not
waiting for the timeout at first - imagine a case of a reply quoting the
previous email on an imap server which may get deleted meanwhile and if you
cannot restore the reply, you've lost the quoted text forever

below there is a part of kmail console log regarding autosaves - what is
interesting, there is no mention of the message '1279102908.4061.ZHE4K' (my
testing message) being deleted but kmail tries to delete
'1279103354.7912.S3zV1' which did not exist anytime during my experiments
(rather than listing the ~/.kde4/share/apps/kmail/autosave/cur directory, I've
used 'find' to list everything under ~/.kde4/share/apps/kmail/autosave)

(oh, and why the autosave index gets created twice?)


kmail(7912) KMFolderMaildir::createIndexFromContents: Creating index for
"/home/kavol/.kde4/share/apps/kmail/autosave"
kmail(7912) KMFolderMaildir::createIndexFromContents: Creating index for
"/home/kavol/.kde4/share/apps/kmail/autosave"
kmail(7912) KMFolderMaildir::getDwString: KDE_fopen(abs_file=
"/home/kavol/.kde4/share/apps/kmail/autosave/cur/1279102908.4061.ZHE4K" , "r")
== stream ==  0x2fd31e0
kmail(7912) KMFolderMaildir::getDwString: fclose(mIndexStream =  0x2fd31e0 )
kmail(7912): No language dictionaries for the language :  "cs" 

kmail(7912) Sonnet::DictionaryComboBox::reloadCombo: Populate combo: "Český" :
"cs"
kmail(7912) Sonnet::DictionaryComboBox::reloadCombo: Populate combo: "Český
(Česká republika)" : "cs_CZ"
kmail(7912) KMComposeWin::slotUpdateFont:
kmail(7912) KMComposeWin::readConfig: "ka...@hajnet.cz"
kmail(7912) KMComposeWin::slotUpdateFont:
kmail(7912) KMComposeWin::rethinkFields:
kmail(7912) KMComposeWin::initAutoSave:
kmail(7912) loadPlugins: BodyPartFormatterFactory: found 4  plugins.
kmail(7912) insertBodyPartFormatter: BodyPartFormatterFactory: overwriting
previously registered formatter for " application / octet-stream "
kmail(7912) insertBodyPartFormatter: BodyPartFormatterFactory: instantiating
new Subtype Registry for " text "
kmail(7912) ::UrlHandler::UrlHandler: UrlHandler() (iCalendar)
kmail(7912) KMFolderMaildir::removeFile: Can't delete
"/home/kavol/.kde4/share/apps/kmail/autosave/new/1279103354.7912.S3zV1"
"Adresář nebo soubor neexistuje"
kmail(7912) KMailApplication::newInstance:
kmail(7912) KMKernel::openReader:
QObject::connect: Cannot queue arguments of type 'KParts::WindowArgs'
(Make sure 'KParts::WindowArgs' is registered using qRegisterMetaType().)
kmail(7912)/kdepimlibs (kpgp) Kpgp::Module::checkForPGP: Kpgp: gpg found
kmail(7912) KMFolderMaildir::reallyDoClose: fclose(mIndexStream =  0x35b09d0 )

-- 
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 243252] New: messages being composed not autosaved

[kavol]

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

   Summary: messages being composed not autosaved
   Product: kmail
   Version: unspecified
  Platform: Gentoo Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz


Version:   unspecified (using KDE 4.4.4) 
OS:Linux

If I start writing an email, and kmail gets terminated for some reason, on
subsequent kmail start the unfinished message is not restored in a composer
window. This has worked up to KDE 4.3

Note: this is NOT a duplicate of bug #230466 - I can't find the unfinished
messages in ~/.kde4/share/apps/kmail/autosave/ and subdirs, unlike comments #3
to #5 to bug #230466 say.

Reproducible: Always

-- 
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 241889] New: kmail crashed when hitting reply while still scrolling message

[kavol]

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

   Summary: kmail crashed when hitting reply while still scrolling
message
   Product: kmail
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz


Application that crashed: kmail
Version of the application: 1.12.4
KDE Version: 4.3.5 (KDE 4.3.5)
Qt Version: 4.6.2
Operating System: Linux 2.6.33-gentoo-r2 x86_64

What I was doing when the application crashed:
SSIA

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#5  0x01abfee0 in ?? ()
#6  0x7f5df5d096fe in KMCommand::slotStart (this=0x2394790) at
/var/tmp/portage/kde-base/kmail-4.3.5/work/kmail-4.3.5/kmail/kmcommands.cpp:247
#7  0x7f5df5cfa92a in KMCommand::qt_metacall (this=0x2394790,
_c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff40aa34b0)
at
/var/tmp/portage/kde-base/kmail-4.3.5/work/kmail-4.3.5_build/kmail/kmcommands.moc:92
#8  0x7f5df211d167 in QMetaObject::activate (sender=0x1d5cb60, m=, local_signal_index=, argv=0x2eee6d0) at
kernel/qobject.cpp:3285
#9  0x7f5df212435f in QSingleShotTimer::timerEvent (this=0x1d5cb60) at
kernel/qtimer.cpp:308
#10 0x7f5df2119c03 in QObject::event (this=0x1d5cb60, e=0x0) at
kernel/qobject.cpp:1204
#11 0x7f5df0d4cd2d in QApplicationPrivate::notify_helper (this=0x10371e0,
receiver=0x1d5cb60, e=0x7fff40aa3cc0) at kernel/qapplication.cpp:4300
#12 0x7f5df0d54124 in QApplication::notify (this=0x7fff40aa4120,
receiver=0x1d5cb60, e=0x7fff40aa3cc0) at kernel/qapplication.cpp:3704
#13 0x7f5df69f0d66 in KApplication::notify (this=0x7fff40aa4120,
receiver=0x1d5cb60, event=0x7fff40aa3cc0)
at
/var/tmp/portage/kde-base/kdelibs-4.3.5/work/kdelibs-4.3.5/kdeui/kernel/kapplication.cpp:302
#14 0x7f5df2109dab in QCoreApplication::notifyInternal
(this=0x7fff40aa4120, receiver=0x1d5cb60, event=0x7fff40aa3cc0) at
kernel/qcoreapplication.cpp:704
#15 0x7f5df2136e94 in QCoreApplication::sendEvent (this=0x103aa60) at
kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x103aa60) at
kernel/qeventdispatcher_unix.cpp:603
#17 0x7f5df2133844 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:184
#18 0x7f5dea2b6d99 in g_main_dispatch (context=0x1039920) at gmain.c:1960
#19 IA__g_main_context_dispatch (context=0x1039920) at gmain.c:2513
#20 0x7f5dea2ba5e8 in g_main_context_iterate (context=0x1039920, block=1,
dispatch=1, self=) at gmain.c:2591
#21 0x7f5dea2ba79c in IA__g_main_context_iteration (context=0x1039920,
may_block=1) at gmain.c:2654
#22 0x7f5df213354c in QEventDispatcherGlib::processEvents (this=0xa8feb0,
flags=) at kernel/qeventdispatcher_glib.cpp:412
#23 0x7f5df0dfcfaf in QGuiEventDispatcherGlib::processEvents
(this=0x1fdc560, flags=) at
kernel/qguieventdispatcher_glib.cpp:204
#24 0x7f5df21086d2 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149
#25 0x7f5df2108aa4 in QEventLoop::exec (this=0x7fff40aa3f70, flags=...) at
kernel/qeventloop.cpp:201
#26 0x7f5df210aef6 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:981
#27 0x004034db in main (argc=, argv=) at
/var/tmp/portage/kde-base/kmail-4.3.5/work/kmail-4.3.5/kmail/main.cpp:146

This bug may be a duplicate of or related to bug 233574

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 229534] Kontact hangs with error libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name"

[kavol]

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





--- Comment #7 from kavol   2010-04-28 07:52:20 ---
it just happened to me again, I had to kill kmail 'cause it did not react, on
subsequent try from konsole it started to repeat te message:

kmail(7231)/libakonadi Akonadi::SessionPrivate::socketError: Socket error
occurred: "QLocalSocket::connectToServer: Invalid name"

but akonadi processes were running

[ka...@kavol ~]$ ps -ef | grep akon
kavol 2847 1  0 Apr26 ?00:00:04 /usr/bin/akonadi_control
kavol 2849  2847  0 Apr26 ?00:00:07 akonadiserver
kavol 2889  2847  0 Apr26 ?00:00:00
/usr/bin/akonadi_contacts_resource --identifier akonadi_contacts_resource_0
kavol 2890  2847  0 Apr26 ?00:00:01 /usr/bin/akonadi_ical_resource
--identifier akonadi_ical_resource_0
kavol 2891  2847  0 Apr26 ?00:00:01 /usr/bin/akonadi_ical_resource
--identifier akonadi_ical_resource_1
kavol 2892  2847  0 Apr26 ?00:00:00
/usr/bin/akonadi_maildir_resource --identifier akonadi_maildir_resource_0
kavol 2893  2847  0 Apr26 ?00:00:01
/usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agent
kavol 2894  2847  0 Apr26 ?00:00:02
/usr/bin/akonadi_nepomuk_contact_feeder --identifier
akonadi_nepomuk_contact_feeder
kavol 2895  2847  0 Apr26 ?00:00:01 /usr/bin/akonadi_vcard_resource
--identifier akonadi_vcard_resource_0
kavol 2896  2847  0 Apr26 ?00:00:01 /usr/bin/akonadi_vcard_resource
--identifier akonadi_vcard_resource_1
kavol 2897  2847  0 Apr26 ?00:00:01 /usr/bin/akonadi_vcard_resource
--identifier akonadi_vcard_resource_2
kavol 7258  7240  0 07:41 pts/200:00:00 grep akon

killing them and then relaunching kmail helped the case

BUT THERE IS ONE BIG DIFFERENCE - it all happened locally, no ssh or NX
connections to the machine ... I'm tempted to report this as a new bug ...

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 209936] can't choose desktop note is to be on

[kavol]

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


kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz




--- Comment #2 from kavol   2010-04-19 13:22:02 ---
I've just hit this issue with kdepim-4.4.2

(the workaround is to quit knotes and edit
~/.kde/share/apps/knotes/notes/libkcal-*)

-- 
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 234080] kaddressbook does not store contacts to vcf

[kavol]

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





--- Comment #4 from kavol   2010-04-13 16:44:36 ---
(In reply to comment #3)
> There is nothing to explain, this is a bug tracker not a user forum!

then why do you keep prolonging the offtopic discussion?

> > sometimes, people just need kicking in the ass ...
> Well, then you are at the wrong place, we like neither ass kicking nor 
> impolite
> people...
> Do not expect any help in this case

now, that is funny :-)

you (the KDE developer community as a whole) started to misbehave, treat users
bad, causing harm to millions of people(*), acting like gods, laughing into
users faces, accusing the distributors and hardware/drivers vendors of your own
faults etc.

now when an user strikes back (not much to do, I can't break your machine just
like you've broken mine, so just verbally), you play the most aggrieved person
in the world

that's what I call hypocrisy :-)

(*) for example I've just read recently that Fedora is estimated to 24M
installations, and KDE is not just 1% minority ...

> > > Which kind of resource? 'Traditional Addressbook' or 'vCard file' 
> > > resource?
> > 
> > I don't remember ... the one that allowed me to use single .vcf
> Then you should maybe remove the resource you've added and add a 'vCard file'
> resource... from you previous description it sounds like you've added the
> former which is known to be buggy.

ok, I've tried

so, adding a vCard file resource seems to work => keeping the bug closed if
this is the only supported way to use .vcf

... but creating bug #234259 to get rid of the unsupported way

> > > The former shouldn't be used anymore.
> > 
> > why is it present then?
> For most users/distribution/kde version combination this resource works 
> without
> problems.

this sounds like "when there is full moon and the night is not cloudy and you
stand on your left leg ..."

note that I've tried bug #234259 on Fedora 13 with KDE 4.4.2

...
> Well, if I (the developer) can't reproduce it, I have no way to fix it...

simply not true

...
> Commits to KAddressBook are irrelevant here, the behavior is caused by the
> resource, which is a completely different code base.

if that was clear then the bug should have been reassigned in the first place;
users are not expected to understand code hierarchy ...

> > > No reason to cry, Akonadi contains a cache, so you see the cached data.
> > 
> > no, I just see shit!
> So it is brown and smells bad?

well, I know that KDE developers expect everyone to have the latest&greatest
hardware, but I still don't own a scent delivery system, so I can't tell, sorry

> > the purpose of cache is to speed up access, not to keep completely different
> > set of data
> It doesn't keep completely different set of data, the data of the cache just
> have not be written back to the original source (aka vCard file).

... which in other words means that the original source has completely
different set of data; wasn't that an oxymoron?


anyways, thankyou for leading me to a workaround for this bug

I won't reopen it again, as stated above, I won't force fixing a bug in a
component which is no longer supported - even if proper action would be to
reopen and then let the owner to close this as WONTFIX (you choose wrong
resolution intentionally to have nicer statistics? - seems like a trend these
days, nobody dares to use WONTFIX, I'm getting INVALID/NOTABUG on obvious
problems a lot recently ...)

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug.
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 234259] New: remove 'Traditional Addressbook' resource option

[kavol]

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

   Summary: remove 'Traditional Addressbook' resource option
   Product: kaddressbook
   Version: unspecified
  Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz
CC: to...@kde.org


Version:(using KDE 4.4.2)
OS:Linux
Installed from:Fedora RPMs

Run kaddressbook, add addressbook

There is an option "KDE Address Book (traditional)". This should NOT be present
- I refer to bug #234080 comment #1:

"'Traditional Addressbook' or 'vCard file' resource? The former shouldn't be
used anymore."

If you choose this, here's how to reproduce a problem:

A wizard is run ...
Step 1 - select file
Step 2 - select vCard, enter path (~/.kde/share/apps/kabc/std.vcf)
Step 3 - do not check read only

Add a contact into that addressbook. Quit kaddressbook. The std.vcf file is
left untouched, the newly added contact does not get saved to it.

-- 
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 234080] kaddressbook does not store contacts to vcf

[kavol]

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


kavol  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|WORKSFORME  |




--- Comment #2 from kavol   2010-04-11 20:53:02 ---
(In reply to comment #1)
> (In reply to comment #0)
> > KDE4 simply sucks. (Yes, I know it is bad to say such things in a
> > bugreport,
> So why do you do it then anyway?

I've explained that

too sad you fail to listen

> > but being nice does not help.
> Hmm? Doesn't have your mommy told you that being nice is a basic part of 
> social
> communication?

yes, she told me

unfortunately, I'm too old by now and I have found out already that life is not
a fairytale

sometimes, people just need kicking in the ass ... and sometimes even that does
not help, like we can see here (but at least it got attention, which is more
than we can say about some other bugs rotting here for ages ...)

> > I've removed all the automagically created addressbooks and started from
> > scratch. I've added only one addressbook resource which refers to the old
> > std.vcf file.
> Which kind of resource? 'Traditional Addressbook' or 'vCard file' resource?

I don't remember ... the one that allowed me to use single .vcf

> The former shouldn't be used anymore.

why is it present then?

> > However, when I add a contact, it does not get added to the file, even if it
> > shows within the list!
> Can't reproduce this here with vanilla KDE SVN trunk, both resources work 
> fine.

sticking your head in the sand and saying "if a bug does not show on my system
it does not exist" does not help the case

svn says there hasn't been any possibly relevant commit to kaddressbook in the
last FOUR months while 4.4.1 is out for one and a half month => reopening

... you say it's not directly in kaddressbook? - feel free to reassign

> > But after running kaddressbook again,
> > the newly added contact is there - WHERE THE HECK DOES IT COME FROM???
> No reason to cry, Akonadi contains a cache, so you see the cached data.

no, I just see shit!

the purpose of cache is to speed up access, not to keep completely different
set of data

and this doesn't explain the other question ...

-- 
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 233078] KAddressbook in KDE 4.4 is not feature-complete

[kavol]

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


kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz




--- Comment #6 from kavol   2010-04-11 19:36:48 ---
(In reply to comment #4)
> Complete list of bugs filed for the currently known direct regressions:

add
Bug 234080 -  kaddressbook does not store contacts to vcf

-- 
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 234080] New: kaddressbook does not store contacts to vcf

[kavol]

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

   Summary: kaddressbook does not store contacts to vcf
   Product: kaddressbook
   Version: unspecified
  Platform: Fedora RPMs
OS/Version: unspecified
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz
CC: to...@kde.org


Version:(using KDE 4.4.1)
Installed from:Fedora RPMs

For the purpose of easy synchronisation with my phone and other places, I need
to keep my contacts in .vcf file. This has worked for years, and now it is
broken. KDE4 simply sucks. (Yes, I know it is bad to say such things in a
bugreport, but being nice does not help. Hope you finally realise how bad the
situation is when you force users to do things they know to be bad. I refer
also to bug #233078)

I've removed all the automagically created addressbooks and started from
scratch. I've added only one addressbook resource which refers to the old
std.vcf file.

In the addressbook properties, Read only is NOT checked, the format is vCard
and the location is ~/.kde/share/apps/kabc/std.vcf

The contacts are displayed okay.

However, when I add a contact, it does not get added to the file, even if it
shows within the list!

When I log out, the modification time of the std.vcf file gets updated, but the
contents of the file is left untouched. But after running kaddressbook again,
the newly added contact is there - WHERE THE HECK DOES IT COME FROM??? AND WHY
THE HECK THE MTIME GETS UPDATED WHEN NOTHING IS CHANGED???

-- 
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 229534] Kontact hangs with error libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name"

[kavol]

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





--- Comment #6 from kavol   2010-04-05 09:51:43 ---
I can confirm the same with kmail over ssh

today it happened to me again, but the other way round than described in bug
#232191 (i.e. kmail hanged on the local machine, not with the remote
connection) and killing it did not led to that nice backtrace which is included
in bug #232191

-- 
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 229534] Kontact hangs with error libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name"

[kavol]

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


kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz




--- Comment #5 from kavol   2010-04-05 09:47:25 ---
*** Bug 232191 has been marked as a duplicate of this bug. ***

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 232191] kmail hanged on opening a message from IMAP server

[kavol]

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





--- Comment #4 from kavol   2010-04-05 09:47:25 ---
well, yes, finally I've found this is duplicate, but of another bug ...

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

-- 
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 232864] New: no way to send Disposition-Notification once ignored

[kavol]

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

   Summary: no way to send Disposition-Notification once ignored
   Product: kmail
   Version: unspecified
  Platform: Fedora RPMs
OS/Version: unspecified
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz


Version:(using KDE 4.4.1)
Installed from:Fedora RPMs

When an email with Disposition-Notification-To header is opened for the first
time, the user is asked whether to send ack, nack or ignore.

There is no way to postpone the decision - once user selects ignoring the
Disposition-Notification, no chance to send ack later.

I've tried to mark the email as new/unread, but it did not help, I never got
the question again. And I haven't found any menu item to send the notification
explicitly.

-- 
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 232191] kmail hanged on opening a message from IMAP server

[kavol]

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





--- Comment #1 from kavol   2010-03-26 10:28:53 ---
it is reproducible, and I guess these are the relevant console messages:

kmail(4556)/libakonadi Akonadi::SessionPrivate::socketError: Socket error
occurred: "QLocalSocket::connectToServer: Invalid name" 
kmail(4556)/libakonadi Akonadi::SessionPrivate::socketError: Socket error
occurred: "QLocalSocket::connectToServer: Invalid name" 
kmail(4556)/libakonadi Akonadi::SessionPrivate::socketError: Socket error
occurred: "QLocalSocket::connectToServer: Invalid name" 
[akonadiserver] Error during selection of all records from table
"CollectionTable" "MySQL server has gone away QMYSQL: Unable to execute query"
kmail(4556)/libakonadi Akonadi::SessionPrivate::socketError: Socket error
occurred: "QLocalSocket::connectToServer: Invalid name"

-- 
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 232191] New: kmail hanged on opening a message from IMAP server

[kavol]

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

   Summary: kmail hanged on opening a message from IMAP server
   Product: kmail
   Version: 1.13.1
  Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz


Application: kmail (1.13.1)
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
Operating System: Linux 2.6.32.9-70.fc12.i686.PAE i686
Distribution (Platform): Fedora RPMs

-- Information about the crash:
I've started kmail as usual, and it hanged ... well, except for one special
precondition, I usually don't reuse ssh connections, see below:

I logged onto the machine via ssh, run kmail
closed kmail, logged via kdm, run kmail
logged out
reused the original ssh connection, run kmail
kmail then opened its main window, without asking for kwallet password or
whatever
an IMAP inbox was selected
kmail displayed the contents of the inbox, last but one email was selected
but the contents of the selected message was not displayed
kmail didn't react to any action - but still, it was able to redraw its window,
so not a complete hang
I tried to close kmail clicking the close icon in window titlebar
it didn't react ... so kwin stepped in and asked me to kill
I agreed to kill and this trace is the result

 -- Backtrace:
Application: KMail (kmail), signal: Aborted
[KCrash Handler]
#6  0x0052d416 in __kernel_vsyscall ()
#7  0x054cda91 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#8  0x054cf35a in abort () at abort.c:92
#9  0x054c6be8 in __assert_fail (assertion=, file=, line=, function=) at
assert.c:81
#10 0x021e6c0a in _XAllocID (dpy=0x842dad0) at xcb_io.c:378
#11 0x009cac48 in XRenderCreatePicture (dpy=,
drawable=, format=, valuemask=, attributes=)
at Picture.c:90
#12 0x019968ab in QX11PixmapData::fromImage (this=0x8521e50, img=...,
flags=...) at image/qpixmap_x11.cpp:526
#13 0x019829c8 in QPixmap::fromImage (image=..., flags=...) at
image/qpixmap.cpp:1999
#14 0x019e5bbe in QPaintEngine::drawImage (this=0x8f60dd0, r=..., image=...,
sr=..., flags=...) at painting/qpaintengine.cpp:623
#15 0x01aa1b61 in QX11PaintEngine::drawImage (this=0x8f60dd0, r=..., image=...,
sr=..., flags=...) at painting/qpaintengine_x11.cpp:1893
#16 0x019fb9dc in QPainterPrivate::draw_helper (this=0x85e6d50,
originalPath=..., op=StrokeDraw) at painting/qpainter.cpp:484
#17 0x019fcc49 in QPainter::drawLines (this=0xbff13fbc, lines=0xbff126c8,
lineCount=1) at painting/qpainter.cpp:4634
#18 0x03d6507b in drawLine (this=0x8463328, p=0xbff13fbc, r=..., pal=...,
orientation=Horizontal, hover=false, opacity=-1) at
/usr/include/QtGui/qpainter.h:534
#19 drawLine (this=0x8463328, p=0xbff13fbc, r=..., pal=...,
orientation=Horizontal, hover=false, opacity=-1) at
/usr/include/QtGui/qpainter.h:556
#20 OxygenStyle::renderScrollBarHandle (this=0x8463328, p=0xbff13fbc, r=...,
pal=..., orientation=Horizontal, hover=false, opacity=-1)
at /usr/src/debug/kdebase-runtime-4.4.1/kstyles/oxygen/oxygen.cpp:4362
#21 0x03d65c42 in renderScrollBarHandle (this=0x8463328, primitive=9,
opt=0xbff13544, r=..., pal=..., flags=..., p=0xbff13fbc, widget=0x8c724e8,
kOpt=0x0)
at /usr/src/debug/kdebase-runtime-4.4.1/kstyles/oxygen/oxygen.h:293
#22 OxygenStyle::drawScrollBarPrimitive (this=0x8463328, primitive=9,
opt=0xbff13544, r=..., pal=..., flags=..., p=0xbff13fbc, widget=0x8c724e8,
kOpt=0x0)
at /usr/src/debug/kdebase-runtime-4.4.1/kstyles/oxygen/oxygen.cpp:1582
#23 0x03d53a62 in OxygenStyle::drawKStylePrimitive (this=0x8463328,
widgetType=WT_ScrollBar, primitive=9, opt=0xbff13544, r=..., palette=...,
flags=..., p=0xbff13fbc, widget=0x8c724e8, kOpt=0x0)
at /usr/src/debug/kdebase-runtime-4.4.1/kstyles/oxygen/oxygen.cpp:753
#24 0x00cacc26 in KStyle::drawControl (this=0x8463328,
element=CE_ScrollBarSlider, option=0xbff13544, p=0xbff13fbc, widget=0x8c724e8)
at /usr/src/debug/kdelibs-4.4.1/kdeui/kernel/kstyle.cpp:2266
#25 0x03d56b36 in OxygenStyle::drawControl (this=0x8463328,
element=CE_ScrollBarSlider, option=0xbff13544, p=0xbff13fbc, widget=0x8c724e8)
at /usr/src/debug/kdebase-runtime-4.4.1/kstyles/oxygen/oxygen.cpp:632
#26 0x01bc864d in QCommonStyle::drawComplexControl (this=0x8463328,
cc=CC_ScrollBar, opt=0xbff13f54, p=0xbff13fbc, widget=0x8c724e8) at
styles/qcommonstyle.cpp:3236
#27 0x00ca8c9d in KStyle::drawComplexControl (this=0x8463328, cc=CC_ScrollBar,
opt=0xbff13f54, p=0xbff13fbc, w=0x8c724e8) at
/usr/src/debug/kdelibs-4.4.1/kdeui/kernel/kstyle.cpp:3591
#28 0x03d54489 in OxygenStyle::drawComplexControl (this=0x8463328,
control=CC_ScrollBar, option=0xbff13f54, painter=0xbff13fbc, widget=0x8c724e8)
at /usr/src/debug/kdebase-runtime-4.4.1/kstyles/oxygen/oxygen.cpp:299
#29 0x01d19eb9 in QScrollBar::paintEvent (this=0x8c724e8) at
widgets/qscrollbar.cpp:547
#30 0x018f4e8b in QWidget::event (this=0x8c724e8, event=0xbff145a4) a

[Bug 188142] Kmail crash (SIGSEGV) when opening attachment [KMHandleAttachmentCommand::slotStart]

[kavol]

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





--- Comment #22 from kavol   2010-03-25 22:55:18 ---
Created an attachment (id=42261)
 --> (http://bugs.kde.org/attachment.cgi?id=42261)
New crash information added by DrKonqi

I've tried to open .jpg attachment with Gwenview

the e-mail is stored on IMAP server

-- 
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 188142] Kmail crash (SIGSEGV) when opening attachment [KMHandleAttachmentCommand::slotStart]

[kavol]

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


kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz




-- 
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 186502] Kmail crashes at startup / other situations (IMAP-cache related) [QTreeWidget*, KMMimePartTreeItem, partNode::fillMimePartTree, KMail::ObjectTreeParser::insertAndParseNewChildNode]

[kavol]

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


kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz




-- 
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 186502] Kmail crashes at startup / other situations (IMAP-cache related) [QTreeWidget*, KMMimePartTreeItem, partNode::fillMimePartTree, KMail::ObjectTreeParser::insertAndParseNewChildNode]

[kavol]

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





--- Comment #45 from kavol   2010-03-09 12:38:33 ---
Created an attachment (id=41472)
 --> (http://bugs.kde.org/attachment.cgi?id=41472)
New crash information added by DrKonqi

don't know if it is the kmail version or something special about the e-mail
causing this, but I've only started seeing this today

-- 
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 228423] New: can't start kmail over ssh at the first try

[kavol]

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

   Summary: can't start kmail over ssh at the first try
   Product: kmail
   Version: unspecified
  Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: ka...@seznam.cz


Version:(using KDE 4.3.5)
OS:Linux
Installed from:Fedora RPMs

when trying to start kmail over ssh with X forwarding, the first try is always
unsucessful - almost immediately I get the following error (in less than 5
seconds - hardly any timeout due to network lag, sometimes it takes more to
start kmail locally ...)

[ka...@kavol ~]$ kmail
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kded4.so
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kconf_update.so
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kwalletd.so
(1593)/: Communication problem with  "kmail" , it
probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a
reply. Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken." " 


on any subsequent try, I get these messages and kmail starts normally:

[ka...@kavol ~]$ kmail
kdeinit4: preparing to launch /usr/bin/knotify4
[ka...@kavol ~]$ kdeinit4: preparing to launch /usr/bin/kwalletmanager
kdeinit4: preparing to launch /usr/lib/kde4/kio_imap4.so
(1634)/ kdemain: IMAP4::kdemain
QSystemTrayIcon::setVisible: No Icon set
kdeinit4: preparing to launch /usr/lib/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib/kde4/kio_file.so


while I suspect this problem probably is not specific to kmail, I didn't manage
to reproduce with anything else

-- 
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 32684] auto save in kmail to drafts folder

[kavol]

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


kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz




--- Comment #5 from kavol   2009-12-25 11:23:10 ---
ahem, I don't see this bug as resolved (in KMail 1.12.3, KDE 4.3.3) - you still
can't have a backup copy of the message you are editing saved in drafts folder
... once you choose to save as draft, the editor closes, once you open the
message to edit it, it disappears from drafts folder

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 118356] kmail does not correctly synthesise quoted-printable encoded multibyte characters in subject if they are divided by line break

[kavol]

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


kavol  changed:

   What|Removed |Added

 Status|RESOLVED|UNCONFIRMED
 Resolution|WAITINGFORINFO  |




--- Comment #3 from kavol   2009-12-25 11:15:26 ---
(In reply to comment #1)
> Is this still a problem in KDE 4.3? Never have gotten such a problem?

yes, if I use the attached reproducer with KMail 1.12.3 (KDE 4.3.3), the last
character of the subject line is not synthesized correctly - however, now the
behaviour is a bit different, there are two question marks instead of the
proper character, and copy&pasting that outside kmail doesn't change them into
the correct character

-- 
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 118356] kmail does not correctly synthesise quoted-printable encoded multibyte characters in subject if they are divided by line break

[kavol]

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





--- Comment #2 from kavol   2009-12-25 11:10:51 ---
Created an attachment (id=39325)
 --> (http://bugs.kde.org/attachment.cgi?id=39325)
problem reproducer

-- 
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 67516] KMail does not seem to suppost the RFC 2046 standard for content type: message/partial. (at least partial messages I receive are not reassembled)

[kavol]

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


kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz




--- Comment #2 from kavol   2009-09-16 09:21:39 ---
Note that this bug is still present in KDE 4.3.1, which is very sad ...

-- 
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 203088] cannot select whole message content (ctrl+a)

[kavol]

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


kavol  changed:

   What|Removed |Added

 CC||ka...@seznam.cz




--- Comment #2 from kavol   2009-08-21 09:37:43 ---
please see (and vote for) the bug #204625

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