Just recently noticed that after upgrading to FC7, X-windows starts and just sits there with an X cursor with just the FC wallpaper (I normally use/play through SSH). I'm not familiar enough with the connection between X and Gnome to know where to look next. Anyone have any suggestions as to how to proceed?
Edward DeMeulle wrote:
Just recently noticed that after upgrading to FC7, X-windows starts and just sits there with an X cursor with just the FC wallpaper (I normally use/play through SSH). I'm not familiar enough with the connection between X and Gnome to know where to look next. Anyone have any suggestions as to how to proceed?
The first thing I would do is create a new user, and see if they if it works for them. (It probably will.) If this works, then do a cli login to your account (Ctrl-Alt-F1) or run "su - <your login>" from an xterm and run "mv .gnome2 .gnome2.save". This will remove all you old Gnome settings, and a fresh setup will be created when you log in as you. The drawback is that you lose all your settings. You can try and migrate them by hand from .gnome2.save. (I think I have the correct directory - working on my first cup of coffee.)
Mikkel
Edward DeMeulle writes:
Just recently noticed that after upgrading to FC7, X-windows starts and just sits there with an X cursor with just the FC wallpaper (I normally use/play through SSH). I'm not familiar enough with the connection between X and Gnome to know where to look next. Anyone have any suggestions as to how to proceed?
Boot into run level 3 or 4, then run 'yum update'. There are about 22GB worth of updates to Fedora 7, already. There is a known bug in esound that does that, fixed several months ago.
On 9/1/07 09:02, Sam Varshavchik wrote:
Boot into run level 3 or 4, then run 'yum update'. There are about 22GB worth of updates to Fedora 7, already. There is a known bug in esound that does that, fixed several months ago.
All I get when I run yum update is this: Loading "installonlyn" plugin Setting up Upgrade Process Error: Cannot open/read repomd.xml file for repository: updates
yum repolist: Loading "installonlyn" plugin repo id repo name status core Fedora Core 6 - i386 enabled extras Fedora Extras 6 - i386 enabled fedora Fedora 6 - i386 enabled updates Fedora 6 - i386 - Updates enabled
Apparently, the upgrade didn't revise the $releasever. Does anyone know where yum picks that up?
On Sunday 02 September 2007 01:48:17 am Edward DeMeulle wrote:
On 9/1/07 09:02, Sam Varshavchik wrote:
Boot into run level 3 or 4, then run 'yum update'. There are about 22GB worth of updates to Fedora 7, already. There is a known bug in esound that does that, fixed several months ago.
All I get when I run yum update is this: Loading "installonlyn" plugin Setting up Upgrade Process Error: Cannot open/read repomd.xml file for repository: updates
yum repolist: Loading "installonlyn" plugin repo id repo name status core Fedora Core 6 - i386 enabled extras Fedora Extras 6 - i386 enabled fedora Fedora 6 - i386 enabled updates Fedora 6 - i386 - Updates enabled
Apparently, the upgrade didn't revise the $releasever. Does anyone know where yum picks that up?
What says `rpm -q fedora-release ' ?
Anyway, you can install the fedora-release package version F7 with the following (please, note that is all a single command line):
rpm -Uvh ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/fedora-release-7-3.noarch.rpm ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/fedora-release-notes-7.0.0-1.noarch.rpm
best regards
Teo Fonrouge
On 9/2/07 03:51, Teo Fonrouge wrote:
On Sunday 02 September 2007 01:48:17 am Edward DeMeulle wrote:
On 9/1/07 09:02, Sam Varshavchik wrote:
Boot into run level 3 or 4, then run 'yum update'. There are about 22GB worth of updates to Fedora 7, already. There is a known bug in esound that does that, fixed several months ago.
All I get when I run yum update is this: Loading "installonlyn" plugin Setting up Upgrade Process Error: Cannot open/read repomd.xml file for repository: updates
yum repolist: Loading "installonlyn" plugin repo id repo name status core Fedora Core 6 - i386 enabled extras Fedora Extras 6 - i386 enabled fedora Fedora 6 - i386 enabled updates Fedora 6 - i386 - Updates enabled
Apparently, the upgrade didn't revise the $releasever. Does anyone know where yum picks that up?
What says `rpm -q fedora-release ' ?
Anyway, you can install the fedora-release package version F7 with the following (please, note that is all a single command line):
rpm -Uvh ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/fedora-release-7-3.noarch.rpm ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/fedora-release-notes-7.0.0-1.noarch.rpm
I tried both, results below: [root@troll ~]# rpm -q fedora-release fedora-release-6-4 fedora-release-7-3 [root@troll ~]# rpm -Uvh ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/fedora-release-7-3.noarch.rpm ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/fedora-release-notes-7.0.0-1.noarch.rpm Retrieving ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/fedora-release-7-3.noarch.rpm Retrieving ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/Fedora/fedora-release-notes-7.0.0-1.noarch.rpm Preparing... ########################################### [100%] package fedora-release-notes-7.0.0-1 is already installed package fedora-release-7-3 is already installed
Is is 'normal' for rpm to report two releases?
On Sunday 02 September 2007 10:40:36 am Edward DeMeulle wrote:
On 9/2/07 03:51, Teo Fonrouge wrote:
On Sunday 02 September 2007 01:48:17 am Edward DeMeulle wrote:
On 9/1/07 09:02, Sam Varshavchik wrote:
Boot into run level 3 or 4, then run 'yum update'. There are about 22GB worth of updates to Fedora 7, already. There is a known bug in esound that does that, fixed several months ago.
All I get when I run yum update is this: Loading "installonlyn" plugin Setting up Upgrade Process Error: Cannot open/read repomd.xml file for repository: updates
yum repolist: Loading "installonlyn" plugin repo id repo name status core Fedora Core 6 - i386 enabled extras Fedora Extras 6 - i386 enabled fedora Fedora 6 - i386 enabled updates Fedora 6 - i386 - Updates enabled
Apparently, the upgrade didn't revise the $releasever. Does anyone know where yum picks that up?
What says `rpm -q fedora-release ' ?
Anyway, you can install the fedora-release package version F7 with the following (please, note that is all a single command line):
rpm -Uvh ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/ os/Fedora/fedora-release-7-3.noarch.rpm ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/ os/Fedora/fedora-release-notes-7.0.0-1.noarch.rpm
I tried both, results below: [root@troll ~]# rpm -q fedora-release fedora-release-6-4 fedora-release-7-3 [root@troll ~]# rpm -Uvh ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os /Fedora/fedora-release-7-3.noarch.rpm ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os /Fedora/fedora-release-notes-7.0.0-1.noarch.rpm Retrieving ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os /Fedora/fedora-release-7-3.noarch.rpm Retrieving ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os /Fedora/fedora-release-notes-7.0.0-1.noarch.rpm Preparing... ########################################### [100%] package fedora-release-notes-7.0.0-1 is already installed package fedora-release-7-3 is already installed
Is is 'normal' for rpm to report two releases?
It depends on how you did the upgrade.
In fact, I have some FC6 boxes around that had been upgraded across all fedora releases since FC1, only by replacing the current 'fedora-release' package with the new release one.
In your case, you need to remove the fedora-release-6-4 package, after that send a 'yum clean all' and then a 'yum update kernel', then verify that you have the new kernel installed and dont' remove the old one for the momment.
best regards
Teo Fonrouge
On 9/2/07 10:52, Teo Fonrouge wrote:
It depends on how you did the upgrade.
In fact, I have some FC6 boxes around that had been upgraded across all fedora releases since FC1, only by replacing the current 'fedora-release' package with the new release one.
In your case, you need to remove the fedora-release-6-4 package, after that send a 'yum clean all' and then a 'yum update kernel', then verify that you have the new kernel installed and dont' remove the old one for the momment.
Thanks. I originally did the upgrade through the FC7 DVD. Removing the 6-4 release package seems to have passed the 'Cannot open/read repomd.xml' hurdle. Now I'm getting a "Error: No Package Matching glibc.i686" message. Trying 'yum update glibc-common' or 'yum install glibc-common' received the same error. I see some mention of the problem (for example: https://bugzilla.redhat.com/show_bug.cgi?id=228430) but no resolution was offered.
[root@troll home]# yum update glibc-common Loading "installonlyn" plugin Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package glibc-common.i386 0:2.6-4 set to be updated --> Processing Dependency: glibc-common = 2.6-3 for package: glibc Error: No Package Matching glibc.i686
[root@troll home]# yum update glibc.i686 Loading "installonlyn" plugin Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package glibc.i686 0:2.6-4 set to be updated --> Processing Dependency: glibc = 2.6-3 for package: glibc-devel --> Processing Dependency: glibc = 2.6-3 for package: glibc-headers --> Processing Dependency: glibc-common = 2.6-4 for package: glibc --> Restarting Dependency Resolution with new changes. --> Running transaction check ---> Package glibc-common.i386 0:2.6-4 set to be updated ---> Package glibc-devel.i386 0:2.6-4 set to be updated ---> Package glibc-headers.i386 0:2.6-4 set to be updated --> Processing Dependency: glibc-common = 2.5-10.fc6 for package: glibc Error: No Package Matching glibc.i686
[root@troll home]# rpm -q --queryformat "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" glibc glibc-2.5-10.fc6.i686 glibc-2.5-3.i686 glibc-2.6-3.i686
Edward DeMeulle writes:
[root@troll home]# rpm -q --queryformat "%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n" glibc glibc-2.5-10.fc6.i686 glibc-2.5-3.i686 glibc-2.6-3.i686
Your system is totally screwed up. You should never have different versions of glibc installed. rpm will not let you do it, left to its own devices. There was some serious breakage when you upgraded. You should look at what was saved in /root/upgrade.log.
You're not going to be able to press a single magic button, and fix this. You can begin by trying to remove both older versions of glibc via rpm. See if 'rpm -e glibc-2.5-10.fc6.i686 glibc-2.5-3.i686' runs without any errors. If so, then run 'rpm -V glibc' to see how badly screwed up is the most recent, remaining glibc.
But I suspect that glibc is not the only package that has multiple, conflicting, versions installed. Try running
rpm -q -a --queryformat '%{NAME}.%{ARCH}\n' | sort | uniq -c | sort -n
to see how many packages you've got that have multiple versions installed at the same time. You probably have hundreds of packages that need to be cleaned up by hand, before you have any hope of getting yum update to work. yum just doesn't know what to do when you have multiple versions of the same package, installed.
On 9/2/07 14:15, Sam Varshavchik wrote:
Your system is totally screwed up. You should never have different versions of glibc installed. rpm will not let you do it, left to its own devices. There was some serious breakage when you upgraded. You should look at what was saved in /root/upgrade.log.
You're not going to be able to press a single magic button, and fix this. You can begin by trying to remove both older versions of glibc via rpm. See if 'rpm -e glibc-2.5-10.fc6.i686 glibc-2.5-3.i686' runs without any errors. If so, then run 'rpm -V glibc' to see how badly screwed up is the most recent, remaining glibc.
But I suspect that glibc is not the only package that has multiple, conflicting, versions installed. Try running
rpm -q -a --queryformat '%{NAME}.%{ARCH}\n' | sort | uniq -c | sort -n
to see how many packages you've got that have multiple versions installed at the same time. You probably have hundreds of packages that need to be cleaned up by hand, before you have any hope of getting yum update to work. yum just doesn't know what to do when you have multiple versions of the same package, installed.
I was afraid someone was going to tell me something like that. There are a number of packages that are in duplicate and triplicate. I assume that if I get a dependency message, such as glibc = 2.5-10.fc6 is needed by (installed) glibc-headers-2.5-10.fc6.i386 glibc = 2.5-10.fc6 is needed by (installed) glibc-devel-2.5-10.fc6.i386 that I need to follow it through by checking for dup's on those packages and then removing and so on...
Just so I understand , are there any cases where multiple versions of the same package are acceptable?
Edward DeMeulle wrote:
I was afraid someone was going to tell me something like that. There are a number of packages that are in duplicate and triplicate. I assume that if I get a dependency message, such as glibc = 2.5-10.fc6 is needed by (installed) glibc-headers-2.5-10.fc6.i386 glibc = 2.5-10.fc6 is needed by (installed) glibc-devel-2.5-10.fc6.i386 that I need to follow it through by checking for dup's on those packages and then removing and so on...
Just so I understand , are there any cases where multiple versions of the same package are acceptable?
You might want to install the yum-utils package which contains a program called package-cleanup. It has an option called --problems which will tell you what programs are missing items or are wrong in other ways.
After you find out what packages have multiple versions outside kernel and gpg-key packages if you are running a 32-bit version, download the latest version of the rpm into a directory. Afterward, run rpm from that directory with the -Uvh --replacepkgs and --replacefiles options. This should replace any missing files and remove the remnants from the incompletely removed older package. If it is a kernel package, you would put them in a seperate directory and use -ivh instead of -Uvh
If you are running a 64-bit version there are both i386 and 64-bit versions of some packages that should have the same version I believe. I only have i386 so am not sure directly how same versions are setup.
Jim
-
Edward DeMeulle -
Jim Cornette -
Mikkel -
Sam Varshavchik -
Teo Fonrouge