Re: Code signing available for OpenOffice

[Mark Thomas]

On 9 September 2016 23:29:49 BST, Andrea Pescetti  wrote:
>Mark Thomas wrote:
>> The infrastructure team has regained access to the OpenOffice code
>> signing account. If you would like to use it to sign releases please
>> open an infra ticket and provide the Apache IDs of those committers
>that
>> need access.
>
>May I ask if this is the same Symantec system that was rumored to be 
>about to be abandoned in early 2016? I hadn't renewed credentials since
>
>it seemed clear that the ASF would abandon it.

It is. The renewal discussion prompted a number of additional PMCs to come 
forward to request access. This enabled VP Infra to negotiate acceptable terms 
to renew it.

>Anyway, thanks for getting access again; just to be clear, it has not 
>been discussed so far to use it very soon, but it's good to know that 
>the ASF still has signing facilities available.

ACK.

Mark


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

Re: Release process and 4.1.3

[Patricia Shanahan]

On 9/9/2016 12:11 AM, Andrea Pescetti wrote:

Patricia Shanahan wrote:

https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template

It is what I would want to do for a major release with user interface
changes.


Yes, that one is the template for a 4.2.0, not for a 4.1.3 release.


We also need something far, far more agile for getting simple bug fix
releases out quickly and easily. I propose using 4.1.3 as a test case
for a stripped down process.


Actually, 4.1.2 was exactly this. Your starting point should thus be
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2 ; just
copy the wiki page and edit/generalize accordingly.


Can you give me a pointer to how to copy and edit confluence pages?

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

Re: Status of ASF Ubuntu Buildbots

[Andrea Pescetti]

Gavin McDonald wrote:

I’ve been working on creating replacement VMs for the deprecated Tethys


Thanks a lot. This is really much appreciated.


I reduced the frequency of some builds - I mean why spend 9 hours building and 
uploading language packs every single day, there is
no need - especially from the aoo410 branch thats seen like 2 commits in 9 
months!


Well, this is correct SO FAR... but now we will definitely need to build 
AOO410 often for 4.1.3, so a daily run would make sense as of now.



Any questions, I’m here on list.


Is there a way to start buildbots on demand? I remember that there was a 
dedicated chat (IRC? HipChat?) for managing them, but I don't remember 
the details and I don't know what permissions one needs.


Regards,
  Andrea.

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

Re: Release process and 4.1.3

[Andrea Pescetti]

Patricia Shanahan wrote:

On 9/9/2016 12:11 AM, Andrea Pescetti wrote:

Actually, 4.1.2 was exactly this. Your starting point should thus be
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2 ; just
copy the wiki page and edit/generalize accordingly.

Can you give me a pointer to how to copy and edit confluence pages?


At first you need to login (top right); you need a whitelisted account, 
so if the following instructions do not work we have to whitelist it 
(create the account first; then give us the username and we will 
whitelist it).


To copy a page: dots top right, then copy.

To edit a page: edit in top-right toolbar. On-line help is available for 
advanced formatting features, like dates and icons. Unfortunately, I 
think we are on WYSIWYG-only mode, which makes it a bit harder for those 
who prefer text-based markup.


Regards,
  Andrea.

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

Re: Release process and 4.1.3

[Patricia Shanahan]

On 9/10/2016 7:02 AM, Andrea Pescetti wrote:

Patricia Shanahan wrote:

On 9/9/2016 12:11 AM, Andrea Pescetti wrote:

Actually, 4.1.2 was exactly this. Your starting point should thus be
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1.2 ; just
copy the wiki page and edit/generalize accordingly.

Can you give me a pointer to how to copy and edit confluence pages?


At first you need to login (top right); you need a whitelisted account,
so if the following instructions do not work we have to whitelist it
(create the account first; then give us the username and we will
whitelist it).



I just created an account, user name "pats".

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

Re: Release process and 4.1.3

[Andrea Pescetti]

Patricia Shanahan wrote:

I just created an account, user name "pats".


Whitelisted.

Andrea

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

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

[Ariel Constenla-Haile]

On Thu, Sep 08, 2016 at 12:40:48AM +0200, Andrea Pescetti wrote:
> Recent events make it clear we will have to release OpenOffice 4.1.3 sooner
> or later, with some duplication of work with respect to 4.1.2-patch1 but
> with more clarity for those who couldn't see that we made a release last
> month.
> 
> I'll thus consider the AOO410 branch to be open again for the needed
> structural fixes, like version numbering and similar. And I can take care of
> fixing version numbers as I already did for 4.1.2.

I'd suggest we create a AOO413 branch, as suggested on private@.

Also, if the procedure didn't change, we should stick to the rule that
only code with a bug and release blocker flag approved by the Release
Manager can be checked in that branch; that is: if you want to include
changes in the AOO413 branch:

1) open a bug
2) request releaser blocker status
3) only once the release manager approves the release blocker status,
   commit your changes



Regards
-- 
Ariel Constenla-Haile


signature.asc
Description: Digital signature

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

[Patricia Shanahan]

On 9/10/2016 12:55 PM, Ariel Constenla-Haile wrote:

On Thu, Sep 08, 2016 at 12:40:48AM +0200, Andrea Pescetti wrote:

Recent events make it clear we will have to release OpenOffice 4.1.3 sooner
or later, with some duplication of work with respect to 4.1.2-patch1 but
with more clarity for those who couldn't see that we made a release last
month.

I'll thus consider the AOO410 branch to be open again for the needed
structural fixes, like version numbering and similar. And I can take care of
fixing version numbers as I already did for 4.1.2.


I'd suggest we create a AOO413 branch, as suggested on private@.

Also, if the procedure didn't change, we should stick to the rule that
only code with a bug and release blocker flag approved by the Release
Manager can be checked in that branch; that is: if you want to include
changes in the AOO413 branch:

1) open a bug
2) request releaser blocker status
3) only once the release manager approves the release blocker status,
   commit your changes


Andrea argues that it is traditional to put all point releases in the 
same branch. Following that tradition we would use AOO410 for all 4.1.x 
releases.


The reasons are lost in the mists of antiquity. The argument for 
carrying on that way for now is that there may be people following 
AOO410 and doing downstream packaging that depend on that behavior.


A possible compromise is to treat AOO410 as you recommend for AOO413 
from now on. We would still create AOO414, which I see as being 
necessary to become more agile. We should overlap testing, voting, and 
uploading of 4.1.3 with preparation of 4.1.4. Using the same branch for 
both would not be good.


I can go either way on this.

Patricia

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

4.1.3_release_blocker granted: [Issue 125980] Set default currency to Euro in Lithuanian locale

[bugzilla]

Patricia Shanahan  has granted Ariel Constenla-Haile
's request for 4.1.3_release_blocker:
Issue 125980: Set default currency to Euro in Lithuanian locale
https://bz.apache.org/ooo/show_bug.cgi?id=125980

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

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

[Gavin McDonald]

> On 11 Sep 2016, at 7:13 AM, Patricia Shanahan  wrote:
> 
> On 9/10/2016 12:55 PM, Ariel Constenla-Haile wrote:
>> On Thu, Sep 08, 2016 at 12:40:48AM +0200, Andrea Pescetti wrote:
>>> Recent events make it clear we will have to release OpenOffice 4.1.3 sooner
>>> or later, with some duplication of work with respect to 4.1.2-patch1 but
>>> with more clarity for those who couldn't see that we made a release last
>>> month.
>>> 
>>> I'll thus consider the AOO410 branch to be open again for the needed
>>> structural fixes, like version numbering and similar. And I can take care of
>>> fixing version numbers as I already did for 4.1.2.
>> 
>> I'd suggest we create a AOO413 branch, as suggested on private@.
>> 
>> Also, if the procedure didn't change, we should stick to the rule that
>> only code with a bug and release blocker flag approved by the Release
>> Manager can be checked in that branch; that is: if you want to include
>> changes in the AOO413 branch:
>> 
>> 1) open a bug
>> 2) request releaser blocker status
>> 3) only once the release manager approves the release blocker status,
>>   commit your changes
> 
> Andrea argues that it is traditional to put all point releases in the same 
> branch. Following that tradition we would use AOO410 for all 4.1.x releases.
> 
> The reasons are lost in the mists of antiquity. The argument for carrying on 
> that way for now is that there may be people following AOO410 and doing 
> downstream packaging that depend on that behaviour.

I really don’t get that reasoning. I’d like examples to understand why people 
downstream would be using a branch in the first place.
If anything, I’d half expect downstream to depend on the ‘Tag’ that a release 
was based on , not the branch (that has since changed.)

Tags seem to be labelled correctly, branches should follow suit. But I’ll leave 
it to you guys.

Gav…

Tags:-

.. 
AOO340/ 
AOO341/ 
AOO400/ 
AOO401/ 
AOO410/ 
AOO410_Beta/ 
AOO411/ 
AOO412/ 
AOO4121/ 
SNAPSHOT/ 

