Bug 337903

Summary: graphically unmanaged areas in dockwidgets after debugging
Product: [Applications] kdevelop Reporter: jhnnslschnr
Component: UI: childframe windowAssignee: kdevelop-bugs-null
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version First Reported In: 4.6.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description jhnnslschnr 2014-07-30 12:29:27 UTC
After debugging (after closing the app, which causes kdevelop to return to code view) some areas in dockwidgets, for example the project view, are graphically unmanaged (mostly black, moving them around can change their content) and ignore mouse input.
Comment 1 jhnnslschnr 2014-08-06 10:16:07 UTC
I have to correct myself, the widgets still work normally when this bug occurs, including mouse and keyboard input, but the graphics are corrupted as i described. This bug does not always occur after debug view, but about half the time. Going to debug view an returning to code once again view does not fix it, so debugging a few times makes all dock widgets graphically corrupted, until i restart KDevelop.
Comment 2 Andrew Crouthamel 2018-11-12 02:52:18 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-21 04:35:39 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 jhnnslschnr 2018-12-02 13:45:43 UTC
Thanks for the friendly reminder.
This bug seems to be resolved.