Your message dated Tue, 21 May 2013 14:46:16 +0200 with message-id <20130521124616.GC12846@radis.cristau.org> and subject line Re: Bug#708980: xserver-xephyr does not open a window has caused the Debian Bug report #708980, regarding xserver-xephyr does not open a window to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 708980: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708980 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: xserver-xephyr does not open a window
- From: Jan Christoph Uhde <linux@obiwahn.org>
- Date: Mon, 20 May 2013 00:55:22 +0200
- Message-id: <20130519225522.11253.26936.reportbug@edward>
Package: xserver-xephyr Version: 2:1.12.4-6 Severity: important Dear Maintainer, Xephyr stopped working for me some days ago. At first I thought it is some problem of the enlightenment 17 build I use. Today I have tried to run bbox, gnome-session and other WMs but none of them worked. I use the following script to start my sessions: » cat desktop-xephyr #!/bin/bash if [[ -z "$@" ]]; then echo "you need to supply something to be started in Xephyr" exit 1 fi xdisplay() { local disp=0; while [ -e "/tmp/.X${disp}-lock" ]; do disp=$(( disp + 1 )); done; echo $disp } #select display display=$(xdisplay) #start xserver Xephyr -ac -screen 1600x900 -br 2> /dev/null :$display & #set display export DISPLAY=:$display #wait for Xephyr to become ready sleep 1 #start window manager bash -c "$@" #remove x lock rm -fr /tmp/.X${display}-lock And it creates the following output: » bash -x desktop-xephyr /usr/bin/blackbox + [[ -z /usr/bin/blackbox ]] ++ xdisplay ++ local disp=0 ++ '[' -e /tmp/.X0-lock ']' ++ disp=1 ++ '[' -e /tmp/.X1-lock ']' ++ echo 1 + display=1 + export DISPLAY=:1 + Xephyr -ac -screen 1600x900 -br :1 + DISPLAY=:1 + sleep 1 + bash -c /usr/bin/blackbox bt::Display: failed to open display '' + rm -fr /tmp/.X1-lock I think running "+ Xephyr ..." line used to open a window. But this is not happening anymore. Please give me some hints how to provide more useful information. Regards, Jan C. Uhde -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xephyr depends on: ii libaudit0 1:1.7.18-1.1 ii libc6 2.17-3 ii libdrm2 2.4.40-1~deb7u2 ii libgcrypt11 1.5.0-5 ii libgl1-mesa-glx [libgl1] 8.0.5-5 ii libpixman-1-0 0.26.0-4 ii libselinux1 2.1.13-1 ii libx11-6 2:1.5.0-1 ii libxau6 1:1.0.7-1 ii libxdmcp6 1:1.1.1-1 ii libxext6 2:1.3.1-2 ii libxfont1 1:1.4.5-2 ii libxv1 2:1.0.7-1 ii xserver-common 2:1.12.4-6 Versions of packages xserver-xephyr recommends: ii libgl1-mesa-dri 8.0.5-5 xserver-xephyr suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: Jan Christoph Uhde <linux@obiwahn.org>, 708980-done@bugs.debian.org
- Subject: Re: Bug#708980: xserver-xephyr does not open a window
- From: Julien Cristau <jcristau@debian.org>
- Date: Tue, 21 May 2013 14:46:16 +0200
- Message-id: <20130521124616.GC12846@radis.cristau.org>
- In-reply-to: <20130519225522.11253.26936.reportbug@edward>
- References: <20130519225522.11253.26936.reportbug@edward>
On Mon, May 20, 2013 at 00:55:22 +0200, Jan Christoph Uhde wrote: > Package: xserver-xephyr > Version: 2:1.12.4-6 > Severity: important > > Dear Maintainer, > > Xephyr stopped working for me some days ago. At first I thought it is some > problem of the enlightenment 17 build I use. Today I have tried to run bbox, > gnome-session and other WMs but none of them worked. > > I use the following script to start my sessions: > » cat desktop-xephyr > #!/bin/bash > if [[ -z "$@" ]]; then > echo "you need to supply something to be started in Xephyr" > exit 1 > fi > > xdisplay() > { > local disp=0; > while [ -e "/tmp/.X${disp}-lock" ]; do > disp=$(( disp + 1 )); > done; > echo $disp > } > > #select display > display=$(xdisplay) > > #start xserver > Xephyr -ac -screen 1600x900 -br 2> /dev/null :$display & > > #set display > export DISPLAY=:$display > > #wait for Xephyr to become ready > sleep 1 > > #start window manager > bash -c "$@" > > #remove x lock > rm -fr /tmp/.X${display}-lock > > And it creates the following output: > > » bash -x desktop-xephyr /usr/bin/blackbox > + [[ -z /usr/bin/blackbox ]] > ++ xdisplay > ++ local disp=0 > ++ '[' -e /tmp/.X0-lock ']' > ++ disp=1 > ++ '[' -e /tmp/.X1-lock ']' > ++ echo 1 > + display=1 > + export DISPLAY=:1 Setting DISPLAY to the Xephyr display before starting Xephyr seems broken. That also doesn't correspond to the script above. > + Xephyr -ac -screen 1600x900 -br :1 > + DISPLAY=:1 > + sleep 1 > + bash -c /usr/bin/blackbox > bt::Display: failed to open display '' > + rm -fr /tmp/.X1-lock > > > I think running "+ Xephyr ..." line used to open a window. But this is not > happening anymore. > > Please give me some hints how to provide more useful information. > What happens if you just run Xephyr outside of your script, and without sending its output to /dev/null? Seems like your blackbox command doesn't get $DISPLAY properly. Anyway, there's no evidence of a bug here, so I'll close this. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---