Re: [E-devel] Apache OpenOffice 4.1.2 locks in Enlightenment 0.21.99.21605

[The Rasterman]

On Tue, 30 Aug 2016 04:22:00 -0700 Jose R R  said:

> Thanks for replying.
> 
> On Sun, Aug 28, 2016 at 11:27 PM, Carsten Haitzler 
> wrote:
> > On Sat, 27 Aug 2016 03:42:52 -0700 Jose R R  said:
> >
> >> Niltze [Hello], all!
> >>
> >> I've noticed that Enlightenment 0.17.x.y and 0.21.x.y GUI environment
> >> sometimes becomes locked upon mousing over icons in Apache OpenOffice
> >> 4.1.2.
> >>
> >> Notwithstanding, when I built Enlightenment 0.19.x.y and 0.20.xy, the
> >> locking issue disappeared and I thought it was resolved; but then issue
> >> reappeared once more in Enlightenment 0.21.x.y. I have to CTRL + ALT and
> >> press F1, F2, etc. to get another shell, login and restart XDM.
> >>
> >> Any feedback would be greatly appreciated.
> >
> > is e stuck - has it crashed? do you get a crashdump?
> E21 must be 'stuck' -- as I can't locate a 'crashdump'.
> 
> Please see pic at:
> <
> https://metztli.it/blog/media/blogs/ixiptli/quick-uploads/p125/e21_apacheoo_issue.png?mtime=1472553272
> >
> >
> > https://www.enlightenment.org/docs-efl-debug
> I will try this as time avails. Thank you.
> >
> > you can also find if it isnt crashing by forcing a segv and seeing where
> > the bt says it was stuck:
> >
> > killall -SEGV enlightenment
> I have executed above directive and Recovery option seems useful -- as
> I don't have to restart XDM, thus potentially preserving existing
> sessions and/or data/work; again, please snapshot above and if
> interested for context, post entry:
> <
> https://metztli.it/blog/index.php/ixiptli/eterm-and-enlightenment-window-manager
> >

so when you sent a SEGV to enlightenment... after that did you have
~/.e-crashdump.txt ? because you now FORCED it to crash, thus a crashdump
should be produced. this may not work if yama ptrace is enabled.

sudo sysctl -w kernel.yama.ptrace_scope=0


will turn that off. you need gdb installed too. also when compiling e and efl
you need your CFFLAGS to contain "-g" to enable gdb debug symbols of course.

export CFLAGS="-g -O2 -march=native -fvisibility=hidden -ffast-math"

for example before you compile.

remember - e APPENDS to the crashdump file every crash, so the most recent
crash is the last bt set - grep for "pause" to find the crash points. :)

so crashdump file after this? that'll tell use what's up. hopefully. or give us
another thing to follow.

p.s.

btw - why eterm? eterm is fine and all but its an old old old school terminal
still using xlib directly etc. terminology is the modern terminal that uses efl
et. (runs even on OSX too) that has real bells and whistles (videos in the bg,
inline image display, tabs AND splits etc.)? and it does PROPER transparency -
no "esetroot" with fake "lets copy parts of the background pixmap into app
window to make it look transparent but only with a wallpaper".

> >
> > --
> > - Codito, ergo sum - "I code, therefore I am" --
> > The Rasterman (Carsten Haitzler)ras...@rasterman.com
> >
> 
> 
> Best Professional Regards.
> 
> -- 
> Jose R R
> http://metztli.it
> -
> Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
> -
> from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
> 


-- 
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carsten Haitzler)ras...@rasterman.com


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

Re: dmake

[Don Lewis]

On 29 Aug, Gav wrote:
> On Sun, Aug 28, 2016 at 4:42 PM, Don Lewis  wrote:
> 
>> On 27 Aug, Pedro Giffuni wrote:
>> >> On 28 Aug, Gav wrote:
>> >>> when did you try that last Don?
>> >>>
>> >>> That url comes up oops 404
>> >>
>> >> I last tried that in the last few weeks, but have been using a cached
>> >> copy since then.
>> >>
>> >> This page lists lots of mirrored copies:
>> >> 
>> >>
>> >> It looks like development has moved to GitHub:
>> >> 
>> >
>> > and this is exactly what I was going to say ...
>> >
>> > With the demise of Google code the project moved to github and is under
>> > a new maintainer (FreeBSD uses the new github version).
>> >
>> > Perhaps we should mirror dmake-4.12.2, which was the last version
>> > released on apache-extras, on sourceforge and update the build link.
>>
>> That seems like the easiest thing to do.  I tried downloading from
>> GitHub and ran into a complication.  The tarfile name downloaded from
>> github is DMAKE_4_12_2_2.tar.gz, but it unpacks into the directory
>> dmake-DMAKE_4_12_2_2 and bootstrap can't cope with that.  I could fix
>> bootstrap, but that only helps trunk.  Nothing could be done to fix
>> 4.1.2 other than re-rolling the tarball.
>>
>> At least for now, the new dmake download URL is:
>> > >
>>
> 
> Thanks Don, that works fine.

