Date: Sun, 22 Jun 2008 15:49:33 -0700 From: "Kurt Buff" <kurt.buff@gmail.com> To: "Matthew Donovan" <kitche@kitchetech.com> Cc: questions@freebsd.org Subject: Re: xfce on amd64 not working Message-ID: <a9f4a3860806221549m61b9b673y9b5ed19f40c5772d@mail.gmail.com> In-Reply-To: <20080622223143.GA3871@njord.Belkin> References: <a9f4a3860806221448g18b14e43y708251572e5a19c8@mail.gmail.com> <20080622223143.GA3871@njord.Belkin>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_18863_28930032.1214174973601 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Sun, Jun 22, 2008 at 3:31 PM, Matthew Donovan <kitche@kitchetech.com> wrote: > On Sun, Jun 22, 2008 at 02:48:45PM -0700, Kurt Buff wrote: >> All, >> >> My (relatively) newly purchased Thinkpad T61 (type 7658-CTO) with 4g >> RAM is running 7.0-STABLE amd64 from June 8. >> >> I've gotten Xorg running from a generic xorg.conf generated by 'Xorg >> -configure', with startx, but when starting XFCE4 with xtartxfce, it >> is not happy, and bombs out, leaving a message in /var/log/messages: >> >> kernel: PID 92xxx (xfwn), uid 0: exited on signal 11 (core dumped) >> >> I've csup'ed today, and did 'portupgrade -aRr' to get the latest. >> >> I also tried copying the xorg.conf from the Suse install that I'm dual >> booting with, but that's not any help. >> >> >> Any thoughts? >> >> Kurt > > Well it's not an Xorg problem. consoidering it's xfwn that is being dumped. > It'd be easier if we could see the core that xfwn actually dumped since > that leads to a bit more clues on why it cored. Happy to provide it, but I don't have a web site to which I can post it. gzipped, it's about 120k. I'll attach it, and hope it gets through. Kurt ------=_Part_18863_28930032.1214174973601--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a9f4a3860806221549m61b9b673y9b5ed19f40c5772d>