Device registration failed with fatal error after update


Description of the issue:
I recently upgraded my KDE Neon to 22.04 (from 20.04) and with this upgrade, my Brave Browser got upgraded to:

Brave Browser 108.1.46.140

Now, the browser is not opening any web pages, and I see the following error when starting the browser from CLI with:

brave-browser --verbose

mesa: for the --simplifycfg-sink-common option: may only occur zero or one times!
mesa: for the --global-isel-abort option: may only occur zero or one times!
mesa: for the --amdgpu-atomic-optimizations option: may only occur zero or one times!
[230497:230497:1213/214215.390581:ERROR:sharing_service.cc(222)] Device registration failed with fatal error

It also uses a lot of CPU, and does nothing:

I tried installing, purging, reinstalling, install nightly, but, the same error. I have Firefox and Chromium, and both of them are working fine.

How can this issue be reproduced?

  1. Install the latest version of Brave on KDE/Kubuntu/Ubuntu 22.04
  2. start brave with brave-browser --verbose
  3. observe the error

Expected result:
It should open the pages, as expected.

Brave Version( check About Brave): 108.1.46.140

Additional Information:

Hello @rkt

Thank you for reaching out and sorry to hear you’re having trouble with Brave. Could you kindly try installing the Beta or Nightly version of Brave to see if the issue persists on those versions.

Be waiting for your response!

Hey @Alice2095 -
Just tried with Nightly as well, that sharing error is no longer there, but, still it does not work:

brave-browser-nightly --verbose
mesa: for the --simplifycfg-sink-common option: may only occur zero or one times!
mesa: for the --global-isel-abort option: may only occur zero or one times!
mesa: for the --amdgpu-atomic-optimizations option: may only occur zero or one times!

Nightly Version I have:

brave-browser-nightly --version
Brave Browser 108.1.48.51 nightly

Nightly too :rocket: the :computer: CPU from 2% to 80% in under 5 second after opening the browser.
This behaviour is there in the stable version as well.

brave-browser --version
Brave Browser 108.1.46.140 

@Alice2095

I just updated Brave Nightly and Brave Browser to latest versions:

❯ brave-browser --version
Brave Browser 108.1.46.144 
❯ brave-browser-nightly --version
Brave Browser 109.1.48.61 nightly

Still, the error persists.

@Alice2095 - do you need additional Data?
I :bomb: Brave data Directory and do a clean slate install, still the same issue.

Looks like a problem with Chromium Core than with Brave. Just installed Opera (another Chromium-based browser) and Update Chrome to latest, all of them stopped working working :frowning:

any updates? is this a known issue? does not seem to be working with all of the following :

  • stable
  • beta
  • alpha

has someone from the Brave team looked into this issue or planning to?

Hello @rkt

how did you install brave using snap or the 4 command line from this link

make sure to use the release version

does this help or not?

if not then could you run brave using this flag --disable-gpu it will disable the hardware acceleration

hope that help and have a nice day :slight_smile:

Hi @justsomeone1,
I am not a big snap fan, so, I used following to install Brave:

and I tried running with gpu acceleration disabled with this

brave-browser --disable-gpu

but, this time I got this error:

[2093893:2093893:0130/163346.758168:ERROR:sharing_service.cc(222)] Device registration failed with fatal error

my brave version currently is:

brave-browser --disable-gpu --version
Brave Browser 109.1.47.186 

Hello @rkt

do you have dual gpu on your system ?

could you try to change the default gpu or at least make brave run with certain gpu and if it did not work could you try the other one

hope one of those help and have a nice day :slight_smile:

Hi @justsomeone1 - not exactly sure if I have dual GPU:

image

this is hardware info for GPU:
image

No worries mate, I have given up hope of being able to use Brave in near future.

i guess you have single gpu but to make sure could you run this command

sudo lshw -numeric -C display

here my output

notice the 2 *-display which mean i have 2 gpu

another thing did you enabled any flags from here brave://flags/ if you did try to start brave using --no-experiments flags and see if it start up

Hey @justsomeone1 : I have just one GPU, here is my output:

*-display                 
       description: VGA compatible controller
       product: Lucienne [1002:164C]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: /dev/fb0
       version: c1
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi msix vga_controller bus_master cap_list fb
       configuration: depth=32 driver=amdgpu latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080
       resources: iomemory:40-3f iomemory:40-3f irq:46 memory:460000000-46fffffff memory:470000000-4701fffff ioport:1000(size=256) memory:fd600000-fd67ffff

and it eats a bit less CPU with the --no-experiments flag, but, still nothing loads.

i did some research and here what i found

read both of them and see if the answer their could help or not

it’s for chrome but still valid for brave

hope this one nail it

@justsomeone1 - I am not sure about v=1 flag, but, it fixed the issue for me

brave-browser --v=1
mesa: for the --simplifycfg-sink-common option: may only occur zero or one times!
mesa: for the --global-isel-abort option: may only occur zero or one times!
mesa: for the --amdgpu-atomic-optimizations option: may only occur zero or one times!
[3504239:3504239:0212/082005.374150:ERROR:sharing_service.cc(222)] Device registration failed with fatal error

I see the errors, but, Brave works. Thanks mate .

you welcome @rkt

i also not sure how v make it work as from this link --v is about setting the log level

Gives the default maximal active V-logging level; 0 is the default. Normally positive values are used for V-logging levels.

but glad it helped to fix your issue hope chrome fix it so you be able to run it without this flag

and have a nice day :slight_smile:

so, these error messages were never a problem:

mesa: for the --simplifycfg-sink-common option: may only occur zero or one times!
mesa: for the --global-isel-abort option: may only occur zero or one times!
mesa: for the --amdgpu-atomic-optimizations option: may only occur zero or one times!
[1281472:1281472:0228/121421.673979:ERROR:sharing_service.cc(222)] Device registration failed with fatal error
[1281513:1281513:0228/121650.724183:ERROR:shared_image_manager.cc(197)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
[1281513:1281513:0228/121650.725872:ERROR:shared_image_manager.cc(197)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
[1281513:1281513:0228/121650.728337:ERROR:shared_image_manager.cc(197)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
[1281513:1281513:0228/121650.728715:ERROR:shared_image_manager.cc(197)] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
[1281472:1281496:0228/125315.532473:ERROR:get_updates_processor.cc(264)] PostClientToServerMessage() failed during GetUpdates with error 2
[1281513:1281513:0228/130815.138951:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[1281513:1281513:0228/144905.467296:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[1281513:1281513:0228/183850.685752:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!

after:

brave-browser --v=1 &

I have been using Brave without any problem.

1 Like

glad to hear that @rkt

when you get an update for brave try to use it without the v flag and see if the update fix it and if not then keep using the flag

and have a nice day :slight_smile:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.