[Akonadi] [Bug 317293] error message: failed to fetch the resource collection

2013-04-04 Thread András Manţia
https://bugs.kde.org/show_bug.cgi?id=317293

--- Comment #8 from András Manţia aman...@kde.org ---
Seems your imap resource is crashing (but you refer to maildir originally, so
might be not related). Anyway, can you do a ps uax | grep akonadi to see what
akonadi processes are running?

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


[kmail] [Bug 246808] Kmail messes up gpg.conf if changing debug-level

2013-04-04 Thread Gregor Tätzner
https://bugs.kde.org/show_bug.cgi?id=246808

Gregor Tätzner gre...@freenet.de changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||gre...@freenet.de
 Resolution|--- |DUPLICATE

--- Comment #3 from Gregor Tätzner gre...@freenet.de ---


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

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


[kleopatra] [Bug 226630] kwatchgnupg appends invalid options to ~/.gnupg/gpg.conf

2013-04-04 Thread Gregor Tätzner
https://bugs.kde.org/show_bug.cgi?id=226630

Gregor Tätzner gre...@freenet.de changed:

   What|Removed |Added

 CC||env...@rolamasao.org

--- Comment #9 from Gregor Tätzner gre...@freenet.de ---
*** Bug 246808 has been marked as a duplicate of this bug. ***

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


[kleopatra] [Bug 226630] kwatchgnupg appends invalid options to ~/.gnupg/gpg.conf

2013-04-04 Thread Diego
https://bugs.kde.org/show_bug.cgi?id=226630

Diego diego...@zoho.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #10 from Diego diego...@zoho.com ---
*** This bug has been confirmed by popular vote. ***

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


[kleopatra] [Bug 226630] kwatchgnupg appends invalid options to ~/.gnupg/gpg.conf

2013-04-04 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=226630

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

   What|Removed |Added

 CC||mon...@kde.org

--- Comment #11 from Laurent Montel mon...@kde.org ---
Ok someone can resume problem please ?
We must use gpg2 ?  or not ?
option is not valid for which version etc.

-- 
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 309946] KMail forgets reply or forward status in mails

2013-04-04 Thread Cyrille Dunant
https://bugs.kde.org/show_bug.cgi?id=309946

Cyrille Dunant cyrille.dun...@gmail.com changed:

   What|Removed |Added

 CC||cyrille.dun...@gmail.com

-- 
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 309946] KMail forgets reply or forward status in mails

2013-04-04 Thread Cyrille Dunant
https://bugs.kde.org/show_bug.cgi?id=309946

--- Comment #7 from Cyrille Dunant cyrille.dun...@gmail.com ---
I have that problem also, and I would be glad to help

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


[kontact] [Bug 317816] New: Kmail crash when deleting emails in IMAP folder

2013-04-04 Thread Nathan Wolf
https://bugs.kde.org/show_bug.cgi?id=317816

Bug ID: 317816
   Summary: Kmail crash when deleting emails in IMAP folder
Classification: Unclassified
   Product: kontact
   Version: 4.10.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: future...@delorean.net

Application: kontact (4.10.1)
KDE Platform Version: 4.10.1 release 545
Qt Version: 4.8.4
Operating System: Linux 3.7.10-1.1-desktop x86_64
Distribution: openSUSE 12.3 (x86_64)

-- Information about the crash:
I selected and deleted an email from an IMAP folder.  The program hung for a
moment, and crashed.  It doesn't happen every time but does happen
periodically.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f7e86887780 (LWP 9624))]

