Bug 443217

Summary: Bug trying to change widget settings
Product: [Plasma] Active Window Control Reporter: Artur <mister-park>
Component: GeneralAssignee: Chris Holland <zrenfire>
Status: RESOLVED DUPLICATE    
Severity: minor CC: nate, plasma-bugs
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian unstable   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Video demonstrathion

Description Artur 2021-10-02 07:15:32 UTC
Created attachment 142079 [details]
Video demonstrathion

SUMMARY
Artur Navitanyuk:Bug trying to change widget settings

STEPS TO REPRODUCE
1. Right Mouse click on top panel
2. Click on "Edit panel"
3. User should try to click on "Configure" in widget

OBSERVED RESULT
Hard to hit the "Configure" button

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Artur 2021-10-02 09:12:50 UTC
(In reply to Artur from comment #0)
> Created attachment 142079 [details]
> Video demonstrathion
> 
> SUMMARY
> Artur Navitanyuk:Bug trying to change widget settings
> 
> STEPS TO REPRODUCE
> 1. Right Mouse click on top panel
> 2. Click on "Edit panel"
> 3. User should try to click on "Configure" in widget
> 
> OBSERVED RESULT
> Hard to hit the "Configure" button
> 
> EXPECTED RESULT
> 
> 
> SOFTWARE/OS VERSIONS
> Windows: 
> macOS: 
> Linux/KDE Plasma: Kali GNU/Linux Rolling x86_64
> (available in About System)
> KDE Plasma Version: 5.21.5
> KDE Frameworks Version: 5.86.0
> Qt Version: 5.15.2
> 
> ADDITIONAL INFORMATION
Comment 2 Nate Graham 2021-10-05 00:09:30 UTC
I've marked this as a duplicate of Bug 413736 despite the fact that that's marked as fixed in 5.21.5 and you have that version, because I recall that a further frameworks fix wound up being necessary as well. The next time you upgrade your system to Plasma 5.22 (and its required frameworks version), this should be--finally--fully fixed. If you find that it's still happening anyway, please do re-open Bug 413736 with a comment. Thanks!

*** This bug has been marked as a duplicate of bug 413736 ***