Bug#635154: olvwm corrupts DISPLAY when running menu commands if DISPLAY lacks screen number
Package: olvwm
Version: 4.4.3.2p1.4-25
Severity: important
If DISPLAY lacks a screen number (for example, :0 rather than :0.0) then
olvwm corrupts it when running a command from the popup menu, preventing
the command from connecting to the X server.
For example, with DISPLAY=:0 olvwm will invoke menu commands with
DISPLAY=.0 which is invalid. You can reproduce this by adding a menu
command in ~/.openwin-menu that invokes a script that writes $DISPLAY to
some file.
A workaround is to rewrite DISPLAY in ~/.xsession to append .0 if
DISPLAY lacks a screen number.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'stable'), (600, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages olvwm depends on:
ii libc6 2.13-10 Embedded GNU C Library: Shared lib
ii libx11-6 2:1.4.3-2 X11 client-side library
ii libxext6 2:1.3.0-3 X11 miscellaneous extension librar
ii libxpm4 1:3.5.9-1 X11 pixmap library
olvwm recommends no packages.
Versions of packages olvwm suggests:
ii menu 2.1.45 generates programs menu for all me
pn olwm <none> (no description available)
pn xview-clients <none> (no description available)
-- no debconf information
Reply to: