Bug#1076474: icebreaker: is not classified in the games section of the Debian menu but in Other

[Stéphane Aulery]

Package: icebreaker
Version: 2.2.0-1
Severity: minor
Tags: d-i
X-Debbugs-Cc: saul...@free.fr

Hello,

IceBreaker is not classified in the games section of the Debian menu but in 
Other.

Regards,


-- System Information:
Debian Release: 12.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-22-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages icebreaker depends on:
ii  libc62.36-9+deb12u7
ii  libsdl-mixer1.2  1.2.12-17+b3
ii  libsdl1.2debian  1.2.15+dfsg2-8

icebreaker recommends no packages.

icebreaker suggests no packages.

-- no debconf information

Bug#827459: libreoffice changes gnome-workspaces on popup

[Stéphane Aulery]

Hello,

Do you still get this behavior with the LO version provided by bullseye 
or bookworm?


Regards,

--
Stéphane Aulery

Bug#890638: libreoffice-calc: Freezes while saving

[Stéphane Aulery]

Hello,

This version oF LO is not supported anymore.

Could you reproduce on with last LO version?

Regards,
--
Stéphane Aulery

Bug#928953: libreoffice: Impossible to move a dialog window

[Stéphane Aulery]

Hello,

Does this still happen with a newer version?

Couldn't the Windows manager reduce the window too much, unlike LO?

Regards,

--
Stéphane Aulery

Bug#781087: libreoffice-impress: impress animation "strechy" dosn't work with drawings

[Stéphane Aulery]

Hi Wolfgang,

Did you still have the same bug with 7.0.4 (bullseye) or 7.4.3 (bookworm) ?

Regards,

--
Stéphane Aulery

Bug#857467: libreoffice-base: Postgresql — Cannot enter or edit data or edit table columns without primary key

[Stéphane Aulery]

Hello,

Le 30/10/2018 à 09:38, Lionel Elie Mamane a écrit :

On Tue, Oct 30, 2018 at 01:17:49AM +0100, Stéphane Aulery wrote:

forwarded 857467 https://bugs.documentfoundation.org/show_bug.cgi?id=45252


No, that upstream bug is about something else, namely that the
PostgreSQL SDBC driver does not implement changing table structure,
creating tables, deleting tables, etc. Only data manipulation (adding
rows, changing rows, deleting rows).

This Debian bug is that data manipulation is not possible without a
primary key on the table.



Ok. I have opened a new report on LO bugtracker.

Regards,

--
Stéphane Aulery

Bug#856817: Fwd: [Bug 96197] Korean text to Wrap in the middle of a word

[Stéphane Aulery]

Commit in master: https://gerrit.libreoffice.org/#/c/42987/

---

 Change 42987 - Needs Code-Review
tdf#96197 do not break Korean words in the middle.

Korean words are composed of Hangul and are separated
by space or newline. This patch improves line breaking
function in CJK break iterator so that it does not
break Korean words in the middle. It now breaks at the
first character of the last Korean word.

Change-Id: I91b20733c0c5ec4755bf68eb0d7c14c42c1f3556

Bug#871484: fixed-upstream

[Stéphane Aulery]

This bug should be fixed with LO 6.0.0.

See https://bugs.documentfoundation.org/show_bug.cgi?id=59424#c11

-- 
Stéphane Aulery

Bug#677484: libreoffice: Menu / submenu overlapping

[Stéphane Aulery]

Hello jEsuSdA,

What version is working for you please?

Reagrds,

-- 
Stéphane Aulery

Bug#640462: libreoffice: default window appears partly off-screen

[Stéphane Aulery]

Hello Vincent,

Could you reproduce it with a current version please?

Regards,

-- 
Stéphane Aulery

Bug#836767: libreoffice-calc: Slow rendering of UI

[Stéphane Aulery]

Hello Emil,

Could you try to reproduce with the current version please?

It should be fixed now.

Regards,

-- 
Stéphane Aulery

Bug#780607: libreoffice-writer: TrueType Hebrew fonts have stopped working in Writer

[Stéphane Aulery]

Hello Celejar,

Do you still have this problem with your current version of LO?

I can't find any bug like that in LO bugtracker.

Regards,

-- 
Stéphane Aulery

Bug#867591: libreoffice-writer: bug or no bug? Libreoffice-dmath inhibits to open gallery in libreoffice-writer

[Stéphane Aulery]

Hello,

I can't test with stable but in testing I have no problem like that.

Regards,

-- 
Stéphane Aulery

Bug#838262: libreoffice-calc: Renders wrong characters in sheet after some time

[Stéphane Aulery]

Hello,

Do you still have the same behaviour with a current version please?

Regards,

-- 
Stéphane Aulery

Bug#836935: libreoffice-gtk3: Setting GDK_SCALE and GDK_DPI_SCALE to values other than 1 screws up rendering

[Stéphane Aulery]

Hello,

I tested with your command and LO 5.4.1-1 and the result is not bad.
Could you look into my screenshot Christian?

Regards,

-- 
Stéphane Aulery

Bug#821401: libreoffice-gtk3: First [Ctrl+Scroll Down] after changing focus to LO makes LO to zoom in instead of zoom out

[Stéphane Aulery]

Hello,

I can't reproduce it with LO 1:5.4.1-1.

Regards,

-- 
Stéphane Aulery

Bug#708162: dd

[Stéphane Aulery]

Hello,

Maybe it's the reason of the circular dependancy [1]?

[1] 
https://lintian.debian.org/tags/intra-source-package-circular-dependency.html

-- 
Stéphane Aulery

Bug#728977: libreoffice-draw: doesn't properly print slides that are larger than the paper size

[Stéphane Aulery]

Hello,

I can't reproduce it with LO 1:5.4.1-1 but I use A4 paper size.

Regards,

-- 
Stépahne Aulery

Bug#656072: libreoffice-writer: Displaying very large plot pasted from Calc causes Writer to become unresponsive

[Stéphane Aulery]

With LO 1:5.4.1-1 the copy-paste is slow (because the graph is really
huge) but LO doesn't crash anymore. It cosume 1.5 Gb of memory.

Bug#842726: [libreoffice-writer] Cannot select text and scroll at the same time

[Stéphane Aulery]

Hello,

This bug is confirmed but I can't repoduce it with LO 5.4.1-1.

Regards

-- 
Stéphane Aulery

Bug#806128: libreoffice: debian system freezes

[Stéphane Aulery]

Hello Rouven-Matthias,

Do you still have some crash after a long run of LO?

Regards,

-- 
Stéphane Aulery

Bug#682516: libreoffice-writer: Can't save odt files, access denied to /tmp/luz...

[Stéphane Aulery]

Hello,

There are others bugs in LO about /tmp use.

This could be still relevant.

Does it happened again with your current version?

Regards,

-- 
Stéphane

Bug#671774: /usr/bin/libreoffice: LibreOffice calc creates malformed links to external XLS-sheets

[Stéphane Aulery]

Hello,

I can't reproducre this bug with LO 5.4.1-1.

Seems fixed.

Regards,

-- 
Stéphane Aulery

Bug#772097: libreoffice: LibreOffice sees only "Generic Printer"

[Stéphane Aulery]

Hello,

The last week I installed a fresh buster and I have seen a variant of
this bug.

When LO was first started, the printer displayed was the Generic Printer. After
closing and reopening LO displayed the correct printer.

We handled the printer's built-in scanner with Gimp and xsane. I do not
know if it was between the two openings or after the second.

Regards,

-- 
Stéphane Aulery

Bug#810723: Bug 810723 split in 814962, 877269, 877268

[Stéphane Aulery]

forwarded 877268 https://bugs.documentfoundation.org/show_bug.cgi?id=112768
retitle 877268 PDF once it's timestamped, no further changes should be allowed
stop

Bug#732380: libreoffice-writer: Vertical text alignment problem with Japanese text

[Stéphane Aulery]

Hello Osuma,

Could you test the fonts alignment please?

It's seems better now. If not better, can you explain it.

Regards,

-- 
Stéphane Aulery

Bug#862291: closed by Thomas Goirand <z...@debian.org> (Re: Bug#862290: Version displayed 2.5, but version packaged 2.6)

[Stéphane Aulery]

hi Thomas,

Le 11/05/2017 22:24, Thomas Goirand a écrit :

On 05/11/2017 05:03 PM, Stéphane Aulery wrote:


I expect to control a rotation for each periodicity. It's supported in
V. 3.0, so I have installed and configured it by myself.

But if it is packaged it's better.

Upstream seems dead. I have sent a mail yesterday, offering to become
the maintainer.

Is the packaging of a new upstream version excluded for you?

In that case it would be better to change it's name because it's a
noiseless fork.


If someone is able to recover all the functionalities added to the
Debian package to the version 3.0, then I'll happily package that.
However, I don't have time to do it myself, and also, Stretch is frozen
so it will only be possible to upload to Experimental until the 
release.


I leave it to the developer to react and if nothing happens,
I will consider the forker and how to integrate your improvements
in version 3.0.

Cheers,

--
Stéphane Aulery

Bug#862291: closed by Thomas Goirand <z...@debian.org> (Re: Bug#862290: Version displayed 2.5, but version packaged 2.6)

[Stéphane Aulery]

Hi Thomas,

Le 11/05/2017 16:30, ow...@bugs.debian.org a écrit :

This is an automatic notification regarding your Bug report
which was filed against the automysqlbackup package:

#862291: Version displayed 2.6, but version packaged 2.5

It has been closed by Thomas Goirand <z...@debian.org>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Thomas Goirand
<z...@debian.org> by
replying to this email.


Thanks for your reply.

I expect to control a rotation for each periodicity. It's supported in 
V. 3.0, so I have installed and configured it by myself.


But if it is packaged it's better.

Upstream seems dead. I have sent a mail yesterday, offering to become 
the maintainer.


Is the packaging of a new upstream version excluded for you?

In that case it would be better to change it's name because it's a 
noiseless fork.


Regards,

--
Stéphane Aulery

Bug#862291: Version displayed 2.6, but 2.5 packaged

[Stéphane Aulery]

Package: automysqlbackup
Version: 2.6+debian.4-1
Severity: minor


Dear Maintainer,

After testing I realized that the version included in Debian is 2.5,
while the package announces version 2.6.

Can you change the package to indicate that it is version 2.5,
or to pack the latest version?

I am interested in the backup rotation which is better in version 2.6.

Regards,

--
Stéphane Aulery





-- System Information:
Debian Release: 8.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages automysqlbackup depends on:
ii  bsd-mailx [mailx] 
8.1.2-0.20141216cvs-2
ii  percona-server-client-5.6 [virtual-mysql-client]  
5.6.35-81.0-1.wheezy


Versions of packages automysqlbackup recommends:
pn  mutt  

automysqlbackup suggests no packages.

-- Configuration Files:
/etc/default/automysqlbackup changed [not included]

-- no debconf information

Bug#862290: Version displayed 2.5, but version packaged 2.6

[Stéphane AULERY]

Package: automysqlbackup
Version: 2.6+debian.4-1
Severity: minor


Dear Maintainer,

After testing I realized that the version included in Debian is 2.5,
while the package announces version 2.6.

Can you change the package to indicate that it is version 2.5,
or to pack the latest version?

I am interested in the backup rotation which is better in version 2.6.

Regards,

-- 
Stéphane Aulery





-- System Information:
Debian Release: 8.8
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages automysqlbackup depends on:
ii  bsd-mailx [mailx] 8.1.2-0.20141216cvs-2
ii  percona-server-client-5.6 [virtual-mysql-client]  5.6.35-81.0-1.wheezy

Versions of packages automysqlbackup recommends:
pn  mutt  

automysqlbackup suggests no packages.

-- Configuration Files:
/etc/default/automysqlbackup changed [not included]

-- no debconf information

Bug#749979: Bug #749979 libreoffice-common: Should recommend fonts-stix instead of xfonts-mathml (which got removed from Debian)

[Stéphane Aulery]

retitle 749979 libreoffice-common: Remove xfonts-mathml recommandation (package 
removed from Debian)
stop
-

Hello Rene,

libreoffice-core already depends on fonts-opensymbol. It remains only to remove 
the recommendation of the xfonts-mathml package.

Regards,

-- 
Stéphane Aulery

Bug#808476: Re : libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[Stéphane Aulery]

Hi,

Le 16/03/2016 20:25, nicolas.patr...@gmail.com a écrit :

Le 02/03/2016 22:22:44, Stéphane Aulery a écrit :


Thanks for your help. I forward the document and comments.


The bug is corrected in LibreOffice:
Version: 5.1.1.3
Build ID: 1:5.1.1-1


You have tested this version and it's good?

Regards,

--
Stéphane Aulery

Bug#719590: retitle 719590 Provide a C.UTF-8 locale by default

[Stéphane Aulery]

tags 719590 - fixed-upstream

retitle 719590 Provide a C.UTF-8 locale by default
forwarded 719590 https://sourceware.org/bugzilla/show_bug.cgi?id=17318

reassign 719590 libc6
stop

The current use of locale C.UTF-8 is a Debianisme that can not be taken 
into account by upstream. By against another bug was opened to add this 
locale:


https://sourceware.org/bugzilla/show_bug.cgi?id=17318

--
Stéphane Aulery

Bug#798809: reopen 798809

[Stéphane Aulery]

Hello Matt,

On Sat, 17 Oct 2015 15:30:12 -0500 Matt Zagrabelny <mzagr...@d.umn.edu> wrote:
> reopen 798809
>
> Greetings,
>
> This bug is still biting me. I did run an strace on the process while
> the CPU was being pegged, but the trace didn't yield anything of use
> with regards to the processor.
>
> 1:5.0.3~rc1-1
>
> What else can I provide to help with this bug?

Please send use a document which you use to reproduce this bug please.

Regards,

-- 
Stéphane Aulery

Bug#661654: merge 661654 661973

[Stéphane Aulery]

retitle 661654 libreoffice-common: consider adding a '--convert-to help' 
feature that would work like "-vo help" in 'mplayer'
forwarded 661654 https://bugs.documentfoundation.org/show_bug.cgi?id=98153
merge 661654 661973
stop
-

Hello,

Upstream replied that the request for documentation in the manpage is not 
maintainable, but the "-vo help" option is a good idea.

Regards,

-- 
Stéphane Aulery

Bug#661654: retitle 661654 libreoffice-common: 'man libreoffice' and 'soffice --help': "--convert-to": mention *all* possible file extensions

