Description of problem: Start gnucash, pen an account. Assume all items are sorted by date. Add an item with a newer date and the most recent item: (1) auto-completion is hardly working at all, (2) after adding the item is finished, the sort by date sequence is lost, all entries are shown with a not-sorted sequence-by-date and the new item added cannot be seen anywhere, It was the same with one less recent version (2.5.4-1.mga4). A little before that gnucash in Cauldron was working well. Previous occasion I used it was sometime in August: then it was okay ! Reproducible: Steps to Reproduce:
Summary: Current gnucash is not unworkable => Current gnucash is unworkable
After using gnucash, my ~/tmp contains a file gnucash.trace which is reading: * 17:44:45 WARN <gnc.backend.dbi> [gnc_module_init_backend_dbi()] No DBD drivers found * 17:44:50 WARN <gnc.python> Unable to initialize Python module (unable to open /usr/share/gnucash/python/init.py)
I have gnucash execute in a Linux cash account upon login. I launch a "xterm -e sudo su - cash &" and the xterm is spitting out 28+ seconds of messages before gnucash shows up. So far I have seen no operational errors adding transactions and I use it weekly. I also have ~cash/tmp/gnucash.trace looking pretty much like yours.
CC: (none) => junknospam
Keywords: (none) => TriagedAssignee: bugsquad => fundawang
What if gnucash-python be installed?
(In reply to Funda Wang from comment #3) > What if gnucash-python be installed? It is not installed. Do you want it installed? It sure would drag in a bunch more stuff. :( Currently can not do python updates. 1 installation transactions failed There was a problem during the installation: file /etc/profile.d/30python.csh from install of python-2.7.5-5.mga4.x86_64 conflicts with file from package python3-3.3.2-4.mga4.x86_64
urpmi says there is no package gnucash-python
*** Bug 11728 has been marked as a duplicate of this bug. ***
Source RPM: gnucash-2.5.5-1.mga4 => gnucash-2.5.6-2.mga4
Since Manuel closed my 11728, I'll add gnucash will not launch from the command line if you have never set up an Account, or if you are executing gnucash for the first time.
I found oneworkaround that will make gc a little workable (but not acceptable as an ordinary application should be), namely: (assuming sort mode is correct) add one transaction and after that move the left hand scrollbar completely from top to bottom, and the new entry will be visible as the last line entry.
(In reply to Dick Gevers from comment #8) > I found oneworkaround that will make gc a little workable It is not workable at all unless you have already setup a gnu account. Try it, create a new user, say junk. Log into junk, and run gnucash for the first time. It will crash pretty quick. :( In my "Production" database I tried to modify a expense transaction amount to balance/sync what is in my wallet asset and gnucash crashed. Now it is always complaining some other gnucash has the database open and what to do. :-) This is a showstopper as far as I am concerned.
How about gnucash 2.5.8 in core/updates_testing?
For me 2.5.8 from core/updates_testing solves all my problems I had with gnucash. Due to different problems reported here by Bit Twister, I suggest he should also approve this version !
(In reply to Dick Gevers from comment #11) > For me 2.5.8 from core/updates_testing solves all my problems I had with > gnucash. Sounds like progress to me. > Due to different problems reported here by Bit Twister, I suggest he should > also approve this version ! Don't let me hold up the parade. I always do clean installs, apply updates, reboot for each release and phase. In this case gnucash will not even run for a new user. There is nothing to lose by going ahead and releasing it. I did rsync my 2013 database into a mga3 VirutalBox guest and was happy to see the data. Also manually removed the *.LNK file which is used to indicate database in use.
*** Bug 11823 has been marked as a duplicate of this bug. ***
CC: (none) => inster.css
okay for me for 2.5.8 :)
then close this. If there are other problems, report it as another bug.
Status: NEW => RESOLVEDResolution: (none) => FIXED