Re: Instant crash with Linux OpenOffice

2009-06-20 Thread Chris Turner

no idea w/r/t hammer -

IIRC I had to muck around with some version of fonts.conf in the past -
perhaps the linux-emulator installed version -
to make things work for some OOO release or another,

e.g. change the directories listed within, or similar..

and then possibly run the linux 'fc-cache' to update..

can't recall..

Francois Tigeot wrote:
  Aniway, I tried your trick of null-mounting fonts/ from /boot. It 
works for

reading documents but fails when trying to save them:



Re: Instant crash with Linux OpenOffice

2009-06-06 Thread Bill Hacker

Matthew Dillon wrote:

:Hi,
:
:I have recently upgraded the root fs to Hammer on one of my machines. Since
:then, I have been unable to run any version of OpenOffice.
:Previously, misc/openoffice2-bin and misc/openoffice3-bin ran fine.
:
:The OS is DragonFly 2.2.2-RELEASE.
:
:The splash screen begins to appear and then OpenOffice crashes with some weird
:errors:
:
:$ soffice
:javaldx: Could not find a Java Runtime Environment! 
:sh: g/,: No such file or directory

:
:$ soffice
:javaldx: Could not find a Java Runtime Environment! 
:sh: -c: line 0: unexpected EOF while looking for matching `''

:sh: -c: line 1: syntax error: unexpected end of file
:
:I'm not sure how to debug this.
:
:-- 
:Francois Tigeot


I've had similar issues with OpenOffice but I have never been able
to figure out what's wrong.  I don't think it is HAMMER per-say, but
instead something related to our linux emulation that is breaking.
It seems to happen more consistently with HAMMER but issues also pop
up with UFS.


OO 2.X also consistently useless on Mac OSX 10.3.9 with all-UFS fs. Shows OO 
splash screen, dies and goes where all responsible bloatware should take itself.


OOS 1.X did work on Mac UFS  10.3.9.

OO 2.X works OK on OSX 10.4 with hfs+ fs.



It could be related to the path prefixing the linux emulation does
to give priority to the emulation directory structure on lookups.

-Matt
	Matthew Dillon 
	dil...@backplane.com


Probably a lot more to it than that I'd point at javishness, but Mac's have 
/* oxymoron warning */ fairly usable java


Bill


Instant crash with Linux OpenOffice

2009-06-02 Thread Francois Tigeot
Hi,

I have recently upgraded the root fs to Hammer on one of my machines. Since
then, I have been unable to run any version of OpenOffice.
Previously, misc/openoffice2-bin and misc/openoffice3-bin ran fine.

The OS is DragonFly 2.2.2-RELEASE.

The splash screen begins to appear and then OpenOffice crashes with some weird
errors:

$ soffice
javaldx: Could not find a Java Runtime Environment! 
sh: g/,: No such file or directory

$ soffice
javaldx: Could not find a Java Runtime Environment! 
sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file

I'm not sure how to debug this.

-- 
Francois Tigeot


Re: Instant crash with Linux OpenOffice

2009-06-02 Thread Simon 'corecode' Schubert

Francois Tigeot wrote:

I have recently upgraded the root fs to Hammer on one of my machines. Since
then, I have been unable to run any version of OpenOffice.


I'll add my crashes (HAMMER, 2.3.1):
% soffice
javaldx: Could not find a Java Runtime Environment!
/etc/host.conf: line 4: bad command `hosts'
/etc/host.conf: line 6: bad command `bind'
Fontconfig error: conf.d, line 1: no element found

Same thing, splash appears, then aborts.

cheers
  simon

--
  3 the future  +++  RENT this banner advert  +++   ASCII Ribbon   /\
  rock the past  +++  space for low €€€ NOW!1  +++ Campaign \ /
Party Enjoy Relax   |   http://dragonflybsd.org  Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz   Mail + News   / \



Re: Instant crash with Linux OpenOffice

2009-06-02 Thread Sdävtaker
I got a another one
I created a fresh pfs-slave, and after that i did mirror-copy from
home to the fresh pfs. Then i got kernel panic.
After reboot tried the mirror-copy again and worked ok.
i could reproduce it at home, i was using dfbsd 2.2.1
I think its a problem about the timing of the operations, maybe it
needs to wait for sync before the mirror copy and maybe it is already
fixed in 2.2.2.
Sdav


On Tue, Jun 2, 2009 at 04:41, Simon 'corecode' Schubert
corec...@fs.ei.tum.de wrote:
 Francois Tigeot wrote:

 I have recently upgraded the root fs to Hammer on one of my machines.
 Since
 then, I have been unable to run any version of OpenOffice.

 I'll add my crashes (HAMMER, 2.3.1):
 % soffice
 javaldx: Could not find a Java Runtime Environment!
 /etc/host.conf: line 4: bad command `hosts'
 /etc/host.conf: line 6: bad command `bind'
 Fontconfig error: conf.d, line 1: no element found

 Same thing, splash appears, then aborts.

 cheers
  simon

 --
  3 the future  +++  RENT this banner advert  +++   ASCII Ribbon   /\
  rock the past  +++  space for low €€€ NOW!1  +++     Campaign     \ /
 Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
 Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \





-- 
Sdävtaker prays to Rikku goddess for a good treasure.


Re: Instant crash with Linux OpenOffice

2009-06-02 Thread Matthew Dillon

:I got a another one
:I created a fresh pfs-slave, and after that i did mirror-copy from
:home to the fresh pfs. Then i got kernel panic.
:After reboot tried the mirror-copy again and worked ok.
:i could reproduce it at home, i was using dfbsd 2.2.1
:I think its a problem about the timing of the operations, maybe it
:needs to wait for sync before the mirror copy and maybe it is already
:fixed in 2.2.2.
:Sdav

What was the kernel panic?

There *WAS* a bug related to doing mirror-copy's to a fresh slave,
the kernel would panic on not being able to find the root inode on
the slave (because it hadn't been copied yet by the mirror code).

I'm pretty sure I fixed it in HEAD and possibly also in 2.2.2.

-Matt
Matthew Dillon 
dil...@backplane.com


Re: Instant crash with Linux OpenOffice

2009-06-02 Thread Matthew Dillon

:Hi,
:
:I have recently upgraded the root fs to Hammer on one of my machines. Since
:then, I have been unable to run any version of OpenOffice.
:Previously, misc/openoffice2-bin and misc/openoffice3-bin ran fine.
:
:The OS is DragonFly 2.2.2-RELEASE.
:
:The splash screen begins to appear and then OpenOffice crashes with some weird
:errors:
:
:$ soffice
:javaldx: Could not find a Java Runtime Environment! 
:sh: g/,: No such file or directory
:
:$ soffice
:javaldx: Could not find a Java Runtime Environment! 
:sh: -c: line 0: unexpected EOF while looking for matching `''
:sh: -c: line 1: syntax error: unexpected end of file
:
:I'm not sure how to debug this.
:
:-- 
:Francois Tigeot

I've had similar issues with OpenOffice but I have never been able
to figure out what's wrong.  I don't think it is HAMMER per-say, but
instead something related to our linux emulation that is breaking.
It seems to happen more consistently with HAMMER but issues also pop
up with UFS.

It could be related to the path prefixing the linux emulation does
to give priority to the emulation directory structure on lookups.

-Matt
Matthew Dillon 
dil...@backplane.com


Re: Instant crash with Linux OpenOffice

2009-06-02 Thread Matthew Dillon
:...
:javaldx: Could not find a Java Runtime Environment!
:/etc/host.conf: line 4: bad command `hosts'
:/etc/host.conf: line 6: bad command `bind'
:Fontconfig error: conf.d, line 1: no element found
:
:Same thing, splash appears, then aborts.
:
:cheers
:   simon

What I did on my laptop to make it work was put
/usr/pkg/openoffice.org2.4/share/fonts on a small UFS partition
(my /boot) and then null-mount it onto
/usr/pkg/openoffice.org2.4/share/fonts.

This can be done using the VN device as well.  I know it's nuts but
it seemed to work.

OpenOffice has other issues unrelated to the filesystem... it has issues
trying to locate files due to the prioritized linux emulation path
lookups.  It gets very confused sometimes.

I could never figure out why it didn't work with HAMMER.  I'm at a loss.
Maybe there's some sort of zero-fill or other issue related to the linux
emulation but I ran out of time trying to diagnose it.  I still don't
think it is HAMMER-specific but instead some sort of side effect
somewhere, like perhaps related to the stat info for the file(s) or
something.  I just don't know.

-Matt



Re: Instant crash with Linux OpenOffice

2009-06-02 Thread Francois Tigeot
On Tue, Jun 02, 2009 at 12:11:35PM -0700, Matthew Dillon wrote:
 What I did on my laptop to make it work was put
 /usr/pkg/openoffice.org2.4/share/fonts on a small UFS partition
 (my /boot) and then null-mount it onto
 /usr/pkg/openoffice.org2.4/share/fonts.
 
 OpenOffice has other issues unrelated to the filesystem... it has issues
 trying to locate files due to the prioritized linux emulation path
 lookups.  It gets very confused sometimes.

I had a quick look at the source distribution; the build system is full of
arcane and unneeded stuff. Like configure scripts auto-generating perl
scripts, themselves sourcing environment variables from two possible different
shell scripts, one bash, one tcsh for good mesure, etc...
It also has its own make program, and about a dozen old versions of other
programs and libraries thrown in the tarball for fun.

Pure madness.
I can only imagine what sort of bugs and assumptions lie in the source code
proper...


Aniway, I tried your trick of null-mounting fonts/ from /boot. It works for
reading documents but fails when trying to save them:

Error saving the document blah:
Write Error.
The file could not be written.

blah.ods is in my /home pfs, and chmod 0666.


The auto-save feature gives a different error message:

Openoffice.org could not save important internal information due to
insufficient free disk space at the following location:
/home/ftigeot/.openoffice.org/3/user/backup

You will not be able to continue working with OpenOffice.org without
allocating more free disk space at that location.


There is 80 GB of free space on this fs. Could it be counting free inodes ?

-- 
Francois Tigeot


Re: Instant crash with Linux OpenOffice

2009-06-02 Thread Joerg Sonnenberger
On Tue, Jun 02, 2009 at 11:46:53PM +0200, Francois Tigeot wrote:
 Pure madness.

Come on, it has gotten a lot better since the OpenOffice 1.x days.
I think they no longer use Pascal in the build system, not sure about
Java and Python though.

Joerg


Re: Instant crash with Linux OpenOffice

2009-06-02 Thread Matthew Dillon

Yah, I gave up trying to mess with the source to track the issue
down last time.  It would be really valuable if someone tracked down
the font startup issue.

-Matt
Matthew Dillon 
dil...@backplane.com