Bug 4037

Summary:	LibreOffice Calc error in sorting data in spreadsheet
Product:	Mageia	Reporter:	Margot Lawrence <margot>
Component:	RPM Packages	Assignee:	D Morgan <dmorganec>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	major
Priority:	Normal	Keywords:	Triaged, UPSTREAM
Version:	1
Target Milestone:	---
Hardware:	i586
OS:	Linux
See Also:	https://bugs.freedesktop.org/show_bug.cgi?id=40426
Whiteboard:
Source RPM:	libreoffice-3.4.4.2-0.3.mga1.src.rpm	CVE:
Status comment:

Description Margot Lawrence 2012-01-05 22:18:45 CET

Description of problem:
Since the update to this version this morning, sorting a range of data omits the top row of the range in the sort.

Version-Release number of selected component (if applicable):
LibreOffice Calc 3.4.4.2-0.3.mga1

How reproducible:
Every time

Steps to Reproduce:
1. Create a spreadsheet with data that needs to be sorted - for example, include a column for dates in column E.
2. Select a range of rows in the spreadsheet where the dates have been changed and which therefore needs to be re-sorted back into date order.
3. Discover that, instead of being able to select sorting by column E, the choice is limited to sorting by the information (if any) in the cells in the first row of the range.
4. Discover that the top row of the range is not included in the sort.

I can email a cut-down version of one of my spreadsheets to someone if it would help, but cannot supply the entire spreadsheet as it includes confidential business records - which are now in the wrong order.

Comment 1 Manuel Hiebel 2012-01-06 21:46:26 CET

Hi, thanks for reporting this bug.

In can be an upstream bug, so you can post it at https://bugs.freedesktop.org/ component LibreOffice

anyway assigned to the package maintainer.

Keywords: (none) => Triaged
Assignee: bugsquad => dmorganec

Comment 2 Margot Lawrence 2012-01-06 22:31:18 CET

Manuel,

Thanks for reminding me about upstream - this seems identical to upstream bug #40426. Strangely, this was reported on x86-64 on Windows in August last year, but has only just now appeared in Mageia.

Comment 3 Manuel Hiebel 2012-01-07 17:35:08 CET

(In reply to comment #2)
> Thanks for reminding me about upstream - this seems identical to upstream bug
> #40426. Strangely, this was reported on x86-64 on Windows in August last year,
> but has only just now appeared in Mageia.

Thank you for looking.

Yep we have updated libreoffice from 3.3 to 3.4 :/

Keywords: (none) => UPSTREAM
See Also: (none) => https://bugs.freedesktop.org/show_bug.cgi?id=40426

Comment 4 Manuel Hiebel 2012-11-05 16:52:15 CET

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Comment 5 Manuel Hiebel 2012-12-02 14:31:55 CET

Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX