Cannot Logon to Gnome After Upgrade
I just finished using Synaptic to upgrade a bunch of Gnome stuff, anything that had an upgrade available. When I logged out of Gnome and tried to log back on, I got the following error message: Could not resolve the address "xml:readonly: /etc/opt/gnome/gconf/preconf/gconf.xml.defaults" in the configuration file "/etc/opt/gnome/gconf/2/path": Failed: Could not make directory '/etc/opt/gnome/gconf/preconf/gconf.xml.defaults': No such file or directory By playing around with various files and directories, I managed to get logged in to Gnome wherein Gnome showed desktop icons and menu trees but there was no background (except black) and no text. There were just short lines where text would normally appear. Since I'm way out my depth here, I put everything back to where it was before I started playing in the hopes that some kind soul could tell me a simple way out of this situation. Any help will be appreciated. Don Henson
On Sun, 2004-01-25 at 07:05, Donald Henson wrote:
I just finished using Synaptic to upgrade a bunch of Gnome stuff, anything that had an upgrade available. When I logged out of Gnome and tried to log back on, I got the following error message:
Could not resolve the address "xml:readonly: /etc/opt/gnome/gconf/preconf/gconf.xml.defaults" in the configuration file "/etc/opt/gnome/gconf/2/path": Failed: Could not make directory '/etc/opt/gnome/gconf/preconf/gconf.xml.defaults': No such file or directory
By playing around with various files and directories, I managed to get logged in to Gnome wherein Gnome showed desktop icons and menu trees but there was no background (except black) and no text. There were just short lines where text would normally appear. Since I'm way out my depth here, I put everything back to where it was before I started playing in the hopes that some kind soul could tell me a simple way out of this situation.
Any help will be appreciated.
Don Henson
Replying to my own post. I have continued to search for a solution for the above. I've found a couple of threads (using Google). I was able to discern two possible solutions, neither of which worked. One was to change the permissions on a directory. Did that. Didn't work. Another was to delete a couple of ior files in my home directory. Did that. Didn't work. It seems that no one knows what the problem is nor how to fix it. However, I cannot believe that this is a common problem. If it was common, I'd expect to see a lot of activity about it. But I see none, not even a response to my queries. So I must assume that the problem is unique to my system. Can anybody give me any assistance? I've pretty much exhausted my resources. If I can't fix it, then I'll be forced to go back to KDE. (KDE is okay. I just prefer Gnome.) Thanks for your consideration. Don Henson
Replying to my own post. I have continued to search for a solution for the above. I've found a couple of threads (using Google). I was able to discern two possible solutions, neither of which worked. One was to change the permissions on a directory. Did that. Didn't work. Another was to delete a couple of ior files in my home directory. Did that. Didn't work. It seems that no one knows what the problem is nor how to fix it. However, I cannot believe that this is a common problem. If it was common, I'd expect to see a lot of activity about it. But I see none, not even a response to my queries. So I must assume that the problem is unique to my system. Can anybody give me any assistance? I've pretty much exhausted my resources. If I can't fix it, then I'll be forced to go back to KDE. (KDE is okay. I just prefer Gnome.) Thanks for your consideration.
What directories/files did you delete???? Also have you tried to roll back to the default SuSE GNOME??? Marshall Heartley
On Sun, 2004-01-25 at 11:02, Marshall Heartley wrote:
Replying to my own post. I have continued to search for a solution for the above. I've found a couple of threads (using Google). I was able to discern two possible solutions, neither of which worked. One was to change the permissions on a directory. Did that. Didn't work. Another was to delete a couple of ior files in my home directory. Did that. Didn't work. It seems that no one knows what the problem is nor how to fix it. However, I cannot believe that this is a common problem. If it was common, I'd expect to see a lot of activity about it. But I see none, not even a response to my queries. So I must assume that the problem is unique to my system. Can anybody give me any assistance? I've pretty much exhausted my resources. If I can't fix it, then I'll be forced to go back to KDE. (KDE is okay. I just prefer Gnome.) Thanks for your consideration.
What directories/files did you delete???? Also have you tried to roll back to the default SuSE GNOME???
Marshall Heartley
I deleted ~/.gconf/%gconf-xml-backend.lock/ior and ~/.gconfd/lock/ior. Both files are back now even though I have not been successful in logging in to Gnome. I haven't yet tried rolling back mainly because I've spent a lot of time getting the Gnome desktop to look and work the way I like it. But that's my next step if I don't get any assistance here. Thanks for responding. Don Henson
<snip>
I deleted ~/.gconf/%gconf-xml-backend.lock/ior and ~/.gconfd/lock/ior. Both files are back now even though I have not been successful in logging in to Gnome.
I haven't yet tried rolling back mainly because I've spent a lot of time getting the Gnome desktop to look and work the way I like it. But that's my next step if I don't get any assistance here. Thanks for responding.
It seems like that something is hosed up here. You may want to move the .gconf and .gconfd directories to another directory and then try to log in again. I do not know if this will help but you can see. Let us know how it goes! Marshall Heartley
On Sun, 2004-01-25 at 13:46, Marshall Heartley wrote:
<snip>
I deleted ~/.gconf/%gconf-xml-backend.lock/ior and ~/.gconfd/lock/ior. Both files are back now even though I have not been successful in logging in to Gnome.
I haven't yet tried rolling back mainly because I've spent a lot of time getting the Gnome desktop to look and work the way I like it. But that's my next step if I don't get any assistance here. Thanks for responding.
It seems like that something is hosed up here. You may want to move the .gconf and .gconfd directories to another directory and then try to log in again.
I do not know if this will help but you can see.
Let us know how it goes!
Marshall Heartley
I used YaST, from KDE, to delete gconf and gconf2. Then I used YaSt again to reinstall them. I can now log in and I can read the labels on the desktop icons. I haven't checked everything yet but so far it seems as though everything is working with the exception of themes. I don't seem to be able to change them. But that's a really minor problem compared to what I had before. Don Henson
<snip>
I used YaST, from KDE, to delete gconf and gconf2. Then I used YaSt again to reinstall them. I can now log in and I can read the labels on the desktop icons. I haven't checked everything yet but so far it seems as though everything is working with the exception of themes. I don't seem to be able to change them. But that's a really minor problem compared to what I had before.
I was meaning for you to either move or delete the 2 folders in your home directory. But if your solution allowed you to log in, then I guess that was another way of doing things :) Marshall Heartley
On 01/26/2004 01:40 AM, Donald Henson wrote:
On Sun, 2004-01-25 at 07:05, Donald Henson wrote:
I just finished using Synaptic to upgrade a bunch of Gnome stuff, anything that had an upgrade available. When I logged out of Gnome and tried to log back on, I got the following error message:
So I must assume that the problem is unique to my system. Can anybody give me any assistance? I've pretty much exhausted my resources. If I can't fix it, then I'll be forced to go back to KDE. (KDE is okay. I just prefer Gnome.) Thanks for your consideration.
Did you run ldconfig AND SuSEconfig after the update. This needs to be done after closing Synaptic, since it locks the rpm database. You could do it from the console. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
On Sun, 2004-01-25 at 17:10, Joe Morris (NTM) wrote:
On 01/26/2004 01:40 AM, Donald Henson wrote:
On Sun, 2004-01-25 at 07:05, Donald Henson wrote:
I just finished using Synaptic to upgrade a bunch of Gnome stuff, anything that had an upgrade available. When I logged out of Gnome and tried to log back on, I got the following error message:
So I must assume that the problem is unique to my system. Can anybody give me any assistance? I've pretty much exhausted my resources. If I can't fix it, then I'll be forced to go back to KDE. (KDE is okay. I just prefer Gnome.) Thanks for your consideration.
Did you run ldconfig AND SuSEconfig after the update. This needs to be done after closing Synaptic, since it locks the rpm database. You could do it from the console.
-- Joe Morris
No. In fact I got myself in such deep trouble that I couldn't log into either gui. I eventually reinstalled everything from scratch. But thanks for the suggestion anyway. Don Henson
Donald Henson wrote:
I just finished using Synaptic to upgrade a bunch of Gnome stuff, anything that had an upgrade available. When I logged out of Gnome and tried to log back on, I got the following error message:
Could not resolve the address "xml:readonly: /etc/opt/gnome/gconf/preconf/gconf.xml.defaults" in the configuration file "/etc/opt/gnome/gconf/2/path": Failed: Could not make directory '/etc/opt/gnome/gconf/preconf/gconf.xml.defaults': No such file or directory
[snip] Refers to a missing file /etc/opt/gnome/gconf/preconf/gconf.xml.defaults? When I had the same problem a while ago, I just created a blank file called gconf.xml.defaults where gnome complained it couldn't find it and since then things have been working OK. Fish
participants (5)
-
Donald D Henson -
Donald Henson
-
Joe Morris (NTM) -
Mark Crean -
Marshall Heartley