Fedora + Yum Problems

[n2ize]

Hello. I need the help of someone who is well versed in understanding Linux and the YUM package manager. Maybe someone can help me out on this. I was in the middle of doing a routine update via yum on a Fedora 20 (64 bit) system. I was using the standard update notifier on the panel which has always worked problem free. For some crazy and unknown reason the system shut down on me during the update. Now when I try to complete the update transaction it fails with errors telling me there are duplicate packages. For example, trying to update libuuid gives me...



[root@galois ~]# yum update libuuid
Loaded plugins: langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package libuuid.i686 0:2.24.2-1.fc20 will be updated
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: util-linux-2.24.2-1.fc20.x86_64
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libmount-2.24.2-1.fc20.x86_64
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libblkid-2.24.2-1.fc20.x86_64
---> Package libuuid.x86_64 0:2.24.2-1.fc20 will be updated
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libmount-2.24.2-1.fc20.x86_64
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libblkid-2.24.2-1.fc20.x86_64
---> Package libuuid.i686 0:2.24.2-2.fc20 will be an update
---> Package libuuid.x86_64 0:2.24.2-2.fc20 will be an update
--> Running transaction check
---> Package libuuid.i686 0:2.24.2-1.fc20 will be updated
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libmount-2.24.2-1.fc20.x86_64
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libblkid-2.24.2-1.fc20.x86_64
---> Package libuuid.x86_64 0:2.24.2-1.fc20 will be updated
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libmount-2.24.2-1.fc20.x86_64
--> Processing Dependency: libuuid = 2.24.2-1.fc20 for package: libblkid-2.24.2-1.fc20.x86_64
---> Package util-linux.x86_64 0:2.24.2-1.fc20 will be updated
---> Package util-linux.x86_64 0:2.24.2-2.fc20 will be an update
--> Finished Dependency Resolution
Error: Package: libmount-2.24.2-1.fc20.x86_64 (installed)
Requires: libuuid = 2.24.2-1.fc20
Removing: libuuid-2.24.2-1.fc20.i686 (installed)
libuuid = 2.24.2-1.fc20
Updated By: libuuid-2.24.2-2.fc20.i686 (updates)
libuuid = 2.24.2-2.fc20
Available: libuuid-2.24-2.fc20.i686 (fedora)
libuuid = 2.24-2.fc20
Error: Package: libblkid-2.24.2-1.fc20.x86_64 (installed)
Requires: libuuid = 2.24.2-1.fc20
Removing: libuuid-2.24.2-1.fc20.i686 (installed)
libuuid = 2.24.2-1.fc20
Updated By: libuuid-2.24.2-2.fc20.i686 (updates)
libuuid = 2.24.2-2.fc20
Available: libuuid-2.24-2.fc20.i686 (fedora)
libuuid = 2.24-2.fc20
You could try using --skip-broken to work around the problem
** Found 17 pre-existing rpmdb problem(s), 'yum check' output follows:
1:autocorr-en-4.2.7.2-11.fc20.noarch is a duplicate with 1:autocorr-en-4.2.7.2-9.fc20.noarch
libblkid-2.24.2-2.fc20.x86_64 is a duplicate with libblkid-2.24.2-1.fc20.x86_64
libmount-2.24.2-2.fc20.x86_64 is a duplicate with libmount-2.24.2-1.fc20.x86_64
2:libnm-qt-0.9.8.3-1.fc20.x86_64 is a duplicate with 2:libnm-qt-0.9.8.2-5.fc20.x86_64
1:libreoffice-core-4.2.7.2-11.fc20.x86_64 is a duplicate with 1:libreoffice-core-4.2.7.2-9.fc20.x86_64
1:libreoffice-opensymbol-fonts-4.2.7.2-11.fc20.noarch is a duplicate with 1:libreoffice-opensymbol-fonts-4.2.7.2-9.fc20.noarch
1:libreoffice-ure-4.2.7.2-11.fc20.x86_64 is a duplicate with 1:libreoffice-ure-4.2.7.2-9.fc20.x86_64
libuuid-2.24.2-2.fc20.x86_64 is a duplicate with libuuid-2.24.2-1.fc20.x86_64
motion-3.3.0-trunkREV557.11.fc19.x86_64 has missing requires of libavcodec.so.54()(64bit)
motion-3.3.0-trunkREV557.11.fc19.x86_64 has missing requires of libavcodec.so.54(LIBAVCODEC_54)(64bit)
motion-3.3.0-trunkREV557.11.fc19.x86_64 has missing requires of libavformat.so.54()(64bit)
motion-3.3.0-trunkREV557.11.fc19.x86_64 has missing requires of libavformat.so.54(LIBAVFORMAT_54)(64bit)
php-cli-5.5.19-3.fc20.x86_64 is a duplicate with php-cli-5.5.18-1.fc20.x86_64
php-common-5.5.19-3.fc20.x86_64 is a duplicate with php-common-5.5.18-1.fc20.x86_64
php-pdo-5.5.19-3.fc20.x86_64 is a duplicate with php-pdo-5.5.18-1.fc20.x86_64
selinux-policy-3.12.1-195.fc20.noarch is a duplicate with selinux-policy-3.12.1-193.fc20.noarch
wireshark-1.10.11-1.fc20.x86_64 is a duplicate with wireshark-1.10.10-1.fc20.x86_64