[Stéphane Aulery]

Hi,

Le 08/03/2016 00:00, Rene Engelhard a écrit :

Hi,

On Mon, Mar 07, 2016 at 11:53:59PM +0100, Stéphane Aulery wrote:

Where do you see that? I don't believe they will add every possible format
(well, extension) in the manpage, will they?

Which is what this bug is about.


Oups, I made a mistake with forward link and title.
I correct this.

Manpage is ours, the command line for them.


Nah, the manpage is also coming from upstream.

Yeah, I said manpage in my reply, but that is a generic ""problem".
As I said: I don't believe they will add every possible extenson suitable
for --convert-to to either, will they? But that is what the submitter
wants.

Thus it was + wontfix. (Could have been closed, too, for being totally
nonsensical, but)


Yes, all is to much, major formats is better. I am not against to close 
it, now that it has been passed upstream. Lots of other bugs like that. 
I made a first pass for sorting. There is a lot of noise!


I would not be too aggressive.

Regards,

--
Stéphane Aulery

Bug#661654: retitle 661654 libreoffice-common: 'man libreoffice' and 'soffice --help': "--convert-to": mention *all* possible file extensions

[Stéphane Aulery]

Hi Rene,

Le 07/03/2016 23:45, Rene Engelhard a écrit :

Hi,

On Mon, Mar 07, 2016 at 01:11:42AM +0100, Stéphane Aulery wrote:

retitle 661654 libreoffice-common: 'man libreoffice' and 'soffice --help':
"--convert-to": mention *all* possible file extensions
tags 661654 - wontfix
stop
-

Upstream will fix 'soffice --help'.


Where do you see that? I don't believe they will add every possible format
(well, extension) in the manpage, will they?

Which is what this bug is about.


Oups, I made a mistake with forward link and title.
I correct this.

Manpage is ours, the command line for them.

Regards,

--
Stéphane Aulery

Bug#808125: Re : Bug #808125 - libreoffice-base: c/p from calc to create table, character_data does not exist on postgresql

[Stéphane Aulery]

Lionel Elie Mamane committed a patch related to this issue.
It has been pushed to "libreoffice-5-1":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=43bca025961c4d78082e18efb95f9212b27f964b=libreoffice-5-1

tdf#92538 pgsql-sdbc make a reasonable sorting of types

It will be available in 5.1.2.

--
Stéphane Aulery

Bug#717846: Re : Bug#717846: tags 717846 + fixed-upstream

[Stéphane Aulery]

- Rene Engelhard <r...@debian.org> a écrit :
> On Mon, Mar 07, 2016 at 03:08:03AM +0100, Stéphane Aulery wrote:
> > tags 717846 + fixed-upstream
> > stop
> > -
> > 
> > I think this bug is fixed upstream because I can't reproduce it with LO
> > 5.1.0.3.
> > 
> > We can test if it is in 5.0.5 and close the bug if there is not.
> 
> It's not really that important to know about 5.0.5 (if we do, fine, if not, 
> ok.)
> , we could also close in 5.1.0~rc3 or whatever later; 
> 5.0.5 as in testing is a dead branch anyway.

Ok, it will be easier for me.

Regards,

-- 
Stéphane Aulery

Bug#717846: tags 717846 + fixed-upstream

[Stéphane Aulery]

tags 717846 + fixed-upstream
stop
-

I think this bug is fixed upstream because I can't reproduce it with LO 
5.1.0.3.


We can test if it is in 5.0.5 and close the bug if there is not.

--
Stéphane Aulery

Bug#661654: retitle 661654 libreoffice-common: 'man libreoffice' and 'soffice --help': "--convert-to": mention *all* possible file extensions

[Stéphane Aulery]

retitle 661654 libreoffice-common: 'man libreoffice' and 'soffice 
--help': "--convert-to": mention *all* possible file extensions

tags 661654 - wontfix
stop
-

Upstream will fix 'soffice --help'.

To us fix our manpage.

--
Stéphane Aulery

Bug#749979: Re : Bug #749979 - libreoffice-common: Should recommend fonts-stix instead of xfonts-mathml (which got removed from Debian)

[Stéphane Aulery]

Hello,

Upstream gives no mandatory font list. At most OpenSymbol font is essential.

Regards,

--
Stéphane Aulery

Bug#639006: Bug #639006 - libreoffice-calc: Basic runtime error '423' for Maxchange

[Stéphane Aulery]

Hello naths,

Tue, 23 Aug 2011 21:18:09 +0530, naths wrote:
> Package: libreoffice-calc
> Version: 1:3.3.4-1
> Severity: normal
>
> When try to open a file containing macro libreofficeCalc open a > 
LibreOffice

> Basic window of VBAProject with the macro
> containing line " .MaxChange = 0.001 ".
> This shows an error of " BASIC runtime error ' 423 ' MaxChange " .
> Still the file/sheets are working fine.

The following bug is similar. This is probably a non or poorly 
implemented feature:


Can you reproduce this bug with a newer version of LO please?

Do you have a document to test?

Regards,

--
Stéphane Aulery

Bug#714417: - libreoffice-base: can't open dBASE files in base

[Stéphane Aulery]

Hello Gary,

Le Fri, 28 Jun 2013 21:18:52 -0400, Gary Dale wrote :


Package: libreoffice-base
Version: 1:4.0.3-3
Severity: normal

* What led up to the situation?
I use an ancient Visual dBASE running in a Windows XP VM to manipulate run resul
ts from several
sources in order to create a single table that I use to drive a "form letter" ce
rtificate to
send to each of the participents. Now that I'm using Jessie, I find I can't get
to the
dBASE tables.

* What exactly did you do (or not do) that was effective (or ineffective)?
When I connect to existing databases that link to dBASE tables, I can see the ta
bles. However,
when I create a new table and link to a dBASE table, I can't see the tables. The
  connection
tests OK, but the tables aren't visible.


I have no dBASE database for testing by myself.

Are there has been progress with new versions?

In the bugtracker LO I could find about twenty bug related dBASE but 
nothing identical:


https://bugs.documentfoundation.org/buglist.cgi?quicksearch=dBASE_id=596063

Regards,

--
Stéphane Aulery

Bug#725221: Bug #725221 - libreoffice-calc: Japanese characters not correctly displayed

[Stéphane Aulery]

Hello Charles,

Thu, 03 Oct 2013 10:20:57 +0900, Charles Plessy wrote :


it has been a long time that I have a strange problem with LibreOffice
Calc: while it can display Japanese characters in the Input line, it
replaces them with a rectangular box in the cell itself.

I attached a test file and a screenshot to illustrate.  Using the same
file Gnumeric displays the character correctly.  It seems that, in the
cells only, LibreOffice is not able to use a replacement font to
display Japanese (and probably other CJK) characters.  For instance,
if in the attached file I change the font from Liberation Sans (or any
Latin-oriented font) to a Japanese-oriented font ( *-gothic, *-mincho,
etc), then the problem dissapears.

Would there be a simple solution to this problem ?


Generaly speaking, Asiatics languages support is broken in LO as for 
viewing and typing.


Search LO bugtracker with keywords japanese, CJK, Chinese, Hangul, ibus; 
everything is more or less broken.


I could not reproduce the bug with LO 5.1.0.3, but it seems random 
according to comments.


Regards,

--
Stéphane Aulery

Bug#731366: Re : Bug #731366 - libreoffice: ibus and complex input methods do not work at all in 4.4.x

[Stéphane Aulery]

This bug is the subject of two similar reports involving ibus and KDE 
(4) for the entry of Asian languages:


https://bugs.documentfoundation.org/show_bug.cgi?id=91375

and

https://bugs.documentfoundation.org/show_bug.cgi?id=34016

--
Stéphane Aulery

Bug#734652: Re : Bug #734652 libreoffice-calc: saving file as .sxc screws up content

[Stéphane Aulery]

Hello 0 1,

Wed, 08 Jan 2014 22:29:21 +0100, 0 1 wrote :


I am experiencing a very simple problem: it seems Libreoffice Calc can't
save properly as .sxc format.

Numbers are kept properly inside the spreadsheet, but a simple «sum»
operation is screwed up, as seen in this screenshot:
https://pix.isalo.org/?img=1387458494.png

Attached some .odx document (the original, no problem with it) and some
(saved as) .sdx one, which exhibits the problem.


This bug is fixed in version 5.1.0.3 at least.

Can you reproduce it with your current version please?

Regards,

--
Stéphane Aulery

Bug#781087: Bug #781087 - libreoffice-impress: impress animation "strechy" dosn't work with drawings

[Stéphane Aulery]

Hi Wolfgang,

Le 05/03/2016 23:51, Wolfgang Hainz a écrit :


yes, I'm still seeing this bug with 5.0.5.2.


Everything matches. I forward the information. Thank you. :))

Regards,

--
Stéphane Aulery

Bug#781087: Bug #781087 - libreoffice-impress: impress animation "strechy" dosn't work with drawings

[Stéphane Aulery]

Hi Wolfgang,

Le 05/03/2016 15:33, Wolfgang Hainz a écrit :


thanks for looking into this issue. Please find below the output of lsusb and 
lspci. Actually I'm using LO Version 5.0.5.2 from Debian Stable backports.


Thanks for tho output.

Did you have the same bug with 5.0.5.2 ?

Regards,

--
Stéphane Aulery

Bug#760179: tags 760179 + unreproducible

[Stéphane Aulery]

tags 760179 + upstream
tags 760179 + unreproducible
stop
-

I can't reproduce it with Lo 5.0.5.

-- 
Stéphane Aulery

Bug#808125: Re : Bug #808125 - libreoffice-base: c/p from calc to create table, character_data does not exist on postgresql

[Stéphane Aulery]

Lionel Elie Mamane committed a patch related to this issue.
It has been pushed to "libreoffice-5-1":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=95b10e373d117f3ed3e53987aa40a65d1ca6d1a0=libreoffice-5-1

tdf#92538 use proper schema name for type names

It will be available in 5.1.2.

--
Stéphane Aulery

Bug#808125: Re : Bug #808125 - libreoffice-base: c/p from calc to create table, character_data does not exist on postgresql

[Stéphane Aulery]

Lionel Elie Mamane committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=280f234e5e9fb2879ef99d6888bd0b5b30d16b45

fixup tdf#92538

It will be available in 5.2.0.

--
Stéphane Aulery

Bug#808125: Re : Bug #808125 - libreoffice-base: c/p from calc to create table, character_data does not exist on postgresql

[Stéphane Aulery]

Lionel Elie Mamane committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=0b0c99edbbd29a89ddc5af60f9abba141e42a4a4

tdf#92538 pgsql-sdbc make a reasonable sorting of types

It will be available in 5.2.0.

--
Stéphane Aulery

Bug#808125: Re : Bug #808125 - libreoffice-base: c/p from calc to create table, character_data does not exist on postgresql

[Stéphane Aulery]

Lionel Elie Mamane committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=a70586d9980d71bd3310fcda69f16ac1dafae2d4

fixup tdf#92538

It will be available in 5.2.0.

--
Stéphane Aulery

Bug#808125: Re : Bug #808125 - libreoffice-base: c/p from calc to create table, character_data does not exist on postgresql

[Stéphane Aulery]

Lionel Elie Mamane committed a patch related to this issue.
It has been pushed to "master":

http://cgit.freedesktop.org/libreoffice/core/commit/?id=ac2505632c96b2653aea2d65178053d1ad9430ef

tdf#92538 use proper schema name for type names

It will be available in 5.2.0.

--
Stéphane Aulery

Bug#760591: Close 760591 760869

[Stéphane Aulery]

Le 03/03/2016 19:54, Stéphane Aulery a écrit :


Le 03/03/2016 18:43, B a écrit :

On Thu, 3 Mar 2016 18:27:19 +0100 (CET)
Stéphane Aulery <saul...@free.fr> wrote:

I too can't reproduce it in 5.0.5.2; IIRC, it was fixed 2 versions
away from the one of the bug report.


Ok. I close them.

--
Stéphane Aulery

Bug#760591: Bug#760869: Bug #760869 libreoffice-calc: Sometimes replaces all instances instead of choosen cellspresent anymore

[Stéphane Aulery]

Hello B,

Le 03/03/2016 18:43, B a écrit :

On Thu, 3 Mar 2016 18:27:19 +0100 (CET)
Stéphane Aulery <saul...@free.fr> wrote:

Whao, for a bug originated on 2014-09-08… A slight ignition delay? ;-p)


The maintainer is (a little) overwhelmed by the amount of bugs to follow 
in parallel to the LO publishing rhythm which is fast. so, I do a full 
review.


Even older bugs with reports on Debian and LO tracker are not yet fixed, 
or are new bugs for upstream. I have no qualms at all forward, you never 
know.




I too can't reproduce it in 5.0.5.2; IIRC, it was fixed 2 versions
away from the one of the bug report.


Ok. I close them.


> And, please, for the sake of understanding when very old bugs, include
> the original bug's text.

Ok, thanks for yours help.

Regards,

--
Stéphane Aulery

Bug#760591: Bug #760591 - libreoffice-calc: Mouse copy is wrong

[Stéphane Aulery]

Hello B,

Can you reproduce this bug with a newer version (backports) please?

Regards,

-- 
Stéphane Aulery

Bug#760869: Bug #760869 libreoffice-calc: Sometimes replaces all instances instead of choosen cellspresent anymore

[Stéphane Aulery]

tags 760869 + moreinfo
stop


Hello B,

I can't reproduce this bug with LO 5.0.5. The following report describe that 
the checkbox "Limit to selection only" is cleared after replace:

https://bugs.documentfoundation.org/show_bug.cgi?id=44837

Does it be what you are describing?

Regards,

-- 
Stéphane Aulery

Bug#781087: Bug #781087 - libreoffice-impress: impress animation "strechy" dosn't work with drawings

[Stéphane Aulery]

forwarded 781087 https://bugs.documentfoundation.org/show_bug.cgi?id=63443
tags 781087 + upstream
tags 781087 + moreinfo
stop
-

Hello Wolfgang,

I think yours bug is similar to this other bug :

https://bugs.documentfoundation.org/show_bug.cgi?id=63443

Can you send me the output of "lsusb" and "lspci" commands please?

If you can test with a newer version of LO (from backports maybe), it's fine.

Regards,

-- 
Stéphane Aulery

Bug#781493: Bug #781493 - libreoffice-writer: Page number field does not increment

[Stéphane Aulery]

tags 781493 + moreinfo
tags 781493 + upstream
stop
-

Hello David,

Does this bug fits your problem?

 https://bugs.documentfoundation.org/show_bug.cgi?id=34502

Did you make a merge?

Can you test with a newer version please?

Regards,

-- 
Stéphane Aulery

Bug#811474: Re : Bug#811474: Bug #811474 - libreoffice-calc: LibreOffice Calc forces workspace switch when its window is acted on

[Stéphane Aulery]

fixed 811474 1:5.0.5~rc2-1~bpo8+2
stop
-

Good morning David,

- David Guyot <david.gu...@europecamions-interactive.com> a écrit :
> 
> The problem seeems to have vanished with the backports version. Great!
> Thank you for the suggestion, I didn't think about this.

Nothing, thanks for yours test. I close this bug.

Regards,

-- 
Stéphane Aulery

Bug#668965: Bug #668965 - libreoffice-writer: Libreoffice Writer window does not have focus when I switch to another window and back

[Stéphane Aulery]

Hello Toby,

Can you test with version newer than 4.4 of LO please?

LO devs refuse to receive bug report for an old version.

Regards,

--
Stéphane Aulery

Bug#811474: Bug #811474 - libreoffice-calc: LibreOffice Calc forces workspace switch when its window is acted on

[Stéphane Aulery]

Hello David,

Can you test with version 1:5.0.5~rc2-1~bpo8+2 of LO?

LO devs refuse to receive bug report for an old version.

Regards,

--
Stéphane Aulery

Bug#808476: libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[Stéphane Aulery]

Le 02/03/2016 20:26, nicolas.patr...@gmail.com a écrit :

Le 25/02/2016 18:17:24, Stéphane Aulery a écrit :


I have forwarded your bug report to LibreOffice devs and they request
a document for reproducing the behaviour.



Could you send me one document please ?


Here is a simple text document with the error.
The used and bugged symbol is 픽.

Thanks for your help. I forward the document and comments.

--
Stéphane Aulery

Bug#815565: Re : Bug #815565 - libreoffice: recreating table of content on existing documents, page are numbered using Capital Letter (C, D, ...)

[Stéphane Aulery]

Hello,

Do you have a document to reproduce the bug please?

Regards,

--
Stéphane Aulery

Bug#795513: Re : Bug#795513: Bug #795513 libreoffice-core: Styles crashing X

[Stéphane Aulery]

fixed 795513 1:5.0.5~rc2-1
stop
-

Le 01/03/2016 20:16, Jason Woofenden a écrit :

My last email about testing was with libreoffice version: 1:5.0.5~rc2-1

Sorry I forgot to include that. Is reportbug making me
lazy/forgetful?


No, I could also immediately clarify my question.

Another bug eradication, Jason thank you!

--
Stéphane Aulery

Bug#664706: python-uno: RuntimeError from unopkg on upgrade

[Stéphane Aulery]

Hello Ben,

I saw that since you have done extensive testing on other bugs with LO. 
I assume that you no longer met the problem described in this bug.

I am wrong ?

Regards,

--
Stéphane Aulery

Bug#795513: Re : Bug#795513: Bug #795513 libreoffice-core: Styles crashing X

[Stéphane Aulery]

- Jason Woofenden <ja...@jasonwoof.com> a écrit :
> 
> I can no longer reproduce this bug.
> 
> I am able to open the styles and formatting sidebar via the icon or
> the menu, and it does not crash Xorg either way.

Please with what version?

-- 
Stéphane Aulery

Bug#795513: Re : Bug#795513: Bug #795513 libreoffice-core: Styles crashing X

[Stéphane Aulery]

Hi Jason,

- Jason Woofenden <ja...@jasonwoof.com> a écrit :
> 
> Thank you for putting some time into this.

:))


> I skimmed those bug reports, and none of them seem to be about Xorg
> crashing (which is the problem reported here).
> 
> I'm having a little trouble wrapping my brain around how to get a
> backtrace of a graphical program as Xorg crashes... probably
> possible with screen. But I don't know if that would help because
> localc isn't crashing, it's closing because Xorg is going down.

Does it work if you launch it with a linux console?


> I'll test if I can still reproduce this bug, and report back soon.
> There have been kernel, xorg and localc updates since this bug
> report, maybe it's better now.

That's all I wish :))

Regards,

-- 
Stéphane Aulery

Bug#705605: libreoffice-impress: Export to .pptx screws up several formattings

[Stéphane Aulery]

Hello Nick,

These two points seems fixed but there are a lot of bugs opened about 
wrong PPT/PPTX export:



2) background colors of text boxes are changed;
3) wrapping of text boxes is removed.



Point 1 persists :

https://bugs.documentfoundation.org/show_bug.cgi?id=98309


With yours document I have find two others bugs, reported upstream :

https://bugs.documentfoundation.org/show_bug.cgi?id=98310
https://bugs.documentfoundation.org/show_bug.cgi?id=98311

Regards,

--
Stéphane Aulery

Bug#709180: libreoffice: zoom of document is changing by mouseover

[Stéphane Aulery]

Hello Keywan,

Can you still reproduce this old bug with a current version of LibreOffice 
please?

I can't, so, if you can't, I close it.

Regards,

-- 
Stéphane Aulery

Bug#712550: libreoffice: Writer inserts blank pages in form letters

[Stéphane Aulery]

forwarded 712550 
tags 712550 + upstream
tags 712550 - unreproducible
tags 712550 - moreinfo
tags 712550 + confirmed
stop
-

I can reproduce it with 5.0.1.3 (on Windows) and report it to upstream.

-- 
Stéphane Aulery

Bug#749831: Bug #749831 libreoffice: LibreOffice mail merge didn't work under Gnome 3

[Stéphane Aulery]

Hello Gary,

Do you still have the document that causes this problem?

Without it we can only close this bug and wait somebody else hit this bug.

Regards,

-- 
Stéphane Aulery

Bug#795513: Bug #795513 libreoffice-core: Styles crashing X

[Stéphane Aulery]

Hello Jason,

There is a bug report on bugs.documentfoundation.org which is almost identical 
and 6 other concerning the conditional formatting:

https://bugs.documentfoundation.org/show_bug.cgi?id=68686

https://bugs.documentfoundation.org/show_bug.cgi?id=93571
https://bugs.documentfoundation.org/show_bug.cgi?id=95039
https://bugs.documentfoundation.org/show_bug.cgi?id=88555
https://bugs.documentfoundation.org/show_bug.cgi?id=91131
https://bugs.documentfoundation.org/show_bug.cgi?id=92372
https://bugs.documentfoundation.org/show_bug.cgi?id=96367

Can you get a backtrace please?

It will help to isolate the bug because this time it resists.

See this page for informations:

https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace

Regards,

-- 
Stéphane Aulery

Bug#700980: Bug #700980 - libreoffice claims file is corrupt when system is out of disk space

[Stéphane Aulery]

Hello Jeff,

LibreOffice devs ask if you can reproduce this bug with the last release 
of LO.


Regards,

--
Stéphane Aulery

Bug#808476: libreoffice-math: Libreoffice math shows 1xxxx utf8 characters incorrectly

[Stéphane Aulery]

Hello,

I have forwarded your bug report to LibreOffice devs and they request a 
document for reproducing the behaviour.


Could you send me one document please ?

