[Bug 312145] New: Failed to parse incidence when updating calendar folder
https://bugs.kde.org/show_bug.cgi?id=312145 Bug ID: 312145 Summary: Failed to parse incidence when updating calendar folder Classification: Unclassified Product: Akonadi Version: 4.10 Hardware: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Google Resource Assignee: dvra...@redhat.com Reporter: adeptsm...@gmail.com CC: kdepim-bugs@kde.org After updating LibKGAPI from 0.4.2 to 0.4.4 I can't update my main google calendar. In ~/.xsession-errors: ... akonadi_googlecalendar_resource_0(2164)/kdepimlibs (kcalcore): parse error ; string is empty? true akonadi_googlecalendar_resource_0(2164)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: Failed to parse incidence! Item id = 17489 Storage collection id 67 parentCollectionId = -452 akonadi_googlecalendar_resource_0(2164)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: "" akonadi_googlecalendar_resource_0(2164)/libakonadi Akonadi::ItemSerializer::deserialize: Unable to deserialize payload part: "RFC822" akonadi_googlecalendar_resource_0(2164)/libakonadi Akonadi::ItemSerializer::deserialize: Payload data was: "" akonadi_googlecalendar_resource_0(2164)/kdepimlibs (kcalcore): parse error ; string is empty? true akonadi_googlecalendar_resource_0(2164)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: Failed to parse incidence! Item id = 17483 Storage collection id 67 parentCollectionId = -453 akonadi_googlecalendar_resource_0(2164)/akonadiserializer (calendar) Akonadi::SerializerPluginKCalCore::deserialize: "" akonadi_googlecalendar_resource_0(2164)/libakonadi Akonadi::ItemSerializer::deserialize: Unable to deserialize payload part: "RFC822" akonadi_googlecalendar_resource_0(2164)/libakonadi Akonadi::ItemSerializer::deserialize: Payload data was: "" ... Reproducible: Always LibKGAPI installed from my ppa: https://launchpad.net/~adeptg/+archive/libkgapi Maybe something wrong with package. There wasn't this problem with LibKGAPI 0.4.2 (but with this version my calendar was read-only: https://bugs.kde.org/show_bug.cgi?id=312089) -- 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 312144] high dpi displays cut message list text off
https://bugs.kde.org/show_bug.cgi?id=312144 --- Comment #1 from Manuel Amador (Rudd-O) --- Created attachment 75992 --> https://bugs.kde.org/attachment.cgi?id=75992&action=edit bug bug with text rendering -- 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 312144] New: high dpi displays cut message list text off
https://bugs.kde.org/show_bug.cgi?id=312144 Bug ID: 312144 Summary: high dpi displays cut message list text off Classification: Unclassified Product: kmail2 Version: 4.9.3 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-bugs@kde.org Reporter: rud...@rudd-o.com see attached image (with 192 dpi) 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
[Bug 312089] Cannot create a new event in a google calendar
https://bugs.kde.org/show_bug.cgi?id=312089 --- Comment #4 from Yuriy Vidineev --- FYI https://bugs.launchpad.net/ubuntu/+source/libkgapi/+bug/1093371 -- 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 312089] Cannot create a new event in a google calendar
https://bugs.kde.org/show_bug.cgi?id=312089 --- Comment #3 from Yuriy Vidineev --- 0.4.2-0ubuntu1. So looks like its kubuntu bug. Thank you! -- 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 288605] Mail Dispatcher Agent went offline for unknown reason
https://bugs.kde.org/show_bug.cgi?id=288605 Mathias Homann changed: What|Removed |Added CC||mathias.hom...@opensuse.org --- Comment #1 from Mathias Homann --- I'm having the same issues in KDE 4.9.4 here. After a few hours of working with my computer the mail dispatcher simply stops working and needs to be restarted. -- 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 312139] New: Crash editing recurring event on kontact
https://bugs.kde.org/show_bug.cgi?id=312139 Bug ID: 312139 Summary: Crash editing recurring event on kontact Classification: Unclassified Product: kontact Version: unspecified Hardware: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rser...@gmail.com Application: kontact (4.10 rc1) KDE Platform Version: 4.9.95 (Compiled from sources) Qt Version: 4.8.2 Operating System: Linux 3.7.1 x86_64 Distribution: Debian GNU/Linux 7.0 (wheezy) -- Information about the crash: I'm using google calendar resource, and while editing a recurring event, just double clicking on the event I get a kontact crash with the attached backtrace. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc4780b6780 (LWP 19301))] Thread 3 (Thread 0x7fc470757700 (LWP 19302)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fc48d873ebd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7fc48d873fc9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7fc489805b50 in start_thread (arg=) at pthread_create.c:304 #4 0x7fc487911a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 2 (Thread 0x7fc46fe56700 (LWP 19303)): #0 0x7fc48980d18d in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7fc48611c77f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc4860e11a9 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc4860e15c2 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc4860e1744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc489bc6296 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7fc489b968af in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7fc489b96b38 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7fc489a99d70 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7fc489a9cd0b in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7fc489805b50 in start_thread (arg=) at pthread_create.c:304 #11 0x7fc487911a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 1 (Thread 0x7fc4780b6780 (LWP 19301)): [KCrash Handler] #6 0x7fc487869475 in *__GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7fc48786c6f0 in *__GI_abort () at abort.c:92 #8 0x7fc489a92722 in qt_message_output(QtMsgType, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7fc489a92a98 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #10 0x7fc489a92c24 in qFatal(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7fc46cc59a5c in IncidenceEditorNG::CombinedIncidenceEditor::load (this=0x3f68280, incidence=...) at /media/kdesvn/kde4svn/src/kdepim/incidenceeditor-ng/combinedincidenceeditor.cpp:108 #12 0x7fc46cc9e1d7 in IncidenceEditorNG::EventOrTodoDialogPrivate::load (this=0x3f5ae00, item=...) at /media/kdesvn/kde4svn/src/kdepim/incidenceeditor-ng/eventortododialog.cpp:532 #13 0x7fc46cc5665b in IncidenceEditorNG::EditorItemManager::load (this=0x3f68440, item=...) at /media/kdesvn/kde4svn/src/kdepim/incidenceeditor-ng/editoritemmanager.cpp:282 #14 0x7fc46cc9f630 in IncidenceEditorNG::EventOrTodoDialog::load (this=0x45fde30, item=..., activeDate=...) at /media/kdesvn/kde4svn/src/kdepim/incidenceeditor-ng/eventortododialog.cpp:693 #15 0x7fc46da2335f in CalendarView::editIncidence (this=0x2d62ee0, item=..., isCounter=false) at /media/kdesvn/kde4svn/src/kdepim/korganizer/calendarview.cpp:2524 #16 0x7fc46da282fe in CalendarView::qt_static_metacall (_o=0x2d62ee0, _c=QMetaObject::InvokeMetaMethod, _id=50, _a=0x7fff00621640) at /media/kdesvn/kde4svn/build/kdepim/korganizer/calendarview.moc:439 #17 0x7fc489bad54f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #18 0x7fc46c548957 in KOrg::BaseView::editIncidenceSignal (this=0x2f24a60, _t1=...) at /media/kdesvn/kde4svn/build/kdepim/korganizer/interfaces/korganizer/baseview.moc:202 #19 0x7fc46c548379 in KOrg::BaseView::qt_static_metacall (_o=0x2f24a60, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7fff006217d0) at /media/kdesvn/kde4svn/build/kdepim/korganizer/interfaces/korganizer/baseview.moc:110 #20 0x7fc489bad54f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from
[Bug 312089] Cannot create a new event in a google calendar
https://bugs.kde.org/show_bug.cgi?id=312089 --- Comment #2 from Dan Vrátil --- What version of LibKGAPI do you have? Please make sure you have updated to the latest (0.4.4) version. -- 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 310899] Resource KMail Folders is broken. This resource is now online
https://bugs.kde.org/show_bug.cgi?id=310899 --- Comment #4 from Neil --- Near as i can tell kmail2 with mboxes is a time bomb. Eventually the size of the mbox gets too big for the new infrastructure to handle and people will start getting failures. I've done a fair bit of testing and can't find a consistent threshold for when problems start but the problems always start eventually. I've mostly had success up to about 500 messages in one file but sometimes I can get up to 1000 messages before the error messages start (and sometimes the flakiness happens before 500). It might be more dependant on the size of the file (attachments, etc) rather than the number of messages. Seems the new infrastructure is WAY too precariously balanced and it's easy for a big mbox file to bring the whole house of cards down. The numerous layers of complexity also make troubleshooting real difficult if not impossible. I'm using a 500G spinning disk on a Core2 Quad 3.2Ghz machine with 4 gigs of RAM. I haven't tested on an SSD drive but I suspect a SSD will handle more messages before the failures start but the failures will still happen eventually. Best bet seems to be considering MBOXes unsupported under the new infrastructure and either convert all your folders to Maildirs or switch to something like Thunderbird or Claws that handle large mbox folders reliably. Kmail2 is definitely a step backwards. -- 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 312089] Cannot create a new event in a google calendar
https://bugs.kde.org/show_bug.cgi?id=312089 Yuriy Vidineev changed: What|Removed |Added CC||adeptsm...@gmail.com --- Comment #1 from Yuriy Vidineev --- I can confirm this bug in Kubuntu 13.04 (KDE 4.9.95). I can't create new event or edit existed one. Looks like calendar in read-only mode -- 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 293271] KMail doesn't remember the SMTP password
https://bugs.kde.org/show_bug.cgi?id=293271 David Faure changed: What|Removed |Added CC||fa...@kde.org --- Comment #42 from David Faure --- Patch under review: https://git.reviewboard.kde.org/r/107885/ -- 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 311722] Kontact crashed upon launch
https://bugs.kde.org/show_bug.cgi?id=311722 Allen Winter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.9.5 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/788bb67808c873d460ac47a7 ||9c7144f7eb3bd9e5 --- Comment #3 from Allen Winter --- Git commit 788bb67808c873d460ac47a79c7144f7eb3bd9e5 by Allen Winter. Committed on 23/12/2012 at 17:24. Pushed by winterz into branch 'KDE/4.9'. don't crash if the navigatorToolBar can't be found in the kontactui.rc (probably because kontactui.rc can't be located.) instead, print a kError() and just continue without a toolbar. FIXED-IN: 4.9.5 MERGE: 4.10, master M +9-6kontact/src/mainwindow.cpp http://commits.kde.org/kdepim/788bb67808c873d460ac47a79c7144f7eb3bd9e5 -- 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 312089] Cannot create a new event in a google calendar
https://bugs.kde.org/show_bug.cgi?id=312089 Sergio Martins changed: What|Removed |Added CC||iamser...@gmail.com, ||kdepim-bugs@kde.org Component|general |Google Resource Assignee|korganizer-de...@kde.org|dvra...@redhat.com Product|korganizer |Akonadi -- 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 312114] New: Crash while adding a folder in Kmail
https://bugs.kde.org/show_bug.cgi?id=312114 Bug ID: 312114 Summary: Crash while adding a folder in Kmail Classification: Unclassified Product: kontact Version: 4.9.3 Hardware: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: waterfront5...@gmail.com Application: kontact (4.9.3) KDE Platform Version: 4.9.3 Qt Version: 4.8.3 Operating System: Linux 3.5.0-19-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: - What I was doing when the application crashed: I right-clicked on my Google IMAP mailbox in the sidepane and selected 'Add folder', then typed the name of my new folder. When I clicked 'OK', Kontact crashed. The behaviour does not seem to be systematic: this is the first time I notice this, and I've added folders like this before. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff390ce97c0 (LWP 1721))] Thread 4 (Thread 0x7ff3898af700 (LWP 1723)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7ff3a225fb2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7ff3a225fc39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7ff39d7aae9a in start_thread (arg=0x7ff3898af700) at pthread_create.c:308 #4 0x7ff3a2f8acbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7ff3890ae700 (LWP 1724)): #0 0x7ff39d318c31 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff39d2db623 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff39d2dbcab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff39d2dbea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff3a36ffc16 in QEventDispatcherGlib::processEvents (this=0x7ff3840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7ff3a36d02bf in QEventLoop::processEvents (this=this@entry=0x7ff3890addc0, flags=...) at kernel/qeventloop.cpp:149 #6 0x7ff3a36d0548 in QEventLoop::exec (this=0x7ff3890addc0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7ff3a35d1b10 in QThread::exec (this=) at thread/qthread.cpp:501 #8 0x7ff3a35d4aec in QThreadPrivate::start (arg=0x1bca1f0) at thread/qthread_unix.cpp:338 #9 0x7ff39d7aae9a in start_thread (arg=0x7ff3890ae700) at pthread_create.c:308 #10 0x7ff3a2f8acbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7ff33b2b7700 (LWP 2035)): #0 0x7fff5cdff827 in clock_gettime () #1 0x7ff39bb0d15d in __GI_clock_gettime (clock_id=, tp=) at ../sysdeps/unix/clock_gettime.c:116 #2 0x7ff3a362a9c4 in do_gettime (frac=0x7ff33b2b6ae8, sec=0x7ff33b2b6ae0) at tools/qelapsedtimer_unix.cpp:123 #3 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #4 0x7ff3a370041d in QTimerInfoList::updateCurrentTime (this=this@entry=0x7ff334002660) at kernel/qeventdispatcher_unix.cpp:343 #5 0x7ff3a3700763 in QTimerInfoList::timerWait (this=0x7ff334002660, tm=...) at kernel/qeventdispatcher_unix.cpp:450 #6 0x7ff3a36ff2cc in timerSourcePrepareHelper (src=, timeout=0x7ff33b2b6bd4) at kernel/qeventdispatcher_glib.cpp:136 #7 0x7ff3a36ff375 in timerSourcePrepare (source=, timeout=) at kernel/qeventdispatcher_glib.cpp:169 #8 0x7ff39d2db618 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7ff39d2dbcab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7ff39d2dbea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7ff3a36ffc16 in QEventDispatcherGlib::processEvents (this=0x7ff3340008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #12 0x7ff3a36d02bf in QEventLoop::processEvents (this=this@entry=0x7ff33b2b6d90, flags=...) at kernel/qeventloop.cpp:149 #13 0x7ff3a36d0548 in QEventLoop::exec (this=0x7ff33b2b6d90, flags=...) at kernel/qeventloop.cpp:204 #14 0x7ff3a35d1b10 in QThread::exec (this=) at thread/qthread.cpp:501 #15 0x7ff3a36b09af in QInotifyFileSystemWatcherEngine::run (this=0x21b9910) at io/qfilesystemwatcher_inotify.cpp:248 #16 0x7ff3a35d4aec in QThreadPrivate::start (arg=0x21b9910) at thread/qthread_unix.cpp:338 #17 0x7ff39d7aae9a in start_thread (arg=0x7ff33b2b7700) at pthread_create.c:308 #18 0x7ff3a2f8acbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #19 0x in ?? () Thread 1 (Thread 0x7ff390ce97c0 (LWP 1721)): [KCrash Handler] #6 QSortFilterProxyModelPrivate::updateChildrenMapping (this=this@entry=0x3570580, source_parent=..., parent_mapping=parent_
[Bug 310735] Kontact crash while switching virtual desktops
https://bugs.kde.org/show_bug.cgi?id=310735 Christophe Giboudeaux changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Christophe Giboudeaux --- Webkit crash. Also crashes in rekonq. Please report this issue to the webkit bug tracker. See http://trac.webkit.org/wiki/QtWebKitBugs for the details. -- 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
