Red Hat Bugzilla – Bug 209689
oobase fails to start
Last modified: 2007-11-30 17:11:45 EST
Description of problem: oobase fails to start Version-Release number of selected component (if applicable): openoffice.org-base-2.0.2-5.19.2 How reproducible: Very Steps to Reproduce: 1. start term 2. type oobase 3. Actual results: The program 'soffice.bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 83 error_code 1 request_code 145 minor_code 1) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Expected results: oobase should start Additional info:
That's fairly unusual, there's no other reports of this, and FC-5 has been released for quite some time. Without any other information I would suspect that something else has changed, not OOo itself. Any idea if anything else possibly relevent has changed on your box recently ?
The only recent change was to install oobase using yum.
it works here (tm), which I know isn't particularly useful for you :-), so let's see if we can narrow it down to make it reproducable for me... a) KDE or GNOME ? b) does just oobase fail, i.e. are oowriter and oocalc ok ? c) do you have a different java installed, i.e. not using gij/gcj ?, e.g. launch a non-crashing OOo component, e.g. writer and what is listed under tools->options->openoffice.org->java ? d) what's your display depth, i.e. output of... xdpyinfo | grep "depth of root window"
a) Gnome b) Only oobase c) Free software Foundation 1.4.2 d) depth of root window: 24 planes
exactly the same as me here :-( I assume it's not an x86_64 box as the arch is i686 so there's can't be anything unusual there. Maybe the video driver, what does "grep drivers /var/log/Xorg.0.log" say ?
just not able to reproduce this :-(