You have a mismatched set of packages, some depending on old X libraries and some on new X libraries, causing a conflict.
/usr/ports/infrastructure/bin/out-of-date should show you which need updates. On 2012-03-21, Alan Cheng <bsdp...@gmail.com> wrote: > below is what i got from startx log. it's better to have some error that i > can pass to google. > > will do my homework first, but wouldn't mind a few pointers if this looks > obvious to anyone. :-) > > thanks. > > [acheng@azalea ~]$ tail -f startx.out > > Thunar:/usr/X11R6/lib/libGL.so.12.0: /usr/X11R6/lib/libGL.so.10.0 : WARNING: > symbol(__glapi_noop_table) size mismatch, relink your program > Thunar:/usr/X11R6/lib/libGL.so.12.0: /usr/X11R6/lib/libGL.so.10.0 : WARNING: > symbol(__glapi_noop_table) size mismatch, relink your program > xfdesktop:/usr/X11R6/lib/libGL.so.12.0: /usr/X11R6/lib/libGL.so.10.0 : > WARNING: symbol(__glapi_noop_table) size mismatch, relink your program > xfdesktop:/usr/X11R6/lib/libGL.so.12.0: /usr/X11R6/lib/libGL.so.10.0 : > WARNING: symbol(__glapi_noop_table) size mismatch, relink your program > > (xfce4-settings-helper:9953): xfce4-settings-helper-WARNING **: Unknown mode > '1024x600 @ 0.0' for output default. > > > (xfce4-settings-helper:9953): xfce4-settings-helper-CRITICAL **: Stored > Xfconf properties disable all outputs, aborting. > xfdesktop[18998]: starting up > > (xfdesktop:18998): GLib-GObject-WARNING **: invalid (NULL) pointer instance > > (xfdesktop:18998): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion > `G_TYPE_CHECK_INSTANCE (instance)' failed > > > > > Juan Francisco Cantero Hurtado <i...@juanfra.info>g<eo< > >>On Tue, Mar 20, 2012 at 11:41:56PM +0800, Alan Cheng wrote: >>> Hello List, >>> >>> So I'm using a Loongson YeeLoong netbook. I installed XFCE4 without any >>> issues, But it will freeze after around 15 minutes, even if I do nothing on >>> it. Starting "terminal" will cause it to freeze immediately. >>> >>> I can still SSH into this netbook after freeze and everything else seems to >>> be fine. >>> >>> This happens back during 4.9 days. It's the same on 5.0 and current >>> snapshot. >>> >>> Any insight will be appreciated. and I'll be glad to provide any info >>> required to troubleshoot this. >>> >>> I'm not sure exactly what info will be needed, so I'll start with dmesg. >>> More will be provided as necessary: >> >>I can't help with your problem but if you run the window manager with >>"startx", the output of "startx" is always very useful. Run "startx" >>with this command: >>startx 1>startx-output.log 2>&1 >> >>Also, you can log in your loongson with ssh, execute "tail -f >>startx-output.log" and look the errors in real time when your wm is >>freeze. >> >>Cheers. >> >>-- >>Juan Francisco Cantero Hurtado http://juanfra.info