Use 808...@bugs.debian.org for it to be archived with bug report.

Thanks for your help.

Regards,

--
Stéphane Aulery

Bug#618278: - libreoffice-writer: In font settings, "bold" and "italic" are "Cursiva" and "Negreta"

[Stéphane Aulery]

Hello Tim,

There may be a link with this bug:

https://bugs.documentfoundation.org/show_bug.cgi?id=79933

The version that you had the bug is too old.
Can you still reproduce it on your current system, please?

Regards,

-- 
Stéphane Aulery

Bug#630466: forwarded 630466 https://bugs.documentfoundation.org/show_bug.cgi?id=98185

[Stéphane Aulery]

forwarded 630466 https://bugs.documentfoundation.org/show_bug.cgi?id=98185
tags 630466 + upstream
stop
-

Forwarded in three reports :

- https://bugs.documentfoundation.org/show_bug.cgi?id=98185
- https://bugs.documentfoundation.org/show_bug.cgi?id=98186
- https://bugs.documentfoundation.org/show_bug.cgi?id=98187

-- 
Stéphane Aulery

Bug#669064: Bug #669064 libreoffice-calc: LibreOffice Calc is not shown in top context menu of xlsx files like for xls files

[Stéphane Aulery]

tags 669064 + moreinfo
stop
-

Hello,

After checking, the XLS and XLSX of mimetypes are correct in LO package.

We have to look in another direction I think.

Regards,

-- 
Stéphane Aulery

Bug#719540: Bug #719540 python3-uno: capitalisePython() takes 0 positional arguments but 1 was given

[Stéphane Aulery]

Hello James Michael,

I can't identify the source file of the sample which cause the bug.
Could you tell me what is the example in question please?

It may have changed.

Regards,

-- 
Stéphane Aulery

Bug#780253: Re : Bug#780253: Re Bug #780253 - libreoffice-writer: LibreOffice has no support for Google Drive

[Stéphane Aulery]

Hi Rene,

- Rene Engelhard <r...@debian.org> a écrit :
> On Thu, Feb 25, 2016 at 12:38:30AM +0100, Stéphane Aulery wrote:
> > Le 24/02/2016 23:41, Rene Engelhard a écrit :
> > >On Wed, Feb 24, 2016 at 07:12:17PM +0100, Stéphane Aulery wrote:
> > >Or I misunderstand the concept of a "secret" here, but I doubt that.
> > >
> > >That said, I see that chromium-browser in Debian also has a 
> > >debian/apikeys...
> > 
> > Ok, forget that. No way to spread this kind of thing!
> 
> Well, actually it is "worse", which makes this actually fixable :)

[Re-]Ok, if necessary really.


> As said, there's debian/apikeys in the chromium source package *and* it even
> is installed to /etc/chromium.d/apikeys.
> This was added back in 2014 with https://bugs.debian.org/748867 - so
> the "Debian Google secrets" are available already.
> 
> Actually I discussed that this night  in #debian-devel (tone: "well, API keys,
> whatever" and with the chromium maintainer (tone: "you can use it, it's in
> /etc/chromium.d/apikeys - maybe you should ask google for permission but I
> don't have a problem with that"
> 
> We could use those.
> 
> Will ask Google for permission.
> 
> And if that works, the patch is even more simple, we don't even need to
> copy it over ;)
> 
> diff --git a/rules b/rules
> index e4d30e8..d1baef8 100755
> --- a/rules
> +++ b/rules
> @@ -430,6 +430,12 @@ LIBCMIS_MINVER=0.5.0-3
>  else
>  LIBCMIS_MINVER=0.5.0
>  endif
> +ifeq "$(DEB_VENDOR)" "Debian"
> +# Google API stuff for GDrive access
> +BUILD_DEPS += chromium (>= 39.0.2171.71-1)
> +include /etc/chromium.d/apikeys
> +CONFIGURE_FLAGS += --with-gdrive-client-id=$(GOOGLE_DEFAULT_CLIENT_ID) 
> --with-gdrive-client-secret=$(GOOGLE_DEFAULT_CLIENT_SECRET)
> +endif
>  SYSTEM_STUFF += jpeg
>  SYSTEM_STUFF += libxml
>  SYSTEM_STUFF += expat

It is a half consolation. I guess the permissions must be correct.

Regards,

-- 
-- 
Stéphane Aulery

Bug#780253: Re Bug #780253 - libreoffice-writer: LibreOffice has no support for Google Drive

[Stéphane Aulery]

Hi Rene,

Le 24/02/2016 23:41, Rene Engelhard a écrit :

On Wed, Feb 24, 2016 at 07:12:17PM +0100, Stéphane Aulery wrote:

This bug has been fixed in Ubuntu.

Maybe the patch is transferable?


No. (Well, maybe.)

Looking at what they did:

   # Set up Google API keys, see 
http://www.chromium.org/developers/how-tos/api-keys .
   # Note: these are for Ubuntu use ONLY. For your own distribution,
   # please get your own set of keys.
   # Permission to add API keys, from Paweł Hajdan, To chad.mil...@canonical.com
   # msgid: caadnaofsfoch68nm1sgpctrxqmspykqguputsf7sgrsrxih...@mail.gmail.com
   # reused from chromium-browser 48.0.2564.82-0ubuntu1.1222
   GOOGLEAPI_APIKEY_UBUNTU := <snipped, but is publically visible in debian/rules 
>
   GOOGLEAPI_CLIENTID_UBUNTU := <snipped, but is publically visible in 
debian/rules >
   GOOGLEAPI_CLIENTSECRET_UBUNTU := <snipped, but is publically visible in 
debian/rules >
   CONFIGURE_FLAGS += --with-gdrive-client-id=$(GOOGLEAPI_CLIENTID_UBUNTU) 
--with-gdrive-client-secret=$(GOOGLEAPI_CLIENTSECRET_UBUNTU)

so no, we can't take that. Of course, we could get ours via the same way
- but then we also could post it somewhere on a public site, it's then no
secret anymore. It's as if we would put passwords publically visible.

Or I misunderstand the concept of a "secret" here, but I doubt that.

That said, I see that chromium-browser in Debian also has a debian/apikeys...


Ok, forget that. No way to spread this kind of thing!

Thanks Rene.

Regards,

--
Stéphane Aulery

Bug#749979: forwarded 749979 https://bugs.documentfoundation.org

[Stéphane Aulery]

forwarded 749979 https://bugs.documentfoundation.org/show_bug.cgi?id=98164
tags 749979 + upstream
tags 749979 + moreinfo
stop
-

He request a list on mandatory fonts to upstream.

--
Stéphane Aulery

Bug#697917: forwarded 697917 https://bugs.documentfoundation.org/show_bug.cgi?id=96902

[Stéphane Aulery]

forwarded 697917 https://bugs.documentfoundation.org/show_bug.cgi?id=96902
tags 697917 + upstream
tags 697917 + confirmed
tags 697917 - wontfix
stop
-

I remove wontfix flag because this bug is know by upstream and I added a 
link to LO bugtracker to this bug.


--
Stéphane Aulery

Bug#731052: retitle 731052 broken extensions without integrity check can crash LO

[Stéphane Aulery]

retitle 731052 broken extensions without integrity check can crash LO
stop
-

Hello,

I added yours report to a request of feature on LO bugtracker :

https://bugs.documentfoundation.org/show_bug.cgi?id=81155

Extension Manager: Integrity Check mechanism should be implemented to 
avoid installing broken extensions


Regards,

--
Stéphane Aulery

Bug#677484: Re Bug #677484 - Libreoffice Menu / submenu overlapping

[Stéphane Aulery]

Hello jEsuSdA,

I know it's been a long time you sent this bug report. :) Meanwhile LO 
has changed a lot.


I could not find a similar bug in the bugtracker LO.

Could you, please, try again if this bug is present with a new version?
If present I will report to LO, otherwise I'll close this bug

Thanks for your help.

Regards,

--
Stéphane Aulery

Bug#780253: Re Bug #780253 - libreoffice-writer: LibreOffice has no support for Google Drive

[Stéphane Aulery]

Hello Rene,

This bug has been fixed in Ubuntu.

Maybe the patch is transferable?

Regards,

 Message transféré 
Sujet : [Bug 1389936] Re: LibreOffice has no support for Google Drive
Date : Tue, 23 Feb 2016 11:04:38 -
De : Launchpad Bug Tracker <1389...@bugs.launchpad.net>
Répondre à : Bug 1389936 <1389...@bugs.launchpad.net>
Pour : dispa...@tracker.debian.org

This bug was fixed in the package libreoffice - 1:5.1.0-0ubuntu1

---
libreoffice (1:5.1.0-0ubuntu1) xenial; urgency=medium

  * finalize version, rc3 = 5.1.0
  * depend on libreoffice-sdbc-hsqldb from 
libreoffice-subsequentcheckbase for

autopkgtests
  * add libreoffice-style-elementary from upstream (LP: #1483914)
  * continue building libreoffice-gtk3, but dont default-deploy (yet)
  * use system ucpp instead of bundling (LP: #1524638)
  * add google drive bits (LP: #1389936)
  * update indic fonts package names (LP: #958345)

 -- Bjoern Michaelsen   Sun, 21 Feb
2016 15:23:45 +0100

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Released

--
You received this bug notification because you are subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389936

Title:
  LibreOffice has no support for Google Drive

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 14.04
  LibreOffice 4.2.7
  also LibreOffice 4.2.7 and later from ppa 
https://launchpad.net/~libreoffice/+archive/ubuntu/ppa


  Steps to Reproduce:
  1) Select check box: Tool -> Options -> General -> Open/Save Dialog - 
Use LibreOffice dialog

  2) Open: File -> Open...
  3) Click "Server" in the top right corner of the dialog.
  4) Select "CMIS" in the drop-down list "Type"

  The drop-down list "Type Server" has not the item "Google Drive".
  I was expecting LibreOffice to be built with --with-gdrive-client-id 
--with-gdrive-client-secret and Google Drive is available.


  Methods  work around:
  1) setup with the site LibreOffice.
  2) Buid with flags --with-gdrive-client-id 
--with-gdrive-client-secret independently.

  but it is very annoying :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1389936/+subscriptions

Bug#711166: Bug #711166 libreoffice-impress: Slideshows have to X-windows title bar title

[Stéphane Aulery]

Hello,

It's not a Debian specific bug. I can reprodure it with LO 5.0.1.2 under 
Windows.

Regards,

-- 
Stéphane Aulery

Bug#790903: GBK encoded Chinese text not auto-detected

[Stéphane Aulery]

tags 790903 + upstream
tags 790903 - unreproducible
forwarded 790903 https://bugs.documentfoundation.org/show_bug.cgi?id=92161
stop
-

According to comment #5 for Bug #92161 form LO bugtracker, Chinese support is 
yet embryonic!

https://bugs.documentfoundation.org/show_bug.cgi?id=92161

-- 
Stéphane Aulery

Bug#747132: libreoffice: The metapackage libreoffice should not recommend liberation fonts

[Stéphane Aulery]

Hello,

IMHO recommanding fonts with libreoffice-core package is a good idea.

In absolute terms would rather meta packages that install the desktop 
environments,
which should be responsible for recommending fonts for all office suites.

Regards,

-- 
Stéphane Aulery

Bug#665094: 665094 fixed-upstream

[Stéphane Aulery]

forwarded 665094 https://bugs.documentfoundation.org/show_bug.cgi?id=32248
tags 665094 + confirmed
tags 665094 + fixed-upstream
stop

--

See https://bugs.documentfoundation.org/show_bug.cgi?id=32248#c70

and 

http://cgit.freedesktop.org/libreoffice/core/commit/?id=dc3eb865bd10e690dbf80f41277b062ac2253572

for the patch.

It will be available in 5.2.0.

-- 
Stéphane Aulery

Bug#623232: Re : Libreoffice takes up 100% CPU time + all memory when opening certain files

[Stéphane Aulery]

tags 623232 + confirmed
tags 623232 + upstream
stop
---


Hello Hans and Leandro,


   From: Hans Linkels <jlink...@rnw.an>
   To: sub...@bugs.debian.org
   Subject: Libreoffice takes up 100% CPU time + all memory when 
opening

   certain files
   Date: Mon, 18 Apr 2011 11:00:22 -0400

Package: libreoffice-writer
Version: 1:3.3.2-2
Severity: normal

When I try to open a certain file (saved with Microsoft Office 2007(??) 
)

as .DOC file, LibreOffice takes up 100% CPU time and starts to use all
available memory, until memory and swap is fully exhausted. File size 
about

2.5 MB. Other files, saved in the same format and on the same Windows
computer of larger size (7MB) open without problems.
Unfortunately this file is on a computer of a co-worker several 
thousand miles
away, I can't play around with saving the file differently or 
experimenting.

I have placed the problematic file here:
http://pdis.rnw.nl/~hansl/links/BTPU%2001%20deel%202%20duurzame%20enegie%20rappo
rt.doc

   Message #10 received at 623...@bugs.debian.org (full text, mbox,
   reply):

   From: Leandro Guimarães Faria Corcete DUTRA
   <leandro.du...@camara.gov.br>
   To: 623...@bugs.debian.org
   Date: Tue, 18 Oct 2011 19:22:49 -0200

I have the same issue here, but under versions 3.4.3-3 and 3.4.3-4.



--
Leandro Guimarães Faria Corcete DUTRA  leandro.du...@camara.gov.br  
7244
Analista de Informática Legislativa Seção de Especificação de 
Ativos
Coordenação de Relacionamento com Cliente  +55 (61) 3216 3603, 3216 
3515
Centro de Informática, Câmara dos Deputados   Anexo I, sala 
1108



   Message #15 received at 623...@bugs.debian.org (full text, mbox,
   reply):

   From: Leandro Guimarães Faria Corcete DUTRA
   <leandro.du...@camara.gov.br>
   To: 623...@bugs.debian.org
   Subject: Additional information
   Date: Wed, 19 Oct 2011 14:01:02 -0200

The culprit file also dies when I tried turning off modification
tracking and applying all changes.  I also noticed it has grown too
much, from just over 40 KiB to more than 120 KiB.  Opening it in GNU
Emacs, I see most of it is at contents.xml; opening that and searching
for text last edited, GNU Emacs also freezes until some other buffer
gets focus (for example, ERC loosing its connection), so I guess XML is
so screwed up the Emacs XML mode gets lost.  less also seems to die, 
but

I could not guess why.


