LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Error with google-chrome 69, slackware 14.2 (https://www.linuxquestions.org/questions/slackware-14/error-with-google-chrome-69-slackware-14-2-a-4175638445/)

garpu 09-15-2018 07:05 AM
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.

Darth Vader 09-15-2018 07:12 AM
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. :D

Gordie 09-15-2018 07:45 AM
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

Darth Vader 09-15-2018 07:54 AM
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

55020 09-15-2018 07:56 AM
Quote:
Originally Posted by garpu (Post 5903622)
/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.

kjhambrick 09-15-2018 08:06 AM
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

garpu 09-15-2018 09:21 AM
Quote:
Originally Posted by 55020 (Post 5903642)
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.)

Darth Vader 09-15-2018 10:33 AM
Quote:
Originally Posted by 55020 (Post 5903642)
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? ;)

glorsplitz 09-16-2018 08:43 AM
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.

Alien Bob 09-16-2018 09:13 AM
Quote:
Originally Posted by Darth Vader (Post 5903685)
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?

bassmadrigal 09-17-2018 06:55 PM
Quote:
Originally Posted by Darth Vader (Post 5903685)
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)...

kjhambrick 09-18-2018 12:39 AM
Quote:
Originally Posted by bassmadrigal (Post 5904670)

<<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


All times are GMT -5. The time now is 03:07 AM.