[solved] checkgmail no longer working

rogorido · 2013-01-19 07:04:09

Hi, since a few days checkgmail is not working anymore. It gives a ERROR 200 OK. Any ideas? (I'm using checkgmail from community, have also tried the AUR svn package with no success).

Last edited by rogorido (2013-01-19 15:50:43)

Mektub · 2013-01-19 14:46:06

rogorido,

I am using checkgmail 1.13-7.

However for some reason I don't remember, I have to start it with:

checkgmail -no_cookies

Checkgmail depends on

perl-crypt-blowfish
perl-crypt-simple
perl-freezethaw
perl-gtk2-trayicon
perl-lwp-protocol-https
perl-xml-simple
perl-gtk2-sexy (optional)

Try reinstalling.

Mektub

rogorido · 2013-01-19 15:50:28

exactly. With the option -no_cookies it's working again... maybe some change made by google?

Thnaks!

jskier · 2013-01-19 16:27:28

Something did change with GMail.

Re-installing and clearing config didn't help. Disabling cookies takes care of it.

firewalker · 2013-01-21 07:58:52

Without cookies, checkgmail is just another email notifier. No "Mark as read, Archive" etc.

jtaylor · 2013-01-23 03:10:07

There is a proper solution in the comments for the bug report on SourceForge.

The brief summary of that is that you need to edit /usr/bin/checkgmail and replace https://www.google.com/accounts/ with https://accounts.google.com/, which should be three occurrences.

Mektub · 2013-01-23 16:56:23

jtaylor wrote:

There is a proper solution in the comments for the bug report on SourceForge.
The brief summary of that is that you need to edit /usr/bin/checkgmail and replace https://www.google.com/accounts/ with https://accounts.google.com/, which should be three occurrences.

Solves problem. Thanks, jtaylor

Mektub

rogorido · 2013-01-28 15:17:05

This solves really the problem. Thnaks.

bpont · 2013-04-18 13:57:38

Mektub wrote:

jtaylor wrote:
There is a proper solution in the comments for the bug report on SourceForge.
The brief summary of that is that you need to edit /usr/bin/checkgmail and replace https://www.google.com/accounts/ with https://accounts.google.com/, which should be three occurrences.
Solves problem. Thanks, jtaylor
Mektub

I'm trying to follow the advice on that page, but when I ran:

# patch checkgmail checkgmail.patch

I got:

# patching file checkgmail
Reversed (or previously applied) patch detected!  Assume -R? [n]

I still have my console up and I haven't responded to the console prompt until I get some advice here.

Last edited by bpont (2013-04-18 13:58:22)

bpont · 2013-04-19 18:30:48

# patching file checkgmail
Reversed (or previously applied) patch detected!  Assume -R? [n]

Why is this error appearing?

-R or --reverse
Assume that this patch was created with the old and new files swapped. (Yes, I'm afraid that does happen occasionally, human
nature being what it is.) patch attempts to swap each hunk around before applying it. Rejects come out in the swapped format.
The -R option does not work with ed diff scripts because there is too little information to reconstruct the reverse operation.
If the first hunk of a patch fails, patch reverses the hunk to see if it can be applied that way. If it can, you are asked if you
want to have the -R option set. If it can't, the patch continues to be applied normally. (Note: this method cannot detect a
reversed patch if it is a normal diff and if the first command is an append (i.e. it should have been a delete) since appends
always succeed, due to the fact that a null context matches anywhere. Luckily, most patches add or change lines rather than
delete them, so most reversed normal diffs begin with a delete, which fails, triggering the heuristic.)

Assume that this patch was created with the old and new files swapped.

By this I'm assuming the -R switch thinks that it's dealing with a newer version of the executable in which the patch had already been applied versus a version of the executable in which the patch hadn't been applied?

(Yes, I'm afraid that does happen occasionally, human
nature being what it is.) patch attempts to swap each hunk around before applying it. Rejects come out in the swapped format.

I'm not really understanding what's being described here.

The -R option does not work with ed diff scripts because there is too little information to reconstruct the reverse operation.

OK

If the first hunk of a patch fails, patch reverses the hunk to see if it can be applied that way. If it can, you are asked if you
want to have the -R option set.

So I should assume this is exactly what happened and that's why I was prompted if I wanted to apply the -R switch? If so, since it reversed the first hunk and was applied successfully, should I assume that I have a version of the executable in which the patch was already applied?

If it can't, the patch continues to be applied normally. (Note: this method cannot detect a
reversed patch if it is a normal diff and if the first command is an append (i.e. it should have been a delete) since appends
always succeed, due to the fact that a null context matches anywhere. Luckily, most patches add or change lines rather than
delete them, so most reversed normal diffs begin with a delete, which fails, triggering the heuristic.)

I don't understand this part, but don't think it really applies to this particular issue.

cirrus · 2013-05-02 02:23:15

checkgmail -no_cookies & in autostart or a shell alias will suffice, fixes it for me on 2 arch installs. the method above replacing 3x URL entries didnt work for me, the -no_cookies switch did.

Lockheed · 2013-05-02 06:48:18

Replacing URLs does work for me, while no_cookies destroys functionality of checkgmail.

drcouzelis · 2013-05-02 12:48:41

Some additional information that's SORT OF related to this issue:

I use the "check Gmail" Bash script found here in the wiki: https://wiki.archlinux.org/index.php/Co … er_Methods I noticed it stopped working reliably around the time that this thread was created.

Thanks to the information in this thread, I tried changing the wget command by adding "--no-cookies" to it, and it seems to work better now. After I learn a bit more about the recent changes to Gmail and this situation, I'll update the wiki.

Lockheed · 2013-05-02 13:26:36

Speaking of checkgmail, I am really surprised no-one is developing or at least maintaining it since a long time, because this is by far and away THE BEST gmail notificator available for linux.

drcouzelis · 2013-05-02 13:29:49

Lockheed wrote:

Speaking of checkgmail, I am really surprised no-one is developing or at least maintaining it since a long time, because this is by far and away THE BEST gmail notificator available for linux.

Oh my gosh... It hasn't had a code commit in three years?? I'm amazed that it still works!

As for my comment above, I just want to further clarify that I don't really know what I'm doing. I'm still looking into my problem. And now I'll stop hijacking this thread. Maybe.

CPUnltd · 2013-05-09 00:05:26

I don't think this is officially solved because I just installled this program today and I am stuck with the -no-cookies option because the url change didn't fix the ERROR 200 OK issue for me. Anyone still working on or dealing with this? I'm using the version of checkgmail from the main repos, not AUR...

tomaqa · 2013-06-11 19:25:29

jtaylor wrote:

There is a proper solution in the comments for the bug report on SourceForge.
The brief summary of that is that you need to edit /usr/bin/checkgmail and replace https://www.google.com/accounts/ with https://accounts.google.com/, which should be three occurrences.

This helps for me.

Thanks,

Tomaqa

rcspam · 2014-09-21 10:32:27

Hi,

If you want a checkgmail adapted to the colors of your desktop theme, you can visit Rcspam's Blog
This version correct some little bugs and you can launch it without adding "--no-cookies".

Last edited by rcspam (2014-10-14 15:29:05)

Lockheed · 2014-09-22 07:51:44

It is a pity the buttons to manage mail no longer work even with this version.

rcspam · 2014-10-01 11:28:50

Lockheed wrote:

It is a pity the buttons to manage mail no longer work even with this version.

Apparently, it's possible to code this with 'imaplib' and 'email' python libraries but i have no time to learn it. If anyone could do it, he will be my undying gratitude

Last edited by rcspam (2014-10-01 11:43:48)

monojp · 2014-10-11 18:24:45

Hi, I think I got the buttons working again. There were - again - outdated urls in the script.
I'm not experienced in Perl scripts so I hope the simple url replacement is enough.

You can try and see if it works here:
https://aur.archlinux.org/packages/checkgmail-svn/

I also added a 2 factor auth patch which was floating around and seems to work fine for me

Last edited by monojp (2014-10-11 18:30:27)

rcspam · 2014-10-14 11:41:38

Hi monojp

Good Job, peharps we can join your "button back again" version and my "themable" version in one
I had re-write the themable version based on your hack, the script is here
This version resolve the "icon background color setting" bug.
As i see your are a perl hacker, perhaps you can write a part to change colors directly in the preferences window. The variables are already in the beginning of the script (line ~230 )
Cheers

Last edited by rcspam (2014-10-14 16:01:40)

Lockheed · 2014-10-15 11:50:14

monojp wrote:

Hi, I think I got the buttons working again. There were - again - outdated urls in the script.
I'm not experienced in Perl scripts so I hope the simple url replacement is enough.
You can try and see if it works here:
https://aur.archlinux.org/packages/checkgmail-svn/
I also added a 2 factor auth patch which was floating around and seems to work fine for me

@monojp,

You have my great gratitude for taking over maintenance of this forgotten piece of irreplaceable software.

monojp · 2015-09-10 08:25:04

Does somebody of you want to takeover the modified checkgmail? I'm afraid I'm not using it anymore (chromium extensions work well and better..) It's currently on https://github.com/monojp/checkgmail
Apparently the official homepage and sourceforge still seem to exist and are delivering the old and broken version. A new, cleaner approach in Python or something more readable would be better I guess. I'm not experienced in Perl myself, but the source code of checkgmail is really not easy to maintain.

Arch Linux

#1 2013-01-19 07:04:09

[solved] checkgmail no longer working

#2 2013-01-19 14:46:06

Re: [solved] checkgmail no longer working

#3 2013-01-19 15:50:28

Re: [solved] checkgmail no longer working

#4 2013-01-19 16:27:28

Re: [solved] checkgmail no longer working

#5 2013-01-21 07:58:52

Re: [solved] checkgmail no longer working

#6 2013-01-23 03:10:07

Re: [solved] checkgmail no longer working

#7 2013-01-23 16:56:23

Re: [solved] checkgmail no longer working

#8 2013-01-28 15:17:05

Re: [solved] checkgmail no longer working

#9 2013-04-18 13:57:38

Re: [solved] checkgmail no longer working

#10 2013-04-19 18:30:48

Re: [solved] checkgmail no longer working

#11 2013-05-02 02:23:15

Re: [solved] checkgmail no longer working

#12 2013-05-02 06:48:18

Re: [solved] checkgmail no longer working

#13 2013-05-02 12:48:41

Re: [solved] checkgmail no longer working

#14 2013-05-02 13:26:36

Re: [solved] checkgmail no longer working

#15 2013-05-02 13:29:49

Re: [solved] checkgmail no longer working

#16 2013-05-09 00:05:26

Re: [solved] checkgmail no longer working

#17 2013-06-11 19:25:29

Re: [solved] checkgmail no longer working

#18 2014-09-21 10:32:27

Re: [solved] checkgmail no longer working

#19 2014-09-22 07:51:44

Re: [solved] checkgmail no longer working

#20 2014-10-01 11:28:50

Re: [solved] checkgmail no longer working

#21 2014-10-11 18:24:45

Re: [solved] checkgmail no longer working

#22 2014-10-14 11:41:38

Re: [solved] checkgmail no longer working

#23 2014-10-15 11:50:14

Re: [solved] checkgmail no longer working

#24 2015-09-10 08:25:04

Re: [solved] checkgmail no longer working

Board footer