Bug 495848 - Korganizer crash when I want to add new event or open existing event
Summary: Korganizer crash when I want to add new event or open existing event
Status: ASSIGNED
Alias: None
Product: korganizer
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: HI crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
: 485950 492807 499153 500188 505086 506417 508427 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-11-05 17:32 UTC by emi.caruso
Modified: 2025-08-18 15:45 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (84.00 KB, text/plain)
2024-11-05 17:32 UTC, emi.caruso
Details

Note You need to log in before you can comment on or make changes to this bug.
Description emi.caruso 2024-11-05 17:32:21 UTC
Application: korganizer (6.2.2 (24.08.2))

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.0
Frameworks Version: 6.7.0
Operating System: Linux 6.8.0-48-generic x86_64
Windowing System: Wayland
Distribution: KDE neon 6.2
DrKonqi: 6.2.2 [CoredumpBackend]

-- Information about the crash:
Korganizer crash (window closed) when you want to add new event or new task or new journal or open existing event.
Liste of existing event get from my previous LFS (KDE compiled by myself) and added to my new KDE Neon distribution.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#6  __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#7  __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#8  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#9  0x000078abcd84526e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#10 0x000078abcd8288ff in __GI_abort () at ./stdlib/abort.c:79


Reported using DrKonqi
Comment 1 emi.caruso 2024-11-05 17:32:22 UTC
Created attachment 175559 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Allen Winter 2025-02-16 15:43:18 UTC
*** Bug 499153 has been marked as a duplicate of this bug. ***
Comment 3 Allen Winter 2025-02-16 15:44:24 UTC
*** Bug 500188 has been marked as a duplicate of this bug. ***
Comment 4 Allen Winter 2025-02-22 21:30:30 UTC
I'm unable to reproduce these crashes

