Skip to content
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

Connection Issues #25

Open
SamuelFountain opened this issue Jul 19, 2023 · 3 comments
Open

Connection Issues #25

SamuelFountain opened this issue Jul 19, 2023 · 3 comments

Comments

@SamuelFountain
Copy link

I am having issues getting the web ui to populate.

I have installed using the straight recipe from the readme with use-package. My default browser is Firefox. When I run org-hyperscheduler-open firefox gives me the following error

Screenshot from 2023-07-19 10-43-00

If you click okay you get a second error message

Screenshot from 2023-07-19 10-43-06

Clicking Okay there will bring you to an empty calendar.

Attempting the same process with chromium get

Screenshot from 2023-07-19 10-46-46

I have checked and the index.html file in question has the following permissions "-rw-rw-r--"

GNU Emacs 30.0.50
Mozilla Firefox 115.0
Chromium 114.0.5735.198 snap

@dmitrym0
Copy link
Owner

That's pretty strange.

  1. What OS are you on?
  2. Is your agenda functioning normally (M-x org-agenda works fine?)

@Superjomn
Copy link

Superjomn commented Jan 5, 2024

I had the same issue.
My org-agenda works fine.

The *org-hyperscheduler-server* buffer was left blank no matter how many times I triggered the org-hyperscheduler-open command.

Do you have any clue how to fix it?

@RyanGreenup
Copy link

RyanGreenup commented Jan 20, 2024

I had a similar experience using Firefox from a Flatpak. This can be fixed by giving Firefox permission to the home directory with Flatseal.

In my case, I was on Suse MicroOS so I couldn't just install it from the repositories, that would also work.

I personally run Emacs from a container (with distrobox + podman). In my case I installed another Firefox with a different profile into that container, that way Emacs was able to call Firefox to open it and they both shared the permissions for $HOME.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants