GNOME Bugzilla – Bug 721765
All text entry fails, system beep on keypress (2.4.14)
Last modified: 2018-06-29 23:24:09 UTC
When I run the Gnucash app 2.4.14 on Mac OS X 10.5.8, I am unable to enter text into any text entry field in the application. Each keypress yields a system beep sound, and no character entered. How to reproduce: * Run GnuCash application * Gnucash application starts. * Tip of the Day dialog appears. Click Close button. Disappears. * Account window appears. * Open any account (I use "Miscellaneous") * Click in Description field at bottom of register to enter a new transaction. Observed behaviour: * No character appears in the Description field. A system beep sounds at any key press. Expected behaviour: * Characters appear in the Description field. No system beep. Further information: * Similar behaviour discovered in 2.6.0 on my system, see https://bugzilla.gnome.org/show_bug.cgi?id=721762 * Running 2.4.14 from command line gets an error dialog about error occurred while loading or saving configuration information for Gnucash-bin, with buttons which don't respond on being clicked, and underneath that a dialog "Cannot find default values", with buttons for whether GnuCash should Quit, Skip, or Setup. When I click the "Skip" button I get a long error message to the command line, and the app exits. Here's what I see: % /Applications/Gnucash-2.4.14.app/Contents/MacOS/Gnucash-bin Application Path /Applications/Gnucash-2.4.14.app/Contents/MacOS/Gnucash-bin Failed to load key /apps/gnucash/general/show_splash_screen: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to load key /apps/gnucash/general/account_separator: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to load key /apps/gnucash/general/auto_decimal_point: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to load key /apps/gnucash/general/auto_decimal_places: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to load key /apps/gnucash/general/date_format: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to load key /apps/gnucash/general/date_completion: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to load key /apps/gnucash/general/date_backmonths: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to save key /apps/gnucash/general/date_completion: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to save key /apps/gnucash/general/date_backmonths: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to add history section to watched directories in gconf: Failed to contact configuration server; some possible ca** gnc.gui:ERROR:gnc-icons.c:74:gnc_add_stock_icon_pair: assertion failed: (pixbuf1 && pixbuf2) uses are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to add history section to watched directories in gconf: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to load key /apps/gnucash/general/toolbar_style: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to load key /desktop/gnome/interface/toolbar_style: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Failed to load key /apps/gnucash/general/tab_position: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix"))Abort % I've attached a trace file from running Gnucash 2.4.14 on my Mac OS X 10.5.8 system. This is a run where the app launched properly. There are five CRIT messages in the trace file. However, there are similar CRIT messages in a trace file for 2.4.13, so I suspect they aren't closely related to the text entry failure. Running Gnucash from the command line with the --debug flag has no apparent effect. It yields a similar long-winded error message to the above. Workaround in https://bugzilla.gnome.org/show_bug.cgi?id=721260 has no effect. Opening an empty file from the app and putting a transaction into a new Account yields the same behaviour. Thus I suspect text entry is broken throughout the application, and it isn't simply a corruption in my bookkeeping file. After some attempts to compare 2.4.14 behaviour with 2.6.0 and 2.4.13 behaviour, running GnuCash 2.4.14 by double-clicking on the application icon now causes the application to fail on startup with this error message in the Console: 07/01/14 6:51:31 PM [0x0-0xa00a0].org.gnucash.Gnucash[12577] Application Path /Applications/Gnucash-2.4.14.app/Contents/MacOS/Gnucash-bin 07/01/14 6:51:31 PM [0x0-0xa00a0].org.gnucash.Gnucash[12577] Application Path /Applications/Gnucash-2.4.14.app/Contents/MacOS/Gnucash-bin 07/01/14 6:51:31 PM [0x0-0xa00a0].org.gnucash.Gnucash[12577] * 18:51:31 WARN <gnc.bin> Error parsing command line arguments: [Unknown option -psn_0_655520]; try `gnucash --help` for available options. 07/01/14 6:51:31 PM com.apple.launchd[1593] ([0x0-0xa00a0].org.gnucash.Gnucash[12577]) Exited with exit code: 1 GnuCash 2.4.13 seems to still work as it always did.
Created attachment 265631 [details] Trace from run of Gnucash 2.4.14 on Mac OS X 10.5.8
John Ralls asks, via gnucash-users: >Intel or PPC? Intel. Hardware = MacBook Core 2 duo. >For 2.4.14, try deleting Gnucash.app/Contents/Resources/etc/gtk-2.0/gtk.immodules Tried it. No change to symptoms. There is a crash log also, from one of the runs -- but not apparently from running the GnuCash 2.4.14 app from the Finder.
You can't run Gnucash-bin directly, you must use the shell script, Gnucash, to set up Gnucash's environment. That's what launching from Finder does. I've just tested 2.4.14 on MacOSX 10.5.8, and after removing gtk.immodules, it appears to work fine. If you're curious, it's because the quartz input module uses an interface, NSInputManager, that's not available until 10.6. Your error about command line arguments suggests that you might have managed to alter the shell script. You should move the current Gnucash.app to the trash, empty, and get a fresh copy from the dmg.
Thanks to John Ralls for the guidance. I confirm that on my Mac OS X 10.5.8 system, if I: 1. Delete the previous copy of GnuCash 2.4.14 2. Re-copy GnuCash application from the .dmg to the /Applications folder 3. Delete (or in my case remove to a separate directory) the gtk.immodules file, as in: rm /Applications/Gnucash.app/Contents/Resources/etc/gtk-2.0/gtk.immodules 4. Run GnuCash 2.4.14 by double-clicking the Application icon, then the observed behaviour becomes is the same as expected. That is: * Gnucash application starts. * Tip of the Day dialog appears. Click Close button. Disappears. * Account window appears. * Open any account (I use "Miscellaneous") * Click in Description field at bottom of register to enter a new transaction. * Characters appear in the Description field. No system beep. Based on the discussion, it makes sense to me that the bug behaviour is due to the GTK NSInputManager functionality related to gtk.immodules being incompatible with versions of Mac OS X before 10.6.0. Thus I'd support reducing the Priority of this bug to Normal, and the Severity to Normal or Minor (not many of us left on 10.5.8). I won't make this change, because I don't know the ground rules here well enough. Also, it seems to me that reasonable responses to this bug report might be: * Declare that GnuCash 2.4.14 requires Mac OS X 10.6.0 or newer to run * Document the workaround of deleting gtk.immodules in the README file or similar, for the benefit of GnuCash 2.5.8 users * Add a feature to GnuCash that, if it finds itself running on Mac OS X 10.5.8, it deletes gtk.immodules on the user's behalf In any event, on behalf of the other 10.5.8 users, thanks for explaining this workaround.
*** This bug has been marked as a duplicate of bug 721762 ***
Reassign version to 2.4.x so that individual 2.4 versions can be retired.
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=721765. Please update any external references or bookmarks.