Hi all,
some time ago we discussed where and how we should share
"Tips&Tricks" for YaST users and developers.
IIRC there was no clear conclusion so I decided to start
a wiki [1] to collect all our tricks we know or use.
For now it's just a place for dumping your ideas, links, short
howtos, etc... When we collect enough data we can probably
split it to several categories or move it somewhere else.
We just need the data first.
I have added there some my tricks from my personal "knowledgebase"
file. If you have better tricks or find something wrong simply
change it, it's a wiki ;-)
Ladislav
[1] https://github.com/yast/yast.github.io/wiki/YaST-Tips-and-Tricks
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi there!
In the context of revamping yast2-users[1], 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[2], 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[3].
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.
Thanks!
[1] "Revamping yast2-users" mailing list thread -
https://lists.opensuse.org/archives/list/yast-devel@lists.opensuse.org/thre…
[2] "UI library limitations"
https://github.com/yast/yast-users-ng/issues/8
[3] "Revamping yast2-users UI: an initial proposal"
https://github.com/yast/yast-users-ng/issues/6
--
David Díaz
YaST Team at SUSE LINUX GmbH
IRC: dgdavid
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
expert partitioner?
--
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/
As you may know, this pull request in libyui brought nicer tabs in Qt
that rely on QTabWidget
https://github.com/libyui/libyui/pull/31
As explained there, some hacks were needed because the philosophy of
tabs in Qt is different from the one in libyui.
With Qt, the widgets contained in all tabs exist in memory (they keep
their state and can be referenced) as long as the group of tabs exists.
Changing between tabs is controlled by Qt itself (mostly transparent to
the program) and its just a matter of which widgets are visible and
which are not. In some sense, switching tabs is not so different from
scrolling a screen - some widgets will become visible and other will not
be longer in the spotlight, but all widgets are still there.
With libyui, switching a tab is just an event and it's program
responsibility to actually redraw the content below the tabs. Something
that is done thanks to the usage of replace points and that implies
destroying all the visible widgets and creating new ones to be drawn in
their places. If the program is using CWM (which offers an extra
abstraction layer on top of libyui with it's own sequence of events),
that means that for every widget that becomes hidden (destroyed,
actually) a "validate" and a "store" events are triggered. On the other
hand, the status of every widget that becomes visible (created again,
actually) must be initialized based on an "init" event (apart from
calling the constructor, the usual calls to "content", etc.).
While reviewing the changes in libyui we came to the question of whether
it would be actually better to adopt the Qt philosophy in libyui. Maybe
with an alternative widget (to not completely break backwards
compatibility and CWM tabs). What do you think? Would it be worth
considering?
Cheers
--
Ancor González Sosa
YaST Team at SUSE Software Solutions
As the main highlight for this sprint, the YaST team finished the first
phase of the reworked management of users and groups in (Auto)YaST.
Check all the details at
https://yast.opensuse.org/blog/2021-06-28/sprint-126
Cheers.
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
Time flies and another two weeks of YaST development have passed. Apart
from learning and experimenting with technologies that will shape the
role of Linux installers in the future, the YaST team fixed quite some
bugs and made some progress in the following features:
- Simplified support for hibernation
- Make network forwarding configurable in the installer
- Improved tabs in graphical mode
- Progress in the rewrite of yast2-users
Check the full report at
https://yast.opensuse.org/blog/2021-06-17/sprint-125
Cheers.
PS.- And remember openSUSE Virtual Conference 2021 starts tomorrow!
https://events.opensuse.org/conferences/oSVC21
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
Hi,
raw data[1] was published for Leap 15.3 retrospective and I use that opportunity to look into it if there is something related to yast.
General impression is that people are in general not so happy about older versions of some packages and that update repos are confusing. Also some people do not update before upgrade and there was quite lot complains about conflicts in patches caused by some SLE patches.
Yast Specific feedback (unsorted):
- Lack of translations EVEN THOUGH I am the (Finnish) translator! Some strings are missing even though I am sure they’ve been in the localization files for a long time. Like the system roles (KDE Plasma, GNOME, Xfce): they were translated in time for Leap 15.2 and remain translated in Weblate, so why are the strings not being used?
- yast settings like ratbagctl (NOTE: in section "what is not going well" and to be honest I do not get what reporter mean, if someone has clue. Maybe missing yast module for configurable mouses? )
- I have very old hardware Dell Inspiron 1525 which had Leap 15.2 installed and the upgrade to Leap 15.3 via external USB and choosing upgrade went very smoothly. The NET image was available just a few hours after launch when I tried and I had no hiccups during the download of packages here in India. All in all this method worked well for me. ( NOTE: as negative was that zypper dup failed for that user due to need of more repos and failed to do it properly. So he do snapper rollback and use usb for upgrade )
- After installation I checked for updates and got error messages that
1. a dependency for a file could not be resolved (can't remember which one).
2. no data for NonOSS and NonOSS update repositories could be found, I then replaced the "$_releaseserver" in the URL with "15.3" and it worked
- I cannot install or boot it on my laptop because of the shim issue https://bugzilla.opensuse.org/show_bug.cgi?id=1185232 so I unfortunately am using Fedora until opensuse is fixed
- guided installing to disk. no major changes with installer probably a good thing
- The installer did not recognize my internal ssd and could not install. My device is an Acer Aspire 5 A515-56-56DJ.
- 1.I did a new install.Re-install (It clears out old rubbish). It worked but the install instructions need MUCH more clarity, to BOTH reformat root"/", mount it, THEN SELECT snapshots in pop up, then select to mount swap and /home or you get mini installation in old root "/" without "/home" being added and without snapshots.
2. This ability to only add snapshots AFTER you select mount "/" is bad it needs it own clear box.
The instructions should say snapshots wanted as a BOX on the page, before ticking 'mount'. then if low storage a reply "snapshots not available due storage limits" can be displayed
3. I experimented (with a friend) and found why others missed this 'snapshot' enable process.
- * Yast team was always super responsive. Thanks to zypper team for fixing a lot of last minute issues.
- Did an offline upgrade; the installer didn’t manage to install some packages (six libX packages, I forgot the exact ones) from the SUSE repository but otherwise successfully completed the installation. When starting YaST the first time, it notified about the missing libX-packages and prompted to install them, which it successfully did. Also there seems to be a problem with some libreoffice packages (libreoffice-icon-themes, and libreoffice localisations) being available in a newer version than the main libreoffice package, making them impossible to update.
Additionally, zypper up wants to remove yast2-trans-en and install yast2-trans. YaST, however, marks yast2-trans as unneeded and wants to replace it with yast2-trans.
- almost translated installer
download packages while installing
clever disk partitioner in installer
repository filter in yast software
install updates by one-click in taskbar
boot linux system easily by linuxrc in installer media ( NOTE: in positive, negative follows, non yast related stuff is filtered out )
can't hide grub loading message
installer will install ibus ime,but it can't change theme.installer should install fcitx
mute led in keyboard isn't working
kde connect can't connect to phone,I should modify firewall setting
gnome edition can't display all yast settings in my pc
- a) the partition manager, if you use your own layout, is... uncomfortable, at least.
- 2 - the ${releasever} feature in repo file is very good
- The hardware detection and driver loading part of the installing took way too long.
when I try to open YaST software management and It's already being used I get a ruby error instead of a proper error message saying that it is already being used.
I hope you find it useful and maybe for some issues it makes sense to create proper bug reports?
Josef
[1] https://en.opensuse.org/Portal:15.3/Retrospective
Hi,
I just would like to point that there is already collecting features for next Leap 15.4 which now has own partner features in jira.
It is collected at https://en.opensuse.org/Feature_Planning_15.4
So far interesting parts for YaST team is:
- Improved release upgrade ( something like yast migrate for opensuse )
- Up to date cockpit ( due to our collaboration on some cockpit modules )
And thats it. Maybe more will appear, so it will be interesting to check it also in future, as there is also "use case" ( well, not formal use case but at least reasoning ).
Josef
