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

Firefox doesn't open after installing and enabling apparmor. d, Xfce. "Failed to execute default web browser. input/output error" #330

Open
Renkoto opened this issue May 13, 2024 · 6 comments

Comments

@Renkoto
Copy link

Renkoto commented May 13, 2024

When i open Firefox on a terminal, this is the output.

[🧱] × firefox
Authorization required, but no authorization protocol specified

Error: cannot open display: :0

The distro i'm using is a Arch Linux derivative, Garuda specifically, i tried both the AUR package (which is outdated) and the package compiled in the CachyOS repos and both have the same issue, the first one I tried and rebooted the system booted fine, the problem seems to lie in that Firefox or Xfce don't have enough permissions to perform that action.

audit.log

This is the full log file, i think. My system is in the Spanish language, just in case if different language settings can interfere with that for whatever reason.

@Renkoto Renkoto changed the title Firefox doesn't open after enabling apparmor. d in Xfce. "Failed to execute default web browser. input/output error" Firefox doesn't open after installing and enabling apparmor. d, Xfce. "Failed to execute default web browser. input/output error" May 13, 2024
@roddhjav
Copy link
Owner

roddhjav commented May 13, 2024

Thanks for this log file, I am going to integrate them soon. However your issue with firefox does not seems to be related with apparmor (this is more a xorg/wayland issue).

Also, looking at the logs. Did you try to edit the profile in /etc/apparmor.d using a GUI app as root?

This is the full log file, i think.

You can try aa-log -R -s to get all logs since you booted the system, this could help getting more logs.

i tried both the AUR package (which is outdated) and the package compiled in the CachyOS repos

What package are you talking about? apparmor.d-git ?

@Renkoto
Copy link
Author

Renkoto commented May 13, 2024

Also, looking at the logs. Did you try to edit the profile in /etc/apparmor.d using a GUI app as root?

No, I keep everything as is.

You can try aa-log -R -s to get all logs since you booted the system, this could help getting more logs.

I will do it later, an important note is that doesn't happen with Firefox Dev Edition, so maybe it has something to do with the Firefox or Xorg related profiles profile, i'm using Xorg because of NVIDIA, and Xfce also doesn't support Wayland yet.

What package are you talking about? apparmor.d-git ?

Yep, but in both the problem persists, the rest of the system works as usual, i installed the AUR package in complain mode, I don’t know in which mode the pre-compiled apparmor.d-git in the Cachy repos was built.

@roddhjav
Copy link
Owner

I was able to reproduce the issue. I will investigate a bit and report here later.

Yep, but in both the problem persists,

I did not know they added the pkg to they own repo. Anyway it seems to be the very same than on the AUR, so you should not have issue with any of them.

@Renkoto
Copy link
Author

Renkoto commented Jun 9, 2024

You can try aa-log -R -s to get all logs since you booted the system, this could help getting more logs.

Sorry for responding so late, here are the 5 rotating log files, the issue is still happening.

A-Logs.zip

Authorization required, but no authorization protocol specified

Error: cannot open display: :0.0

btw, I don't remember that extra .0 there the last time I checked.

@Renkoto
Copy link
Author

Renkoto commented Jun 9, 2024

I tried opening Brave and works, .which would also mean other confined Chromium-based browsers, Firefox is the only one that gives an error at startup.

Tor Browser also works, I think Tor Browser is also confined, I would have to install and test the rest of the confined browsers like Chrome.
...

I have tested Chrome and also works with apparmor.d.

@Renkoto
Copy link
Author

Renkoto commented Jun 17, 2024

I was able to reproduce the issue. I will investigate a bit and report here later.

Yep, but in both the problem persists,

I did not know they added the pkg to they own repo. Anyway it seems to be the very same than on the AUR, so you should not have issue with any of them.

It seems that the issue is solved temporarily by deleting the .mozilla folder in home, for some reason the access to that folder is locked from the GUI when you install appamor..d, at least on Xfce, It's something that shouldn't happen, but it appears again a short time after the folder is created.

So I think it's a permission issue between Xfce and Firefox.

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

2 participants