search

UIKit0 / newsbeuter

Automatically exported from code.google.com/p/newsbeuter
0 stars 0 forks source link

Google Reader sync #221

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Put this on ~/.newsbeuter/config:
urls-source "googlereader"
googlereader-login "123456@gmail.com"
googlereader-password "123456" (contains numbers and lower/uppercase chars)
2. Open app and get: Authentication failed

What is the expected output? What do you see instead?
~ newsbeuter 
Iniciando newsbeuter 2.3...
Cargando configuracion...hecho.
Abriendo cache...hecho.
Cargando URLs desde Google Reader...Authentication failed.

What version of the product are you using? On what operating system?
~ uname -a
Linux 2.6.34-ARCH #1 SMP PREEMPT Sat Jun 19 00:07:49 CEST 2010 x86_64 Intel(R) 
Core(TM) i5 CPU M 520 @ 2.40GHz GenuineIntel GNU/Linux

Original issue reported on code.google.com by kismet010 on 8 Jul 2010 at 2:34

GoogleCodeExporter commented 9 years ago 
Can't reproduce. Can you run strace -o log.txt newsbeuter and send the 
resulting log.txt to ak@newsbeuter.org for further inspection?

Original comment by theunixe...@gmail.com on 8 Jul 2010 at 8:15

GoogleCodeExporter commented 9 years ago

Original comment by theunixe...@gmail.com on 8 Jul 2010 at 8:15

GoogleCodeExporter commented 9 years ago 
Are you sure you're using the correct login / password?

Original comment by karol.bl...@gmail.com on 8 Jul 2010 at 8:23

GoogleCodeExporter commented 9 years ago 
The same problem:

k1b@k1book:~/.newsbeuter> newsbeuter
Запускаю newsbeuter 2.3...
Загружаю настройки...сделано.
Открываю кеш...сделано.
Загружаю ссылки из Google Reader...Authentication failed.

Login and password is correct.

OpenSUSE 11.3
2.6.34-12-desktop #1 SMP PREEMPT 2010-06-29 02:39:08 +0200 i686 i686 i386 
GNU/Linux

Original comment by alex.k1b on 27 Jul 2010 at 11:22

GoogleCodeExporter commented 9 years ago 
in which encoding is the config-file written?

i can see in 'configparser.cpp' the stl:getline() method is used and the 
read-in data is stored as normal std::strings ..

Original comment by mathias....@gmail.com on 23 Aug 2010 at 4:19

GoogleCodeExporter commented 9 years ago 
I recently submitted a patch which fixed issues with logging in when a password 
had non standard characters in (though I have only tested with characters in 
the ASCII set).
If you checkout the latest version from git does this fix the issue?

Original comment by a.lown0@gmail.com on 11 Dec 2010 at 6:56

GoogleCodeExporter commented 9 years ago 
My password is with standard ASCII characters, and I get the authentication 
errors as well.  Are there any logs or files I could attach to help debug this?

Original comment by Steven.S...@gmail.com on 18 Dec 2010 at 7:33

GoogleCodeExporter commented 9 years ago 
Which git commit/version are you using?
You can get a log file by starting newsbeuter with the -l and -d switches, eg.
newsbeuter -l 6 -d newsbeuter.log
but bear in mind that this will be very verbose.

Original comment by a.lown0@gmail.com on 18 Dec 2010 at 10:24

