Currently on Tumbleweed 20241012.
Anyone else have this happen? I can run YAST (gui) once, and do stuff, then hit finish and exit. Then some time later, if I need to get back into YAST, I click the “software management” button again, and…nothing. Just nothing. Clicky clicky and still nothing. Maybe it works the second time but not the third. Usually a reboot solves it - since i’m back to the first time starting yast…
Don’t understand. You say you are NOT in YaST and nevertheless there seems the Software Management button of YaST. Is YaST now running or not?
First time - and other times after, I can “open” the YAST menu:
You’ve never specified how you’re launching Yast GUI.
We always open a terminal, log to root, and execute Yast.
If you don’t do it that way, execute it as such and see if there is any error output.
Would this be a situation where maybe rebuild rpm database?
# rpm --rebuilddb or is that completely wrong thinking on my part?
-Thanks
That is for rebuliding the RPM database from the installed packages and the /var/lib/rpm/Packages file. It is not relevant to the YaST issue being described here.
Which desktop environment are you using? If you run yast using the text (ncurses) mode, does that work successfully each time?
su -c yast
OK, thank you. For me it is clear now what the “not working” (that is a terrible and infamous way of describing a problem) of the title means.
YaST starts, but then all the buttons of the several YaST modules do not start anything.
Did you try log-out-log-in also?
After closing, check that it has not remained active in terminal pgrep yast2
I am in KDE. I launch from the “start” - well not really start (the little geko), would be start if it was windows - then settings, then yast icon.
I got a message from someone - not sure why I don’t see it here - to try pgrep. So some interesting results. Of course today things worked fine for a while, so it took me a while to recreate the issue. If I start “software management” from the icon in control center, and it doesn’t launch, I think it is still running in the background. I tried clicking other icons “security” and “printers” and nothing launched then either. Now take a look at my pgrep results:
22729 /bin/bash /sbin/yast2
22768 /bin/bash /usr/sbin/yast2 sw_single
22830 /bin/bash /usr/sbin/yast2 security
22869 /bin/bash /usr/sbin/yast2 printer
so it looks like it did indeed start the processes, but no visible indication in the GUI that they were “launched”.
If I close the “control center” I lose the top process:
22768 /bin/bash /usr/sbin/yast2 sw_single
22830 /bin/bash /usr/sbin/yast2 security
22869 /bin/bash /usr/sbin/yast2 printer
If I click the YAST icon and reopen “control center”, then click the “software management” it looks like I get a second process of the “software management” running which I am guessing is the yast2 sw_single process:
22768 /bin/bash /usr/sbin/yast2 sw_single
22830 /bin/bash /usr/sbin/yast2 security
22869 /bin/bash /usr/sbin/yast2 printer
23280 /bin/bash /sbin/yast2
23319 /bin/bash /usr/sbin/yast2 sw_single
but still no indication in the GUI that the process has begun.
Oh, and logging out/in doesn’t help. The same processes show running after logging back in as well.
I’m going to anticipate the next question: what if I kill the running processes and retry to launch them via “control center”? Interestingly, they still don’t appear to launch (processes do start however).
Oh, not sure it matters, but I’m also in X11 not wayland.
As suggested earlier, open up konsole, then execute “su -l” at the prompt, then execute “yast2” … does the problem still occur?
The other side effect is you might see error messages displayed in the konsole.
I get this error message and the “control center” gui launches, but the fonts are a bit different.
localhost:~ # yast2
MESA-LOADER: failed to open nouveau: /usr/lib64/dri/nouveau_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: nouveau
If I click on the software management icon, nothing launches, but the Konsole window added this line:
Run command: /usr/bin/nohup /usr/sbin/yast2 sw_single > /var/log/YaST2/nohup.out 2>&1 &
You have added third party repositories if you disable or delete them, then try to kill all Yast processes, then sudo rpm --rebuilddb and then sudo zypper dup
Try this (the : zypper in …)
# zypper in libsrt1_5
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following NEW package is going to be installed:
libsrt1_5
1 new package to install.
Package download size: 332.5 KiB
Package install size change:
| 899.2 KiB required by packages that will be installed
899.2 KiB | - 0 B released by packages that will be removed
Backend: classic_rpmtrans
Continue?
Thanks for all the suggestions, but now that I think about it, maybe my problems are bigger than just this. Probably a corrupt OS install at some point along the way, or my hardware is just getting too old to keep up.
The YAST thing is unique in that that it works and then doesn’t, and then does again. I have had other programs that just stop working - like my XnView appimage. Same behavior - click and nothing launches. I just chalked it up to incompatibilities with some new system updates. Funny thing is, I downloaded the zip file and tried that version - and it runs just fine. I have downloaded programs in the past that do the same thing - nothing when you click on them. I figured it was standard incompatibility behavior for linux. This week I just downloaded Photini for image tagging - it doesn’t launch either.
So if this YAST behavior is just me, I guess it’s time to start over. The last tumbleweed update totally killed the video driver and made the gui unusable, so I am afraid to update again as it will likely become unusable again - and maybe from here on out… Time for a new computer I guess. Then I’ll have the opposite problem - hardware too new to be supported…
I have a desktop machine I built from components purchased in Aug 2018 - still running great (added NVME drives a year+ ago).
If you have not tried this … create a new user account, log in as that new user, then check if you have the same problems.
Another option to do … delete the contents in the /home/your-user-name/.cache/* sub-directory.
Don’t delete the ~/.cache sub-directory itself, but files and the sub-directories within (under) it.
Sometimes the files in ~/.cache/* get corrupted or munged up. The files in ~/.cache aren’t critical, they are simply there to “speed up” response times for apps. As you use the apps again, entries in ~/.cache/* will be recreated anew.
Do some cleaning, my computer is 10 years old in June and it’s still lightning fast, and the only thing I’ve given up on are the Nvidia Drivers
Hi, what type of graphics card does your machine have?
What is the output displayed of < inxi -GSaz --vs --za > in Konsole?
Time for a new computer I guess.
Providing some hardware information may be of help also to see if you need to replace your computer yet. What is the output of inxi -Fxz
You can paste the output of these commands between code tags.
OK, but don’t laugh too hard…
System:
Kernel: 6.11.2-1-default arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
Desktop: KDE Plasma v: 6.2.0 Distro: openSUSE Tumbleweed 20241012
Machine:
Type: Laptop System: LENOVO product: 2516CTO v: ThinkPad T410
serial:
Mobo: LENOVO model: 2516CTO serial: BIOS: LENOVO
v: 6IET85WW (1.45 ) date: 02/14/2013
Battery:
ID-1: BAT0 charge: 82.4 Wh (97.7%) condition: 84.3/84.3 Wh (100.0%)
volts: 11.7 min: 11.1 model: LGC 42T4912 status: not charging
CPU:
Info: dual core model: Intel Core i5 M 540 bits: 64 type: MT MCP
arch: Westmere rev: 2 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 1199 min/max: 1199/2534 boost: enabled cores: 1: 1199
2: 1199 3: 1199 4: 1199 bogomips: 20226
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: NVIDIA GT218M [NVS 3100M] vendor: Lenovo ThinkPad T410
driver: nouveau v: kernel arch: Tesla bus-ID: 01:00.0 temp: 49.0 C
Device-2: Lenovo Integrated Webcam [R5U877] driver: uvcvideo type: USB
bus-ID: 1-1.6:6
Display: x11 server: X.Org v: 21.1.12 with: Xwayland v: 24.1.3 driver: X:
loaded: N/A unloaded: fbdev,modesetting,vesa failed: nouveau dri: nouveau
gpu: nouveau resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: kms_swrast,swrast platforms:
active: gbm,x11,surfaceless,device inactive: wayland,device-0
API: OpenGL v: 4.5 vendor: mesa v: 24.1.7 glx-v: 1.4 direct-render: yes
renderer: llvmpipe (LLVM 18.1.8 128 bits)
API: Vulkan Message: No Vulkan data available.
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
Device-2: NVIDIA High Definition Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus-ID: 01:00.1
API: ALSA v: k6.11.2-1-default status: kernel-api
Server-1: PipeWire v: 1.2.5 status: active
Network:
Device-1: Intel 82577LM Gigabit Network vendor: Lenovo driver: e1000e
v: kernel port: 1820 bus-ID: 00:19.0
IF: eth0 state: down mac:
Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel
bus-ID: 03:00.0
IF: wlan0 state: up mac:
Bluetooth:
Device-1: Broadcom BCM2045B (BDC-2.1) driver: btusb v: 0.8 type: USB
bus-ID: 1-1.4:4
Report: btmgmt ID: hci0 rfk-id: 3 state: up address: bt-v: 2.1
lmp-v: 4
Drives:
Local Storage: total: 465.76 GiB used: 389.72 GiB (83.7%)
ID-1: /dev/sda vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
Partition:
ID-1: / size: 64 GiB used: 44.79 GiB (70.0%) fs: btrfs dev: /dev/dm-1
mapped: system-root
ID-2: /home size: 393.92 GiB used: 344.93 GiB (87.6%) fs: xfs
dev: /dev/dm-3 mapped: system-home
ID-3: /opt size: 64 GiB used: 44.79 GiB (70.0%) fs: btrfs dev: /dev/dm-1
mapped: system-root
ID-4: /tmp size: 64 GiB used: 44.79 GiB (70.0%) fs: btrfs dev: /dev/dm-1
mapped: system-root
ID-5: /var size: 64 GiB used: 44.79 GiB (70.0%) fs: btrfs dev: /dev/dm-1
mapped: system-root
Swap:
ID-1: swap-1 type: partition size: 7.63 GiB used: 2 MiB (0.0%)
dev: /dev/dm-2 mapped: system-swap
Sensors:
System Temperatures: cpu: 51.0 C mobo: 34.9 C gpu: nouveau temp: 50.0 C
Fan Speeds (rpm): fan-1: 1986
Info:
Memory: total: 8 GiB available: 7.62 GiB used: 4.17 GiB (54.7%)
Processes: 277 Uptime: 19h 33m Init: systemd
Packages: N/A note: see --rpm Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.37
inxi: 3.3.36