Issue 80539 - bad gtk initialization causes hang on glib 2.13.x gtk 2.11.x
Summary: bad gtk initialization causes hang on glib 2.13.x gtk 2.11.x
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 680m224
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Olaf Felka
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-09 17:56 UTC by ccheney
Modified: 2007-08-12 16:58 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description ccheney 2007-08-09 17:56:30 UTC 
Apparently OpenOffice doesn't initialize glib/gtk properly, in the past this has
just caused error messages to be printed to console. However, now due to changes
in glib 2.13.x and gtk 2.11.x improper initialization of GTK causes OpenOffice
to not start at all. It just hangs at the splash screen. This will affect many
users in the near future when people upgrade to Gnome 2.20.

https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/127944
http://bugzilla.gnome.org/show_bug.cgi?id=463773
https://bugzilla.novell.com/show_bug.cgi?id=294385
Comment 1 ccheney 2007-08-09 18:10:29 UTC 
I should add that this affects both OpenOffice 2.2.1 as well as src680m224
(2.3.x). I haven't tested it on older versions than that.
Comment 2 ccheney 2007-08-09 18:14:41 UTC 
Also, note that the novell bug in the initial report is actually about KDE's
Konqueror nspluginviewer, but it is affected by the same bug so the comments may
be informative to someone looking into this bug for OpenOffice.
Comment 3 Olaf Felka 2007-08-09 18:47:09 UTC 
@ pl:Please have a look.
Comment 4 ccheney 2007-08-09 20:31:21 UTC 
I believe that the change that caused the OOo hang was between glib 2.13.6 and
2.13.7
Comment 5 ccheney 2007-08-09 20:39:45 UTC 
In Ubuntu GTK was updated from 2.11.5 to 2.11.6 on the same day as the glib
update so it actually could be either or both of the libraries that had updates
that exposed the issue.
Comment 6 philipp.lohmann 2007-08-10 12:44:48 UTC 
If OOo hangs in some function called X11SalGraphics::GetFontHints, then this is
somewhere in code that some distribution added as OOo does not contain that
method on its X11SalGraphics. Looks to me like this is an ubuntu/Novell problem
since they added  code they did not QA.
Comment 7 philipp.lohmann 2007-08-10 12:46:03 UTC 
pl->of: if you can reproduce this problem with a real OOo and one of the
described gtk versions, then please send this back to me. else close it.
Comment 8 rene 2007-08-10 12:51:00 UTC 
note that I am not the author of the patch, but Novell isn't either:

rene@mini:~/tmp/openoffice.org-2.3.0/ooo-build/patches/src680$ grep -r
X11SalGraphics::GetFontHints *
ooo64508.vcl.honourfontconfighinting.diff:+void X11SalGraphics::GetFontHints(
const ImplFontAttributes& rFontAttributes, int nSize, ImplFontHints& rFontHints)
const

So it happens with the patch for 64508.

Cc'ing cmc.

[ oh, and btw, probably QA was done but it broke only a new, changed glib ]
Comment 9 caolanm 2007-08-10 12:56:05 UTC 
I've no hang with glib2-2.14.0 FWIW
Comment 10 ccheney 2007-08-11 04:15:56 UTC 
Yes the bug actually is ooo-build sorry about reporting it here. 

The patch at fault appears to be:

patches/src680/ooo64508.vcl.honourfontconfighinting.diff

which was a patch to fix openoffice bug 64508, apparently it isn't quite good
enough to work with newer glib/gtk. I had someone else test with glib 2.14.0,
since someone here claimed it worked fine with it, and apparently the new glib
is not enough by itself to fix the problem. I sent an email to the go-oo dev
list to see if someone with more glib/gtk experience can correct the issue with
the patch.

Thanks,

Chris
Comment 11 Olaf Felka 2007-08-12 16:58:13 UTC 
closed