[kdepim] [Bug 312841] 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 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||4.11 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/0e88ca01e9a4fea9d14e6140 ||a6b87e77ace6f541 --- Comment #1 from Laurent Montel mon...@kde.org --- Git commit 0e88ca01e9a4fea9d14e6140a6b87e77ace6f541 by Montel Laurent. Committed on 08/01/2013 at 09:57. Pushed by mlaurent into branch 'master'. fix Bug 312841 - importwizard.desktop use Name=Import Wizard, which is a quite generic name and does not give users much hint. FIXED-IN: 4.11 M +1-1importwizard/importwizard.desktop http://commits.kde.org/kdepim/0e88ca01e9a4fea9d14e6140a6b87e77ace6f541 -- 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] 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 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org -- 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] Nepomuk Feeder does not recognise removal of the important flag
https://bugs.kde.org/show_bug.cgi?id=312847 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org Assignee|kdepim-bugs@kde.org |chrig...@fastmail.fm --- Comment #2 from Laurent Montel mon...@kde.org --- I confirm there is a problem. When I set important tag is not set. -- 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 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #3 from Laurent Montel mon...@kde.org --- Which application send this email ? I confirm that it shows only one 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] Email with two To: shows only first one in the list
https://bugs.kde.org/show_bug.cgi?id=312837 --- Comment #4 from Laurent Montel mon...@kde.org --- Thunderbird shows it correctly. -- 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 #5 from Albert Astals Cid aa...@kde.org --- The mbox file says ;-) User-Agent: trojita/v0.3-1275-g499e9a4-dirty; Qt/4.8.4; X11; Linux; Do you think this is a format break by the sender? -- 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 #6 from Laurent Montel mon...@kde.org --- by default it's better to add all To in same line. But as thunderbird supports it we must support it, but we need to hack kmime to support search multi headers... don't know if it's possible. I hope but it will better that Trojita put all To/Cc/Bcc in same line and not create multi headers. -- 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 264383] akonadiserver uses ~/.my.cnf dangerously
https://bugs.kde.org/show_bug.cgi?id=264383 --- Comment #8 from Simon Williams si...@systemparadox.co.uk --- The severity of this bug MUST be upgraded to CRITICAL. This is not just a crash. 1. It affects other programs 2. It crashes other programs 3. It risks corrupting data 4. It risks corrupting data of other programs 5. It risks corrupting data on other machines -- 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 308122] After some weeks downtime, google calendar fetch fails. The requested minimum modification time lies too far in the past
https://bugs.kde.org/show_bug.cgi?id=308122 Dan Vrátil dvra...@redhat.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Dan Vrátil dvra...@redhat.com --- Confirmed, Calendar API allows to fetch only items changed within approximately last 25 days. When trying to request list of changes from deeper in the history, the API will return this error. Solution is probably to use timeMin argument when last update was more then 20 (?) days ago and fetch all events with dtStart=timeMin. Using lastUpdated date, we can filter out events that were not changed between timeMin and now and use itemsRetrievedIncremental(). -- 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 312873] New: Akonadi crash when adding new Calendar
https://bugs.kde.org/show_bug.cgi?id=312873 Bug ID: 312873 Summary: Akonadi crash when adding new Calendar Classification: Unclassified Product: Akonadi Version: 4.9 Hardware: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: KResource compat bridges Assignee: kram...@kde.org Reporter: ema...@stealthassassin.net CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_kcal_resource (4.9) KDE Platform Version: 4.9.3 Qt Version: 4.8.3 Operating System: Linux 3.5.0-21-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: Every time I add a new calendar, Akonadi crash. When I am accessing to a calendar event update email, Akonadi crash also. The crash can be reproduced every time. -- Backtrace: Application: Test Calendrier de type Calendrier KDE (traditionnel) (akonadi_kcal_resource), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7ffa081ac780 (LWP 9572))] Thread 3 (Thread 0x7ff9ed369700 (LWP 9574)): #0 0x7ffa04fc2303 in __GI___poll (fds=optimized out, nfds=optimized out, timeout=optimized out) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7ffa03250d84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa03250ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa07637c16 in QEventDispatcherGlib::processEvents (this=0x7ff9e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7ffa076082bf in QEventLoop::processEvents (this=this@entry=0x7ff9ed368dd0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7ffa07608548 in QEventLoop::exec (this=0x7ff9ed368dd0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7ffa07509b10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7ffa075e89af in QInotifyFileSystemWatcherEngine::run (this=0x2b1ff30) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7ffa0750caec in QThreadPrivate::start (arg=0x2b1ff30) at thread/qthread_unix.cpp:338 #9 0x7ffa03b2be9a in start_thread (arg=0x7ff9ed369700) at pthread_create.c:308 #10 0x7ffa04fcdcbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 2 (Thread 0x7ff9e7fff700 (LWP 9575)): #0 0x7ffa03b2dfc0 in __pthread_mutex_lock (mutex=0x7ff9ea60) at pthread_mutex_lock.c:113 #1 0x7ffa0328de21 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ffa03250d6a in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ffa03250ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ffa07637c16 in QEventDispatcherGlib::processEvents (this=0x7ff9e8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x7ffa076082bf in QEventLoop::processEvents (this=this@entry=0x7ff9e7ffedd0, flags=...) at kernel/qeventloop.cpp:149 #6 0x7ffa07608548 in QEventLoop::exec (this=0x7ff9e7ffedd0, flags=...) at kernel/qeventloop.cpp:204 #7 0x7ffa07509b10 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #8 0x7ffa075e89af in QInotifyFileSystemWatcherEngine::run (this=0x2c29340) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x7ffa0750caec in QThreadPrivate::start (arg=0x2c29340) at thread/qthread_unix.cpp:338 #10 0x7ffa03b2be9a in start_thread (arg=0x7ff9e7fff700) at pthread_create.c:308 #11 0x7ffa04fcdcbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 1 (Thread 0x7ffa081ac780 (LWP 9572)): [KCrash Handler] #6 begin (this=0x7365746f6e2e660c) at /usr/include/qt4/QtCore/qlist.h:101 #7 contains (t=@0x7fff4b32ec78: 0x2bdacd0, this=0x7365746f6e2e660c) at /usr/include/qt4/QtCore/qlist.h:882 #8 removeRef (t=0x2bdacd0, this=0x7365746f6e2e660c) at ../../kcal/listbase.h:118 #9 KCal::Incidence::removeRelation (this=0x2e03dc0, incidence=0x2bdacd0) at ../../kcal/incidence.cpp:535 #10 0x7ffa06d13ea7 in KCal::Incidence::~Incidence (this=0x2bdacd0, __in_chrg=optimized out) at ../../kcal/incidence.cpp:207 #11 0x7ffa06d17a39 in KCal::Todo::~Todo (this=0x2bdacd0, __in_chrg=optimized out) at ../../kcal/todo.cpp:105 #12 0x00412269 in release (this=0x29e1240) at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:145 #13 ~shared_count (this=0x280f380, __in_chrg=optimized out) at /usr/include/boost/smart_ptr/detail/shared_count.hpp:305 #14 ~shared_ptr (this=0x280f378, __in_chrg=optimized out) at /usr/include/boost/smart_ptr/shared_ptr.hpp:164 #15 ~Payload (this=0x280f370, __in_chrg=optimized out) at /usr/include/akonadi/itempayloadinternals_p.h:285 #16 Akonadi::Payloadboost::shared_ptrKCal::Incidence ::~Payload (this=0x280f370, __in_chrg=optimized out) at /usr/include/akonadi/itempayloadinternals_p.h:285 #17 0x7ffa07c7fd26 in
[Akonadi] [Bug 312873] Akonadi crash when adding new Calendar
https://bugs.kde.org/show_bug.cgi?id=312873 --- Comment #1 from Kevin Krammer kram...@kde.org --- Thank you for your report. Is your goal a calendar in a local ics file? If yes I recommend you use the ical resource instead. It has been written for exactly that purpose and does not have to go through the KDE legacy infrastructure (like the kcal resource that is crashing here) -- 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 312687] kmail stalls when working with imap servers after upgrading akonadi to 1.8.80 or 1.9.0
https://bugs.kde.org/show_bug.cgi?id=312687 Sebastian Wessalowski sebast...@wessalowski.org changed: What|Removed |Added CC||sebast...@wessalowski.org --- Comment #1 from Sebastian Wessalowski sebast...@wessalowski.org --- I can confirm this. After upgrading to KDE 4.10 RC2 akonadi stopped working. Its not possible to provide any logs because of the complete lockup of akonadi. It just stops working when opening any mail account. Distro is Gentoo ~amd64 KDE ist 4.10 RC2 compiled from kde overlay. -- 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 287984] Native MAPI support for all kontact components
https://bugs.kde.org/show_bug.cgi?id=287984 --- Comment #3 from Olivier LAHAYE olivier.laha...@free.fr --- This is not a duplicate of bug 227672. Bug 227672 only deals with mail support while this bug deals with ALL kontact components (calendare, notes, contacts, ...) Marking 227672 as redundant of this bug whould have been the solution. Anyway, it has been to yeas now that I have abandoned kmail completely as there is no exchange support (calendars, shared calendars, and mail), and I have no C++ skills to do it myself :-( -- 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 312873] Akonadi crash when adding new Calendar
https://bugs.kde.org/show_bug.cgi?id=312873 --- Comment #2 from Jean-Christophe ema...@stealthassassin.net --- I tried to choose an ical resource : same problem, Akonadi crash. -- 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 312873] Akonadi crash when adding new Calendar
https://bugs.kde.org/show_bug.cgi?id=312873 --- Comment #3 from Kevin Krammer kram...@kde.org --- Can you attach a crash report for that as well? Would make much more sense to put the limited resources into fixing the main resource. -- 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 264383] akonadiserver uses ~/.my.cnf dangerously
https://bugs.kde.org/show_bug.cgi?id=264383 --- Comment #9 from Christophe Giboudeaux cgiboude...@gmx.com --- To clarify things. Please correct if anything is incorrect AFAIU the mysql doc, the my.cnf files are ignored if --defaults-file is used. That's the case for the mysqld process launched by the akonadi server: ps x |grep mysqld returns /usr/sbin/mysqld --defaults-file=$HOME/.local/share/akonadi/mysql.conf --datadir=$HOME/.local/share/akonadi/db_data/ --socket=$HOME/.local/share/akonadi/socket-yuuko.site/mysql.socket Now, when starting up, Akonadi also runs mysqlcheck --check-upgrade --all-databases --auto-repair --socket=$HOME/.local/share/akonadi/socket-$HOST/mysql.socket would adding --defaults-file help you? ie mysqlcheck --defaults-file=$HOME/.local/share/akonadi/mysql.conf --check-upgrade --all-databases --auto-repair --socket=$HOME/.local/share/akonadi/socket-$HOST/mysql.socket -- 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 187217] Column order is not remembered between sessions when having used drag and drop
https://bugs.kde.org/show_bug.cgi?id=187217 Matthew Taft matthewet...@gmail.com changed: What|Removed |Added CC||matthewet...@gmail.com --- Comment #16 from Matthew Taft matthewet...@gmail.com --- Using Kontact Version 4.4.11, KMail Version 1.13.7. Issue persists. This has been going on for years now with no apparent serious attention given to it. As has been asked before, is there a temporary fix we can make in some configuration file, or can we get an update on whether this is going to be looked at soon? -- 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 312880] Plasma keeps crashing due to exception from akonadi
https://bugs.kde.org/show_bug.cgi?id=312880 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Component|general |general Version|unspecified |4.9 Assignee|plasma-b...@kde.org |kdepim-bugs@kde.org Product|plasma |Akonadi -- 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 312873] Akonadi crash when adding new Calendar
https://bugs.kde.org/show_bug.cgi?id=312873 --- Comment #4 from Jean-Christophe ema...@stealthassassin.net --- Created attachment 76307 -- https://bugs.kde.org/attachment.cgi?id=76307action=edit crash report when creating ical resource -- 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 312873] Akonadi crash when adding new Calendar
https://bugs.kde.org/show_bug.cgi?id=312873 --- Comment #5 from Kevin Krammer kram...@kde.org --- This is still a Traditional KDE Calendar Agenda Local de type Calendrier KDE (traditionnel) (akonadi_kcal_resource) The one I was suggesting is called ICal Calendar File, in french Fichier d'agenda au format ICal -- 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 187217] Column order is not remembered between sessions when having used drag and drop
https://bugs.kde.org/show_bug.cgi?id=187217 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #17 from Laurent Montel mon...@kde.org --- 4.4.11 is obsolete. We never fix it in 4.4.11 I worked on 4.10 to fixing it but not perfect 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 312880] Plasma keeps crashing due to exception from akonadi
https://bugs.kde.org/show_bug.cgi?id=312880 davidebasilio marsicanb...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from davidebasilio marsicanb...@gmail.com --- UPDATE: The problem seems to be related to using akonadi google applets plasmoids: the crashes disappear when deleting those plasmoids. Marking as invalid; will reopen in case of need. Sorry for the mess. (In reply to comment #0) Application: plasma-desktop (0.4) KDE Platform Version: 4.9.5 (Compiled from sources) Qt Version: 4.8.4 Operating System: Linux 3.6.11-gentoo x86_64 Distribution: Gentoo Base System release 2.1 -- Information about the crash: After updating PyQt4 to version 4.9.6 and rebuilding pykde4 4.9.5 I get crashes every time I start plasma; the source of the problem seems to be an exception from akonadi: terminate called after throwing an instance of 'Akonadi::PayloadException' what(): Akonadi::PayloadException: No payload set The crash can be reproduced every time. -- Backtrace: Application: Shell del desktop di Plasma (plasma-desktop), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f70d4184780 (LWP 4215))] Thread 3 (Thread 0x7f70afd7c700 (LWP 4468)): #0 0x7f70d024059c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f70cd3edbd4 in ?? () from /usr/lib64/qt4/libQtScript.so.4 #2 0x7f70cd3edc09 in ?? () from /usr/lib64/qt4/libQtScript.so.4 #3 0x7f70d023bd96 in start_thread () from /lib64/libpthread.so.0 #4 0x7f70d3a9442d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f70aab6a700 (LWP 4633)): #0 0x7f70d3a8b663 in poll () from /lib64/libc.so.6 #1 0x7f70c73456d6 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f70c73457f4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f70d0604966 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x7f70d05d4292 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x7f70d05d4545 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7f70d04cfd48 in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7f70d05b2d38 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #8 0x7f70d04d2406 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #9 0x7f70d023bd96 in start_thread () from /lib64/libpthread.so.0 #10 0x7f70d3a9442d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f70d4184780 (LWP 4215)): [KCrash Handler] #6 0x7f70d39dea65 in raise () from /lib64/libc.so.6 #7 0x7f70d39dfd65 in abort () from /lib64/libc.so.6 #8 0x7f70cf32576d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #9 0x7f70cf3239a6 in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #10 0x7f70cf3239d3 in std::terminate() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #11 0x7f70cf323b25 in __cxa_rethrow () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/libstdc++.so.6 #12 0x7f70d05d4749 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/qt4/libQtCore.so.4 #13 0x7f70d05d8f9b in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #14 0x7f70d3d9094d in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so #15 0x7f70d39cb4bd in __libc_start_main () from /lib64/libc.so.6 #16 0x004007a9 in _start () Possible duplicates by query: bug 312866, bug 312814, bug 312735, bug 312697, bug 312677. Reported using DrKonqi -- 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 312873] Akonadi crash when adding new Calendar
https://bugs.kde.org/show_bug.cgi?id=312873 --- Comment #6 from Jean-Christophe ema...@stealthassassin.net --- Strange, I chose Fichier d'agenda au format ICal :s I retried, after deleted all calendar, restart Kontact and Akonadi. No crash after created Ical. kcal resource was crashing all other resources. -- 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 264383] akonadiserver uses ~/.my.cnf dangerously
https://bugs.kde.org/show_bug.cgi?id=264383 --- Comment #10 from Simon Williams si...@systemparadox.co.uk --- That is indeed the case for the mysqld process launched by Akonadi. But to be extra clear, this only applies to the *SERVER* process. The whole point of this bug is that Akonadi isn't using it's own server process because any *CLIENT* connections it creates are incorrectly reading ~/.my.cnf. I suspect that --defaults-file should fix the problem. However, this bug is NOT specific to mysqlcheck. *ALL* client processes must use --defaults-file *WITHOUT FAIL* in order to solve this problem. Please be aware that if Akonadi access the database in any other manner (for example, using libmysqlclient directly) that will also have to be guaranteed to not use ~/.my.cnf. -- 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 264383] akonadiserver uses ~/.my.cnf dangerously
https://bugs.kde.org/show_bug.cgi?id=264383 --- Comment #11 from Christophe Giboudeaux cgiboude...@gmx.com --- Created attachment 76312 -- https://bugs.kde.org/attachment.cgi?id=76312action=edit test patch If anyone is willing to test, please apply this patch to the akonadi server source, build, install then run akonadictl restart and look at the output A normal one should be: Found mysqlcheck: /usr/bin/mysqlcheck akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontableOK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.pimitemflagrelationOK akonadi.pimitemtable OK akonadi.resourcetable OK akonadi.schemaversiontable OK mysql.columns_priv OK mysql.db OK mysql.eventOK mysql.func OK mysql.general_log OK mysql.help_categoryOK mysql.help_keyword OK mysql.help_relationOK mysql.help_topic OK mysql.host OK mysql.ndb_binlog_index OK mysql.plugin OK mysql.proc OK mysql.procs_priv OK mysql.proxies_priv OK mysql.servers OK mysql.slow_log OK mysql.tables_priv OK mysql.time_zoneOK mysql.time_zone_leap_secondOK mysql.time_zone_name OK mysql.time_zone_transition OK mysql.time_zone_transition_typeOK mysql.user OK If that's still not enough, I have other ideas -- 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 312089] Cannot create a new event in a google calendar
https://bugs.kde.org/show_bug.cgi?id=312089 lnx...@westlot.net changed: What|Removed |Added CC||lnx...@westlot.net --- Comment #7 from lnx...@westlot.net --- Sorry, this is not fixed. I have kdepim-runtime 4.9.97 (4.10 rc2) with libkgapi0 0.4.4 and I cannot add new or edit existing google calendar events. -- 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 312813] akonadi_nepomuk_feeder sucks memory (1.5 GB reserved memory at this time)
https://bugs.kde.org/show_bug.cgi?id=312813 Hans-Peter Jansen h...@urpla.net changed: What|Removed |Added Summary|akonadi_nepomuk_feeder |akonadi_nepomuk_feeder |sucks memory (~!.5 GB |sucks memory (1.5 GB |reserved memory at this |reserved memory at this |time) |time) --- Comment #1 from Hans-Peter Jansen h...@urpla.net --- Interestingly, after akonadictl start, it takes 3 cpu seconds for akonadi_nepomuk_feeder to reserve 1.6 GB ram now: hp7931 12.9 19.7 1897084 1616672 ? S20:51 0:03 /usr/bin/akonadi_nepomuk_feeder Hmm. -- 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 304647] CardDav data loss
https://bugs.kde.org/show_bug.cgi?id=304647 Daniel Laidig lai...@kde.org changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED CC||lai...@kde.org Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #2 from Daniel Laidig lai...@kde.org --- I can confirm this bug (or at least something very similar) with KDE 4.9.4. To reproduce this bug, try adding the attached .vcf as a VCF File address book and copy the contact to the ownCloud address book. The vcf contains a custom entry that contains an underscore which is not allowed in the vcf specification. Kontact seems to ignore this, ownCloud returns an error. After copying the contact to the ownCloud address book it is added to the cache and shows up just fine in KAddressBook for a while. There user does not get any error message at all and probably won't notice the loss of data until it's way too late... Akonadi Console shows: AgentBase(akonadi_davgroupware_resource_0): Unable to add item: There was a problem with the request. The item has not been created on the server. An unexpected error (415) occurred while attempting to upload https://[url]/apps/contacts/carddav.php/addressbooks/dani/archiv/uNQJBXZthD.vcf. (415). It's probably hard to prevent this error in all cases in the first place (and I've also been getting some strange 412 errors that I can't reproduce) but at least the error should be handled in a way that won't lead to unnoticed data loss. -- 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 304647] CardDav data loss
https://bugs.kde.org/show_bug.cgi?id=304647 --- Comment #3 from Daniel Laidig lai...@kde.org --- Created attachment 76321 -- https://bugs.kde.org/attachment.cgi?id=76321action=edit vcf to reproduce the 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
[Akonadi] [Bug 312917] New: A message was received from the server with no job to handle it: * BYE Too many invalid IMAP commands.
https://bugs.kde.org/show_bug.cgi?id=312917 Bug ID: 312917 Summary: A message was received from the server with no job to handle it: * BYE Too many invalid IMAP commands. Classification: Unclassified Product: Akonadi Version: 1.9.0 Hardware: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: er...@kde.org Reporter: devuran...@gmx.net CC: kdepim-bugs@kde.org, vkra...@kde.org I get several of these over time, when starting Akonadi on the console (akonadictl restart): A message was received from the server with no job to handle it: * BYE Too many invalid IMAP commands. (SOME-HASH) SOME-HASH is always the same hash for all of them. Does Akonadi log BAD IMAP responses (and the corresponding command) somewhere? -- 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 312917] A message was received from the server with no job to handle it: * BYE Too many invalid IMAP commands.
https://bugs.kde.org/show_bug.cgi?id=312917 --- Comment #1 from Christophe Giboudeaux cgiboude...@gmx.com --- (In reply to comment #0) Does Akonadi log BAD IMAP responses (and the corresponding command) somewhere? Check http://techbase.kde.org/Projects/PIM/Akonadi/Debug_IMAP -- 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 259813] reading mails in unread mode instantly disappears from list
https://bugs.kde.org/show_bug.cgi?id=259813 Arthur Titeica arthur.tite...@gmail.com changed: What|Removed |Added CC||arthur.tite...@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
[kmail2] [Bug 312696] filters: folder to move mail to, path is blank
https://bugs.kde.org/show_bug.cgi?id=312696 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- Screenshot ? settings config please. -- 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 312923] New: Server side errors not visualized when managing sieve scripts
https://bugs.kde.org/show_bug.cgi?id=312923 Bug ID: 312923 Summary: Server side errors not visualized when managing sieve scripts Classification: Unclassified Product: kmail2 Version: 4.9.5 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: sieve Assignee: kdepim-bugs@kde.org Reporter: f...@christian-reiner.info I just found out about the reason a problem I faced for several weeks: When managing my personal sieve scripts using kmail2s interface I always got a Error unknown whatever I tried. Managing the scripts had worked before, actually I setup the scripts using kmail2s interface. I failed to find out what the actual problem is. Today I finally used 'sieveshell' to give it another try and was presented a clear and easy to understand error, when trying to upload a modified script: you are only allowed to setup 5 scripts. Wow. Ok, that is something that actually helps! 1.) I know what the problem is 2.) is was a question of seconds to fix the problem 3.) I was able to manage my scripts again So my question is: why does kmail2 not display that error message? Why the Error unknown? Reproducible: Always Steps to Reproduce: 1. Use a cyrus imap account and maintain sieve scripts, more than are actually allowed on the server 2. Try to make _any_ modifications to the existing sieve scripts using kmail2s script manager 3. Shake your head at the great error message you get Actual Results: I get a meaningless error message: Error unknown for whatever modification I try, except activating a script or another. Expected Results: I would expect to get the error message the server generates. This is what error messages are there for. It actually sometimes helps users to give them the error message. -- 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