If you have yet yours culprit files, you can add them to this bug report 
:


https://bugs.documentfoundation.org/show_bug.cgi?id=39006

Regards,

--
Stéphane Aulery

Bug#679323: clearenv(3): implies that it's a security tool

[Stéphane Aulery]

tags 679323 + fixed-upstream
stop

-

Will be fixed in man-pages-4.04.

See commit c66649c8359865ff2a464e5b82284e6b1acf 
by Michael Kerrisk <mtk.manpa...@gmail.com>, 2016-02-19 12:04:51 (GMT)

https://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/man3/clearenv.3?id=c66649c8359865ff2a464e5b82284e6b1acf



- Matt Zimmerman <m...@debian.org> a écrit :
> On Fri, Feb 19, 2016 at 12:59:05PM +0100, Michael Kerrisk (man-pages) wrote:
> > On 18 February 2016 at 21:34, Matt Zimmerman <m...@debian.org> wrote:
> > > Thanks for following up.  My recommendation is to say something like:
> > >
> > > This function DOES NOT securely erase the contents of the environment.
> > > Security-conscious applications which need to do this should use 
> > > instead.
> > 
> > So, I think this report is a little confused, but mainly because of
> > the poor description in the man page.
> > 
> > The security-conscious applications in this context are those that
> > want to precisely control the environment passed to an exec()ed
> > program. clearenv() cannot, indeed must not, try to erase the buffers
> > containing the environment definitions. (See putenv(3) to understand
> > why.) I've adjusted the man page in away that I hope explains things
> > better:
> > 
> >The  clearenv()  function  may  be  useful  in security-conscious
> >applications that want to precisely control the environment  that
> >is  passed  to  programs executed using exec(3).  The application
> >would do this by first clearing the environment and  then  adding
> >select environment variables.
> > 
> >Note that the main effect of clearenv() is to adjust the value of
> >the pointer environ(7); this function does not erase the contents
> >    of the buffers containing the environment definitions.
> 
> Yes, that's much clearer, thank you!

Case classified, thank you for your help Matt and Michael!

Regards,

-- 
Stéphane Aulery

Bug#679323: clearenv(3): implies that it's a security tool

[Stéphane Aulery]

Hello Michael and Matt,

- Michael Kerrisk (man-pages) <mtk.manpa...@gmail.com> a écrit :
> On 18 February 2016 at 21:34, Matt Zimmerman <m...@debian.org> wrote:
> > Thanks for following up.  My recommendation is to say something like:
> >
> > This function DOES NOT securely erase the contents of the environment.
> > Security-conscious applications which need to do this should use 
> > instead.
> 
> So, I think this report is a little confused, but mainly because of
> the poor description in the man page.
> 
> The security-conscious applications in this context are those that
> want to precisely control the environment passed to an exec()ed
> program. clearenv() cannot, indeed must not, try to erase the buffers
> containing the environment definitions. (See putenv(3) to understand
> why.) I've adjusted the man page in away that I hope explains things
> better:
> 
>The  clearenv()  function  may  be  useful  in security-conscious
>applications that want to precisely control the environment  that
>is  passed  to  programs executed using exec(3).  The application
>would do this by first clearing the environment and  then  adding
>select environment variables.
> 
>Note that the main effect of clearenv() is to adjust the value of
>the pointer environ(7); this function does not erase the contents
>of the buffers containing the environment definitions.


It's much better that I can do.
If no objection Matt,
I pass the bug report in fixed-upstream.


Regards,

-- 
Stéphane Aulery

Bug#95444: Bug 95444 fixed upstream in man-pages-3.83

[Stéphane Aulery]

tags 95444 + fixed-upstream
tags 95444 + pending
fixed 95444 4.04-0.1
stop

-

Fixed upstream in man-pages-3.83.

See commit e20476d37019777315c3f284b61bfaa314393760

Michael Kerrisk <mtk.manpa...@gmail.com>, 2015-04-12 07:43:27 (GMT)

https://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/man3/strcasecmp.3?id=e20476d37019777315c3f284b61bfaa314393760

-- 
Stéphane Aulery

Bug#679323: clearenv(3): implies that it's a security tool

[Stéphane Aulery]

Hello Matt,

Le 18/02/2016 21:34, Matt Zimmerman a écrit :

Thanks for following up.  My recommendation is to say something like:

This function DOES NOT securely erase the contents of the environment.
Security-conscious applications which need to do this should use 
instead.


Thanks for your reply. To match the note recommending a solution of 
withdrawal, then I suggest:


-

If it is unavailable the assignment

environ = NULL;

will probably do.

But these solutions DO NOT securely erase the contents of the 
environment. ecurity-conscious applications which need to do this should 
use [...] instead.




Problem, I have no idea of good security practice. A helping hand, please?

Regards,

--
Stéphane Aulery

Bug#794947: manpages-dev: printf(3) example: possible integer overflow

[Stéphane Aulery]

Hello Walter,

Le 17/02/2016 22:13, walter harms a écrit :


Jakub Wilk reported a possible integer overflow in make_message example :


The example in the printf(3) manpages looks like this (with boring parts
omitted):

int n;
/* ... */
   n = vsnprintf(p, size, fmt, ap);
/* ... */
if (n < 0) {
/* ... */
return NULL;
}
/* ... */
size = n + 1;


But vsnprintf could return INT_MAX, which would then cause "n + 1" to
overflow.

(AFAICS, the glibc vsnprintf implementation never returns INT_MAX, but
it could in principle.)

I'd suggest changing "n < 0" to "n < 0 || n == INT_MAX".




the bug is real, the type of size should be size_t (in my original post it was 
int)
That would make the error check useless, so we would need to store
the vsnprintf return value in an int.

The problem is that the idea was to have a simple example and cluttering
it with error checks will make it hard to read. How many people would
notice that size_t is unsigned and n is signed ? (i added an comment).

IMHO we should simply add a sentence that "examples are examples and
will not check for every possible error condition."



I agree with the general idea: the examples must remain so. They must 
also be correct. Tough choice!


I will not put a note on this page about it, nor on the other, too much 
for so little.


man-pages.7 specifically requests:

 Example programs shoulds be fairly short (preferably less than 100 
lines;

 Ideally less than 50 lines).

 Example programs shoulds do error checking after-system calls and
 library function calls.

So I will do a patch with your new corrected version that is very readable.

Thanks a lot for your help.

Regards,

--
Stéphane Aulery

Bug#679323: clearenv(3): implies that it's a security tool

[Stéphane Aulery]

severity 679323 minor
stop
-

Hello Matt,

I dig your bug reports about the clearenv() function.

Does the sentence below would do, please?


   Used by security-conscious application, with the reservation
   that the memory is not zeroed by the glibc implementation
   before release.


Regards,

-- 
Stéphane Aulery

Bug#794876: manpages-dev: Should guide users away from deprecated sys_errlist more

[Stéphane Aulery]

First commit of upstream to fix this bug:

Michael Kerrisk <mtk.manpa...@gmail.com>
2016-02-08 15:23:13 (GMT)
88cc4cb6cc7d95f2389061d69a9692b7633b54e2

https://git.kernel.org/cgit/docs/man-pages/man-pages.git/commit/man3/perror.3?id=88cc4cb6cc7d95f2389061d69a9692b7633b54e2

-- 
Stéphane Aulery