how can I set it don’t close automatically?
I want it just stay there, and let me close it manully.
[ol]
[li]Start up YaST Control Center[/li][li]Select System[/li][li]Click /etc/sysconfig Editor on the right[/li][li]Unfold the following options:[/li][LIST=1]
[li]System[/li][li]YaST2[/li][li]GUI[/li][/ol]
[li]Select PKGMGR_ACTION_AT_EXIT[/li][li]Pick one of the options,[/li][/LIST]
no options can be unfolded on the /etc/sysconfig Editor.
please see the image:
You mean it’s blank on the left of the UI?
yes
Unfold the following options:
- System
- YaST2
- GUI
where are these 3 options?
What do you get from
zypper ve
linux-dkkq:/opt/lampp # zypper ve
Loading repository data…
Reading installed packages…
Dependencies of all installed packages are satisfied.
There is something you’re not telling us. I’ve just checked in case it was a language problem and yast renders fine with Chinese.
I’ve seen something similar when yast is run via sudo and the appropriate permissions aren’t given for the relevant modules, but it normally gives a warning. I bet if you look in /etc/sysconfig its all there so their has to be a reason why it isn’t showing.
In a su - terminal try this
yast
You need the keyboard to work thru this yast.
Can you see text in it?
by the way, last time I didn’t use sodo to run yast2.
I used the menu:
- click [Computer]
- click [yast]
- type the root password
- then the yast window open
- select [system]—then the steps you asked me to do
linux-dkkq:/etc/sysconfig # ls
SuSEfirewall2 displaymanager lvm smartmontools
SuSEfirewall2.d displaymanager.orig mail sound
apache2 dmraid mdadm ssh
auditd dvb mouse storage
autofs fonts-config network suse_register
backup hardware news suseconfig
bluetooth ide nfs susehelp
boot irda ntp sysctl
bootloader irqbalance postfix syslog
bootsplash joystick proxy ulimit
clock kernel rpcbind windowmanager
clock.orig keyboard scpm windowmanager.orig
compcache language scripts yast2
console ldap security ypbind
cron lirc services
cups logitech_mouse shutdown
I find your problem really strange tbh…
Before trying the below you could see if you can catch any output in the terminal as su.
yast2 sysconfig
I can’t understand why it should be doing this did the install media checksum match? The next thing is to check the yast versions,
zypper se -si yast
On an updated here I have yast2 2.18.25-2.5 and yast2-sysconfig 2.17.0-56.2
The next option would be to try a reinstall but as I’m unsure of the modules beyond the 2 quoted above I’d get them all.
zypper in --force $(rpm -qa --queryformat "%{NAME}
" | grep yast )
The bit in red you should probably run first just to check. Also that is using a force which is far from nice but this will reinstall the found packages.
**linux-dkkq:~ # zypper se -si yast**
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
--+--------------------------------------+---------+----------------+--------+---------------------
i | autoyast2-installation | package | 2.18.14-1.1.3 | noarch | openSUSE-11.2-Oss
i | gnome_yast | pattern | 11.2-20.22.1 | x86_64 | openSUSE-11.2-Oss
i | gnome_yast | pattern | 11.2-20.22.1 | i586 | openSUSE-11.2-Oss
i | patterns-openSUSE-gnome_yast | package | 11.3-1.1.1 | x86_64 | openSUSE-11.2-Update
i | patterns-openSUSE-yast2_basis | package | 11.3-1.1.1 | x86_64 | openSUSE-11.2-Update
i | patterns-openSUSE-yast2_install_wf | package | 11.3-1.1.1 | x86_64 | openSUSE-11.2-Update
i | yast2 | package | 2.18.25-2.5 | x86_64 | openSUSE-11.2-Oss
i | yast2-add-on | package | 2.18.3-2.1 | noarch | openSUSE-11.2-Oss
i | yast2-apparmor | package | 2.18.4-1.1.1 | noarch | openSUSE-11.2-Oss
i | yast2-backup | package | 2.18.5-0.1.1 | noarch | openSUSE-11.2-Update
i | yast2-backup | patch | 1651 | noarch | openSUSE-11.2-Update
i | yast2-bootloader | package | 2.18.17-2.5 | x86_64 | openSUSE-11.2-Oss
i | yast2-branding-openSUSE | package | 2.18.0-2.1 | noarch | openSUSE-11.2-Oss
i | yast2-control-center | package | 2.18.12-1.1.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-control-center-gnome | package | 2.13.4-2.3 | x86_64 | openSUSE-11.2-Oss
i | yast2-core | package | 2.18.19-2.3 | x86_64 | openSUSE-11.2-Oss
i | yast2-country | package | 2.18.20-2.2 | x86_64 | openSUSE-11.2-Oss
i | yast2-country-data | package | 2.18.20-2.2 | x86_64 | openSUSE-11.2-Oss
i | yast2-dbus-client | package | 2.18.0-2.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-fingerprint-reader | package | 2.18.1-2.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-firewall | package | 2.18.1-1.1.2 | noarch | openSUSE-11.2-Oss
i | yast2-gtk | package | 2.20.5-1.2.3 | x86_64 | openSUSE-11.2-Oss
i | yast2-hardware-detection | package | 2.17.1-2.3 | x86_64 | openSUSE-11.2-Oss
i | yast2-inetd | package | 2.17.3-3.3 | noarch | openSUSE-11.2-Oss
i | yast2-installation | package | 2.18.33-1.1.2 | noarch | openSUSE-11.2-Oss
i | yast2-irda | package | 2.18.2-0.1.1 | noarch | openSUSE-11.2-Update
i | yast2-irda | patch | 1652 | noarch | openSUSE-11.2-Update
i | yast2-iscsi-client | package | 2.18.6-2.2 | noarch | openSUSE-11.2-Oss
i | yast2-kerberos-client | package | 2.18.3-2.2 | noarch | openSUSE-11.2-Oss
i | yast2-ldap | package | 2.17.3-9.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-ldap-client | package | 2.18.5-2.6 | noarch | openSUSE-11.2-Oss
i | yast2-libyui | package | 2.18.8-2.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-mail | package | 2.18.2-2.2 | noarch | openSUSE-11.2-Oss
i | yast2-metapackage-handler | package | 0.8.10-0.1.1 | noarch | openSUSE-11.2-Update
i | yast2-metapackage-handler | patch | 1561 | noarch | openSUSE-11.2-Update
i | yast2-mouse | package | 2.18.2-2.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-ncurses | package | 2.18.11-0.1.1 | x86_64 | openSUSE-11.2-Update
i | yast2-ncurses | patch | 1784 | noarch | openSUSE-11.2-Update
i | yast2-ncurses-pkg | package | 2.18.4-2.10.1 | x86_64 | openSUSE-11.2-Update
i | yast2-network | package | 2.18.53-1.1.1 | x86_64 | openSUSE-11.2-Update
i | yast2-network | patch | 1668 | noarch | openSUSE-11.2-Update
i | yast2-nfs-client | package | 2.18.0-2.2 | noarch | openSUSE-11.2-Oss
i | yast2-nfs-common | package | 2.18.1-2.2 | noarch | openSUSE-11.2-Oss
i | yast2-nis-client | package | 2.18.2-2.2 | x86_64 | openSUSE-11.2-Oss
i | yast2-ntp-client | package | 2.18.0-3.2 | noarch | openSUSE-11.2-Oss
i | yast2-online-update | package | 2.18.5-2.2 | noarch | openSUSE-11.2-Oss
i | yast2-online-update-frontend | package | 2.18.5-2.2 | noarch | openSUSE-11.2-Oss
i | yast2-packager | package | 2.18.13-1.1.3 | x86_64 | openSUSE-11.2-Oss
i | yast2-packager-webpin | package | 2.18.13-1.1.3 | x86_64 | openSUSE-11.2-Oss
i | yast2-pam | package | 2.17.1-2.1 | noarch | openSUSE-11.2-Oss
i | yast2-perl-bindings | package | 2.18.0-2.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-pkg-bindings | package | 2.18.11-1.1.4 | x86_64 | openSUSE-11.2-Oss
i | yast2-printer | package | 2.18.19-2.2 | x86_64 | openSUSE-11.2-Oss
i | yast2-profile-manager | package | 2.18.2-2.2 | x86_64 | openSUSE-11.2-Oss
i | yast2-qt | package | 2.18.7-2.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-qt-graph | package | 2.18.4-4.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-qt-pkg | package | 2.18.18-1.1.2 | x86_64 | openSUSE-11.2-Oss
i | yast2-registration | package | 2.18.0-2.4 | noarch | openSUSE-11.2-Oss
i | yast2-registration-branding-openSUSE | package | 2.18.0-2.4 | noarch | openSUSE-11.2-Oss
i | yast2-repair | package | 2.18.3-2.4 | noarch | openSUSE-11.2-Oss
i | yast2-restore | package | 2.18.1-3.1 | noarch | openSUSE-11.2-Oss
i | yast2-runlevel | package | 2.17.4-2.2 | noarch | openSUSE-11.2-Oss
i | yast2-samba-client | package | 2.18.3-2.2 | noarch | openSUSE-11.2-Oss
i | yast2-samba-server | package | 2.18.2-2.1 | noarch | openSUSE-11.2-Oss
i | yast2-scanner | package | 2.18.0-2.2 | x86_64 | openSUSE-11.2-Oss
i | yast2-security | package | 2.18.3-2.2 | noarch | openSUSE-11.2-Oss
i | yast2-slp | package | 2.16.0-83.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-sound | package | 2.18.4-1.1.2.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-storage | package | 2.18.19-2.3 | x86_64 | openSUSE-11.2-Oss
i | yast2-sudo | package | 2.18.2-2.2 | noarch | openSUSE-11.2-Oss
i | yast2-sysconfig | package | 2.17.0-56.2 | noarch | openSUSE-11.2-Oss
i | yast2-theme-openSUSE | package | 2.18.10-1.1.1 | noarch | openSUSE-11.2-Oss
i | yast2-trans-de | package | 2.18.1-16.19.1 | noarch | openSUSE-11.2-Update
i | yast2-trans-en_US | package | 2.18.1-16.19.1 | noarch | openSUSE-11.2-Update
i | yast2-trans-es | package | 2.18.1-16.19.1 | noarch | openSUSE-11.2-Update
i | yast2-trans-fr | package | 2.18.1-16.19.1 | noarch | openSUSE-11.2-Update
i | yast2-trans-it | package | 2.18.1-16.19.1 | noarch | openSUSE-11.2-Update
i | yast2-trans-pl | package | 2.18.1-16.19.1 | noarch | openSUSE-11.2-Update
i | yast2-trans-ru | package | 2.18.1-16.19.1 | noarch | openSUSE-11.2-Update
i | yast2-trans-stats | package | 2.15.0-122.2 | noarch | openSUSE-11.2-Oss
i | yast2-trans-zh_CN | package | 2.18.1-16.19.1 | noarch | openSUSE-11.2-Update
i | yast2-transfer | package | 2.18.0-3.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-tune | package | 2.18.1-2.2 | x86_64 | openSUSE-11.2-Oss
i | yast2-tv | package | 2.18.4-2.8 | noarch | openSUSE-11.2-Oss
i | yast2-update | package | 2.18.6-2.3 | x86_64 | openSUSE-11.2-Oss
i | yast2-users | package | 2.18.13-2.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-vm | package | 2.16.10-3.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-x11 | package | 2.18.0-2.1 | noarch | openSUSE-11.2-Oss
i | yast2-xml | package | 2.16.1-56.1 | x86_64 | openSUSE-11.2-Oss
i | yast2-ycp-ui-bindings | package | 2.18.5-2.1 | x86_64 | openSUSE-11.2-Oss
i | yast2_basis | pattern | 11.2-20.22.1 | x86_64 | openSUSE-11.2-Oss
i | yast2_basis | pattern | 11.2-20.22.1 | i586 | openSUSE-11.2-Oss
i | yast2_install_wf | pattern | 11.2-20.22.1 | x86_64 | openSUSE-11.2-Oss
i | yast2_install_wf | pattern | 11.2-20.22.1 | i586 | openSUSE-11.2-Oss
should I try below command now?
zypper in --force $(rpm -qa --queryformat "%{NAME}
" | grep yast )
I take it running it from the command line isn’t helping? By all accounts you look like you’re up to date, if you’re really not getting anything from the console when running it, then I guess it has finally come to that as I’m running out of ideas.
To be fair I can actually tell you how to solve the OP but to me it would seem this suggests something else is going on and is probably worth fixing(You would open /etc/sysconfig/yast2 in an editor and correct the var to restart). The problem is I’ve been about a little while and I have tbh I’ve never seen this and I’ve been using Suse since 9.2.
Are you using QT in gnome?
To get the better package management interface?
I take it you have rebooted recently?
sorry? what you mean? below is my /etc/sysconfig/yast2, what should I change?
# Tweakable settings for the 'yast2' script.
# to over-ride these settins per-user create a
# ~/.yast2/yast2 file.
## Path: System/Yast2/GUI
## Description: Default UI for YaST
## Type: list(auto,qt,gtk)
## Default: "auto"
# Default control center for YaST
# selects the control-center implementation to be used
# to render yast widgets
# auto: will attempt to detect both desktop & plugin
# presence and adapt accordingly
**WANTED_SHELL="auto"**
## Type: list(auto,qt,gtk,ncurses)
## Default: "auto"
# Default UI backend for YaST
# selects the GUI plugin to be used to render yast widgets
# auto: will attempt to detect both desktop & plugin
# presence and adapt accordingly, falling back to
# qt rendering if gtk is not present
**WANTED_GUI="auto"**
## Type: string(linux,xterm,rxvt,mono,braille)
## Default: ""
# Color theme for YaST ncurses UI
# xterm: blue-white-red
# linux: blue-white-yellow
# rxvt: black-yellow-red
# mono: white-black
# braille: for visually impaired
**Y2NCURSES_COLOR_THEME=""**
## Type: list(yes,no)
## Default: "no"
# Enable tracking of configuraiton changes in subversion repository
# This is EXPERIMENTAL and not all YaST modules do support it.
# Use at your own risk
**STORE_CONFIG_IN_SUBVERSION="no"**
## Type: list(yes,no)
## Default: "no"
# Track all changes in all files in configuration directory
# If set to "no", YaST adds to the repository only files it changes
# itself and the first change of a particular configuration file
# gets lost (it can only be manually compared to the one in
# configuration file).
# If set to "yes", all files in the configuration directory
# are tracked in the subversion repository. This has big impact
# on start-up and finish times of YaST modules
# This option is experimental and not all YaST modules do support
# configuration tracking via subversion
**SUBVERSION_ADD_DIRS_RECURSIVE="no"**
## Type: list(close,restart,summary)
## Default: "close"
# Set the default behavior of the package manager when package installation has finished.
# Possible actions are:
sorry I even don’t know what is QT. I didn’t use it.
I reboot my computer everyday since it is the desktop of my laptop, I shut down the computer when I sleep, then in the morning I will restart my computer.
You seem to have trimmed the last bit of the file there is several lines missing mostly comments but also the last and needed var.
PKGMGR_ACTION_AT_EXIT=“restart”
Still think you need to find out why yast2 sysconfig is misbehaving and also the ncurses(yast terminal) version seems very strange to me. The above is working around the sysconfig problem but not solving it. Though there is no reason why you couldn’t continue like so just seems to be pointing to something wrong.
The only other suggestion is to run it through strace but I doubt I’ll understand it. I did construct an egrep expression for the errors but I’m not sure it’ll enlighten me unless it is glaringly obvious i.e the get.id is not 0.
Might be worth bug reporting.