In the context of revamping yast2-users, I spent some days looking
for an alternative layout that could help to improve the current UI by
reducing the number of tabs and grouping form fields to make better use
of available space.
However, due to our resolution constraints (UI must fit well in an
80x24 terminal) and some UI library limitations, looks like there is
not too much room for big changes and our best bet is to keep the
layout almost as it is, just making some necessary adjustments.
Summarizing them a lot, those changes will consist of adding a top menu
bar for making easier the user navigation, moving all settings to the
same dialog, improving filters by using a popup, making small changes
in forms, and adding some summary views.
Of course, nothing is written in stone and it would be nice to know
your feedback and/or ideas too. So, please, keep reading the following
links if you are interested and tell us what do you think. Is there
anything we overlooked? Some other ideas we should evaluate?
Remember that you can reach us by email, on IRC, or even by directly
leaving a comment in those Github issues.
 "Revamping yast2-users" mailing list thread -
 "UI library limitations"
 "Revamping yast2-users UI: an initial proposal"
YaST Team at SUSE LINUX GmbH
Curious about the summer activities of the YaST Team? Housekeeping,
learning and much more in a new report from the YaST trenches at:
* Better management of the Help button in text mode
* Improved unmounting of file-systems at the end of installation
* More robust handling of progress bars
* Integrating contributions made by our users
* Learning and improving the Release Tools
Ancor González Sosa
YaST Team at SUSE Linux GmbH
NameScheme=by-label on installer cmdline has had no effect I have observed for a
lot longer than I can remember, several years at least, continuing in 15.3 build
117.13. Has it been removed and the linuxrc page need matching update? Is this a
broken installer option? Am I not understanding why it's listed on the linuxrc
page? Shouldn't it prevent me from needing to change default mount by in the
Evolution as taught in public schools, like religion,
is based on faith, not on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
While checking and refining some older bugs and feature request with
David and Ancor, we came across an interesting one:
*Prevent the same YaST module from running twice at the same time*
We've been discussing the topic back and forth, identified some
use-cases in which it would make sense, a few technical solutions and
even more obstacles, but we decided it would make sense to ask for
opinions at YaST Devel first.
Why to prevent from running the same twice?
- Some may click too fast and run two or more at the same time -> here
you instantly see more modules starting
- Some may start a YaST module, then do something else, overlook the
first one, start another, ... then hard to say which one wins at the
end and what would be the changes --> is that likely?
- Two admins could run the same module without knowing about each other
--> this may happen in remote session at COVID times
How to prevent from running them more times?
- Logging the PID, storing it at some file (module/client name),
checking at startup (more PIDs in case of more sessions of the same?)
- Either at YaST startup scripts (easier) or YaST core (some might skip
using a startup script, is that likely?)
- Showing a message (another special client) and offering some options,
e.g., kill the other session, exiting
- Offering a read-only mode (quite hard) for the second session
- Another idea was to bring the UI to the front (only possible with Qt)
instead of starting a new one
Some possible problems
- Some admins really just run YaST to see the current configuration, so
preventing from running something twice might not be an option
- Some YaST modules can be called from within another ones, e.g.,
Repositories from the Packager, what to do with that?
- Some YaST modules can be called as a user; what if the user differs?
Quite some unknowns as you may see :) Is that worth it? Is there a
simpler solution? Would that fit?
- https://jira.suse.com/browse/SLE-2999 (internal)
Thanks for your opinions
Lukas Ocilka, Systems Mgmt & Consulting Team Leader & YaST Product Owner
SLE Department, SUSE Linux
just come when debugging some slowdown in yast that ruby 2.7 ( one in TW ) removes profiler. What is result? Y2PROFILER=1 no longer works.
Do you know about any lightweigth alternative? Advantage of builtin profiler was that was part of ruby, so no additional dependencies are needed.