On Mon, 2004-02-23 at 20:33, Peter Luciak wrote: > Nope, nothing. There are no TT fonts loaded
'loaded'? How did you see that? Please try to provide logs of what you are doing and seeing on the screen in addition to (or instead of) summarising in your own words; it helps me understand what exactly you have done, and the responses you received. > , and the bug occurs > with the "nv" driver as well (module nvidia was rmmod'ed before). The same > segfault. OK. > To make this clear, OOo segfaults only in the latest version. I've > never had any problems with it before (I use it ca. 1 year, with nvidia > drivers, different kernels, Debian unstable). Yes, I had noticed you said that; the problem is, nothing actually changed in setup in recent versions so something else must have changed to trigger the (probably already existing) bug. The question is.. what. People have occasionly reported segfaults in setup but they are usually related to fonts or video drivers. Is there anything created under ~/.openoffice before the segfault? If so you might find setup.log - if so please post it since it may provide a clue to which stage the segfault occured. Does the same segfault happen if you run /usr/lib/openoffice/setup directly? It's a little strange that you got so little information from the gdb backtrace, too. I see from the gdb output you posted (thanks :) that you used a corefile. Sometimes I find I get better results by letting the crash happen under gdb instead of using a corefile: cd /usr/lib/openoffice/program; LD_LIBRARY_PATH=/usr/lib/openoffice/program gdb ./setup.bin Then type 'run' at the (gdb) prompt, wait for the crash and enter 'thread apply all bt full' at the next prompt. Chris
