I tried to open KMyMoney today like I always do (my data file is a SQLite database file) and got an error with the following text:

Error in function const QMap MyMoneyStorageSql::fetchSchedules(const QStringList&, bool) const : reading Schedules Driver = QSQLITE, Host = localhost, User = robert, Database = /home/robert/Documents/kmymoney/robert.kdbx Driver Error: Database Error No -1: Text: Error type 0 Executed: SELECT id, name, type, typeString, occurence, occurenceMultiplier, occurenceString, paymentType, paymentTypeString, startDate, endDate, fixed, autoEnter, lastPayment, nextPaymentDue, weekendOption, weekendOptionString FROM kmmSchedules
ORDER BY id;; Query error No -1: No query Unable to fetch row Error type 1 in file /build/buildd/kmymoney-4.6.1/kmymoney/mymoney/storage/mymoneystoragesql.cpp line 3362

I've tried to submit a bug report but I'm still waiting for an activation email to create a bug reporting account before I can submit it... sigh.

Anyway, I need a fix pretty quick since I have bills to pay (you know how that goes). This error occurs every time I try to open my data file. Looking at the error text, I'm wondering if the double semicolon (";;") at the end of the SQL portion is causing a SQL syntax error. If I open the data file in SQLiteman (a tool for opening SQLite files), the SQL statement executes without error. Also, I didn't see anything that jumped out at me as strange looking at the records in my kmmSchedules table.

I used Clay's PPA to update to his latest (4.6.1) but that didn't solve the problem.

Any ideas of what I can do on my end to fix this? Is there a way to convert a SQLite back to the normal KMyMoney format (XML I think)?

Thanks,
Robert Rathbone

From your Forum email address I can see you use an AT&T company for your email. Unfortunately you will need to use a different provider - as they have blocked the KDE Bugzilla server (among others) for "abuse" (which has never occurred - our servers are clean).

From your Forum email address I can see you use an AT&T company for your email. Unfortunately you will need to use a different provider - as they have blocked the KDE Bugzilla server (among others) for "abuse" (which has never occurred - our servers are clean).

I tried creating a new bug reporting account using my gmail address this morning and I'm still waiting for the email 2 hours later as I write this. Is gmail blocking the Bugzilla server as well?

UPDATE: Oops, I don't use my gmail address that often so I accidentally mis-typed the address when I submitted it. I just now sent the correct address and got the activation email. I'll try to submit the bug report at my first opportunity since I'm at work and the machine with KMyMoney is at home. However, I'm still very much open to any advice to help me get back into my KMyMoney file while waiting for the developers to evaluate the bug report.


Robert Rathbone

I'm still not able to file a report. The crash handler isn't working. I tried to manually file a bug at bugs.kde.org, but they are apparently reworking the bug filing process and it's not working. When I filled in all the blanks and tried to submit the report, it gave me an error that there is no hardware called "PC", even though I picked it from their list. In fact, non of the choices worked (PC, Macintosh, Other, All). Somebody doesn't want my issue fixed...

If anyone knows a work-around that will help me get to where I can pay my bills, I'd very much appreciate it!

Thanks!
Robert

Bugs.kde.org is down for upgrade today. Can you please wait a couple of days until it gets back to normal?

I can wait about filing a bug report but I was hoping to get some help more quickly than that. I'm sorta in a bind not having access to my financial information, particularly the bill scheduler. I guess I can use SQLiteman to manually open the file and query the kmmSchedules table to see which bills are currently due so I can get them paid before they become late. But if you can advise me as to how I can convert the SQLite version of the file to a the native XML based version of the file, I'd appreciate it.

Update:
I went back to bugs.kde.org and somehow was able to file a bug report (it must have been the old method rather than the "new template" that they were talking about). The bug report is #295235 if you want to look at it, although I got a message that a moderator had to approve the report before it was accepted.

Thanks!
Robert

I fixed the issue you indicated. This is not such a great time to be trying to interact with KDE Bugzilla at the moment unfortunately.

We were forced to rush this upgrade as such due to a critical security bug. Unfortunately because the KDE Bugzilla previously used to run a very old version of Bugzilla the theme we were running was not compatible at all with the new version - necessitating a rewrite.

The issue you saw was the fault of the Mozilla developers who maintain Bugzilla - they decided it was a good idea to hard code their operating system names into the template used for the Create Bug page.

Reporting back in case this may help someone else having this same issue:

As previously reported, I had finally been able to submit the bug report under bug #295235. Fernando Vilas (one of the developers, I assume) said thought he had fixed the problem for 4.6.2 but then came back and said he'd been able to reproduce my error. He commited the fix to the source tree.

I downloaded the 4.6.2 source from Sourceforge.net and after jumping through all the hoops and cmake errors (had to install all the needed development tools) I was finally able to build KMyMoney 4.6.2 on my machine. As Fernando predicted, it didn't solve the problem.

However, I downloaded the new mymoneystoragesql.cpp file he committed and replaced the one I had and after building the app with the replacement file I'm happy to say that I was able to open my SQLite .kdbx file and catch up on my banking and bill paying. I did a "Save As..." to a .kmy as a precaution and closed the app and was able to reopen it without any issues. The app is even faster, although I'm not sure if that's due to my building it on a 64 bit machine or (more likely) to performance enhancements the developers have made between the 4.5.3 version I had through Kubuntu and the 4.6.2 version.

Hope this helps someone else who may be facing the same issue.

Thanks for everyone's help!

Robert Rathbone

I downloaded the 4.6.2 source from Sourceforge.net and after jumping through all the hoops and cmake errors (had to install all the needed development tools) I was finally able to build KMyMoney 4.6.2 on my machine. As Fernando predicted, it didn't solve the problem.

When Fernando committed the fix he did it in the 'master' and the '4.6' branch of the git repository so there is no way for the fixes to be available in the 4.6.2 release which took place a month ago.

When Fernando committed the fix he did it in the 'master' and the '4.6' branch of the git repository so there is no way for the fixes to be available in the 4.6.2 release which took place a month ago.

I understand that. If you read the bug report, he initially asked me to try 4.6.2 because he said he remembered fixing this issue in the last release cycle (which would be 4.6.2). Then some 40 minutes later he came back and said he spoke too soon as he was able to reproduce my error, showing that my particular issue was not completely fixed (hence his prediction). Later he posted the link to his commit which did fix my problem.

Since this was only the second app of any significant size that I've tried to build, I wanted to make sure I could build the official 4.6.2 version before I muddied the waters applying patches. Once I successfully built 4.6.2, I tested it even though I knew it probably wouldn't solve my issue. Then I downloaded and applied his replacement source file and rebuilt and that's when my problem was solved. I guess you could say I now have v4.6.2.000001 or something similar...

I was merely documenting my journey/thought-process for anyone else that might need to do something similar. Perhaps the confusion came because I wasn't detailed enough. My apologies.

Robert

I was merely documenting my journey/thought-process for anyone else that might need to do something similar. Perhaps the confusion came because I wasn't detailed enough. My apologies.

It's OK no harm was done . I guess it was a misunderstanding on my behalf, sorry.