github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #1568] Unable to start Xfce with latest firejail (Arch Linux) #1042

New issue

Closed

opened 2026-05-05 07:21:01 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 07:21:01 -06:00

Owner

Originally created by @cjsthompson on GitHub (Sep 20, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1568

Hi,

I had to reboot my (Arch Linux) machine today (1 month+ uptime). I was unable to start xfce (from lightdm) until I did a 'firejail --clean'. It used to work fine with 0.9.48 I'm pretty sure. xfce4-session seems to be stuck when firejail is in use. I did give it a try without any /etc/firejail/*.local customizations to be sure it has nothing to do with this. I also tried with the latest git.

I don't know if this is related, but I noticed there are some unkillable firejailed ssh-agent processes that are lingering each time I try to start xfce with firejail active.

Any help to fix this would be greatly appreciated.

Originally created by @cjsthompson on GitHub (Sep 20, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1568 Hi, I had to reboot my (Arch Linux) machine today (1 month+ uptime). I was unable to start xfce (from lightdm) until I did a 'firejail --clean'. It used to work fine with 0.9.48 I'm pretty sure. xfce4-session seems to be stuck when firejail is in use. I did give it a try without any /etc/firejail/*.local customizations to be sure it has nothing to do with this. I also tried with the latest git. I don't know if this is related, but I noticed there are some unkillable firejailed ssh-agent processes that are lingering each time I try to start xfce with firejail active. Any help to fix this would be greatly appreciated.

gitea-mirror

2026-05-05 07:21:01 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 07:21:05 -06:00

Author

Owner

@SkewedZeppelin commented on GitHub (Sep 20, 2017):

So if you

sudo firecfg
sudo rm /usr/local/bin/ssh-agent

xfce starts fine, yes? If so could you comment shell none in /etc/firejail/ssh-agent.profile and rerun sudo firecfg and logout/login to xfce again to confirm if that fixes it or not. If that works, then this is already fixed in master.

If that doesn't fix it however, could you provide a list of the output from firecfg and also check the logs of xfce for any errors.

@SkewedZeppelin commented on GitHub (Sep 20, 2017): So if you ``` sudo firecfg sudo rm /usr/local/bin/ssh-agent ``` xfce starts fine, yes? If so could you comment `shell none` in /etc/firejail/ssh-agent.profile and rerun `sudo firecfg` and logout/login to xfce again to confirm if that fixes it or not. If that works, then this is already fixed in master. If that doesn't fix it however, could you provide a list of the output from firecfg and also check the logs of xfce for any errors.

gitea-mirror commented

2026-05-05 07:21:07 -06:00

Author

Owner

@cjsthompson commented on GitHub (Sep 20, 2017):

Only commenting out "shell none" in ssh-agent.profile does not work. But removing the ssh-agent symlink does indeed fix the problem.

EDIT: I don't know if that could have something to do with it but my user account's default shell is fish not bash.

@cjsthompson commented on GitHub (Sep 20, 2017): Only commenting out "shell none" in ssh-agent.profile does not work. But removing the ssh-agent symlink does indeed fix the problem. EDIT: I don't know if that could have something to do with it but my user account's default shell is fish not bash.

gitea-mirror commented

2026-05-05 07:21:08 -06:00

Author

Owner

@netblue30 commented on GitHub (Sep 21, 2017):

I have removed it from firecfg until we figure out what is going on. Delete the symbolic link in /usr/local/bin for now.

@netblue30 commented on GitHub (Sep 21, 2017): I have removed it from firecfg until we figure out what is going on. Delete the symbolic link in /usr/local/bin for now.

gitea-mirror commented

2026-05-05 07:21:09 -06:00

Author

Owner

@cjsthompson commented on GitHub (Sep 21, 2017):

Ok, thanks.

@cjsthompson commented on GitHub (Sep 21, 2017): Ok, thanks.

gitea-mirror commented

2026-05-05 07:21:10 -06:00

Author

Owner

@joelazar commented on GitHub (Dec 17, 2017):

This bug is still around. Manjaro 17.0.6 xfce, firejail 0.9.50.

@joelazar commented on GitHub (Dec 17, 2017): This bug is still around. Manjaro 17.0.6 xfce, firejail 0.9.50.

gitea-mirror commented

2026-05-05 07:21:12 -06:00

Author

Owner

@joelazar commented on GitHub (Feb 1, 2018):

Ok, it looks like it is fixed now :) 0.9.52

@joelazar commented on GitHub (Feb 1, 2018): Ok, it looks like it is fixed now :) 0.9.52

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1042

No description provided.

Rows
Columns