LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-15-2018, 07:05 AM   #1
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 153

Rep: Reputation: 58
Error with google-chrome 69, slackware 14.2


google-chrome 69.0.3497.92, installed via Pat's slackbuild found in /extra; Slackware 14.2 multilib.

Since updating to chrome 69, I've been getting the following error in syslog once when I start the browser:

[1549:1549:0915/074713.090855:ERROR:browser_dm_token_storage_linux.cc(93)] Error: /etc/machine-id contains 32 characters (32 were expected).

Only thing I can find with it is that it's connected to a systemd function. For the record, I'm not looking for alternatives. I'm not married to chrome, and if it does require systemd in the future, I'll happily go back to firefox.

Does this mean there will be problems for the use of chrome/chromium and Slackware in the near future? The browser still starts and runs fine.
 
Old 09-15-2018, 07:12 AM   #2
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,699

Rep: Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205
Then, apparently another major software behind Skype started to use the systemd features...

I for one, I can't wait to see if the Plasma6 will work without systemd - two years will pass quite fast, after all.

Last edited by Darth Vader; 09-15-2018 at 07:13 AM.
 
Old 09-15-2018, 07:45 AM   #3
Gordie
Member
 
Registered: Aug 2007
Posts: 410

Rep: Reputation: 134Reputation: 134
I use ruario's script to repackage Chrome. The one I run now is
Version 69.0.3497.92 (Official Build) (64-bit).

There is no problem for me
 
Old 09-15-2018, 07:54 AM   #4
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,699

Rep: Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205
BTW, speaking only about Eric's latest Chromium...
Code:
bash-4.4# chromium

(chromium:22026): Gtk-WARNING **: 15:51:57.553: Theme parsing error: gtk.css:127:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(chromium:22026): Gtk-WARNING **: 15:51:57.553: Theme parsing error: gtk.css:128:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(chromium:22026): Gtk-WARNING **: 15:51:57.553: Theme parsing error: gtk.css:132:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version
[22026:22026:0915/155158.886321:ERROR:browser_dm_token_storage_linux.cc(93)] Error: /etc/machine-id contains 32 characters (32 were expected).
[22073:22073:0915/155203.531911:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
[22267:22267:0915/155212.319682:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
[22318:22318:0915/155219.159378:ERROR:webthread_impl_for_utility_thread.cc(19)] Not implemented reached in virtual blink::ThreadScheduler *blink::scheduler::WebThreadImplForUtilityThread::Scheduler() const
 
Old 09-15-2018, 07:56 AM   #5
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,279
Blog Entries: 4

Rep: Reputation: Disabled
Quote:
Originally Posted by garpu View Post
/etc/machine-id contains 32 characters (32 were expected) [...] The browser still starts and runs fine.
That's just some zombie code doing nothing.

Even if chrome ever *requires* a machine-id, we can all just set it to 0xb0ll0c5.

My advice: save the outraged mob with torches for when this becomes an Actual Problem.
 
3 members found this post helpful.
Old 09-15-2018, 08:06 AM   #6
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,423

Rep: Reputation: 829Reputation: 829Reputation: 829Reputation: 829Reputation: 829Reputation: 829Reputation: 829
Yes, I reported the same message for Alien Bob's Chromium on Alien Pastures ... my comment at the time was chromium worked fine and "my machine-id is none of google's business" ...

Code:
konrad@kjhlt6 ~]$ chromium &
[1] 9503
[konrad@kjhlt6 ~]$ [9503:9503:0915/080002.692059:ERROR:browser_dm_token_storage_linux.cc(93)] Error: /etc/machine-id contains 32 characters (32 were expected).
[1]+  Done                    chromium
This page: https://www.freedesktop.org/software...achine-id.html seems to be all about systemd.

But it mentions at the end under History that /etc/machine-id may be a Symlink to /var/lib/dbus/machine-id

I made the link as root:
Code:
# ln -s /var/lib/dbus/machine-id /etc/machine-id
And now chromium no longer complains:
Code:
[konrad@kjhlt6 ~]$ chromium &
[1] 9256
[konrad@kjhlt6 ~]$ 
1]+  Done                    chromium
And as a Bonus, there seem to be no ill-effects of having the /etc/machine-id SymLink on my System

I meant to mention this but I fixed it and then forgot all about it

-- kjh

Last edited by kjhambrick; 09-15-2018 at 08:10 AM. Reason: omment -> comment
 
2 members found this post helpful.
Old 09-15-2018, 09:21 AM   #7
garpu
Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 153

Original Poster
Rep: Reputation: 58
Quote:
Originally Posted by 55020 View Post
That's just some zombie code doing nothing.

Even if chrome ever *requires* a machine-id, we can all just set it to 0xb0ll0c5.

