Package Details: grive-tools 1.15-5

Git Clone URL: (read-only)
Package Base: grive-tools
Description: Grive Tools will assist in the installation and setup of Google Drive under GTK
Upstream URL:
Keywords: drive google thefanclub
Licenses: GPL3
Submitter: skad
Maintainer: nullptr_t
Last Packager: nullptr_t
Votes: 59
Popularity: 0.969215
First Submitted: 2014-01-17 15:14
Last Updated: 2017-01-14 19:00

Latest Comments

Ziim commented on 2017-03-02 08:27

Hello everyone
I made it!

It worked two times at KDE environment; I created manually the "Google Drive" Folder and enter with the Terminal, i wrote "grive -a" inside the "Google Drive" folder and did the manual authentication (copy the key and paste it on the terminal)... then i wait to complete the full sync...
I closed the terminal once ended and opened the "Google Drive Indicator"; I had to manually set it to launch at startup... i find problems with the KDEWallet, so i turned it off in the wallet configuration (global disable) because if the "Indicator" cant connect immidiatly it get bug telling is offline until you close and open it again.

I hope this help someone to save the head and a few dollars in licenses ;)

PS: using currently version available (1.15-5)

liberalphg commented on 2017-01-26 22:48

No visible icon and no automatic sync here! Last version.

wyre commented on 2016-07-15 11:48

I don't have got dialog prompt asking me for google auth token. Just it says it is syncing but nothing happens.

dixi_minga commented on 2016-07-13 04:57

> Since the Update of Qt to 5.7 I have no visible Icon anymore in my control bar.
solved-with KDE Frameworks 5.24 the icon is now visible again

dixi_minga commented on 2016-07-05 17:46

Am I the only one, who uses KDE Plasma5 with grive-tools?

Since the Update of Qt to 5.7 I have no visible Icon anymore in my control bar.

There is clickable space for the icon and synchronization works fine; but the icon is not visible anymore.

nullptr_t commented on 2016-06-02 12:18

Since thefanclub only provides binaries and I cannot find sources anywhere, I have no influence on this behaviour. Sorry.

grive-tools is superseeded by a properitary 4,99$ solution called overgrive, so we have to stay at the current state of grive-tools or please them to publish the sources.

grive is a standalone user-contributed solution we use as dependency instead.

jro commented on 2016-06-02 10:38

Grive-indicator creates a lock file /tmp/grive-indicator.lock and refuses to start if it is already present. So only one user can have it running at a time. It would be better if the lockfile was placed in a place like /run/user/$UID/, which I guess is the standard place for it.

nullptr_t commented on 2016-04-24 17:00

That line already exists before everything gets moved out of the directory...

macieks commented on 2016-04-24 14:55

I found some minro problem during installation...
grive-tools.install should be updated, this line should be moved to PKGBUILD:
chmod 755 /opt/grive-tools/grive-indicator

Also the path above is wrong.

nullptr_t commented on 2016-04-24 11:28

Can groups like thefanclub please state their wishes before something gets updated? I got this:
"Also, removing a group's name is just bad taste." - I fully agree, but: GPL does not forbid this.
I thought a full empty directory would be too much and too properitary.
You now got credits in our tags.

On the one hand, some try to haste me, when I'm late, on the other hand I understand the wishes of groups and simple persons to get credits. Because of that,I want to drop this package. I'm thinking of only maintaining my own packages like liblogcpp until GPLv4 explicitly states
* that maintaining a package by another legal person is allowed.
* that packaging software by another legal person is allowed
* how to give credit to persons good ideas in whatever form (binary, package)
* that credits given inside path are allowed, too, or just in filenames. First would be really properitary
* how to give credit to the initial writers, developers and debuggers, even if packaged or not

Maybe it should state
* how to identify the wishes beyond GPL without really knowing the legal persons.

So thefanclub stays in and I want a co-maintainer of them. Please state here:
Are you, I received a mail from, really part of thefanclub? Was this your code? Would you please co-maintain this (and revert the change)?


All comments