I noticed the message below on the list, and have the same problem. I
manually restored parts of my .gconf directory, noting which things
cause the crash. It was a time consuming task, the biggest nuisance is
having to reboot after every crash. I have reduced it to:
~/.gconf/%gconf-tree.xml
~/
On Fri, Apr 28, 2006 at 02:08:06PM +0100, Chris Lale wrote:
> I dist-upgraded Etch (Testing) today. Attempting to open a Gnome session
> caused Gnome to abort and made other virtual terminals unusable (they
> all had a screen with a coloured pattern and no prompt or text). This
> was true for an
On Fri, 2006-04-28 at 14:08 +0100, Chris Lale wrote:
> I dist-upgraded Etch (Testing) today. Attempting to open a Gnome session
> caused Gnome to abort and made other virtual terminals unusable (they
> all had a screen with a coloured pattern and no prompt or text). This
> was true for any exist
I dist-upgraded Etch (Testing) today. Attempting to open a Gnome session
caused Gnome to abort and made other virtual terminals unusable (they
all had a screen with a coloured pattern and no prompt or text). This
was true for any existing user with a gnome configuration. Newly-created
users did
4 matches
Mail list logo