Description of problem:
In Gnumeric v. 1.8.2 (current version in fc10 repo), when a graph is moved, the graph does not release and anchor itself upon release of the mouse button.
Version-Release number of selected component (if applicable):
Guaranteed, every time. Incredibly annoying.
Steps to Reproduce:
1. In Gnumeric 1.8.2, create a graph
2. Click and hold on graph, drag to a new position.
3. Graph will not release until a "double click"
Graph should release and anchor itself at new position upon release of mouse button.
Graph fails to anchor, requires double to release
This bug is specific to version 1.8.2, and has been corrected in version 1.8.4. It is well known in other Linux distros. See, for example, this Ubuntu bug record: https://bugs.launchpad.net/gnumeric/+bug/316502
Version 1.8.4 is available in the rawhide repo, but upgrading to 1.8.4 with the fc11 rawhide repo requires many, many other updates to fc10.
Still present in Fedora 12 beta.
Requires updating goffice, I believe.
See also https://bugzilla.gnome.org/show_bug.cgi?id=566652 .
This is not a bug of gnumeric, but in goffice. The patches referenced in
comment #1 solve this issue. I'm going to apply the patches from 0.6 branch
of goffice at Fedora - this will fix the issue.
I've applied all missing fixes from the goffice 0.6 branch:
goffice-0.6.6-4.fc10 has been submitted as an update for Fedora 10.
For goffice-0.6.6-4.fc12 see: https://fedorahosted.org/rel-eng/ticket/2612
When these updates be part of the YUM repositories?
I got the update for gnumeric yesterday and goffice today via the F12 rawhide channel. The F11 channel updates hadn't been pushed as of yesterday, I imagine they will trickle in.
It should arrive in updates-testing in the next days.
gnome-chemistry-utils-0.10.8-1.fc10.1, goffice-0.6.6-4.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
goffice-0.6.6-4.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.