Bug 164859 - Solver data not showing when switching from Windows to Linux
Summary: Solver data not showing when switching from Windows to Linux
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
24.8.4.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Solver
  Show dependency treegraph
 
Reported: 2025-01-26 08:33 UTC by mobilen
Modified: 2025-12-26 03:20 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mobilen 2025-01-26 08:33:58 UTC
Description:
Solver data works fine in Windows. You can enter data and it is still there when opening the document another time, but opening the same document in Linux the Solver data is emtpty. Saving the same document with no visible Solver data in Linux and the opening the saved document i Windows, the Solver data is back as if the document was never saved in Linux (without visible Solver data).

Steps to Reproduce:
1.Enter data in Solver dialog box
2.Save document in Windows
3.Open document in Linux
4.Check data in Solver dialog box (apparently empty)
5.Change something (not Solver data) in document
6.Save document in Linux
7.Open document in Windows
8.Check Solver dialog box (should be data originally saved ther now)


Actual Results:
As described

Expected Results:
Solver data should be visible regardless of operating system document is opened from.


Reproducible: Always


User Profile Reset: No

Additional Info:
Can't copy info - writing bug from telephone, but using latest official version in Windows 10 and Linux Mint (all op's updated).
Comment 1 Mike Kaganski 2025-01-26 11:17:59 UTC
(In reply to mobilen from comment #0)
> Can't copy info - writing bug from telephone, but using 
> version in Windows 10 and Linux Mint (all op's updated).

Find a way and do copy the infos. The "latest official version" means nothing - especially with Mint, which has its own (or rather, Ubuntu's own) package managing system, with packages available for you depending on the OS version - which you also didn't mention. And if, as I suspect, the version that you use on Mint is old, then please test with a current version there.
Comment 2 Rafael Lima 2025-01-26 22:56:04 UTC
What's the exact LibreOffice version you're using on Windows and Linux? Please, copy the info in Help - About and paste it here.

You may be using an outdated version of LibreOffice on Windows.

On my PC I'm using this version on Windows:

Version: 24.8.4.2 (X86_64) / LibreOffice Community
Build ID: bb3cfa12c7b1bf994ecc5649a80400d06cd71002
CPU threads: 4; OS: Windows 10 X86_64 (10.0 build 19045); UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

And on Linux I'm using:

Version: 24.8.4.2 (X86_64) / LibreOffice Community
Build ID: 480(Build:2)
CPU threads: 16; OS: Linux 6.11; UI render: default; VCL: kf6 (cairo+wayland)
Locale: pt-BR (pt_BR.UTF-8); UI: en-US
Ubuntu package version: 4:24.8.4-0ubuntu0.24.10.1
Calc: threaded

I created a Calc file on Windows (ods extension), created a sample solver model and saved the file. Then I opened it on Linux and all the solver info was there.
Comment 3 QA Administrators 2025-11-25 15:23:27 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2025-12-26 03:20:21 UTC
Dear mobilen,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp