[knotes] [Bug 338687] Number of notes displayed in the system tray by default
https://bugs.kde.org/show_bug.cgi?id=338687 Laurent Montel mon...@kde.org changed: What|Removed |Added Version Fixed In||4.14.1 Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kdep ||im/678001e719a882d25e981a68 ||caad7e4b78035f27 Resolution|--- |FIXED --- Comment #1 from Laurent Montel mon...@kde.org --- Git commit 678001e719a882d25e981a68caad7e4b78035f27 by Montel Laurent. Committed on 31/08/2014 at 06:06. Pushed by mlaurent into branch 'KDE/4.14'. Fix Bug 338687 - Number of notes displayed in the system tray by default FIXED-IN: 4.14.1 M +1-1knotes/apps/knotesapp.cpp M +0-1knotes/configdialog/knoteconfigdialog.cpp M +0-2knotes/configdialog/knoteconfigdialog.h M +1-1kontact/plugins/knotes/knotes_part.cpp http://commits.kde.org/kdepim/678001e719a882d25e981a68caad7e4b78035f27 -- 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
[knotes] [Bug 338687] Number of notes displayed in the system tray by default
https://bugs.kde.org/show_bug.cgi?id=338687 Laurent Montel mon...@kde.org changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im/678001e719a882d25e981a68 |im/31d995ec7948af20760b7e75 |caad7e4b78035f27|d55bba7e5dc4c935 --- Comment #2 from Laurent Montel mon...@kde.org --- Git commit 31d995ec7948af20760b7e75d55bba7e5dc4c935 by Montel Laurent. Committed on 31/08/2014 at 06:07. Pushed by mlaurent into branch 'KDE/4.14'. Fix Bug 338687 - Number of notes displayed in the system tray by default FIXED-IN: 4.14.1 M +1-1knotes/settings/knotesglobalconfig.kcfg.cmake http://commits.kde.org/kdepim/31d995ec7948af20760b7e75d55bba7e5dc4c935 -- 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 338672] Can't create folder on IMAP server
https://bugs.kde.org/show_bug.cgi?id=338672 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #3 from Laurent Montel mon...@kde.org --- 4.10.5 is very old. Did you test in new version. I remember that it was fixed . -- 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 338656] KMail-4.14 always wants a confirmation before sending of a message
https://bugs.kde.org/show_bug.cgi?id=338656 Laurent Montel mon...@kde.org changed: What|Removed |Added Resolution|--- |FIXED CC||mon...@kde.org Status|UNCONFIRMED |RESOLVED Version Fixed In||4.14.1 --- Comment #1 from Laurent Montel mon...@kde.org --- Fixed in 4.14.1 -- 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 338692] New: crash on close
https://bugs.kde.org/show_bug.cgi?id=338692 Bug ID: 338692 Summary: crash on close Product: akregator Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: criss...@gmx.de Application: akregator (4.14) KDE Platform Version: 4.14.0 Qt Version: 4.8.6 Operating System: Linux 3.13.0-35-generic x86_64 Distribution: Ubuntu 14.04.1 LTS -- Information about the crash: I ran akregator for a while and open some articles using the webkit part. Then I close the application and it crashed. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f9ce3324800 (LWP 7979))] Thread 4 (Thread 0x7f9cbcd3d700 (LWP 7980)): #0 update_get_addr (ti=0x7f9ce1abba50) at dl-tls.c:758 #1 0x7f9ce1653044 in get_thread_data () at thread/qthread_unix.cpp:188 #2 QThreadData::current () at thread/qthread_unix.cpp:219 #3 0x7f9ce1783af5 in postEventSourcePrepare (s=0x7f9cb8001350, timeout=0x7f9cbcd3cbe4) at kernel/qeventdispatcher_glib.cpp:263 #4 0x7f9cda9d668d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f9cda9d6f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f9cda9d70ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f9ce17837be in QEventDispatcherGlib::processEvents (this=0x7f9cb80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436 #8 0x7f9ce17550af in QEventLoop::processEvents (this=this@entry=0x7f9cbcd3cda0, flags=...) at kernel/qeventloop.cpp:149 #9 0x7f9ce17553a5 in QEventLoop::exec (this=this@entry=0x7f9cbcd3cda0, flags=...) at kernel/qeventloop.cpp:204 #10 0x7f9ce1651c5f in QThread::exec (this=this@entry=0x1030f30) at thread/qthread.cpp:537 #11 0x7f9ce1736823 in QInotifyFileSystemWatcherEngine::run (this=0x1030f30) at io/qfilesystemwatcher_inotify.cpp:265 #12 0x7f9ce165432f in QThreadPrivate::start (arg=0x1030f30) at thread/qthread_unix.cpp:349 #13 0x7f9cdb0a7182 in start_thread (arg=0x7f9cbcd3d700) at pthread_create.c:312 #14 0x7f9cdfec5fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f9cb6ea3700 (LWP 8074)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9cc589a81d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f9cc589a859 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f9cdb0a7182 in start_thread (arg=0x7f9cb6ea3700) at pthread_create.c:312 #4 0x7f9cdfec5fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f9cb4ada700 (LWP 8076)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f9cc55db20d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f9cc58c9fd6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f9cdb0a7182 in start_thread (arg=0x7f9cb4ada700) at pthread_create.c:312 #4 0x7f9cdfec5fbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f9ce3324800 (LWP 7979)): [KCrash Handler] #6 0x7f9ce176a607 in isSignalConnected (signal_index=7, this=0x9) at kernel/qobject_p.h:237 #7 QMetaObject::activate (sender=0xf40800, m=m@entry=0x7f9ce2a33760 Akregator::Frame::staticMetaObject, local_signal_index=local_signal_index@entry=4, argv=argv@entry=0x7fff95c89160) at kernel/qobject.cpp:3444 #8 0x7f9ce281a782 in Akregator::Frame::signalCompleted (this=optimized out, _t1=0xf40800) at moc_frame.cpp:200 #9 0x7f9ce28115b8 in Akregator::Frame::slotSetState (this=optimized out, state=state@entry=Akregator::Frame::Completed) at ../../../akregator/src/frame.cpp:94 #10 0x7f9cc7d471f7 in Akregator::MainWidget::slotFetchingStopped (this=0xe3d150) at ../../../akregator/src/mainwidget.cpp:808 #11 0x7f9ce176a87a in QMetaObject::activate (sender=sender@entry=0xd1f3a0, m=m@entry=0x7f9ce2a337e0 Akregator::FetchQueue::staticMetaObject, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3539 #12 0x7f9ce281a363 in Akregator::FetchQueue::signalStopped (this=this@entry=0xd1f3a0) at moc_fetchqueue.cpp:126 #13 0x7f9ce2811039 in Akregator::FetchQueue::slotAbort (this=this@entry=0xd1f3a0) at ../../../akregator/src/fetchqueue.cpp:68 #14 0x7f9ce28110aa in Akregator::FetchQueue::~FetchQueue (this=0xd1f3a0, __in_chrg=optimized out) at ../../../akregator/src/fetchqueue.cpp:50 #15 0x7f9ce289 in Akregator::FetchQueue::~FetchQueue (this=0xd1f3a0, __in_chrg=optimized out) at ../../../akregator/src/fetchqueue.cpp:53 #16 0x7f9ce28100d9 in
[akregator] [Bug 338692] crash on close
https://bugs.kde.org/show_bug.cgi?id=338692 --- Comment #1 from Christoph Feck christ...@maxiom.de --- Looks like a global QObject that references already deleted stuff. Not good. -- 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 338692] crash on close
https://bugs.kde.org/show_bug.cgi?id=338692 Alexandre Detiste alexan...@detiste.be changed: What|Removed |Added CC||alexan...@detiste.be --- Comment #2 from Alexandre Detiste alexan...@detiste.be --- Hi, I have got the same on Debian unstable: akregator allways (and only) crash at shutdown Application: akregator (4.14) KDE Platform Version: 4.14.0 Qt Version: 4.8.6+git64-g5dc8b2b+dfsg-1 Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [KCrash Handler] #5 0x7fe5469529ad in isSignalConnected (signal_index=7, this=0x5) at kernel/qobject_p.h:237 #6 QMetaObject::activate (sender=0x138b240, m=optimized out, local_signal_index=4, argv=0x7fff52ee6c10) at kernel/qobject.cpp:3472 #7 0x7fe54877f2a2 in Akregator::Frame::signalCompleted(Akregator::Frame*) () from /usr/lib/libakregatorprivate.so.4 #8 0x7fe548774a8b in Akregator::Frame::slotSetState(Akregator::Frame::State) () from /usr/lib/libakregatorprivate.so.4 #9 0x7fe52ecfa407 in Akregator::MainWidget::slotFetchingStopped() () from /usr/lib/kde4/akregatorpart.so #10 0x7fe546952c5c in QMetaObject::activate (sender=0x1299930, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3567 #11 0x7fe5487746b9 in Akregator::FetchQueue::slotAbort() () from /usr/lib/libakregatorprivate.so.4 #12 0x7fe54877473a in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4 #13 0x7fe5487747a9 in Akregator::FetchQueue::~FetchQueue() () from /usr/lib/libakregatorprivate.so.4 #14 0x7fe5487735d9 in Akregator::Kernel::~Kernel() () from /usr/lib/libakregatorprivate.so.4 #15 0x7fe545c97ec9 in __run_exit_handlers (status=0, listp=0x7fe5460035a8 __exit_funcs, run_list_atexit=run_list_atexit@entry=true) at exit.c:82 #16 0x7fe545c97f15 in __GI_exit (status=optimized out) at exit.c:104 #17 0x7fe545c81b4c in __libc_start_main (main=0x407230, argc=3, argv=0x7fff52ee6f58, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fff52ee6f48) at libc-start.c:321 #18 0x004079ed in _start () -- 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 283020] Store Kmail Tags in IMAP flags, like Thunderbird
https://bugs.kde.org/show_bug.cgi?id=283020 k...@stekahelo.de changed: What|Removed |Added CC||k...@stekahelo.de -- 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 335833] Akonadi Dav Resource: Broken State / Resource cannot be deleted (401)
https://bugs.kde.org/show_bug.cgi?id=335833 --- Comment #4 from Grégory Oestreicher g...@kamago.net --- Git commit c9a781f5b61813da80a31793bb6ce90b6f2e9046 by Grégory Oestreicher. Committed on 31/08/2014 at 16:43. Pushed by goestreicher into branch 'KDE/4.14'. Don't unnecessarily go offline Check if the error returned by the jobs while creating, modifying or deleting items are transient or final and act accordingly. Related: bug 335090 M +2-1resources/dav/common/davitemcreatejob.cpp M +2-3resources/dav/common/davitemcreatejob.h M +2-1resources/dav/common/davitemdeletejob.cpp M +2-3resources/dav/common/davitemdeletejob.h M +2-1resources/dav/common/davitemmodifyjob.cpp M +2-3resources/dav/common/davitemmodifyjob.h A +84 -0resources/dav/common/davjobbase.cpp [License: GPL (v2+)] A +78 -0resources/dav/common/davjobbase.h [License: GPL (v2+)] M +1-0resources/dav/resource/CMakeLists.txt M +20 -3resources/dav/resource/davgroupwareresource.cpp http://commits.kde.org/kdepim-runtime/c9a781f5b61813da80a31793bb6ce90b6f2e9046 -- 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 335090] Akonadi Dav Resource: Broken State / Unexpected Error 401
https://bugs.kde.org/show_bug.cgi?id=335090 --- Comment #27 from Grégory Oestreicher g...@kamago.net --- Git commit c9a781f5b61813da80a31793bb6ce90b6f2e9046 by Grégory Oestreicher. Committed on 31/08/2014 at 16:43. Pushed by goestreicher into branch 'KDE/4.14'. Don't unnecessarily go offline Check if the error returned by the jobs while creating, modifying or deleting items are transient or final and act accordingly. Related: bug 335833 M +2-1resources/dav/common/davitemcreatejob.cpp M +2-3resources/dav/common/davitemcreatejob.h M +2-1resources/dav/common/davitemdeletejob.cpp M +2-3resources/dav/common/davitemdeletejob.h M +2-1resources/dav/common/davitemmodifyjob.cpp M +2-3resources/dav/common/davitemmodifyjob.h A +84 -0resources/dav/common/davjobbase.cpp [License: GPL (v2+)] A +78 -0resources/dav/common/davjobbase.h [License: GPL (v2+)] M +1-0resources/dav/resource/CMakeLists.txt M +20 -3resources/dav/resource/davgroupwareresource.cpp http://commits.kde.org/kdepim-runtime/c9a781f5b61813da80a31793bb6ce90b6f2e9046 -- 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 325485] Locally created events are not synced to the server
https://bugs.kde.org/show_bug.cgi?id=325485 Grégory Oestreicher g...@kamago.net changed: What|Removed |Added Latest Commit||9e7377709da9f0aba758ea0d259 ||a84b0c4858bc1 Status|CONFIRMED |RESOLVED Version Fixed In||4.14.1 Resolution|--- |FIXED CC||g...@kamago.net --- Comment #7 from Grégory Oestreicher g...@kamago.net --- This should have been fixed by 9e7377709da9f0aba758ea0d259a84b0c4858bc1, which will be part of 4.14.1. -- 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 304725] CalDAV resource offline although server connection works
https://bugs.kde.org/show_bug.cgi?id=304725 Grégory Oestreicher g...@kamago.net changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||g...@kamago.net Resolution|--- |FIXED --- Comment #3 from Grégory Oestreicher g...@kamago.net --- The original cause of the bug has been fixed since. Closing, but feel free to add any comment to existing bugs still open (I'm thinking about bug #335090) in particular). Cheers, Grégory -- 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 335090] Akonadi Dav Resource: Broken State / Unexpected Error 401
https://bugs.kde.org/show_bug.cgi?id=335090 --- Comment #28 from Till Schäfer till2.schae...@uni-dortmund.de --- thx a lot! … looking forward to see this in 4.14.1 -- 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 333808] DAV resource asks for password, while kwallet password dialog is still open
https://bugs.kde.org/show_bug.cgi?id=333808 --- Comment #6 from Sander van Grieken san...@outrightsolutions.nl --- thanks for this fix, much appreciated! -- 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 327623] Contact is not sync to DAV (owncloud) when I import VCF-file
https://bugs.kde.org/show_bug.cgi?id=327623 Grégory Oestreicher g...@kamago.net changed: What|Removed |Added Version Fixed In||4.14.1 Status|REOPENED|RESOLVED Latest Commit||http://commits.kde.org/kdep ||im-runtime/509c99171995c78b ||7aae39ef73cf9d4209d704fd Resolution|--- |FIXED --- Comment #6 from Grégory Oestreicher g...@kamago.net --- Git commit 509c99171995c78b7aae39ef73cf9d4209d704fd by Grégory Oestreicher. Committed on 31/08/2014 at 21:41. Pushed by goestreicher into branch 'KDE/4.14'. Generate a unique ID for file names Based on a review submitted by Dan Vratil. FIXED-IN: 4.14.1 M +11 -12 resources/dav/common/davutils.cpp M +5-0resources/dav/common/davutils.h http://commits.kde.org/kdepim-runtime/509c99171995c78b7aae39ef73cf9d4209d704fd -- 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 335090] Akonadi Dav Resource: Broken State / Unexpected Error 401
https://bugs.kde.org/show_bug.cgi?id=335090 --- Comment #29 from Ingo Ratsdorf i...@envirology.co.nz --- Hi Grégory, good to see you back. Thanks a lot for the work so far. I had a look through the code and you seem not to handle error 412, Precondition failed. This is now separate bug #338570. -- 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 338570] Akonadi Dav Resource: Missing Conflict Resolution
https://bugs.kde.org/show_bug.cgi?id=338570 Ingo Ratsdorf i...@envirology.co.nz changed: What|Removed |Added CC||i...@envirology.co.nz --- Comment #1 from Ingo Ratsdorf i...@envirology.co.nz --- The way the resource is designed is the following: Say we delete an event from Calendar in KOrganizer: 1) Akonadi calls item-deleted function in resource 2) Resource grabs url and etag and send a delete request to the caldav server together with an if-match header and the stored etag. 3) If everything worked, resource deletes item from akonadi collection Now comes the tricky bit: If the above DOES NOT WORK (because the item was changed meanwhile before we sent that delete request), the resource gets a 412 error back from the server and calls its retry function and that does emit broken, offline. So in order for this to work, we need to introduce conflict resolution handling. Ie in the above, have three exclusive options: 1) ask the user for input 2) delete anyway (we are the boss) 3) reload from server. This currently does not work as the dav job is not given to the retry function, only the error message. In the above example of deleting an element, the resource should probably do (either or): 1) Ask user for input and then do one of the below 2) Server wins: ignore delete request and start new job to retrieve updated item from DAV server - if that fails, either ignore silently or notify user 3) Client wins: Restart the job without the if-match header, delete the item. If that fails, delete item from collection only, and/or notify user -- 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 335090] Akonadi Dav Resource: Broken State / Unexpected Error 401
https://bugs.kde.org/show_bug.cgi?id=335090 Grégory Oestreicher g...@kamago.net changed: What|Removed |Added CC||g...@kamago.net --- Comment #30 from Grégory Oestreicher g...@kamago.net --- Hey Ingo, (In reply to Ingo Ratsdorf from comment #29) I had a look through the code and you seem not to handle error 412, Precondition failed. Well actually 412 and 428 are considered unrecoverable errors, so an error message will be shown and the event not updated. This is now separate bug #338570. Yup, I saw this bug and worked on the conflict resolution tonight. Now it's a bit tricky to get it working (at least I couldn't) because Akonadi only implement local/local conflicts, i.e. conflicts that happen when two items are updated locally by multiple applications. The local/remote conflicts are not implemented, though there's the idea in the code. In the end I've tried to game the system by faking a local conflict but this did not work out because the resource is never notified of the choice made by the user and thus can't act accordingly (overwrite the remote item for example). Another limiting point is that the conflict handler is declared in a private header that can't be used from the resources… I guess that the grunt of the work must be in Akonadi to implement the local/remote conflicts management. Actually I have a lot of work to bring the bugs back under control, so this is not a high priority, especially now that errors will be shown plainly, but it's clearly something that must be worked on. Cheers, Grégory -- 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
