GhostBSD with bsdrc crashes brave due to illegal instuction
Izder456 opened this issue · 1 comments
Izder456 commented
If you didn't see, ghostbsd upstream just updated to bsdrc. I figured i'd give installing brave a try.
standard installation, everything worked except i had to manually add the brave repo signing key, no biggie.
but when launching brave from the *.desktop, it crashes.
when loading from cli, this is the error log:
[3047:101300:0823/145029.671656:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[3047:101296:0823/145029.686596:ERROR:file_path_watcher_linux.cc(326)] inotify_init() failed: Function not implemented (38)
[3047:101296:0823/145029.687420:ERROR:address_tracker_linux.cc(195)] Could not create NETLINK socket: Address family not supported by protocol (97)
[3047:101295:0823/145029.710087:ERROR:udev_watcher.cc(52)] Failed to initialize a udev monitor.
[0823/145029.741003:ERROR:ptracer.cc(476)] Unexpected registers size 0 != 216, 68
[0823/145029.741593:ERROR:proc_task_reader.cc(45)] format error
[3047:101318:0823/145029.795924:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[3047:101318:0823/145029.802390:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[3053:101323:0823/145029.839999:ERROR:file_path_watcher_linux.cc(326)] inotify_init() failed: Function not implemented (38)
[3053:101323:0823/145029.840524:ERROR:address_tracker_linux.cc(195)] Could not create NETLINK socket: Address family not supported by protocol (97)
[3047:101318:0823/145029.941380:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[3047:101318:0823/145029.942061:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[3047:101352:0823/145030.851939:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[3047:101352:0823/145030.852525:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[3047:101352:0823/145030.855388:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[3047:101352:0823/145030.855814:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[3047:101352:0823/145030.856157:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[3047:3047:0823/145031.548787:ERROR:CONSOLE(1)] "[Shields]: Can't request shields panel data. Error: No tab url specified", source: chrome-extension://mnojpmjdmbbfmejpflffifhffcmidifd/out/brave_extension_background.bundle.js (1)
[1] 3047 illegal hardware instruction (core dumped) /compat/ubuntu/bin/brave
is this a known issue with the script or just ghostbsd upstreams version of the linuxulator?
i figured id also put my hardware info here too if thats useful :
izder456@Poplar
'+ijwbRMDS+ ---------------
`=uNQge\^,.'FRp OS: FreeBSD 13.0-STABLE amd64
`^9QQRi: .+9Ww; Uptime: 15 mins
'vQQBj' :/+vw#gF^ Packages: 727 (pkg)
'{@@Ri `7DbbNa; Shell: zsh 5.8
`=@@g\ :zBBi' Resolution: 1366x768
`D@Qy +eQQa: DE: MATE 1.24.3
,D@Q_ .sDQQD| WM: Metacity (Marco)
6@Q; .>OQdBQa` Theme: Vimix-Dark [GTK2/3]
@@M:';sq@QySQg{yDx Icons: Qogir-dark [GTK2/3]
w@@@@@#e+?#QQBe* Terminal: mate-terminal
,=?;'`:gQQ#i, CPU: AMD E1-2500 APU (2) @ 1.397GHz
`:d@QE:` CPU Usage: 102%
./Q@Q6' Memory: 2046MiB / 3461MiB
.l@@@b, Battery: 91% Charging
F@QO: