ver. 4.2 copy/paste bug - update

On Feb. 17, I posted about this problem. I got several potentially useful responses. With the limited time available to me, I've explored them all, and here's the present status of this problem:

1. I'm running ver. 4.2.1.1 now.

2. The problem reported earlier is still very much with me. I typically begin my day by running a macro that opens 8 Calc spreadsheets, including several that are rather large. I use these to organize my day and track certain complex tasks. I've been doing since 2005, and using LO/Calc to do it since 2008.

I've tried deleting my user profile. I can reproduce the error _immediately_, with the only profile change in place being a lowering of the macro security level to the lowest level to allow me to actually USE my spreadsheets. So, this doesn't appear to be a user-profile corruption issue.

3. Here's the problem:

a. I move some cells from one sheet in a Calc document to a higher location in the same sheet.

b. This messes up some linked formulas, so I copy two cells that are correct down through all the others (normally this works OK). to relink the formula.

c. Immediately and I get this error message:

/vector::_M_range_check

/...closing the error message modal window immediate crashes the whole problem.

I'd attempt a bug report, but every time I've tried that I've gotten lost in the sheer strangeness of the process. I just can't take the time to try to wrestle through the process, which is certainly not set up for average users, I'd say.

I can offer to share the spreadsheet in which the crash occurs, for what that's worth. It has maybe 30 sheets and is about a meg. in size. I did find that removing about 15 of the sheets appeared to stop the problem, for unknown reasons.

I'll continue to use ver. 4.2x, as I seem to have a workaround figured out, and hope that this gets fixed in future releases.

Tom

Tom,

Issue with Calc were one of the reasons that the ESC is moving directly to a 4.2.2 release.

Grab the current TinderBox build of LODev 4.2.3 and install that to see if it has corrected behavior with your corrupted formulas. http://dev-builds.libreoffice.org/daily/libreoffice-4-2/Win-x86@42/current/

Most of the patches applied there will be in the upcoming 4.2.2 posting.

Stuart

UPDATE:

To recap - the dev version you refer me to below is for Windows. I run Kubuntu Linux 13.11.

So I located and installed the LibreOfficeDev_4.3.0.0.alpha0_Linux_x86_deb package - the only 32 bit package I could find that looked like it might be the Linux equivalent of the version you referred me to.

Initially, I could figure out how to launch it (one uses libreofficedev4.3, not libreoffice4.3), but I got that figured out this morning.

Sadly, there's no fix of my problem, plus I seem to have some alpha version bugs to deal with. I've had 3 crashes so far, but am making progress. However, all this noise is hardly productive for me, and I have to be productive, so I'm returning to 4.2.1.1, for which I at least have a workaround for my "vector::_M_range_check" problem.

If there's some other package I should have installed, let me know and I'll try it, but right now it looks like this issue isn't even on anyone's radar.

Tom

Tom,

To recap - the dev version you refer me to below is for Windows. I run Kubuntu Linux 13.11.

Sorry for the misunderstanding on my part, I did not realize you were on -- kubuntu.

3. Here's the problem:

a. I move some cells from one sheet in a Calc document to a higher
location in the same sheet.

b. This messes up some linked formulas, so I copy two cells that are
correct down through all the others (normally this works OK). to relink
the formula.

c. Immediately and I get this error message:

/vector::_M_range_check

/...closing the error message modal window immediate crashes the whole
problem.

I can offer to share the spreadsheet in which the crash occurs, for what
that's worth. It has maybe 30 sheets and is about a meg. in size. I did
find that removing about 15 of the sheets appeared to stop the problem,
for unknown reasons.

The primary developers for Calc have been on top of issues with the major code refactoring done for the 4.2.0 release.
So, if you can attach your problem spreadsheet to a FDO hosted Bugzilla report with precise Steps to Reproduce the issue that is the best way to assure that the issue gets attention.

I'd attempt a bug report, but every time I've tried that I've gotten
lost in the sheer strangeness of the process. I just can't take the time
to try to wrestle through the process, which is certainly not set up for
average users, I'd say.

In truth filing is pretty straight forward, but you'll need to register an account to submit. Two choices: one guided with the Bug Submission Assistant (BSA) -> https://www.libreoffice.org/get-help/bug/ or directly into the Bugzilla interface at http://bugs.libreoffice.org/ (currently a link to bugs.freedesktop.org hosted BZ). For either case, give it a descriptive title and you'd report against:

Product: LibreOffice
Version: 4.2.1.1 release
Component: Spreadsheet
Platform: x86(IA32), Linux -- once we get a look at your attached spreadsheet we'd confirm and expand the platform against other platforms.

And If you file, and please do so we can confirm and get this attended to, post back with the BZ number.

If there's some other package I should have installed, let me know and
I'll try it, but right now it looks like this issue isn't even on
anyone's radar.

Devs sort of expect folks on Linux to roll their own, but as you found there is the nightly TinderBox-45 rolling 32-bit RPM and DEBs of master: http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86@45-TDF/current/

If you can get the kunbutu install done from the DEB, should help identify if the revised code in master has addressed your issues.

Also, there are PPA packaged builds for the Unbutu folks as well, I just checked and a 4.2.2.0 not yet posted. But you could keep an eye on it:

https://launchpad.net/~libreoffice/+archive/ppa
and
https://launchpad.net/~libreoffice/+archive/libreoffice-prereleases for earlier review.

Stuart

Stuart,

Tom,

From: Tom Cloyd...

To recap - the dev version you refer me to below is for Windows. I run Kubuntu Linux 13.11.

Sorry for the misunderstanding on my part, I did not realize you were on -- kubuntu.

That's my fault. I totally erred in not specifying my environment from the start. I know better.

3. Here's the problem:

a. I move some cells from one sheet in a Calc document to a higher
location in the same sheet.

b. This messes up some linked formulas, so I copy two cells that are
correct down through all the others (normally this works OK). to relink
the formula.

c. Immediately and I get this error message:

/vector::_M_range_check

/...closing the error message modal window immediate crashes the whole
problem.

I can offer to share the spreadsheet in which the crash occurs, for what
that's worth. It has maybe 30 sheets and is about a meg. in size. I did
find that removing about 15 of the sheets appeared to stop the problem,
for unknown reasons.

The primary developers for Calc have been on top of issues with the major code refactoring done for the 4.2.0 release.
So, if you can attach your problem spreadsheet to a FDO hosted Bugzilla report with precise Steps to Reproduce the issue that is the best way to assure that the issue gets attention.

I'd attempt a bug report, but every time I've tried that I've gotten
lost in the sheer strangeness of the process. I just can't take the time
to try to wrestle through the process, which is certainly not set up for
average users, I'd say.

In truth filing is pretty straight forward, but you'll need to register an account to submit. Two choices: one guided with the Bug Submission Assistant (BSA) -> https://www.libreoffice.org/get-help/bug/ or directly into the Bugzilla interface at http://bugs.libreoffice.org/ (currently a link to bugs.freedesktop.org hosted BZ). For either case, give it a descriptive title and you'd report against:

Product: LibreOffice
Version: 4.2.1.1 release
Component: Spreadsheet
Platform: x86(IA32), Linux -- once we get a look at your attached spreadsheet we'd confirm and expand the platform against other platforms.

And If you file, and please do so we can confirm and get this attended to, post back with the BZ number.

I just now have some time to use, and so will go and get the filing done, and return as you request, with the BZ number.

If there's some other package I should have installed, let me know and
I'll try it, but right now it looks like this issue isn't even on
anyone's radar.

Devs sort of expect folks on Linux to roll their own, but as you found there is the nightly TinderBox-45 rolling 32-bit RPM and DEBs of master: http://dev-builds.libreoffice.org/daily/master/Linux-rpm_deb-x86@45-TDF/current/

If you can get the kunbutu install done from the DEB, should help identify if the revised code in master has addressed your issues.

Will do just that.

Also, there are PPA packaged builds for the Unbutu folks as well, I just checked and a 4.2.2.0 not yet posted. But you could keep an eye on it:

https://launchpad.net/~libreoffice/+archive/ppa
and
https://launchpad.net/~libreoffice/+archive/libreoffice-prereleases for earlier review.

Stuart

I'll set up access to this.

Thanks Stuart. I much appreciate your willingness to help. I try to give a little pay back and get that report filed.

Tom