Re: mkconfig mis-identifies windows
On 12/09/2014 07:44 PM, Adam Williamson wrote: On Tue, 2014-12-09 at 19:14 -0500, Frank McCormick wrote: I've been running 21 for a while now and just noticed that grub2-mkconfig misidentifies my Windows partition. It used to correctly put Windows 7 in the grub.cfg...but now is calling it Windows Vista. Not a big deal...but I thought someone should know. Is it worth a bug ? Sure, I think it'd go against the os-prober package. Bug 1172405 has been added to the database -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
mkconfig mis-identifies windows
I've been running 21 for a while now and just noticed that grub2-mkconfig misidentifies my Windows partition. It used to correctly put Windows 7 in the grub.cfg...but now is calling it Windows Vista. Not a big deal...but I thought someone should know. Is it worth a bug ? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Nitrogen
My favorite wallpaper setter Nitrogen has been orphanedso it's unavailable from the repositories. I run IceWm sometimes...and switch backgrounds quite often and nitrogen was the only piece of software that did it for me. Is there anyway I can get the last version for 19 ? -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[SOLVED] Re: grub2-mkconfig not picking up all kernels on another partition
On 06/23/2013 10:04 PM, Frank McCormick wrote: On 06/23/2013 08:18 PM, Matthew Miller wrote: On Sun, Jun 23, 2013 at 03:54:33PM -0600, Chris Murphy wrote: bash -x grub2-mkconfig -o /boot/grub2/grub.cfg Post the result somewhere, then post the URL here. Sounds like an OS Prober issue, which is more problematic on UEFI than BIOS usually. Try fpaste: $ echo foo |fpaste Uploading (0.1KiB)... http://ur1.ca/ef6v3 ->http://paste.fedoraproject.org/20400/20331081 Further checking shows mkconfig IS putting all the kernels into grub.cfg the problem is now grub is not displaying them! And it's happening on 19 and on 18. Too tired tonight to pursue this further...I'll tackle it again tomorrow. Thanks Chris and Matthew ! I checked grub.cfg again and it does contains all the kernels...so then I stripped down /etc/default/grub.cfg to the bare minimum and lo and behold all the kernels display. I don't know which option or if any option was fouling up the display..but I am happy even with the resulting bare bones menu. Thanks -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: rsyslog
On 06/15/2013 03:43 PM, Adam Williamson wrote: On Sat, 2013-06-15 at 15:40 -0400, Frank McCormick wrote: Update wants to replace rsyslog on my system- I have downgraded rsyslog to handle the "spamming log problem". [root@franksfedora19 frank]# yum update Loaded plugins: langpacks, refresh-packagekit Resolving Dependencies --> Running transaction check ---> Package rsyslog.i686 0:7.2.6-1.fc19 will be updated ---> Package rsyslog.i686 0:7.4.0-1.fc19 will be an update --> Finished Dependency Resolution Is it safe now to allow it to be upgraded ? if you have updated to systemd 204-8, it ought to be safe. I have. If you have inflated logs from the SELinux accounts-daemon bug, then rsyslog will still run the CPU to 100% for some time after the upgrade, because it'll be writing the entire journal out to /var/log/messages; but it will eventually complete and quiet down. Personally I recommend pruning the journal first if you have a huge journal full of those SELinux messages - if your system logs aren't that important to you, you can safely just blow away the larger (over 10MB) files in /var/log/journal and that should trim the journal down to a reasonable size. I chose to deleteseems to be running fine...but I'll keep an eye on it for a while. Thanks -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[SOLVED] Repairing truncated file
On 06/04/2013 12:40 PM, Michael Schwendt wrote: On Tue, 04 Jun 2013 10:58:59 -0400, Frank McCormick wrote: Do you run ldconfig as root? Yes What files /etc/ld.so.cache* do you have? [frank@franksfedora19 ~]$ ls /etc/ld.so.cache* /etc/ld.so.cache [frank@franksfedora19 ~]$ What does "ldconfig -v" show about that library? This comes first ldconfig: Path `/usr/lib' given more than once ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated then the list of the libraries it knows about. That means the file does exist. How have you searched for the file? Found it !!! I had been looking adjacent to the originalbut it was at the very bottom of the list in the file manager I use (midnight commander) - When you insisted the file did exist, I did another search. It doesn't exist now...and ldconfig is happy: [frank@franksfedora19 lib]$ sudo ldconfig -v ldconfig: Path `/usr/lib' given more than once /usr/lib/iscsi: libiscsi.so.1 -> libiscsi.so.1.0.10700 /usr/lib/llvm: libLLVM-3.3.so -> libLLVM-3.3.so libprofile_rt.so -> libprofile_rt.so libLTO.so -> libLTO.so etc etc The temporary file will never belong into any package (in case you try to run a query for its path). I did and found nothing. Thanks for all your help. -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Repairing truncated file
On 06/04/2013 11:48 AM, Adam Williamson wrote: On Tue, 2013-06-04 at 09:42 -0400, Frank McCormick wrote: On 06/04/2013 01:07 AM, Michal Jaegermann wrote: The file that is there is libQtOpenGL.so.4.8.4 along with two symbolic links pointing to it. So ldconfig did its job. It appears that there is nothing wrong with your installation. There must be something wrong as ldconfig keeps reporting this truncated file which doesn't exist :) If you are not sure to which packages belongs a specific file you can run a verification step like that: rpm -Vf /lib/libQtOpenGL.so.4.8.4 where a file you are referencing has to exist. That also reports nothing, so it appears rpm isn't aware of the file/package even though it has been erased and re installed a few times now. I think some people are missing that the file does not actually exist once the package install process is complete. To me, it sounds like an ldconfig is somehow being run from the package's scriptlets before extraction of the files from the RPM is actually complete. This all came about after an update was aborted by a hardware failure. Unfortunately I don't recall what I did after the aborted update...as it was several weeks ago. I **assume** I redid the update and after the next package was handled, ldconfig was run for it.but the extraction/handling of files from qt-x11 had not been completed. The question now is how I get rid of that "/usr/lib/ is truncated" warning. Reinstalls and re-running ldconfig after cache deletion doesn't work. -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: updating 19
On 06/04/2013 11:09 AM, Adam Williamson wrote: On Tue, 2013-06-04 at 10:36 -0400, Frank McCormick wrote: I attempted to update my 19 this morning...what does this mean ? [frank@franksfedora19 ~]$ sudo yum check-update Loaded plugins: langpacks, refresh-packagekit An update notice is broken, or duplicate, skipping: updates-testing/FEDORA-2013-9550 [frank@franksfedora19 ~]$ https://bugzilla.redhat.com/show_bug.cgi?id=960642 Good to know. I guess patience is a virtue :) -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Repairing truncated file
On 06/04/2013 09:57 AM, Michael Schwendt wrote: On Tue, 04 Jun 2013 09:42:19 -0400, Frank McCormick wrote: There must be something wrong as ldconfig keeps reporting this truncated file which doesn't exist :) Do you run ldconfig as root? Yes What files /etc/ld.so.cache* do you have? [frank@franksfedora19 ~]$ ls /etc/ld.so.cache* /etc/ld.so.cache [frank@franksfedora19 ~]$ What does "ldconfig -v" show about that library? This comes first ldconfig: Path `/usr/lib' given more than once ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated then the list of the libraries it knows about. It's _good_ that nothing is reported, because -Vf means "verify the package this file belongs into". The query to show a package a file belongs into is this: rpm -qf /lib/libQtOpenGL.so.4.8.4 [frank@franksfedora19 ~]$ rpm -qf /lib/libQtOpenGL.so.4.8.4 qt-x11-4.8.4-19.fc19.i686 [frank@franksfedora19 ~] -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
updating 19
I attempted to update my 19 this morning...what does this mean ? [frank@franksfedora19 ~]$ sudo yum check-update Loaded plugins: langpacks, refresh-packagekit An update notice is broken, or duplicate, skipping: updates-testing/FEDORA-2013-9550 [frank@franksfedora19 ~]$ -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Repairing truncated file
On 06/04/2013 01:07 AM, Michal Jaegermann wrote: The file that is there is libQtOpenGL.so.4.8.4 along with two symbolic links pointing to it. So ldconfig did its job. It appears that there is nothing wrong with your installation. There must be something wrong as ldconfig keeps reporting this truncated file which doesn't exist :) If you are not sure to which packages belongs a specific file you can run a verification step like that: rpm -Vf /lib/libQtOpenGL.so.4.8.4 where a file you are referencing has to exist. That also reports nothing, so it appears rpm isn't aware of the file/package even though it has been erased and re installed a few times now. Is there a way to re build the info that rpm has ? -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Repairing truncated file
On 06/03/2013 11:40 PM, Sérgio Basto wrote: On Dom, 2013-06-02 at 19:14 -0400, Frank McCormick wrote: On 06/02/2013 06:50 PM, Frank McCormick wrote: On 06/02/2013 02:06 PM, Sérgio Basto wrote: On Dom, 2013-06-02 at 13:23 -0400, Frank McCormick wrote: On 06/02/2013 01:12 PM, Frank McCormick wrote: After an aborted yum update recently I began to notice ldconfig complaining about a truncated file Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated Verifying : 1:qt-x11-4.8.4-19.fc19.i686 I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers Further to this I found out the rpm file containing that library is :qt-x11-4.8.4-19.fc19.i686 and I re installed. However ldconfig is still complaining the file is truncated and the message has that added "; 51a94e8f on the end . How to fix ..anyone ? rm /lib/libQtOpenGL.so.4.8.4;51a94e8f yum reinstall qt-x11 I'll try removing it first. Doesn't work. Erased the offending files and re installed but ldconfig still complains about the truncated file. And what is the ;51a94e8f on the end of the file ? if /lib/libQtOpenGL.so.4.8.4;51a94e8f doesn't exit , and qt-x11 is correctly installed rpm -V qt-x11 what says ? Nothing at all. /lib/libQtOpenGL.so.4.8.4;51a94e8f does not actually exist, at least not in /lib The file that is there is libQtOpenGL.so.4.8.4 along with two symbolic links pointing to it. Erasing all three, then erasing and re installing qt-x11xxx does nothing. As was pointed out here already, the file name with those extra characters on the end is a temp file created as part of the install procedure. If it actually exists on the disk , I can't find it. ldconfig -i don't fix it ? No it doesn't. -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Repairing truncated file
On 06/03/2013 04:40 PM, Michal Jaegermann wrote: On Sun, Jun 02, 2013 at 07:14:15PM -0400, Frank McCormick wrote: And what is the ;51a94e8f on the end of the file ? This is one of temporary suffixes used to create temporary targets when unpacking an update rpm. If you are seeing something of that sort that means that something got screwy and a rename to a "final" form did not happen. I have seen something of that sort on occasions when a package update tried to replace directly a file with a symlink or vice-versa (or another mixup of that sort). What is really messed up in your case it is not really possible to tell from what you are saying but something definitely is. Deleting the file..then removing the rpm and re installing it doesn't change anything. Neither does deleting ldconfig's cache, or re installing GLIBC . It's a resistant error if nothing else. The good new is it doesn't **seem** to affect any of the software I use on a daily basis. If and when it does, I have 3 other partitions of usable Linux distros :) -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Repairing truncated file
On 06/03/2013 09:36 AM, Ralf Corsepius wrote: On 06/03/2013 02:43 PM, Frank McCormick wrote: On 06/03/2013 01:09 AM, Adam Williamson wrote: On Sun, 2013-06-02 at 19:14 -0400, Frank McCormick wrote: Doesn't work. Erased the offending files and re installed but ldconfig still complains about the truncated file. And what is the ;51a94e8f on the end of the file ? Have you run out of disk space? No 40% used. Wild guess: You might have run out of memory due to /tmp on /tmpfs. I have occasionally hit such issues during yum runs on low RAM machines. Ralf It's possible I guess...this machine only has one gig and even with barebones windows managers will usually utilize the swap. But that still begs the question how do I fix this truncated file ? -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Repairing truncated file
On 06/03/2013 01:09 AM, Adam Williamson wrote: On Sun, 2013-06-02 at 19:14 -0400, Frank McCormick wrote: Doesn't work. Erased the offending files and re installed but ldconfig still complains about the truncated file. And what is the ;51a94e8f on the end of the file ? Have you run out of disk space? No 40% used. [frank@localhost ~]$ df Filesystem 1K-blocksUsed Available Use% Mounted on /dev/sda3 13831448 5178960 7943220 40% / devtmpfs 501352 0501352 0% /dev tmpfs 505224 0505224 0% /dev/shm tmpfs 505224 852504372 1% /run tmpfs 505224 0505224 0% /sys/fs/cgroup tmpfs 505224 4505220 1% /tmp /dev/sda5 222666372 9267220 202081700 5% /media/sda5 /dev/sda7 113656464 5472556 107028088 5% /media/sda7 /dev/sda2 13979216 5701136 7561300 43% /media/sda2 I have since re installed glibc (for ldconfig) and no change. I have Googled the problem but came up with almost nothing - maybe I am using the wrong terms. -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Repairing truncated file
On 06/02/2013 06:50 PM, Frank McCormick wrote: On 06/02/2013 02:06 PM, Sérgio Basto wrote: On Dom, 2013-06-02 at 13:23 -0400, Frank McCormick wrote: On 06/02/2013 01:12 PM, Frank McCormick wrote: After an aborted yum update recently I began to notice ldconfig complaining about a truncated file Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated Verifying : 1:qt-x11-4.8.4-19.fc19.i686 I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers Further to this I found out the rpm file containing that library is :qt-x11-4.8.4-19.fc19.i686 and I re installed. However ldconfig is still complaining the file is truncated and the message has that added "; 51a94e8f on the end . How to fix ..anyone ? rm /lib/libQtOpenGL.so.4.8.4;51a94e8f yum reinstall qt-x11 I'll try removing it first. Doesn't work. Erased the offending files and re installed but ldconfig still complains about the truncated file. And what is the ;51a94e8f on the end of the file ? -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Repairing truncated file
On 06/02/2013 02:06 PM, Sérgio Basto wrote: On Dom, 2013-06-02 at 13:23 -0400, Frank McCormick wrote: On 06/02/2013 01:12 PM, Frank McCormick wrote: After an aborted yum update recently I began to notice ldconfig complaining about a truncated file Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated Verifying : 1:qt-x11-4.8.4-19.fc19.i686 I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers Further to this I found out the rpm file containing that library is :qt-x11-4.8.4-19.fc19.i686 and I re installed. However ldconfig is still complaining the file is truncated and the message has that added "; 51a94e8f on the end . How to fix ..anyone ? rm /lib/libQtOpenGL.so.4.8.4;51a94e8f yum reinstall qt-x11 I'll try removing it first. -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Repairing truncated file
On 06/02/2013 01:12 PM, Frank McCormick wrote: After an aborted yum update recently I began to notice ldconfig complaining about a truncated file Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated Verifying : 1:qt-x11-4.8.4-19.fc19.i686 I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers Further to this I found out the rpm file containing that library is :qt-x11-4.8.4-19.fc19.i686 and I re installed. However ldconfig is still complaining the file is truncated and the message has that added "; 51a94e8f on the end . How to fix ..anyone ? -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Repairing truncated file
After an aborted yum update recently I began to notice ldconfig complaining about a truncated file Transaction test succeeded Running transaction Installing : 1:qt-x11-4.8.4-19.fc19.i686 1/1 /sbin/ldconfig: file /lib/libQtOpenGL.so.4.8.4;51a94e8f is truncated Verifying : 1:qt-x11-4.8.4-19.fc19.i686 I have tried to fine out which file contains the library but yum whatprovides doesn't return any answers Help ? Thanks -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: video players in 19
On 05/29/2013 04:51 PM, Chuck Forsberg WA7KGX N2469R wrote: On 05/29/2013 01:46 PM, Frank McCormick wrote: Is VLC or Mplayer available for 19 (32 bit). If so where. It isn't in Fedoras repositories and I hesitate to install it from anywhere else. I'm running a newly installed Beta Thanks -- --Cheers-- Rpmfusion works for me, at least for 64 bit vlc and ffmpeg. http://rpmfusion.org OK, that worked. Thanks..I had forgotten about rpmfusion. -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
video players in 19
Is VLC or Mplayer available for 19 (32 bit). If so where. It isn't in Fedoras repositories and I hesitate to install it from anywhere else. I'm running a newly installed Beta Thanks -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Attempt to recover
On 05/25/2013 05:24 PM, Michal Jaegermann wrote: On Sat, May 25, 2013 at 11:22:38AM -0400, Frank McCormick wrote: Being the stubborn person I am I am attempting to recover my 19 system. I chrooted into 19 from 18 and ran package-clean --problems . I have reinstalled libxvmc...but for some reason the system still thinks it's incomplete Are you sure that you installed in the right system (rpm has an option -r)? If yes then maybe a wrong version? No I have since reinstalled a long list of packages...and they are in the right system. I than ran ldconfig # ldconfig: File /lib/libqpdf.so.10.1.0 is empty, not checked. ldconfig: File /lib/libdialog.so.11.1.0 is empty, not checked. Does 'rpm -qf /lib/libqpdf.so.10.1.0' says that they belong to installed packages? Maybe these are just leftovers? Yes you're right there. They belong to packages I added later. 'rpm -Va' will test an integrity of all packages present in the current database. Redirect an output and check results later. It is really hard to guess what you possibly removed. A trivial reason you are failing to boot could be that you are attempting to use a new kernel for which initramfs was not yet build. This happens in %posttrans package script and you apparently crashed before this had a chance to run. Michal I did rpm -Va.and the list is huge. There is apparently so much wrong now...I think I'll wait until 19 Beta to reinstall it. I didn't think an interrupted update could cause so much trouble. -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Attempt to recover
Being the stubborn person I am I am attempting to recover my 19 system.
I chrooted into 19 from 18 and ran package-clean --problems
This is what it spewed out
Unable to connect to dbus
Package libXvMC-1.0.7-6.20130524gite9415ddef.fc19.i686 has missing
requires of config(libXvMC) = ('0', '1.0.7', '6.20130524gite9415ddef.fc19')
Package xorg-x11-drv-intel-2.21.6-1.fc19.i686 has missing requires of
libXvMC.so.1
Package xorg-x11-drv-openchrome-0.3.3-1.fc19.i686 has missing requires
of libXvMC.so.1
I have reinstalled libxvmc...but for some reason the system still thinks
it's incomplete
I than ran ldconfig
# ldconfig: File /lib/libqpdf.so.10.1.0 is empty, not checked. ldconfig:
File /lib/libdialog.so.11.1.0 is empty, not checked.
Any suggestions?
Thanks
--
--Cheers--
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Re: Big problem with an update
On 05/25/2013 12:32 AM, Adam Williamson wrote: On Fri, 2013-05-24 at 23:01 -0400, Frank McCormick wrote: I am a relative newcomer to Fedora (I'm a Debian refugee) so my knowledge of yum at the moment is pretty minimal. Does anyone have any suggestions on how this can be fixed? The system still boots fine FWIW, the few times I got stuck in a case like that, I rpm -V'ed the newer dupes, and if that resulted in an OK, you can do this: rpm -e --justdb --noscripts (older version) what that basically does is simply remove the entry from the RPM database without running any scriptlets or actually deleting any files from the filesystem. I wish now had waited rather than running tum complete transaction ( which it never did) as it ended up marking the transaction files as invalid. It was then I ran package cleanup and that's what left my partition unbootable. Thanks for the suggestions anyway :) -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Big problem with an update
On 05/24/2013 11:39 PM, Frank McCormick wrote: On 05/24/2013 11:08 PM, Christopher Meng wrote: Tell us your "yum history" Too late Christopher - found "package-cleanup --dupes" in the Fedora forums (and a suggestion from another user on the regular list) - so I tried it - now the 19 partition is unbootable :) So it sort of solved my problem. Package cleanup ran into a bunch of what it said were zero-length files..dunno what it did or didn't do with them..nothing I guess. But it appears some . many or all were essential. Anyway I can roll back time to a few hours ago :) A second problem Christopher is there is no history for tonight when it happened. I guess Yum/RPM writes the file after/during the update process, which never ended properly. The partition still boots but ends up with the message of no /boot/init so I get a sh-4.2 prompt on a read-only partition. A fine state of affairs :) --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Big problem with an update
On 05/24/2013 11:35 PM, Ed Greshko wrote: Frank McCormick wrote: On 05/24/2013 11:23 PM, Ed Greshko wrote: Frank McCormick wrote: I was updating Fedora 19 tonight when my system crashed ( I suspect it's a memory error)but anyway it now **appears I have a lot of duplicate files on my system, at least that what yum check all reports. The crash happened after the updates had been installed I think during the verify stage. This is a partial list of what "yum check all" reports: Try package-cleanup --dupes Yeah, that's what I found in the Fedora forums. So I tried it. Now the partition won't boot. package-cleanup --dupes removed the dupes..at least it said it wasbut it also ran into a bunch of files it said were zero-length...what it did about them I don't know. Short version: the partition is now unbootable. So I am back in Fedora 18...where I think I'll stay for a while. I don't anticipate re-installing 19...at least not for a while. The only comforting thing is that this same problem could happen no matter what version you're running. :-) Since F19 is beta it isn't a big deal IMHO. I've had similar things go wrong, disk problems, and getting it fixed took time and effortbut I was able to recover. Yeah maybe I'll reinstall when 19 is released, Or maybe not. Thanks anyway for the suggestion - it seems it's about the only thing that could be done under the circumstances -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Big problem with an update
On 05/24/2013 11:08 PM, Christopher Meng wrote: Tell us your "yum history" Too late Christopher - found "package-cleanup --dupes" in the Fedora forums (and a suggestion from another user on the regular list) - so I tried it - now the 19 partition is unbootable :) So it sort of solved my problem. Package cleanup ran into a bunch of what it said were zero-length files..dunno what it did or didn't do with them..nothing I guess. But it appears some . many or all were essential. Anyway I can roll back time to a few hours ago :) -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Big problem with an update
On 05/24/2013 11:23 PM, Ed Greshko wrote: Frank McCormick wrote: I was updating Fedora 19 tonight when my system crashed ( I suspect it's a memory error)but anyway it now **appears I have a lot of duplicate files on my system, at least that what yum check all reports. The crash happened after the updates had been installed I think during the verify stage. This is a partial list of what "yum check all" reports: Try package-cleanup --dupes Yeah, that's what I found in the Fedora forums. So I tried it. Now the partition won't boot. package-cleanup --dupes removed the dupes..at least it said it wasbut it also ran into a bunch of files it said were zero-length...what it did about them I don't know. Short version: the partition is now unbootable. So I am back in Fedora 18...where I think I'll stay for a while. I don't anticipate re-installing 19...at least not for a while. -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Big problem with an update
I was updating Fedora 19 tonight when my system crashed ( I suspect it's a memory error)but anyway it now **appears I have a lot of duplicate files on my system, at least that what yum check all reports. The crash happened after the updates had been installed I think during the verify stage. This is a partial list of what "yum check all" reports: Loaded plugins: langpacks, refresh-packagekit SDL-1.2.15-8.fc19.i686 is a duplicate with SDL-1.2.15-7.fc19.i686 1:autocorr-en-4.0.3.3-3.fc19.noarch is a duplicate with 1:autocorr-en-4.0.3.3-2.fc19.noarch 1:cups-1.6.2-7.fc19.i686 is a duplicate with 1:cups-1.6.2-4.fc19.i686 1:cups-filesystem-1.6.2-7.fc19.noarch is a duplicate with 1:cups-filesystem-1.6.2-4.fc19.noarch 1:cups-libs-1.6.2-7.fc19.i686 is a duplicate with 1:cups-libs-1.6.2-4.fc19.i686 desktop-backgrounds-compat-19.0.0-2.fc19.noarch is a duplicate with desktop-backgrounds-compat-19.0.0-1.fc19.noarch desktop-backgrounds-gnome-19.0.0-2.fc19.noarch is a duplicate with desktop-backgrounds-gnome-19.0.0-1.fc19.noarch dialog-1.2-2.20130523.fc19.i686 is a duplicate with dialog-1.2-1.20121230.fc19.i686 dmraid-1.0.0.rc16-21.fc19.i686 is a duplicate with dmraid-1.0.0.rc16-20.fc19.i686 dmraid-events-1.0.0.rc16-21.fc19.i686 is a duplicate with dmraid-events-1.0.0.rc16-20.fc19.i686 dracut-027-46.git20130430.fc19.i686 is a duplicate with dracut-027-45.git20130430.fc19.i686 dracut-network-027-46.git20130430.fc19.i686 is a duplicate with dracut-network-027-45.git20130430.fc19.i686 glusterfs-3.4.0-0.5.beta2.fc19.i686 is a duplicate with glusterfs-3.4.0-0.4.beta1.fc19.i686 glusterfs-api-3.4.0-0.5.beta2.fc19.i686 is a duplicate with glusterfs-api-3.4.0-0.4.beta1.fc19.i686 glusterfs-fuse-3.4.0-0.5.beta2.fc19.i686 is a duplicate with glusterfs-fuse-3.4.0-0.4.beta1.fc19.i686 1:grub2-2.00-18.fc19.i686 is a duplicate with 1:grub2-2.00-16.fc19.i686 1:grub2-efi-2.00-18.fc19.i686 is a duplicate with 1:grub2-efi-2.00-16.fc19.i686 1:grub2-tools-2.00-18.fc19.i686 is a duplicate with 1:grub2-tools-2.00-16.fc19.i686 The list goes on and on... I am a relative newcomer to Fedora (I'm a Debian refugee) so my knowledge of yum at the moment is pretty minimal. Does anyone have any suggestions on how this can be fixed? The system still boots fine I wrote this message originally on the regular users list but at least one person took exception to it even though it's not an F19 problem specifically. Thanks -- --Cheers-- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
