[Bug 1226525] New: Cockpit confusing behavior with performance profiles
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1226525 Bug ID: 1226525 Summary: Cockpit confusing behavior with performance profiles Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cockpit Assignee: Cockpit-bugs@suse.de Reporter: robert.simai@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Fresh boot, log into Cockpit as regular user, see Overview, Configuration, "Performance profile: none". Mouse over "none" shows "Tuned is not running". All correct so far. Switch to administrative access, still it shows "Performance profile none" but isn't grayed out anymore. Click on that gives an error -->-- Change performance profile Danger alert:Server has closed the connection. -<-- which makes sense, as tuned is not running. But after clicking the error away the performance profile ("virtual-guest" in my installation) shows correctly and can be changed. Tuned is still disabled but now running, Cockpit magically started it. Changing the profile finally changes tuned to be enabled for system boot, again magically and without telling the admin. This is confusing. I suggest to change the error to something understandable, maybe along with adding something meaningful to the docs. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com