Issue 8176 - OOo shouldn't abort because of missing Gnome libraries
Summary: OOo shouldn't abort because of missing Gnome libraries
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: 643
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: osavill
QA Contact: issues@installation
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-10-09 12:43 UTC by osavill
Modified: 2003-09-30 07:52 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description osavill 2002-10-09 12:43:40 UTC
The installation of 643 was brought to an abrupt halt. There were no 
explanatory dialogs. One second it was there, the next it wasn't. At the 
launch console was the message that libgconf2.so.3 could not be found. 
Assuming that this is the reason for the sudden abort of the install this 
doesn't seem appropriate. On a system without GConf installed it would not be 
possible to install OOo.
Comment 1 Olaf Felka 2002-10-17 13:15:34 UTC
Hi Owen,
I don't think that this abort depends on missing gnome libraries.
We need more information to reproduce:
- which linux distribution is running
- did you chose not to use gnome at Linux installation
- did you remove it from your system
- have you manually remove any packages belonging to gnome
One further question: Are you using RedHat 7.2? Then please deselect
Java at the setup modules. It's a known issue that setup aborts when
Java is selected (issue 8196)
Comment 2 joerg.skottke 2002-10-17 13:53:57 UTC
We don't need Gnome libraries. Possibly they are required during the
compile-process but not at runtime. Need more info.
Comment 3 osavill 2002-10-17 14:28:02 UTC
> Are you using RedHat 7.2?
Yes I am so this is more likely to be the problem. Does this problem
exist with 7.3 or 8.0 ? If not I will upgrade.

The thing that "fooled" me was the message before the crash about not
being able to find libgconf2.so.3

For a while now OOo has been doing this. In the "old days" OOo used to
produce more verbose error messages. I realise that this may not be
considered a good thing with a released product, but this incident
possibly shows that it can be a good thing. If most users launch from
an icon then a short message to the launch console would probably not
be seen by most users anway.

Anyway I am happy to mark this as FIXED.
Comment 4 Olaf Felka 2002-10-17 14:43:25 UTC
Hi Owen,
I don't know wether this is really fixed, AFAIK we are still
investigating in this problem.
This problem should not occure on RH 7.3 (we haven't seen it yet
there) or if you deselect Java at the OOo modules (which is much
easyer than updating your system) when you don't need Java in OOo.
Comment 5 osavill 2002-10-17 16:55:31 UTC
I'll re-open it :-)
Comment 6 Rainer Bielefeld 2003-09-19 12:11:13 UTC
No reporter-activity for 11 months
No votes
No other one who confirmed the problem

I think we should close that issue.
If someone still sees the problem, the issue can be reopened

If I will not see any further action as votes, attachments or
confirmations, I will have to close this issue 2003-09-30 as WFM.

Rainer
Comment 7 joerg.skottke 2003-09-19 12:34:36 UTC
I have not been able to reproduce this. The only place we use
gnome-libs is within the crash reporter and there the libs are
statically linked.
The missing libgconf2.so.3 is not the reason, just querying info from
gnome doesn't stop the office. BTW: This console output can be seen on
many installations. And still the office runs.
Comment 8 Rainer Bielefeld 2003-09-30 07:52:47 UTC
.