Bug 249028 - If an Import dialog is open in KOrganizer and you double-click an .ics file, KOrganizer will crash
Summary: If an Import dialog is open in KOrganizer and you double-click an .ics file, ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 0.9
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-25 20:03 UTC by Daniel Buus
Modified: 2017-01-07 22:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Buus 2010-08-25 20:03:49 UTC
Version:           0.9 (using KDE 4.4.5) 
OS:                Linux



Reproducible: Didn't try

Steps to Reproduce:
Open Kontact
Go to Calendar
Open File > Import > Import Calendar
Open Dolphin
Find an .ics file and double-click it
Focus will shift to KOrganizer
Close the Import file dialog


Actual Results:  
KOrganizer & Kontact crash

Expected Results:  
They would not crash

OS: Linux (x86_64) release 2.6.34-zen1-zen
Compiler: cc
Comment 1 Sergio Martins 2010-12-31 03:40:44 UTC
==10409== Invalid write of size 1
==10409==    at 0xB180213: QBoolBlocker::~QBoolBlocker() (qobject_p.h:277)
==10409==    by 0xB1F0388: QMenuPrivate::activateCausedStack(QList<QPointer<QWidget> > const&, QAction*, QAction::ActionEvent, bool) (qmenu.cpp:988)
==10409==    by 0xB1F0674: QMenuPrivate::activateAction(QAction*, QAction::ActionEvent, bool) (qmenu.cpp:1085)
==10409==    by 0xB1F484F: QMenu::mouseReleaseEvent(QMouseEvent*) (qmenu.cpp:2306)
==10409==    by 0xA684658: KMenu::mouseReleaseEvent(QMouseEvent*) (kmenu.cpp:458)
==10409==    by 0xACE5153: QWidget::event(QEvent*) (qwidget.cpp:8255)
==10409==    by 0xB1F4F15: QMenu::event(QEvent*) (qmenu.cpp:2415)
==10409==    by 0xAC7E64F: QApplicationPrivate::notify_helper(QObject*, QEvent*) (qapplication.cpp:4462)
==10409==    by 0xAC7C5DC: QApplication::notify(QObject*, QEvent*) (qapplication.cpp:4023)
==10409==    by 0xA5C7335: KApplication::notify(QObject*, QEvent*) (kapplication.cpp:311)
==10409==    by 0xC31CDC2: QCoreApplication::notifyInternal(QObject*, QEvent*) (qcoreapplication.cpp:731)
==10409==    by 0xAC80E32: QCoreApplication::sendSpontaneousEvent(QObject*, QEvent*) (in /data/installation/qt/qt-4.7/lib/libQtGui.so.4.7.1)
==10409==  Address 0x253794a9 is 537 bytes inside a block of size 736 free'd
==10409==    at 0x4C23F8E: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==10409==    by 0xB1F9553: QMenuPrivate::~QMenuPrivate() (qmenu_p.h:183)
==10409==    by 0xC2E4F8D: QScopedPointerDeleter<QObjectData>::cleanup(QObjectData*) (qscopedpointer.h:62)
==10409==    by 0xC33C72A: QScopedPointer<QObjectData, QScopedPointerDeleter<QObjectData> >::~QScopedPointer() (qscopedpointer.h:100)
==10409==    by 0xC33510A: QObject::~QObject() (qobject.cpp:818)
==10409==    by 0xACD3318: QWidget::~QWidget() (qwidget.cpp:1504)
==10409==    by 0xB1F14EF: QMenu::~QMenu() (qmenu.cpp:1391)
==10409==    by 0xA683988: KMenu::~KMenu() (kmenu.cpp:167)
==10409==    by 0xA6B5D9D: KXMLGUIBuilder::removeContainer(QWidget*, QWidget*, QDomElement&, QAction*) (kxmlguibuilder.cpp:276)
==10409==    by 0xA6C5752: KXMLGUI::ContainerNode::destruct(QDomElement, KXMLGUI::BuildState&) (kxmlguifactory_p.cpp:347)
==10409==    by 0xA6C5813: KXMLGUI::ContainerNode::destructChildren(QDomElement const&, KXMLGUI::BuildState&) (kxmlguifactory_p.cpp:371)
==10409==    by 0xA6C5677: KXMLGUI::ContainerNode::destruct(QDomElement, KXMLGUI::BuildState&) (kxmlguifactory_p.cpp:326)
Comment 2 Jaime Torres 2011-09-09 16:12:09 UTC
Probably a Qt bug, the valgrind output is quite similar to what I've go in bug 278366.
Comment 3 Denis Kurz 2016-09-24 18:49:03 UTC
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.
Comment 4 Denis Kurz 2017-01-07 22:47:06 UTC
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.