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

Bug#300820: marked as done (No keyboard inputs after system boot in kdm)

Your message dated Fri, 12 May 2006 08:26:34 -0400
with message-id <200605120826.35488.chrsmrtn@debian.org>
and subject line No keyboard inputs after system boot in kdm
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kdm
Version: 4:3.3.2-1
Severity: grave
Justification: renders package unusable

When I start the system, everything looks fine. But when I try to login I can't type anything. Only the mouse works. Starting the login manager takes a long 
time and XFree86.0.log indicates that vt2 is used. If I restart kdmand then lookinto XFree86.0.log it now shows that vt7 is used (which is correctI can type andlogin again). I found a bug report in the xserver-section and an answer was thatit had something to do with kdm or kdelibs. So I post this error here.

System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.11
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages kdm depends on:
ii  debconf                  1.4.30.11       Debian configuration management sy
ii  kdebase-bin              4:3.3.2-1       KDE Base (binaries)
ii  kdelibs4                 4:3.3.2-4.0.2   KDE core libraries
ii  libart-2.0-2             2.3.17-1        Library of functions for 2D graphi
ii  libc6                    2.3.2.ds1-20    GNU C Library: Shared libraries an
ii  libfam0c102              2.7.0-6         client library to control the FAM 
ii  libgcc1                  1:3.4.3-6       GCC support library
ii  libice6                  4.3.0.dfsg.1-10 Inter-Client Exchange library
ii  libidn11                 0.5.13-1.0      GNU libidn library, implementation
ii  libpam-runtime           0.76-22         Runtime support for the PAM librar
ii  libpam0g                 0.76-22         Pluggable Authentication Modules l
ii  libpng12-0               1.2.8rel-1      PNG library - runtime
ii  libqt3c102-mt            3:3.3.3-8       Qt GUI Library (Threaded runtime v
ii  libsm6                   4.3.0.dfsg.1-10 X Window System Session Management
ii  libstdc++5               1:3.3.5-8       The GNU Standard C++ Library v3
ii  libx11-6                 4.3.0.dfsg.1-10 X Window System protocol client li
ii  libxext6                 4.3.0.dfsg.1-10 X Window System miscellaneous exte
ii  libxrender1              0.8.3-7         X Rendering Extension client libra
ii  libxtst6                 4.3.0.dfsg.1-10 X Window System event recording an
ii  xbase-clients            4.3.0.dfsg.1-10 miscellaneous X clients
ii  xlibs                    4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu
ii  zlib1g                   1:1.2.2-3       compression library - runtime

-- debconf information:
  kdm/stop_running_server_with_children: false
  shared/default-x-display-manager: kdm
  kdm/daemon_name: /usr/bin/kdm

--- End Message ---
--- Begin Message --- 
Version: 4:3.5.2-1

This bug has long since become irrelevant, since kdm's NEWS.Debian 
clearly explains the need to update kdmrc for 3.3.2 (and other times 
thereafter). Since 3.3.2 shipped with Sarge, this problem isn't really 
relevant anymore.

If you're still having problems, for God's sake just allow kdmrc to be 
updated and you'll probably find all sorts of issues simply vanish...

--- End Message ---
Reply to: