[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 --- Comment #42 from Vincent Fortier --- Bump for 2013 with linkage to https://bugs.kde.org/show_bug.cgi?id=227672 ;) -- 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 227672] MAPI support in kmail
https://bugs.kde.org/show_bug.cgi?id=227672 Vincent Fortier changed: What|Removed |Added CC||th0...@gmail.com --- Comment #10 from Vincent Fortier --- Bump for 2013 with linkage to https://bugs.kde.org/show_bug.cgi?id=78629 ;) -- 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
[Akonadi] [Bug 312847] Nepomuk Feeder does not recognise removal of the important flag
https://bugs.kde.org/show_bug.cgi?id=312847 --- Comment #1 from Jan Gerrit Marker --- I forgot to add that this does happen when using the "todo" flag, too. It does not happen when using a nepomuk tag like "School" which is not specially used by KMail. -- 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 312847] New: Nepomuk Feeder does not recognise removal of the important flag
https://bugs.kde.org/show_bug.cgi?id=312847
Bug ID: 312847
Summary: Nepomuk Feeder does not recognise removal of the
important flag
Classification: Unclassified
Product: Akonadi
Version: 4.10
Hardware: Ubuntu Packages
OS: Linux
Status: CONFIRMED
Severity: normal
Priority: NOR
Component: Nepomuk Feeder Agents
Assignee: kdepim-bugs@kde.org
Reporter: janger...@weiler-marker.com
CC: vkra...@kde.org
Every time the "Important" flag of an email is removed nepomuk does not remove
the association between the email and the "Important" tag from its database.
Reproducible: Always
Steps to Reproduce:
1. Mark a message as important
2. Remove the important flag again
Actual Results:
Open akonadiconsole, search for the email and have a look at the "Nepomuk" tab:
"Important" is still checked although the \FLAGGED flag ("Internals" tab) is
not set anymore.
Expected Results:
"Important" should not be a tag of the email anymore.
I had a look at the code:
For every update of an email the nepomuk feeder agent creates a new graph which
is merged into the old already saved graph of the same email. The newly created
graph correctly does not contain the association with the tag but the old graph
does, of course. Nepomuk2::storeRessources() is used to push and merge the new
graph into the old one but that function does not remove the tag association
because from its point of view the association should not be deleted because
only new information of the new graph should be added to the old graph.
At least that's what I understood.
I am not sure how to fix this therefore I wrote this bug report.
--
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 289097] error "Unable to fetch item from backend" when entering IMAP folder
https://bugs.kde.org/show_bug.cgi?id=289097 ioa...@yandex.ru changed: What|Removed |Added CC||ioa...@yandex.ru --- Comment #59 from ioa...@yandex.ru --- I got the same error with 4.9.4 (Gentoo amd64) when entered one of IMAP folders on my server. I think this can be caused by any unhandled message received from server. In my case the problem was with incorrect mailbox on the server. Akonadi-imap-resource received message "* OK Message 1 no longer exists" from cyrus-imap. This message wasn't handled by Job or FetchJob and thus caused RetrieveItemTask::cancelTask call from RetrieveItemTask::onContentFetchDone. I think Akonadi should handle such messages correctly, maybe as warnings. I don't know if such errors can accure when a message was moved or deleted while Akonadi creates a request to read it. Messages from akonadi in KIMAP_LOGFILE: C: A04 SELECT "INBOX.logs" S: * 522 EXISTS S: * 0 RECENT S: * FLAGS ( \Answered \Flagged \Draft \Deleted \Seen KMAILFORWARDED KMAILTODO KMAILWATCHED KMAILIGNORED $FORWARDED $TODO $WATCHED $IGNORED ) S: * OK Ok [ PERMANENTFLAGS ( \Answered \Flagged \Draft \Deleted \Seen KMAILFORWARDED KMAILTODO KMAILWATCHED KMAILIGNORED $FORWARDED $TODO $WATCHED $IGNORED \* ) ] S: * OK Ok [ UIDVALIDITY 1327548174 ] S: * OK Ok [ UIDNEXT 1400 ] S: * OK Ok [ HIGHESTMODSEQ 2783 ] S: * OK Ok [ URLMECH INTERNAL ] S: A04 OK Completed [ READ-WRITE ] C: A05 EXPUNGE S: A05 OK Completed C: A06 SELECT "INBOX.logs" S: * OK Ok [ CLOSED ] S: * 522 EXISTS S: * 0 RECENT S: * FLAGS ( \Answered \Flagged \Draft \Deleted \Seen KMAILFORWARDED KMAILTODO KMAILWATCHED KMAILIGNORED $FORWARDED $TODO $WATCHED $IGNORED ) S: * OK Ok [ PERMANENTFLAGS ( \Answered \Flagged \Draft \Deleted \Seen KMAILFORWARDED KMAILTODO KMAILWATCHED KMAILIGNORED $FORWARDED $TODO $WATCHED $IGNORED \* ) ] S: * OK Ok [ UIDVALIDITY 1327548174 ] S: * OK Ok [ UIDNEXT 1400 ] S: * OK Ok [ HIGHESTMODSEQ 2783 ] S: * OK Ok [ URLMECH INTERNAL ] S: A06 OK Completed [ READ-WRITE ] C: A07 FETCH 1:522 (FLAGS UID) S: * 1 FETCH ( FLAGS (\Seen) UID 8 ) S: * 2 FETCH ( FLAGS (\Seen) UID 879 ) <...> S: * 521 FETCH ( FLAGS (\Seen) UID 1398 ) S: * 522 FETCH ( FLAGS (\Seen) UID 1399 ) S: A07 OK Completed ( 0.010 sec ) C: A08 UID FETCH 8 (BODY.PEEK[] UID) S: * OK Message 1 no longer exists S: A08 OK Completed ( 0.000 sec ) C: A09 EXPUNGE S: A09 OK Completed P.S. In my case this error belongs to "IMAP resource", not "server" component of Akonadi. P.P.S. Sorry for my English. -- 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 312841] New: importwizard.desktop use "Name=Import Wizard", which is a quite generic name and does not give users much hint.
https://bugs.kde.org/show_bug.cgi?id=312841 Bug ID: 312841 Summary: importwizard.desktop use "Name=Import Wizard", which is a quite generic name and does not give users much hint. Classification: Unclassified Product: kdepim Version: GIT (master) Hardware: Other OS: Linux Status: CONFIRMED Severity: minor Priority: NOR Component: importwizard Assignee: kdepim-bugs@kde.org Reporter: adap...@gmail.com Currently the menu item is just shown as barely "Import Wizard". I think that has a few problems: 1. too generic to be meaningful. What kinds of thing(s) does it import: pictures, music, documents or whatever? Users do not have any clue until runing it. 2. Which application installs that menu item ? Again, users do not have any clue until running it. 3. That does not go well with freedesktop specs. "Name=" is for specific names like "Gwenview" and "KMail", while "Import Wizard" sounds quite generic. So I would suggest using a more specific and informational name, like "KMail Import Wizard". Actually, even importwizard.desktiop and the importwizard executable themselves are also too generic. But those are less visible compared to this "Name=Import Wizard". 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
[kdepimlibs] [Bug 312840] New: Procedure to fix and upload namedays holidays for the Greek language
https://bugs.kde.org/show_bug.cgi?id=312840 Bug ID: 312840 Summary: Procedure to fix and upload namedays holidays for the Greek language Classification: Unclassified Product: kdepimlibs Version: 4.9 Hardware: Other URL: https://bugs.kde.org/show_bug.cgi?id=312744 OS: Linux Status: CONFIRMED Severity: normal Priority: NOR Component: kholidays Assignee: jl...@kde.org Reporter: dgl...@gmail.com CC: kdepim-bugs@kde.org To fix the bug 312744 (Problem: some namedays with fixed date have to be changed to follow Eastern date) i want to explain me how to proceed. I see that there are two files in kholiday: plan1 and plan2. I have to fix one of them or both ? After, i can send the file somewhere , probably here ? Thanks Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 312837] Email with two "To:" shows only first one in the list
https://bugs.kde.org/show_bug.cgi?id=312837 --- Comment #2 from Albert Astals Cid --- Created attachment 76289 --> https://bugs.kde.org/attachment.cgi?id=76289&action=edit How it looks like (notice there is only one To:) listed -- 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 312837] Email with two "To:" shows only first one in the list
https://bugs.kde.org/show_bug.cgi?id=312837 --- Comment #1 from Albert Astals Cid --- Created attachment 76288 --> https://bugs.kde.org/attachment.cgi?id=76288&action=edit The email i got with two "To:" -- 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 312837] New: Email with two "To:" shows only first one in the list
https://bugs.kde.org/show_bug.cgi?id=312837 Bug ID: 312837 Summary: Email with two "To:" shows only first one in the list Classification: Unclassified Product: kmail2 Version: 4.9.3 Hardware: Other OS: Linux Status: CONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: aa...@kde.org Email with two "To:" shows only first one in the list Reproducible: Always Steps to Reproduce: 1. Get an email that has two "To:" addresses 2. Look at it in the message view Actual Results: The "To:" in the message line only has my address Expected Results: The "To:" in the message line has both addresses -- 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 312145] Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 Dan Vrátil changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #13 from Dan Vrátil --- No, keep it open. Something somewhere is still broken :-) -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 311688] The "Export KMail Data" action uses icon "backup-mail", which is unavailable
https://bugs.kde.org/show_bug.cgi?id=311688 Laurent Montel changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||4.10 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/6fd48159f6fc7b7470493d66 ||28321603d9aae237 --- Comment #3 from Laurent Montel --- Git commit 6fd48159f6fc7b7470493d6628321603d9aae237 by Montel Laurent. Committed on 07/01/2013 at 19:37. Pushed by mlaurent into branch 'KDE/4.10'. Fix Bug 311688 - The "Export KMail Data" action uses icon "backup-mail", which is unavailable We don't have icons for it. So Use kmail for 4.10 We will ask for new icon FIXED-IN: 4.10 M +1-1kmail/kmmainwidget.cpp http://commits.kde.org/kdepim/6fd48159f6fc7b7470493d6628321603d9aae237 -- 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 259813] reading mails in unread mode instantly disappears from list
https://bugs.kde.org/show_bug.cgi?id=259813 Ingo Ratsdorf changed: What|Removed |Added CC||i...@envirology.co.nz --- Comment #18 from Ingo Ratsdorf --- more than 2 years down the track and no fix yet? -- 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 312145] Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 --- Comment #12 from Yuriy Vidineev --- Nice, thank you! I tried to recreate resource few days ago - and it didn't helped. But now it helped - all works! Few days ago I had only very unstable GPRS, now I have stable internet access - maybe, it is the root of my problem. So now all works, thank you again! Should I close this bug? -- 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 312830] New: Kmail crashed while viewing email
https://bugs.kde.org/show_bug.cgi?id=312830 Bug ID: 312830 Summary: Kmail crashed while viewing email Classification: Unclassified Product: kontact Version: 4.9.4 Hardware: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: sgr...@redhat.com Application: kontact (4.9.4) KDE Platform Version: 4.9.4 Qt Version: 4.8.4 Operating System: Linux 3.6.10-4.fc18.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: When kmail crashed, I had clicked on an email I wanted to see. The interface froze up and I decided to browse some web sites. Then the crash handler popped up. About 5 minutes had ellapsed from the time I clicked on an email until the crash occurred. I do have filters that send email to the trash. So, I don't know if that had anything to do with a crash. -- Backtrace: Application: Kontact (kontact), 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 0x7fe50840c880 (LWP 6188))] Thread 4 (Thread 0x7fe4f875d700 (LWP 6189)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 #1 0x003e6ce1672d in WTF::TCMalloc_PageHeap::scavengerThread (this=0x3e6d800ce0 ) at wtf/FastMalloc.cpp:2495 #2 0x003e6ce16839 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at wtf/FastMalloc.cpp:1618 #3 0x003e41407d15 in start_thread (arg=0x7fe4f875d700) at pthread_create.c:308 #4 0x003e410f22cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 3 (Thread 0x7fe4f7e5c700 (LWP 6190)): #0 0x003e410e97ed in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x003e40c47d44 in g_main_context_poll (n_fds=1, fds=0x7fe4f00029c0, timeout=4390, context=0x7fe4f9a0, priority=) at gmain.c:3584 #2 g_main_context_iterate (context=context@entry=0x7fe4f9a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3285 #3 0x003e40c47e64 in g_main_context_iteration (context=0x7fe4f9a0, may_block=1) at gmain.c:3351 #4 0x003e4d1a60f6 in QEventDispatcherGlib::processEvents (this=0x7fe4f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x003e4d1767df in QEventLoop::processEvents (this=this@entry=0x7fe4f7e5bd00, flags=...) at kernel/qeventloop.cpp:149 #6 0x003e4d176a68 in QEventLoop::exec (this=0x7fe4f7e5bd00, flags=...) at kernel/qeventloop.cpp:204 #7 0x003e4d078950 in QThread::exec (this=) at thread/qthread.cpp:542 #8 0x003e4d07b92c in QThreadPrivate::start (arg=0xb545e0) at thread/qthread_unix.cpp:338 #9 0x003e41407d15 in start_thread (arg=0x7fe4f7e5c700) at pthread_create.c:308 #10 0x003e410f22cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 2 (Thread 0x7fe4f6707700 (LWP 6191)): #0 0x003e410e97ed in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x003e40c47d44 in g_main_context_poll (n_fds=3, fds=0x7fe4e00010c0, timeout=-1, context=0xe46410, priority=) at gmain.c:3584 #2 g_main_context_iterate (context=0xe46410, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3285 #3 0x003e40c481a2 in g_main_loop_run (loop=0xe463a0) at gmain.c:3484 #4 0x003e49ccc546 in gdbus_shared_thread_func (user_data=0xe463e0) at gdbusprivate.c:277 #5 0x003e40c6b5f5 in g_thread_proxy (data=0xe4c990) at gthread.c:797 #6 0x003e41407d15 in start_thread (arg=0x7fe4f6707700) at pthread_create.c:308 #7 0x003e410f22cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 Thread 1 (Thread 0x7fe50840c880 (LWP 6188)): [KCrash Handler] #6 operator QItemSelectionModel* (this=) at ../../src/corelib/kernel/qpointer.h:78 #7 QAbstractItemView::selectionModel (this=0x322d4143) at itemviews/qabstractitemview.cpp:766 #8 0x003f1fec6676 in MailCommon::FolderTreeWidget::selectedCollections (this=) at /usr/src/debug/kdepim-4.9.4/mailcommon/foldertreewidget.cpp:244 #9 0x003f20f2206a in KMMainWidget::updateFolderMenu (this=this@entry=0x135c090) at /usr/src/debug/kdepim-4.9.4/kmail/kmmainwidget.cpp:4167 #10 0x003f20f32eb8 in KMMainWidget::slotEndCheckFetchCollectionsDone (this=0x135c090, job=) at /usr/src/debug/kdepim-4.9.4/kmail/kmmainwidget.cpp:469 #11 0x003f20f386e6 in KMMainWidget::qt_static_metacall (_o=0x135c090, _c=, _id=, _a=0x79c5a950) at /usr/src/debug/kdepim-4.9.4/x86_64-redhat-linux-gnu/kmail/kmmainwidget.moc:370 #12 0x003e4d18cebf in QMetaObject::activate (sender=0x11e41930, m=, local_signal_index=, argv=0x79c5a950) at kernel/qobject.cpp:3539 #13 0x003e5c7f in KJob::finished (this=this@entry=0x11e41930, _t1=_t1@entry=0x11e41930) at /usr/src/debug/kdelibs-4.9.4/x86_64-redhat-linux-gnu/kdecore/kjob.moc:186 #14 0x003e533
[Akonadi] [Bug 312145] Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 --- Comment #11 from Dan Vrátil --- It just says RFC822 (which is actually an RFC for emails), but for some reason in Akonadi that means "content body" for any content :-) The problem here is, that Akonadi and the Google resource does not expect the field to be empty, so it kinda breaks stuff. I'll see if and how this is supposed to be handled. Meanwhile try removing the Akonadi Resource and adding it again. It will sync all the events again, hopefully correctly now. -- 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 312145] Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 --- Comment #10 from Yuriy Vidineev --- Created attachment 76281 --> https://bugs.kde.org/attachment.cgi?id=76281&action=edit Information from DB for pimitemid 17483 -- 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 312145] Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 --- Comment #9 from Yuriy Vidineev --- I guess that right pimitemid 17483 (not 17834) because of error: "akonadi_googlecalendar_resource_0(9820)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: Failed to parse incidence! Item id = 17483 Storage collection id 67 parentCollectionId = -102" Second, pimitemid =17834 looks like regular email, not calendar event. For 17483 there is not so much information, only blank fields (I will attach screenshot) P.S. Sorry for my English -- 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 312145] Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 --- Comment #8 from Dan Vrátil --- You can obtain value of "id" column by running query "SELECT id FROM parttable WHERE pimitemid=17834" in DB Console. They are sorted, so it will be easier to find. -- 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 312145] Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 --- Comment #7 from Dan Vrátil --- Ok, let's try the more hardcore approach :) In Akonadi Console, "DB Browser" tab, select "parttable" and click Refresh. Try to find row with pimitemid=17834 and paste content of "data" column. -- 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 312145] Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 --- Comment #6 from Yuriy Vidineev --- Created attachment 76280 --> https://bugs.kde.org/attachment.cgi?id=76280&action=edit Just my akonadi console creenshot Calendar ade...@gmail.com doesn't work, other calendars work fine -- 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 312145] Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 --- Comment #5 from Yuriy Vidineev --- Thank you for your answer! Looks like I can't see any items from my main calendar (It's just blank right panel in Akonadi Console). When I trying to do it in akonadi log: akonadi_googlecalendar_resource_0(9820)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: Failed to parse incidence! Item id = 17495 Storage collection id 67 parentCollectionId = -100 akonadi_googlecalendar_resource_0(9820)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: "" akonadi_googlecalendar_resource_0(9820)/libakonadi Akonadi::ItemSerializer::deserialize: Unable to deserialize payload part: "RFC822" akonadi_googlecalendar_resource_0(9820)/libakonadi Akonadi::ItemSerializer::deserialize: Payload data was: "" akonadi_googlecalendar_resource_0(9820)/kdepimlibs (kcalcore): parse error ; string is empty? true akonadi_googlecalendar_resource_0(9820)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: Failed to parse incidence! Item id = 17489 Storage collection id 67 parentCollectionId = -101 akonadi_googlecalendar_resource_0(9820)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: "" akonadi_googlecalendar_resource_0(9820)/libakonadi Akonadi::ItemSerializer::deserialize: Unable to deserialize payload part: "RFC822" akonadi_googlecalendar_resource_0(9820)/libakonadi Akonadi::ItemSerializer::deserialize: Payload data was: "" akonadi_googlecalendar_resource_0(9820)/kdepimlibs (kcalcore): parse error ; string is empty? true akonadi_googlecalendar_resource_0(9820)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: Failed to parse incidence! Item id = 17483 Storage collection id 67 parentCollectionId = -102 akonadi_googlecalendar_resource_0(9820)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: "" akonadi_googlecalendar_resource_0(9820)/libakonadi Akonadi::ItemSerializer::deserialize: Unable to deserialize payload part: "RFC822" akonadi_googlecalendar_resource_0(9820)/libakonadi Akonadi::ItemSerializer::deserialize: Payload data was: "" akonadi_nepomuk_feeder(9829) FeederPluginloader::feederPluginsForMimeType: No feeder for type "inode/directory" found akonadi_googlecalendar_resource_0(9820) KGAPI::AccessManagerPrivate::nam_sendRequest: Failed to resolve service "" ItemRetrieverException : Unable to retrieve item from resource: Invalid item retrieved -- 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 312145] Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 --- Comment #4 from Dan Vrátil --- Can you please check what the item contains? Open Akonadi Console -> Browser, select "Generic" model, in the left list select all calendars you have (Ctrl+click) and try to find item with ID 17834. Paste here content of "Raw Payload" tab (strip any sensitive information). -- 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 312145] Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 --- Comment #3 from Yuriy Vidineev --- With the "official" ubuntu raring libkgapi (http://changelogs.ubuntu.com/changelogs/pool/universe/libk/libkgapi/libkgapi_0.4.4-0ubuntu1/changelog) I have the same problem -- 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 310700] Multiple actions in one filter not applied correctly
https://bugs.kde.org/show_bug.cgi?id=310700 --- Comment #1 from Nick Leverton --- Still an issue in 4.9.97 RC2. -- 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 259813] reading mails in unread mode instantly disappears from list
https://bugs.kde.org/show_bug.cgi?id=259813 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu -- 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
[nepomuk] [Bug 294320] kmail complains about the semantic destkop not running, when it is
https://bugs.kde.org/show_bug.cgi?id=294320 Kristian Rink changed: What|Removed |Added CC||k...@zimmer428.net --- Comment #12 from Kristian Rink --- I do have the same issue in KDE 4.10 rc2. Didn't see this before so far, it just popped up all of a sudden this morning. Restarting nepomuk doesn't seem to solve that problem. Is there anything else to check what is happening here? -- 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 312813] New: akonadi_nepomuk_feeder sucks memory (~!.5 GB reserved memory at this time)
https://bugs.kde.org/show_bug.cgi?id=312813 Bug ID: 312813 Summary: akonadi_nepomuk_feeder sucks memory (~!.5 GB reserved memory at this time) Classification: Unclassified Product: Akonadi Version: 4.9 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Nepomuk Feeder Agents Assignee: kdepim-bugs@kde.org Reporter: h...@urpla.net CC: vkra...@kde.org I have a total of 4 imap huge accounts (take that literal), which I try to manage with the kde pim suite (now at K:R:49 = 4.9.5 from OBS, running on openSUSE 12.2/x86_64). Thanks god, my primary system is well equipped with a fast CPU and 8 GB RAM, as well as are the mail server. Unfortunately, I have to restart akonadi every two days at least, because: hp9112 5.8 0.5 2470692 41104 ? Sl Jan04 260:52 akonadiserver hp9126 3.5 2.8 766564 230144 ? Sl Jan04 155:56 /usr/bin/akonadi_imap_resource hp9127 0.3 0.6 625376 49176 ?Sl Jan04 14:10 /usr/bin/akonadi_imap_resource hp9128 0.0 0.1 554872 11324 ?Sl Jan04 0:35 /usr/bin/akonadi_imap_resource hp9129 0.0 0.1 555712 13284 ?Sl Jan04 0:46 /usr/bin/akonadi_imap_resource hp9134 0.0 0.1 507080 11804 ?SJan04 0:20 /usr/bin/akonadi_mailfilter_agent hp9135 1.5 19.5 1895240 1596364 ? SJan04 68:35 /usr/bin/akonadi_nepomuk_feeder >From this, you can see, that I really use one primary and one secondary imap account, while the other two are kept silent (no accesses, no manual nor auto updates). I've stopped kmail already, since that wasn't responding anymore. The semantic desktop is on, file indexer and email indexer are switched off. Looking at the numbers, the 1.5 GB from akonadi_nepomuk_feeder disturbs me most. I've no idea what the code is doing or trying to archive, but feeding nepomuk must be possible with much less resource consumption or something is conceptually wrong. Reproducible: Always Steps to Reproduce: 1. run kmail with huge imap mailboxes for a while 2. check memory consumption 3. I can provide more detailed information, if necessary as I control the cyrus imap server as well. -- 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 259813] reading mails in unread mode instantly disappears from list
https://bugs.kde.org/show_bug.cgi?id=259813 Paul Sobey changed: What|Removed |Added CC||bud...@the-annexe.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
[kmail2] [Bug 55339] Using ":" in filenames is incompatible with some NFS servers (Dell and others that are Windows Powered)
https://bugs.kde.org/show_bug.cgi?id=55339 Laurent Montel changed: What|Removed |Added Status|RESOLVED|REOPENED CC||mon...@kde.org Component|maildir |commands and actions Version|1.10.1 |4.10 pre Resolution|FIXED |--- Product|kmail |kmail2 --- Comment #11 from Laurent Montel --- Move to kmail2 -- 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 55339] Using ":" in filenames is incompatible with some NFS servers (Dell and others that are Windows Powered)
https://bugs.kde.org/show_bug.cgi?id=55339
Bruno Haible changed:
What|Removed |Added
CC||br...@clisp.org
--- Comment #10 from Bruno Haible ---
This bug is not completely fixed in KDE 4.8.5.
I tried to activate the workaround, as explained in
http://article.gmane.org/gmane.comp.kde.devel.pim/26928 :
I added to $HOME/.kde4/share/config/kmail2rc, in the section [General], the
line
MaildirFilenameSeparator=!
and renamed all files named id:flags to id!flags inside the
$HOME/.local/share/local-mail directory.
Then, when I select a mail folder on the VFAT formatted USB-stick that is in
maildir format, and perform the action "Mark all mails read" on it, then the
log shows error messages like
Maildir: Failed to rename entry: "MAILDIR/FOLDER/new/1345995993.R500.HOSTNAME"
to "MAILDIR/FOLDER/cur/1345995993.R500.HOSTNAME:2,S" ! Error: "The argument
is invalid"
This error message comes from
kdepim-runtime-4.8.5/resources/maildir/libmaildir/maildir.cpp method
Maildir::changeEntryFlags, line 676. This method contains the code
#ifdef Q_OS_WIN
finalKey.append( QLatin1String("!2,") + mailDirFlags.join(QString()) );
#else
finalKey.append( QLatin1String(":2,") + mailDirFlags.join(QString()) );
#endif
In other words: For Linux users of maildir folders on NFS mounts (bug 55339)
and of USB-sticks (bug 189441) the code still attempts to use the character ':'
in the filenames. It should use a configurable default here as well.
Please, can you reopen this bug report?
--
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 312809] New: Limit tray icon "new message" count to favorite folders
https://bugs.kde.org/show_bug.cgi?id=312809 Bug ID: 312809 Summary: Limit tray icon "new message" count to favorite folders Classification: Unclassified Product: kmail2 Version: unspecified Hardware: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: k...@zimmer428.net Running kmail with having a Google Mail account (many tags which mail gets automatically sorted to) and a local company IMAP server (cyrus, server sided filtering, large amount of folders as well), I am at the moment "suffering" from having "new message" notification in my kmail tray icon as soon as there are new messages in _any_ of all these hundreds of folders. Via kde mailing lists I learnt that this behaviour can be disabled on a per-folder basis but obviously indeed this _has_ to be done manually for each folder in question. It would be nice to have a global kmail configuration option restricting new message notifications in the tray icon only to these folders listed as "favorites" / "preferred folders". Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 312798] New: kmail ends during set up new imap aacount.
https://bugs.kde.org/show_bug.cgi?id=312798 Bug ID: 312798 Summary: kmail ends during set up new imap aacount. Classification: Unclassified Product: kmail2 Version: 4.8.5 Hardware: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jana.domorow...@gmx.de Application: kmail (4.8.5) KDE Platform Version: 4.8.5 (4.8.5) Qt Version: 4.8.1 Operating System: Linux 3.2.0-35-generic-pae i686 Distribution: Ubuntu 12.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I set up a further imap outgoing server account. The incoming set up was ok. The automatic outgoing check was ok. The final ok button was ok. 1 second later Kmail ends. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xb5d92a00 (LWP 4352))] Thread 4 (Thread 0xb396db40 (LWP 4356)): #0 0x0029a416 in __kernel_vsyscall () #1 0x00d5296b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x0712964c in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6 #3 0xb6fc5263 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb6fc537f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0x00d4ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #6 0x0711bd3e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 3 (Thread 0xb3044b40 (LWP 4357)): #0 0x00d4d483 in __i686.get_pc_thunk.bx () from /lib/i386-linux-gnu/libpthread.so.0 #1 0x00d51c39 in __pthread_mutex_unlock_usercnt () from /lib/i386-linux-gnu/libpthread.so.0 #2 0x071298a4 in pthread_mutex_unlock () from /lib/i386-linux-gnu/libc.so.6 #3 0x04c36410 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x04bf680b in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x04bf6faf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #6 0x04bf7201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0x096c48e7 in QEventDispatcherGlib::processEvents (this=0xb2700468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #8 0x0969050d in QEventLoop::processEvents (this=0xb3044270, flags=...) at kernel/qeventloop.cpp:149 #9 0x096907a9 in QEventLoop::exec (this=0xb3044270, flags=...) at kernel/qeventloop.cpp:204 #10 0x0957994c in QThread::exec (this=0xa4238b0) at thread/qthread.cpp:501 #11 0x09579a3b in QThread::run (this=0xa4238b0) at thread/qthread.cpp:568 #12 0x0957cde0 in QThreadPrivate::start (arg=0xa4238b0) at thread/qthread_unix.cpp:298 #13 0x00d4ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #14 0x0711bd3e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 2 (Thread 0xb1443b40 (LWP 4372)): #0 0x04c36931 in g_private_get () from /lib/i386-linux-gnu/libglib-2.0.so.0 #1 0x04c1ac84 in g_thread_self () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0x04bf61b7 in g_main_context_acquire () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0x04bf6f58 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0x04bf7201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0x096c48e7 in QEventDispatcherGlib::processEvents (this=0xa41b760, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x0969050d in QEventLoop::processEvents (this=0xb1443240, flags=...) at kernel/qeventloop.cpp:149 #7 0x096907a9 in QEventLoop::exec (this=0xb1443240, flags=...) at kernel/qeventloop.cpp:204 #8 0x0957994c in QThread::exec (this=0xa7c7950) at thread/qthread.cpp:501 #9 0x0966db5d in QInotifyFileSystemWatcherEngine::run (this=0xa7c7950) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x0957cde0 in QThreadPrivate::start (arg=0xa7c7950) at thread/qthread_unix.cpp:298 #11 0x00d4ed4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0 #12 0x0711bd3e in clone () from /lib/i386-linux-gnu/libc.so.6 Thread 1 (Thread 0xb5d92a00 (LWP 4352)): [KCrash Handler] #7 size (this=) at ../../include/QtCore/../../src/corelib/tools/qlist.h:98 #8 size (this=) at ../../include/QtCore/../../src/corelib/tools/qlist.h:137 #9 QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0xa026b70, receiver=0xaecb140, event=0xbf950b80) at kernel/qcoreapplication.cpp:978 #10 0x00ed2ea2 in notify_helper (e=0xbf950b80, receiver=0xaecb140, this=0xa026b70) at kernel/qapplication.cpp:4555 #11 QApplicationPrivate::notify_helper (this=0xa026b70, receiver=0xaecb140, e=0xbf950b80) at kernel/qapplication.cpp:4531 #12 0x00ed83a2 in QApplication::notify (this=0xa026b70, receiver=0xaecb140, e=0xbf950b80) at kernel/qapplication.cpp:4524 #13 0x00604e01 in KApplication::notify (this=0xbf9518dc, receiver=0xaecb140, event=0xbf950b80) at ../../kdeui/kernel/kapplication.cpp:311 #14 0x0969197e in QCoreApplication::notifyInternal (th
[akregator] [Bug 305494] Akregator always claims it wasn't closed correctly
https://bugs.kde.org/show_bug.cgi?id=305494 Belomir changed: What|Removed |Added CC||leg...@mail.ru --- Comment #2 from Belomir --- Appeared for me after upgrading from kubuntu-backports ppa to 4.9.5 kubuntu 12.04, kde 4.9.5 -- 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
