Summary: | Crash in KDatePicker selectYearClicked() | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Guillermo Belli <gbelli> |
Component: | kdeui | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | alexandreracine, andresbajotierra, bugs, cfeck, kde-bugs, quantumbro, rtavenar |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Guillermo Belli
2009-01-29 18:10:42 UTC
*** Bug 189002 has been marked as a duplicate of this bug. *** *** Bug 189217 has been marked as a duplicate of this bug. *** SVN commit 952794 by cfeck: Fix crash in KDatePicker selectYearClicked() Revert r834444. Use an event handler to catch outside clicks instead. Reviewed by aacid BUG: 182325 M +1 -12 kdatepicker.cpp M +0 -1 kdatepicker.h M +54 -6 kdatetable.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=952794 SVN commit 952798 by cfeck: Fix crash in KDatePicker selectYearClicked() (backport r952794) CCBUG: 182325 M +1 -12 kdatepicker.cpp M +0 -1 kdatepicker.h M +54 -6 kdatetable.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=952798 *** Bug 189928 has been marked as a duplicate of this bug. *** SVN commit 956274 by sedwards: Restore binary compatibility after commit 952798 . Protected Q_SLOT uncheckYearSelector() should not be removed. CCBUG: 182325 CCMAIL: christoph@maxiom.de M +7 -0 kdatepicker.cpp M +1 -0 kdatepicker.h WebSVN link: http://websvn.kde.org/?view=rev&revision=956274 SVN commit 956275 by sedwards: Restore binary compatibility after commit 952794 . Protected Q_SLOT uncheckYearSelector() should not be removed. CCBUG: 182325 CCMAIL: christoph@maxiom.de M +6 -0 kdatepicker.cpp M +1 -0 kdatepicker.h WebSVN link: http://websvn.kde.org/?view=rev&revision=956275 *** Bug 198010 has been marked as a duplicate of this bug. *** Bug 198010 is reported for KDE4.2.4 (but the fix included here should have been applied to 4.2.4 already); could it be a different issue? Thanks *** Bug 202099 has been marked as a duplicate of this bug. *** |