[opensuse] Latest big upgrade garbled up TW
Dear all, In the last few days there was a big TW upgrade with more than 1300 items. I am glad, I could reboot. But... My laptop says it removed thunderbird. Well, then let's reinstall it. It says it is already installed and nothing to be done. Then let's remove it. It says there is no such software. I tried to change from CLI zypper (zypper -f did not work either) to Yast, I failed, because neither Yast nor Yast2 worked, missing some modules. I tried to save some documents, it insisted to put them in temp. I tried to run zypper dup several times, with minor success. these processes always began with trying to remove cyrus* packages that could not be done because they are not installed - said zypper. i use TW with KDE Please help, where should I begin to tidy up things? Thanks: Albert ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* oszko@chem.u-szeged.hu
Dear all,
In the last few days there was a big TW upgrade with more than 1300 items. I am glad, I could reboot. But...
My laptop says it removed thunderbird. Well, then let's reinstall it. It says it is already installed and nothing to be done. Then let's remove it. It says there is no such software. I tried to change from CLI zypper (zypper -f did not work either) to Yast, I failed, because neither Yast nor Yast2 worked, missing some modules. I tried to save some documents, it insisted to put them in temp. I tried to run zypper dup several times, with minor success. these processes always began with trying to remove cyrus* packages that could not be done because they are not installed - said zypper.
i use TW with KDE
I would *guess* your rpm db is faulty, you could try: rpmdb --rebuilddb (you need to be root). as always, backup,backup,backup,backup -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/02/2020 17.58, oszko@chem.u-szeged.hu wrote: | Dear all, | | In the last few days there was a big TW upgrade with more than 1300 | items. I am glad, I could reboot. But... Did it crash during the update? ... | i use TW with KDE | | Please help, where should I begin to tidy up things? Probably corrupt rpm database, as Patrick says. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXkMHYQAKCRC1MxgcbY1H 1XpEAJ0XqrbNIB0oLjFZQXVCbLPgPcqLcQCfY9EHDVYx6YATSH7r5krGnHD4MuY= =qnFn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Well, I rebuilt the database, rebooted, but got back to the point
where I started. I forgot to mention that after rebooting after that
big upgrade the date and time were set to a value back in 2015. Even
the month, day and hour did not match. Finally I culd set it back to
manual, but other Yast modules do not work.
Albert
Idézet ("Carlos E. R."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/02/2020 17.58, oszko@chem.u-szeged.hu wrote: | Dear all, | | In the last few days there was a big TW upgrade with more than 1300 | items. I am glad, I could reboot. But...
Did it crash during the update?
...
| i use TW with KDE | | Please help, where should I begin to tidy up things?
Probably corrupt rpm database, as Patrick says.
- -- Cheers / Saludos,
Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXkMHYQAKCRC1MxgcbY1H 1XpEAJ0XqrbNIB0oLjFZQXVCbLPgPcqLcQCfY9EHDVYx6YATSH7r5krGnHD4MuY= =qnFn -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2020-02-12 a las 15:51 +0100, oszko@chem.u-szeged.hu escribió:
Well, I rebuilt the database, rebooted, but got back to the point where I started. I forgot to mention that after rebooting after that big upgrade the date and time were set to a value back in 2015. Even the month, day and hour did not match. Finally I culd set it back to manual, but other Yast modules do not work.
After rebuilding the database you had to reinstall everything that it is missing. Maybe zypper dup, maybe reinstall some patterns. - -- Cheers Carlos E. R. (from openSUSE 15.1 (Legolas)) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXkQiWBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVutkAnj3l2tAoBu/zzb7pg/5H v37gLnjGAJ9+zQlBQ5y9J/v7mZroW44TRJ02lA== =nbbr -----END PGP SIGNATURE-----
In data mercoledì 12 febbraio 2020 15:51:33 CET, oszko@chem.u-szeged.hu ha scritto:
Well, I rebuilt the database, rebooted, but got back to the point where I started. I forgot to mention that after rebooting after that big upgrade the date and time were set to a value back in 2015. Even the month, day and hour did not match. Finally I culd set it back to manual, but other Yast modules do not work.
Albert
Idézet ("Carlos E. R."
): -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/02/2020 17.58, oszko@chem.u-szeged.hu wrote: | Dear all, | | In the last few days there was a big TW upgrade with more than 1300 | items. I am glad, I could reboot. But...
Did it crash during the update?
...
| i use TW with KDE | | Please help, where should I begin to tidy up things?
Probably corrupt rpm database, as Patrick says.
- -- Cheers / Saludos,
Carlos E. R. (from 15.1 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXkMHYQAKCRC1MxgcbY1H 1XpEAJ0XqrbNIB0oLjFZQXVCbLPgPcqLcQCfY9EHDVYx6YATSH7r5krGnHD4MuY= =qnFn -----END PGP SIGNATURE-----
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. Now, normally when you have an issue with the BIOS date and time, after a reboot, it would be prudent to ask: how many years has the mainboard of service. The mainboard battery may be close to failure and maybe it was the first sign of it. I am not aware of an issue with upgrades that could "reset" or alter the time and date.
My advice would be: rpmdb --rebuilddb zypper clean zypper rf zypper dup I had an issue with one file during that update (a debug one) that would brake the process always. And there was suddenly no space in root. So I cleaned all the mess, did zypper clean, fr, dup and restarted, all went smooth. Maybe one of the mirror was not completely synced when you did it? _________________________________________________________________ ________________________________________________________ Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13/02/2020 10.19, stakanov wrote: | In data mercoledì 12 febbraio 2020 15:51:33 CET, | oszko@chem.u-szeged.hu ha scritto: ... | Now, normally when you have an issue with the BIOS date and time, | after a reboot, it would be prudent to ask: how many years has the | mainboard of service. The mainboard battery may be close to failure | and maybe it was the first sign of it. I am not aware of an issue | with upgrades that could "reset" or alter the time and date. That's a good point, yes. Maybe the scripts that set the time during boot are missing (or Internet is not available), but in that case the time would be simply that of the BIOS. | | My advice would be: rpmdb --rebuilddb zypper clean zypper rf zypper | dup And probably make sure the time is correct before running them. I don't know what weird things can happen if the computer uses a very wrong time. | I had an issue with one file during that update (a debug one) that | would brake the process always. And there was suddenly no space in | root. So I cleaned all the mess, did zypper clean, fr, dup and | restarted, all went smooth. Maybe one of the mirror was not | completely synced when you did it? - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXkUq5gAKCRC1MxgcbY1H 1au2AJ9/dIZPfT3CrDBny2dVF+MzG5zfUwCfXhTf0Pvv35aGxjoaN4uhzkQIdoE= =oA7V -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R.
-
oszko@chem.u-szeged.hu
-
Patrick Shanahan
-
stakanov