The Windows buildbot still needs the dmake fix.


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

RE: [REPORT] CVE-2016-1513 Security Advisory

[Dennis E. Hamilton]

> -Original Message-
> From: Rodrigo Marin-Rogers [mailto:rodmarog...@gmail.com]
> Sent: Tuesday, August 30, 2016 16:44
> To: annou...@openoffice.apache.org; orc...@apache.org
> Subject: Re: [REPORT] CVE-2016-1513 Security Advisory
> 
> Dear Dennis:
> 
>  The hotfix download and installation process is quite long and
> complicated for the general users who are not developers.  Why don't you
> just create a new version with the hotfix already included much easier
> to download.  I've lost several documents that showed as corrupt when I
> tried to reopen them,  then I suspected that something like this was
> happening, so I deleted them from my computer.
> 
>   Thank you for your kind concern,  Please let me know if you create
> such new version!
> 
> Truly yours,
> 
> 
> 
>   Rodrigo.
[orcmid] 

Thank you for the feedback, Rodrigo.

It may be months before there is a full update for Apache OpenOffice.  The 
hotfixes are for those able to make use of them in the meantime.  The reason we 
make the README files available to be read first is so folks can calibrate 
whether they want to go through it or not.

With regard to your document corruption experience, that is not the behavior 
associated with the CVE-2016-1513 vulnerability.  They were probably damaged in 
the Save process.  That is not unknown.

 - Dennis
> 
> 
> On Tue, Aug 30, 2016 at 9:46 AM, Dennis E. Hamilton   > wrote:
> 
> 
>   [BCC PMC]
> 
>   Today, Version 2.0 of the Advisory for CVE-2016-1513  1513>  has been issued.
> 
>   There is now general availability of a Hotfix that can be
> downloaded and applied to installations of Apache OpenOffice 4.1.2.  The
> Hotfix details can be found at
>     >.
> 
>   Please review the README instructions before deciding to download
> and apply the Hotfix.
[ ... ]



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

RE: Updated Security Advisory: CVE-2016-1513 Memory Corruption Vulnerability (Impress Presentations)

[Dennis E. Hamilton]

Thanks for the feedback, Don.

Please provide more details (and copy the public dev@ user list) so we can 
narrow in on the problem.

Which version of Windows 10 are you running?  Windows 10 Home or Windows 10 Pro?

Are you following the steps in the README file for the Windows 4.1.2-patch1 
Hotfix?

By "Open the Patch" do you mean the .zip file or do you mean attempting to run 
the APPLY .bat file?

 - Dennis

> -Original Message-
> From: Don Rake [mailto:raked...@yahoo.com]
> Sent: Tuesday, August 30, 2016 14:12
> To: annou...@openoffice.apache.org; orc...@apache.org
> Subject: Re: Updated Security Advisory: CVE-2016-1513 Memory Corruption
> Vulnerability (Impress Presentations)
> 
> Windows 10 won't let me open the patch.
> 
> 
[ ... ]



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

New Version of Openoffice

[andschlick1]

Dear OpenOffice Team,
I have a question is the OpenOffice dead or is a new version in development
in advance Many thanks

Best regards
Andreas Schlick

Andreas Schlick
Wernleitenstraße  7 
83313 Siegsdorf

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

Re: [E-devel] Apache OpenOffice 4.1.2 locks in Enlightenment 0.21.99.21605

[Pau Espin Pedrol]

Hi,

Recently I also noticed that E hanged (no more graphic interaction or
refreshed) a few times randomly while opening a link menu in firefox by
right-clicking on a link. I think it is more probable to hit the issue if
the page is heavy and is still finishing loading.

I guess it may be the same issue.

I'm using enlightenment-0.20.10-1 and efl-1.17.2-1 from Archlinux
Graphic card (lspci): Intel Corporation Haswell-ULT Integrated Graphics
Controller (rev 0b)
xf86-video-intel is not installed, so I guess I'm using generic KMS.

Regards,
Pau Espin Pedrol

2016-08-30 13:22 GMT+02:00 Jose R R :

