Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 71288 - startxfce cant open display after upgrading PAM
Summary: startxfce cant open display after upgrading PAM
Status: RESOLVED DUPLICATE of bug 70585
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: PAM Gentoo Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-15 07:56 UTC by John Barton
Modified: 2005-07-17 13:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Barton 2004-11-15 07:56:57 UTC
After emerging world, which included an upgrade from pam 0.77 to 0.77-r1, startxfce4 would no longer work due to some problem with the DISPLAY variable. During the emerge and etc-update, changes were made to /etc/security/pam_env.conf which seem to have added an entry for setting DISPLAY, causing startxfce4 to fail but startx still works

Reproducible: Always
Steps to Reproduce:
1.emegre pam-0.77-r1
2.accept changes to /etc/security/pam_env.conf
3.startxfce4

Actual Results:  
X failed with error

Expected Results:  
started xfce4

After commenting out the following line in /etc/security/pam_env.conf,
startxfce4 resumed normal operation:

# Set the DISPLAY variable if it seems reasonable 
# DISPLAY               DEFAULT=${REMOTEHOST}:0.0 OVERRIDE=${DISPLAY}

Portage 2.0.51-r3 (default-linux/x86/2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r1,
2.6.9-gentoo-r1 i686)
=================================================================
System uname: 2.6.9-gentoo-r1 i686 Mobile AMD Athlon(tm) 64 Processor 3200+
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.14.90.0.8-r1
Headers:  sys-kernel/linux-headers-2.4.21-r1
Libtools: sys-devel/libtool-1.5.2-r5
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -mcpu=athlon-xp -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown
/usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -mcpu=athlon-xp -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://gentoo.osuosl.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="3dnow X acl alsa apm arts avi berkdb bitmap-fonts cdr crypt cups dvdr
encode ethereal f77 foomaticdb fortran gdbm gif gpm gtk gtk2 imlib innodb java
jpeg libg++ libwww mad mikmod motif mpeg mysql ncurses offensive oggvorbis
opengl oss pam pdflib perl png python qt quicktime readline samba sdl slang snmp
spell ssl svga tcpd tiff truetype x86 xml xml2 xmms xv zlib"
Comment 1 John Barton 2004-11-15 08:01:11 UTC
Here is the error generated by running startsfce4 after PAM upgrade:

/usr/bin/startxfce4: X server already running on display :0.0
xsetroot:  unable to open display ':0.0'
...
...
Comment 2 Brad Cowan (RETIRED) gentoo-dev 2004-11-25 20:11:33 UTC

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