Error on update YaST in openSUSE

e@d79 · 03-01-2018, 03:46 AM

Hi giys.

I'm beginner in the linux system and install openSUSE Tumbleweed.
I open Yast Control Center and start Software Management.
Start check, two or four seconds and I have error:

http://funkyimg.com/i/2CTAL.jpeg
Please, help me!

ferrari · 03-01-2018, 12:00 PM

Read this recent openSUSE thread dealing with the same issue. It linked to a bug report which is now resolved.

In particular, run the following from a terminal to fully update the machine...

Code:

sudo zypper dup

e@d79 · 03-06-2018, 01:50 AM

Quote:

Originally Posted by ferrari

Read this recent openSUSE thread dealing with the same issue. It linked to a bug report which is now resolved.

In particular, run the following from a terminal to fully update the machine...

Code:

sudo zypper dup

thanks so mush

ferrari · 03-06-2018, 02:00 AM

Glad to have been of guidance.

mrmazda · 03-06-2018, 08:01 PM

Even though Tumbleweed contains YaST2 software management, the only officially supported update method for it is 'zypper dup'. YaST2 is generally fine for searching and installing additional packages, and typically necessary for pattern management.

e@d79 · 03-16-2018, 03:27 AM

Quote:

Originally Posted by ferrari

Glad to have been of guidance.

Help me, please...
After update my system ("sudo zyper up") I have error:
http://funkyimg.com/view/2Dpwu

ferrari · 03-16-2018, 03:58 AM

Don't use 'zypper up' on Tumbleweed. Use the following

Code:

sudo zypper dup

e@d79 · 03-17-2018, 01:32 PM

Quote:

Originally Posted by ferrari

Don't use 'zypper up' on Tumbleweed. Use the following

Code:

sudo zypper dup

Hm-m-m...ok,but, thanks so lot

ferrari · 03-17-2018, 03:19 PM

I didn't examine your posted image. The 'Failed to cache rpm database(1)' error could be due to a corrupted RPM database. Try rebuilding it with

Code:

rpm --rebuilddb

e@d79 · 03-24-2018, 07:38 AM

Quote:

Originally Posted by ferrari

I didn't examine your posted image. The 'Failed to cache rpm database(1)' error could be due to a corrupted RPM database. Try rebuilding it with

Code:

rpm --rebuilddb

I did it and I have't errors)) Thks!!!