> Thanks for replying.
>
> On Sun, Aug 28, 2016 at 11:27 PM, Carsten Haitzler 
> wrote:
> > On Sat, 27 Aug 2016 03:42:52 -0700 Jose R R  said:
> >
> >> Niltze [Hello], all!
> >>
> >> I've noticed that Enlightenment 0.17.x.y and 0.21.x.y GUI environment
> >> sometimes becomes locked upon mousing over icons in Apache OpenOffice
> 4.1.2.
> >>
> >> Notwithstanding, when I built Enlightenment 0.19.x.y and 0.20.xy, the
> >> locking issue disappeared and I thought it was resolved; but then issue
> >> reappeared once more in Enlightenment 0.21.x.y. I have to CTRL + ALT and
> >> press F1, F2, etc. to get another shell, login and restart XDM.
> >>
> >> Any feedback would be greatly appreciated.
> >
> > is e stuck - has it crashed? do you get a crashdump?
> E21 must be 'stuck' -- as I can't locate a 'crashdump'.
>
> Please see pic at:
> < https://metztli.it/blog/media/blogs/ixiptli/quick-uploads/
> p125/e21_apacheoo_issue.png?mtime=1472553272
> >
> >
> > https://www.enlightenment.org/docs-efl-debug
> I will try this as time avails. Thank you.
> >
> > you can also find if it isnt crashing by forcing a segv and seeing where
> the bt
> > says it was stuck:
> >
> > killall -SEGV enlightenment
> I have executed above directive and Recovery option seems useful -- as
> I don't have to restart XDM, thus potentially preserving existing
> sessions and/or data/work; again, please snapshot above and if
> interested for context, post entry:
> < https://metztli.it/blog/index.php/ixiptli/eterm-and-
> enlightenment-window-manager
> >
>
> >
> > --
> > - Codito, ergo sum - "I code, therefore I am" --
> > The Rasterman (Carsten Haitzler)ras...@rasterman.com
> >
>
>
> Best Professional Regards.
>
> --
> Jose R R
> http://metztli.it
> 
> -
> Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
> 
> -
> from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy
> way!
>
> 
> --
> ___
> enlightenment-devel mailing list
> enlightenment-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>

[NOMINATION REQUEST] Next Chair of AOO Project Management Committee

[Dennis E. Hamilton]

[BCC to PMC]

I am now ready to begin the Chair nomination process.  Because of delays, the 
next change of Chair has moved to October 19.

REQUEST FOR NOMINATIONS

This message starts the nomination process for the next Chair for the Apache 
OpenOffice PMC.  The term of the next Chair will start on 2016-10-19 and my 
resignation will be effective on that date.

Members of the PMC can nominate themselves, expressing their willingness to 
serve.

You can also place the names of others in nomination.  Those individuals must 
accept the nomination to be considered as eligible.

The identification of Nominees will end on Tuesday, 2016-09-13.  The nature of 
subsequent discussion will depend on the number of Nominees.


TIMELINE

Here's the new timeline that has the replacement be ratified by the October 19, 
2016 meeting of the ASF Board:

2016-10-19 ASF Board Meeting - Board rules on the resolution to install the new 
Chair.

2016-10-12 (latest) Resolution from AOO PMC to accept the new Chair is added to 
the Agenda for the 2016-10-19 Board Meeting (latest possible date)

2016-10-05 (latst) [RESULT][VOTE] on election of next Chair is reported.

2016-09-28 (latest) [VOTE] on election of next Chair begins.  This could be by 
lazy consensus if there is already a single acceptable candidate.

2016-09-14 [NOMINEE DISCUSSION] process begins formally and any discussion on 
and among candidates willing to serve takes place.

2016-08-30 [NOMINATIONS] Individuals are recommended or offer
themselves, indicate their availability to serve for at least one
single-year term, and also have their own questions answered.

 - Dennis


> -Original Message-
> From: Dennis E. Hamilton [mailto:orc...@apache.org]
> Sent: Sunday, July 31, 2016 20:44
> To: dev@openoffice.apache.org
> Subject: [DISCUSS] Process: Elect Next Chair of AOO Project Management
> Committee
> 
> [BCC to PMC]
> 
> [From the Chair]
> It is time for the selection of the next chair for the Apache OpenOffice
> Project Management Committee.
> 
> INCUMBENT CHAIR
> 
> I officially began my term on the third Wednesday of September, 2015. My
> commitment was to serve for one full year and then be replaced. I will
> complete that one-year term and step down on the third Wednesday of
> September, 2016.  My successor will then be established by the Apache
> Software Foundation Board.
> 
> Although I will continue as a member of the Project Management Committee
> and as a contributor to the Apache OpenOffice project, I am not
> available to continue as Chair beyond the 2016-09-21 ASF Board Meeting.
> I am available to assist the incoming Chair in any manner required for
> successfully transferring duties of the Chair.
> 
> CHAIR ELECTION
> 
> Based on previous practice, nomination, discussion, and election periods
> are held.  Here is my proposed time-line, from endgame backwards:
> 
> 2016-09-21 ASF Board Meeting - Board rules on the resolution to install
> the new Chair.
> 
> 2016-09-14 Resolution from AOO PMC to accept the new Chair is added to
> the Agenda for the 2016-09-21 Board Meeting (latest possible date)
> 
> 2016-09-07 [RESULT][VOTE] on election of next Chair is reported.
> 
> 2016-08-31 [VOTE] on election of next Chair begins (with allowance for
> US Holiday weekend).  This could be by lazy consensus if there is
> already a single acceptable candidate.
> 
> 2016-08-17 [NOMINEE DISCUSSION] process begins formally and any
> discussion on and among candidates willing to serve takes place.
> 
> 2016-08-03 [NOMINATIONS] Individuals are recommended or offer
> themselves, indicate their availability to serve for at least one
> single-year term, and also have their own questions answered.
> 
> This process can be accelerated where it is seen that discussions have
> quieted and consensus for moving forward is evident.
> 
>  - Dennis
> 
> 
> -
> 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: compiler warnings when building OpenOffice

[Don Lewis]

On 30 Aug, Don Lewis wrote:
> On 30 Aug, Kay Schenk wrote:
>> 
>> 
>> On 08/29/2016 04:14 PM, Don Lewis wrote:

>>> A couple -Wtautological-undefined-compare warnings:
>>> 
>>> warning: reference cannot be bound to dereferenced null pointer in 
>>> well-defined C++ code; comparison may be assumed to always evaluate to 
>>> false [-Wtautologica
>>> l-undefined-compare]
>>> if ( == NULL) {
>>>  ^
>> 
>> This one is apparently an old holdoever from C and not recommended
>> currently...
>> 
>> See. e.g:
>> http://stackoverflow.com/questions/17772103/can-i-use-if-pointer-instead-of-if-pointer-null
>> 
>> It probably needs an update to accomplish what it's trying to do.
>> 
>> 
>>> 
>>> warning: 'this' pointer cannot be null in well-defined C++ code; comparison 
>>> may be assumed to always evaluate to false [-Wtautological-undefin
>>> ed-compare]
>>>   if(this == 0 || this == ) {
>>>  ^~~~~
>>> 
>> 
>> Same here...
> 
> nullptr is a c++11 thing and is not supported by older compilers.
> 
> When I upgraded one of the bundled packages (nss?) I found it had some
> test code that used nullptr that didn't compille on many of our
> platforms.  I had to disconnect the tests from the build.
> 
> The warnings are about things that can't be null.  In the first case if
> you have a reference to another variable, then the address of that
> variable can't be null.  In the second case, this could only be null if
> you call a method on a null object.
> 
> One of the bits of code that I looked at for the first error looked
> suspicious.  It looks like it is passing *ptr as a reference parameter.
> I'm not sure that's legal, and then the question is what happens if ptr
> is null?  Other calls to the same function were passing a regular
> variable by reference.  The appropriate fix in this case my be to create
> a variant function that accepts a pointer and checks for NULL.  Rather
> than checking  == NULL.

Hmn, this is what I was afraid of.  The following code compiles without
any warnings or errors:

#include 
 
void 
func(int )
{
fprintf(stderr, "%p\n", );
}
 
int 
main(void)
{
int i, *p1, *p2;

i = 42;
p1 = 
p2 = NULL;
 
func(*p1);
func(*p2);
}

Running it gives the following output:

0x7fffea7c
0x0

So basically it is allowing *p2 to be dereferenced even though it is
NULL, and the address of the reference variable inside func() is 0.

I guess this isn't well defined C++ code ...




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

Re: compiler warnings when building OpenOffice

[Don Lewis]

On 30 Aug, Kay Schenk wrote:
> 
> 
> On 08/29/2016 04:14 PM, Don Lewis wrote:
>> When building OpenOffice trunk revsion r1758161 as a FreeBSD port on
>> FreeBSD 12.0-CURRENT with clang 3.8.0, I get the following warnings.
>> I'm mostly interested in the OpenOffice code and not the bundled
>> external code, so I specifically built the FreeBSD port it uses
>> --with-system-foo extensively which minimizes the compilation of third
>> party code.  The total number of warnings is 5105.
>> 
>> 1175 -Wtautological-undefined-compare
>>  949 -Wunused-private-field
>>  660 -Wshift-negative-value
>>  391 -Wunused-parameter
>>  362 -Wunused-const-variable
>>  312 -Woverloaded-virtual
>>  177 -Wunused-variable
>>  116 -Winfinite-recursion
>>  109 -Wlogical-op-parentheses
>>   93 -Wsign-compare
>>   76 -Wdelete-non-virtual-dtor
>>   72 -Wint-to-void-pointer-cast
>>   63 -Wshadow
>>   55 -Wunused-function
>>   41 -Wformat
>>   36 -Wreturn-type-c-linkage
>>   30 -Wchar-subscripts
>>   27 -Wdeprecated-declarations
>>   26 -Wundefined-bool-conversion
>>   26 -Wsizeof-pointer-memaccess
>>   26 -Wformat-security
>>   24 -Wunused-local-typedef
>>   22 -Wmacro-redefined
>>   21 -Wswitch
>>   20 -Wbitwise-op-parentheses
>>   18 -Winvalid-source-encoding
>>   13 -Wuninitialized
>>   11 -Wtautological-compare
>>   11 -Wlogical-not-parentheses
>>   11 -Wdangling-else
>>9 -Wmismatched-new-delete
>>8 -Wimplicit-function-declaration
>>8 -Wheader-guard
>>8 -Wcomment
>>7 -Wtautological-constant-out-of-range-compare
>>7 -Wself-assign
>>6 -Wunused-value
>>6 -Wunneeded-internal-declaration
>>6 -Wtautological-pointer-compare
>>6 -Wpointer-bool-conversion
>>6 -Wparentheses-equality
>>6 -Wdynamic-class-memaccess
>>6 -Wconstant-conversion
>>5 -Wpointer-sign
>>4 -Wnull-conversion
>>3 -Wunsequenced
>>3 -Wreorder
>>3 -Wknr-promoted-parameter
>>3 -Wint-to-pointer-cast
>>2 -Wstrncat-size
>>2 -Wstring-compare
>>2 -Wsometimes-uninitialized
>>2 -Wconstant-logical-operand
>>2 -Warray-bounds
>>1 -Wunused-comparison
>>1 -Wunknown-pragmas
>>1 -Wstring-plus-int
>>1 -Wpotentially-evaluated-expression
>>1 -Wnon-literal-null-conversion
>>1 -Wmismatched-tags
>>1 -Wincompatible-pointer-types-discards-qualifiers
>>1 -Wimplicit-int
>>1 -Wignored-qualifiers
>>1 -Wformat-extra-args
>>1 -Wcompare-distinct-pointer-types
>>1 -Wc++11-compat-deprecated-writable-strings
>> 
>> 
>> A couple -Wtautological-undefined-compare warnings:
>> 
>> warning: reference cannot be bound to dereferenced null pointer in 
>> well-defined C++ code; comparison may be assumed to always evaluate to false 
>> [-Wtautologica
>> l-undefined-compare]
>> if ( == NULL) {
>>  ^
> 
> This one is apparently an old holdoever from C and not recommended
> currently...
> 
> See. e.g:
> http://stackoverflow.com/questions/17772103/can-i-use-if-pointer-instead-of-if-pointer-null
> 
> It probably needs an update to accomplish what it's trying to do.
> 
> 
>> 
>> warning: 'this' pointer cannot be null in well-defined C++ code; comparison 
>> may be assumed to always evaluate to false [-Wtautological-undefin
>> ed-compare]
>>   if(this == 0 || this == ) {
>>  ^~~~~
>> 
> 
> Same here...

nullptr is a c++11 thing and is not supported by older compilers.

When I upgraded one of the bundled packages (nss?) I found it had some
test code that used nullptr that didn't compille on many of our
platforms.  I had to disconnect the tests from the build.

The warnings are about things that can't be null.  In the first case if
you have a reference to another variable, then the address of that
variable can't be null.  In the second case, this could only be null if
you call a method on a null object.

One of the bits of code that I looked at for the first error looked
suspicious.  It looks like it is passing *ptr as a reference parameter.
I'm not sure that's legal, and then the question is what happens if ptr
is null?  Other calls to the same function were passing a regular
variable by reference.  The appropriate fix in this case my be to create
a variant function that accepts a pointer and checks for NULL.  Rather
than checking  == NULL.



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

Re: compiler warnings when building OpenOffice

[Kay Schenk]

On 08/29/2016 04:14 PM, Don Lewis wrote:
> When building OpenOffice trunk revsion r1758161 as a FreeBSD port on
> FreeBSD 12.0-CURRENT with clang 3.8.0, I get the following warnings.
> I'm mostly interested in the OpenOffice code and not the bundled
> external code, so I specifically built the FreeBSD port it uses
> --with-system-foo extensively which minimizes the compilation of third
> party code.  The total number of warnings is 5105.
> 
> 1175 -Wtautological-undefined-compare
>  949 -Wunused-private-field
>  660 -Wshift-negative-value
>  391 -Wunused-parameter
>  362 -Wunused-const-variable
>  312 -Woverloaded-virtual
>  177 -Wunused-variable
>  116 -Winfinite-recursion
>  109 -Wlogical-op-parentheses
>   93 -Wsign-compare
>   76 -Wdelete-non-virtual-dtor
>   72 -Wint-to-void-pointer-cast
>   63 -Wshadow
>   55 -Wunused-function
>   41 -Wformat
>   36 -Wreturn-type-c-linkage
>   30 -Wchar-subscripts
>   27 -Wdeprecated-declarations
>   26 -Wundefined-bool-conversion
>   26 -Wsizeof-pointer-memaccess
>   26 -Wformat-security
>   24 -Wunused-local-typedef
>   22 -Wmacro-redefined
>   21 -Wswitch
>   20 -Wbitwise-op-parentheses
>   18 -Winvalid-source-encoding
>   13 -Wuninitialized
>   11 -Wtautological-compare
>   11 -Wlogical-not-parentheses
>   11 -Wdangling-else
>9 -Wmismatched-new-delete
>8 -Wimplicit-function-declaration
>8 -Wheader-guard
>8 -Wcomment
>7 -Wtautological-constant-out-of-range-compare
>7 -Wself-assign
>6 -Wunused-value
>6 -Wunneeded-internal-declaration
>6 -Wtautological-pointer-compare
>6 -Wpointer-bool-conversion
>6 -Wparentheses-equality
>6 -Wdynamic-class-memaccess
>6 -Wconstant-conversion
>5 -Wpointer-sign
>4 -Wnull-conversion
>3 -Wunsequenced
>3 -Wreorder
>3 -Wknr-promoted-parameter
>3 -Wint-to-pointer-cast
>2 -Wstrncat-size
>2 -Wstring-compare
>2 -Wsometimes-uninitialized
>2 -Wconstant-logical-operand
>2 -Warray-bounds
>1 -Wunused-comparison
>1 -Wunknown-pragmas
>1 -Wstring-plus-int
>1 -Wpotentially-evaluated-expression
>1 -Wnon-literal-null-conversion
>1 -Wmismatched-tags
>1 -Wincompatible-pointer-types-discards-qualifiers
>1 -Wimplicit-int
>1 -Wignored-qualifiers
>1 -Wformat-extra-args
>1 -Wcompare-distinct-pointer-types
>1 -Wc++11-compat-deprecated-writable-strings
> 
> 
> A couple -Wtautological-undefined-compare warnings:
> 
> warning: reference cannot be bound to dereferenced null pointer in 
> well-defined C++ code; comparison may be assumed to always evaluate to false 
> [-Wtautologica
> l-undefined-compare]
> if ( == NULL) {
>  ^

This one is apparently an old holdoever from C and not recommended
currently...

See. e.g:
http://stackoverflow.com/questions/17772103/can-i-use-if-pointer-instead-of-if-pointer-null

It probably needs an update to accomplish what it's trying to do.


> 
> warning: 'this' pointer cannot be null in well-defined C++ code; comparison 
> may be assumed to always evaluate to false [-Wtautological-undefin
> ed-compare]
>   if(this == 0 || this == ) {
>  ^~~~~
> 

Same here...

> I'd like to just nuke these comparisions.
> 
> 
> To fix the -Wunused-private-field private field warnings, I'd prefer to
> delete them, but that would have the side effect of breaking the ABI if
> an extensions use the class constructor.  The alternative would be to
> mark them unused.  I don't think there are actually many cases of this.
> The same warning gets generated anytime the header is included.
> 
> 
> In the case of -Wshift-negative-value, result of shifting negative
> values is undefined.  This is generally fixable by using unsigned values
> instead.
> 
> 
> I'm not sure what to about -Wunused-parameter.  It's probably a case by
> case situation where it may sometimes make sense to have a variant
> function that doesn't have that parameter and modify the callers.  The
> alternative is to mark the argument as unused.  I haven't really
> examined any of these in detail.
> 
> 
> For -Wunused-const-variable and -Wunused-variable, I propose just
> deleting them unless they are referenced by conditionally compiled code,
> in which case I would make the variable declaration conditional as well.
> 
> 
> I fixed one other case of -Winfinite-recursion.  I'm pretty sure this is
> just one error, but it is contained in a header.
> 
> 
> I think -Wshadow warnings should be fixed by renaming the variable.
> 
> 
> I don't recall ever seeing -Wunused-function scroll by, but if functions
> are totally unused, they should be deleted.
> 
> 
> The parentheses warnings should just get fixed.
> 
> 
> This is an example -Wdelete-non-virtual-dtor warning:
> 
> warning: delete called on non-final 'RscError' that has virtual functions but 
> non-virtual destructor [-Wdelete-non-virtual-dtor]
> delete pErrHdl;
> 
> My C++ book says that non-virtual destructors are bad generally bad.  We
> also compile 

Re: gstreamer

[Kay Schenk]

On Tue, Aug 30, 2016 at 12:18 AM, Andrea Pescetti 
wrote:

> Gav wrote:
>
>> "checking whether to build the GStreamer media backend... checking for
>> GSTREAMER... no
>> configure: error: requirements to build the GStreamer media backend not
>> met. Do not use --enable-gstreamer or install the missing packages
>>
>
> Hi Gavin, this won't help you with GStreamer since I checked and it is not
> immediately clear that it would help, but I suggest to use -and update if
> needed; we can of course create a wiki account for you- the following
> resources:
>
> https://wiki.openoffice.org/wiki/Documentation/Building_Guid
> e_AOO/Step_by_step
> a section for Ubuntu 14.04 with all needed packages.
>
> https://wiki.openoffice.org/wiki/Ubuntu_Build_Instructions
> Outdated, but still contain useful hints.
>
> http://svn.apache.org/viewvc/openoffice/devtools/build-scrip
> ts/4.1.2/unxlngix6/
> Our build scripts for 4.1.2. These configure options are for a release
> build, but ideally we want this to succeed on the buildbot. Languages can
> be left out (for example, the Windows buildbot only uses en and de) and the
> package formats can be reduced too, but these should be the reference
> options.
>
> And thanks a lot for this work. It won't help us with building releases,
> but it will make buildbot maintenance easier for both Infra and the project.
>
> Regards,
>   Andrea.
>

​Gavin --

As I don't see any information in the wiki links Andrea provided directly
pertaining to gstreamer, can you give us an accounting of what IS installed
vis a vis gstreamer on this system? It could be that our configure script
needs some tweaking.​

​ We use PKG_CONFIG exclusively toe "find" packs on systems, and sometimes
that does not work for all installed packages.​



-- 
--
Kay Schenk
Apache OpenOffice

"Things work out best for those who make
 the best of the way things work out."
   -- John Wooden

Re: gstreamer

[Kay Schenk]

On Mon, Aug 29, 2016 at 9:41 PM, Gav  wrote:

>
>
> On Tue, Aug 30, 2016 at 2:56 AM, Kay Schenk  wrote:
>
>>
>> On Mon, Aug 29, 2016 at 3:08 AM, Gav  wrote:
>>
>>> Hi All,
>>>
>>> I have a successful build on our Ubuntu 14.04 in prelim
>>> tests before we migrate. That's the good news.
>>>
>>> As per subject; I could not get gstreamer to work so chose to
>>> disable it to get on with the rest of the build.
>>>
>>> I could not find a suitable ubuntu package to install is the issue.
>>>
>>> Can someone enlighten me please so I can enable gstreamer
>>> again.
>>>
>>> Thanks
>>>
>>> Gav...
>>>
>>
>> ​Maybe here?
>>
>> ​http://packages.ubuntu.com/trusty/libgstreamer0.10-0
>>
>
> Great, that works fine, gstreamer enabled again.
>
> btw I've been using system Java 7 1.7.0_111 and works fine, but do we
> want to keep using this? (I'd think so)
>

​Absolutely! And I was going to tell you we wanted to update to Java 1.7.
​


>
> Gav...
>
>
>>
>> I did see information that  Ubuntu may already use gstreamer (libs?) in
>> some form?
>> ​I'm not sure what to tell you so something doesn't get overwritten.​
>>
>>
>> --
>> --
>> MzK
>>
>> "God helps those that help themselves."
>>   -- popular adage
>>
>>
>


-- 
--
MzK

"God helps those that help themselves."
  -- popular adage

RE: [PROBLEM] General Availability of ApacheOpenOffice 4.1.2-patch1 Hotfixes

[Dennis E. Hamilton]

> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Monday, August 29, 2016 13:27
> To: dev@openoffice.apache.org
> Subject: Re: [PROBLEM] General Availability of ApacheOpenOffice 4.1.2-
> patch1 Hotfixes
> 
> Am 08/29/2016 04:39 PM, schrieb Dennis E. Hamilton:
> > There is a problem with the README files for Windows not being
> populated to archive.apache.org.
> >
> > I suspect it has to do with the file name beginning with README, since
> the files such as Linux32.README.txt populated to the archive area just
> fine.
> >
> > To rename the files everywhere is going to be a serious regression
> risk.
> >
> > Instead, I am going to copy the three Windows README files (en-US, de,
> and nl) to openoffice.org in the folder for security bulletins.  They
> will be linked to directly from hotfix.html.
> >
> > The hotfix.html file will be updated to locate those README files in
> that location once they are present.
> >
> > Then I will complete this long and winding road with the updated
> advisory.
[orcmid] 

Done.  General availability announcement now going to the lists.

 - Dennis
> 
> great. However, if you need some more help, just let us know.
> 
> Marcus
> 
> 
> 
> >> -Original Message-
> >> From: Dennis E. Hamilton [mailto:orc...@apache.org]
> >> Sent: Friday, August 26, 2016 10:28
> >> To: dev@openoffice.apache.org
> >> Cc: l...@openoffice.apache.org; q...@openoffice.apache.org
> >> Subject: RE: [PROPOSAL] General Availability of ApacheOpenOffice
> 4.1.2-
> >> patch1 Hotfixes
> >>
> >> [BCC to PMC, FYI to L10N and QA.]
> >>
> >> The 4.2.1-patch1 release repository is now populated with the only
> >> localizations that we have: English (en-US) and German (de) for all
> >> platforms plus the additional Nederland (nl) for Windows.  The
> >> localizations took until yesterday, 2016-08-25, to be completed.
> >>
> >> Propagation to the archive site has begun and will probably not be
> >> complete for another 24 hours.  Meanwhile, an updated CVE-2016-1513
> will
> >> be prepared.  The update will be posted when the archive is stable,
> >> along with notification to dev@ and users@.  Those actions will
> provide
> >> the general availability of the Hotfix.
> >>
> >> While minor blemishes may remain, this material will be kept stable
> as
> >> is unless a serious defect is brought to our attention.  Cosmetic
> >> matters are appropriate to save for whenever we need to do this
> again.
> >>
> >> One lesson: Localizations should not hold up release in the future.
> >> Localizations not available during the initial dev QA and review
> period
> >> should not stop the train.  Supplemental localizations are always
> >> possible.  That will likely always be the case when a hotfix is made
> >> available along with an initial vulnerability disclosure and
> advisory.
> >>
> >>   - Dennis
> >>
> > [ ... ]
> 
> -
> 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: [REPORT] CVE-2016-1513 Security Advisory

[Dennis E. Hamilton]

[BCC PMC]

Today, Version 2.0 of the Advisory for CVE-2016-1513 has been issued.

There is now general availability of a Hotfix that can be downloaded and 
applied to installations of Apache OpenOffice 4.1.2.  The Hotfix details can be 
found at 
.

Please review the README instructions before deciding to download and apply the 
Hotfix.

 - Dennis

> -Original Message-
> From: Dennis E. Hamilton [mailto:orc...@apache.org]
> Sent: Thursday, July 21, 2016 09:43
> To: dev@openoffice.apache.org
> Subject: [REPORT] CVE-2016-1513 Security Advisory
> 
> [BCC AOO Users; BCC AOO PMC]
> 
> Today, advisory CVE-2016-1513 has been published with regard to
> disclosure of a potentially-exploitable defect in crafted Impress
> documents.  The advisory can be found at
> .
> 
> There is no updated release at this time.  There is action underway.  We
> can now discuss those actions and also seek assistance in the wider
> community.
> 
[ ... ]


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

ApacheCon Seville CFP closes September 9th

[Rich Bowen]

It's traditional. We wait for the last minute to get our talk proposals
in for conferences.

Well, the last minute has arrived. The CFP for ApacheCon Seville closes
on September 9th, which is less than 2 weeks away. It's time to get your
talks in, so that we can make this the best ApacheCon yet.

It's also time to discuss with your developer and user community whether
there's a track of talks that you might want to propose, so that you
have more complete coverage of your project than a talk or two.

For Apache Big Data, the relevant URLs are:
Event details:
http://events.linuxfoundation.org/events/apache-big-data-europe
CFP:
http://events.linuxfoundation.org/events/apache-big-data-europe/program/cfp

For ApacheCon Europe, the relevant URLs are:
Event details: http://events.linuxfoundation.org/events/apachecon-europe
CFP: http://events.linuxfoundation.org/events/apachecon-europe/program/cfp

This year, we'll be reviewing papers "blind" - that is, looking at the
abstracts without knowing who the speaker is. This has been shown to
eliminate the "me and my buddies" nature of many tech conferences,
producing more diversity, and more new speakers. So make sure your
abstracts clearly explain what you'll be talking about.

For further updated about ApacheCon, follow us on Twitter, @ApacheCon,
or drop by our IRC channel, #apachecon on the Freenode IRC network.

-- 
Rich Bowen
WWW: http://apachecon.com/
Twitter: @ApacheCon

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

Re: [E-devel] Apache OpenOffice 4.1.2 locks in Enlightenment 0.21.99.21605

[Jose R R]

Thanks for replying.

On Sun, Aug 28, 2016 at 11:27 PM, Carsten Haitzler  wrote:
> On Sat, 27 Aug 2016 03:42:52 -0700 Jose R R  said:
>
>> Niltze [Hello], all!
>>
>> I've noticed that Enlightenment 0.17.x.y and 0.21.x.y GUI environment
>> sometimes becomes locked upon mousing over icons in Apache OpenOffice 4.1.2.
>>
>> Notwithstanding, when I built Enlightenment 0.19.x.y and 0.20.xy, the
>> locking issue disappeared and I thought it was resolved; but then issue
>> reappeared once more in Enlightenment 0.21.x.y. I have to CTRL + ALT and
>> press F1, F2, etc. to get another shell, login and restart XDM.
>>
>> Any feedback would be greatly appreciated.
>
> is e stuck - has it crashed? do you get a crashdump?
E21 must be 'stuck' -- as I can't locate a 'crashdump'.

Please see pic at:
< 
https://metztli.it/blog/media/blogs/ixiptli/quick-uploads/p125/e21_apacheoo_issue.png?mtime=1472553272
>
>
> https://www.enlightenment.org/docs-efl-debug
I will try this as time avails. Thank you.
>
> you can also find if it isnt crashing by forcing a segv and seeing where the 
> bt
> says it was stuck:
>
> killall -SEGV enlightenment
I have executed above directive and Recovery option seems useful -- as
I don't have to restart XDM, thus potentially preserving existing
sessions and/or data/work; again, please snapshot above and if
interested for context, post entry:
< 
https://metztli.it/blog/index.php/ixiptli/eterm-and-enlightenment-window-manager
>

>
> --
> - Codito, ergo sum - "I code, therefore I am" --
> The Rasterman (Carsten Haitzler)ras...@rasterman.com
>


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!

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

Re: gstreamer

[Andrea Pescetti]

Gav wrote:

"checking whether to build the GStreamer media backend... checking for
GSTREAMER... no
configure: error: requirements to build the GStreamer media backend not
met. Do not use --enable-gstreamer or install the missing packages


Hi Gavin, this won't help you with GStreamer since I checked and it is 
not immediately clear that it would help, but I suggest to use -and 
update if needed; we can of course create a wiki account for you- the 
following resources:


https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step
a section for Ubuntu 14.04 with all needed packages.

https://wiki.openoffice.org/wiki/Ubuntu_Build_Instructions
Outdated, but still contain useful hints.

http://svn.apache.org/viewvc/openoffice/devtools/build-scripts/4.1.2/unxlngix6/
Our build scripts for 4.1.2. These configure options are for a release 
build, but ideally we want this to succeed on the buildbot. Languages 
can be left out (for example, the Windows buildbot only uses en and de) 
and the package formats can be reduced too, but these should be the 
reference options.


And thanks a lot for this work. It won't help us with building releases, 
but it will make buildbot maintenance easier for both Infra and the project.


Regards,
  Andrea.

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