Summary: | Crash if I close kolourpaint when the acquire screenshot dialog is open | ||
---|---|---|---|
Product: | [Applications] kolourpaint | Reporter: | Santhiar <santhiar.anirudh> |
Component: | general | Assignee: | kolourpaint-support |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | kollix |
Priority: | NOR | ||
Version: | 4.13.1 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Screenshot showing that dialogs are not application modal |
Description
Santhiar
2015-11-29 05:01:42 UTC
This scenario will crash kolourpaint with any open dialog. But since the dialog is application modal, this scenario should never happen on normal usage, since you can not activate the application quit menu while the modal dialog is open. How did you hit this problem ? Or are you just testing what happens if you do nasty things ? (I assume you can crash a lot of other applications this way) Created attachment 95813 [details]
Screenshot showing that dialogs are not application modal
That's true, but usually the crash is because of a seg-fault/freeing memory that wasn't malloc'd. The scenarios that lead to a use after free are quitting kolourpaint with a print dialog open or the acquire screenshot dialog open. Weirdly enough, the kolourpaint () I installed via apt-get in Ubuntu 12.04 does not use application modal dialogs (please see the attached screenshot) -- which is how I ran into the problem. Here are its version details: Qt: 4.8.6 KDE Development Platform: 4.13.3 KolourPaint: 4.13.1 I then investigated kolourpaint 4.14.13 built from source - here, the dialogs are application modal - I was curious to see whether I could still crash the app, which is why I quit it using qdbus. And yes, you are right, you can crash a lot of other applications this way. Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |