Summary: | Event drag and drop from today to any another day does not work. | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Sabine Faure <sabine> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | montel, smartins |
Priority: | LO | ||
Version: | 4.3 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Crash backtrace after retesting drag and dropping an event to another day.
Kontact is still crashing when trying to drag and drop an event. Trunk, Svn Rev 1092481 |
Description
Sabine Faure
2010-01-28 01:35:29 UTC
I confirm this bug. I will look at it. Problem is in koagenda.cpp comment #2 was not for this bug. Ignore it korganizer(17873) KODayMatrix::dropEvent: AKONADI PORT: Disabled code in virtual void KODayMatrix::dropEvent(QDropEvent*) dnd is not ported. So we need to do it. Regards I ported it in trunk. Need to fix some little bugs yet. Created attachment 40509 [details]
Crash backtrace after retesting drag and dropping an event to another day.
I retested this today.
It worked once but most of the time I get a crash (see backtrace attached) and the event is not moved.
Trunk, Svn Rev 1084694
Hi, Yesterday I fixed a crash in dnd. Could you look at if it fixes your crash please ? Thanks Regards Created attachment 40931 [details]
Kontact is still crashing when trying to drag and drop an event. Trunk, Svn Rev 1092481
I retested this today.
And Kontact/KOrganizer still crashes when trying to drag and drop an event to another day.
Trunk, Svn Rev 1092481
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |