Description of problem: On the new diagnostic reports page in Cockpit in Fedora 36, if I generate a new sosreport and use the "Use verbose logging" option, while the report is being generated, I am blocked from completing any other tasks in Cockpit. For example, if I go to the terminal page while the report is being created, I cannot type any input in to the terminal. Version-Release number of selected component (if applicable): cockpit-272-1.fc36.x86_64 How reproducible: Every time Steps to Reproduce: 1. Go to diagnostic reports in Cockpit 2. Click "Run report" 3. Enable "Use verbose logging" option 4. Click Run report 5. While report is running, click on Terminal 6. Attempt to type input in to the Terminal Actual results: Unable to type in to terminal or complete other tasks. If I go to other areas of Cockpit, such as Services, it stays on "Loading.." and never shows any info Expected results: Still able to go to other areas while report is running. The "Use verbose logging" option makes the report take significantly longer to generate, so it is likely that users will want to complete other tasks while the report is being run.
I can reproduce this. I enabled `window.debugging = 'all'` during this, and I see gajillions of messages coming through the bridge, which just DoS it. These messages are supposed to land in the sosreport tarball/log file only, but not all sent to the channel. We don't show them in the UI anyway. Thanks for reporting!
Yes, I totally missed this misbehavior during development, sorry. We pass "-vvv" to sos when the "Verbose" checkbox is on, which causes it to write all DEBUG level messages to the console. This is pointless with Cockpit. With just "-v", sos will only write WARNING level messages, but will still include DEBUG level messages in the archive itself. So let's just use "-v" with Cockpit.
https://github.com/cockpit-project/cockpit/pull/17571
FEDORA-2022-5421bec777 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5421bec777
FEDORA-2022-b60c113cdd has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b60c113cdd
FEDORA-2022-b60c113cdd has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-b60c113cdd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b60c113cdd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-5421bec777 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-5421bec777` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5421bec777 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-b60c113cdd has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-5421bec777 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.