[Bug 289342] Akonadi server should shut down automatically if idle
https://bugs.kde.org/show_bug.cgi?id=289342 Niels van Mourik ni...@shodan.nl changed: What|Removed |Added CC||ni...@shodan.nl --- Comment #3 from Niels van Mourik ni...@shodan.nl --- Please be a bit more polite here, we are all trying to improve KDE and Akonadi to gain more market share. I'm actually agreeing with Jonathan that this makes sense as we'd only like these services to be available when we - the user - demand them to. Let's not forget the user perspective in here, that doesn't know what Akonadi is and - as being a humble user - shouldn't know about it. Akonadi is a background service that facilitates the user indirectly and therefore should be gaining less to no direct attention - even not in unexpected system resources. Adding a auto shutdown feature would be very appreciated - and I think I speak on behalf of many KDE users - and even does it when it's optional. Niels (In reply to comment #1) so, following your logic, you should also: - stop cups when you don't need it, - stop the firewall when you don't need it, - stop udev when you don't need it and so on for every service ? -- 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 269589] which version to keep-dialogue blocks Kontact-GUI
https://bugs.kde.org/show_bug.cgi?id=269589 Niels van Mourik ni...@shodan.nl changed: What|Removed |Added CC||ni...@shodan.nl --- Comment #1 from Niels van Mourik ni...@shodan.nl --- Totally agreeing here that this dialogue creates a daily amount of irritation and the - data integrity focused - attempt at preserving data is very humble but different compared to other e-mail and PIM solutions. I would therefore opt that Akonadi gets automatic conflict resolution picking whatever option it seems best, even duplicating records with BACKUP in a title is usually less obtrusive then a blocking dialog in front of the user. My attempt here is to raise awareness on the fact that Akonadi is a - very beautiful - piece of tech but that it facilitates the user indirectly and not directly - e.g. Kmail has a direct relationship with the user. The less visible Akonadi and it's logo's are to the end user, the better as it gives them the it all just works impression. -- 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 301205] New: kmail crashes every time I try save senders email address to address-book
https://bugs.kde.org/show_bug.cgi?id=301205 Bug ID: 301205 Severity: major Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail crashes every time I try save senders email address to address-book Classification: Unclassified OS: Linux Reporter: llewellyn@mtnloaded.co.za Hardware: Debian stable Status: UNCONFIRMED Component: commands and actions Product: kmail2 Application: kmail (1.13.7) KDE Platform Version: 4.6.5 (4.6.5) Qt Version: 4.7.3 Operating System: Linux 2.6.38.8-pclos3.bfs i686 Distribution: PCLinuxOS -- Information about the crash: In detail, tell us what you were doing when the application crashed. with a recieved email message open mouse point to senders address and right click gives option to save to addressbook. A window appears for selecting which adress book. In the window is only one file so I select it and click. Kmail crashes immediately. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Traceback (most recent call last): File /usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3116.0-gdb.py, line 9, in module from gobject import register File /usr/share/glib-2.0/gdb/gobject.py, line 3, in module import gdb.backtrace ImportError: No module named backtrace [KCrash Handler] #7 0xe424 in __kernel_vsyscall () #8 0xb4af0311 in raise () from /lib/i686/libc.so.6 #9 0xb4af1e3e in abort () from /lib/i686/libc.so.6 #10 0xb4d1d875 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #11 0xb4d1b795 in ?? () from /usr/lib/libstdc++.so.6 #12 0xb4d1b7d2 in std::terminate() () from /usr/lib/libstdc++.so.6 #13 0xb4d1b9ab in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #14 0xb4fbfb0d in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #15 0xb4fc4540 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #16 0xb52f7bc4 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #17 0x0804a883 in _start () Report to https://bugs.kde.org Reproducible: Always Steps to Reproduce: 1.veiw a recieved email message 2.Right click on senders address gives option to add to address book. Select the option 3.a screen appears for selecting which af=dressbook clicking on the adressbook file shown and Kmaol crashes.EVERY TIME Actual Results: Kmail crashed and a message screen suggesting crash report appears Expected Results: stored to address in the address book Nothing is added to the address book It is impossible now to collecta any email 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
[Bug 301206] New: Wish: Improve KDE, be less obtrusive!
https://bugs.kde.org/show_bug.cgi?id=301206 Bug ID: 301206 Severity: wishlist Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Wish: Improve KDE, be less obtrusive! Classification: Unclassified OS: Linux Reporter: ni...@shodan.nl Hardware: Other Status: UNCONFIRMED Component: general Product: Akonadi Hi there, As a wintered programmer the first thing - besides stating that I don't have enough time myself - I would like to state is how much of a beautiful piece of tech Akonadi actually is. It's architecture makes total sense, the system works and came a very long way but is getting rock solid. The point I would like to make to everybody is that Akonadi is a background service that never facilitates users directly, it facilitates developers of front-end implementations like Kmail and Korganizer. Although I'm not telling any new here, where I do want to emphasize on is Akonadi's role in the user interface of the average KDE user (John Ko :p). The fact the project has a logo and is named generically PIM services in some dialogues is good and there's nothing wrong with that. However, there are several examples in it's design where we wouldn't want the user to be bothered with things - most users - won't understand initially, let me give some examples: - Not automatically going back to online mode after connection failure (kmail). - Failed connection notifications, technical error messages that disturb users. - Conflict notification that disturb users instead of forced automatic conflict resolution. - Presence of the systray applet named AkonadiTray, why no generic naming? - Any direct mentioning of Akonadi where users expect something they understand. - Akonadi not automatically shutting down when it's not needed anymore, saving resources. Well I gave some examples and I do know and realize that many tickets created probably try to mention them or users giving their irritation on it. My point here is a little bit different though. Once we are at the point that the average user never sees Akonadi or knows about its existence anymore we have accomplished something very useful, a KDE experience that just works (TM) with rock solid PIM service integration everywhere. I genuinely think that getting more user expected behavior in the interface bits will improve the product and thus the long-term satisfaction for the limited resources behind Akonadi! When I ever find the time I will try to work on bits like the ones mentioned! Thanks a lot for listening to my plea! Niels -- 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 301092] no proxy configuration
https://bugs.kde.org/show_bug.cgi?id=301092 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||4.9 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im/6acbd6fa4dbdb141addfd4f6 ||50ec4ba46711ef26 --- Comment #2 from Laurent Montel mon...@kde.org --- Git commit 6acbd6fa4dbdb141addfd4f650ec4ba46711ef26 by Montel Laurent. Committed on 05/06/2012 at 13:20. Pushed by mlaurent into branch 'master'. Fix Bug 301092 - no proxy configuration FIXED-IN: 4.9 M +22 -0kmail/configuredialog.cpp M +14 -1kmail/configuredialog_p.h http://commits.kde.org/kdepim/6acbd6fa4dbdb141addfd4f650ec4ba46711ef26 -- 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 301205] kmail crashes every time I try save senders email address to address-book
https://bugs.kde.org/show_bug.cgi?id=301205 Laurent Montel mon...@kde.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Laurent Montel mon...@kde.org --- 4.7.3 is too old = update it. Your backtrace is not usefull = install debug package. Reopen it when you will have a good backtrace. Thanks -- 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 301214] New: Akregator crashes when i close it
https://bugs.kde.org/show_bug.cgi?id=301214 Bug ID: 301214 Severity: crash Version: unspecified Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Akregator crashes when i close it Classification: Unclassified OS: Linux Reporter: kdeb...@twilo.de Hardware: Debian unstable Status: UNCONFIRMED Component: general Product: akregator Application: akregator (1.6.6) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.8.1 Operating System: Linux 3.2.0-2-amd64 x86_64 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: Every time I stop Akregator (File-Exit), I got a crash with this backstrace. The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [KCrash Handler] #6 0x in ?? () #7 0x7fdca150521e in qDeleteAllQListAkregator::TreeNode*::const_iterator (end=..., begin=...) at /usr/include/qt4/QtCore/qalgorithms.h:322 #8 qDeleteAllQListAkregator::TreeNode* (c=...) at /usr/include/qt4/QtCore/qalgorithms.h:330 #9 Akregator::Folder::FolderPrivate::~FolderPrivate (this=0x23fbe10, __in_chrg=optimized out) at ../../../akregator/src/folder.cpp:68 #10 0x7fdca15052c0 in Akregator::Folder::~Folder (this=0x2306540, __in_chrg=optimized out) at ../../../akregator/src/folder.cpp:95 #11 0x7fdca1505309 in Akregator::Folder::~Folder (this=0x2306540, __in_chrg=optimized out) at ../../../akregator/src/folder.cpp:97 #12 0x7fdca1509bb8 in Akregator::FeedList::setRootNode (this=0x22a94b0, folder=0x0) at ../../../akregator/src/feedlist.cpp:435 #13 0x7fdca150a707 in Akregator::FeedList::~FeedList (this=0x22a94b0, __in_chrg=optimized out) at ../../../akregator/src/feedlist.cpp:315 #14 0x7fdca150a7e9 in Akregator::FeedList::~FeedList (this=0x22a94b0, __in_chrg=optimized out) at ../../../akregator/src/feedlist.cpp:319 #15 0x7fdca155a69a in release (this=0x1fce2a0) at /usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:145 #16 ~shared_count (this=synthetic pointer, __in_chrg=optimized out) at /usr/include/boost/smart_ptr/detail/shared_count.hpp:305 #17 ~shared_ptr (this=synthetic pointer, __in_chrg=optimized out) at /usr/include/boost/smart_ptr/shared_ptr.hpp:164 #18 Akregator::MainWidget::setFeedList (this=this@entry=0x20b98d0, list=...) at ../../../akregator/src/mainwidget.cpp:431 #19 0x7fdca155a785 in Akregator::MainWidget::slotOnShutdown (this=0x20b98d0) at ../../../akregator/src/mainwidget.cpp:315 #20 0x7fdca155250a in Akregator::Part::slotOnShutdown (this=this@entry=0x201d290) at ../../../akregator/src/akregator_part.cpp:296 #21 0x7fdca1553f20 in Akregator::Part::~Part (this=this@entry=0x201d290, __in_chrg=optimized out, __vtt_parm=optimized out) at ../../../akregator/src/akregator_part.cpp:341 #22 0x7fdca1554079 in Akregator::Part::~Part (this=0x201d290, __in_chrg=optimized out, __vtt_parm=optimized out) at ../../../akregator/src/akregator_part.cpp:344 #23 0x0040a387 in Akregator::MainWindow::queryExit (this=0x1e1b610) at ../../../akregator/src/mainwindow.cpp:196 #24 0x7fdcbaa1767c in _k_shuttingDown (this=optimized out) at ../../kdeui/widgets/kmainwindow.cpp:1126 #25 qt_static_metacall (_a=optimized out, _id=optimized out, _o=optimized out, _c=optimized out) at ./kmainwindow.moc:79 #26 KMainWindow::qt_static_metacall (_o=optimized out, _c=optimized out, _id=optimized out, _a=optimized out) at ./kmainwindow.moc:66 #27 0x7fdcb9207a9f in QMetaObject::activate (sender=0x7fffa967caf0, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547 #28 0x7fdcb91f632d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1153 #29 0x00408c13 in main (argc=optimized out, argv=optimized out) at ../../../akregator/src/main.cpp:103 Possible duplicates by query: bug 288154, bug 285938, bug 285753, bug 278742. 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
[Bug 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 --- Comment #52 from Sergio Martins iamser...@gmail.com --- Please read Comment #19 again. Do not use the old KResources, they are broken and aren't supported anymore. In akonadiconsole, the resource type should be akonadi_ical_resource. If you still see akonadi_kcal_resource then you're using the old KResource. -- 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 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 --- Comment #53 from Michael Reiher r...@gmx.de --- There should be a migration path then, I guess. You can't expect users to know about this. Other than that, at least some of us have the problem with akonadi_davgroupware_resource. So your suggestion doesn't apply then, I'd say. -- 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 301171] On startup, all folders synced, even if they are set to never sync
https://bugs.kde.org/show_bug.cgi?id=301171 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel mon...@kde.org --- How do you set never sync ? -- 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 300819] Sync hangs on N9 does not recover with offline - online
https://bugs.kde.org/show_bug.cgi?id=300819 --- Comment #2 from Andre Heinecke aheine...@intevation.de --- I've updated the available akonadi server version, but so far i am unable to reproduce this bug. Could you please do a full shutdown and then obtain the debug output from starting kmail-mobile on the command line. The recent output around such a hang of /var/log/syslog would also be helpful. -- 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 301231] New: kmail opens attachment in kwrite when its told to open it in libreoffice calc
https://bugs.kde.org/show_bug.cgi?id=301231 Bug ID: 301231 Severity: normal Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: kmail opens attachment in kwrite when its told to open it in libreoffice calc Classification: Unclassified OS: Linux Reporter: farmb...@googlemail.com Hardware: Other Status: UNCONFIRMED Component: commands and actions Product: kmail2 I got an email with a csv file attached with mimetype application/octet-stream. I click on it to open it. The open attachment dialog is shown. The second button(with the default open option) says: Open with 'LibreOffice Calc' I press this button. The attachment opens in KWrite. Reproducible: Always Expected Results: I expect the attachment to open in libreoffice calc. In file association libreoffice calc is set as default application for text/csv -- 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 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 --- Comment #124 from dotred erasmocapo...@tiscali.it --- I've noticed that after configuring once the completion order (right click on the address field to and then click to configure completion order in the menu to open the configuring window) the same configuration window becomes blank at a second try and kmail mail starts to become slow (for example: the message Retriving folder contents. Please wait... hangs on for a few seconds, deleting a message requires seconds and so on). This slowness does not disappear shutting down kmail or akonadi or restarting the system. I've gotten back kmail a normal speed of work suddenly, without a reason that I can understand. -- 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 301171] On startup, all folders synced, even if they are set to never sync
https://bugs.kde.org/show_bug.cgi?id=301171 --- Comment #2 from Szokovacs Robert s...@szo.hu --- folder properties/retrieval/automatically synchronize after: never. Actually, the folders with lots of messages have use options from parent... checked, and the parent (empty, only subfolders) has the setting described above. -- 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 300047] CardDav not syncing, no errors, while CalDav is ok for the same resource
https://bugs.kde.org/show_bug.cgi?id=300047 Jan malte.ge...@googlemail.com changed: What|Removed |Added Status|RESOLVED|REOPENED CC||malte.ge...@googlemail.com Resolution|FIXED |--- Ever confirmed|0 |1 --- Comment #9 from Jan malte.ge...@googlemail.com --- Is this related to http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-831 -- 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 300047] CardDav not syncing, no errors, while CalDav is ok for the same resource
https://bugs.kde.org/show_bug.cgi?id=300047 --- Comment #10 from Eric MSP Veith eve...@wwweb-library.net --- Does OC work around broken clients? It seems that the Akonadi DAV resource does not include the filter and limit properties in its requests. (See #300915) -- 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 301100] Cannot create a folder in the top level (gmail account)
https://bugs.kde.org/show_bug.cgi?id=301100 Laurent Montel mon...@kde.org changed: What|Removed |Added CC||kdepim-bugs@kde.org, ||mon...@kde.org Component|folders |Google Resource Version|4.8.2 |4.9 Assignee|kdepim-bugs@kde.org |d...@progdan.cz Product|kmail2 |Akonadi -- 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
[Bug 300047] CardDav not syncing, no errors, while CalDav is ok for the same resource
https://bugs.kde.org/show_bug.cgi?id=300047 Thomas Olsen tho...@tanghus.net changed: What|Removed |Added CC||tho...@tanghus.net --- Comment #11 from Thomas Olsen tho...@tanghus.net --- As Jan says in comment #9 it looks very much like the issue we have in ownCloud. I run KDE SC 4.8.3 but with KDEPIM 4.8.2 and I don't have any problems. Most (all?) of the reporters on http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-831 use KDEPIM 4.8.3. -- 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 300047] CardDav not syncing, no errors, while CalDav is ok for the same resource
https://bugs.kde.org/show_bug.cgi?id=300047 --- Comment #12 from Thomas Olsen tho...@tanghus.net --- (In reply to comment #10) Does OC work around broken clients? It seems that the Akonadi DAV resource does not include the filter and limit properties in its requests. (See #300915) OC uses SabreDAV - https://code.google.com/p/sabredav/ - as backend, AFAIK without any modifications. -- 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 300047] CardDav not syncing, no errors, while CalDav is ok for the same resource
https://bugs.kde.org/show_bug.cgi?id=300047 Grégory Oestreicher g...@kamago.net changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #13 from Grégory Oestreicher g...@kamago.net --- (In reply to comment #9) Is this related to http://bugs.owncloud.org/thebuggenie/owncloud/issues/oc-831 Yup, same issue. As I said in comment #6 I reverted the commit introducing the issue, and it's now part of KDE SC 4.8.4. -- 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 300047] CardDav not syncing, no errors, while CalDav is ok for the same resource
https://bugs.kde.org/show_bug.cgi?id=300047 --- Comment #14 from Grégory Oestreicher g...@kamago.net --- (In reply to comment #10) Does OC work around broken clients? It seems that the Akonadi DAV resource does not include the filter and limit properties in its requests. (See #300915) Exact, this was the issue with the commit. I've quickly tried to add the filter attribute, but the support for various carddav implementations was too time consuming (at least I couldn't find a good filter in a couple of hours, so I just gave up for now on this and went the easy way). -- 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 291315] After Upgrade to Kmail2, no entries shown in kaddressbook neither can they be added
https://bugs.kde.org/show_bug.cgi?id=291315 Ralph Clark r.clark...@cantab.net changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Ralph Clark r.clark...@cantab.net --- I have solved this now. In Kaddressbook there was a hidden pane on the left hand side of the view. By clicking and dragging from the far left edge of the window I was able to reveal the pane that allowed me to select Personal Contacts and then all my contacts appear. Maybe a fix could be implemented in Kmail2 to make it more obvious that a pane was hiding by the side of the window? -- 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 301240] New: Parsing token page failed
https://bugs.kde.org/show_bug.cgi?id=301240 Bug ID: 301240 Severity: grave Version: 4.7 Priority: NOR CC: kdepim-bugs@kde.org Assignee: d...@progdan.cz Summary: Parsing token page failed Classification: Unclassified OS: Linux Reporter: vojtech.zei...@opensuse.org Hardware: openSUSE RPMs Status: UNCONFIRMED Component: Google Resource Product: Akonadi Recently, synchronization of my calendar (and later a also contacts) stopped working. When I try to reload address book (literally nothing happens when I try to reload calendar resource), I see Google Sign in dialog asking about permission for Akonadi Google to access my Google account. I log in, I grant access, but instead of confirmation page I see only Error while talking to Google - Parsing token page failed. Same happens when I try to add new Google account. It happens every time. I have akonadi-4.7.4-3.20.31.x86_64, kdebase4-workspace-plasma-engine-akonadi-4.7.4-6.20.35.x86_64, plasma-addons-akonadi-4.7.4-2.6.2.x86_64, akonadi-runtime-1.6.2-3.4.2.x86_64, libakonadi4-4.7.4-2.7.2.x86_64, libakonadiprotocolinternals1-1.6.2-3.4.2.x86_64 and akonadi-google-0.3git-89.1.x86_64 -- 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 301241] New: Navigator toolbar shows icons at wrong side
https://bugs.kde.org/show_bug.cgi?id=301241 Bug ID: 301241 Severity: normal Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Navigator toolbar shows icons at wrong side Classification: Unclassified OS: Linux Reporter: mat...@gmx.com Hardware: Ubuntu Packages Status: UNCONFIRMED Component: general Product: kontact The navigator toolbar (the one from Settings - Toolbars Shown - Navigator) shows the icons to the right of the text in stead of to the left of the text. When right clicking on the toolbar, the menu is showing a right-to-left layout. This only happens from the second time you right click on the toolbar. My navigator toolbar is in front of the main toolbar, Text position: Text Alongside Icons, Icon size: Medium, Orientation: Top, Toolbar Positions are locked. Navigator is showing buttons for e-mail, addressbook and calendar. Reproducible: Always Steps to Reproduce: 1. Enable Settings - Toolbars Shown - Navigator 2. Place it at the top (right click: Orientation - Top) 3. Actual Results: The icons are shown to the right of the text Expected Results: The icons are shown to the left of the text I use a left-to-right language (Dutch), the icons on the toolbars are to the left of the text. -- 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 301241] Navigator toolbar shows icons at wrong side
https://bugs.kde.org/show_bug.cgi?id=301241 --- Comment #1 from Matthias mat...@gmx.com --- Created attachment 71608 -- https://bugs.kde.org/attachment.cgi?id=71608action=edit Screenshot of the problem -- 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 301240] Parsing token page failed
https://bugs.kde.org/show_bug.cgi?id=301240 Dan Vratil d...@progdan.cz changed: What|Removed |Added Component|Google Resource |General Version|4.7 |0.4.0 Product|Akonadi |libkgapi -- 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 301240] Parsing token page failed
https://bugs.kde.org/show_bug.cgi?id=301240 Dan Vratil d...@progdan.cz changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||0.4.1 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/akon ||adi-google/5c92e2fb5ced528a ||20fd1d8723fd7a8d7ba686a3 --- Comment #1 from Dan Vratil d...@progdan.cz --- Git commit 5c92e2fb5ced528a20fd1d8723fd7a8d7ba686a3 by Dan Vrátil. Committed on 06/06/2012 at 00:36. Pushed by dvratil into branch 'LibKGAPI/0.4'. Parse OAuth code from page title instead of body The OAuth code used for obtaining access tokens is provided in webpage title as a string. The title is guaranteed not to change syntax, while the body of the page, from which we were parsing the token before, can change anytime, which breaks the authentication process. FIXED-IN: 0.4.1 M +8-3libkgapi/ui/authwidget_p.cpp http://commits.kde.org/akonadi-google/5c92e2fb5ced528a20fd1d8723fd7a8d7ba686a3 -- 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 300047] CardDav not syncing, no errors, while CalDav is ok for the same resource
https://bugs.kde.org/show_bug.cgi?id=300047 --- Comment #15 from Ingo Ratsdorf i...@envirology.co.nz --- As a result however, all carddav servers based on sabredav will not work with any version of KDE 4.8.3. Simply because the required filters are missing. Sabredav has introduced support for this issue however, so all sabredav implementations could or should upgrade the the latest to provide short term workaround. Yup, same issue. As I said in comment #6 I reverted the commit introducing the issue, and it's now part of KDE SC 4.8.4. -- 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 301250] New: Kontact crash at startup due to not finding the calendar resource
https://bugs.kde.org/show_bug.cgi?id=301250 Bug ID: 301250 Severity: crash Version: 4.8.3 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: Kontact crash at startup due to not finding the calendar resource Classification: Unclassified OS: Linux Reporter: ehakandu...@gmail.com Hardware: Fedora RPMs Status: UNCONFIRMED Component: general Product: kontact Application: kontact (4.8.3) KDE Platform Version: 4.8.3 (4.8.3) Qt Version: 4.8.1 Operating System: Linux 3.3.7-1.fc17.x86_64 x86_64 Distribution: Fedora release 17 (Beefy Miracle) -- Information about the crash: - What I was doing when the application crashed: Started up the Kontact, after restoring ~/.kde directory from a few-days old backup. This directory was inadvertently modified probably losing some its contents before restoration. The initial error message complained of not being able to find a specific calendar followed by Kontact exiting. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7fdcfd0f1880 (LWP 9229))] Thread 3 (Thread 0x7fdcf201f700 (LWP 9230)): #0 0x0039a940b595 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00384d41677d in ?? () from /lib64/libQtWebKit.so.4 #2 0x00384d416889 in ?? () from /lib64/libQtWebKit.so.4 #3 0x0039a9407d14 in start_thread () from /lib64/libpthread.so.0 #4 0x0039a8cf199d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fdcf1716700 (LWP 9231)): #0 0x00383e04787c in ?? () from /lib64/libglib-2.0.so.0 #1 0x00383e047ad4 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #2 0x00383eda39e6 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #3 0x00383ed7493f in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #4 0x00383ed74bc8 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #5 0x00383ec785a0 in QThread::exec() () from /lib64/libQtCore.so.4 #6 0x00383ec7b53b in ?? () from /lib64/libQtCore.so.4 #7 0x0039a9407d14 in start_thread () from /lib64/libpthread.so.0 #8 0x0039a8cf199d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fdcfd0f1880 (LWP 9229)): [KCrash Handler] #5 0x0039a8c35965 in raise () from /lib64/libc.so.6 #6 0x0039a8c37118 in abort () from /lib64/libc.so.6 #7 0x00383ec71184 in qt_message_output(QtMsgType, char const*) () from /lib64/libQtCore.so.4 #8 0x00383ec71338 in ?? () from /lib64/libQtCore.so.4 #9 0x00383ec714c4 in qFatal(char const*, ...) () from /lib64/libQtCore.so.4 #10 0x00385529b047 in MailCommon::Kernel::self() () from /lib64/libmailcommon.so.4 #11 0x00385528aea9 in MailCommon::FolderCollection::writeConfig() const () from /lib64/libmailcommon.so.4 #12 0x00385528b91a in MailCommon::FolderCollection::~FolderCollection() () from /lib64/libmailcommon.so.4 #13 0x00385528b999 in MailCommon::FolderCollection::~FolderCollection() () from /lib64/libmailcommon.so.4 #14 0x003855289714 in ?? () from /lib64/libmailcommon.so.4 #15 0x0039a8c38bb1 in __run_exit_handlers () from /lib64/libc.so.6 #16 0x0039a8c38c35 in exit () from /lib64/libc.so.6 #17 0x00385529b993 in MailCommon::Kernel::emergencyExit(QString const) () from /lib64/libmailcommon.so.4 #18 0x00385529bd60 in MailCommon::Kernel::createDefaultCollectionDone(KJob*) () from /lib64/libmailcommon.so.4 #19 0x00383ed8c07f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib64/libQtCore.so.4 #20 0x00383ff336b2 in KJob::result(KJob*) () from /lib64/libkdecore.so.5 #21 0x00383ff336f0 in KJob::emitResult() () from /lib64/libkdecore.so.5 #22 0x0038461a6391 in Akonadi::TransactionSequence::slotResult(KJob*) () from /lib64/libakonadi-kde.so.4 #23 0x003846180793 in Akonadi::SpecialCollectionsRequestJob::slotResult(KJob*) () from /lib64/libakonadi-kde.so.4 #24 0x0038461a5bc4 in ?? () from /lib64/libakonadi-kde.so.4 #25 0x00383ed8c07f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib64/libQtCore.so.4 #26 0x00383ff336b2 in KJob::result(KJob*) () from /lib64/libkdecore.so.5 #27 0x00383ff336f0 in KJob::emitResult() () from /lib64/libkdecore.so.5 #28 0x00384617de28 in ?? () from /lib64/libakonadi-kde.so.4 #29 0x00383ed8c07f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib64/libQtCore.so.4 #30 0x00383ff336b2 in KJob::result(KJob*) () from /lib64/libkdecore.so.5 #31 0x00383ff336f0 in KJob::emitResult() () from /lib64/libkdecore.so.5 #32 0x00383ed8a1ce in QObject::event(QEvent*) () from /lib64/libQtCore.so.4 #33
