[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#54640: marked as done (xdm: should parse /etc/inittab to see what VT to start local servers on)

Your message dated Sun, 6 Mar 2011 00:24:09 +0100
with message-id <20110305232409.GB21542@debian.org>
and subject line Re: Bug#54640: wishlist: defaulting to a given tty can conflict with user changed inittab settings
has caused the Debian Bug report #54640,
regarding xdm: should parse /etc/inittab to see what VT to start local servers on
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.)


-- 
54640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=54640
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xdm
Version: 3.3.5-2
Severity: wishlist

I was running xdm for a long time with several more vc's (added in
/etc/inittab on ttys through tty10), and suddenly around the time of the
package split my machine would lock on boot.  We eventually traced it to
the conflicting tty which had suddenly become specified as tty7 instead
of the default "next available" it had previously used.

I request that there be some interaction - either with xdm reading the
/etc/inittab file, or asking the person installing it what tty it should
use.  It's not a perfect solution, because the configuration is not all
in one place.  If i were to forget about the xdm setting, and go add a
virtual console on tty12, i would have the same problem i mentioned
earlier.

The freeze part of the problem can be fixed by telnetting in and issuing
the command /etc/init.d/xdm stop.  The problem itself takes
configuration file changing.

Also, the included changed files may not all have changed - i did for a
while have one of the "xdm themes" running, and after i realized it was
causing me to be unable to return to a text mode after exiting xdm (and
the reset and whatever scripts run), i replaced the relevant files with
my pre-xdm-theme copy.  The only obviously relevant change is in the
Xservers file.

-m

-- System Information
Debian Release: potato
Architecture: i386
Kernel: Linux zen 2.2.13 #1 SMP Mon Nov 29 14:00:11 CST 1999 i686

Versions of packages xdm depends on:
ii  cpp                           1:2.95.2-4 The GNU C preprocessor.           
ii  libc6                         2.1.2-11   GNU C Library: Shared libraries an
ii  xlib6g                        3.3.5-2    shared libraries required by X cli

-- Configuration Files:
/etc/X11/xdm/Xaccess changed:
*					#any host can get a login window
*		CHOOSER BROADCAST	#any indirect host can get a chooser

/etc/X11/xdm/Xservers changed:
:0 local /usr/bin/X11/X vt12 -dpi 120

/etc/X11/xdm/Xsetup_0 [Errno 13] Permission denied: '/etc/X11/xdm/Xsetup_0'
/etc/X11/xdm/Xstartup changed:
if grep -qs ^ignore-nologin /etc/X11/xdm/xdm.options; then
  if [ -f /etc/nologin ]; then
    if [ -x /usr/bin/X11/xmessage ]; then
      xmessage -file /etc/nologin -geometry 640x480
    fi
  fi
elif [ -f /etc/nologin ]; then
  if [ -x /usr/bin/X11/xmessage ]; then
    xmessage -file /etc/nologin -geometry 640x480
  fi
  exit 1
fi 
if grep -qs ^use-sessreg /etc/X11/xdm/xdm.options; then
  exec sessreg -a -l $DISPLAY -u /var/run/utmp -x /etc/X11/xdm/Xservers $USER
  # NOTREACHED
fi
exit 0

/etc/X11/xdm/xdm-config changed:
! /etc/X11/xdm/xdm-config
!
! resources specific to xdm itself
DisplayManager.authDir:		/var/state/xdm
DisplayManager.errorLogFile:	/var/log/xdm.log
DisplayManager.pidFile:		/var/run/xdm.pid
DisplayManager.keyFile:		/etc/X11/xdm/xdm-keys
DisplayManager.servers:		/etc/X11/xdm/Xservers
DisplayManager.accessFile:	/etc/X11/xdm/Xaccess
DisplayManager._0.authorize:	true
DisplayManager._0.resources:	/etc/X11/xdm/Xresources_0
DisplayManager._0.setup:	/etc/X11/xdm/Xsetup_0
DisplayManager._0.startup:	/etc/X11/xdm/Xstartup_0
DisplayManager._0.reset:	/etc/X11/xdm/Xreset_0
DisplayManager*resources:	/etc/X11/xdm/Xresources
DisplayManager*setup:		/etc/X11/xdm/Xsetup
DisplayManager*startup:		/etc/X11/xdm/Xstartup
DisplayManager*reset:		/etc/X11/xdm/Xreset
DisplayManager*session:		/etc/X11/Xsession
DisplayManager*userPath:	/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
DisplayManager*systemPath:	/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11

--- End Message ---
--- Begin Message --- 
Cyril Brulebois <kibi@debian.org> (06/03/2011):
> (better late than never?)

Too late:
| urman@students.uiuc.edu
|   Unrouteable address

Closing this bug report accordingly.

KiBi.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: