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

Bug#368818: marked as done (x11-common: insufficient error checking in Xsession can prevent users from logging in)

Your message dated Fri, 04 Oct 2013 00:56:04 +0000
with message-id <524E1224.6040201@solveig.org>
and subject line Re: x11-common: insufficient error checking in Xsession can prevent users from logging in - closing
has caused the Debian Bug report #368818,
regarding x11-common: insufficient error checking in Xsession can prevent users from logging in
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.)


-- 
368818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368818
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: x11-common
Version: 6.9.0.dfsg.1-6
Severity: normal

If fold is given zero columns as an argument, it dies with the error
message below. If the $COLUMNS enivornment variable is for some reason
set to zero, then the command "fold -s -w ${COLUMNS:-80}" in
Xsessions's message functions will cause xinit to die with only the
following output in .xsession-errors:

Xsession: X session started for iseggev at Wed May 24 23:51:20 CDT 2006
fold: invalid number of columns: `0'

The result is that the user cannot log in. This can be fixed by
setting COLUMNS=80 by hand in Xsession.

Clearly the ultimate cause is some underlying bug which I have yet to
identify. I would appreciate help in tracking down that bug as well,
but given the ugly results for X and simple work around, (test
COLUMNS and set it to 80 if it equals zero), I'm filing this bug. 

This never happened to me in the past; it started happening today
after an upgrade. Kdm and curses seem like the most likely culprits of
the packages upgraded today. The really wierd thing is that it only
happens for some accounts and not others. I don't entirely understand
the X login process, which makes it difficult for me to figure out
exactly why this is happening. Any help would be appreciated.

Thanks,

Itai 



-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (110, 'unstable'), (10, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16cavy1
Locale: LANG=he_IL.UTF-8, LC_CTYPE=he_IL.UTF-8 (charmap=UTF-8)

Versions of packages x11-common depends on:
ii  debconf [debconf-2.0]         1.5.1      Debian configuration management sy
ii  debianutils                   2.16       Miscellaneous utilities specific t
ii  lsb-base                      3.1-5      Linux Standard Base 3.1 init scrip

x11-common recommends no packages.

-- debconf information:
  x11-common/experimental_packages:

--- End Message ---
--- Begin Message --- 
Hi! I'm closing this bug, since it was tagged "wontfix" for some
years, without answer. If you have new reasons to point out this
problem, please feel free to re-open it.

--- End Message ---
Reply to: