Bug 681542 - Xephyr display is blank when doing sandbox -X firefox
Summary: Xephyr display is blank when doing sandbox -X firefox
Keywords:
Status: CLOSED DUPLICATE of bug 707021
Alias: None
Product: Fedora
Classification: Fedora
Component: policycoreutils
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-02 14:26 UTC by Robin Green
Modified: 2011-11-08 16:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-08 16:14:14 UTC
Type: ---


Attachments (Terms of Use)

Description Robin Green 2011-03-02 14:26:50 UTC
Description of problem:
I tried to create a web sandbox for Firefox. Firefox is running inside the sandbox, but the Xephyr display is either solid black or solid grey, all the time.

Version-Release number of selected component (if applicable):
policycoreutils-sandbox-2.0.85-12.fc15.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install policycoreutils-sandbox
2. Reboot
3. sandbox -X -H sandboxes/music/ -t sandbox_web_t firefox
  
Actual results:
The Xephyr display is either solid black or solid grey, all the time.

Expected results:
Firefox should appear

Additional info:
Firefox works if I create a blank home directory, set HOME to it, start a Xephyr server on :1 and set DISPLAY=:1 and run Firefox.

I experience some very minor graphics corruption issues with this graphics chipset.

Comment 1 Daniel Walsh 2011-03-02 19:21:38 UTC
Can you try using -W metacity?

Comment 2 Robin Green 2011-03-02 22:12:16 UTC
It works with -W metacity.

If I then run it again without -W metacity, it still works (although there are no window decorations at all - I don't know whether that's expected or not).

However, if I then try it again, supplying a different, empty directory as the -H argument, this bug occurs again.

I previously tried starting firefox in Xephyr and then running matchbox - that worked. So it may be an issue with the timing of when matchbox is started.

This bug does not occur on our Fedora 14 machine - it only occurs on Fedora 15.

Comment 3 Carl G. 2011-11-08 16:14:14 UTC

*** This bug has been marked as a duplicate of bug 707021 ***


Note You need to log in before you can comment on or make changes to this bug.