Bug 433707 - Firefox/Thunderbird download dialog not receiveing focus and not "ungreying" ok/save button
Summary: Firefox/Thunderbird download dialog not receiveing focus and not "ungreying" ...
Status: RESOLVED DUPLICATE of bug 433708
Alias: None
Product: kwin
Classification: Plasma
Component: core (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-27 15:59 UTC by r.pfeiffer22
Modified: 2021-03-02 18:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Save dialog in Thunderbird with greyed-out "Ok" button (38.18 KB, image/png)
2021-02-27 15:59 UTC, r.pfeiffer22
Details

Note You need to log in before you can comment on or make changes to this bug.
Description r.pfeiffer22 2021-02-27 15:59:46 UTC
Created attachment 136228 [details]
Save dialog in Thunderbird with greyed-out "Ok" button

SUMMARY
Thunderbird or Firefox never realize the download popup window is active and activate the "Ok" button when downloading a file or email attachment. Instead, it stays greyed out indefinitely.
In Firefox, this can be forced by setting the notification delay to 0 in about:config, but this workaround does not work for Thunderbird. Here, alt-tabbing between Thunderbird and other programs a few times sometimes helps.


STEPS TO REPRODUCE
1. Fresh install of Kubuntu 20.10
2. Open a PDF within Firefox and click on the download button.
3. Or, in Thunderbird, open an email with attachments and try opening or downloading them.

OBSERVED RESULT
"OK" or "Save" button stays greyed out indefinitely.

EXPECTED RESULT
"Ok" or "Save" button should activate after 1000 ms.

SOFTWARE/OS VERSIONS
Windows: -
macOS:  -
Linux/KDE Plasma: Kubuntu 20.10
(available in About System)
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0 
Qt Version: 5.14.2

ADDITIONAL INFORMATION
Dual boot with Win10.
Comment 1 r.pfeiffer22 2021-02-27 17:37:39 UTC
Seems to have been introduced by the last firmware update of the Cherry MX Board 3.0S (v. 0126).
Unplugging the keyboard solves all the issues.
Comment 2 Nate Graham 2021-03-02 18:15:50 UTC
*** This bug has been marked as a duplicate of bug 433708 ***