[Akonadi] [Bug 423132] New: mail dispatcher crash on sending email
https://bugs.kde.org/show_bug.cgi?id=423132 Bug ID: 423132 Summary: mail dispatcher crash on sending email Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Mail Dispatcher Agent Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Target Milestone: --- Application: akonadi_maildispatcher_agent (5.14.3 (20.04.3)) Qt Version: 5.15.0 Frameworks Version: 5.70.0 Operating System: Linux 5.6.14-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I sent an email and the mail dispatcher crashed. The mail was sent via a locally running davmail -- Backtrace: Application: akonadi_maildispatcher_agent (akonadi_maildispatcher_agent), signal: Aborted [KCrash Handler] #4 0x7f73a26ad4b1 in raise () from /lib64/libc.so.6 #5 0x7f73a2696539 in abort () from /lib64/libc.so.6 #6 0x7f73a2c0dc27 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffed2472c88, msg=msg@entry=0x7f73a2f07ea0 "ASSERT: \"%s\" in file %s, line %d") at global/qlogging.cpp:893 #8 0x7f73a2c0d074 in qt_assert (assertion=, file=, line=) at ../../include/QtCore/../../src/corelib/global/qlogging.h:90 #9 0x00424473 in SendJob::transportResult (this=0x7f738804fbc0, job=0x1889e30) at /home/KDE5/source/kde/pim/kdepim-runtime/agents/maildispatcher/sendjob.cpp:202 #10 0x004291cf in QtPrivate::FunctorCall, QtPrivate::List, void, void (SendJob::*)(KJob*)>::call (f=(void (SendJob::*)(SendJob * const, KJob *)) 0x424430 , o=0x7f738804fbc0, arg=0x7ffed2472f30) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:152 #11 0x00429138 in QtPrivate::FunctionPointer::call, void> (f=(void (SendJob::*)(SendJob * const, KJob *)) 0x424430 , o=0x7f738804fbc0, arg=0x7ffed2472f30) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:185 #12 0x00429065 in QtPrivate::QSlotObject, void>::impl (which=1, this_=0x183c3c0, r=0x7f738804fbc0, a=0x7ffed2472f30, ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:418 #13 0x7f73a2e5cfe6 in QtPrivate::QSlotObjectBase::call (a=0x7ffed2472f30, r=0x7f738804fbc0, this=0x183c3c0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate (sender=0x1889e30, signal_index=6, argv=argv@entry=0x7ffed2472f30) at kernel/qobject.cpp:3886 #15 0x7f73a2e56340 in QMetaObject::activate (sender=sender@entry=0x1889e30, m=m@entry=0x7f73a4010660 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffed2472f30) at kernel/qobject.cpp:3946 #16 0x7f73a3fbee0c in KJob::result (this=this@entry=0x1889e30, _t1=, _t1@entry=0x1889e30, _t2=...) at /usr/src/debug/kcoreaddons-5.70.0-1.2.x86_64/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:574 #17 0x7f73a3fc30b3 in KJob::finishJob (this=0x1889e30, emitResult=) at /usr/src/debug/kcoreaddons-5.70.0-1.2.x86_64/src/lib/jobs/kjob.cpp:96 #18 0x7f739c0ae6d7 in MailTransport::SmtpJob::startSmtpJob()::$_0::operator()(QString const&) const (this=0x18876e0, err=...) at /home/KDE5/source/kde/pim/kmailtransport/src/kmailtransport/plugins/smtp/smtpjob.cpp:169 #19 0x7f739c0ae654 in QtPrivate::FunctorCall, QtPrivate::List, void, MailTransport::SmtpJob::startSmtpJob()::$_0>::call(MailTransport::SmtpJob::startSmtpJob()::$_0&, void**) (f=..., arg=0x1856e38) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #20 0x7f739c0ae621 in QtPrivate::Functor::call, void>(MailTransport::SmtpJob::startSmtpJob()::$_0&, void*, void**) (f=..., arg=0x1856e38) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #21 0x7f739c0ae5cc in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x18876d0, r=0x1889e30, a=0x1856e38, ret=0x0) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #22 0x7f73a2e52a31 in QObject::event (this=0x1889e30, e=0x1856df0) at kernel/qobject.cpp:1314 #23 0x7f73a397d0cf in QApplicationPrivate::notify_helper (this=, receiver=0x1889e30, e=0x1856df0) at kernel/qapplication.cpp:3671 #24 0x7f73a2e26b0a in QCoreApplication::notifyInternal2 (receiver=0x1889e30, event=0x1856df0) at ../../include/QtCore/5.15.0/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #25 0x7f73a2e29531 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x15f91b0) at kernel/qcoreapplication.cpp:1815 #26 0x7f73a2e7e8c3 in postEventSourceDispatch (s=0x16cdb70) at kernel/qeventdispatcher_glib.cpp:277 #27 0x7f73a12e12c7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x7f73a12e1648 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x7f73a12e16ff in g_main_context_iteration () from
[korganizer] [Bug 139959] remember dialogue window position when adding new date
https://bugs.kde.org/show_bug.cgi?id=139959 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from gjditchfi...@acm.org --- KDE can be configured to control many window properties, including size and position. Presently by default the dialog's size is remembered, but the position is not. You can change this by right-clicking the windows title bar and selecting "More Actions" ยป "Configure Special Window Settings". See also the Window Management" tab in System Settings. Does this satisfy your wish? -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 179505] New event dialog properties (size and location) should be saved
https://bugs.kde.org/show_bug.cgi?id=179505 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |DUPLICATE CC||gjditchfi...@acm.org Status|REPORTED|RESOLVED --- Comment #1 from gjditchfi...@acm.org --- *** This bug has been marked as a duplicate of bug 139959 *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 139959] remember dialogue window position when adding new date
https://bugs.kde.org/show_bug.cgi?id=139959 gjditchfi...@acm.org changed: What|Removed |Added CC||geert.po...@skynet.be --- Comment #1 from gjditchfi...@acm.org --- *** Bug 179505 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 423121] New: Adding complete task event in journal doesn't work if task completed via "completed" slider
https://bugs.kde.org/show_bug.cgi?id=423121 Bug ID: 423121 Summary: Adding complete task event in journal doesn't work if task completed via "completed" slider Product: korganizer Version: 5.14.2 Platform: Archlinux Packages OS: All Status: REPORTED Severity: normal Priority: NOR Component: todoview Assignee: kdepim-bugs@kde.org Reporter: derfe...@gmail.com Target Milestone: --- SUMMARY If I complete task by checking the checkbox on it - task completion will be stored in journal. But if I move the slider to the 100%, checkbox will be checked automatically, task will be considered as completed, but no journal entry will be created. STEPS TO REPRODUCE 1. Create task 2. Open it and move "Completed" slider to 100% and save 3. Task will be marked as completed (checkbox checked) 4. Open the Journal OBSERVED RESULT No record about completed task in journal EXPECTED RESULT Record about task completion should be added in journal as it does after checking task's checkbox manually -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 417982] To-do events that are set to all day show up in the previous day
https://bugs.kde.org/show_bug.cgi?id=417982 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/pim/eventviews/-/merge_requests/1 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 421664] Sending email does not work with XOAUTH2
https://bugs.kde.org/show_bug.cgi?id=421664 Aldo Latino changed: What|Removed |Added CC||aldo...@gmail.com --- Comment #2 from Aldo Latino --- I am in the same, exact situation as Vishnu. I am using KDE neon 5.19.1 with latest updates. -- You are receiving this mail because: You are on the CC list for the bug.
[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab
https://bugs.kde.org/show_bug.cgi?id=399570 --- Comment #16 from John Scott --- Created attachment 129456 --> https://bugs.kde.org/attachment.cgi?id=129456=edit New crash information added by DrKonqi akregator (5.14.1 (20.04.0)) using Qt 5.12.5 I still get this on Debian Bullseye, with Akregator and KF5 at 20.04.1. The crash *does* happen for me when manually right-clicking and opening in a new tab, i.e. this doesn't seem to mitigate it as prior comments suggested. I was able to reproduce with JavaScript disabled, and also opening in a Background Tab. What seems to do it for me is clicking a link beneath the title on an /r/netsec post, which you can get the RSS feed like https://www.reddit.com/r/netsec/.rss -- Backtrace (Reduced): #4 0x7f7b6aceb46e in QtWebEngineCore::ProfileAdapter::httpUserAgent() const () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7b6ad178b5 in QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7b6ad1fb8e in QtWebEngineCore::WebContentsDelegateQt::AddNewContents(content::WebContents*, std::unique_ptr >, WindowOpenDisposition, gfx::Rect const&, bool, bool*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7b6c740187 in content::WebContentsImpl::CreateNewWindow(content::RenderFrameHost*, int, int, int, content::mojom::CreateNewWindowParams const&, content::SessionStorageNamespace*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7b6c44d150 in content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr, base::OnceCallback)>) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 --- Comment #17 from John Scott --- Created attachment 129457 --> https://bugs.kde.org/attachment.cgi?id=129457=edit New crash information added by DrKonqi akregator (5.14.1 (20.04.0)) using Qt 5.12.5 I still get this on Debian Bullseye, with Akregator and KF5 at 20.04.1. The crash *does* happen for me when manually right-clicking and opening in a new tab, i.e. this doesn't seem to mitigate it as prior comments suggested. I was able to reproduce with JavaScript disabled, and also opening in a Background Tab. What seems to do it for me is clicking a link beneath the title on an /r/netsec post, which you can get the RSS feed like https://www.reddit.com/r/netsec/.rss -- Backtrace (Reduced): #4 0x7f7b6aceb46e in QtWebEngineCore::ProfileAdapter::httpUserAgent() const () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7b6ad178b5 in QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7b6ad1fb8e in QtWebEngineCore::WebContentsDelegateQt::AddNewContents(content::WebContents*, std::unique_ptr >, WindowOpenDisposition, gfx::Rect const&, bool, bool*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7b6c740187 in content::WebContentsImpl::CreateNewWindow(content::RenderFrameHost*, int, int, int, content::mojom::CreateNewWindowParams const&, content::SessionStorageNamespace*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7b6c44d150 in content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr, base::OnceCallback)>) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab
https://bugs.kde.org/show_bug.cgi?id=399570 John Scott changed: What|Removed |Added CC||jsc...@posteo.net -- You are receiving this mail because: You are the assignee for the bug.
[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab
https://bugs.kde.org/show_bug.cgi?id=399570 --- Comment #16 from John Scott --- Created attachment 129456 --> https://bugs.kde.org/attachment.cgi?id=129456=edit New crash information added by DrKonqi akregator (5.14.1 (20.04.0)) using Qt 5.12.5 I still get this on Debian Bullseye, with Akregator and KF5 at 20.04.1. The crash *does* happen for me when manually right-clicking and opening in a new tab, i.e. this doesn't seem to mitigate it as prior comments suggested. I was able to reproduce with JavaScript disabled, and also opening in a Background Tab. What seems to do it for me is clicking a link beneath the title on an /r/netsec post, which you can get the RSS feed like https://www.reddit.com/r/netsec/.rss -- Backtrace (Reduced): #4 0x7f7b6aceb46e in QtWebEngineCore::ProfileAdapter::httpUserAgent() const () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f7b6ad178b5 in QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f7b6ad1fb8e in QtWebEngineCore::WebContentsDelegateQt::AddNewContents(content::WebContents*, std::unique_ptr >, WindowOpenDisposition, gfx::Rect const&, bool, bool*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f7b6c740187 in content::WebContentsImpl::CreateNewWindow(content::RenderFrameHost*, int, int, int, content::mojom::CreateNewWindowParams const&, content::SessionStorageNamespace*) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f7b6c44d150 in content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr, base::OnceCallback)>) () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[plasmashell] [Bug 423112] After the update of QT to 5.15.0 the calendar highlights yesterday instead of today
https://bugs.kde.org/show_bug.cgi?id=423112 Allen Winter changed: What|Removed |Added Version|5.71.0 |master Product|frameworks-kcalendarcore|plasmashell Assignee|kdepim-bugs@kde.org |plasma-b...@kde.org Target Milestone|--- |1.0 Component|general |Calendar CC||win...@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[frameworks-kcalendarcore] [Bug 423112] New: After the update of QT to 5.15.0 the calendar highlights yesterday instead of today
https://bugs.kde.org/show_bug.cgi?id=423112 Bug ID: 423112 Summary: After the update of QT to 5.15.0 the calendar highlights yesterday instead of today Product: frameworks-kcalendarcore Version: 5.71.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: rauchwo...@gmx.net Target Milestone: --- Created attachment 129452 --> https://bugs.kde.org/attachment.cgi?id=129452=edit picture showing the bug SUMMARY After the update of QT to 5.15.0 the calendar highlights yesterday instead of today STEPS TO REPRODUCE 1. clock on the clock in the taskbar OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 395060] Knotes crash on creating a new note
https://bugs.kde.org/show_bug.cgi?id=395060 --- Comment #1 from vor...@z-ray.de --- Created attachment 129447 --> https://bugs.kde.org/attachment.cgi?id=129447=edit New crash information added by DrKonqi knotes (5.14.2 (20.04.2)) using Qt 5.15.0 - What I was doing when the application crashed: 1) Right click: New Note 2) Selected Folder "Notes" 3) Hit OK 4) Crash -- Backtrace (Reduced): #10 0x7f8ea55dde0d in Akonadi::Item::throwPayloadException (this=0x555fb56e3ee0, spid=0, mtid=12) at /usr/src/debug/akonadi-server-20.04.2-1.1.x86_64/src/core/exceptionbase.h:103 #11 0x7f8ea5633267 in Akonadi::Item::payloadImpl (this=0x555fb56e3ee0) at /usr/include/qt5/QtCore/qarraydata.h:236 #12 Akonadi::Item::payload (this=0x555fb56e3ee0) at /usr/src/debug/akonadi-server-20.04.2-1.1.x86_64/src/core/item.h:848 #13 Akonadi::DefaultItemSerializerPlugin::serialize (this=, item=..., label=..., data=..., version=) at /usr/src/debug/akonadi-server-20.04.2-1.1.x86_64/src/core/itemserializer.cpp:64 #14 0x7f8ea5633c59 in Akonadi::ItemSerializer::serialize (item=..., label=..., data=..., version=@0x7ffd301477d4: 0) at /usr/src/debug/akonadi-server-20.04.2-1.1.x86_64/src/core/itemserializer.cpp:137 -- You are receiving this mail because: You are the assignee for the bug.
[knotes] [Bug 395060] Knotes crash on creating a new note
https://bugs.kde.org/show_bug.cgi?id=395060 vor...@z-ray.de changed: What|Removed |Added CC||vor...@z-ray.de -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 359792] Start Kmail in tray
https://bugs.kde.org/show_bug.cgi?id=359792 Podagric changed: What|Removed |Added CC||kde.podag...@slmail.me --- Comment #4 from Podagric --- Why can't this be added? Non-native email clients, like tutanota-desktop, support this. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 422309] Akonadi dies after suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=422309 --- Comment #2 from Martin van Es --- This is what the mysql.err.old and mysql.err look like after a crash - mysql.err.old 2020-06-15 22:18:22 0 [Note] /usr/sbin/mysqld-akonadi: ready for connections. Version: '10.3.22-MariaDB-1ubuntu1' socket: '/run/user/1000/akonadi/mysql.socket' port: 0 Ubuntu 20.04 2020-06-15 22:18:22 0 [Note] InnoDB: Buffer pool(s) load completed at 200615 22:18:22 2020-06-17 8:24:58 10 [Warning] Aborted connection 10 to db: 'akonadi' user: 'martin' host: '' (Got an error reading communication packets) 2020-06-17 8:24:58 11 [Warning] Aborted connection 11 to db: 'akonadi' user: 'martin' host: '' (Got an error reading communication packets) 2020-06-17 8:24:58 13 [Warning] Aborted connection 13 to db: 'akonadi' user: 'martin' host: '' (Got an error reading communication packets) 2020-06-17 8:24:58 12 [Warning] Aborted connection 12 to db: 'akonadi' user: 'martin' host: '' (Got an error reading communication packets) 2020-06-17 8:24:58 38 [Warning] Aborted connection 38 to db: 'akonadi' user: 'martin' host: '' (Got an error reading communication packets) - mesql.err 2020-06-17 8:26:04 0 [ERROR] mysqld-akonadi: Can't lock aria control file '/home/martin/.local/share/akonadi/db_data/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds 2020-06-17 8:26:35 0 [ERROR] mysqld-akonadi: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/home/martin/.local/share/akonadi/db_data/aria_log_control' 2020-06-17 8:26:35 0 [ERROR] Plugin 'Aria' init function returned error. 2020-06-17 8:26:35 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 2020-06-17 8:26:35 0 [Note] InnoDB: Using Linux native AIO 2020-06-17 8:26:35 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-06-17 8:26:35 0 [Note] InnoDB: Uses event mutexes 2020-06-17 8:26:35 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-06-17 8:26:35 0 [Note] InnoDB: Number of pools: 1 2020-06-17 8:26:35 0 [Note] InnoDB: Using SSE2 crc32 instructions 2020-06-17 8:26:35 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 2020-06-17 8:26:35 0 [Note] InnoDB: Completed initialization of buffer pool 2020-06-17 8:26:35 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2020-06-17 8:26:35 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2020-06-17 8:26:35 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. 2020-06-17 8:26:35 0 [Note] InnoDB: Retrying to lock the first data file 2020-06-17 8:26:36 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11 2020-06-17 8:26:36 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files. ... -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 421664] Sending email does not work with XOAUTH2
https://bugs.kde.org/show_bug.cgi?id=421664 Sebastian Kuhne changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com -- You are receiving this mail because: You are on the CC list for the bug.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #133 from Vishnu --- Opened a report for that: https://bugs.kde.org/show_bug.cgi?id=421664 -- You are receiving this mail because: You are the assignee for the bug.
