Gnucash freezes after using backspace key

Bug #1316186 reported by Skewray
40
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gnucash (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The following behaviours started after upgrad to Tahr:

Using the the backspace kay while entering data freezes all future entry. Gnucash must be restarted in order to again enter data.

Gnucash forgets the user's sorting of the accounts and the account display columns after closing and reopening. This is a known bug on Gnucash 2.6.1, and (according to the gnucash mailing list) was fixed in 2.6.2.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnucash 1:2.6.1-2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: LXDE
Date: Mon May 5 08:03:58 2014
InstallationDate: Installed on 2014-01-02 (122 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/tcsh
SourcePackage: gnucash
UpgradeStatus: Upgraded to trusty on 2014-05-01 (3 days ago)

Revision history for this message
Skewray (ubuntu-skewray) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnucash (Ubuntu):
status: New → Confirmed
Revision history for this message
poikiloid (efelthauser) wrote :

This is affecting me too, on Kubuntu 14.04 (GnuCash 2.6.1), as well as in Lubuntu 13.10 (GnuCash 2.4).

This is making GnuCash basically unusable.

Revision history for this message
tagMacher (tagmacher) wrote :

Unable to reproduce this on Ubuntu 14.04 LTS 64-bit with GnuCash 2.6.1. Is there a special type of entry / field where this happens?

Revision history for this message
Skewray (ubuntu-skewray) wrote :

I have the problem when altering data in the description of an account entry or the amount of an account entry. Other places as well, but at least those two for sure.

Revision history for this message
poikiloid (efelthauser) wrote :

Hi all,

It is probably caused by using ibus instead of xim as your input method. see here for fix: https://bugzilla.gnome.org/show_bug.cgi?id=730195

Revision history for this message
Skewray (ubuntu-skewray) wrote :

I switched to xim and the problem does appear to have gone away afterwards. This should be confirmed by someone else as well; I had just also changed from LXDE to XFCE before trying it, and afterwards im-config would not allow me to change back to ibus.

Revision history for this message
poikiloid (efelthauser) wrote :

hmm, i don't know why you can't re-enable ibus. did you try to restart computer first?
check whether you have im-switch or im-config. (they are not compatible.) i think im-config is the more modern of the two methods.
note that, in order to get ibus to start when I log in on kubuntu, i had to add the ibus daemon to the list of auto-start apps in the system settings. i don't remember the command i entered there to get it to start (i'm away from my linux machine today...) maybe you'll need to do that in XFCE as well...

it is unfortunate how problematic ibus is (i have had various issued with it in the past), but it seems to work best for non-latin/roman character input for many languages. I know there are some other input methods, but the couple i've tried, i couldn't get to work as well as ibus for traditional chinese.

Revision history for this message
Skewray (ubuntu-skewray) wrote :

I used im-config to change to xim, and it won't change back, even with a reboot and ibus daemon restart. im-config from the command line attempts to open files in the current working directory and then exits with an error when it doesn't find whatever it expects. Not a very well written program. Also somewhat off topic.

Anyone else confirm the xim fix?

Revision history for this message
Christopher C. LaFrancis (clafrancis) wrote :

Installing the package "ibus-gtk" and restarting the ibus daemon fixed the problem for me.

This also appears to be a duplicate of #1306500.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.