I am trying to fix this so "yum update" works again. I have already tried running "$ yum-complete-transaction" but it won't fix the problem. Searching around online has so far given me partial half-assed answers ranging from manually fixing the problem. Not sure how to go about fixing this. I tried running "$ package-cleanup --dupes" and it gives me a listing of all the duplicate packages so its definitely a multipackage issue. But where do I go from there ? Do I manually remove each of the older packages one by one ? Can I run "$ package-cleanup --cleandupes" to remove all the duplicates ? I was going to try this but I read that this can sometimes cause more problems.

In any even, short of reinstalling the entire system, what is the best way to fix this. Any helpful ideas, comments ,,etc. are appreciated.

[KC2UGV]

yum clean all

If that doesn't work, follow the steps here:
http://www.cyberciti.biz/tips/rebuilding-corrupted-rpm-database.html

(You don't really need to drop to single user for this)

[n2ize]

yum clean all

If that doesn't work, follow the steps here:
http://www.cyberciti.biz/tips/rebuilding-corrupted-rpm-database.html

(You don't really need to drop to single user for this)

Much thanks. I'll give it a try when I get back home. I'll let you know how it works out.

[n2ize]

yum clean all

If that doesn't work, follow the steps here:
http://www.cyberciti.biz/tips/rebuilding-corrupted-rpm-database.html

(You don't really need to drop to single user for this)

Okay, so far "$yum clean all" doesn't do the trick. So, I am going to have to check out the link you provided and see if I can find an answer there.

In the future I will make sure to never interrupt a yum update, either accidentally (as in this case) or intentionally. I think I'll do all my future updates in single user mode with as few processes as needed running in the background.

[n2ize]

The problem seems to be that YUM is seeing 2 packages for each package it's trying to update. In other words it's seeing duplicates... the old version and the new version which is also yielding dependency issues. One would think it's a simple matter to fix an interrupted routine update but apparently it is not.

[KC2UGV]

The problem seems to be that YUM is seeing 2 packages for each package it's trying to update. In other words it's seeing duplicates... the old version and the new version which is also yielding dependency issues. One would think it's a simple matter to fix an interrupted routine update but apparently it is not.

No, it's really not... You could do a yum erase on the package it's seeing a dupe of. The rebuilding of the rpm db is a pretty safe maneuver. Do backups of the db files.

[n2ize]

No, it's really not... You could do a yum erase on the package it's seeing a dupe of. The rebuilding of the rpm db is a pretty safe maneuver. Do backups of the db files.

OK I'll try that. I was thinking of doing that earlier but I wasn't sure. I guess I would delete the older package assuming the newer package was properly installed ??

[NA4BH]

https://www.youtube.com/watch?v=ztA0AJxHqQ8

[n2ize]

https://www.youtube.com/watch?v=ztA0AJxHqQ8

Thanks. A little light hearted humor is always welcome. :) While I am dealing with a red fedora here I got a smile out of the green fedora. Cute classic cartoon.

[n2ize]

No, it's really not... You could do a yum erase on the package it's seeing a dupe of. The rebuilding of the rpm db is a pretty safe maneuver. Do backups of the db files.

Okay, so far so good. I first tried to use "# yum erase" to remove the dupes but it wanted to also remove all packages that were dependent on the dupe. So I used "rpm -e --nodeps <dupe-package-name>" and that seemed to clear the dupes. I did them manually one by one, fortunately there weren't too many, otherwise I would have had to write a shell program to do it quicker. Okay, once the dupes were cleared I did a "# yum clean all" and a "# rpm --rebuilddb" and all seems okay now. I did a system update and it went okay. So, as long as no unexpected glitches kick in I'll label this problem as FIXED. Much thanks for your help.

[W2NAP]

I never use the gui update notifier, I always run updates in terminal. I just don't trust the gui stuff on updates been burned before by it.

[KK4AMI]

I kicked out some bucks on ebay for a 32Gb Multiboot Thumb drive with Linux operating systems. Our Computers for Kids program gets a lot of junk computers that I could assemble into licenseless machines. Microsoft MAR licenses are not supposed to be put on machines that didn't already have licenses. Linux looks like a good way to go if I can figure out how to set it up for kids. My thumb drive has Bohdi, Fedora, DSL,Kubuntu,Mint 17, Lubuntu 14.04, Tails, Ubuntu 14.04, UbuntuStudio and Ubuntu Gnome. I'm working with Ubuntu Studio right now on a 32 bit AMD machine. It seems to work well, except for getting all the video to work (Adobe Flash issues). I'm still learning, but I kind of like working in the terminal, vs Ubuntu Software Center. So far it has been fun to explore Linux.

[n2ize]

I never use the gui update notifier, I always run updates in terminal. I just don't trust the gui stuff on updates been burned before by it.

I've had very good luck with the GUI update notifier. Until yesterday. But I don't know if it was the updater that failed or perhaps something I did that was unrelated to the updater. The system just shut down unexpectedly. I guess if I get a chance I could check the system logs and maybe that might reveal what caused the failure. Meanwhile I seemed to have managed to fix it. I was notified of some updates and the updater did its job with no issues. BTW on earlier versions I always did my updates in a terminal. Earlier versions of the GUI were not as stable and seemed very slow. These days the GUi seems to be very reliable.

[n2ize]

I kicked out some bucks on ebay for a 32Gb Multiboot Thumb drive with Linux operating systems. Our Computers for Kids program gets a lot of junk computers that I could assemble into licenseless machines. Microsoft MAR licenses are not supposed to be put on machines that didn't already have licenses. Linux looks like a good way to go if I can figure out how to set it up for kids. My thumb drive has Bohdi, Fedora, DSL,Kubuntu,Mint 17, Lubuntu 14.04, Tails, Ubuntu 14.04, UbuntuStudio and Ubuntu Gnome. I'm working with Ubuntu Studio right now on a 32 bit AMD machine. It seems to work well, except for getting all the video to work (Adobe Flash issues). I'm still learning, but I kind of like working in the terminal, vs Ubuntu Software Center. So far it has been fun to explore Linux.

Glad you're having fun. Video should work (on Fedora at least) as long as you have the right driver modules installed and the proper video players, codecs, etc. Try installing VLC and see how that works. Hopefully your thumbdrive systems are set up to "remember" what was installed on them between boots.

[NM5TF]

IZE....

have you installed or tried yum extender yet ???

basically a GUI "auto yum updater"......you can select to update packages or individual files....

I believe I found it thru the software updater....works great running Fedora 20 amd_64 & the
new 3.17.4-200 kernel....

FWIW & YMMV

[n2ize]

IZE....

have you installed or tried yum extender yet ???

basically a GUI "auto yum updater"......you can select to update packages or individual files....

I believe I found it thru the software updater....works great running Fedora 20 amd_64 & the
new 3.17.4-200 kernel....

FWIW & YMMV

No but I'll definitely check it out. I am always interested in trying different applications so I'll give it a go.

[NM5TF]

IZE....

have you updated to Fedora 21 yet ???

if so, did it work ???

there seems to be major bugs with the new 3.17.6-300 kernel & nvidia video cards using the nvidia 304.123 drivers.....

I had to fallback to Nouveau with .nomodeset=1 to even get to the desktop.....still getting random screen freezes....

[W2NAP]

IZE....

have you updated to Fedora 21 yet ???

if so, did it work ???

there seems to be major bugs with the new 3.17.6-300 kernel & nvidia video cards using the nvidia 304.123 drivers.....

I had to fallback to Nouveau with .nomodeset=1 to even get to the desktop.....still getting random screen freezes....

yep major issue. I did the upgrade and could no longer launch chrome (or FF but thats been a long standing issue) without the machine locking up and scrambling the screen.. tried the latest lubuntu as well which has the 3.17 kern same problem. fell back to debian 7 lxde 3.2 kern everything works so yeah big issue with 3.17

[n2ize]

IZE....

have you updated to Fedora 21 yet ???

if so, did it work ???

there seems to be major bugs with the new 3.17.6-300 kernel & nvidia video cards using the nvidia 304.123 drivers.....

I had to fallback to Nouveau with .nomodeset=1 to even get to the desktop.....still getting random screen freezes....

No, not yet. I am going to do the upgrade soon but on my "test machine" first and see how it goes. My guess is that any problems will be fixed in the upgrade/bugfixes. Fedora is like that. But then it's a "proving ground" and we are the "test pilots".

[NM5TF]

I took the plunge & wiped Fedora 21

re-installed Fedora 20....back to "normal" again.....even with nvidia drivers & 3.17.4 kernel....

the major screwup happened with the release of the 3.17.6 kernel....someone screwed the pooch there...

[n2ize]

I took the plunge & wiped Fedora 21

re-installed Fedora 20....back to "normal" again.....even with nvidia drivers & 3.17.4 kernel....

the major screwup happened with the release of the 3.17.6 kernel....someone screwed the pooch there...

Has a bug report been filed ? Is the problem mainly isolated to nvidia drivers or does it encompass other video systems ? One thing I do hate about upgrades is when they break things that have been working well in earlier versions. My guess is that the problem will be fixed. You might try the upgrade again in a couple of months. Or just wait till Fedora 22 comes out. I usually wait at least a month or so after the official release date before I upgrade. I also apply the upgrade on a test machine before I commit my main system to the upgrade.

What app did you use for the upgrade ? Did you use YUM or Fedup ? Also did you install via an ISO image or via a network upgrade?

[NM5TF]

many bug reports have been filed...not sure if only nvidia, may be others...check the Forums....

Fedora upgrades have been working flawlessly until the upgrade to kernel 3.17.6....

used FedUp with network install....seemed to take several hours.....next time will just download iso & use
Unetbootin...has never failed me yet...

[n2ize]

many bug reports have been filed...not sure if only nvidia, may be others...check the Forums....

Fedora upgrades have been working flawlessly until the upgrade to kernel 3.17.6....

used FedUp with network install....seemed to take several hours.....next time will just download iso & use
Unetbootin...has never failed me yet...

I used fedUP to go from 19-20 last summer and it went pretty smooth. Is partially broke one or two programs that I run under mono but I was still able to run them. Seems that after a glibc update the problem went away and everything worked perfect. I plan to do the upgrade from 20 to 21 on my "test machine" this week. If it goes smooth and all seems well then I'll do the upgrade on this machine. Otherwise I'll wait till they fix it.

At present I'm running kernel 3.17.7-200 on Fedora 20 and all is good.