Liferea has SQL error when run after applying filter on Gusy-64 bit

[William Woelke]

Binary package hint: liferea

The program didn't update the search folder correctly when I added a rule, so I exited it as that has fixed it in the past. When I tried to start it back up, I received this error:

** ERROR **: Failure while preparing statement, (error=1, no such table: main.view_aqxxirs) SQL: "DELETE FROM itemsets WHERE item_id = ?"
aborting...
Aborted

[Richard Seguin (sectech)]

Thank you for reporting this issue and trying to make Ubuntu better. Could you please answer the following questions:

1) What version of Ubuntu are your running (also indicate if it's 32 or 64 bit)
2) What steps do I need to go through in order to consistently reproduce this issue

Just to clarify, this issue was fixed in the past but broke again in newer versions? If so, do you know if a bug was reported for the issue?

Thanks,

Richard Seguin

[Richard Seguin (sectech)]

* Marking as incomplete pending enough information to complete triage

[William Woelke (williamwoelke)]

I am running Gutsy Gibbon - 64-bit.

I have only just started using Liferea a couple days ago but it hasn't seemed the most reliable in general for me. The only problem I have had up to this point was that when I added rules for the search folders, it didn't update right away or would go empty. The last time that happened, I closed the program and re-opened it and the folder was correctly updated.

I had just added a rule to my "unread" search folder and it went empty, but still said there were 118 unread items when I clicked on it. I closed it and tried to reopen it, but that is when I had the problem. I know of know way to reproduce the problem, but then... I am still working on getting Liferea to run.

I renamed liferea.db to liferea.db.bak and the program opens correctly now, though all the old feeds are gone. I don't know if it did this before, but now when I open it, it says:

Obtaining the module object from Python failed.

Traceback (most recent call last):
cant import cStringIO
<type 'exceptions.ImportError'>: /usr/lib/python2.5/lib-dynload/time.so: undefined symbol: PyExc_ValueError

and on close an assert appears to have failed:

(liferea:5255): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed

I am attaching the liferea.db file. I believe replacing the db file with mine will cause the same error, but if you want to know how to manually cause the problem, I don't have that answer yet.

[William Woelke (williamwoelke)]

Steps to reproduce:

1. Right click on a search folder. e.g. "Unread"
2. Click "Properties"
3. Click "Add"
4. Change to "Feed Title", "Does Not Match", and for the criteria, enter an apostrophe.
5. Click OK.
6. Exit Liferea
7. Attempt to Open Liferea

[Richard Seguin (sectech)]

I just tested this issue on Gusty 32 bit (I don't have a 64 bit to test on) and was not able to re-produce the problem. What version of liferea are you running? Does this occur with a new liferea.db?

Thanks,

Richard Seguin

[William Woelke (williamwoelke)]

I am running Liferea 1.4.14 and I have tested the bug on 32 and 64 bit versions of Hardy Heron with identical results. The problem happens even with a fresh install of both Hardy Heron and Liferea.

[Richard Seguin (sectech)]

I have been able to confirm that I do get the problem when I use your liferea.db file, have you tried deleting the file and allowing lifrea to create a new one? It appears that somewhere along the way the database file might have become corrupt.

Thanks,

Richard Seguin

[William Woelke (williamwoelke)]

As I stated, when I allow a new db file to be created, it works again. At least until I add an apostrophe to a filter and have to delete it again.

[Richard Seguin (sectech)]

Sorry for the confusion... I just had to make things perfectly clear as I believe there should be enough information for a developer to look at the issue... It's fairly straight forward in the way that the error is consistently caused by an apostrophe.

Thank you for reporting this issue and please feel free to report any other Ubuntu bugs.

Thanks,

Richard Seguin

[Dimitrios Symeonidis (azimout)]

it's been >1 year since this bug saw any activity, and gutsy supports expires next week.
is this still an issue for any of you, with the latest version of ubuntu?
thank you

[xteejx (xteejx)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!