Kubuntu 7.04 and Oo2.2

[jack]

On Tue, 2007-06-26 at 15:52 -0400, NoOp wrote:
> On 06/26/2007 11:05 AM, jack wrote:
> > I know that I posted something on this before and didn't get it
> > resolved, but I've just loaded my laptop with Kubuntu 7.04 and Oo2.2
> > , and it's happening again.  I open a .doc file, and Oo immediately
> > crashes, then tells me that it will recover the file.  When I select
> > the file to recover, it just repeats the process, and cannot open
> ANY
> > .doc files.  This is strange because I sent a .doc file I was
> working
> > with to NoOp, and he was able to successfully open the file, but I
> > never could.
> >
> > Between evo crashing randomly, and Oo2.2 being rendered useless for
> > opening doc files, I'm beginning to wonder if I haven't jinxed all
> of
> > my installations of Kubuntu (it's the first time I've used KDE as
> > opposed to gnome, and the first time I've seen these problems)...
> >
> > Any input is appreciated, as always
> >
> 
> Not sure if I got it... sometimes my CRS gets the best of me :-) You
> can
> resend (glgxg at sbcglobal.net).
> 
> I've actually been able to recreate a similar situation in OOo
> (Official) while testing an https url bug
> (see: http://www.openoffice.org/issues/show_bug.cgi?id=77322).
> In that case if I copy and past an https url into a Writer document,
> 2.2.1 through OOo-dev2.3.0 crashes every time. If I recover the doc,
> it
> recovers it properly, then promptly crashes again. If it's only a
> single
> URL it crashes so fast that it appears that Writer isn't even opening.
>   The solution to 'that' situation is to not recover the document...
> not
> much of a solution, but afterwards it will no longer prompt to recover
> the doc.
> 
> You might try:
> <http://documentation.openoffice.org/HOW_TO/misc/Troubleshooting_guide.html>
> [Recovering content from a damaged OpenOffice.org file  7]
The file types that crash are M$ Word (.doc) files. 
> 
> The other thing that you might do if you plan to run kde is to clean
> out
> all of your gnome files. This works for me on my test machine when I
> want to test in kde, see:
> 
> http://www.psychocats.net/ubuntu/
>  http://www.psychocats.net/ubuntu/purekde <== these instructions
I only installed this as a kde environment.  The only gnome files that
have been installed would be those that were required (if any) during
the kde installation.
> 
> When I want to switch back to a clean gnome I use:
> http://www.psychocats.net/ubuntu/puregnome
> 
> *** Usual backup user data etc applies ***

running oowriter from the terminal produces this...
$ /usr/bin/oowriter ./Pre-Assessment\ Questionnaire.doc
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  145
  Minor opcode:  3
  Resource id:  0x0
Failed to open device

(process:13444): GLib-GObject-CRITICAL **: gtype.c:2242: initialization
assertion failed, use IA__g_type_init() prior to this function

(process:13444): Gdk-CRITICAL **: gdk_screen_get_font_options: assertion
`GDK_IS_SCREEN (screen)' failed

[the above 2 errors are repeated a number of times]

on selecting the file to recover, this is repeated, telling me that it
is just going through the process again.

I also disabled hunspell spell-checking, since there are already known
bugs with this.  But, it doesn't matter if i call oowriter with the
file, or open oowriter first (no file), and then attempt to open the
file from the <file><open> dialog.  The results are the same.

I need to use this for work - attempting to make a case for switching to
Ubuntu and Oo ... Any input is appreciated.