I'm asking this here is so that if it is a known problem
with -current, I'll have no need to investigate further, and i can just
wait until it's fixed.
If it is not a known problem, then I shall report my findings to the
relevant parties.
Cliff Rowley
- while (!asleep) { code(); }
ode 1
Gdk-ERROR **: BadShmSeg (invalid shared segment parameter)
serial 85 error_code 151 request_code 142 minor_code 5
Reckon this is due to a work in progress on the SYSV* section of the
kernel? Anyone know if that is being worked on right now?
Cliff Rowley
- while (!asleep) { code(); }
> Do you have any plans to make XFree86-devel port of it? This let us to test
> it and refine before XF-4.0 will be released.
I had no plans, personally, but then I'm not a ports
maintainer. Compiling the snapshot is pretty simple anyway.
Cliff Rowley
- while (!asleep) { code
eliable. Aside from a few teething problems with -current (which is to
be expected). If you're waiting for it's official release, you will be
pleasantly suprised :)
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
st not using a pre 4.0 XFree86 snapshot could help us out
here?
Of course, it could just be (and most likely is) just being triggered by a
change in FreeBSD 4.0, which the XFree86 code (obviously) hasnt caught up
on yet.
It's not urgent, there are no critical errors produced by this situati
> More likely work in progress with broken gtk desktop voodoo.
Dont you think that would be bit of a cooincidence? Since the messages
are almost identical in nature to the ones I've been getting from other
programs *not* gtk/gdk based ;) The link between them so far is shared
memory...
To Un
the
shared memory in 1 swoop. Then we'd be able to shut down XFree86 (and
obviously any other apps using shared memory), and get on with life :)
(anyone listening?)
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> options SHMMAXPGS=4096
> options SHMALL=16384
> options SHMSEG=16
> options SEMMNI=32
> options SEMMNS=128
Tried those, same error :(
_XF86BigfontQueryFont: could not attach shm segment
Cliff Rowley
- while (!asleep) { code(); }
> Try increasing SHMSEG to 128.
Appears to be working fine with SHMAXPGS=4097 and SHMSEG=128 - fingers
crossed ;) Thanks for your help everyone...
Cliff Rowley
- while (!asleep) { code(); }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in th
