[kontact] [Bug 471944] New: Kontact crashed while trying to enable calendars in KOrganizer
https://bugs.kde.org/show_bug.cgi?id=471944
Bug ID: 471944
Summary: Kontact crashed while trying to enable calendars in
KOrganizer
Classification: Applications
Product: kontact
Version: unspecified
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: vend...@gmail.com
Target Milestone: ---
Application: kontact (5.23.2 (23.04.2))
Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.4.1-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.6 [KCrashBackend]
-- Information about the crash:
In KOrganizer I have several calendars setup that live on Google Calendar. When
I opened up KOrganizer both my Google accounts and the associated calendars
were not displayed in the UI, only the default "Birthdays & Anniversaries" and
the "Search" options were listed. To fix this I went to Settings -> Configure
KOrganizer -> Calendars -> (Select one of my two Google Accounts) -> Modify.
Once that page loaded my calendars got refreshed and the account and the
associated calendars were once again visible in the UI. Unfortunatley while the
calendars where syncing Kontact crashed.
The crash can be reproduced sometimes.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7fa08c3fbbd7 in
EventViews::AgendaView::calendar2(QSharedPointer
const&) const (this=, incidence=) at
/usr/src/debug/eventviews/eventviews-23.04.2/src/agenda/agendaview.cpp:1227
#7 0x7fa08c406c63 in
EventViews::AgendaView::displayIncidence(QSharedPointer
const&, bool) (this=this@entry=0x55faca8dd150, incidence=...,
createSelected=createSelected@entry=false) at
/usr/src/debug/eventviews/eventviews-23.04.2/src/agenda/agendaview.cpp:1981
#8 0x7fa08c40865f in EventViews::AgendaView::fillAgenda()
(this=0x55faca8dd150) at
/usr/src/debug/eventviews/eventviews-23.04.2/src/agenda/agendaview.cpp:1947
#9 0x7fa1046d06a7 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fffa32bd240, r=, this=0x55faca9472a0, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#10 doActivate(QObject*, int, void**) (sender=0x7fa0c0043620,
signal_index=7, argv=0x7fffa32bd240) at kernel/qobject.cpp:3925
#11 0x7fa078225310 in CalendarView::updateConfig() (this=0x7fa0c0043620) at
/usr/src/debug/korganizer/korganizer-23.04.2/src/calendarview.cpp:555
#12 0x7fa1046d06a7 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fffa32bd330, r=, this=0x55facaabf300, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate(QObject*, int, void**) (sender=0x55facaa2d720,
signal_index=12, argv=0x7fffa32bd330) at kernel/qobject.cpp:3925
#14 0x7fa10596ee3e in KCMultiDialogPrivate::apply() (this=)
at /usr/src/debug/kcmutils/kcmutils-5.107.0/src/kcmultidialog.cpp:404
#15 0x7fa10596ef13 in KCMultiDialog::slotOkClicked() (this=0x55facaa2d720)
at /usr/src/debug/kcmutils/kcmutils-5.107.0/src/kcmultidialog.h:31
#16 0x7fa1046d06a7 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fffa32bd4e0, r=, this=0x55facad40b10, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#17 doActivate(QObject*, int, void**) (sender=0x55facaac5c30,
signal_index=9, argv=0x7fffa32bd4e0) at kernel/qobject.cpp:3925
#18 0x7fa10545c357 in QAbstractButton::clicked(bool)
(this=this@entry=0x55facaac5c30, _t1=) at
.moc/moc_qabstractbutton.cpp:308
#19 0x7fa10545ec0a in QAbstractButtonPrivate::emitClicked()
(this=this@entry=0x55facaac5c70) at widgets/qabstractbutton.cpp:416
#20 0x7fa10546010c in QAbstractButtonPrivate::click() (this=0x55facaac5c70)
at widgets/qabstractbutton.cpp:409
#21 0x7fa1054602b0 in QAbstractButton::mouseReleaseEvent(QMouseEvent*)
(this=0x55facaac5c30, e=0x7fffa32bda60) at widgets/qabstractbutton.cpp:1045
#22 0x7fa1053af1e1 in QWidget::event(QEvent*) (this=0x55facaac5c30,
event=0x7fffa32bda60) at kernel/qwidget.cpp:8671
#23 0x7fa10537893f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x55fac40751b0, receiver=receiver@entry=0x55facaac5c30,
e=e@entry=0x7fffa32bda60) at kernel/qapplication.cpp:3640
#24 0x7fa10537ddef in QApplication::notify(QObject*, QEvent*)
(this=, receiver=0x55facaac5c30, e=0x7fffa32bda60) at
kernel/qapplication.cpp:3084
#25 0x7fa10469b778 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55facaac5c30, event=0x7fffa32bda60) at
kernel/qcoreapplication.cpp:1064
#26 0x7fa10469b803 in QCoreApplication::sendSpontaneousEvent(QObject*,
QEvent*) (receiver=, event=) at
kernel/qcoreapplication.cpp:1474
#27 0x7fa10537c12a in
[kmail2] [Bug 471911] Fetch new key automatically if a key is expired
https://bugs.kde.org/show_bug.cgi?id=471911 --- Comment #2 from Andre Heinecke --- I have referred this in our task to update the key selection dialog in KMail so that we keep it in mind there. In that keyresolver this might already have been fixed. https://dev.gnupg.org/T6198 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 471911] Fetch new key automatically if a key is expired
https://bugs.kde.org/show_bug.cgi?id=471911 Andre Heinecke changed: What|Removed |Added CC||aheine...@gnupg.org --- Comment #1 from Andre Heinecke --- If you look in Kleopatra under the column "source". Does it say WKD? In that case GnuPG should do this, sadly it does not do it automatically but only if we retrigger a --locate-key so KMail might have to do that. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 452296] Email won't be encrypted automatically
https://bugs.kde.org/show_bug.cgi?id=452296 Andre Heinecke changed: What|Removed |Added Resolution|--- |WORKSFORME CC||aheine...@gnupg.org Status|REPORTED|RESOLVED --- Comment #1 from Andre Heinecke --- This works as intended for me. If encryption is possible, meaning that for every recipient there is a valid encryption key found the encryption is automatically toggled. That was the intention of that feature. I think you are looking for something like "Always encrypt" which would then bring up the keyselection dialog in case no keys were found. I am not sure if there is such an option but you can maybe achive this by changing your address book entry to always encrypt for you. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 471933] New: akonadi crash on logout
https://bugs.kde.org/show_bug.cgi?id=471933 Bug ID: 471933 Summary: akonadi crash on logout Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: joerg.bornem...@qt.io CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.22.3 (22.12.3)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-9-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: I was logging out. The logout timer started to run. I was pressing the logout button maybe twice to accelerate the logout procedure. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x5589a61a41cc in ?? () #5 0x7f3c2c8dd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3c2c8b16cd in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3c2c8b4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3c2c90a153 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f3c2b11e7a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f3c2b11ea38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f3c2b11eacc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f3c2c909836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f3c2c8b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f3c2c8b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x5589a61a1450 in ?? () #16 0x7f3c2c44618a in __libc_start_call_main (main=main@entry=0x5589a61a1150, argc=argc@entry=1, argv=argv@entry=0x7ffc2b1667b8) at ../sysdeps/nptl/libc_start_call_main.h:58 #17 0x7f3c2c446245 in __libc_start_main_impl (main=0x5589a61a1150, argc=1, argv=0x7ffc2b1667b8, init=, fini=, rtld_fini=, stack_end=0x7ffc2b1667a8) at ../csu/libc-start.c:381 #18 0x5589a61a3c81 in ?? () [Inferior 1 (process 52440) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 433253] Folder list shows unread messages but filter doesn't
https://bugs.kde.org/show_bug.cgi?id=433253 Gaël de Chalendar (aka Kleag) changed: What|Removed |Added Platform|Ubuntu |Neon Status|REPORTED|CONFIRMED Version|5.15.1 |5.23.2 Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 433253] Folder list shows unread messages but filter doesn't
https://bugs.kde.org/show_bug.cgi?id=433253 Gaël de Chalendar (aka Kleag) changed: What|Removed |Added CC||kle...@gmail.com --- Comment #2 from Gaël de Chalendar (aka Kleag) --- Created attachment 160071 --> https://bugs.kde.org/attachment.cgi?id=160071=edit Another occurrence of the bug I also encounter this bug from time to time. Don't know how I made it disappear previous times. Some random things with akonadi I suppose. The backend is EWS connector. Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 5.19.0-46-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8650U CPU @ 1.90GHz Memory: 31.2 Gio of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: Latitude 5590 -- You are receiving this mail because: You are the assignee for the bug.
