[akregator] [Bug 256034] Feed content is displayed with date 07.02.2106 07:28
https://bugs.kde.org/show_bug.cgi?id=256034 Philippe ROUBACH changed: What|Removed |Added Version|5.7.2 |5.7.3 --- Comment #34 from Philippe ROUBACH --- Here I found an explanation https://nwrickert2.wordpress.com/2017/09/12/reviewing-akregator-again/ I confirm the procedure to reproduce phenomenon. The explanation is : if an article is older than the delay to keep the article akregator set date to "no date". This "no date" is read at next launch as 07/02/2106. Please I know it is not easy to find someone to fix this bug but now this bug is 8 years old. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 395952] org.kde.pim.davresource: DavGroupwareResource::onMultigetFinished: Failed to parse item data.
https://bugs.kde.org/show_bug.cgi?id=395952 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 375018] Crashes on reboot
https://bugs.kde.org/show_bug.cgi?id=375018 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 375587] crashes on reboot
https://bugs.kde.org/show_bug.cgi?id=375587 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 372260] Crash at shutdown
https://bugs.kde.org/show_bug.cgi?id=372260 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 378533] Kontact crash
https://bugs.kde.org/show_bug.cgi?id=378533 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 402521] crash Akregator
https://bugs.kde.org/show_bug.cgi?id=402521 Colin J Thomson changed: What|Removed |Added Resolution|--- |DUPLICATE CC||colin.thom...@g6avk.co.uk Status|REPORTED|RESOLVED --- Comment #1 from Colin J Thomson --- Probably related to this. *** This bug has been marked as a duplicate of bug 371511 *** -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 402453] KNotes help menu is empty
https://bugs.kde.org/show_bug.cgi?id=402453 Laurent Montel changed: What|Removed |Added Latest Commit||https://commits.kde.org/kno ||tes/f245faae1ff603227fad8c4 ||679698fdfb4261d87 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.10.1 --- Comment #2 from Laurent Montel --- Git commit f245faae1ff603227fad8c4679698fdfb4261d87 by Laurent Montel. Committed on 24/12/2018 at 13:06. Pushed by mlaurent into branch 'Applications/18.12'. Fix Bug 402453 - KNotes help menu is empty FIXED-IN: 5.10.1 M +36 -4src/apps/knotesapp.cpp https://commits.kde.org/knotes/f245faae1ff603227fad8c4679698fdfb4261d87 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 400368] Cannot launch Kmail via apps launcher. It launches via terminal.
https://bugs.kde.org/show_bug.cgi?id=400368 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Patrick Silva --- cannot reproduce anymore. kmail 5.9.2 Operating System: Arch Linux KDE Plasma Version: 5.14.4 Qt Version: 5.12.0 KDE Frameworks Version: 5.53.0 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402526] DATABASE ERROR: Error code: "1213", "Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement", Query: "UPDATE PimItemTable SET at
https://bugs.kde.org/show_bug.cgi?id=402526 Dennis Schridde changed: What|Removed |Added Summary|Akonadi Server 18.08.3: |DATABASE ERROR: Error code: |DATABASE ERROR: Error code: |"1213", "Deadlock found |"1213", "Deadlock found |when trying to get lock; |when trying to get lock;|try restarting transaction |try restarting transaction |QMYSQL3: Unable to execute |QMYSQL3: Unable to execute |statement", Query: "UPDATE |statement", Query: "UPDATE |PimItemTable SET atime = ? |PimItemTable SET atime = ? |WHERE ( ( PimItemTable.id = |WHERE ( ( PimItemTable.id = |? OR PimItemTable.id = ? OR |? OR ...) ) |...) ) -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 402526] New: Akonadi Server 18.08.3: DATABASE ERROR: Error code: "1213", "Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement", Query
https://bugs.kde.org/show_bug.cgi?id=402526 Bug ID: 402526 Summary: Akonadi Server 18.08.3: DATABASE ERROR: Error code: "1213", "Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement", Query: "UPDATE PimItemTable SET atime = ? WHERE ( ( PimItemTable.id = ? OR ...) ) Product: Akonadi Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- SUMMARY I found the following error in my system log: org.kde.pim.akonadiserver: DATABASE ERROR: org.kde.pim.akonadiserver: Error code: "1213" org.kde.pim.akonadiserver: DB error: "Deadlock found when trying to get lock; try restarting transaction" org.kde.pim.akonadiserver: Error text: "Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement" org.kde.pim.akonadiserver: Query: "UPDATE PimItemTable SET atime = ? WHERE ( ( PimItemTable.id = ? OR PimItemTable.id = ? OR << repeats a few hundred (?) times >> ) ) STEPS TO REPRODUCE Unknown OBSERVED RESULT Abovementioned error message in the system log EXPECTED RESULT No error in the system log SOFTWARE/OS VERSIONS Distribution: Fedora 29 Linux: 4.19.10-300.fc29.x86_64 Package Version: kf5-akonadi-server-18.08.3-1.fc29.src.rpm KDE Applications Version: 18.08.3 KDE Plasma Version: 5.9.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 402525] New: KMail crashed on exit
https://bugs.kde.org/show_bug.cgi?id=402525 Bug ID: 402525 Summary: KMail crashed on exit Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Target Milestone: --- Application: kmail (5.9.3) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.19.10-300.fc29.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: 1. Open KMail 2. Press check mail button 3. Wait 4. Go through folders and look at some unread messages in the preview pane 5. Quit KMail 6. Get a DrKonqi notification about it crashing The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f59753ddf40 (LWP 6687))] Thread 34 (Thread 0x7f583700 (LWP 7912)): #0 0x7f5984efbb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f597fcceb57 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7f597fcd081a in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7f597fcd0902 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7f597fcd56c1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #5 0x7f597fcd69bf in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #6 0x7f597fce0fd1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #7 0x7f5984ef558e in start_thread () at /lib64/libpthread.so.0 #8 0x7f5985f366a3 in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7f5929ffb700 (LWP 7911)): #0 0x7f5984efbb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f597fcceb57 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7f597fcd081a in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7f597fcd0902 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7f597fcd56c1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #5 0x7f597fcd6ba1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #6 0x7f597fce0fd1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #7 0x7f5984ef558e in start_thread () at /lib64/libpthread.so.0 #8 0x7f5985f366a3 in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f592affd700 (LWP 7680)): #0 0x7f5984efbb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f597fcceb57 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7f597fcd081a in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7f597fcd0902 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7f597fcd56c1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #5 0x7f597fcd6ba1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #6 0x7f597fce0fd1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #7 0x7f5984ef558e in start_thread () at /lib64/libpthread.so.0 #8 0x7f5985f366a3 in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f58c7fff700 (LWP 7679)): #0 0x7f5984efbb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f597fcceb57 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7f597fcd081a in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7f597fcd0902 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7f597fcd56c1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #5 0x7f597fcd6ba1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #6 0x7f597fce0fd1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #7 0x7f5984ef558e in start_thread () at /lib64/libpthread.so.0 #8 0x7f5985f366a3 in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f58c6ffd700 (LWP 7345)): #0 0x7f5984efbb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f597fcceb57 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7f597fcd081a in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7f597fcd0902 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7f597fcd56c1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #5 0x7f597fcd6ba1
[akregator] [Bug 402521] New: crash Akregator
https://bugs.kde.org/show_bug.cgi?id=402521 Bug ID: 402521 Summary: crash Akregator Product: akregator Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: cornos...@palendriai.lt Target Milestone: --- Application: akregator (5.9.3) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.19.9-300.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: - What I was doing when the application crashed: close the tab after reading the full article (automatic translation) The crash can be reproduced every time. -- Backtrace: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa74c1a5f40 (LWP 16781))] Thread 30 (Thread 0x7fa693fff700 (LWP 16897)): #0 0x7fa74369eb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa74667ab57 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7fa74667c81a in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7fa74667c902 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7fa7466816c1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #5 0x7fa7466829bf in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #6 0x7fa74668cfd1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #7 0x7fa74369858e in start_thread () at /lib64/libpthread.so.0 #8 0x7fa74b3c56a3 in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7fa69350b700 (LWP 16886)): #0 0x7fa74369eb28 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fa74667ab57 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7fa74667c81a in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7fa74667c902 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7fa7466816c1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #5 0x7fa746682ba1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #6 0x7fa74668cfd1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #7 0x7fa74369858e in start_thread () at /lib64/libpthread.so.0 #8 0x7fa74b3c56a3 in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7fa6bccdb700 (LWP 16873)): #0 0x7fa74b3482c0 in _IO_no_init () at /lib64/libc.so.6 #1 0x7fa74b3d4950 in __vsnprintf_chk () at /lib64/libc.so.6 #2 0x7fa7400e1883 in evutil_vsnprintf () at /lib64/libevent-2.1.so.6 #3 0x7fa7400e1923 in evutil_snprintf () at /lib64/libevent-2.1.so.6 #4 0x7fa7400e4ebc in event_logv_ () at /lib64/libevent-2.1.so.6 #5 0x7fa7400e5048 in event_warn () at /lib64/libevent-2.1.so.6 #6 0x7fa7400e6a40 in epoll_dispatch () at /lib64/libevent-2.1.so.6 #7 0x7fa7400dc598 in event_base_loop () at /lib64/libevent-2.1.so.6 #8 0x7fa74664f0f9 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #9 0x7fa74666e61b in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #10 0x7fa746691554 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #11 0x7fa74668cfd1 in () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #12 0x7fa74369858e in start_thread () at /lib64/libpthread.so.0 #13 0x7fa74b3c56a3 in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7fa6beffd700 (LWP 16819)): #0 0x7fa74b3b5f84 in read () at /lib64/libc.so.6 #1 0x7fa740c34aa0 in () at /lib64/libglib-2.0.so.0 #2 0x7fa740bee09b in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7fa740bee550 in () at /lib64/libglib-2.0.so.0 #4 0x7fa740bee6d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fa74ba7282b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fa74ba2117b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fa74b889046 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7fa74b8924bb in () at /lib64/libQt5Core.so.5 #9 0x7fa74369858e in start_thread () at /lib64/libpthread.so.0 #10 0x7fa74b3c56a3 in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fa6bf7fe700 (LWP 16818)): #0 0x7fa7286a68d0 in pa_pstream_ref () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #1 0x7fa7286a70c4 in do_pstream_read_write () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7fa7286a74ad in srb_callback () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #3 0x7fa7286a7d3a in srbchannel_rwloop () at
[kmail2] [Bug 402258] fatal error "could not create collection outbox, resourceId: 7"
https://bugs.kde.org/show_bug.cgi?id=402258
Nicolas changed:
What|Removed |Added
CC||nico@gmail.com
--- Comment #1 from Nicolas ---
Can confirm here, but with resourceID 10, after the same sequence of events.
Journalctl provides the relevant information:
akonadiserver[878]: org.kde.pim.akonadiserver: DATABASE ERROR:
akonadiserver[878]: org.kde.pim.akonadiserver: Error code: "1062"
akonadiserver[878]: org.kde.pim.akonadiserver: DB error: "Duplicate entry
'4-outbox' for key 'CollectionTable_parentAndNameIndex'"
akonadiserver[878]: org.kde.pim.akonadiserver: Error text: "Duplicate entry
'4-outbox' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to
execute statement"
akonadiserver[878]: org.kde.pim.akonadiserver: Values: QMap((":0",
QVariant(QString, ""))(":1", QVariant(QString, ""))(":10", QVariant(int,
-1))(":11", QVariant(int, -1))(":12", QVariant(bool, false))(":13",
QVariant(QString, ""))(":14", QVariant(bool, false))(":2", QVariant(QString,
"outbox"))(":3", QVariant(qlonglong, 4))(":4", QVariant(qlonglong, 10))(":5",
QVariant(bool, true))(":6", QVariant(int, 2))(":7", QVariant(int, 2))(":8",
QVariant(int, 2))(":9", QVariant(bool, true)))
akonadiserver[878]: org.kde.pim.akonadiserver: Query: "INSERT INTO
CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled,
syncPref, displayPref, indexPref, cachePolicyInherit, cachePolicyCheckInterval,
cachePolicyCacheTimeout, cachePolicySyncOnDemand, cachePolicyLocalParts,
isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11, :12, :13,
:14)"
--
You are receiving this mail because:
You are the assignee for the bug.
