[GH-ISSUE #746] strange xpra error. #507

Closed
opened 2026-05-05 06:00:15 -06:00 by gitea-mirror · 6 comments
Owner

Originally created by @xahare on GitHub (Aug 27, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/746

this stopped working earlier today in my main work vm. ~/.xpra does exist. in Vagrant, the same setup still works, so i dont know how to reproduce this. im using ubuntu 16.04. in vagrant, boxcutter/ubuntu1604-desktop

the strange error is "socket path error: [Errno 2] No such file or directory: 'socket-dirs = ~/.xpra'"

this happens with the ppa release or compiling from todays source (git pull, make, sudo make install)

--x11=xephyr still works.

$ cat bin/workbrowser-google-chrome.bash 
#!/bin/bash
firejail --name=workbrowser-google-chrome --x11 --net=fj0 --dns=192.168.113.2 --private=~/firejail/workbrowser google-chrome

$ workbrowser-google-chrome.bash 
2016-08-26 22:13:18,062 Warning: xpra start from an existing 'ubuntu' desktop session
2016-08-26 22:13:18,062  pulseaudio forwarding may not work
2016-08-26 22:13:18,063  try using a clean environment, a dedicated user,
2016-08-26 22:13:18,063  or turn off pulseaudio
xpra initialization error:
 socket path error: [Errno 2] No such file or directory: 'socket-dirs = ~/.xpra'
Xpra server pid 17640, xpra client pid 17656, jail 17657

*** Attaching to xpra display 345 ***

Reading profile /usr/local/etc/firejail/google-chrome.profile
Reading profile /usr/local/etc/firejail/disable-common.inc
Reading profile /usr/local/etc/firejail/disable-programs.inc
Reading profile /usr/local/etc/firejail/whitelist-common.inc
2016-08-26 22:13:19,381 Xpra gtk2 client version 0.17.5-r13455
2016-08-26 22:13:19,382  running on Linux Ubuntu 16.04 xenial
2016-08-26 22:13:19,675 GStreamer version 1.8 for Python 2.7

got signal SIGTERM, exiting

Originally created by @xahare on GitHub (Aug 27, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/746 this stopped working earlier today in my main work vm. ~/.xpra does exist. in Vagrant, the same setup still works, so i dont know how to reproduce this. im using ubuntu 16.04. in vagrant, boxcutter/ubuntu1604-desktop the strange error is "socket path error: [Errno 2] No such file or directory: 'socket-dirs = ~/.xpra'" this happens with the ppa release or compiling from todays source (git pull, make, sudo make install) --x11=xephyr still works. ``` $ cat bin/workbrowser-google-chrome.bash #!/bin/bash firejail --name=workbrowser-google-chrome --x11 --net=fj0 --dns=192.168.113.2 --private=~/firejail/workbrowser google-chrome $ workbrowser-google-chrome.bash 2016-08-26 22:13:18,062 Warning: xpra start from an existing 'ubuntu' desktop session 2016-08-26 22:13:18,062 pulseaudio forwarding may not work 2016-08-26 22:13:18,063 try using a clean environment, a dedicated user, 2016-08-26 22:13:18,063 or turn off pulseaudio xpra initialization error: socket path error: [Errno 2] No such file or directory: 'socket-dirs = ~/.xpra' Xpra server pid 17640, xpra client pid 17656, jail 17657 *** Attaching to xpra display 345 *** Reading profile /usr/local/etc/firejail/google-chrome.profile Reading profile /usr/local/etc/firejail/disable-common.inc Reading profile /usr/local/etc/firejail/disable-programs.inc Reading profile /usr/local/etc/firejail/whitelist-common.inc 2016-08-26 22:13:19,381 Xpra gtk2 client version 0.17.5-r13455 2016-08-26 22:13:19,382 running on Linux Ubuntu 16.04 xenial 2016-08-26 22:13:19,675 GStreamer version 1.8 for Python 2.7 got signal SIGTERM, exiting ```
gitea-mirror 2026-05-05 06:00:15 -06:00
Author
Owner

@chiraag-nataraj commented on GitHub (Aug 28, 2016):

Since you're using --private=~/firejail/workbrowser, I feel like .xpra should reside within that directory. That is, you should create the directory ~/firejail/workbrowser/.xpra. Does that fix the issue?

[EDIT]
Strange...I just tried that combination and it worked without having to create the directory. I would still try it though, since it may fix the issue? Did you upgrade firejail recently on one box but not the other?

<!-- gh-comment-id:242948803 --> @chiraag-nataraj commented on GitHub (Aug 28, 2016): Since you're using `--private=~/firejail/workbrowser`, I feel like `.xpra` should reside within that directory. That is, you should create the directory `~/firejail/workbrowser/.xpra`. Does that fix the issue? [EDIT] Strange...I just tried that combination and it worked without having to create the directory. I would still try it though, since it may fix the issue? Did you upgrade firejail recently on one box but not the other?
Author
Owner

@xahare commented on GitHub (Aug 28, 2016):

same result. i think its a regression with another library or something. having ~/.xpra in my real directory has worked fine for weeks. it also works fine in vagrant with an ubuntu 16.04 desktop.

<!-- gh-comment-id:242949096 --> @xahare commented on GitHub (Aug 28, 2016): same result. i think its a regression with another library or something. having ~/.xpra in my real directory has worked fine for weeks. it also works fine in vagrant with an ubuntu 16.04 desktop.
Author
Owner

@chiraag-nataraj commented on GitHub (Aug 28, 2016):

I wonder which library that would even be...firejail only depends on libc6...and you're running the same version of firejail on both machines?

<!-- gh-comment-id:242949295 --> @chiraag-nataraj commented on GitHub (Aug 28, 2016): I wonder which library that would even be...firejail only depends on libc6...and you're running the same version of firejail on both machines?
Author
Owner

@xahare commented on GitHub (Aug 28, 2016):

in vagrant, the ppa version. on the persistent vm, i tried both the ppa and compiled from github. doing an update in the vagrant box to see if it breaks it.

[update] updating the vagrant box didnt break it. so now, in theory, both vms are running the same stuff. the only difference is the vagrantbox is virtualbox, while the persistent one (thats broken) is vmware-fusion. i doubt this difference could cause the problem. permissions on ~/.xpra are the same.

ill try to get xpra working, but if it cant be done, then the only loss is some convenience, and maybe camera and microphone protection (another thread). i can live with xephyr until wayland takes over.

i also dont care what distro i use, cause all my apps live in firejail anyway. so open to changing. fedora is probably next because wayland. or maybe rebecca black. im not holding my breath for mir.

@netblue30 what distro works for you? have you played with wayland yet?

<!-- gh-comment-id:242949502 --> @xahare commented on GitHub (Aug 28, 2016): in vagrant, the ppa version. on the persistent vm, i tried both the ppa and compiled from github. doing an update in the vagrant box to see if it breaks it. [update] updating the vagrant box didnt break it. so now, in theory, both vms are running the same stuff. the only difference is the vagrantbox is virtualbox, while the persistent one (thats broken) is vmware-fusion. i doubt this difference could cause the problem. permissions on ~/.xpra are the same. ill try to get xpra working, but if it cant be done, then the only loss is some convenience, and maybe camera and microphone protection (another thread). i can live with xephyr until wayland takes over. i also dont care what distro i use, cause all my apps live in firejail anyway. so open to changing. fedora is probably next because wayland. or maybe rebecca black. im not holding my breath for mir. @netblue30 what distro works for you? have you played with wayland yet?
Author
Owner

@netblue30 commented on GitHub (Sep 6, 2016):

I've seen xpra working on Debian and Ubuntu, didn't play with wayland yet.

<!-- gh-comment-id:244932215 --> @netblue30 commented on GitHub (Sep 6, 2016): I've seen xpra working on Debian and Ubuntu, didn't play with wayland yet.
Author
Owner

@xahare commented on GitHub (Sep 11, 2016):

found it. user error. in my ~/.xpra/xpra.conf

socket-dirs = socket-dirs = ~/.xpra

fixed.

<!-- gh-comment-id:246156819 --> @xahare commented on GitHub (Sep 11, 2016): found it. user error. in my ~/.xpra/xpra.conf socket-dirs = socket-dirs = ~/.xpra fixed.
Sign in to join this conversation.
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#507
No description provided.