Description of the issue:
I Installed brave as normal and have some plugins installed as well. It works well but after a while I decide to lock my computer using xscreensaver. When I unlock my computer, brave crashes. If I open it again, It crashes again.
Steps to Reproduce (add as many as necessary): 1. 2. 3.
Install Arch Linux
Install Gnome
Install Xscreensaver
Install Brave
Run brave as normal (maybe install plugins)
lock screen via xscreesaver (xscreensaver-command -lock)
unlock screen & wait for crash
Actual Result (gifs and screenshots are welcome!):
Terminal output:
~
❯ brave
[40468:40468:0615/113422.402812:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.
[40468:40468:0615/113423.424980:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.UnknownMethod: Unknown method GetActive or interface org.freedesktop.ScreenSaver.
[40468:40468:0615/113423.425975:ERROR:object_proxy.cc(590)] Failed to call method: org.gnome.ScreenSaver.GetActive: object_path= /org/gnome/ScreenSaver: org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files
[0615/113433.380268:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0615/113433.380861:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0615/113433.381046:ERROR:elf_dynamic_array_reader.h(64)] tag not found
zsh: segmentation fault (core dumped) brave
~ took 12s
❯ brave -debug
[40894:40894:0615/113442.360668:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.
[40894:40894:0615/113443.383661:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.UnknownMethod: Unknown method GetActive or interface org.freedesktop.ScreenSaver.
[40894:40894:0615/113443.385104:ERROR:object_proxy.cc(590)] Failed to call method: org.gnome.ScreenSaver.GetActive: object_path= /org/gnome/ScreenSaver: org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files
[0615/113455.515028:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0615/113455.515406:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0615/113455.515517:ERROR:elf_dynamic_array_reader.h(64)] tag not found
zsh: segmentation fault (core dumped) brave -debug
~ took 15s
❯
Expected result:
Not Crashing…
Reproduces how often:
Been Happening every time i open brave, only after activating xscreensaver.
@mr_patcher please go to brave://crashes and make sure everything there is uploaded. (If you have to hit the upload button, you’ll need to close your browser for like 30 seconds and then reopen Brave for it to actually upload). Then provide the Uploaded Crash Report ID.
Maybe try without them? Especially if you’re referencing extensions.
Looks like I can’t seem to replicate this crash (with & without extensions). Perhaps it could be an issue related to multi monitor setup? because I’m testing it without my 2nd monitor at the moment.
Also should I click the provide additional details button and create a github issue ?
@mr_patcher I wouldn’t create Github unless able to replicate. Purpose in sharing the crash report ID is so support and developers can pull the records. One thing I’ll advise is that they don’t tend to actively work here on Community over the weekend. So means won’t likely get any further replies until after Monday.
I’ll tag @Mattches in on this, so hopefully he’ll swing by when he gets back. In the meanwhile, I guess it gives you the weekend to test and see if you can find the trigger or at least might be able to narrow things down with whatever you figure out.
@Mattches@steeven seems we haven’t had a follow-up in about a month. Wanted to tag you in on it to see if you were able to learn anything from devs last time they shared crash ID?