Your message dated Sun, 28 Feb 2010 17:48:36 +0100
with message-id <[email protected]>
and subject line Re: Bug#422065: [Debconf-devel] Bug#422065: debconf:
completion file contains
has caused the Debian Bug report #422065,
regarding debconf: completion file contains invalid identifier
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 [email protected]
immediately.)
--
422065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422065
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debconf
Version: 1.5.13
Severity: normal
/etc/bash_completion.d/debconf contains the invalid identifiers
_debconf-show and debconf-showi. The hyphen-minus is invalid, just
replace it with an underscore.
This prevented me from logging in, therefore the elevated severity.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.20-1-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages debconf depends on:
ii debconf-i18n 1.5.13 full internationalization support
ii perl-base 5.8.8-7 The Pathologically Eclectic Rubbis
Versions of packages debconf recommends:
ii apt-utils 0.6.46.4-0.1 APT utility programs
-- debconf information:
debconf-apt-progress/title:
debconf-apt-progress/info:
* debconf/priority: medium
debconf-apt-progress/preparing:
debconf-apt-progress/media-change:
* debconf/frontend: Dialog
--- End Message ---
--- Begin Message ---
On Wed, Nov 21, 2007 at 14:36:33 +0100, Josselin Mouette wrote:
> Hi,
>
> Le lundi 12 novembre 2007 à 12:06 +0000, Unric David a écrit :
> > I can confirm this bug and it's not related to gdm because the same
> > behaviour was observed at xdm.
> >
> > User startup scripts (.profile or .bash_profile) are not sourced at X
> > login (Xsession) by default so bash-completion is not too. If you load
> > them in your ~/.xsession f.E. the described problem shows but only for
> > root account in my case.
> >
> > I guess the bug lies somewhere in (paranoid) environment settings of
> > display managers or Xsession startup scripts for root because bash
> > (login shell for root) has no problems with hyphens in function names.
>
> Enabling bash completion in ~/.xsession looks almost like deliberate
> breakage to me, and I don't think we need so support such a case.
>
Sounds like local configuration error, rather than a gdm bug, so closing
this. Thanks for your report.
Cheers,
Julien
signature.asc
Description: Digital signature
--- End Message ---
