Re: OpenOffice.org1.1 crash with: version GLIBC_2.0 not defined in file libm.so.6 with linktime reference

2003-06-10 Thread Jack Howarth
Jan, I can start the ooffice1.1 without problems here on my debian ppc sid box (this is under debian glibc cvs 2.3.2-1). Everything seems to run fine so far. Jack

Re: Gnome Menu Location of OOo1.1

2003-06-10 Thread Jérôme Warnier
Le mar 10/06/2003 à 14:18, Jan-Hendrik Palic a écrit : > Hi .. > > since, I really finished up the build of 1.1beta2 for me *sigh*, I > realized, that my patches for the gnome integration are not working at > all. The printer-admin-icon is at the wrong place again .. > > I will fix and rework i

OpenOffice.org1.1 crash with: version GLIBC_2.0 not defined in file libm.so.6 with linktime reference

2003-06-10 Thread Jan-Hendrik Palic
Hi... Running OpenOffice.org on debian-unstable (powerpc) I get: 15:02 $openoffice1.1 OpenOffice.org for Debian - see/usr/share/doc/openoffice.org1.1/README.Debian.gz running openoffice.org 1.1 setup... Setup complete. Running openoffice.org... .. importing layer file:///mnt/develop/.tmp/oooLoc

Gnome Menu Location of OOo1.1

2003-06-10 Thread Jan-Hendrik Palic
Hi .. since, I really finished up the build of 1.1beta2 for me *sigh*, I realized, that my patches for the gnome integration are not working at all. The printer-admin-icon is at the wrong place again .. I will fix and rework it And, if I am working on the gnome-integration, I will look fo

Re: oo 1.1 beta2

2003-06-10 Thread jan . palic
Hi .. I build OpenOffice.org on Debian-PPC (unstable) ... You can get it from: http://sevdalia.hajvan.net/~palic/OpenOffice.org/1.1/ until OOo1.1 is already uploaded. I build it with the recent libc from unstable, not 2.3.2. I have a look an mail you, when I have a solution for the ld.so ass

Bug#194898: marked as done (openoffice.org: bad date interpretation (today's date))

2003-06-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Jun 2003 10:37:45 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#194898: closing as requested by submitter 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