Thread 4 (Thread 0x7f7e6dc09700 (LWP 9625)):
#0  0x7f7e7e677964 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7e830657c7 in ?? () from /usr/lib64/libQtWebKit.so.4
#2  0x7f7e830657f9 in ?? () from /usr/lib64/libQtWebKit.so.4
#3  0x7f7e7e673e0f in start_thread () from /lib64/libpthread.so.0
#4  0x7f7e83dcb7dd in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f7e6d308700 (LWP 9626)):
#0  0x7f7e83dbe97d in read () from /lib64/libc.so.6
#1  0x7f7e7d6a3e0f in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f7e7d667634 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f7e7d667a42 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f7e7d667bc4 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f7e851fa1f6 in QEventDispatcherGlib::processEvents
(this=0x7f7e680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x7f7e851ca9ef in QEventLoop::processEvents
(this=this@entry=0x7f7e6d307e00, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f7e851cac78 in QEventLoop::exec (this=0x7f7e6d307e00, flags=...) at
kernel/qeventloop.cpp:204
#8  0x7f7e850cd0f0 in QThread::exec (this=optimized out) at
thread/qthread.cpp:542
#9  0x7f7e850d00cc in QThreadPrivate::start (arg=0x18f9160) at
thread/qthread_unix.cpp:338
#10 0x7f7e7e673e0f in start_thread () from /lib64/libpthread.so.0
#11 0x7f7e83dcb7dd in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f7e1c1cc700 (LWP 9712)):
#0  0x7f7e7e675e7a in pthread_mutex_lock () from /lib64/libpthread.so.0
#1  0x7f7e7d6a4a71 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#2  0x7f7e7d6674ba in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f7e7d667a42 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f7e7d667bc4 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f7e851fa1f6 in QEventDispatcherGlib::processEvents
(this=0x7f7e140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x7f7e851ca9ef in QEventLoop::processEvents
(this=this@entry=0x7f7e1c1cbdd0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f7e851cac78 in QEventLoop::exec (this=0x7f7e1c1cbdd0, flags=...) at
kernel/qeventloop.cpp:204
#8  0x7f7e850cd0f0 in QThread::exec (this=optimized out) at
thread/qthread.cpp:542
#9  0x7f7e851ab1af in QInotifyFileSystemWatcherEngine::run (this=0x271d060)
at io/qfilesystemwatcher_inotify.cpp:256
#10 0x7f7e850d00cc in QThreadPrivate::start (arg=0x271d060) at
thread/qthread_unix.cpp:338
#11 0x7f7e7e673e0f in start_thread () from /lib64/libpthread.so.0
#12 0x7f7e83dcb7dd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f7e86887780 (LWP 9624)):
[KCrash Handler]
#6  QModelIndex (other=..., this=0x7fff7600be40) at
../../src/corelib/kernel/qabstractitemmodel.h:65
#7  QSortFilterProxyModel::parent (this=0x23c9820, child=...) at
itemviews/qsortfilterproxymodel.cpp:1676
#8  0x7f7e851c2630 in parent (this=optimized out) at
kernel/qabstractitemmodel.h:393
#9  QAbstractItemModelPrivate::rowsAboutToBeRemoved (this=this@entry=0x23cae10,
parent=..., first=first@entry=0, last=last@entry=0) at
kernel/qabstractitemmodel.cpp:726
#10 0x7f7e851c3536 in QAbstractItemModel::beginRemoveRows (this=0x23c9820,
parent=..., first=0, last=0) at kernel/qabstractitemmodel.cpp:2471
#11 0x7f7e84afd0f5 in QSortFilterProxyModelPrivate::remove_proxy_interval
(this=0x23cae10, source_to_proxy=..., proxy_to_source=..., proxy_start=0,
proxy_end=optimized out, proxy_parent=..., orient=Qt::Vertical,
emit_signal=true) at itemviews/qsortfilterproxymodel.cpp:557
#12 0x7f7e84b0188a in QSortFilterProxyModelPrivate::remove_source_items
(this=this@entry=0x23cae10, source_to_proxy=..., proxy_to_source=...,
source_items=..., source_parent=..., orient=orient@entry=Qt::Vertical,
emit_signal=emit_signal@entry=true) at itemviews/qsortfilterproxymodel.cpp:539
#13 

[kmail2] [Bug 317817] New: Timezone set wrong in sending headers

2013-04-04 Thread Orion
https://bugs.kde.org/show_bug.cgi?id=317817

Bug ID: 317817
   Summary: Timezone set wrong in sending headers
Classification: Unclassified
   Product: kmail2
   Version: 4.10.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: orion200...@yahoo.co.uk

If I set timezone to CAT (UTC +0200) Kmail inserts in header of sent mails that
it is in fact UTC +0204 - adding 4 minutes from somewhere.
I was made aware of this by Ben Cooksley when I mailed some issues to KDEPIM
developers mailing list. According to him this makes my sent mail to be seen as
possible spam by many systems.
I can not see anywhere else in my system or using Thunderbird that the timezone
gets +4 minutes added

Reproducible: Always

Steps to Reproduce:
1. Set timezone to Harare,Zimbabwe (CAT)
2. Start KMail, create a mail or reply, send it
3. Check headers in sent-mail, in headers you find (eg) Date: Mon, 11 Mar 2013
09:30:03 +0204
Actual Results:  
sent date set to +0204 instead of +0200, thereby creating problems with spam
checking systems

Expected Results:  
sent date set to actual timezone value, +0200

-- 
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 317293] error message: failed to fetch the resource collection

2013-04-04 Thread jmaldrich
https://bugs.kde.org/show_bug.cgi?id=317293

--- Comment #9 from jmaldr...@yahoo.com ---
Quoting András Manţia  aman...@kde.org:

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

 --- Comment #8 from András Manţia aman...@kde.org ---
 Seems your imap resource is crashing (but you refer to maildir originally, so
 might be not related). Anyway, can you do a ps uax | grep akonadi   
 to see what
 akonadi processes are running?

Sure... and IMAP only crashes when I shut down Akonadi. The rest of  
the time (mostly) it works fine. IMAP *is* buggy, but in this case, I  
think it's a red herring, so to speak.

Here's the list:
john  9686  0.4  0.1 250036  5440 ?Sl   07:10   0:00  
/usr/bin/akonadi_control
john  9688  2.0  0.3 1393460 15484 ?   Sl   07:10   0:02 akonadiserver
john  9690  2.8  0.8 1206900 31996 ?   Sl   07:10   0:03  
/usr/libexec/mysqld  
--defaults-file=/home/john/.local/share/akonadi/mysql.conf  
--datadir=/home/john/.local/share/akonadi/db_data/  
--socket=/home/john/.local/share/akonadi/socket-slave1.aldrich/mysql.socket
john  9721  0.4  0.6 700884 25456 ?S07:10   0:00  
/usr/bin/akonadi_archivemail_agent --identifier  
akonadi_archivemail_agent
john  9722  0.2  0.5 437060 19656 ?Sl   07:10   0:00  
/usr/bin/akonadi_agent_launcher akonadi_contacts_resource  
akonadi_contacts_resource_1
john  9723  0.4  0.6 699868 24756 ?Sl   07:10   0:00  
/usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_4
john  9724  1.2  0.8 707820 31804 ?Sl   07:10   0:01  
/usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_7
john  9725  0.2  0.4 445872 18828 ?S07:10   0:00  
/usr/bin/akonadi_kabc_resource --identifier akonadi_kabc_resource_3
john  9726  0.2  0.4 513112 18232 ?Sl   07:10   0:00  
/usr/bin/akonadi_kabc_resource --identifier akonadi_kabc_resource_4
john  9727  0.2  0.5 443456 19976 ?Sl   07:10   0:00  
/usr/bin/akonadi_agent_launcher akonadi_maildir_resource  
akonadi_maildir_resource_2
john  9728  0.3  0.4 483976 18088 ?S07:10   0:00  
/usr/bin/akonadi_maildispatcher_agent --identifier  
akonadi_maildispatcher_agent
john  9729  1.2  0.7 705988 29728 ?S07:10   0:01  
/usr/bin/akonadi_mailfilter_agent --identifier akonadi_mailfilter_agent
john  9730  2.7  1.3 561836 52700 ?Sl   07:10   0:03  
/usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
john  9731  0.2  0.4 443952 17400 ?S07:10   0:00  
/usr/bin/akonadi_pop3_resource --identifier akonadi_pop3_resource_6
john  9732  0.2  0.4 443828 17416 ?S07:10   0:00  
/usr/bin/akonadi_pop3_resource --identifier akonadi_pop3_resource_7
john  9733  0.2  0.4 443828 17412 ?S07:10   0:00  
/usr/bin/akonadi_pop3_resource --identifier akonadi_pop3_resource_9
john  9734  0.2  0.5 437120 19932 ?Sl   07:10   0:00  
/usr/bin/akonadi_agent_launcher akonadi_vcard_resource  
akonadi_vcard_resource_0
john  9845  0.0  0.0 109184   848 pts/1S+   07:12   0:00 grep  
--color=auto akonadi

Anything else you need, let me know.

-- 
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 317823] New: crash when forwarding a mail with multipart/digest attachment

2013-04-04 Thread thilo
https://bugs.kde.org/show_bug.cgi?id=317823

Bug ID: 317823
   Summary: crash when forwarding a mail with multipart/digest
attachment
Classification: Unclassified
   Product: kmail2
   Version: 4.10.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-bugs@kde.org
  Reporter: th...@riessner.de

I tried to forward a mail with a multpard/digest attachment from my sent
folder. Ich forwared some mails to one address before this mail was created
with a multipart/digest attachment containing that mails. I liked to forward
 the same messages to an other address. So marked the already sent mail and
tried to forward it to an other address. But as soon as I typed 'F' kmail
crashed. This doesn't happen with normal mails.


Reproducible: Always

Steps to Reproduce:
1. mark several mails
2. press 'f' to forward them
3. choose to send them in one digest mail, not as single mails
4. select this one mail in the sent folder
5. press 'f' to forward it
Actual Results:  
kmail crashes immediately after pressing 'f'

Expected Results:  
the mail should be forwarded normally

-- 
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 317823] crash when forwarding a mail with multipart/digest attachment

2013-04-04 Thread thilo
https://bugs.kde.org/show_bug.cgi?id=317823

--- Comment #1 from th...@riessner.de ---
Created attachment 78630
  -- https://bugs.kde.org/attachment.cgi?id=78630action=edit
crash report created by kmail

kmail tried to submit this crash report directly, but is was rejected with the
notice, that version 4.10 is not known??

-- 
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 310210] Cannot add apple / icloud address book resource with CardCAV

2013-04-04 Thread numkem
https://bugs.kde.org/show_bug.cgi?id=310210

num...@gmail.com changed:

   What|Removed |Added

 CC||num...@gmail.com

--- Comment #3 from num...@gmail.com ---
Same applies to me.

After some reading, the server prefix doesn't matter. One nice thing I foud
that could help with finding URLs is : https://github.com/muhlba91/icloud

-- 
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 317830] New: Kmail-4.10.1 crashed after I had sent an email (filters)

2013-04-04 Thread Christian
https://bugs.kde.org/show_bug.cgi?id=317830

Bug ID: 317830
   Summary: Kmail-4.10.1 crashed after I had sent an email
(filters)
Classification: Unclassified
   Product: Akonadi
   Version: 4.10
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: Mail Filter Agent
  Assignee: kdepim-bugs@kde.org
  Reporter: joulupukin.ton...@yandex.ru

Application: akonadi_mailfilter_agent (4.10)
KDE Platform Version: 4.10.1
Qt Version: 4.8.4
Operating System: Linux 3.7.10-gentoo x86_64
Distribution: Gentoo Base System release 2.1

-- Information about the crash:
- What I was doing when the application crashed:
I had sent an email and wasn't doing anything in Kmail any more.

- Unusual behavior I noticed:
When I compose a new email, there's a yellow warning at the top saying that the
akonadi desktop indexer is not running. When I click on configure in that
box, the dialog window that pops up says that it is running and indexing or
ready.
Also, kmail-4.10.1 is somewhat slower than the previous kmail-4.9.5. This crash
never occurred in kmail-4.9.5

Additionally, I suspect that this is related to the filter rules of the type,
If To is not in the address book, with action Add to address book. In the
previous kmail-4.9.5 this added lots of addresses many times (or added names
with no addresses), I have reported a bug about this. Maybe in kmail-4.10.1
this is now fixed so that it no longer produces duplicates, but crashes
instead?

