Red Hat Bugzilla – Bug 146580
Paste in Calc shifts cells by default
Last modified: 2007-11-30 17:10:59 EST
Description of problem:
The default paste behavior in Calc shifts cells, which is both
non-standard and unseen in the previous release. (And is redundant
with an option provided in Paste Special.)
Version-Release number of selected component (if applicable):
confirmed, this was caused by an upstream ooo-build patch added by
Novell that we'll have to disable.
Specific changelog entry is:
2005-01-27 Michael Meeks <firstname.lastname@example.org>
* patches/OOO_1_1_4/apply, patches/OOO_1_1_3/apply:
disable sc-paste-insert-rows.diff, very odd / unexpected
behavior hurting users.
Dan, I just stumbled across this bug as well, any plans to re-release?
This bug makes using calc basically useless, I totally screwed up a complex
spreadsheet layout today as parts of columns and rows got pushed around during a
series of pastes... ugh.
Shouldn't this be high priority?
Ian, agreed, although I can't prioritize. :)
How about we just bump up the severity as this is a nearly
*** Bug 146872 has been marked as a duplicate of this bug. ***
Confirmed that this bug appears on multiple distributions, see:
Oddly enough the OOo folks don't appear to think it's their problem.
Somebody hit them with a clue stick please.
Technically its not their problem as the code is a patch in the
ooo-build sources. Vendors like Red Hat, Novell, Suse, and Debian use
common sources and patches from ooo-build.
Wasn't there a plan to have an update out late last week?
Build is pushed to rawhide already, and an FC-3 updates-testing build
will be available soon... (its built already and needs to be mirrored)
Dan, is this new build going to also fix the "cannot unhide a row"
No, unfortunately, that's a separate beast... :( Hopefully next
update after this one.
Can you give us a guestimate as to when the FC3 patch will be released?
Its been pushed and will trickle out to mirrors in the next 24 hours
Please check if bug 146883 is not related. It have appeared in the
same release, and is also very painful.
No, bug 146883 is not related.