All those 41* tags (5 of them) were based on using the same 410 branch.

> 
> A possible compromise is to treat AOO410 as you recommend for AOO413 from now 
> on. We would still create AOO414, which I see as being necessary to become 
> more agile. We should overlap testing, voting, and uploading of 4.1.3 with 
> preparation of 4.1.4. Using the same branch for both would not be good.
> 
> I can go either way on this.
> 
> Patricia
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

[Andrea Pescetti]

Patricia Shanahan wrote:

On 9/10/2016 12:55 PM, Ariel Constenla-Haile wrote:

only code with a bug and release blocker flag approved by the Release
Manager can be checked in that branch; that is: if you want to include
changes in the AOO413 branch:
1) open a bug
2) request releaser blocker status
3) only once the release manager approves the release blocker status,
   commit your changes


Yes, this is the rule to follow. In my case, the changes I referred to 
are https://bz.apache.org/ooo/show_bug.cgi?id=127103 which is an obvious 
release blocker.



Andrea argues that it is traditional to put all point releases in the
same branch. Following that tradition we would use AOO410 for all 4.1.x
releases.


Correct. This is traditional but wrong (or at least awkward). So I also 
agree we should change it. I'm unsure about doing it for 4.1.3, but at 
latest we should change this (and communicate the change) upon releasing 
4.1.3. This ensures we can consider all downstream packagers to be informed.


Regards,
  Andrea.

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

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

[Patricia Shanahan]

On 9/10/2016 2:41 PM, Andrea Pescetti wrote:

Patricia Shanahan wrote:

On 9/10/2016 12:55 PM, Ariel Constenla-Haile wrote:

only code with a bug and release blocker flag approved by the Release
Manager can be checked in that branch; that is: if you want to include
changes in the AOO413 branch:
1) open a bug
2) request releaser blocker status
3) only once the release manager approves the release blocker status,
   commit your changes


Yes, this is the rule to follow. In my case, the changes I referred to
are https://bz.apache.org/ooo/show_bug.cgi?id=127103 which is an obvious
release blocker.


Andrea argues that it is traditional to put all point releases in the
same branch. Following that tradition we would use AOO410 for all 4.1.x
releases.


Correct. This is traditional but wrong (or at least awkward). So I also
agree we should change it. I'm unsure about doing it for 4.1.3, but at
latest we should change this (and communicate the change) upon releasing
4.1.3. This ensures we can consider all downstream packagers to be
informed.


I feel, very strongly, that the creation of the 4.1.4 branch should not 
wait for completion of the 4.1.3 release. We should be making decisions 
about 4.1.4 content, and checking in code for it, while 4.1.3 is 
undergoing testing, voting, and file copying.


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

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

[Andrea Pescetti]

Gavin McDonald wrote:

Tags:-
.. 
AOO340/ 
AOO341/ 
AOO400/ 
AOO401/ 
AOO410/ 
AOO410_Beta/ 
AOO411/ 
AOO412/ 
AOO4121/ 
SNAPSHOT/ 


The convention is indeed that AOO410 (the branch) actually stands for 
AOO41X (i.e., all 4.1.x releases). One may find it stupid (and I agree 
this is to be changed), but this is the consistent behavior the project 
adopted so far.


This also explains why I believe that someone might be tracking AOO410 
(the branch) to see new commits pertinent to the 4.1.x series.


SNAPSHOT instead is a moveable tag, moved to reflect something we base 
developer snapshots on.


Regards,
  Andrea.

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

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

[Patricia Shanahan]

On 9/10/2016 2:49 PM, Andrea Pescetti wrote:

Gavin McDonald wrote:

Tags:-
.. 
AOO340/ 
AOO341/ 
AOO400/ 
AOO401/ 
AOO410/ 
AOO410_Beta/

AOO411/ 
AOO412/ 
AOO4121/ 
SNAPSHOT/ 


The convention is indeed that AOO410 (the branch) actually stands for
AOO41X (i.e., all 4.1.x releases). One may find it stupid (and I agree
this is to be changed), but this is the consistent behavior the project
adopted so far.

This also explains why I believe that someone might be tracking AOO410
(the branch) to see new commits pertinent to the 4.1.x series.

SNAPSHOT instead is a moveable tag, moved to reflect something we base
developer snapshots on.


