Very Computer

I did some search on sunsolve (xclock and supply cutoff date 6 months) and
it seems there are a couple of bugs related to it (or that sound similar):

    xclock -d will not run in 8-bit mode
    Bug Reports: 4907802

    ST font scaling not working
    Bug Reports: 4892613

    Xst crashes Xsun
    Bug Reports: 4909153

    xserver crashes on exit of xst applications
    Bug Reports: 4913502

    xclock crashs with the "-d" option
    Bug Reports: 4917843

but these were supposed to be fixed in s10_b42 ...

Bye, Dragan

--
Dragan Cvetkovic,

To be or not to be is true. G. Boole      No it isn't.  L. E. J. Brouwer

!!! Sender/From address is bogus. Use reply-to one !!!

|I have installed s10_b46 on my Dell Optiplex GX150 a few days ago
|(yesterday, actually) and I have noticed a bizzare problem with it: in X
|windows environment (OW with fvwm2 from SFWfvwm), if I start 'xclock -d' my
|X freezes and I have to do init 0, init 5 or init 6 to get it back. The
|machine is OK now (network connection works), but init 1, init 2 or init 3
|don't change mode (or at least doesn't announces that it changes mode, init
|1 hungs).

I don't know why it would hang (well, it will hang the xserver for a
couple of minutes if you have lots of fonts - that's fixed in s10_49),
but you can disable the new font code being used in xclock -digital.

See my previous message at:
http://groups.yahoo.com/group/solarisx86/message/913

--
________________________________________________________________________


  Working for, but definitely not speaking for, Sun Microsystems, Inc.

[snip]

Quote:> I don't know why it would hang (well, it will hang the xserver for a
> couple of minutes if you have lots of fonts - that's fixed in s10_49),
> but you can disable the new font code being used in xclock -digital.

> See my previous message at:
> http://www.veryComputer.com/

Thanks Dave and Alan. Dave, it's -xrm '*useXst: False' i.e. '*' is needed
(otherwise it will keep*).

Btw, I have been waiting for X to come back for some 15 minutes to see if
it would come back, but after that I had to reboot (using reboot command,
not using e.g. init 6, since the later wouldn't do anything).

OK, I think I'll stay away from xclock -d for a while :-)

Fixed in s10_49? So two more months of waiting? Or are you going to skip a
release?

Bye, Dragan

--
Dragan Cvetkovic,

To be or not to be is true. G. Boole      No it isn't.  L. E. J. Brouwer

!!! Sender/From address is bogus. Use reply-to one !!!