Date: Mon, 29 Dec 2003 17:38:58 +0200 (EET) From: Kiril Kirov <kirov@math.bas.bg> To: Alexander Nedotsukov <bland@FreeBSD.org> Cc: kirov@math.bas.bg Subject: Re: ports/60683: nautilus2 i386_set_ldt problem Message-ID: <20031229170222.R10388-100000@humboldt.math.bas.bg> In-Reply-To: <200312291449.hBTEnZGC018857@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 29 Dec 2003, Alexander Nedotsukov wrote: > Synopsis: nautilus2 i386_set_ldt problem > > State-Changed-From-To: open->feedback > State-Changed-By: bland > State-Changed-When: Mon Dec 29 06:41:56 PST 2003 > State-Changed-Why: > The message you provided says me that there is a big chance you make use > of nvidia drivers. But this warning basicly should not affect nautilus. > Could you provide more details how it don't start. May be you have > core file or something? It's also interesting how do you start nautilus. > Is it part of gnome session startup or let's say you just built > x11-fm/nautilus2 and run it from xterm? > If you start nautilus from cli you may try do it under gdb(1) and try > to get backtrace in case it get crased. > > Thanks. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=60683 > Yes, I really use nvidia drivers (43.65). I built x11/gnome2 from ports tree under 5.1. When I updated to 5.2-RC I tried to start gnome-session and everything works fine except nautilus. It just crashes on start-up and pops-up the gnome bug reporting tool. After that I try to run it from the terminal but I get the same thing. I cvsuped ports tree, rebuild and reinstall it, but there was no change. Changing the user also makes no difference. I couldn't get much info from gdb, it just says: Program received signal SIGSEGV, Segmentation fault. 0x00000000 in ?? () No core dump at all.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031229170222.R10388-100000>