I need hints on how to reproduce the crashes or other info to help me debug
I'm testing with KOrganizer 6.3, if that matters
Comment 5 Allen Winter 2025-02-23 20:09:16 UTC
*** Bug 492807 has been marked as a duplicate of this bug. ***
Comment 6 Carlos De Maine 2025-03-03 00:37:41 UTC
can confirm this on latest user korg package
Comment 7 emi.caruso 2025-03-29 16:54:13 UTC
(In reply to Allen Winter from comment #4)
> I'm unable to reproduce these crashes
> 
> I need hints on how to reproduce the crashes or other info to help me debug
> I'm testing with KOrganizer 6.3, if that matters

Hi,

Some information from GDB.

The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.             
org.kde.pim.incidenceeditor: Faulty editor was  "IncidenceAttendee"
org.kde.pim.incidenceeditor: Incidence  "643f089a-6a76-4691-8093-cd89d0694033"
ASSERT failure in load: "editor shouldn't be dirty", file ./src/combinedincidenceeditor.cpp, line 93

Thread 1 "korganizer" received signal SIGABRT, Aborted.
Download failed: Argument invalide.  Continuing without source file ./nptl/./nptl/pthread_kill.c.
__pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
warning: 44     ./nptl/pthread_kill.c: Aucun fichier ou dossier de ce nom
Comment 8 Allen Winter 2025-03-29 18:59:58 UTC
yes, but I'm unable to reproduce.  

are you using neon too? 

which KDE versions and Qt version?
Comment 9 emi.caruso 2025-03-30 07:56:44 UTC
(In reply to Allen Winter from comment #8)
> yes, but I'm unable to reproduce.  
> 
> are you using neon too? 
> 
> which KDE versions and Qt version?

I'm using KDE Neon 6.3.

KDE plasma is 6.3, KDE frameworks 6.12.0 and Qt 6.8.2.

I use KDE Neon since begin of 2024 and this bug exist for me since the beginning (or may be after the last LTS update).(In reply to Allen Winter from comment #8)
> yes, but I'm unable to reproduce.  
> 
> are you using neon too? 
> 
> which KDE versions and Qt version?

I'm using KDE Neon 6.3.

KDE plasma is 6.3, KDE frameworks 6.12.0 and Qt 6.8.2.

I use KDE Neon since begin of 2024 and this bug exist for me since the beginning (or may be after the last LTS update).

In this method,  "editor->load(incidence);" is alway dirty !!!

void CombinedIncidenceEditor::load(const KCalendarCore::Incidence::Ptr &incidence)
{
    mLoadedIncidence = incidence;
    for (IncidenceEditor *editor : std::as_const(mCombinedEditors)) {
        // load() may fire dirtyStatusChanged(), reset mDirtyEditorCount to make sure
        // we don't end up with an invalid dirty count.
        editor->blockSignals(true);
        editor->load(incidence);
        editor->blockSignals(false);
 
        if (editor->isDirty()) {
            // We are going to crash due to assert. Print some useful info before crashing.
            qCWarning(INCIDENCEEDITOR_LOG) << "Faulty editor was " << editor->objectName();
            qCWarning(INCIDENCEEDITOR_LOG) << "Incidence " << (incidence ? incidence->uid() : QStringLiteral("null"));
 
            editor->printDebugInfo();
 
            Q_ASSERT_X(false, "load", "editor shouldn't be dirty");
        }
    }
 
    mWasDirty = false;
    mDirtyEditorCount = 0;
    Q_EMIT dirtyStatusChanged(false);
}
Comment 10 Allen Winter 2025-06-01 13:07:38 UTC
a couple months later...

since KOrganizer 6.4 are you still experiencing this crash?

only Neon users reported this one
Comment 11 emi.caruso 2025-06-07 09:16:50 UTC
(In reply to Allen Winter from comment #10)
> a couple months later...
> 
> since KOrganizer 6.4 are you still experiencing this crash?
> 
> only Neon users reported this one

Hi

Actually, I use Korganizer 6.4.2 and still same crash when I want to add event. I checked this crash with GDB and find that crash appears in below function "if (editor->isDirty())" but code is too complicated for me to follow why this append.


void CombinedIncidenceEditor::load(const KCalendarCore::Incidence::Ptr &incidence)
{
    mLoadedIncidence = incidence;
    for (IncidenceEditor *editor : std::as_const(mCombinedEditors)) {
        // load() may fire dirtyStatusChanged(), reset mDirtyEditorCount to make sure
        // we don't end up with an invalid dirty count.
        editor->blockSignals(true);
        editor->load(incidence);
        editor->blockSignals(false);
 
        if (editor->isDirty()) {
            // We are going to crash due to assert. Print some useful info before crashing.
            qCWarning(INCIDENCEEDITOR_LOG) << "Faulty editor was " << editor->objectName();
            qCWarning(INCIDENCEEDITOR_LOG) << "Incidence " << (incidence ? incidence->uid() : QStringLiteral("null"));
 
            editor->printDebugInfo();
 
            Q_ASSERT_X(false, "load", "editor shouldn't be dirty");
        }
    }
Comment 12 Allen Winter 2025-06-07 16:09:49 UTC
I installed the KDE Neon ISO into a virtual machine (virtualbox).
Then I tried to start Kontact and noticed it wasn't included with Neon.
Then I started discover and installed Kontact 

start Kontact. switch to KOrganizer part
Now I add my Google calendar

and then Add New Event from the menu.
and I encounter the same assert as reported by  emi.caruso@free.fr , et.al

somehow the Qt signal block is not working here
Comment 13 Allen Winter 2025-06-08 18:52:54 UTC
*** Bug 505086 has been marked as a duplicate of this bug. ***
Comment 14 Bug Janitor Service 2025-06-08 19:33:45 UTC
A possibly relevant merge request was started @ https://invent.kde.org/pim/incidenceeditor/-/merge_requests/69
Comment 15 Allen Winter 2025-07-02 16:50:09 UTC
*** Bug 506417 has been marked as a duplicate of this bug. ***
Comment 16 Allen Winter 2025-07-02 17:02:56 UTC
*** Bug 485950 has been marked as a duplicate of this bug. ***
Comment 17 Allen Winter 2025-08-18 15:45:08 UTC
*** Bug 508427 has been marked as a duplicate of this bug. ***