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

Bug#353940: marked as done (kdm: will no longer start (using Xvnc, "errno 97"))



Your message dated Fri, 9 Feb 2007 19:34:38 -0800
with message-id <000a01c74cc4$649006d0$06000100@page>
and subject line Bug#353940: About your bug: "kdm: will no longer start (using Xvnc" on the Debian BTS
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.5.1-1
Severity: important


I am no longer able to log into my debian linux box using Xvnc, the
following log messages result with any attempt:

kdm[2181]: XDMCP socket creation failed, errno 97
kdm[2181]: Internal error: config reader supplied incomplete data
kdm[2181]: Unable to read configuration for display :0; stopping it.
kdm[2181]: Internal error: config reader supplied incomplete data
kdm[2181]: Unable to read configuration for display knight.vpn:1; stopping it.
kdm[2181]: Internal error: config reader supplied incomplete data
kdm[2181]: Unable to read configuration for display knight.vpn:1; stopping it.

I usually run dselect once a week, this issue began with the update made
last friday.  This last update made a modification to kdmrc, and the issue
here was initially diagnosed with the unmodified file.  I compared the
files and imported the modifications into the dpkg-dist version with no
visible change.  The only obvious modifications are a commenting out of
StaticServers and enabling of XDMRC.

Very few matches on Google for this issue.  I found one message stating
that I needed a "clean rebuild" of the binary, another suggesting that
this might be an IPv6 issue (I do not believe that I am running IPv6 at
the moment)

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kdm depends on:
ii  debconf [debconf-2.0]     1.4.70         Debian configuration management sy
ii  kdebase-bin               4:3.5.1-1      core binaries for the KDE base mod
ii  kdebase-data              4:3.5.1-1      shared data files for the KDE base
ii  kdelibs4c2a               4:3.5.1-2      core libraries for all KDE applica
ii  libc6                     2.3.5-13       GNU C Library: Shared libraries an
ii  libgcc1                   1:4.0.2-8      GCC support library
ii  libpam-runtime            0.79-3.1       Runtime support for the PAM librar
ii  libpam0g                  0.79-3.1       Pluggable Authentication Modules l
ii  libqt3-mt                 3:3.3.5-3      Qt GUI Library (Threaded runtime v
ii  libstdc++6                4.0.2-8        The GNU Standard C++ Library v3
ii  libx11-6                  6.9.0.dfsg.1-4 X Window System protocol client li
ii  libxau6                   6.9.0.dfsg.1-4 X Authentication library
ii  libxdmcp6                 6.9.0.dfsg.1-4 X Display Manager Control Protocol
ii  libxtst6                  6.9.0.dfsg.1-4 X Window System event recording an
ii  xbase-clients             6.9.0.dfsg.1-4 miscellaneous X clients

Versions of packages kdm recommends:
ii  logrotate                     3.7.1-2    Log rotation utility

-- 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 ---
After some configuration corrections (darned multiple interfaces) I have
successfully gotten an XDMRC connection to the KDE server, this was done
without any special configuration changes other than the ones required to
get the basic software working.  I consider this issue closed at this time.

-----Original Message-----
From: Erik Anderson [mailto:erikba@teamworkgroup.com] 
Sent: Friday, February 09, 2007 7:01 PM
To: '353940@bugs.debian.org'; '353940-quiet@bugs.debian.org';
'353940-submitter@bugs.debian.org'
Subject: RE: Bug#353940: About your bug: "kdm: will no longer start (using
Xvnc" on the Debian BTS

I have spent some time trying to get X working again as per this bug, but it
has been some time since I have been in here and many of the packages have
changed since then.

I have not yet successfully gotten an XDMCP session running yet, but I
cannot say whether it is related to this bug or one of many potential
configuration faults on my side.

FWIW a tightvnc server is showing a login prompt for me, so if that is
related to this issue then it may show progress being made

These are the current errors I'm seeing in my daemon.log, I have not yet
found a way to get additional information at this time.  I will try to
revisit this issue again later.

02:04:37 knight kdm[25851]: X server died during startup
02:04:37 knight kdm[25851]: X server for display :0 can't be started,
session disabled
02:06:08 knight kdm: 0.1.0.6:0[25856]: Cannot connect to 0.1.0.6:0, giving
up
02:06:08 knight kdm[25851]: Display 0.1.0.6:0 cannot be opened

-----Original Message-----
From: Ana Guerrero [mailto:ana-bugkde@debian.org] 
Sent: Tuesday, January 09, 2007 10:28 AM
To: 353940-submitter@bugs.debian.org
Cc: 353940-quiet@bugs.debian.org
Subject: Bug#353940: About your bug: "kdm: will no longer start (using Xvnc"
on the Debian BTS

Hi,

We (the Debian Qt/KDE team) are trying to update the bug status of some
old bugs in the BTS.

You filed the bug
 #353940 "kdm: will no longer start (using Xvnc"
some time ago, you can read the bug report at:
http://bugs.debian.org/353940

We are sorry if nobody responded when you filed the bug, KDE has gotten more
bugs
in the past years than the maintainers could handle. We are trying to fix
this now,
but we need your help. So please respond to this mail and tell us if:

- you are still experiencing this bug (adding in what version)
- the bug was already fixed, 
- or if you have extra information on how reproduce this bug.

--- 
Thanks in advance,
  Ana Guerrero,
  on behalf of the Debian Qt/KDE team


--- End Message ---

Reply to: