Can't start X, I am having a read-only filesystem problem.

[Howard Coles Jr.]

On Wednesday 17 January 2007 3:53 pm, OOzy Pal wrote:
> On 1/18/07, OOzy Pal <oozypal at gmail.com> wrote:
> > On 1/18/07, Chris Miller <lordsauronthegreat at gmail.com> wrote:
> > > On 1/17/07, OOzy Pal <oozypal at gmail.com> wrote:
> > > > I Can't start X, I am having a read-only filesystem problem.
> > >
> > > Try "startx."  What have you already tried to fix the problem?
> > >
> > > --
> > > ==  ==  ==  Ƒ 5 |) 3 |/  ==  ==  ==
> > > ==    ( 0 |) 3    \|/ 4 |2 |2 | 0 |2    ==
> > > ==  ==  7 | |\| µ Ж    6 µ |2 µ  ==  ==
> > > --
> > > kubuntu-users mailing list
> > > kubuntu-users at lists.ubuntu.com
> > > Modify settings or unsubscribe at:
> > > https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
> >
> > I tried startx and no help. I get
> > XIO fatal IO error 104 (Connection reset by peer) on X server ":0.0"
> > after 0 requests (0 known processed) with 0 events remaining
> >
> >
> > --
> > OOzy
> > Kubuntu-Edgy
>
> I tried dpkg --configure -a
>
> I did setting ups then I tried startx, I got same error
>
> XIO fatal IO error 104 (Connection reset by peer) on X server ":0.0"
> after 0 requests (0 known processed) with 0 events remaining
>
> plus
>
> xauth: error in locking authority file /home/hab/.Xauthority
> OOzy
> Kubuntu-Edgy

1.  Reboot into recovery mode (this sets the file systems to be checked for 
real when you reboot again) and see if you can edit the xorg.conf.
2.  Try to delete the /home/hab/.Xauthority file or rename it.
3.  Reboot normally, let the filesystem check finish and see if you can access 
the various file spaces, and watch for what gets written to the /var/log/ 
Xorg.0.log; kdm.log and dmesg if X will not start.

-- 
See Ya'
Howard Coles Jr.
John 3:16!