I'm going to wait a few hours to see if someone claims to depend on us 
not changing the branch. Absent a specific issue, I plan to create a 
4.1.3 branch, and expect the, not yet selected, 4.1.4 Release Manager to 
create a branch for it.


Meanwhile, creating bugzilla items and making "release blocker" requests 
should continue.


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

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

[Andrea Pescetti]

Patricia Shanahan wrote:

I'm going to wait a few hours to see if someone claims to depend on us
not changing the branch. Absent a specific issue, I plan to create a
4.1.3 branch, and expect the, not yet selected, 4.1.4 Release Manager to
create a branch for it.


OK. After all, I would assume that a downstream packager knows better 
than tracking a side branch, so my concerns might have been exaggerated; 
I know of no real issues.


Note: the branch should be named AOO413 (but I assume you mean this by 
"a 4.1.3 branch"). It should be an "svn copy" of AOO410.


No problem in creating an AOO414 branch even today, and even without an 
appointed Release Manager. Then if we decide not to release 4.1.4 for 
any reasons, we'll trash it or merge it somewhere else; branches are 
quite flexible.


Regards,
  Andrea.

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

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

[Patricia Shanahan]

On 9/10/2016 3:10 PM, Andrea Pescetti wrote:

Patricia Shanahan wrote:

I'm going to wait a few hours to see if someone claims to depend on us
not changing the branch. Absent a specific issue, I plan to create a
4.1.3 branch, and expect the, not yet selected, 4.1.4 Release Manager to
create a branch for it.


OK. After all, I would assume that a downstream packager knows better
than tracking a side branch, so my concerns might have been exaggerated;
I know of no real issues.

Note: the branch should be named AOO413 (but I assume you mean this by
"a 4.1.3 branch"). It should be an "svn copy" of AOO410.


Yes, the convention I would like is that Release x.y.z is associated 
with branch AOOxyz. We may need to change the format if any layer goes 
beyond one digit, but we can cross that bridge when we get to it.




No problem in creating an AOO414 branch even today, and even without an
appointed Release Manager. Then if we decide not to release 4.1.4 for
any reasons, we'll trash it or merge it somewhere else; branches are
quite flexible.


My view on this is that we should check in the changes for 4.1.3, freeze 
its code, and then create AOO414 as a copy of AOO413.


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

Re: Releasing OpenOffice 4.1.3 (reopening the AOO410 branch)

[Andrea Pescetti]

Patricia Shanahan wrote:

My view on this is that we should check in the changes for 4.1.3, freeze
its code, and then create AOO414 as a copy of AOO413.


Sure, this will work too. Then when you really release 4.1.3 with any 
last-minute fixes, a single "svn merge" command will update the AOO414 
branch; the other option would be to make frequent merges and get the 
same result in the end. But with only one "active" branch at a time, the 
above will work well.


Regards,
  Andrea.

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

AOO413 branch created

[Patricia Shanahan]

I have created an AOO413 branch as a copy of AOO410. It is now available 
for check in of "release blocker" approved changes.


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

Re: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

[Jose R R]

On Fri, Sep 9, 2016 at 12:37 PM, Wolfgang Tichy  wrote:
> Package: src:linux
> Version: 3.16.7-ckt25-2+deb8u3
> Severity: critical
> Tags: security
> Justification: causes serious data loss
>
> Dear Maintainer,
>
> when I open a particular word document (it contains images and I can send it
> to you for testing) with libreoffice, all memory and all swap get used up
> within about a minute.

You may want to *narrow down* your memory issue by trying out Apache OpenOffice:

Download: https://openoffice.org/download/

> This happens slowly enough that it can be monitored
> with "top" and "free". What I see with top is that soffice.bin (which is
> libreoffice) does not use much memory (maybe 2%). Nevertheless more and more
> memory gets used. "free -h" gives something like this:
>
>  total   used   free sharedbuffers cached
> Mem:  7.5G   7.4G   141M   5.9G71M   6.4G
> -/+ buffers/cache:   917M   6.6G
> Swap: 8.0G   663M   7.4G
>
> Eventually the "used" column in the "Mem:" and "Swap:" and lines reach the
> total and the system runs out of memory and becomes totally unresponsive
> (even the mouse pointer freezes), no remote logins are possible at this
> point, and all keypresses are ignored. The only way to regain control is by
> holding down the power button for 10s. However, the "used" column in the
> "-/+ buffers/cache:" line stays near 1GB, so that it is clear that
> buffers/caches take up almost all the space.
>
> You may wonder why I file this against the kernel and not libreoffice. Well,
> I am sure libreoffice is doing something stupid, that could be fixed to
> circumvent this problem. But the kernel should simply not allow any user
> process to bring down the entire system. Also it seems the kernel is
> allocating caches or buffers until it runs out of all memory and then
> freezes. If it was only libreoffice allocating memory, OOM killer would kill
> it. But nothing like this happens, even if you wait 2h nothing happens. I
> think OOM killer does nothing because no single user process uses a lot of
> memory. It's the kernel choking on itself.
>
> Ok, so now let me speculate on what might be wrong. I am filing this report
> for my laptop that has a i7-3667U CPU with integrated Intel graphics card:
> 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
> Graphics Controller (rev 09)
> But the problem also occurs on 3 other Debian desktop machines that run the
> same kernel, and have either Intel or ATI graphics, i.e.:
> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
> Core Processor Integrated Graphics Controller (rev 06)
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
> Barts PRO [Radeon HD 6850]
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
> Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
> However, it happens differently on a 4th Debian desktop machine with
> 07:00.0 VGA compatible controller: NVIDIA Corporation NV42GL [Quadro FX 
> 3450/4000 SDI] (rev a2)
> On this one, Gnome3 crashes and dmesg has a lot of lines lines like:
> [880754.926611] [TTM] Failed to find memory space for buffer 
> 0x880367e42800 eviction
> [880754.926613] [TTM] No space for 880367e42800 (497 pages, 1988K, 1M)
> [880754.926614] [TTM]   placement[0]=0x00070002 (1)
> [880754.926616] [TTM] has_type: 1
> [880754.926617] [TTM] use_type: 1
> [880754.926618] [TTM] flags: 0x000A
> [880754.926619] [TTM] gpu_offset: 0x
> [880754.926620] [TTM] size: 131072
> [880754.926621] [TTM] available_caching: 0x0007
> [880754.926622] [TTM] default_caching: 0x0001
> This is actually good because after the gnome3 crash the system is still
> usable. I should say that in all cases I am using the open source graphics
> drivers that use kernel mode setting. So the latter crash leads me to think
> that some interaction between the graphics drivers and the kernel leads to
> the allocation of too many buffers/caches by the kernel until it runs out.
> Probably this is all triggered by libreoffice (running on X) trying to
> display some JPG images in a document.
>
> The reason why I consider this security relevant is that anybody with a user
> account can use libreoffice to bring the system down. This will cause data
> loss since all other users cannot save any data in open files.
>
> Thank you very much for considering this report,
> Wolfgang Tichy
>
>
> -- Package-specific info:
> ** Version:
> Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
> 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02)
>
> ** Command line:
> BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
> root=UUID=111acff4-4673-47ad-85a1-43f48c1c7621 ro quiet
>
> ** Tainted: W (512)
>  * Taint on warning.
>
> ** Kernel log:
> [44950.827165] Broke affinity for irq 41
> [44950.930086] smpboot: CPU 3

How do all the binaries get built?

[Patricia Shanahan]

What has to be done, in what sorts of environments, to generate all the 
binaries?


Does, for example, building all the language versions for OSX have to be 
done on a Mac, or can one take some language files and some OSX files 
and combine them on a Windows machine?


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

RE: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

[Dennis E. Hamilton]

I don't understand the point of posting this message to dev@oo.a.o, especially 
with all the details of an apparent Linux problem in conjunction with 
LibreOffice (but not necessarily caused by LibreOffice).

I assume the recommendation of Apache OpenOffice is not as a substitute but to 
see if there is any forensic information to be gained by trying it too.  That's 
similar to why I compare AOO problems reported on .doc and .xls files in 
Microsoft Office and LibreOffice to see if there is anything different that is 
informative.

What did you have in mind, Jose?

> -Original Message-
> From: jose@metztli.com [mailto:jose@metztli.com] On Behalf Of
> Jose R R
> Sent: Saturday, September 10, 2016 17:37
> To: Wolfgang Tichy ; 837...@bugs.debian.org
> Cc: Debian Bug Tracking System ; dev
> 
> Subject: Re: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap
> is used up until system freezes
> 
> On Fri, Sep 9, 2016 at 12:37 PM, Wolfgang Tichy 
> wrote:
> > Package: src:linux
> > Version: 3.16.7-ckt25-2+deb8u3
> > Severity: critical
> > Tags: security
> > Justification: causes serious data loss
> >
> > Dear Maintainer,
> >
> > when I open a particular word document (it contains images and I can
> send it
> > to you for testing) with libreoffice, all memory and all swap get used
> up
> > within about a minute.
> 
> You may want to *narrow down* your memory issue by trying out Apache
> OpenOffice:
> 
> Download: https://openoffice.org/download/
> 
[ ... ]



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

