after install of OO 1.0.1, the same issue remains. I have installed OO
on several other Windows machines (W2K, XP, 98SE) and could not
reproduice the problem there.....

Ralf, thanks for taking the time to update this issue.

Could it be a video driver issue?

I take it there are no error logs generated.


Thanks for using and supporting OOo.

I was unable to recreate this defect in my windows 98
open office 1.0.1 system.
            Raj Narasimmon 9/11/02

Sorry for getting back tp you so late, but i was working out of town...

I was able to 
reproduce the problem on two systems, both with Windows ME and as i check now, both with 
SiS620 video chip onboard. On other systems, i don't get this problem either. 

As 
both machine have the video chip in common, and i have verified that they use both the 
latest video driver available, i must assume at this point that it might be a driver 
issue, which only seem to show up when the fonts get rendered in the dropdown menu. 
Other software (O2K, AbiWord, etc) do not have the same problem, neither does any font 
viewing/installing program...

Changing the owner and component to who I think this issue should go 
to.

User can reproduce on machine with

SiS620 video chip onboard
Windows ME

I am also experiencing this problem, only in Draw instead of writer.  
the specifics of my machine are:
   Win 98 SE
   224 MB RAM
   453 Fonts installed (mostly True Type, a couple screen fonts)
   "Free" version of Adobe Type Manager installed
   NVIDIA RIVA TNT (Gateway) video card
   Screen resolution 1280x1024
   

us->tm:
SiS620 driver issue?
Do you have such a graphic chip/adapter available for testing?

TM->US: As discussed, I set you as owner, thanks !

Hard to judge from remote, especially as I do not have access to a
SiS620 graphic adaptor nor an Nvidia Riva TNT.
But it is *very* likely that a corrupt font causes the crash.
Try to isolate the corrupt font(s). There is no other way to find the
cause than you isolate the font.
Using the font drop-down list box until it crashes should be feasible
(as the fonts are listed alphabetically).

BTW. other apps don't crash as they do not use the font itself to
display its name.

us->Bitbeisser@openoffice.org: reassign back to me when you have
isolated and attached the font(s) to this bug. Good luck.

It was at least in my case for sure not a corrupt font. I had a shareware 
fontviewer/manager installed on my office machine, where the problem first 
occurred and it did not have a problem to show a sample of the font. I am very confident 
that the issue was related to the video driver and the use of certain functions, as i 
experienced crashes  in the video driver in Mozilla and Opera as well, while IE and 
Word/WordPerfect were just working fine.
Unfortunatley, i do not have access to 
that machine or any other SiS620 driven ones right now, as the two machines where i 
could reproduce it have been upgraded/replaced by now. I am more than happy to make 
some tests as soon as i get my hands on such a machine again...
Ralf

Seems to be rather a buggy video driver than an OOo issue.
Try to disable "Optimized output" in Tools/Options/OpenOffice.org/View.

Same problem with OOo 1.0.2 on Debian Linux (current unstable).

Using Gnome desktop, mouse input is no longer possible until
soffice.bin is killed from terminal.

Video card is NVIDIA RIVA TNT.

Disabling "Optimized output" or OpenGL did'nt help.

If you need more info, feel free to contact me.

I also had this problem. (Gentoo Linux, kernel 2.4.20-gentoo-r2,
nVidia GEForce 2)

I removed the RenderAccell option from the video driver section of
XF86Config, and the problem is now gone.

I do not, however, think it was related to a specific font, but rather
to the selection combo box.  I experienced the lock-up in two
circumstances:

1. Using the scroll bar on the combo box and *then* moving the mouse
over a font (any font.)  A blue bar appeared over the font name
(probably an incomplete selection highlight) and then the system
locked.  I never experienced problems selecting fonts without using
the scroll bar on the combo box.

2. Using the mouse scroll wheel inside the combo box.  Same selection
highlight issue.

Since disabling hardware acceleration works around this problem
for Linux, maybe it will for Windows, too.  Anyone having this
problem in Windows, please try cranking "hardware accelleration"
down to the minimum.  See
http://www.ati.com/support/faq/winme/winmeconfigadjusthardwareaccelslider.html
In WinME, right-click on My Computer, pickthe SYSTEM PROPERTIES panel
click the PERFORMANCE tab and then click the GRAPHICS button.
Then set Hardware Acceleration to None.  Let us know whether this helps.

I'm going to resolve this assuming it's a system driver problem,
but you can still add comments to this issue.

Thanks!

SBA: No reaction for more than 3 months => Closed.
Feel free to reopen this one if there is further findings.