#310 closed defect (obsolete)
Xephyr can't run on :100 on jaunty
| Reported by: | morgs | Owned by: | marcopg |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | Sugar | Version: | Git as of bugdate |
| Severity: | Minor | Keywords: | |
| Cc: | sascha_silbe | Distribution/OS: | Ubuntu |
| Bug Status: | New |
Description
Logged against Ubuntu jaunty:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/325706
Xephyr can only run on :0 or :1 in the default config, due to a more restrictive D-Bus policy.
I'm not sure how to resolve this since it would seem we need <allow own="org.x.config.display100"/> ... <allow own="org.x.config.display110"/> added to /etc/dbus-1/system.d/xorg-server.conf to permit running Xephyr the way we do.
I'll give feedback here from the Ubuntu bug report - consider this ticket informational only for now.
Change History (6)
comment:1 Changed 15 years ago by tomeu
- Bug Status changed from Unconfimed to Needinfo
- Priority changed from Unspecified by Maintainer to Normal
comment:2 Changed 15 years ago by tomeu
- Milestone changed from Unspecified by Release Team to 0.84
Would be nice if we could understand what we are supposed to do here before 0.86.
comment:3 Changed 15 years ago by sascha_silbe
- Bug Status changed from Needinfo to New
Walter seems to have encountered this again (see #798). It has been marked as "Fix Committed" upstream about a month ago, but seems like they either didn't release the fix (just commit it) or it wasn't actually fixed.
We could add a workaround to sugar-emulator, but the actual fix has to be done upstream.
comment:4 Changed 15 years ago by sascha_silbe
- Cc sascha_silbe added
comment:5 Changed 11 years ago by godiard
- Resolution set to obsolete
- Status changed from new to closed
We are not using Xephyr anymore.
Do we know if this is something that should be done in upstream sugar or if it should be taken care by distros?