Re: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

[Jose R R]

On Sat, Sep 10, 2016 at 6:49 PM, Dennis E. Hamilton
 wrote:
>
> I don't understand the point of posting this message to dev@oo.a.o, 
> especially with all the details of an apparent Linux problem in conjunction 
> with LibreOffice (but not necessarily caused by LibreOffice).
>
> I assume the recommendation of Apache OpenOffice is not as a substitute
Your assumption is false. Period.

> but to see if there is any forensic information to be gained by trying it 
> too.  That's similar to why I compare AOO problems reported on .doc and .xls 
> files in Microsoft Office and LibreOffice to see if there is anything 
> different that is informative.
>
> What did you have in mind, Jose?
>
> > -Original Message-
> > From: jose@metztli.com [mailto:jose@metztli.com] On Behalf Of
> > Jose R R
> > Sent: Saturday, September 10, 2016 17:37
> > To: Wolfgang Tichy ; 837...@bugs.debian.org
> > Cc: Debian Bug Tracking System ; dev
> > 
> > Subject: Re: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap
> > is used up until system freezes
> >
> > On Fri, Sep 9, 2016 at 12:37 PM, Wolfgang Tichy 
> > wrote:
> > > Package: src:linux
> > > Version: 3.16.7-ckt25-2+deb8u3
> > > Severity: critical
> > > Tags: security
> > > Justification: causes serious data loss
> > >
> > > Dear Maintainer,
> > >
> > > when I open a particular word document (it contains images and I can
> > send it
> > > to you for testing) with libreoffice, all memory and all swap get used
> > up
> > > within about a minute.
> >
> > You may want to *narrow down* your memory issue by trying out Apache
> > OpenOffice:
> >
> > Download: https://openoffice.org/download/
> >
> [ ... ]
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>



-- 
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: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

[Jose R R]

On Sat, Sep 10, 2016 at 6:10 PM, Ben Hutchings  wrote:
> On Sat, 2016-09-10 at 17:37 -0700, Jose R R wrote:
>> On Fri, Sep 9, 2016 at 12:37 PM, Wolfgang Tichy 
>> wrote:
>> >
>> > Package: src:linux
>> > Version: 3.16.7-ckt25-2+deb8u3
>> > Severity: critical
>> > Tags: security
>> > Justification: causes serious data loss
>> >
>> > Dear Maintainer,
>> >
>> > when I open a particular word document (it contains images and I
>> > can send it
>> > to you for testing) with libreoffice, all memory and all swap get
>> > used up
>> > within about a minute.
>>
>> You may want to *narrow down* your memory issue by trying out Apache
>> OpenOffice:
>>
>> Download: https://openoffice.org/download/
> [...]
>
> Please, we don't need advocacy for rival software in the Debian BTS.
If ApacheOO solves the user's problem, then it is probably time for Debian
to reevaluate 'rival' alternative.


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!
-

4.1.3_release_blocker granted: [Issue 127100] Make NSIS 3.* a build requirement for building Windows installers

[bugzilla]

Patricia Shanahan  has granted  4.1.3_release_blocker:
Issue 127100: Make NSIS 3.* a build requirement for building Windows installers
https://bz.apache.org/ooo/show_bug.cgi?id=127100

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

Re: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

[Ben Hutchings]

On Sat, 2016-09-10 at 17:37 -0700, Jose R R wrote:
> On Fri, Sep 9, 2016 at 12:37 PM, Wolfgang Tichy 
> wrote:
> > 
> > Package: src:linux
> > Version: 3.16.7-ckt25-2+deb8u3
> > Severity: critical
> > Tags: security
> > Justification: causes serious data loss
> > 
> > Dear Maintainer,
> > 
> > when I open a particular word document (it contains images and I
> > can send it
> > to you for testing) with libreoffice, all memory and all swap get
> > used up
> > within about a minute.
> 
> You may want to *narrow down* your memory issue by trying out Apache
> OpenOffice:
> 
> Download: https://openoffice.org/download/
[...]

Please, we don't need advocacy for rival software in the Debian BTS.

Ben.

-- 
Ben Hutchings
Experience is what causes a person to make new mistakes instead of old
ones.


signature.asc
Description: This is a digitally signed message part