OpenOffice freezes/crashes with bad gtk-theme - various symptoms see dupes

[SqUe]

Binary package hint: openoffice.org

Open any openoffice program, spreadsheet, word processor. No need to load a file, the effect remains the same.
Just visit File->Print... It will freeze, and I have to manual kill the process.

[SqUe (sque)]

This bug still exists today (26/09/07) full updated gutsy tribe 5 with OpenOffice 2.3.0 RC1. No custom configuration, no custom build, the one that ships with ubuntu installation. Do I need to post any log? Or this is known bug?

[SqUe (sque)]

This is a dump of open office while selecting print... and freezed!

[Rolf Leggewie (r0lf)]

I am experiencing the same problem on gutsy. Please find the console output at http://launchpadlibrarian.net/9585086/ooo-crash.txt. There is no file being created in /var/crash. The button "Print file directly" works fine.

[SqUe (sque)]

This is the worst bug report I have ever done. Even the dump of ooffice that I attached is incomplete. Sorry but I was too tired every time I checked this page and write something.:S Thanks Rolf for confirming and providing more accurate info, I think its should be fixed before release! :)

[Rolf Leggewie (r0lf)]

Many other menu entries also crash OOO.org

[Andy J. (andy-england1985)]

Open Office 2.3 freezes on Gutsy Beta whenever I go to Options, or open any dialogue. I think it's much the same thing as going to File > Print. OO 2.3 is completely unusable at present. Opening any document makes OO crash instantly.

[Debian God!! (debianlife)]

Yup even am facing the same problem as Andy. Sadly I don have m$ office also at my disposal :(

All my work is held up :((((((

Can't open any option box and highly unstable under gutsy beta

[Arthur Mensch (arthurmensch)]

It seems to be a openoffice.org-gtk problem since it works with openoffice.org-kde. I hope it can help you, it is really annoying.

[Debian God!! (debianlife)]

But I don't fancy kde. I feel in one corner of mind am very close to BSOD if I use kde environment (no offense meant to anyone its just my feeling).

Btw the problem has vanished since the last time I updated my gutsy. Now open office is working without flaw though I have not used it much after the update!!!

[Debian God!! (debianlife)]

Update your gutsy, the problem will be solved. Its working fine now for me.

[SqUe (sque)]

The specific file->print... crash still exists!

[SqUe (sque)]

Please don't close this bug again, unless at least one more confirms this is fixed or a developer believes it is/will be. The options menu is indeed working and everything else as I fast checked. But the File->print... crash still exists at least for me.(this is the title of this bug!)

[Fireaway (d-fireaway)]

The "Quick Print" button works fine (Ubuntu Gutsy Italian last updated today, with openoffice.org-core 1:2.3.0-1ubuntu2). The "Print..." dialog under the "File..." menu freezes OOo. I'm still affected from this bug

[Gert Kulyk (gkulyk)]

Are you using a non-ubuntu gtk-theme (e.g. from gnome-look.org)? If so, please switch your theme to a pre-packaged one (e.g. human or clearlooks). There is a known issue with broken gtk-themes in combination with openoffice.org (I forgot the bug number).

[SqUe (sque)]

W00t! You are right! I changed to default theme and now works just fine even power point and firefox 3(which also crashed on many pages). Everyone having this problem please change to default gtk-themes. As this solution is just a workaround I don't think it should be closed yet.

[CheeseGardener (theautonomist)]

There is one place the crash does NOT exist. You can still print from going to print preview, and then go to "print file directly".

[Mephisto (ferrylandzaat)]

I'm also having prolems with this. But switching theme is not a fix to this issue, it's a workaround, and a lame one at that. I don't *want* to switch theme, cause i like my current one, and it was working fine on feisty with OOo 2.2. Telling people to use the default theme is the microsoft way: "we didnt make that, so we dont support it, and you better not use it". Also, it seems to be OOo having a problem with the pixmap engine. There's quite a lot of themes out there using that...
Oh well, ill just uninstall the openoffice.org-gtk package for now and wait for a fix. I rather have only ugly OOo windows than ugly windows on all apps.

[Michael B. Trausch (mtrausch)]

Interesting. I was just commenting on how asinine the "change your theme" fix is in bug 154224, which I reported and is a dup of this one. It's not right: when did we go from expecting people to code defensively to expecting users to take the brunt of a developer's inability to defensively program? OpenOffice.org should be failing gracefully when something isn't as it expects it to be. While this looks *really* bad for the Ubuntu people and the Gutsy release, it's reflects even worse on Sun Microsystems and the OpenOffice.org community, who shouldn't let something this horrible see the light of day in the first place.

[Hagar (hagar-am)]

I can confirm that bug. Thx for workaround. I`m looking forward to see that fixed:D

[hamayoun (hamayoun-khan)]

Hi

I ran into this bug as well. Man, I'm glad I saw this thread or I would never have figured out the workround! BTW, I was using the 'Crux' theme which I thought is one of the pre-packaged themes, and it still crashed. Works fine with 'Clearlooks'.

[Cedric Brancourt Simple System (cedric-brancourt)]

The same here, using Ghrome look. Got some "bad pointer" error while using "print..." and lots of menu features. OpenOffice.org really need to be fixed nor the sub-libs related to this problem.
Best regards

[Alfredo Gemma (alfredo-gemma)]

Bug Confirmed: OpenOffice 2.3.0. There is no evidence that switching to standard themes is a workaround (in many clients affected by this bug It does not solve the problem). The only workaround, in case you have multiple printers defined, is setting the default printer and then print directly.

[Alfredo Gemma (alfredo-gemma)]

This is a correction of my previous post.
Further analysis seems to demonstrate that the problem is related to the type of "Controls" used by the theme.
On every client affected by this problem, just changing the controls of the current theme with one of the default types include in Ubuntu, solved the problem.