-- Backtrace:
Application: Sähköpostisuodatin (akonadi_mailfilter_agent), signal:
Segmentation fault
Using host libthread_db library /lib64/libthread_db.so.1.
[KCrash Handler]
#6  deref (this=0x382f4c6f51434963) at
/usr/include/qt4/QtCore/qatomic_x86_64.h:133
#7  operator= (l=..., this=0x186e1d8) at /usr/include/qt4/QtCore/qlist.h:442
#8  clear (this=0x186e1d8) at /usr/include/qt4/QtCore/qlist.h:766
#9  timeout (this=0x186e180) at
/tmp/portage/kde-base/kdepimlibs-4.10.1/work/kdepimlibs-4.10.1/akonadi/itemfetchjob.cpp:73
#10 Akonadi::ItemFetchJob::qt_static_metacall (_o=optimized out,
_c=optimized out, _id=optimized out, _a=optimized out) at
/tmp/portage/kde-base/kdepimlibs-4.10.1/work/kdepimlibs-4.10.1_build/akonadi/moc_itemfetchjob.cpp:57
#11 0x7fa017917441 in QMetaObject::activate (sender=0x18356c0, m=optimized
out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3539
#12 0x7fa01791c319 in QObject::event (this=0x18356c0, e=optimized out) at
kernel/qobject.cpp:1156
#13 0x7fa015e58cd4 in notify_helper (e=0x7fff14948910, receiver=0x18356c0,
this=0x1569420) at kernel/qapplication.cpp:4562
#14 QApplicationPrivate::notify_helper (this=0x1569420, receiver=0x18356c0,
e=0x7fff14948910) at kernel/qapplication.cpp:4534
#15 0x7fa015e5da33 in QApplication::notify (this=0x7fff14948c40,
receiver=0x18356c0, e=0x7fff14948910) at kernel/qapplication.cpp:4423
#16 0x7fa018a8f428 in KApplication::notify (this=0x7fff14948c40,
receiver=0x18356c0, event=0x7fff14948910) at
/tmp/portage/kde-base/kdelibs-4.10.1-r1/work/kdelibs-4.10.1/kdeui/kernel/kapplication.cpp:311
#17 0x7fa01790330b in QCoreApplication::notifyInternal
(this=0x7fff14948c40, receiver=0x18356c0, event=0x7fff14948910) at
kernel/qcoreapplication.cpp:946
#18 0x7fa0179346aa in sendEvent (event=0x7fff14948910, receiver=optimized
out) at kernel/qcoreapplication.h:231
#19 QTimerInfoList::activateTimers (this=0x15692d0) at
kernel/qeventdispatcher_unix.cpp:622
#20 0x7fa017931f5d in timerSourceDispatch (source=optimized out) at
kernel/qeventdispatcher_glib.cpp:186
#21 timerSourceDispatch (source=optimized out) at
kernel/qeventdispatcher_glib.cpp:180
#22 0x7fa017931f91 in idleTimerSourceDispatch (source=optimized out) at
kernel/qeventdispatcher_glib.cpp:233
#23 0x7fa00f0ac8fa in g_main_dispatch (context=0x156af30) at gmain.c:2539
#24 g_main_context_dispatch (context=0x156af30) at gmain.c:3075
#25 0x7fa00f0acc58 in g_main_context_iterate (context=0x156af30, block=1,
dispatch=1, self=optimized out) at gmain.c:3146
#26 0x7fa00f0acd0c in g_main_context_iteration (context=0x156af30,
may_block=1) at gmain.c:3207
#27 0x7fa0179326d6 in QEventDispatcherGlib::processEvents (this=0x152aad0,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#28 0x7fa015efd006 in QGuiEventDispatcherGlib::processEvents
(this=optimized out, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x7fa017901db2 in QEventLoop::processEvents (this=optimized out,
flags=...) at kernel/qeventloop.cpp:149
#30 0x7fa017902037 in QEventLoop::exec (this=0x7fff14948bb0, flags=...) at
kernel/qeventloop.cpp:204
#31 0x7fa017906f25 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1218
#32 0x7fa017f49a63 in Akonadi::AgentBase::init (r=0x1717320) at

[kdepimlibs] [Bug 317834] New: Wrong date for Ching Ming Festival (HK holiday)

2013-04-04 Thread aditsu
https://bugs.kde.org/show_bug.cgi?id=317834

Bug ID: 317834
   Summary: Wrong date for Ching Ming Festival (HK holiday)
Classification: Unclassified
   Product: kdepimlibs
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kholidays
  Assignee: jl...@kde.org
  Reporter: adi...@yahoo.com
CC: kdepim-bugs@kde.org

I'm using kde 4.9.5 and the calendar (configured to show Hong Kong holidays)
marks 5 Apr as the Ching Ming Festival holiday. However, that is wrong, the
correct date should be 4 Apr, as can be seen at
http://www.gov.hk/en/about/abouthk/holiday/

Reproducible: Always

Steps to Reproduce:
1. Set the calendar to show info for Hong Kong holidays
2. Look at the calendar for April 2013
Actual Results:  
Friday 05 April 2013 - Ching Ming Festival

Expected Results:  
Thursday 04 April 2013 - Ching Ming Festival

-- 
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 310210] Cannot add apple / icloud address book resource with CardCAV

2013-04-04 Thread Grégory Oestreicher
https://bugs.kde.org/show_bug.cgi?id=310210

Grégory Oestreicher g...@kamago.net changed:

   What|Removed |Added

 CC|g...@kamago.net |

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


[akregator] [Bug 260890] session and crash restauration produce a lot of tabs

2013-04-04 Thread nicofrand
https://bugs.kde.org/show_bug.cgi?id=260890

nicofr...@gmail.com changed:

   What|Removed |Added

 CC||nicofr...@gmail.com

-- 
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 316840] imap resource starts crazy connect / disconnect cycle to mail server

2013-04-04 Thread Miroslav Vujicic
https://bugs.kde.org/show_bug.cgi?id=316840

Miroslav Vujicic miros...@vujicic.com changed:

   What|Removed |Added

 CC||miros...@vujicic.com

--- Comment #4 from Miroslav Vujicic miros...@vujicic.com ---
I am seeing this behaviour too.

I am running a local Courier IMAP server and I noticed this in mail.log - one
connection from my local mail client running on the desktop on the same
network, and another connecting from an external network. In both cases the
client is akonadi_imap on KDE 4.10.1 desktop.

Also from the same desktop I am connecting to another Courier IMAP and I was
told by a sysadmin of that system that the same behaviour is noticed, ie flood
of connect/disconect.

I am happy to provide my Courier and my client settings if that may help.

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