After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 589566 - typed text does not appear in spreadsheet cell
typed text does not appear in spreadsheet cell
Status: RESOLVED DUPLICATE of bug 575267
Product: Gnumeric
Classification: Applications
Component: Main System
1.8.x
Other All
: Normal minor
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2009-07-24 03:52 UTC by Jay
Modified: 2009-07-24 06:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jay 2009-07-24 03:52:58 UTC
Please describe the problem:
I opened Gnumeric, and I created a spreadsheet. I typed simple characters into the spreadsheet.  a in one cell, b in another cell, etc.  Then I saved the spreadsheet and exited the Gnumeric application.  If I open the spreadsheet again by double clicking on the filename icon, there's no problem.  I can easily modify it or add cells.  But if I open the Gnumeric application, then open the spreadsheet by using the "file/open" command,  I can no longer enter data into the spreadsheet.  When I click on an empty cell and type something, it doesn't appear in the cell.

Steps to reproduce:
1. Open the Gnumeric application
2. Open a Gnumeric spreadsheet using 'file/open'
3. type something into an empty cell


Actual results:
Nothing appears in the cell

Expected results:
I would expect that the text I type appears in the cell

Does this happen every time?
yes

Other information:
I'm using Fedora 11 with the Gnumeric application installed from the add/remove programs menu
Comment 1 Andreas J. Guelzow 2009-07-24 06:48:44 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 575267 ***