Re: New Committer: Arrigo Marchiori

[Keith N. McKenna]

On 12/26/2020 4:19 PM, Marcus wrote:
> The Apache OpenOffice project is happy to have a new committer on board:
> 
> Arrigo Marchiori
> 
> Please give him a warm welcome. :-)
> 
> Marcus
> (on behalf of the Apache OpenOffice PMC)

Welcome and congratulations Arrigio.

Regards
Keith



signature.asc
Description: OpenPGP digital signature

Re: New Committer: Arrigo Marchiori

[Matthias Seidel]

Hi Arrigo,

Welcome!

I promise we get some more of your PRs merged. ;-)

Regards,

   Matthias

Am 26.12.20 um 22:19 schrieb Marcus:
> The Apache OpenOffice project is happy to have a new committer on board:
>
> Arrigo Marchiori
>
> Please give him a warm welcome. :-)
>
> Marcus
> (on behalf of the Apache OpenOffice PMC)
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [openoffice] branch AOO419 updated: Force SDK 10.11 at most Pass NULL, not -1 (!!)

[Matthias Seidel]

Hi Jim,

Am 26.12.20 um 21:59 schrieb Jim Jagielski:
> I have uploaded a test build of en-US AOO419-dev for macOS. I have confirmed 
> on my macOS11/BigSur VM that this version opens docx files w/ no problems, 
> edits and saves them, etc...
>
> Please test:
>
> http://home.apache.org/~jim/AOO-builds/

I did a quick test with your build and can confirm that it opens docx
files without problems.
This was on macOS 11.2 beta

No other file formats were tested.

Regards,

   Matthias

>
> Cheers!
>
>> On Dec 26, 2020, at 3:54 PM, Rory O'Farrell  wrote:
>>
>> On Sat, 26 Dec 2020 21:43:06 +0100
>> Matthias Seidel > > wrote:
>>
>>> Hi Jim,
>>>
>>> Am 26.12.20 um 20:45 schrieb Jim Jagielski:
 So there is for sure a bug in AOO41X, but why it only seems to affect 
 macOS BigSur is
 unknown. It is this:

> diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx 
> b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> index f4d6c56..2ca9b8f 100644
> --- a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> +++ b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> @@ -195,7 +195,7 @@ VtableFactory::VtableFactory(): m_arena(
>rtl_arena_create(
>"bridges::cpp_uno::shared::VtableFactory",
>sizeof (void *), // to satisfy alignment requirements
> -0, reinterpret_cast< rtl_arena_type * >(-1), allocExec, 
> freeExec, 0))
> +0, reinterpret_cast< rtl_arena_type * >(0), allocExec, freeExec, 
> 0))
> {
>if (m_arena == 0) {
>throw std::bad_alloc();
 I *think* this solves the issue, and a quick-and-dirty compilation seems 
 to indicate that, but
 I will double check.

 The question is: Does this warrant a full 4.1.9 release for ALL platforms? 
 To my mind, it does.
>>> I will start a test build on Windows right now...
>>>
>>> We have a small Linux issue as well [1] and we can still put some minor
>>> cherry-picks into this build.
>>>
>>> +1 for a 4.1.9
>>>
>>> Regards,
>>>
>>>Matthias
>>>
>>> [1] https://bz.apache.org/ooo/show_bug.cgi?id=128413
>> I think all platforms should maintain the same version numbering.  
>>
>> There are occasional but frequent reports on Forum of problems with tables 
>> in Writer causing crashes when they are extended to cover multiple pages; my 
>> usual advice is to limit tables to one page, and repeat the structure if 
>> needed on subsequent pages.  This seems to work; I cannot comment from 
>> personal experience as my routine work does not involve Writer tables.  If 
>> this proposed fix involves tables it may have cross-talk into the Windows 
>> and other platforms.
>>
>> -- 
>> Rory O'Farrell mailto:ofarr...@iol.ie>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
>> 
>> For additional commands, e-mail: dev-h...@openoffice.apache.org 
>> 



smime.p7s
Description: S/MIME Cryptographic Signature

New Committer: Arrigo Marchiori

[Marcus]

The Apache OpenOffice project is happy to have a new committer on board:

Arrigo Marchiori

Please give him a warm welcome. :-)

Marcus
(on behalf of the Apache OpenOffice PMC)

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [openoffice] branch AOO419 updated: bump rev to 4.1.9

[Marcus]

As Jim is bumping the version numbers for a new release.

I know we have a script to increase the version number for a new build / 
release. And the 4.1.x releases up to now are a good proof that it works.


However, when looking at the code I think there are too many places (5 
different files with countless lines where it needs to be adjusted). 
Therefore it's somehow error-prone and it should be stripped-down to a 
minimum of files and places.


@all:
Do you also think this way?
Or is it just me?

Thanks

Marcus



Am 26.12.20 um 22:06 schrieb j...@apache.org:

This is an automated email from the ASF dual-hosted git repository.

jim pushed a commit to branch AOO419
in repository https://gitbox.apache.org/repos/asf/openoffice.git


The following commit(s) were added to refs/heads/AOO419 by this push:
  new 30f2cd9  bump rev to 4.1.9
  new 96ef350  Merge branch 'AOO419' of 
https://gitbox.apache.org/repos/asf/openoffice into AOO419
30f2cd9 is described below

commit 30f2cd9a04dc52522341372a9eff85674a7e9f73
Author: Jim Jagielski 
AuthorDate: Sat Dec 26 16:06:23 2020 -0500

 bump rev to 4.1.9
---
  main/instsetoo_native/util/openoffice.lst | 42 +++
  main/odk/util/makefile.pmk|  2 +-
  main/solenv/bin/srcrelease.xml|  2 +-
  main/solenv/inc/minor.mk  | 10 
  main/sysui/desktop/productversion.mk  |  2 +-
  5 files changed, 29 insertions(+), 29 deletions(-)

diff --git a/main/instsetoo_native/util/openoffice.lst 
b/main/instsetoo_native/util/openoffice.lst
index 004c619..b7be746 100644
--- a/main/instsetoo_native/util/openoffice.lst
+++ b/main/instsetoo_native/util/openoffice.lst
@@ -6,8 +6,8 @@ Globals
  {
  APACHEPROJECTNAME Apache OpenOffice
  OOOBASEVERSION 4.1
-OOOPACKAGEVERSION 4.1.8
-UREPACKAGEVERSION 4.1.8
+OOOPACKAGEVERSION 4.1.9
+UREPACKAGEVERSION 4.1.9
  URELAYERVERSION 1
  BASISROOTNAME OpenOffice
  UNIXBASISROOTNAME openoffice
@@ -59,8 +59,8 @@ Apache_OpenOffice
  {
  FULLPRODUCTNAME Apache OpenOffice
  PRODUCTNAME OpenOffice
-PRODUCTVERSION 4.1.8
-PREVIOUS_VERSION 4.1.7
+PRODUCTVERSION 4.1.9
+PREVIOUS_VERSION 4.1.8
  PRODUCTEXTENSION
  LONG_PRODUCTEXTENSION
  SHORT_PRODUCTEXTENSION
@@ -68,7 +68,7 @@ Apache_OpenOffice
  POSTVERSIONEXTENSIONUNIX
  BRANDPACKAGEVERSION 4
  USERDIRPRODUCTVERSION 4
-ABOUTBOXPRODUCTVERSION 4.1.8
+ABOUTBOXPRODUCTVERSION 4.1.9
  BASEPRODUCTVERSION 4.1
  PCPFILENAME openoffice.pcp
  UPDATEURL https://ooo-updates.apache.org/aoo418/check.Update
@@ -76,7 +76,7 @@ Apache_OpenOffice
  REMOVE_UPGRADE_CODE_FILE upgradecode_remove_ooo.txt
  ADDSYSTEMINTEGRATION 1
  EVAL
-PACKAGEVERSION 4.1.8
+PACKAGEVERSION 4.1.9
  PACKAGEREVISION {milestone}
  LICENSENAME ALv2
  GLOBALFILEGID gid_File_Lib_Vcl
@@ -120,7 +120,7 @@ Apache_OpenOffice_wJRE
  {
  FULLPRODUCTNAME Apache OpenOffice
  PRODUCTNAME OpenOffice
-PRODUCTVERSION 4.1.8
+PRODUCTVERSION 4.1.9
  PRODUCTEXTENSION
  LONG_PRODUCTEXTENSION
  SHORT_PRODUCTEXTENSION
@@ -128,14 +128,14 @@ Apache_OpenOffice_wJRE
  POSTVERSIONEXTENSIONUNIX
  BRANDPACKAGEVERSION 4
  USERDIRPRODUCTVERSION 4
-ABOUTBOXPRODUCTVERSION 4.1.8
+ABOUTBOXPRODUCTVERSION 4.1.9
  BASEPRODUCTVERSION 4.1
  UPDATEURL https://ooo-updates.apache.org/aoo418/check.Update
  ADD_INCLUDE_FILES 
cliureversion.mk,clioootypesversion.mk,javaversion2.dat,userland.txt,version.lst
  REMOVE_UPGRADE_CODE_FILE upgradecode_remove_ooo.txt
  ADDSYSTEMINTEGRATION 1
  EVAL
-PACKAGEVERSION 4.1.8
+PACKAGEVERSION 4.1.9
  PACKAGEREVISION {milestone}
  LICENSENAME ALv2
  WITHJREPRODUCT 1
@@ -180,7 +180,7 @@ Apache_OpenOffice_Dev
  {
  FULLPRODUCTNAME AOO-Developer-Build
  PRODUCTNAME AOO-Developer-Build
-PRODUCTVERSION 4.1.8
+PRODUCTVERSION 4.1.9
  PRODUCTEXTENSION
  LONG_PRODUCTEXTENSION
  SHORT_PRODUCTEXTENSION
@@ -190,7 +190,7 @@ Apache_OpenOffice_Dev
  POSTVERSIONEXTENSIONUNIX
  BRANDPACKAGEVERSION 4
  USERDIRPRODUCTVERSION 4
-ABOUTBOXPRODUCTVERSION 4.1.8
+ABOUTBOXPRODUCTVERSION 4.1.9
  BASEPRODUCTVERSION 4.1
  DEVELOPMENTPRODUCT 1
  BASISPACKAGEPREFIX aoodev
@@ -200,7 +200,7 @@ Apache_OpenOffice_Dev
  

RE: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)

[Jörg Schmidt]

 

> -Original Message-
> From: Jörg Schmidt [mailto:joe...@j-m-schmidt.de] 
> Sent: Saturday, December 26, 2020 10:05 PM
> To: dev@openoffice.apache.org
> Subject: RE: How should we proceed with BigSur? (was: Does 
> AOO 4.1.8 run under macOS Big Sur?)
> 
> > -Original Message-
> > From: Jim Jagielski [mailto:j...@jagunet.com] 
> > Sent: Saturday, December 26, 2020 3:18 PM
> > To: dev
> > Subject: Re: How should we proceed with BigSur? (was: Does 
> > AOO 4.1.8 run under macOS Big Sur?)
> > 
> > It is more than likely that we may need to release a 4.1.9 
> > just to accommodate BigSur. However, AOO
> > is hardly unique in being an app that no longer works when 
> > someone upgrades to BigSur. The macOS
> > community is replete w/ such apps. I'm not using that as an 
> > excuse, but that is what it is.
> 
> I have not claimed anything to the contrary.
> 
> Other "apps" are not our job, but our job is to do a good job 
> for AOO and currently informing the users would be part of 
> the good job. 

Oh, sorry, I thought your reply was referring to the other thread (="Addition 
in release notes because of Big Sur").


Jörg


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [openoffice] branch AOO419 updated: Force SDK 10.11 at most Pass NULL, not -1 (!!)

[Matthias Seidel]

Hi Jim,

Am 26.12.20 um 21:59 schrieb Jim Jagielski:
> I have uploaded a test build of en-US AOO419-dev for macOS. I have confirmed 
> on my macOS11/BigSur VM that this version opens docx files w/ no problems, 
> edits and saves them, etc...
>
> Please test:
>
> http://home.apache.org/~jim/AOO-builds/

I will test it...

However, when we already have a new branch, we should bump up the
version numbers asap.

Matthias

>
> Cheers!
>
>> On Dec 26, 2020, at 3:54 PM, Rory O'Farrell  wrote:
>>
>> On Sat, 26 Dec 2020 21:43:06 +0100
>> Matthias Seidel > > wrote:
>>
>>> Hi Jim,
>>>
>>> Am 26.12.20 um 20:45 schrieb Jim Jagielski:
 So there is for sure a bug in AOO41X, but why it only seems to affect 
 macOS BigSur is
 unknown. It is this:

> diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx 
> b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> index f4d6c56..2ca9b8f 100644
> --- a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> +++ b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> @@ -195,7 +195,7 @@ VtableFactory::VtableFactory(): m_arena(
>rtl_arena_create(
>"bridges::cpp_uno::shared::VtableFactory",
>sizeof (void *), // to satisfy alignment requirements
> -0, reinterpret_cast< rtl_arena_type * >(-1), allocExec, 
> freeExec, 0))
> +0, reinterpret_cast< rtl_arena_type * >(0), allocExec, freeExec, 
> 0))
> {
>if (m_arena == 0) {
>throw std::bad_alloc();
 I *think* this solves the issue, and a quick-and-dirty compilation seems 
 to indicate that, but
 I will double check.

 The question is: Does this warrant a full 4.1.9 release for ALL platforms? 
 To my mind, it does.
>>> I will start a test build on Windows right now...
>>>
>>> We have a small Linux issue as well [1] and we can still put some minor
>>> cherry-picks into this build.
>>>
>>> +1 for a 4.1.9
>>>
>>> Regards,
>>>
>>>Matthias
>>>
>>> [1] https://bz.apache.org/ooo/show_bug.cgi?id=128413
>> I think all platforms should maintain the same version numbering.  
>>
>> There are occasional but frequent reports on Forum of problems with tables 
>> in Writer causing crashes when they are extended to cover multiple pages; my 
>> usual advice is to limit tables to one page, and repeat the structure if 
>> needed on subsequent pages.  This seems to work; I cannot comment from 
>> personal experience as my routine work does not involve Writer tables.  If 
>> this proposed fix involves tables it may have cross-talk into the Windows 
>> and other platforms.
>>
>> -- 
>> Rory O'Farrell mailto:ofarr...@iol.ie>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
>> 
>> For additional commands, e-mail: dev-h...@openoffice.apache.org 
>> 



smime.p7s
Description: S/MIME Cryptographic Signature

RE: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)

[Jörg Schmidt]

> -Original Message-
> From: Jim Jagielski [mailto:j...@jagunet.com] 
> Sent: Saturday, December 26, 2020 3:18 PM
> To: dev
> Subject: Re: How should we proceed with BigSur? (was: Does 
> AOO 4.1.8 run under macOS Big Sur?)
> 
> It is more than likely that we may need to release a 4.1.9 
> just to accommodate BigSur. However, AOO
> is hardly unique in being an app that no longer works when 
> someone upgrades to BigSur. The macOS
> community is replete w/ such apps. I'm not using that as an 
> excuse, but that is what it is.

I have not claimed anything to the contrary.

Other "apps" are not our job, but our job is to do a good job for AOO and 
currently informing the users would be part of the good job. 


Jörg


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [openoffice] branch AOO419 updated: Force SDK 10.11 at most Pass NULL, not -1 (!!)

[Jim Jagielski]

BUGZ seems to be a build issue, not a code one, but it still needs to be fixed 
and noted, likely with some autoconf checks that fakeroot exists.

> On Dec 26, 2020, at 3:43 PM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> Am 26.12.20 um 20:45 schrieb Jim Jagielski:
>> So there is for sure a bug in AOO41X, but why it only seems to affect macOS 
>> BigSur is
>> unknown. It is this:
>> 
>>> diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx 
>>> b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>>> index f4d6c56..2ca9b8f 100644
>>> --- a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>>> +++ b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>>> @@ -195,7 +195,7 @@ VtableFactory::VtableFactory(): m_arena(
>>>rtl_arena_create(
>>>"bridges::cpp_uno::shared::VtableFactory",
>>>sizeof (void *), // to satisfy alignment requirements
>>> -0, reinterpret_cast< rtl_arena_type * >(-1), allocExec, freeExec, 
>>> 0))
>>> +0, reinterpret_cast< rtl_arena_type * >(0), allocExec, freeExec, 
>>> 0))
>>> {
>>>if (m_arena == 0) {
>>>throw std::bad_alloc();
>> I *think* this solves the issue, and a quick-and-dirty compilation seems to 
>> indicate that, but
>> I will double check.
>> 
>> The question is: Does this warrant a full 4.1.9 release for ALL platforms? 
>> To my mind, it does.
> 
> I will start a test build on Windows right now...
> 
> We have a small Linux issue as well [1] and we can still put some minor
> cherry-picks into this build.
> 
> +1 for a 4.1.9
> 
> Regards,
> 
>Matthias
> 
> [1] https://bz.apache.org/ooo/show_bug.cgi?id=128413
> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [openoffice] branch AOO419 updated: Force SDK 10.11 at most Pass NULL, not -1 (!!)

[Jim Jagielski]

I have uploaded a test build of en-US AOO419-dev for macOS. I have confirmed on 
my macOS11/BigSur VM that this version opens docx files w/ no problems, edits 
and saves them, etc...

Please test:

http://home.apache.org/~jim/AOO-builds/

Cheers!

> On Dec 26, 2020, at 3:54 PM, Rory O'Farrell  wrote:
> 
> On Sat, 26 Dec 2020 21:43:06 +0100
> Matthias Seidel  > wrote:
> 
>> Hi Jim,
>> 
>> Am 26.12.20 um 20:45 schrieb Jim Jagielski:
>>> So there is for sure a bug in AOO41X, but why it only seems to affect macOS 
>>> BigSur is
>>> unknown. It is this:
>>> 
 diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx 
 b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
 index f4d6c56..2ca9b8f 100644
 --- a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
 +++ b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
 @@ -195,7 +195,7 @@ VtableFactory::VtableFactory(): m_arena(
rtl_arena_create(
"bridges::cpp_uno::shared::VtableFactory",
sizeof (void *), // to satisfy alignment requirements
 -0, reinterpret_cast< rtl_arena_type * >(-1), allocExec, freeExec, 
 0))
 +0, reinterpret_cast< rtl_arena_type * >(0), allocExec, freeExec, 
 0))
 {
if (m_arena == 0) {
throw std::bad_alloc();
>>> I *think* this solves the issue, and a quick-and-dirty compilation seems to 
>>> indicate that, but
>>> I will double check.
>>> 
>>> The question is: Does this warrant a full 4.1.9 release for ALL platforms? 
>>> To my mind, it does.
>> 
>> I will start a test build on Windows right now...
>> 
>> We have a small Linux issue as well [1] and we can still put some minor
>> cherry-picks into this build.
>> 
>> +1 for a 4.1.9
>> 
>> Regards,
>> 
>>Matthias
>> 
>> [1] https://bz.apache.org/ooo/show_bug.cgi?id=128413
> 
> I think all platforms should maintain the same version numbering.  
> 
> There are occasional but frequent reports on Forum of problems with tables in 
> Writer causing crashes when they are extended to cover multiple pages; my 
> usual advice is to limit tables to one page, and repeat the structure if 
> needed on subsequent pages.  This seems to work; I cannot comment from 
> personal experience as my routine work does not involve Writer tables.  If 
> this proposed fix involves tables it may have cross-talk into the Windows and 
> other platforms.
> 
> -- 
> Rory O'Farrell mailto:ofarr...@iol.ie>>
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
> 
> For additional commands, e-mail: dev-h...@openoffice.apache.org 
> 

Re: [openoffice] branch AOO419 updated: Force SDK 10.11 at most Pass NULL, not -1 (!!)

[Rory O'Farrell]

On Sat, 26 Dec 2020 21:43:06 +0100
Matthias Seidel  wrote:

> Hi Jim,
> 
> Am 26.12.20 um 20:45 schrieb Jim Jagielski:
> > So there is for sure a bug in AOO41X, but why it only seems to affect macOS 
> > BigSur is
> > unknown. It is this:
> >
> >> diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx 
> >> b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> >> index f4d6c56..2ca9b8f 100644
> >> --- a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> >> +++ b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> >> @@ -195,7 +195,7 @@ VtableFactory::VtableFactory(): m_arena(
> >> rtl_arena_create(
> >> "bridges::cpp_uno::shared::VtableFactory",
> >> sizeof (void *), // to satisfy alignment requirements
> >> -0, reinterpret_cast< rtl_arena_type * >(-1), allocExec, freeExec, 
> >> 0))
> >> +0, reinterpret_cast< rtl_arena_type * >(0), allocExec, freeExec, 
> >> 0))
> >> {
> >> if (m_arena == 0) {
> >> throw std::bad_alloc();
> > I *think* this solves the issue, and a quick-and-dirty compilation seems to 
> > indicate that, but
> > I will double check.
> >
> > The question is: Does this warrant a full 4.1.9 release for ALL platforms? 
> > To my mind, it does.
> 
> I will start a test build on Windows right now...
> 
> We have a small Linux issue as well [1] and we can still put some minor
> cherry-picks into this build.
> 
> +1 for a 4.1.9
> 
> Regards,
> 
>    Matthias
> 
> [1] https://bz.apache.org/ooo/show_bug.cgi?id=128413

I think all platforms should maintain the same version numbering.  

There are occasional but frequent reports on Forum of problems with tables in 
Writer causing crashes when they are extended to cover multiple pages; my usual 
advice is to limit tables to one page, and repeat the structure if needed on 
subsequent pages.  This seems to work; I cannot comment from personal 
experience as my routine work does not involve Writer tables.  If this proposed 
fix involves tables it may have cross-talk into the Windows and other platforms.

-- 
Rory O'Farrell 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [openoffice] branch AOO419 updated: Force SDK 10.11 at most Pass NULL, not -1 (!!)

[Marcus]

Am 26.12.20 um 21:43 schrieb Matthias Seidel:

Am 26.12.20 um 20:45 schrieb Jim Jagielski:

So there is for sure a bug in AOO41X, but why it only seems to affect macOS 
BigSur is
unknown. It is this:


diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx 
b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
index f4d6c56..2ca9b8f 100644
--- a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
+++ b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
@@ -195,7 +195,7 @@ VtableFactory::VtableFactory(): m_arena(
 rtl_arena_create(
 "bridges::cpp_uno::shared::VtableFactory",
 sizeof (void *), // to satisfy alignment requirements
-0, reinterpret_cast< rtl_arena_type * >(-1), allocExec, freeExec, 0))
+0, reinterpret_cast< rtl_arena_type * >(0), allocExec, freeExec, 0))
{
 if (m_arena == 0) {
 throw std::bad_alloc();

I *think* this solves the issue, and a quick-and-dirty compilation seems to 
indicate that, but
I will double check.

The question is: Does this warrant a full 4.1.9 release for ALL platforms? To 
my mind, it does.


when we put in some minor bug fixes for all plattforms, then yes.
But this time they must be *really* small.


I will start a test build on Windows right now...

We have a small Linux issue as well [1] and we can still put some minor
cherry-picks into this build.

+1 for a 4.1.9

[1] https://bz.apache.org/ooo/show_bug.cgi?id=128413


Yes +1

Marcus


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [openoffice] branch AOO419 updated: Force SDK 10.11 at most Pass NULL, not -1 (!!)

[Matthias Seidel]

Hi Jim,

Am 26.12.20 um 20:45 schrieb Jim Jagielski:
> So there is for sure a bug in AOO41X, but why it only seems to affect macOS 
> BigSur is
> unknown. It is this:
>
>> diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx 
>> b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>> index f4d6c56..2ca9b8f 100644
>> --- a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>> +++ b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
>> @@ -195,7 +195,7 @@ VtableFactory::VtableFactory(): m_arena(
>> rtl_arena_create(
>> "bridges::cpp_uno::shared::VtableFactory",
>> sizeof (void *), // to satisfy alignment requirements
>> -0, reinterpret_cast< rtl_arena_type * >(-1), allocExec, freeExec, 
>> 0))
>> +0, reinterpret_cast< rtl_arena_type * >(0), allocExec, freeExec, 0))
>> {
>> if (m_arena == 0) {
>> throw std::bad_alloc();
> I *think* this solves the issue, and a quick-and-dirty compilation seems to 
> indicate that, but
> I will double check.
>
> The question is: Does this warrant a full 4.1.9 release for ALL platforms? To 
> my mind, it does.

I will start a test build on Windows right now...

We have a small Linux issue as well [1] and we can still put some minor
cherry-picks into this build.

+1 for a 4.1.9

Regards,

   Matthias

[1] https://bz.apache.org/ooo/show_bug.cgi?id=128413

>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [openoffice] branch AOO419 updated: Force SDK 10.11 at most Pass NULL, not -1 (!!)

[Jim Jagielski]

So there is for sure a bug in AOO41X, but why it only seems to affect macOS 
BigSur is
unknown. It is this:

> diff --git a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx 
> b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> index f4d6c56..2ca9b8f 100644
> --- a/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> +++ b/main/bridges/source/cpp_uno/shared/vtablefactory.cxx
> @@ -195,7 +195,7 @@ VtableFactory::VtableFactory(): m_arena(
> rtl_arena_create(
> "bridges::cpp_uno::shared::VtableFactory",
> sizeof (void *), // to satisfy alignment requirements
> -0, reinterpret_cast< rtl_arena_type * >(-1), allocExec, freeExec, 0))
> +0, reinterpret_cast< rtl_arena_type * >(0), allocExec, freeExec, 0))
> {
> if (m_arena == 0) {
> throw std::bad_alloc();

I *think* this solves the issue, and a quick-and-dirty compilation seems to 
indicate that, but
I will double check.

The question is: Does this warrant a full 4.1.9 release for ALL platforms? To 
my mind, it does.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Big Sur 4.1.x core dumps

[Jim Jagielski]

I've confirmed that my 4.2.0 builds work fine on BigSur but
the 4.1.8 builds, even using Xcode10 and the 10.13SDK still
result in core on macOS11. Below you'll find the stack.

My initial thoughts are that it is NOT a build issue, but
rather a code one, so I'll start some investigation with that
mindset and especially look at the diffs between AOO418 and
AOO42X that might be key.


Time Awake Since Boot: 1000 seconds

System Integrity Protection: enabled

Crashed Thread:0  Dispatch queue: com.apple.main-thread

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   KERN_INVALID_ADDRESS at 0x0009
Exception Note:EXC_CORPSE_NOTIFY

Termination Signal:Segmentation fault: 11
Termination Reason:Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [1770]

VM Regions Near 0x9:
--> 
__TEXT  10d063000-10d064000[4K] r-x/rwx SM=COW  
/Applications/OpenOffice-4.1.8.app/Contents/MacOS/soffice

Application Specific Information:
ViewBridge hint(s): (
"bridge key: delegateInvocation"
)

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libs5abi_uno.dylib  0x0001162d7259 
s5abi::fillUnoException(s5abi::__cxa_exception*, _uno_Any*, _uno_Mapping*) + 41
1   libs5abi_uno.dylib  0x0001162d98bd 0x1162d5000 + 18621
2   libs5abi_uno.dylib  0x0001162d8e40 
bridges::cpp_uno::shared::unoInterfaceProxyDispatch(_uno_Interface*, 
_typelib_TypeDescription const*, void*, void**, _uno_Any**) + 736
3   libuno_cppuhelpers5abi.dylib.3  0x00010d4cd688 
cppu::getCaughtException() + 840
4   libxstor.dylib  0x00013868d104 
OStorage::hasByName(rtl::OUString const&) + 964
5   libxo.dylib 0x000111d4b222 
XMLVersionListPersistence::load(com::sun::star::uno::Reference
 const&) + 322
6   libxo.dylib 0x000111d4b9be non-virtual thunk to 
XMLVersionListPersistence::load(com::sun::star::uno::Reference
 const&) + 14
7   libsfx.dylib0x00010d807fcf 
SfxMedium::GetVersionList(com::sun::star::uno::Reference
 const&) + 271
8   libsfx.dylib0x00010d787753 
sfx2::FileDialogHelper_Impl::updateVersions() + 547
9   libsfx.dylib0x00010d795afd 
sfx2::FileDialogHelper::FileSelectionChanged(com::sun::star::ui::dialogs::FilePickerEvent
 const&) + 29
10  libsfx.dylib0x00010d78715d 
sfx2::FileDialogHelper_Impl::fileSelectionChanged(com::sun::star::ui::dialogs::FilePickerEvent
 const&) + 45
11  fps_aqua.uno.dylib  0x0001429242a0 0x142917000 + 53920
12  com.apple.AppKit0x7fff236752f5 -[NSSavePanel 
observeValueForKeyPath:ofObject:change:context:] + 562
13  com.apple.Foundation0x7fff2119bab8 
NSKeyValueNotifyObserver + 327
14  com.apple.Foundation0x7fff21262e45 NSKeyValueDidChange 
+ 431
15  com.apple.Foundation0x7fff21303539 
NSKeyValueDidChangeWithPerThreadPendingNotifications + 146
16  com.apple.ViewBridge0x7fff2703dd9b __41-[NSViewBridge 
setObject:forKey:withKVO:]_block_invoke + 360
17  com.apple.ViewBridge0x7fff270b8829 withHintInProgress + 
359
18  com.apple.ViewBridge0x7fff27035cb7 -[NSViewBridge 
setObject:forKey:withKVO:] + 641
19  com.apple.ViewBridge0x7fff27036e05 -[NSViewBridge 
nonLocalChangeInProgress:block:] + 230
20  com.apple.ViewBridge0x7fff27036b93 
-[NSRemoteViewMarshal exceptionSafeSetRemoteObject:forKey:withReply:] + 264
21  com.apple.ViewBridge0x7fff27036a47 
-[NSRemoteViewMarshal setRemoteObject:forKey:withReply:] + 56
22  com.apple.CoreFoundation0x7fff2041e56c __invoking___ + 140
23  com.apple.CoreFoundation0x7fff2041e410 -[NSInvocation 
invoke] + 303
24  com.apple.ViewBridge0x7fff27034b65 
__deferNSXPCInvocationOntoMainThread_block_invoke + 228
25  com.apple.ViewBridge0x7fff27027d34 
__wrapBlockWithVoucher_block_invoke + 37
26  com.apple.ViewBridge0x7fff27027a25 
__deferBlockOntoMainThread_block_invoke_2 + 352
27  com.apple.CoreFoundation0x7fff2043b5a2 
__CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
28  com.apple.CoreFoundation0x7fff2043b44c __CFRunLoopDoBlocks 
+ 437
29  com.apple.CoreFoundation0x7fff2043a7bd __CFRunLoopRun + 2582
30  com.apple.CoreFoundation0x7fff204396ce CFRunLoopRunSpecific 
+ 563
31  com.apple.HIToolbox 0x7fff286be6d0 
RunCurrentEventLoopInMode + 292
32  com.apple.HIToolbox 0x7fff286be4cc 
ReceiveNextEventCommon + 709
33  com.apple.HIToolbox 0x7fff286be1ef 
_BlockUntilNextEventMatchingListInModeWithFilter + 64
34  com.apple.AppKit  

Re: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)

[Jim Jagielski]

For me, the issue is whether it is, indeed, a code problem in 4.1.8 that 
requires fixes
and thus a 4.1.9 release, or whether it is a *build* problem, that implies that 
building
4.1.8 with a newer SDK will resolve the problem. AFAICT, that question is still 
unresolved.
What we DO know is that 4.2.0-dev works fine under Big Sur.

With that in mind, over the next week I may try building 4.1.8 but with various 
versions
of Xcode and macOS SDKs...

> On Dec 26, 2020, at 10:05 AM, Matthias Seidel  
> wrote:
> 
> Hi Jim,
> 
> Am 26.12.20 um 15:17 schrieb Jim Jagielski:
>> It is more than likely that we may need to release a 4.1.9 just to 
>> accommodate BigSur. However, AOO
>> is hardly unique in being an app that no longer works when someone upgrades 
>> to BigSur. The macOS
>> community is replete w/ such apps. I'm not using that as an excuse, but that 
>> is what it is.
> 
> More than once Apple did break something with an OS upgrade and fixed it
> with one of the next updates...
> 
> Let's see how macOS 11.2 (beta) behaves [1].
> 
> Regards,
> 
>Matthias
> 
> [1]
> https://www.macrumors.com/2020/12/17/apple-seeds-macos-big-sur-11-2-public-beta-1/
> 
>> 
>> 
>>> On Dec 25, 2020, at 5:02 AM, Jörg Schmidt  wrote:
>>> 
>>> Hello,
>>> 
>>> I had opened the thread "Does AOO 4.1.8 run under macOS Big Sur?" and it 
>>> was also diligently discussed there.
>>> But there seems to be no solution yet and at the same time the requests 
>>> from users who are practically not able to work anymore because AOO does 
>>> not work under BigSur continue.
>>> 
>>> 1.
>>> Is there any solution in sight?
>>> 
>>> 2.
>>> If not, shouldn't we at least publicly announce that AOO under MacOS 11.0 
>>> (BigSur) is currently not supported? 
>>> (This would give users the chance to wait with the update of MacOS to 
>>> version 11.0).
>>> 
>>> 
>>> Sorry, my point of view is only that of a supporter who supports users day 
>>> by day  (voluntarily in the community and professionally), I can't assess 
>>> the technical problems, but unfortunately I see that the current situation 
>>> is damaging our reputation.
>>> 
>>> 
>>> 
>>> greetings,
>>> Jörg
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)

[Matthias Seidel]

Hi Jim,

Am 26.12.20 um 15:17 schrieb Jim Jagielski:
> It is more than likely that we may need to release a 4.1.9 just to 
> accommodate BigSur. However, AOO
> is hardly unique in being an app that no longer works when someone upgrades 
> to BigSur. The macOS
> community is replete w/ such apps. I'm not using that as an excuse, but that 
> is what it is.

More than once Apple did break something with an OS upgrade and fixed it
with one of the next updates...

Let's see how macOS 11.2 (beta) behaves [1].

Regards,

   Matthias

[1]
https://www.macrumors.com/2020/12/17/apple-seeds-macos-big-sur-11-2-public-beta-1/

>
>
>> On Dec 25, 2020, at 5:02 AM, Jörg Schmidt  wrote:
>>
>> Hello,
>>
>> I had opened the thread "Does AOO 4.1.8 run under macOS Big Sur?" and it was 
>> also diligently discussed there.
>> But there seems to be no solution yet and at the same time the requests from 
>> users who are practically not able to work anymore because AOO does not work 
>> under BigSur continue.
>>
>> 1.
>> Is there any solution in sight?
>>
>> 2.
>> If not, shouldn't we at least publicly announce that AOO under MacOS 11.0 
>> (BigSur) is currently not supported? 
>> (This would give users the chance to wait with the update of MacOS to 
>> version 11.0).
>>
>>
>> Sorry, my point of view is only that of a supporter who supports users day 
>> by day  (voluntarily in the community and professionally), I can't assess 
>> the technical problems, but unfortunately I see that the current situation 
>> is damaging our reputation.
>>
>>
>>
>> greetings,
>> Jörg
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: How should we proceed with BigSur? (was: Does AOO 4.1.8 run under macOS Big Sur?)

[Jim Jagielski]

It is more than likely that we may need to release a 4.1.9 just to accommodate 
BigSur. However, AOO
is hardly unique in being an app that no longer works when someone upgrades to 
BigSur. The macOS
community is replete w/ such apps. I'm not using that as an excuse, but that is 
what it is.


> On Dec 25, 2020, at 5:02 AM, Jörg Schmidt  wrote:
> 
> Hello,
> 
> I had opened the thread "Does AOO 4.1.8 run under macOS Big Sur?" and it was 
> also diligently discussed there.
> But there seems to be no solution yet and at the same time the requests from 
> users who are practically not able to work anymore because AOO does not work 
> under BigSur continue.
> 
> 1.
> Is there any solution in sight?
> 
> 2.
> If not, shouldn't we at least publicly announce that AOO under MacOS 11.0 
> (BigSur) is currently not supported? 
> (This would give users the chance to wait with the update of MacOS to version 
> 11.0).
> 
> 
> Sorry, my point of view is only that of a supporter who supports users day by 
> day  (voluntarily in the community and professionally), I can't assess the 
> technical problems, but unfortunately I see that the current situation is 
> damaging our reputation.
> 
> 
> 
> greetings,
> Jörg
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org