github-starred/firejail

Fork 0

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

[GH-ISSUE #633] failed to start xpra on Arch Linux #440

New issue

Closed

opened 2026-05-05 05:51:56 -06:00 by gitea-mirror · 9 comments

gitea-mirror commented

2026-05-05 05:51:56 -06:00

Owner

Originally created by @fkarl423 on GitHub (Jul 14, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/633

When running with the --x11 option the folliwing error appears on arch linux:

Entering daemon mode; any further errors will be reported to:
/home/user/.xpra/:294.log
Error: failed to start xpra

The log says:

/usr/lib/xorg-server/Xorg.wrap: Only console users are allowed to run the X server
could not connect to X server on display ':294' after 3 seconds

Originally created by @fkarl423 on GitHub (Jul 14, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/633 When running with the --x11 option the folliwing error appears on arch linux: Entering daemon mode; any further errors will be reported to: /home/user/.xpra/:294.log Error: failed to start xpra The log says: /usr/lib/xorg-server/Xorg.wrap: Only console users are allowed to run the X server could not connect to X server on display ':294' after 3 seconds

gitea-mirror

2026-05-05 05:51:56 -06:00

closed this issue
added the
enhancement
label

gitea-mirror commented

2026-05-05 05:52:04 -06:00

Author

Owner

@netblue30 commented on GitHub (Jul 14, 2016):

If you are on Arch, the version of xpra they have is broken.

@netblue30 commented on GitHub (Jul 14, 2016): If you are on Arch, the version of xpra they have is broken.

gitea-mirror commented

2026-05-05 05:52:07 -06:00

Author

Owner

@fkarl423 commented on GitHub (Jul 15, 2016):

OK Thanks for the info. I will try with a different version

@fkarl423 commented on GitHub (Jul 15, 2016): OK Thanks for the info. I will try with a different version

gitea-mirror commented

2026-05-05 05:52:09 -06:00

Author

Owner

@netblue30 commented on GitHub (Jul 16, 2016):

If you find a way to run it on Arch, please let me know. Thanks.

@netblue30 commented on GitHub (Jul 16, 2016): If you find a way to run it on Arch, please let me know. Thanks.

gitea-mirror commented

2026-05-05 05:52:11 -06:00

Author

Owner

@fkarl423 commented on GitHub (Jul 19, 2016):

I found the issue and how to solve it.

It seems recent versions of the x-server need the file /etc/X11/Xwrapper.config with the content allowed_users=anybody

This allows everyone to start the xserver.
I don't really know if there are any security implications, maybe someone can verify that this is save to use.

@fkarl423 commented on GitHub (Jul 19, 2016): I found the issue and how to solve it. It seems recent versions of the x-server need the file /etc/X11/Xwrapper.config with the content allowed_users=anybody This allows everyone to start the xserver. I don't really know if there are any security implications, maybe someone can verify that this is save to use.

gitea-mirror commented

2026-05-05 05:52:13 -06:00

Author

Owner

@netblue30 commented on GitHub (Jul 20, 2016):

Just to make sure I understand what you have there: Arch Linux with xpra-winswitch package from AUR installed, you modify /etc/X11/Xwrapper.config "allowed_users=anybody", and is working! Is this right?

For security implications I would say if you are not running a server or a multiuser system you should be fine.

@netblue30 commented on GitHub (Jul 20, 2016): Just to make sure I understand what you have there: Arch Linux with xpra-winswitch package from AUR installed, you modify /etc/X11/Xwrapper.config "allowed_users=anybody", and is working! Is this right? For security implications I would say if you are not running a server or a multiuser system you should be fine.

gitea-mirror commented

2026-05-05 05:52:15 -06:00

Author

Owner

@fkarl423 commented on GitHub (Jul 25, 2016):

Yes, that is correct.

@fkarl423 commented on GitHub (Jul 25, 2016): Yes, that is correct.

gitea-mirror commented

2026-05-05 05:52:18 -06:00

Author

Owner

@netblue30 commented on GitHub (Jul 25, 2016):

I'll update the documentation, thanks!

@netblue30 commented on GitHub (Jul 25, 2016): I'll update the documentation, thanks!

gitea-mirror commented

2026-05-05 05:52:21 -06:00

Author

Owner

@vn971 commented on GitHub (Jul 31, 2016):

Oh, that's interesting. xpra didn't work for me, too.
Actually, I don't even understand why xpra checks the config. Xephyr can launch itself without any questions.
Does it mean that Xephyr is emulating X as a normal user-space program while xpra communicates with parent X directly? (Confused.)

@vn971 commented on GitHub (Jul 31, 2016): Oh, that's interesting. `xpra` didn't work for me, too. Actually, I don't even understand why xpra checks the config. Xephyr can launch itself without any questions. Does it mean that Xephyr is emulating X as a normal user-space program while `xpra` communicates with parent X directly? (_Confused_.)

gitea-mirror commented

2026-05-05 05:52:24 -06:00

Author

Owner

@netblue30 commented on GitHub (Aug 1, 2016):

Documentation updated, thanks.

I don't even understand why xpra checks the config

Who knows what they are doing there. I guess you are correct, they emulate a user-space X11 server, while communicating with the parent server directly.

@netblue30 commented on GitHub (Aug 1, 2016): Documentation updated, thanks. > I don't even understand why xpra checks the config Who knows what they are doing there. I guess you are correct, they emulate a user-space X11 server, while communicating with the parent server directly.

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#440

No description provided.

Rows
Columns