Red Hat Bugzilla – Full Text Bug Listing
|Summary:||libreoffice calc standard filter doesn't show criteria after file re-open|
|Product:||[Fedora] Fedora||Reporter:||Stan King <stanley.king>|
|Component:||libreoffice||Assignee:||Eike Rathke <erack>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||17||CC:||caolanm, dtardon, erack, ltinkl, mstahl, sbergman|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2012-08-18 20:27:38 EDT||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Stan King 2012-07-07 17:09:43 EDT
Created attachment 596813 [details] A libreoffice calc spreadsheet with a simple standard filter. Description of problem: With the most recent version of libreoffice calc on Fedora 17, when I open a spreadsheet file in which I've defined a standard filter before saving it, the filter criteria are still applied, but when editing it, the comparison criteria (after the equal sign or whatever) appear blank. If I open spreadsheet files that I created last year, I don't see this problem. Also, a file exhibiting this problem on Fedora 17 looks OK when viewed from LibreOffice 3.4.2 on Windows 7. I'll try to attach a file which exhibits this. Version-Release number of selected component (if applicable): rpm info: libreoffice-calc-126.96.36.199-4.fc17.x86_64 additional info from the "about" box: Build ID: 350m1(Build:2) How reproducible: Every time. Steps to Reproduce: 1. Create a new spreadsheet, enter some data, and impose a standard filter on it. 2. Save the file, then exit LibreOffice. 3. Open the file; you'll see the criteria applied, but they'll appear blank in the criteria editor. Actual results: Blank criteria in the standard filter editor. Expected results: Expect to see the previously-saved criteria in the standard filter editor. Additional info:
Comment 1 Stan King 2012-07-07 17:13:39 EDT
Created attachment 596814 [details] Example of blank standard filter criteria when I open the attached spreadsheet.
Comment 2 Eike Rathke 2012-07-09 13:02:37 EDT
Comment 3 Eike Rathke 2012-07-10 05:20:37 EDT
Upstream 3-5, so will be included in 3.5.6 http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-3-5&id=22ccbeef9c88b01ac841de37dfcb5985dc05a530
Comment 4 Fedora Update System 2012-08-01 15:42:40 EDT
libreoffice-188.8.131.52-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/libreoffice-184.108.40.206-5.fc17
Comment 5 Fedora Update System 2012-08-02 07:23:57 EDT
Package libreoffice-220.127.116.11-5.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreoffice-18.104.22.168-5.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11418/libreoffice-22.214.171.124-5.fc17 then log in and leave karma (feedback).
Comment 6 Stan King 2012-08-03 02:21:56 EDT
I'd love to try this out, but when doing the above "yum" command, I get the following message: Package(s) libreoffice-126.96.36.199-5.fc17 available, but not installed. No Packages marked for Update On my machine, I have a number of packages whose names are libreoffice- followed by a component name, but nothing named just "libreoffice". Do I need to specify the components manually? If so, which ones?
Comment 7 Caolan McNamara 2012-08-03 05:16:58 EDT
try yum update --enablerepo=updates-testing libreoffice-calc-188.8.131.52-5.fc17
Comment 8 Stan King 2012-08-04 17:02:09 EDT
That did the trick, Caolan. Thank you. I've deposited some good karma.
Comment 9 Fedora Update System 2012-08-09 02:56:56 EDT
libreoffice-184.108.40.206-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/libreoffice-220.127.116.11-1.fc17
Comment 10 Fedora Update System 2012-08-18 20:27:38 EDT
libreoffice-18.104.22.168-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.