Siduction Forum

Siduction Forum => Upgrade Warnings => Topic started by: se7en on 2014/10/12, 10:28:00

Title: Chromium 38 trouble with syncing?
Post by: se7en on 2014/10/12, 10:28:00: Latest chromium does give me a warning the some API's are disabled and that therefor some services would not work.
Upgrading crashes chromium.
Deleting .config/chromium and restarting does not let me sign in and sync anymore.
Title: Re: Chromium 38 trouble with syncing?
Post by: LN on 2014/10/13, 17:07:26: According to this

http://www.iuculano.it/linux/apt-get-purge-chromium/ (http://www.iuculano.it/linux/apt-get-purge-chromium/)

the chromium package is not maintained in Debian any more.
Title: Re: Chromium 38 trouble with syncing?
Post by: seasons on 2014/10/14, 12:17:34: ^No, it just says that one maintainer had collaborative issues with another maintainer. It does not mean that it's unmaintained...
Title: Re: Chromium 38 trouble with syncing?
Post by: spacepenguin on 2014/10/21, 23:22:43: Any news - i.e. a fix - for this issue? Installing chromium_38.0.2125.101-3 over 38.0.2125.101-2+b1 didn't bring any change...
Title: Re: Chromium 38 trouble with syncing?
Post by: ajavibp on 2014/10/24, 10:55:47: I have the same issue :(
Title: Re: Chromium 38 trouble with syncing?
Post by: ajavibp on 2014/11/04, 12:14:28: I still have the problem, do not know any solution or workaround.
Title: Re: Chromium 38 trouble with syncing?
Post by: ralul on 2014/11/04, 21:01:01: Maybe adding to your sources.list
deb http://dl.google.com/linux/chrome/deb stable main
Rationale:
- If nobody of the opensource community can inspect the code
- if you would have used Pepperflash regardlessly
Why not trust the original package?
Title: Re: Chromium 38 trouble with syncing?
Post by: bluelupo on 2014/11/05, 17:35:06: Currently, the only Workaaround, either a HOLD on the last version 37 or as proposed by ralul, instead install the Google browser (google-chrome-stable). The 38 version of chromium browser in SID is not usable.

This "history" with the Debian maintainer of chromium gets again negatively felt by the user.
Title: Re: Chromium 38 trouble with syncing?
Post by: ajavibp on 2014/11/05, 17:47:30: I added the Google repository, but I get the same version, no earlier versions.
Code: [Select]
javi@toshi:~$ apt-cache show chromium Package: chromium Source: chromium-browser Version: 38.0.2125.101-3 Installed-Size: 140297I'm goint to install Chrome for now, I guess, as bluelupo says, is the only solution.
Title: Re: Chromium 38 trouble with syncing?
Post by: bluelupo on 2014/11/05, 21:36:15: Hi ajavibp,
You can take as chromium substitute the browser directly from Google (Repo http://dl.google.com/linux/chrome/deb/), which is available in later versions. The extent to which versions are comparable, however, I can not judge.

Code: [Select]
google-chrome-stable: Installiert: 38.0.2125.111-1 Installationskandidat: 38.0.2125.111-1 Versionstabelle: *** 38.0.2125.111-1 0 500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages 100 /var/lib/dpkg/status google-chrome-beta: Installiert: (keine) Installationskandidat: 39.0.2171.52-1 Versionstabelle: 39.0.2171.52-1 0 500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages google-chrome-unstable: Installiert: (keine) Installationskandidat: 40.0.2209.0-1 Versionstabelle: 40.0.2209.0-1 0 500 http://dl.google.com/linux/chrome/deb/ stable/main amd64 Packages
Title: Re: Chromium 38 trouble with syncing?
Post by: ajavibp on 2014/11/06, 12:28:12: Yes, i did it. I hope this can be solved soon.
Thanks!
Title: Re: Chromium 38 trouble with syncing?
Post by: DeKa on 2014/11/06, 16:39:53: Eine Möglichkeit die Meldung zu beseitigen ist den alten Key von debian einzutragen:

[Gelöst] Chromium "Google API keys missing" (https://debianforum.de/forum/viewtopic.php?f=29&t=152252#p1012273) (https://debianforum.de/forum/styles/debianforum/imageset/icon_post_target_unread.gif) (https://debianforum.de/forum/viewtopic.php?p=1012273#p1012273)von lightonflux (https://debianforum.de/forum/memberlist.php?mode=viewprofile&u=38031) am 06.11.2014 13:58:18
Wenn man Chromium nutzt und immer schön aktualisiert hat, dann kann es passiert sein dass man beim starten die Meldung bekommt dass die Google API keys fehlen.

In die Datei /etc/chromium.d/googleapikeys schreibt man:

Code: [Select]
export GOOGLE_API_KEY="AIzaSyCkfPOPZXDKNn8hhgu3JrA62wIgC93d44k" export GOOGLE_DEFAULT_CLIENT_ID="811574891467.apps.googleusercontent.com" export GOOGLE_DEFAULT_CLIENT_SECRET="kdloedMFGdGla2P1zacGjAQh"
Bei den Keys handelt es sich um die alten, die bei den vorigen Releases in Debian genutzt wurden.

Möchte man nur die Meldung los werden aber die Funktionalität ist egal dann einfach folgendes eintragen:

Code: [Select]
export GOOGLE_API_KEY="" export GOOGLE_DEFAULT_CLIENT_ID="" export GOOGLE_DEFAULT_CLIENT_SECRET=""
Hier noch ein Artikel von LWN (http://lwn.net/Articles/570485/) der die Umstände beschreibt wodurch die Situation zu stande gekommen ist.

Vielleicht hilft euch das weiter.
Welchen Sync von Chromium meintet ihr?
Title: Re: Chromium 38 trouble with syncing?
Post by: ajavibp on 2014/11/06, 16:56:22: I had no /etc/chromium.d/googleapikeys file :o
I tried creating it with empty data, but nothing change.
Title: Re: Chromium 38 trouble with syncing?
Post by: spacepenguin on 2014/11/06, 21:13:52: I created the file /etc/chromium.d/googleapikeys, added the export lines with the keys and voilà - seems to work, chromium can sync again etc.! :) Thanks a lot, DeKa!
Title: Re: Chromium 38 trouble with syncing?
Post by: se7en on 2014/11/07, 08:13:45: Thanks.

I am quite happy with google-chrome-unstable v40
You can switch user. Very useful.
Hope chromium gets fixed soon but till than I stay with chrome
Title: Re: Chromium 38 trouble with syncing?
Post by: ajavibp on 2014/11/07, 16:02:04: Quote from: se7en on 2014/11/07, 08:13:45
Thanks.

I am quite happy with google-chrome-unstable v40
You can switch user. Very useful.
Hope chromium gets fixed soon but till than I stay with chrome

Thanks to all!, I understood previously that the key should be empty. Filling the file chromium works again ;)

Seven, I think you should mark the post as solved.