Bug 129262 - The copy function (Ctrl-C) doesn't work in Calc
The copy function (Ctrl-C) doesn't work in Calc
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dan Williams
Depends On:
  Show dependency treegraph
Reported: 2004-08-05 13:22 EDT by Fred New
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version: openoffice.org-1.1.2-5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-25 02:24:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Fred New 2004-08-05 13:22:58 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040404 Firefox/0.8

Description of problem:
When I try to copy the contents of one cell to another cell using
Ctrl-C and Ctrl-V, nothing copies.  I have concluded that the copy
function isn't working, because I can copy from the Gnome editor, but
not to the Gnome editor.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start OpenOffice.org Calc
2. Put some data in a cell
3. Attempt to copy that data to a different cell using Ctrl-C and Ctrl-V

Actual Results:  Contents not copied.

Expected Results:  Data copied or if the cell contains a formula,
contents copied with changes to match the new location.

Additional info:
Comment 1 Dan Williams 2004-08-05 13:45:44 EDT
Verified. Did this used to work in previous versions?
Comment 2 Fred New 2004-08-06 01:46:34 EDT
Yes, it worked before.  I'm pretty sure it worked with the version
originally installed with FC3T1.
Comment 3 Dan Williams 2004-09-18 11:13:57 EDT
should be fixed in 1.1.2-5, coming soon.  I cannot reproduce it in
this version.
Comment 4 Fred New 2004-09-25 02:24:49 EDT
Yes, I've confirmed that it works for me, too.

Note You need to log in before you can comment on or make changes to this bug.