[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#365244: marked as done (Subject: openoffice.org: Bad instructions in the README.Debian file)

Your message dated Sun, 23 Jul 2006 03:25:26 +0200
with message-id <20060723012526.GA20271@rene-engelhard.de>
and subject line Subject: openoffice.org: Bad instructions in the README.Debian file
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Subject: openoffice.org: Bad instructions in the README.Debian file
Package: openoffice.org
Version: 1.1.3-9
Severity: normal


*** Please type your report below this line ***

When I type "openoffice" it says
OpenOffice.org for Debian - see
/usr/share/doc/openoffice.org/README.Debian.gz
running openoffice.org setup...
setup failed (code 0).. abort
---- Please read /usr/share/doc/openoffice.org/README.Debian.gz for
known problems -----

But the information in the README.Debian file is no help at all. For
example it says to try :
cd /usr/lib/openoffice/program; LD_LIBRARY_PATH=. strace ./setup.bin 2>&1 |grep -i "open(.*ttf" | tail 

But this command is not accepted, it says:
Ambiguous output redirect.

Then it says "If you are using NFS mounted file systems" without saying
how we can tell whether we're using NFS or not, nor what NFS stands for.

Then it says:
"You may be able to provide us with information about the crash by
producing a core dump. Make sure you are in a directory where you have write 
permission, and execute this:
ulimit -c 10000; LD_LIBRARY_PATH=/usr/lib/openoffice/program /usr/lib/openoffice/program/setup.bin -R:/etc/openoffice/autoresponse.conf" 

But this does not work either, the answer is:
"ulimit: Command not found.
LD_LIBRARY_PATH=/usr/lib/openoffice/program: Command not found."

Then it goes on about "S3", "Matrox", "nVivia" cards, again
without saying how to check what type of card may or may not
be installed on the machine. Etc...

It may sound like I'm complaining about peanuts to you, but look,
if I was an advanced user I would know how to fix this without
even reading the help file, wouldn't I?

In troubleshooting options it would really be nice to see "try this"
options which will do what they are supposed to do when they are
pasted onto the konsole. And pasted "as stated", I can't adapt these
commands, I don't understand them. "open(.*ttf" looks like it has
a missing closing bracket to me.

So it's a bug in the documentation, OK, not in the code, but it is
preventing me from running OO all the same.

Thank you for reading this.

Mary



-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.12.6-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages openoffice.org depends on:
ii dictionaries-common [openoffi 0.25.12 Common utilities for spelling dict ii openoffice.org-bin 1.1.3-9 OpenOffice.org office suite binary ii openoffice.org-debian-files 1.1.3-8+1 Debian specific parts of OpenOffic ii openoffice.org-l10n-en [openo 1.1.3-9 English (US) language package for 
ii  ttf-opensymbol                1.1.3-9    The OpenSymbol TrueType font
ii xml-core 0.09 XML infrastructure and XML catalog 

-- no debconf information

--- End Message ---
--- Begin Message --- 
[ sorry for the late answer... ]

Hi,

Mary Felkin wrote:
> But the information in the README.Debian file is no help at all. For
> example it says to try :
> cd /usr/lib/openoffice/program; LD_LIBRARY_PATH=. strace ./setup.bin 
> 2>&1 |grep -i "open(.*ttf" | tail
> 
> But this command is not accepted, it says:
> Ambiguous output redirect.

2>&1 is right. You use some Bourne shell - *not* (t)csh?

> Then it says "If you are using NFS mounted file systems" without saying
> how we can tell whether we're using NFS or not, nor what NFS stands for.

If you don't you you don't have it :)
And anyway, people in the unix world now when they have NFS...

> Then it says:
> "You may be able to provide us with information about the crash by
> producing a core dump.  Make sure you are in a directory where you have 
> write
> permission, and execute this:
> 
> ulimit -c 10000; LD_LIBRARY_PATH=/usr/lib/openoffice/program 
> /usr/lib/openoffice/program/setup.bin -R:/etc/openoffice/autoresponse.conf"
> 
> But this does not work either, the answer is:
> "ulimit: Command not found.

$ type ulimit
ulimit is a shell builtin

> LD_LIBRARY_PATH=/usr/lib/openoffice/program: Command not found."

of course. the whole thing is one line.

> Then it goes on about "S3", "Matrox", "nVivia" cards, again
> without saying how to check what type of card may or may not
> be installed on the machine. Etc...

a) That's your problem, you should know your PC
b) there's lspci

> It may sound like I'm complaining about peanuts to you, but look,

No, it's nitpicking.

> if I was an advanced user I would know how to fix this without
> even reading the help file, wouldn't I?

No.

> In troubleshooting options it would really be nice to see "try this"
> options which will do what they are supposed to do when they are
> pasted onto the konsole. And pasted "as stated", I can't adapt these

They do.

In any case, those instructions are not in README.Debian anymore
anyways, so I am just closing this bug...

Regards,

Rene

--- End Message ---
Reply to: