[korganizer] [Bug 409972] New: korganizer sends new todo to wrong calendar
https://bugs.kde.org/show_bug.cgi?id=409972 Bug ID: 409972 Summary: korganizer sends new todo to wrong calendar Product: korganizer Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: todoview Assignee: kdepim-bugs@kde.org Reporter: westlake.b...@gmail.com Target Milestone: --- (Korganizer version: 5.9.3) SUMMARY korganizer sends new todo on wrong calendar If a user has more than 1 calendar, and they create a todo (described below), that todo goes to the wrong calendar. Whether a feature or not (new user), the user is not able to change the applied calendar for the new todo. STEPS TO REPRODUCE 1. right-click on calendar event and from context-menu choose to 'create todo' 2. Select a specific calendar 3. check the todo list OBSERVED RESULT The todo does not get created on the specified calendar. Instead the first of available calendars gets the new todo item. Note: a new todo via the "todo view" gets stored in the correct calendar, but not via 'create todo' using the context-menu from calendar events. SOFTWARE/OS VERSIONS Korganizer version: 5.9.3 Linux: Debian 10 Qt Version: 5.x Calendars: Davical server -> 1 caldav server (davical -- using custom https:// connect string) ^ Davical Calendars - 1 account, two calendars Bug occurs using just these two calendars with 1 caldav server. (bug was occurring previously as well with the built-in calendars: when attempting to send a new todo to a caldav server, it was instead being sent to the built-in Personal calendar. The built-in calendars were removed, and the bug was still occurring among the two calendars with the davical server.) -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 409970] New: Kontact segfaults after having cause an important memory hole after having made use of spam filters).
https://bugs.kde.org/show_bug.cgi?id=409970 Bug ID: 409970 Summary: Kontact segfaults after having cause an important memory hole after having made use of spam filters). Product: kontact Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: staka...@eclipso.eu Target Milestone: --- Application: kontact (5.10.3) Qt Version: 5.9.7 Frameworks Version: 5.55.0 Operating System: Linux 4.12.14-lp151.28.7-default x86_64 Distribution: "openSUSE Leap 15.1" -- Information about the crash: - What I was doing when the application crashed: That was an idling kmail that in the meantime did receive a mail. - Unusual behavior I noticed: Filter runs quite slowly. Amount of memory after this triples maybe hightens up to 5 times the normal amount. May crash the machine. The application did crash after check of mail. - Custom settings of the application: spam is filtered by daemonized spamd instead of pearl. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f465c5e6540 (LWP 4071))] Thread 30 (Thread 0x7f46167fc700 (LWP 15605)): #0 0x7f4654a61bdb in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4649784962 in base::ConditionVariable::TimedWait () at ../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:117 #2 0x7f464975a749 in base::PosixDynamicThreadPool::WaitForTask () at ../../3rdparty/chromium/base/threading/worker_pool_posix.cc:176 #3 0x7f464975acab in ThreadMain () at ../../3rdparty/chromium/base/threading/worker_pool_posix.cc:86 #4 0x7f464975355b in ThreadFunc () at ../../3rdparty/chromium/base/threading/platform_thread_posix.cc:71 #5 0x7f4654a5b569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f4658f459ef in clone () from /lib64/libc.so.6 Thread 29 (Thread 0x7f451781a700 (LWP 15604)): #0 0x7f4652be7ff4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f4652ba16fc in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4652ba20db in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4652ba22bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f4659a9896b in QEventDispatcherGlib::processEvents (this=0x7f4510004850, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f4659a3d90a in QEventLoop::exec (this=this@entry=0x7f4517819cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f465985bdaa in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f4659860ced in QThreadPrivate::start (arg=0x55eb72a73290) at thread/qthread_unix.cpp:368 #8 0x7f4654a5b569 in start_thread () from /lib64/libpthread.so.0 #9 0x7f4658f459ef in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7f4529dad700 (LWP 15600)): #0 0x7f4658f36c98 in read () from /lib64/libc.so.6 #1 0x7f4652be6ca0 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4652ba1cb8 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4652ba2150 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f4652ba22bc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f4659a9896b in QEventDispatcherGlib::processEvents (this=0x7f451c013b30, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f4659a3d90a in QEventLoop::exec (this=this@entry=0x7f4529daccb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f465985bdaa in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7f4659860ced in QThreadPrivate::start (arg=0x55eb72706320) at thread/qthread_unix.cpp:368 #9 0x7f4654a5b569 in start_thread () from /lib64/libpthread.so.0 #10 0x7f4658f459ef in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7f44faffd700 (LWP 4155)): #0 0x7f4654a618ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4649755c45 in base::SequencedWorkerPool::Inner::ThreadLoop () at ../../3rdparty/chromium/base/threading/sequenced_worker_pool.cc:1080 #2 0x7f4649756127 in base::SequencedWorkerPool::Worker::Run () at ../../3rdparty/chromium/base/threading/sequenced_worker_pool.cc:611 #3 0x7f4649756ec1 in base::SimpleThread::ThreadMain () at ../../3rdparty/chromium/base/threading/simple_thread.cc:68 #4 0x7f464975355b in ThreadFunc () at ../../3rdparty/chromium/base/threading/platform_thread_posix.cc:71 #5 0x7f4654a5b569 in start_thread () from /lib64/libpthread.so.0 #6 0x7f4658f459ef in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7f44fb7fe700 (LWP 4154)): #0 0x7f4654a618ad in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4649755c45 in
[Akonadi] [Bug 409224] kmail with >=mariadb-10.4.6: not able to refresh email list: Unable to append status flags
https://bugs.kde.org/show_bug.cgi?id=409224 Thomas Fischer changed: What|Removed |Added CC||fisc...@unix-ag.uni-kl.de --- Comment #10 from Thomas Fischer --- On Arch Linux and maybe other Linux distributions, the socket FSO 'mysql.socket' is not located in /tmp/akonadi-*/ but in /run/user/*/akonadi/default/ instead. Thus, the two commands to run become: mysql -S /run/user/$(id -u)/akonadi/default/mysql.socket -e 'create database mysql' && mysql_upgrade -S /run/user/$(id -u)/akonadi/default/mysql.socket At least for me, after running both commands KMail/Akonadi starts fetching and listing mails again. (In reply to Piotr from comment #7) > Workaround wasn't working for me: > > piorek@dreadnought ~ $ mysql_upgrade > --socket=/tmp/akonadi-piorek.XX/mysql.socket > Version check failed. Got the following error when calling the 'mysql' > command line client > ERROR 1049 (42000): Unknown database 'mysql' > FATAL ERROR: Upgrade failed > > Had to create DB mysql first (CREATE DATABASE mysql;). This fixed the > problem and upgrade succeeded. Looks like KMail is working fine so far. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 388178] Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault - ArchiveJob::~ArchiveJob() (this=0x24b1080, __in_chrg=)
https://bugs.kde.org/show_bug.cgi?id=388178 Christophe Giboudeaux changed: What|Removed |Added Resolution|DOWNSTREAM |WORKSFORME --- Comment #3 from Christophe Giboudeaux --- downstream implies this was a distribution issue. This is not the case here. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 383639] PIM-Import-Werkzeug (importwizard), signal: Segmentation fault - MailImporter::Filter::~Filter() ()
https://bugs.kde.org/show_bug.cgi?id=383639 Don Curtis changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Don Curtis --- With openSUSE Leap 15.1 possibly no longer an issue. importwizard 5.10.3 Qt: 5.9.7 KDE Frameworks: 5.55.0 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 394313] Kontact (kontact), signal: Segmentation fault - mapFromSource(QModelIndex const&) const () at /usr/lib64/libQt5Core.so.5
https://bugs.kde.org/show_bug.cgi?id=394313 Don Curtis changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Don Curtis --- With openSUSE Leap 15.1 possibly no longer an issue. kontact 5.10.3 Qt: 5.9.7 KDE Frameworks: 5.55.0 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 390544] Kontact (kontact), signal: Segmentation fault - QAbstractItemModelPrivate::removePersistentIndexData(QPersistentModelIndexData*)
https://bugs.kde.org/show_bug.cgi?id=390544 Don Curtis changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Don Curtis --- With openSUSE Leap 15.1 possibly no longer an issue. kontact 5.10.3 Qt: 5.9.7 KDE Frameworks: 5.55.0 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 388178] Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault - ArchiveJob::~ArchiveJob() (this=0x24b1080, __in_chrg=)
https://bugs.kde.org/show_bug.cgi?id=388178 Don Curtis changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #2 from Don Curtis --- With openSUSE Leap 15.1 this is no longer an issue. kmail2 18.12.3 Qt: 5.9.7 KDE Frameworks: 5.55.0 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 382087] Kontact (kontact), signal: Segmentation fault: QCoreApplication::postEvent(QObject*, QEvent*, int)
https://bugs.kde.org/show_bug.cgi?id=382087 Don Curtis changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Don Curtis --- With openSUSE Leap 15.1 this is no longer an issue. kmail2 18.12.3 Qt: 5.9.7 KDE Frameworks: 5.55.0 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 381640] Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=381640 Don Curtis changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #2 from Don Curtis --- With openSUSE Leap 15.1 this is no longer an issue. kmail 18.12.3 (akonadi_archivemail_agent) Qt: 5.9.7 KDE Frameworks: 5.55.0 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 378429] Kontact Welcome screen - visit the web site - Signal: Segmentation fault (11)
https://bugs.kde.org/show_bug.cgi?id=378429 Don Curtis changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #2 from Don Curtis --- With openSUSE Leap 15.1 this is no longer an issue. kontact 5.10.3 Qt: 5.9.7 KDE Frameworks: 5.55.0 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 384144] KMail - moving an e-Mail which has been read to a new folder, places the e-Mail file in the sub-directory "new"
https://bugs.kde.org/show_bug.cgi?id=384144 --- Comment #1 from Don Curtis --- With kmail2 5.10.3 this is still an issue. Qt: 5.9.7 KDE Frameworks: 5.55.0 plasmashell 5.12.8 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 382856] KMail2 - Received e-mail without a colon on the header field "To" does not display
https://bugs.kde.org/show_bug.cgi?id=382856 --- Comment #2 from Don Curtis --- With kmail2 5.10.3 this is still an issue … KDE Frameworks: 5.55.0 Qt: 5.9.7 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409531] Mail sent is landing in sent-mail/new/ directory.
https://bugs.kde.org/show_bug.cgi?id=409531 Don Curtis changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Don Curtis --- No longer an issue – the openSUSE kdepimruntime patch openSUSE-2019-1696 to v18.12.3 on 8th July seems to have fixed this issue. “Add Qt5NetworkAuth and qca-qt5 BuildRequires for OAuth2 support for the EWS resource.” No idea as to why this fixed the issue but, it did – maybe the rebuild helped … -- You are receiving this mail because: You are the assignee for the bug.
