Opened 11 years ago

Closed 11 years ago

Last modified 7 years ago

#1432 closed defect (fixed)

sugar-emulator starts sugar out of Xephyr

Reported by: alsroot Owned by: alsroot
Priority: Immediate Milestone:
Component: Sugar Version: Unspecified
Severity: Blocker Keywords: r+
Cc: Distribution/OS: Ubuntu
Bug Status: Unconfirmed

Description

Looks like metacity starts in current X session not in Xephyr.

|TestCase|

  • in Ubuntu 9.04 and 0.86 ppa, start sugar-emulator from gnome menu
  • it starts one window for Xephyr and sugar in current X session

Attachments (1)

sugar-1432.patch (3.3 KB) - added by alsroot 11 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 11 years ago by alsroot

sugar-emulator start from xterm, works well.

Changed 11 years ago by alsroot

comment:2 Changed 11 years ago by alsroot

  • Keywords r? added

comment:3 follow-up: Changed 11 years ago by sascha_silbe

That's quite strange. DISPLAY is set in _run_xephyr() unconditionally and should be used by all X programs. I've never seen this problem and would be quite surprised by it. Maybe Ubuntu has broken Xlib?

comment:4 in reply to: ↑ 3 Changed 11 years ago by alsroot

Replying to sascha_silbe:

That's quite strange. DISPLAY is set in _run_xephyr() unconditionally and should be used by all X programs. I've never seen this problem and would be quite surprised by it. Maybe Ubuntu has broken Xlib?

At least /usr/bin/sugar has DISPLAY=:0 at startup(but other environment vars from sugar-emulator are ok) after starting sugar-emulator from gnome menu.

Attached patch doesn't seem to be a hack, we just all time be sure that we use right DISPLAY.

comment:5 Changed 11 years ago by tomeu

  • Keywords r+ added; r? removed
  • Owner changed from tomeu to alsroot
  • Status changed from new to assigned

comment:6 Changed 11 years ago by alsroot

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:7 Changed 7 years ago by dnarvaez

  • Milestone 0.86 deleted

Milestone 0.86 deleted

Note: See TracTickets for help on using tickets.