Post subject: OO hangs randomly on FreeBSD

[int32]

I need help with debugging OO-2.4.0 on FreeBSD-6.3-STABLE. I've upgraded from OO-2.2 because I've had OO constantly hanging at random; this bug is also in 2.3.1 and 2.4.0 The bug manifests itself completely at random, - the OO window stops responding either in the middle of text typing, or after trying to execute any command from the menu. Consequent starts prompt for document recovery, but then they also hang the application.

The only information I found is running truss (freebsd equivalent of linux strace) and getting this output:

kse_release({9.999999248}) = 0 (0x0)
kse_release({60.000000000}) = 0 (0x0)
kse_release({9.999996297}) = 0 (0x0)
kse_release({60.000000000}) = 0 (0x0)
kse_release({9.999995934}) = 0 (0x0)
kse_release({60.000000000}) = 0 (0x0)
kse_release({9.999995902}) = 383 (0x17f)

So apparently the program doesn't hang in a tight loop, but it doesn't draw itself and doesn't respond to other events.

How I can identify the problem so I can either submit it as a bug or try to find it myself?

Thanks

[kingfisher]

Do you get the same problem if you run OO as root or another user? ('root' is Linux-speak for administrator)

[int32]

Yes, exactly same behavior under root.

[kingfisher]

One thing that seems to be required for a bug report is repeatability. If you can put your finger on at least one sequence which repeatedly has the effect you describe, you would be ahead.

[int32]

There are sequences. For example, I was repeatedly trying to add a row in a table, and sometimes it hanged as soon as menu item was chosen, sometimes after the dialog with number of rows appeared, sometimes after the dialog clicked "ok" and disappeared, and sometimes row insertion succeeds, and it hangs only seconds after when I begin to type. Another sequence is after OO is hanged and killed, I start it again, and am asked for recovery. I hit "cancel" or "ok", doesn't matter, and then it hangs after the recovery dialog is disappeared.

[kingfisher]

FWIW, it seems to me that you have enough to file an issue. I would mention those sequences as examples. The first can be duplicated. If you think it would help, you could attach a document. Somewhere on this forum there is a guide to filing a bug report (aka issue).

[int32]

I filed the bug report, thanks... I just have very low hopes that it will be solved or even looked at, too little information, to few possibilities to debug the program. Thanks anyway.