-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible bug: Nyxt unexpectadly closes buffer on the dockerized version of Nyxt for macOS #8
Comments
I seem to be able to reproduce. I did see |
yup, quoting the manual:
I'll try to install and eventually update the docker image. nice catch. |
I have installed those:
but the link still causes a crash with the same message.
I'm unsure on what might be going on. Perhaps I did not pull all deps yet? I've a branch with this setup, you can try locally by issuing a docker build. |
Try disabling compositing by setting the environment variable Also could you time the buffer crash? Does it take the exact same number of seconds for each web site? |
disabling compositing did not help, but I did manage to get a more descriptive message.
running with |
that last message brought me to try to install
|
and by logging in the container,
this is also mentioned in XQuartz/XQuartz#144 . I am starting to be a bit worried. so following that, i did try to run in the host
and restarted xquartz. That does display the glxgears and glxinfo, but still no luck with nyxt and youtube. and for what it's worth, it did not resolve the usual suspect:
|
libGL error: failed to load driver: swrast
I know this error: it's a bug between the Nvidia driver and WebKitGTK
compositing.
Do you have an Nvidia?
|
the machine I normally use does not. It's a plain MBP with an intel iris. I might have an old one with an nvidia card, but I'm surprised it matters. Would not that be completely hidden to the docker container, and would not it expect to use just the standard device? |
running with
shows a different error,
Any help really appreciated here. |
I'm afraid I don't know more than other the previous diagnosis, and I
believe the solution lies in passing the right environment variable.
About Nvidia: are you saying your machine has both an embedded Intel
_and_ a discrete Nvidia GPU? If so, I do believe it could be the source
of your problems.
Can you share the output of `lspci -k` from the Docker?
|
I did fiddle a bit with the packages, and I could get to render the youtube page without a crash. Also the video did start playing but it crashed after a bit - here's the output
now, for your question: there's no lspci, I'll install that and post an update. |
Try installing sound-related packages like alsa-lib, alsa-plugins*,
openal, pulseaudio.
You might also want to fiddle with /etc/asound.conf, but I don't know
the details.
|
so, with regard to adding alsa
here's the error
I've updated the dockerfile in the branch issue-8 with those latest changes |
I saw this one in my logs today ... perhaps worthy of further investigation.
|
This is fixed on master.
No worries, it'a harmless.
|
Describe the bug
This video describes what was written in the title.
Precise recipe to reproduce the issue
1 - open Nyxt following the description on Readme "usage for Docker on macOS". Except for this step "Launch a new xterm terminal and ensure you have “DISPLAY=:0” set." which I did not do because I was not sure about how to do it.
2 - open this website. This is something like the Brazilian version of New York Times
3 - Wait. Suddenly, Nyxt will close the buffer
4 - The mini buffer will send an error message which can be read during the video with the bug description
The same problem also happened with my blog's website. This problem does not happen when browsing stuff like
manual
,tutorial
(kind of internal buffers). Both "problematic websites" have always worked fine while using Nyxt on my Linux machine.Information
show-system-information
: (I will send soon)Observation: this bug did not happen to me. I do not owe a mac. I am trying to help a friend who is craving to use Nyxt on his mac.
The text was updated successfully, but these errors were encountered: