Date: Mon, 23 Jan 2012 23:36:26 -0500 From: Eitan Adler <lists@eitanadler.com> To: Erich Dollansky <erichfreebsdlist@ovitrap.com> Cc: Piotr Kubaj <pkubaj@googlemail.com>, freebsd-x11@freebsd.org Subject: Re: Xorg doesn't start Message-ID: <CAF6rxgkgpQFSqP6W75nE-fxudZEZJK4ot9bBPOFk1DCEEY2uqA@mail.gmail.com> In-Reply-To: <201201241012.51299.erichfreebsdlist@ovitrap.com> References: <CABsLMBQQzuko73y2LpqYTg5nZ1CcMK6sK1shXPAAcQcbqD5J8w@mail.gmail.com> <1327370849.27126.5.camel@Nokia-N900> <1327372708.27126.14.camel@Nokia-N900> <201201241012.51299.erichfreebsdlist@ovitrap.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 23, 2012 at 10:12 PM, Erich Dollansky <erichfreebsdlist@ovitrap.com> wrote: > Hi, > > On Tuesday 24 January 2012 09:38:28 Piotr Kubaj wrote: >> 1. I did, but it doesn't help. >> 2. I compiled with hald and dbus and they are running. >> 3. It's not a configuration problem. It worked flawlessly for 2 months. It is possible that an upgrade broke X. Unfortunately I don't own every piece of hardware so I can't test every possible configuration. Does using portdowngrade help at all? Perhaps we could work from there to figure out exactly what went wrong. I'm sorry that your having problems with newer versions of X. > so, what changed? > > I have had several time the experience that a small upgrade broke X for me. It always could be fixed with some playing in rc.conf and xorg.conf. It would help if you could send send small "case studies" to the x11@ mailing list. I just upgraded foo but when I tweaked bar it fixed the problem. I'm not looking for user error stories but legitimate configuration required issues. -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgkgpQFSqP6W75nE-fxudZEZJK4ot9bBPOFk1DCEEY2uqA>