Date: Sat, 19 Mar 2011 12:33:35 +1100 From: Alexander Cox <alexander.j.cox@gmail.com> To: gua.chunglim@gmail.com Cc: freebsd-x11@freebsd.org Subject: Re: FBSD 8.2R can't startx Message-ID: <4D8407EF.7070604@gmail.com> In-Reply-To: <20110318154101.GA1847@gmail.com> References: <20110317134728.GA1417@gmail.com> <20110318064011.GA69484@server.vk2pj.dyndns.org> <20110318154101.GA1847@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/19/11 02:41, Gua Chung Lim wrote: > [...] > >> Have you tried reverting to the default xinitrc (starting twm and >> a couple of xterms)? This will help distinguish between a problem >> with Xorg and a problem with KDE. >> > Hmm I'm sorry, I don't know twm. > I do not understand the default .xinitrc. I created it by myself. > I only know without .xinitrc being created, startx gave 3 xterms. > But I believe that the problem should be xorg because > both KDE and GNOME cannot start with the same symptom. > > If startx gave three xterms, with no .xinitrc, you were probably seeing twm (X's default wm). This means that the problem may not be xorg. If you delete .xinitrc you should be greeted with these xterms again and be able to move them etc. You can try to delete your xorg.conf, that often gets me into a DE. Due to HAL and the new versions of xorg trying to make config files useless, an xorg.conf can sometimes stop xorg from running. I have not had an xorg.conf in about two years. It sounds (and is) silly, but might work. Make sure to backup your xorg.conf just in case. --Alexander Cox
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D8407EF.7070604>