[gobolinux-users] xorg 7.3 macbook freeze

[Michael Homer]

On 10/11/07, Jonas Karlsson <jonka750 at student.liu.se> wrote:
> On Tue, 09 Oct 2007 15:45:03 +0200, Isaac Dupree <isaacdupree at charter.net> wrote:
>
> > Carlo Calica wrote:
> >> The log right after the freeze would be most useful.
> >
> > I wonder... that might be difficult if I can't get the system to sync
> > writes to disk before force-shutting-down (maybe I should look into
> > enabling/learning that linux-kernel SysRq key...).. Do you know if this
> > is a concern or if there are other ways to deal with it?
> >
> >
> > Anyway I'll try stuff with 7.3 again when I have time
> >
> Having experimented some more with Xorg I can more or less confirm that
> it's a DBus issue. It looks like the issue is gone with DBus 1.1.x, so if
> you're running DBus 1.0.x or earlier you can try to upgrade it and see if
> that solves it, without having to recompile Xorg.
I have the same issue, with DBus 1.1.2 and Xorg 7.3-r4, which was
built after that DBus, as was KDE-Base (i.e. kdm). The end of kdm.log
is:
process 3526: arguments to dbus_connection_send_with_reply_and_block()
were incorrect, assertion "(error) == NULL || !dbus_error_is_set
((error))" failed in file dbus-connection.c line 3254.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace

Starting X with WindowMaker or twm from the console works, but the
same freeze occurs when you exit it by any means (ctrl-alt-backspace
or choosing exit from the menu). Ctrl-Alt-F1 & Ctrl-C doesn't have the
same effect, though. When I do that, I get this in Xorg.0.log:
Backtrace:
0: X(xf86SigHandler+0x9c) [0x80c565c]
1: /System/Links/Libraries/libc.so.6(__libc_start_main+0xd8) [0xb7c777c8]
2: X(FontFileCompleteXLFD+0xb5) [0x806ded1]

Fatal server error:
Caught signal 11.  Server aborting

I'm not sure what that means, though. It doesn't appear when it's
started from kdm.
-Michael