My advice: save the outraged mob with torches for when this becomes an Actual Problem.
Yeah, that's kind of what I thought, since chrome still works. I'm not too worried about it, but was wondering if it was going to be a bigger problem down the road. (Namely, if I should dust off firefox, import bookmarks, etc. Probably a good idea, anyway, given the old adage about eggs and baskets.)
 
Old 09-15-2018, 10:33 AM   #8
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,699

Rep: Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205Reputation: 1205
Quote:
Originally Posted by 55020 View Post
My advice: save the outraged mob with torches for when this becomes an Actual Problem.
Like in the suddenly need for at least of a functional elogind package, when there's no one, right?
 
Old 09-16-2018, 08:43 AM   #9
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 631

Rep: Reputation: 123Reputation: 123
Try ruario's script, what happens?

Using that script I have Chrome Version 69.0.3497.92 (Official Build) (64-bit) and have never had any problems with Chrome.
 
Old 09-16-2018, 09:13 AM   #10
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,221

Rep: Reputation: 5232Reputation: 5232Reputation: 5232Reputation: 5232Reputation: 5232Reputation: 5232Reputation: 5232Reputation: 5232Reputation: 5232Reputation: 5232Reputation: 5232
Quote:
Originally Posted by Darth Vader View Post
Like in the suddenly need for at least of a functional elogind package, when there's no one, right?
I still have not yet seen proof that this is the only solution. Perhaps someone who hates logind and wants to have Skype functional on Slackware, can contact Microsoft?
 
Old 09-17-2018, 06:55 PM   #11
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,296

Rep: Reputation: 3043Reputation: 3043Reputation: 3043Reputation: 3043Reputation: 3043Reputation: 3043Reputation: 3043Reputation: 3043Reputation: 3043Reputation: 3043Reputation: 3043
Quote:
Originally Posted by Darth Vader View Post
Like in the suddenly need for at least of a functional elogind package, when there's no one, right?
There is an actual problem with skype. There isn't one for Chrome. Let's keep the skype problem on the skype thread.

@kjhambrick - Nice idea! I'm curious if there's any potential repercussions or if this is a decent fix to prevent that warning (and other future warnings on things that might also rely on machine-id)...
 
2 members found this post helpful.
Old 09-18-2018, 12:39 AM   #12
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,423

Rep: Reputation: 829Reputation: 829Reputation: 829Reputation: 829Reputation: 829Reputation: 829Reputation: 829
Quote:
Originally Posted by bassmadrigal View Post

<<snip>>

@kjhambrick - Nice idea! I'm curious if there's any potential repercussions or if this is a decent fix to prevent that warning (and other future warnings on things that might also rely on machine-id)...
Thanks bassmadrigal.

This one is a 'definitely, maybe, I dunno'

So far so good thru a kernel build ; update ; boot ( 4.4.155.kjh -> 4.4.156.kjh ) and several SBo updates this week on Slackware 64 14.2 + Multilib + NVidia 390.87 blob laptop.

I also verified that symlinking /etc/machine-id to the existing /var/lib/dbus/machine-id eliminated the same error message for google-chrome built via rurio's SlackBuild on my laptop.

Code:
# ver chromium google-chrome
-rw-r--r-- 1 root root 27727 Sep 12 01:46 /var/log/packages/chromium-69.0.3497.81-x86_64-1alien
-rw-r--r-- 1 root root  1593 Aug 15 18:22 /var/log/packages/chromium-pepperflash-plugin-30.0.0.154-x86_64-1alien
-rw-r--r-- 1 root root  1377 Jan 10  2018 /var/log/packages/chromium-widevine-plugin-1.4.8.1008-x86_64-1alien
-rw-r--r-- 1 root root  4906 Sep 15 09:09 /var/log/packages/google-chrome-69.0.3497.92-x86_64-1ro
And I believe that's the more-or-less the issue reported by the OP in this thread ...

But I still believe that my machine-id is none of google's business

-- kjh
 
2 members found this post helpful.
  


Reply

Tags
chrome browser


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
google-chrome issues Slackware 14.2 jhsdcsjdcvbdj Slackware 12 02-12-2017 06:35 PM
Google Chrome and Slackware moisespedro Slackware 2 11-13-2013 12:14 PM
[SOLVED] This there a Slackware version of Google Chromium Browser? (not Google Chrome) Robert.Thompson Slackware 6 01-13-2011 05:27 AM
[SOLVED] Google Talk Plugin, Slackware64-Current, Google Chrome (Latest) and Multilib - Error Gavin Harper Slackware 3 01-04-2011 07:45 AM
[SOLVED] Google-Chrome Error (Error 9 (net::ERR_UNEXPECTED): Unknown error) smoooth103 Slackware 4 12-04-2010 07:42 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:13 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration