Closed ianyepan closed 3 years ago
ianyepan
commented
3 years ago The current workaround I have (until I solve this issue) is to set the following line in init.el to avoid opening images with EAF altogether:
(setq eaf-find-file-ext-blacklist '("png" "jpg"))
MatthewZMD
commented
3 years ago M-x eaf-open-browser or eaf-open-vue-demo suffer from the same problem. Basically, EAF only works with PDF at this moment for me. Let me know if I should open different issues for different eaf-open functions (one for browser, one for vue demo etc.)
What is in the *eaf* buffer? I suspect the npm install didn't work correctly.
ianyepan
commented
3 years ago @MatthewZMD
This is the complete output of *eaf* when I invoke M-x eaf-open-browser RET google.com RET, in a freshly restarted Emacs instance.
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-yep808'
EAF process starting...
QGLXContext: Failed to create dummy context
QQuickWidget: Failed to make context current
Session is not restored, as no data present in session file.
QQuickWidget: Attempted to render scene with no context
Process *eaf* segmentation faultp.s. yep808 is just my username.
ianyepan
commented
3 years ago I suspect the npm install didn't work correctly.
I see, I just ran ./install-eaf.sh again, and the console output all seems correct though. The script exited rather smoothly.
Edit: The script ran smoothly, but the issue remains unresolved.
ianyepan
commented
3 years ago @manateelazycat Hi Andy, actually the issue isn't resolved yet 😅. I said the script ran smoothly, as an argument against @MatthewZMD 's suspect that it was an npm problem. The original issue (segmentation fault, no response) still remains unsolved. Please kindly reopen the issue :-)
manateelazycat
commented
3 years ago If you got segfault error, please use the following way to collect crash information:
Install gdb and turn on option eaf-enable-debug Use command eaf-stop-process stop current process Restart eaf, send issue with eaf buffer content when next crash
ianyepan
commented
3 years ago @manateelazycat Thanks Andy, I followed the steps on my machine and collected these error messages when trying to open a file (or browser). Again, yep808 is just my username. I'm using Arch Linux WSL2, Emacs 27.2, and GNU gdb (GDB) 10.1.
M-x eaf-open-browser RET google.com RET:manateelazycat
commented
3 years ago From crash context, looks like QOpenGLContext::shareGroup() cause crash. It's perhaps a bug of WSL2 Arch repo, or a bug of QOpenGL with WSL2.
I don't use Windows, and the crash log is clear, not bug of EAF
MatthewZMD
commented
3 years ago @yqu212 could you take a look at this issue?
yqu212
commented
3 years ago @ianpan870102 Please try the following steps:
ianyepan
commented
3 years ago Hi, I tried the steps, but eaf-open-browser crashes with the following error:
Fatal error 6: IOT trap
zsh: abort emacsP.s. Why use Mobaxterm over VcXsrv? The latter provided me with crisp font rendering, while the former left with quite a blurry Emacs instance.
yqu212
commented
3 years ago From the information you provided, it looks like the problem is caused by pyqtwebengine.
I have seen a similar situation under wsl1. Under wsl2, I have not encountered the problem.
So I suggest you start investigating with pyqtwebengine.
You've already ruled out xserver earlier.
A feasible approach now is to run an eaf docker as a way to determine whether there is a problem with wsl and eaf.
I have successfully run the eaf docker under archwsl+wsl2+mobaxterm.
Mobaxterm is not better than vcxser. I just wanted to use it to rule out any problems with the xserver
ianyepan
commented
3 years ago Hi @yqu212 , understood, thanks for getting back to me so promptly.
I'm rather new to Docker -- is there a detailed step-by-step guide that can help me with running an EAF docker? I checked the Wiki (https://github.com/manateelazycat/emacs-application-framework/wiki/Docker), but I can't get pass the first command docker build -t eaf --build-arg=_UID=$UID --build-arg=_USER=$USER .
I am getting an error as follows:
unable to prepare context: unable to evaluate symlinks in Dockerfile pathI am also new to docker. There is no such guide AFAIK.
ianyepan
commented
3 years ago That's okay, guess I'll leave this issue open and hope if anything comes up. In the meanwhile, I'll disable EAF for png and jpg filetypes.
manateelazycat
commented
3 years ago @MatthewZMD Maybe we should remove docker code since EAF has supports Windows/Mac/Linux ?
MatthewZMD
commented
3 years ago @MatthewZMD Maybe we should remove docker code since EAF has supports Windows/Mac/Linux ?
I think we should still have it, some people who doesn't want to install many dependencies may opt-in to use docker.
manateelazycat
commented
3 years ago I have remove docker file since I dont use it。
please dont run EAF with docker
we confirm EAF can work with windows
please try install-eaf.py to install EAF
Describe the bug As titled, M-x eaf-open only works with PDF, not images (PNG, JPG). The image does not open in the buffer, and the buffer simply appeared to be blank (with my blinking cursor at the top left corner).
M-x eaf-open-browser or eaf-open-vue-demo suffer from the same problem. Basically, EAF only works with PDF at this moment for me. Let me know if I should open different issues for different eaf-open functions (one for browser, one for vue demo etc.)
To Reproduce M-x eaf-open and enter a PNG/JPG file name.
Expected behavior The image should open in the buffer as usual.
Versions (please complete the following info):
Screenshots
PNG/JPG doesn't work.
PDF works as expected.
Additional context In the
*eaf*buffer, I noticed these couple of lines: