[kmail2] [Bug 385020] KMail2 does not wait for unlocking of KWallet
https://bugs.kde.org/show_bug.cgi?id=385020 Ryan McCoskrie changed: What|Removed |Added CC||w...@ryanmccoskrie.me Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #5 from Ryan McCoskrie --- This bug is happening on my laptop in 2023, desktop is fine. Both are using Fedora. Any hints on how I can collect relevant information? -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473615] New: Crash after moving email
https://bugs.kde.org/show_bug.cgi?id=473615 Bug ID: 473615 Summary: Crash after moving email Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: piotr.mierzwin...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.24.40 (23.11.40)) Qt Version: 6.6.0 Frameworks Version: 5.240.0 Operating System: Linux 6.2.0-26-generic x86_64 Windowing System: Wayland Distribution: KDE neon Unstable Edition DrKonqi: 5.27.80 [CoredumpBackend] -- Information about the crash: I just moved email from one folder to another. In result appeared crash. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x0) at /usr/include/c++/11/bits/atomic_base.h:486 #7 QAtomicOps::loadRelaxed (_q_value=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239 #8 QBasicAtomicInteger::loadRelaxed (this=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107 [...] #10 QByteArray::QByteArray (a=..., this=0x7f2d9d7f93e0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbytearray.h:525 #11 Akonadi::Protocol::PartMetaData::PartMetaData (this=0x7f2d9d7f93e0) at ./obj-x86_64-linux-gnu/src/private/protocol_gen.h:171 Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473615] Crash after moving email in KMail
https://bugs.kde.org/show_bug.cgi?id=473615 Piotr Mierzwinski changed: What|Removed |Added Summary|Crash after moving email|Crash after moving email in ||KMail CC||piotr.mierzwin...@gmail.com Keywords||qt6, wayland -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473615] Crash after moving email
https://bugs.kde.org/show_bug.cgi?id=473615 --- Comment #1 from Piotr Mierzwinski --- Created attachment 161099 --> https://bugs.kde.org/attachment.cgi?id=161099=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 460186] Timezone not synced correctly for daylight savings in country without DST
https://bugs.kde.org/show_bug.cgi?id=460186 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/pim/kcalutils/-/merge_requests/28 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 473610] New: Kalender eintrag
https://bugs.kde.org/show_bug.cgi?id=473610 Bug ID: 473610 Summary: Kalender eintrag Classification: Applications Product: kontact Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: petry-pohlhe...@t-online.de Target Milestone: --- Application: kontact (5.23.3 (23.04.3)) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.4.9-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: Bei einem Eintrag für den Kalender und Teilnehmer die per E-Mail eingeladen wurden, stürtze die Anwendung ab The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f15e12bc072 in QSortFilterProxyModel::parent(QModelIndex const&) const () from /lib64/libQt5Core.so.5 #5 0x7f15e12872af in QPersistentModelIndex::parent() const () from /lib64/libQt5Core.so.5 #6 0x7f15e129b073 in ?? () from /lib64/libQt5Core.so.5 #7 0x7f15e12a249c in ?? () from /lib64/libQt5Core.so.5 #8 0x7f15e13257b3 in ?? () from /lib64/libQt5Core.so.5 #9 0x7f15e12862e6 in QAbstractItemModel::layoutChanged(QList const&, QAbstractItemModel::LayoutChangeHint) () from /lib64/libQt5Core.so.5 #10 0x7f15e12be6d6 in ?? () from /lib64/libQt5Core.so.5 #11 0x7f15e13257b3 in ?? () from /lib64/libQt5Core.so.5 #12 0x7f15e12862e6 in QAbstractItemModel::layoutChanged(QList const&, QAbstractItemModel::LayoutChangeHint) () from /lib64/libQt5Core.so.5 #13 0x7f157879393a in ?? () from /lib64/libKPim5IncidenceEditor.so.5 #14 0x7f157878420a in ?? () from /lib64/libKPim5IncidenceEditor.so.5 #15 0x7f15787d3cb3 in ?? () from /lib64/libKPim5IncidenceEditor.so.5 #16 0x7f15787879b5 in ?? () from /lib64/libKPim5IncidenceEditor.so.5 #17 0x7f15e1325812 in ?? () from /lib64/libQt5Core.so.5 #18 0x7f15e2695845 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #19 0x7f15e2699beb in ?? () from /lib64/libKF5CoreAddons.so.5 #20 0x7f15e1319320 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f15e1fa519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x7f15e12ed568 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #23 0x7f15e12f0b61 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #24 0x7f15e1346c93 in ?? () from /lib64/libQt5Core.so.5 #25 0x7f15d7b169b8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #26 0x7f15d7b16dc8 in ?? () from /lib64/libglib-2.0.so.0 #27 0x7f15d7b16e5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #28 0x7f15e13464a6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #29 0x7f15e12ebffb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #30 0x7f15e12f4490 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #31 0x561e370e8fe3 in ?? () #32 0x7f15e08281f0 in __libc_start_call_main () from /lib64/libc.so.6 #33 0x7f15e08282b9 in __libc_start_main_impl () from /lib64/libc.so.6 #34 0x561e370e9625 in ?? () [Inferior 1 (process 21296) detached] Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 473593] New: Ability to mark calendars as read-only independent of backend
https://bugs.kde.org/show_bug.cgi?id=473593 Bug ID: 473593 Summary: Ability to mark calendars as read-only independent of backend Classification: Frameworks and Libraries Product: Akonadi Version: 5.23.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: fisc...@unix-ag.uni-kl.de CC: c...@carlschwan.eu Target Milestone: --- Currently, the UI (e.g. Akonadi Console, "Folder Properties" on a calendar) offers no option to mark a calendar as read-only, i.e. to disallow changes or removal of events or adding new events. This should be implemented independent of the backend, irrespective of whether it is a local calendar or a DAV resource. Background: in my groupware server account, I have several calendars: one for events I maintain (add/edit events) and several that are subscriptions to external calendar feeds which are read-only. Either the groupware server does not relay the information which calendars are read-only, or Akonadi does not interpret this information correctly. At least in KOrganizer, changes can be made to calendars that are technically read-only. To block those changes, the user should have the choice to mark a calendar read-only even if changes are technically possible, e.g. to avoid accidental changes to calendars. The Folder Properties dialog has a "ACL" tab, but it warns to make changes here. Even if my request can be "solved" by making changes here, it sounds like a dangerous path and it deters users from making the changes. Instead, there should be a simple checkbox in the "General" tab next to the "custom icon" setting that allows the user to make the calendar read-only (or not). -- You are receiving this mail because: You are the assignee for the bug.
[libkgapi] [Bug 473592] Some contacts in Google "My contacts" do not show up in kmail address autocomplete
https://bugs.kde.org/show_bug.cgi?id=473592 --- Comment #2 from Martin Tlustos --- I just found that Google Contacts shows that I have 2095 contacts, while akonadi console only shows 2070 contacts. -- You are receiving this mail because: You are on the CC list for the bug.
[libkgapi] [Bug 473592] Some contacts in Google "My contacts" do not show up in kmail address autocomplete
https://bugs.kde.org/show_bug.cgi?id=473592 --- Comment #1 from Martin Tlustos --- Oh, and they don't show up in kcontact either. -- You are receiving this mail because: You are on the CC list for the bug.
[libkgapi] [Bug 473592] New: Some contacts in Google "My contacts" do not show up in kmail address autocomplete
https://bugs.kde.org/show_bug.cgi?id=473592 Bug ID: 473592 Summary: Some contacts in Google "My contacts" do not show up in kmail address autocomplete Classification: Frameworks and Libraries Product: libkgapi Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: contacts Assignee: dvra...@kde.org Reporter: martin.tlus...@gmail.com CC: kdepim-bugs@kde.org Target Milestone: --- SUMMARY That's pretty much it. I have a lot of contacts that don't show up in my autocomplete when typing the beginning of the name. Like, my wife! ;-) I have a lot of contacts in my google account (over 2.000), so that might be a factor. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. open kmail - new message 2. type a name of a person that is in an activated google contact list 3. OBSERVED RESULT Person does not show up in autocomplete EXPECTED RESULT Person should show up in autocomplete SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.2.0-26-generic (64-bit) Graphics Platform: X11 Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Acer Product Name: Aspire A515-44G System Version: V1.12 -- You are receiving this mail because: You are on the CC list for the bug.
