Bugzilla – Full Text Bug Listing
|Summary:||yast2-services-manager: applying changes loses selection|
|Product:||[openSUSE] openSUSE Tumbleweed||Reporter:||Christopher Yeleighton <giecrilj>|
|Component:||YaST2||Assignee:||YaST Team <yast-internal>|
|Status:||CONFIRMED ---||QA Contact:||Jiri Srain <jsrain>|
|Priority:||P5 - None||CC:||giecrilj|
|Found By:||Community User||Services Priority:|
|Marketing QA Status:||---||IT Deployment:||---|
|Bug Depends on:||1193284|
Description Christopher Yeleighton 2021-12-01 09:57:49 UTC
REPRO: 1. Tell Service Manager to start service mariadb! 2. Tell Service Manager to apply! EXPECTED: Selected service: mariadb OBSERVED: Selected service: accounts-daemon
Comment 1 Stefan Hundhammer 2021-12-01 11:55:32 UTC
Some context please. You are leaving us guessing with almost everything. You did WHAT from WHAT piece of software? Did you use the YaST control center? If yes, what module did you start from there? What did you do in that? What happened that you consider a problem? If this is really a YaST problem, please attach y2logs: https://en.opensuse.org/openSUSE:Report_a_YaST_bug#Attachments_-_y2logs.2C_hwinfo_etc. Also, please ALWAYS make sure that the problem description is in the bug description, not in the subject: https://en.opensuse.org/openSUSE:Bug_reporting_FAQ#People_were_very_unhappy_because_I_only_wrote_.22see_subject.22_in_the_Bugzilla_bug_description_-_but_my_subject_really_explains_it_all.21_Isn.27t_it_pure_nitpicking_to_insist_on_bug_reporters_repeating_that_in_the_description_field.3F
Comment 2 Christopher Yeleighton 2021-12-01 12:26:44 UTC
(In reply to Stefan Hundhammer from comment #1) > Some context please. You are leaving us guessing with almost everything. > > You did WHAT from WHAT piece of software? I told Service Manager to start service mariadb. > Did you use the YaST control center? > If yes, what module did you start from there? I told it to open the Service Manager. > What did you do in that? I selected service mariadb, I told the Service Manager to start it and to apply. > > What happened that you consider a problem? Selected service: accounts-daemon
Comment 3 Stefan Hundhammer 2021-12-01 15:29:14 UTC
Just repeating the first comment is not helpful at all. We already knew that.
Comment 4 Stefan Hundhammer 2021-12-01 16:16:21 UTC
With a lot of guesswork I tried to reproduce this, and here is what I observed: After applying a change to the currently selected service, the table content is reloaded. The previously selected table item is no longer selected; it is now a different one, probably the (case-insenstive) alphabetically first one, "accounts-daemon". But that's not the first visible item in that table; that would be "Modem-Manager" which is the case-sensitive alphabetically first one. I am not sure how useful it would be to select the previously selected one again; we'll have to discuss that internally. But at the very least the behavior is inconsistent (case-sensitive vs. case-insensitive first item).
Comment 5 Stefan Hundhammer 2021-12-01 16:17:59 UTC
Moving to our task queue for a future sprint.
Comment 6 Christopher Yeleighton 2021-12-02 11:56:07 UTC
(In reply to Stefan Hundhammer from comment #4) > I am not sure how useful it would be to select the previously selected one > again; we'll have to discuss that internally. But at the very least the > behavior is inconsistent (case-sensitive vs. case-insensitive first item). You want to make sure that the service you wanted to run is really running. It need not be.