Google Chrome GPU Driver Issues on Ubuntu 18.04
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I am having some problems starting Google Chrome on Ubuntu 18.04, and it seems to have something to do with my GPU driver--however, I do not know for sure.
I tried google-chrome from the command line, and it gave me the following;
theo@nitrates:~$ google-chrome
[29617:29617:1003/171104.939355:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
[29617:29617:1003/171105.478055:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.490579:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.531946:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.569271:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.585473:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.595687:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.665439:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.678878:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.869643:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.908701:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.012723:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.014180:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.030990:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.041881:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.062463:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
Some important things to note:
- There seems to be (some) unpredictability in this issue. Several times I have simply clicked on chrome or started it from the command line, and it starts up just fine. It is almost as if it goes through phases of working and not working.
- There seems to be a slightly higher rate of success when attempting to start it right after the computer has restarted / woken up from being shut down.
- This is a MacBook Pro from 2010 (15 inch retina), with the NVIDIA GeForce GT 330M and the "Intel HD Graphics with 256 MB of DDR3 SDRAM" as per this site.
EDIT:
Tried google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests as recommended in this answer, and got the following error:
[1416:1416:1003/175305.577073:ERROR:gl_implementation.cc(291)] Failed to load /opt/google/chrome/libosmesa.so: /opt/google/chrome/libosmesa.so: cannot open shared object file: No such file or directory
[1416:1416:1003/175305.579670:ERROR:viz_main_impl.cc(236)] Exiting GPU process due to errors during initialization
[1361:1379:1003/175305.581582:ERROR:service_manager_context.cc(270)] Attempting to run unsupported native service: /opt/google/chrome/content_gpu.service
[1361:1361:1003/175306.061430:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.
ubuntu drivers chrome gpu
asked Oct 4 at 0:20
Theodore Weld
1084
New contributor
Theodore Weld is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
 |Â
show 1 more comment
up vote
1
down vote
favorite
I am having some problems starting Google Chrome on Ubuntu 18.04, and it seems to have something to do with my GPU driver--however, I do not know for sure.
I tried google-chrome from the command line, and it gave me the following;
theo@nitrates:~$ google-chrome
[29617:29617:1003/171104.939355:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
[29617:29617:1003/171105.478055:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.490579:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.531946:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.569271:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.585473:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.595687:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.665439:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.678878:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.869643:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.908701:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.012723:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.014180:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.030990:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.041881:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.062463:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
Some important things to note:
- There seems to be (some) unpredictability in this issue. Several times I have simply clicked on chrome or started it from the command line, and it starts up just fine. It is almost as if it goes through phases of working and not working.
- There seems to be a slightly higher rate of success when attempting to start it right after the computer has restarted / woken up from being shut down.
- This is a MacBook Pro from 2010 (15 inch retina), with the NVIDIA GeForce GT 330M and the "Intel HD Graphics with 256 MB of DDR3 SDRAM" as per this site.
EDIT:
Tried google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests as recommended in this answer, and got the following error:
[1416:1416:1003/175305.577073:ERROR:gl_implementation.cc(291)] Failed to load /opt/google/chrome/libosmesa.so: /opt/google/chrome/libosmesa.so: cannot open shared object file: No such file or directory
[1416:1416:1003/175305.579670:ERROR:viz_main_impl.cc(236)] Exiting GPU process due to errors during initialization
[1361:1379:1003/175305.581582:ERROR:service_manager_context.cc(270)] Attempting to run unsupported native service: /opt/google/chrome/content_gpu.service
[1361:1361:1003/175306.061430:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.
ubuntu drivers chrome gpu
asked Oct 4 at 0:20
Theodore Weld
1084
New contributor
Theodore Weld is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
– Goro
Oct 4 at 0:38
@Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
– Theodore Weld
Oct 4 at 0:44
1
Sure thing, thanks!
– Theodore Weld
Oct 4 at 0:52
1
Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
– Theodore Weld
Oct 4 at 0:55
@Goro I did check this—doesn’t seem to be there.
– Theodore Weld
Oct 4 at 0:59
 |Â
show 1 more comment
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am having some problems starting Google Chrome on Ubuntu 18.04, and it seems to have something to do with my GPU driver--however, I do not know for sure.
I tried google-chrome from the command line, and it gave me the following;
theo@nitrates:~$ google-chrome
[29617:29617:1003/171104.939355:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
[29617:29617:1003/171105.478055:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.490579:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.531946:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.569271:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.585473:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.595687:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.665439:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.678878:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.869643:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.908701:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.012723:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.014180:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.030990:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.041881:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.062463:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
Some important things to note:
- There seems to be (some) unpredictability in this issue. Several times I have simply clicked on chrome or started it from the command line, and it starts up just fine. It is almost as if it goes through phases of working and not working.
- There seems to be a slightly higher rate of success when attempting to start it right after the computer has restarted / woken up from being shut down.
- This is a MacBook Pro from 2010 (15 inch retina), with the NVIDIA GeForce GT 330M and the "Intel HD Graphics with 256 MB of DDR3 SDRAM" as per this site.
EDIT:
Tried google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests as recommended in this answer, and got the following error:
[1416:1416:1003/175305.577073:ERROR:gl_implementation.cc(291)] Failed to load /opt/google/chrome/libosmesa.so: /opt/google/chrome/libosmesa.so: cannot open shared object file: No such file or directory
[1416:1416:1003/175305.579670:ERROR:viz_main_impl.cc(236)] Exiting GPU process due to errors during initialization
[1361:1379:1003/175305.581582:ERROR:service_manager_context.cc(270)] Attempting to run unsupported native service: /opt/google/chrome/content_gpu.service
[1361:1361:1003/175306.061430:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.
ubuntu drivers chrome gpu
asked Oct 4 at 0:20
Theodore Weld
1084
New contributor
Theodore Weld is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am having some problems starting Google Chrome on Ubuntu 18.04, and it seems to have something to do with my GPU driver--however, I do not know for sure.
I tried google-chrome from the command line, and it gave me the following;
theo@nitrates:~$ google-chrome
[29617:29617:1003/171104.939355:ERROR:sandbox_linux.cc(379)] InitializeSandbox() called with multiple threads in process gpu-process.
[29617:29617:1003/171105.478055:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.490579:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.531946:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.569271:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.585473:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.595687:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.665439:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.678878:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.869643:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171105.908701:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.012723:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.014180:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.030990:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.041881:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
[29617:29617:1003/171106.062463:ERROR:gl_surface_presentation_helper.cc(161)] GetVSyncParametersIfAvailable() failed!
Some important things to note:
- There seems to be (some) unpredictability in this issue. Several times I have simply clicked on chrome or started it from the command line, and it starts up just fine. It is almost as if it goes through phases of working and not working.
- There seems to be a slightly higher rate of success when attempting to start it right after the computer has restarted / woken up from being shut down.
- This is a MacBook Pro from 2010 (15 inch retina), with the NVIDIA GeForce GT 330M and the "Intel HD Graphics with 256 MB of DDR3 SDRAM" as per this site.
EDIT:
Tried google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests as recommended in this answer, and got the following error:
[1416:1416:1003/175305.577073:ERROR:gl_implementation.cc(291)] Failed to load /opt/google/chrome/libosmesa.so: /opt/google/chrome/libosmesa.so: cannot open shared object file: No such file or directory
[1416:1416:1003/175305.579670:ERROR:viz_main_impl.cc(236)] Exiting GPU process due to errors during initialization
[1361:1379:1003/175305.581582:ERROR:service_manager_context.cc(270)] Attempting to run unsupported native service: /opt/google/chrome/content_gpu.service
[1361:1361:1003/175306.061430:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.
ubuntu drivers chrome gpu
ubuntu drivers chrome gpu
asked Oct 4 at 0:20
Theodore Weld
1084
New contributor
Theodore Weld is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Oct 4 at 0:20
Theodore Weld
1084
New contributor
Theodore Weld is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Oct 4 at 0:56
asked Oct 4 at 0:20
Theodore Weld
1084
New contributor
Theodore Weld is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Oct 4 at 0:20
Theodore Weld
1084
asked Oct 4 at 0:20
Theodore Weld
1084
1084
New contributor
Theodore Weld is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Theodore Weld is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Theodore Weld is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
– Goro
Oct 4 at 0:38
@Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
– Theodore Weld
Oct 4 at 0:44
1
Sure thing, thanks!
– Theodore Weld
Oct 4 at 0:52
1
Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
– Theodore Weld
Oct 4 at 0:55
@Goro I did check this—doesn’t seem to be there.
– Theodore Weld
Oct 4 at 0:59
 |Â
show 1 more comment
Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
– Goro
Oct 4 at 0:38
@Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
– Theodore Weld
Oct 4 at 0:44
1
Sure thing, thanks!
– Theodore Weld
Oct 4 at 0:52
1
Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
– Theodore Weld
Oct 4 at 0:55
@Goro I did check this—doesn’t seem to be there.
– Theodore Weld
Oct 4 at 0:59
Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
– Goro
Oct 4 at 0:38
Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
– Goro
Oct 4 at 0:38
@Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
– Theodore Weld
Oct 4 at 0:44
@Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
– Theodore Weld
Oct 4 at 0:44
1
1
Sure thing, thanks!
– Theodore Weld
Oct 4 at 0:52
Sure thing, thanks!
– Theodore Weld
Oct 4 at 0:52
1
1
Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
– Theodore Weld
Oct 4 at 0:55
Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
– Theodore Weld
Oct 4 at 0:55
@Goro I did check this—doesn’t seem to be there.
– Theodore Weld
Oct 4 at 0:59
@Goro I did check this—doesn’t seem to be there.
– Theodore Weld
Oct 4 at 0:59
 |Â
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
6
down vote
I would suggest that you do the following:
1) Check whether you have "libgles2-mesa" installed? If not, then install it.
2) Try disabling GPU-accelerated compositing under the flag "--use-gl=osmesa" using the command:
google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests
answered Oct 4 at 0:48
Goro
7,24753168
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
I would suggest that you do the following:
1) Check whether you have "libgles2-mesa" installed? If not, then install it.
2) Try disabling GPU-accelerated compositing under the flag "--use-gl=osmesa" using the command:
google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests
answered Oct 4 at 0:48
Goro
7,24753168
add a comment |Â
up vote
6
down vote
I would suggest that you do the following:
1) Check whether you have "libgles2-mesa" installed? If not, then install it.
2) Try disabling GPU-accelerated compositing under the flag "--use-gl=osmesa" using the command:
google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests
answered Oct 4 at 0:48
Goro
7,24753168
add a comment |Â
up vote
6
down vote
up vote
6
down vote
I would suggest that you do the following:
1) Check whether you have "libgles2-mesa" installed? If not, then install it.
2) Try disabling GPU-accelerated compositing under the flag "--use-gl=osmesa" using the command:
google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests
answered Oct 4 at 0:48
Goro
7,24753168
I would suggest that you do the following:
1) Check whether you have "libgles2-mesa" installed? If not, then install it.
2) Try disabling GPU-accelerated compositing under the flag "--use-gl=osmesa" using the command:
google-chrome --use-gl=osmesa --disable-gl-drawing-for-tests
answered Oct 4 at 0:48
Goro
7,24753168
answered Oct 4 at 0:48
Goro
7,24753168
answered Oct 4 at 0:48
Goro
7,24753168
answered Oct 4 at 0:48
Goro
7,24753168
7,24753168
add a comment |Â
add a comment |Â
Theodore Weld is a new contributor. Be nice, and check out our Code of Conduct.
Â
draft saved
draft discarded
Theodore Weld is a new contributor. Be nice, and check out our Code of Conduct.
Theodore Weld is a new contributor. Be nice, and check out our Code of Conduct.
Theodore Weld is a new contributor. Be nice, and check out our Code of Conduct.
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f473115%2fgoogle-chrome-gpu-driver-issues-on-ubuntu-18-04%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Hello @Theodore Weld. Did you see this issue in previous versions of google chrome? or just after and upgrade to a newer version?
– Goro
Oct 4 at 0:38
@Goro I do not know if this has something to do with an update necessarily. Currently I am on 69.0.3497.92 and have not ever updated it myself since installation.
– Theodore Weld
Oct 4 at 0:44
1
Sure thing, thanks!
– Theodore Weld
Oct 4 at 0:52
1
Yeah so it seems that that file does not exist, I will update my answer with the error as that would be a nicer way to see it.
– Theodore Weld
Oct 4 at 0:55
@Goro I did check this—doesn’t seem to be there.
– Theodore Weld
Oct 4 at 0:59