gnumeric ignores keyboard input

I see the same thing in gnumeric-1.8.4-3ubuntu1 OS: Jaunty alpha updated today

The problem occurs if I open gnumeric, then use the File->Open process to open a file.
From a terminal window upon opening gnumeric I see the following:

~/.config$ gnumeric

(gnumeric:24916): Gtk-WARNING **: Inserting action group 'FileHistory' into UI manager which already has a group with this name

When I open a file to edit, I get the following:

Reading file:///home/a/.config/2009.gnumeric

(gnumeric:24916): Gtk-WARNING **: Inserting action group 'WindowList' into UI manager which already has a group with this name

** (gnumeric:24916): CRITICAL **: scg_edit_start: assertion `IS_SHEET_CONTROL_GUI (scg)' failed

** (gnumeric:24916): CRITICAL **: wbcg_edit_finish: assertion `IS_SHEET (wbcg->editing_sheet)' failed

(gnumeric:24916): Gtk-WARNING **: Inserting action group 'FileHistory' into UI manager which already has a group with this name

(gnumeric:24916): Gtk-WARNING **: Inserting action group 'FileHistory' into UI manager which already has a group with this name

(gnumeric:24916): Gtk-WARNING **: Inserting action group 'WindowList' into UI manager which already has a group with this name

(gnumeric:24916): Gtk-WARNING **: Inserting action group 'FileHistory' into UI manager which already has a group with this name

Now, if I call gnumeric with the name ofthe file I want to open, I get the following:
~/.config$ gnumeric 2009.gnumeric
Reading file:///home/a/.config/2009.gnumeric

(gnumeric:25064): Gtk-WARNING **: Inserting action group 'FileHistory' into UI manager which already has a group with this name

(gnumeric:25064): Gtk-WARNING **: Inserting action group 'FileHistory' into UI manager which already has a group with this name

and I can enter data into any cell in the spreadsheet as expected.

For me it seems somewhat more reliable when I start gnumeric with a
filename (by clicking it in Nautilus) but it's not 100% reliable
either way.

I've found if I open Gnumeric and then try and open a file immediately, either using File->Open or by picking a file from the history, then the document will not accept any keyboard input. The text appears in the entry box at the top, but disappears when you press enter leaving the original cell contents.

If I start Gnumeric, type some content in the empty document and then try and load the existing document, then it works fine and I can edit the document as normal.

When the document is uneditable, the New/Open options in the file menu are also greyed out.

@ian Yes, that seems to be the same bug.
--
Martin <http://launchpad.net/~mbp/>

I have observed the same problem in openSUSE 11.1 when I upgraded to 1.9.3 from the "factory" repository. Translation, this is not specific to Ubuntu.

Anyone to file the bug upstream?

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

This bug has been reported to the developers of the software. You can track it and make comments at:
http://bugzilla.gnome.org/show_bug.cgi?id=575267

Please provide the information requested by upstream

I submitted all the information upstream requested, including the backtrace. Also discussed this issue with developers in IRC, to insure all required information was now available to them.
Thanks for reporting this.

It would be good to get the upstream fix for this into Jaunty, it's a pretty nasty regression.

This bug was fixed in the package gnumeric - 1.8.4-3ubuntu2

---------------
gnumeric (1.8.4-3ubuntu2) jaunty; urgency=low

  * correct the IM interface so input works correctly again (LP: #333139),
    fixed in upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=575267,
    via the 1.8.x backported patch:
    http://bugzilla.gnome.org/attachment.cgi?id=130621&action=view

 -- Kees Cook <email address hidden> Mon, 13 Apr 2009 08:48:46 -0700

Thanks! That seems to have fixed it.

Dave

Why has this gone back to new/confirmed - it's fixed.

Dave

When the debian task was added, the status is automatically changed to "new" by the remote bug watcher. It will also change it to fixed/resolved when it catches up with it.