GoogleCodeExporter commented 9 years ago 
The 10 Dec git commit version (SHA: 06d30f5e99456326d8035cfb43d1f4ea4908fead, 
according to giggle - I'm a bit of a noob to git, so I think that's the right 
thing to tell you;  it's the latest update on github).

I've uninstalled, reinstalled, rebuilt the .rc from scratch.  Which means I've 
probably missed something stupid.  :/   It's important to note that it *did* 
work at one point, and stopped working without changes on my end.

Log file's actually very very short!  I've attached the whole thing 
(obfuscating user/pass), but these are the only relevant bits I can see:

[2010-12-19 11:01:50] DEBUG: configparser::parse: tokenizing googlereader-login 
"USERNAME"
[2010-12-19 11:01:50] DEBUG: configcontainer::handle_action: action = 
googlereader-login, type = 3
[2010-12-19 11:01:50] DEBUG: configparser::parse: tokenizing 
googlereader-password "PASSWORD"
[2010-12-19 11:01:50] DEBUG: configcontainer::handle_action: action = 
googlereader-password, type = 3

...

[2010-12-19 11:01:50] DEBUG: googlereader_api::authenticate: Auth = 
[2010-12-19 11:01:50] DEBUG: utils::remove_fs_lock: removed lockfile 
/home/steven/.newsbeuter/cache.db.lock

Original comment by Steven.S...@gmail.com on 19 Dec 2010 at 4:07

Attachments:

GoogleCodeExporter commented 9 years ago 
it's working with git version for me

Original comment by kismet010 on 20 Dec 2010 at 7:25

GoogleCodeExporter commented 9 years ago 
Is there another setting or dependency that I might be missing?  If everything 
compiles properly, it shouldn't be an issue, right?   ::sigh::

Original comment by Steven.S...@gmail.com on 20 Dec 2010 at 5:43

GoogleCodeExporter commented 9 years ago 
No, it compiled so everything is there.
Without telling your password, could you describe which special characters (non 
[A-Za-z0-9] you use - so that we can attempt to reproduce the problem. 
Particularly if your password contains one of the following: "$-_.+!*'(),"

Original comment by a.lown0@gmail.com on 21 Dec 2010 at 11:27

GoogleCodeExporter commented 9 years ago 
Ah, that's the thing - I *don't* use any special characters.  
Upper/lower/number.  

I uninstalled and reinstalled again just to make sure again today.  Mutt 
connects up fine to my Gmail, so I'm not sure what's going on here.

Original comment by Steven.S...@gmail.com on 21 Dec 2010 at 11:42

GoogleCodeExporter commented 9 years ago 
Tried again - this time leaving out the . in my username.  Also tried another 
username and password.

Is there a place where it should echo what the username / password combination 
that it's using?  Or a place where I could insert that code in myself?   (I'm 
passingly familiar with C and JScript, but that's about my limit.)

Original comment by Steven.S...@gmail.com on 27 Dec 2010 at 9:44

GoogleCodeExporter commented 9 years ago 
I have a . in my username too, so I knew that that was not the issue.
Your username/password were echoed in the log file (you blanked them out of the 
attached file).
Your username and password are passed to google in the src/google_api.cpp 
retrieve_auth() function. If you want you can try injecting them in there.

Original comment by a.lown0@gmail.com on 27 Dec 2010 at 10:05

GoogleCodeExporter commented 9 years ago 
Okay, this is bizarre.  I decided to hack at this again today.  I got the 
standard install from the Ubuntu repositories.  I got the latest git code.  I 
installed 2.3.  Everything failed to authenticate.

Except for newsbeuter_2.3-1_i386.deb from the Debian sid repositories.  And now 
it's working perfectly.  *I didn't change the config file between the last 
version I built from source and the one from sid.*

Since I'm running Ubuntu 10.04, this is at best bizarre.  I hope this helps 
someone either solve their own problem (d/l from here:  
http://packages.debian.org/sid/newsbeuter ) or help y'all discover what the 
difference is.

Original comment by Steven.S...@gmail.com on 16 Jan 2011 at 2:14

GoogleCodeExporter commented 9 years ago 
I also experienced this issue in newsbeuter 2.4
I have many special characters in the password.
What worked was *not* quoting the password string in ~/.newsbeuter/config

Original comment by jane.rea...@gmx.com on 10 Apr 2011 at 6:32

GoogleCodeExporter commented 9 years ago 
Hmmm… I have a similiar, yet strange problem.
When I try tu run newsbeuter (2.5 from Debian Sid) it ends with authentication 
failed.
But when I use the same console and curl to post needed data to 
https://www.google.com/accounts/ClientLogin then I get proper Auth token in 
response.
newsbeuter -l 6 shows that Auth is empty :/

I changed nothing in my config and it worked like a charm the day before.

Original comment by miha...@gmail.com on 12 Oct 2012 at 5:56

GoogleCodeExporter commented 9 years ago 
Looks like recent update of libcurl3-gnutls (7.28.0-1) in Debian Sid is the 
cause of my problems.

Original comment by miha...@gmail.com on 13 Oct 2012 at 3:54