Bug 976995

It works for me. Does it work in permissive mode?

Damn, I was sure I have already tried that. Same problem in permissive mode, so the problem is elsewhere. I am feeling quite ashamed now.. you can certainly close this report.
What is your version of sandbox?
It is a fresh install with the same home partition, so it must be a problem with a configuration file somewhere. Does someone have any clue on where to look at? It happens on all accounts, even new ones.

It is the '-X' argument that is faulty. Without it, the application run (at least in permissive mode).

No the problem is with Xephry, I believe.

remove --resizable option in  /usr/share/sandbox/sandboxX.sh

And see if this fixes the problem.

I have removed the option. I am using the command "sandbox -X xterm" for testing, and it fails even in permissive mode.

Same result using the file /usr/share/sandbox/sandboxX.sh from fedora 17.

You're right Daniel, the problem is with Xephyr. I have a segfault using it alone:
Xephyr -ac -br -noreset -screen 800x600 :2

(EE) 
(EE) Backtrace:
(EE) 0: Xephyr (OsLookupColor+0x129) [0x4672b9]
(EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x7f71e0547f9f]
(EE) 2: Xephyr (XNFprintf+0x9aea) [0x4809fa]
(EE) 3: Xephyr (XNFprintf+0x8dc7) [0x47e967]
(EE) 4: Xephyr (XNFprintf+0x4538) [0x475e78]
(EE) 5: Xephyr (ddxGiveUp+0xf27) [0x48e737]
(EE) 6: Xephyr (AddScreen+0x71) [0x42fdc1]
(EE) 7: Xephyr (ddxGiveUp+0x1409) [0x48f089]
(EE) 8: Xephyr (_init+0x3c4b) [0x4221fb]
(EE) 9: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f71dfc94b75]
(EE) 10: Xephyr (_start+0x29) [0x41ecc1]
(EE) 11: ? (?+0x29) [0x29]
(EE) 
(EE) Segmentation fault at address 0x18

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting

So, could you move the report to Xephyr?

Created attachment 772539 [details]
Fix the segfault

The weird point is that I cannot reproduce the segfault on a virtual machine, but it does happen on the main system.
I can fix it with this patch.
For sandbox, Xephyr does not recognise the resizeable option, and I have to remove it: I really bo not understand this point since it works in the VM. Is there something to do to enable it?
I am using the version 1.14.2-3 (+this patch), from the repository updates-testing.

from bug #984178  , this may be fixed, could you please test :

Package xorg-x11-server-1.14.2-4.fc19:
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xorg-x11-server-1.14.2-4.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-12886/xorg-x11-server-1.14.2-4.fc19
then log in and leave karma (feedback).

Does not fix this bug. The Xephyr option -resizeable is still absent, and the patch is still required (segfault otherwise).

(In reply to Alphonse Steiner from comment #10)
> Does not fix this bug. The Xephyr option -resizeable is still absent, and
> the patch is still required (segfault otherwise).

In my point of view, we just should give negative karma when we have regressions, 
this release fixes many bugs and don't make any regression on yours, so you should change your vote, to get this update in stable soon. 
Your patch, will be analysed and hope that hit branch stable soon if really fix this bug (and others) .

Sorry, I am not really aware of this karma thing and was a little hasty I guess. It is true that I do not see any regressions and that it solves other bugs, so giving a bad karma is really harsh. I will change my vore.

xorg-x11-server-1.14.2-5.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/xorg-x11-server-1.14.2-5.fc19

Bug not fixed. The option is back in Xephyr, but the patch is still required (segfault otherwise).

*** Bug 984684 has been marked as a duplicate of this bug. ***

Package xorg-x11-server-1.14.2-5.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xorg-x11-server-1.14.2-5.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-12995/xorg-x11-server-1.14.2-5.fc19
then log in and leave karma (feedback).

Just to be sure, I rewrite it: this version does not fix the segfault. The path still work.

xorg-x11-server-Xephyr-1.14.2-5.fc19 fixes sandbox -X for me.  Perhaps this is PBKAC, but the command referenced above:

yum update --enablerepo=updates-testing xorg-x11-server-1.14.2-5.fc19

failed with package not found.

To install the new Xephyr I used:

yum update --enablerepo=updates-testing xorg-x11-server-Xephyr-1.14.2-5.fc19

The correct command should be :

yum update --enablerepo=updates-testing xorg-x11-server\*-1.14.2-5.fc19


This is a bug on message of Fedora Update System, for this specific package .

As I said before, the "sandbox -X" part is fixed with 1.14.2-5 (the option is back).

However, I still have a segfault error when I start Xephyr (_alone_ or by sandbox -X). The bad point is that this segfault is not reproducible everywhere. I have it on the main system, but not on virtual ones. 

For information, it did not happened in FC17, and this version of FC19 is from a fresh install.

Does it crash in permissive mode?

Yes it does. This problem is not related to selinux, but to Xephyr. The function 'XGetVisualInfo' returns a NULL pointer, leading to the segfault.

xorg-x11-server-1.14.2-5.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

(In reply to Alphonse Steiner from comment #22)
> Yes it does. This problem is not related to selinux, but to Xephyr. The
> function 'XGetVisualInfo' returns a NULL pointer, leading to the segfault.

Hi, Alphonse Steiner, are you the author of the patch "Fix the segfault" ? 
if yes , is patch posted to the xorg-devel mailing list, for master ?