TTRSS Api Error

[fidel]

I installed Feedreader on Arch - and tried to setup my self-hosted TinyTiny RSS.
This seems not to work - while it does on my other machine (ubuntu).

If i do start Feedreader on arch i do get the following output:
--
[ INFO ] Only critical Errors are logged!

(feedreader:38291): GLib-GObject-WARNING **: The property SoupSession:ssl-ca-file is deprecated and shouldn't be used anymore. It will be removed in a future version.
[ ERROR ] CREATE VIRTUAL TABLE fts_table USING fts4 (content='articles', articleID, preview, title, author)
[ ERROR ] table fts_table already exists
[ INFO ] Only critical Errors are logged!
[ ERROR ] ttrss api error
[ ERROR ] ttrss api error

At this point - Feedreader displays the configure page - with the values of my TTRSS-Server.
Pressing "Anmelden/Login" displays the following error in thr UI:

>> Either your username or the password are not correct

While i am sure both are correct.

any idea?

[fidel (el-fidel)]

Using Feedreader 1.2.1-3 on Arch

[JeanLuc (eviltwin1)]

Can you enable debug output with dconf org/gnome/feedreader/ log-level = DEBUG?
The api-error is nothing unexpected if you don't have the labels-plugin installed in your ttrss server.

[fidel (el-fidel)]

For sure - results in the following output:
--
[ INFO ] Everything is logged. Used to debug!

(feedreader:38767): GLib-GObject-WARNING **: The property SoupSession:ssl-ca-file is deprecated and shouldn't be used anymore. It will be removed in a future version.
[ ERROR ] CREATE VIRTUAL TABLE fts_table USING fts4 (content='articles', articleID, preview, title, author)
[ ERROR ] table fts_table already exists
[ INFO ] Everything is logged. Used to debug!
[ DEBUG ] daemon: constructor
[ DEBUG ] daemon: new FeedServer and login
[ DEBUG ] FeedServer: new with type 0
[ DEBUG ] TTRSS: login
[ DEBUG ] ttrss URL: http://vido.info/tt-rss/api/
[ ERROR ] ttrss api error
[ ERROR ] ttrss api error
[ DEBUG ] daemon: login status = 8
[WARNING] daemon: not logged in
[ DEBUG ] daemon: add timeout
[ DEBUG ] daemon: bus aquired
[ DEBUG ] ContentPage: setup FeedList
[ DEBUG ] menu
[ DEBUG ] minimize,maximize,close
[ DEBUG ] UpdateButton: update status
[ DEBUG ] UpdateButton: setSensitive true
[ DEBUG ] daemon: new FeedServer and login
[ DEBUG ] FeedServer: new with type 0
[ DEBUG ] TTRSS: login
[ DEBUG ] ttrss URL: http://vido.info/tt-rss/api/
[ ERROR ] ttrss api error
[ ERROR ] ttrss api error
[ DEBUG ] daemon: login status = 8
[ DEBUG ] MainWindow: show login
[ DEBUG ] MainWindow: show error bar - errorCode = 6
[ DEBUG ] MainWindow: dont show error bar
[ DEBUG ] HeaderBar: updatebutton status false
[ DEBUG ] UpdateButton: setSensitive false

[JeanLuc (eviltwin1)]

Damn it :D
version 1.2.1 did not print the message and the response after an api-error (master branch does that)
actually shipping software and having to deal with different versions is hard =/

Can you possibly get the incoming and outgoing messages from your ttrss server directly?
I don't know how to do this, but Viktor Kojouharov managed to do it in his bug report:
https://bugs.launchpad.net/feedreader/+bug/1497693

the other two options are:
-upgrading to unstable where all data is printed after an api error
-setting up a demo account on your server for me and hoping that I can reproduce the error

sorry =/

[fidel (el-fidel)]

Hi,

on Arch it helped to update from official 1.2.1-3 to 1.2.1-5 (which was offered via AUR).
1.2.1-5 seems to work just out of the box with my setup.

Now lets see when this version hits the fedora repositories for the other box ;)

You can close this issue from my point of view

[JeanLuc (eviltwin1)]

Uhm ... between 1.2.1-3 and 1.2.1-5 are only packaging changes and a patch to not remember the search term.

[fidel (el-fidel)]

Strange

i did on purpose:
- compare the settings via dconf-editor on that arch machine which the ubuntu hosts where it is working
- tried it again on arch witnh 1.2.1-3 and it failed once again
- updated to 1.2.1-5 via yaourt on arch
- tried it again without modifying any config - and it worked.

Well - as long as noone else has issues with it - seems like a case for "ignore" ;)