Your message dated Sun, 16 Apr 2023 07:12:46 +0200
with message-id <[email protected]>
and subject line kdm has been superseded by sddm
has caused the Debian Bug report #686065,
regarding kdm: the logon process fails using pam_winbind module
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.)


-- 
686065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686065
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kdm
Version: 4:4.8.4-3
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-3-486
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kdm depends on:
ii  adduser                       3.113+nmu3
ii  consolekit                    0.4.5-3.1
ii  debconf [debconf-2.0]         1.5.46
ii  kde-runtime                   4:4.8.4-1
ii  kde-wallpapers-default        4:4.8.4-1
ii  kde-workspace-kgreet-plugins  4:4.8.4-3
ii  libc6                         2.13-35
ii  libck-connector0              0.4.5-3.1
ii  libdbus-1-3                   1.6.0-1
ii  libkdecore5                   4:4.8.4-3
ii  libkdeui5                     4:4.8.4-3
ii  libkio5                       4:4.8.4-3
ii  libknewstuff3-4               4:4.8.4-3
ii  libkworkspace4abi1            4:4.8.4-3
ii  libpam0g                      1.1.3-7.1
ii  libqimageblitz4               1:0.0.6-4
ii  libqt4-svg                    4:4.8.2-2+b1
ii  libqt4-xml                    4:4.8.2-2+b1
ii  libqtcore4                    4:4.8.2-2+b1
ii  libqtgui4                     4:4.8.2-2+b1
ii  libstdc++6                    4.7.1-2
ii  libx11-6                      2:1.5.0-1
ii  libxau6                       1:1.0.7-1
ii  libxdmcp6                     1:1.1.1-1
ii  libxtst6                      2:1.2.1-1
ii  lsb-base                      4.1+Debian7

Versions of packages kdm recommends:
ii  kde-window-manager [x-window-manager]  4:4.8.4-3
ii  kde-workspace                          4:4.8.4-3
ii  konsole [x-terminal-emulator]          4:4.8.4-1
ii  logrotate                              3.8.1-4
ii  xserver-xorg [xserver]                 1:7.7+1
ii  xterm [x-terminal-emulator]            278-1

Versions of packages kdm suggests:
ii  kde-wallpapers  4:4.8.4-1
ii  kdepasswd       4:4.8.4-1

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

If I logon using domain credential in ssh or console there are no 
authentication problem but if I use kdm in /var/log/kdm.log I found:

2 XSELINUXs still allocated at reset
SCREEN: 0 objects of 152 bytes = 0 total bytes 0 private allocs
DEVICE: 0 objects of 64 bytes = 0 total bytes 0 private allocs
CLIENT: 0 objects of 160 bytes = 0 total bytes 0 private allocs
WINDOW: 0 objects of 32 bytes = 0 total bytes 0 private allocs
PIXMAP: 1 objects of 80 bytes = 80 total bytes 0 private allocs
GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs
CURSOR: 1 objects of 4 bytes = 4 total bytes 0 private allocs
CURSOR_BITS: 1 objects of 4 bytes = 4 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 3 objects, 88 bytes, 0 allocs
1 PIXMAPs still allocated at reset
PIXMAP: 1 objects of 80 bytes = 80 total bytes 0 private allocs
GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs
CURSOR: 1 objects of 4 bytes = 4 total bytes 0 private allocs
CURSOR_BITS: 1 objects of 4 bytes = 4 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 3 objects, 88 bytes, 0 allocs
1 CURSORs still allocated at reset
CURSOR: 1 objects of 4 bytes = 4 total bytes 0 private allocs
CURSOR_BITS: 1 objects of 4 bytes = 4 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 2 objects, 8 bytes, 0 allocs
1 CURSOR_BITSs still allocated at reset
CURSOR_BITS: 1 objects of 4 bytes = 4 total bytes 0 private allocs
DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs
TOTAL: 1 objects, 4 bytes, 0 allocs
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
klauncher(2786) kdemain: No DBUS session-bus found. Check if you have started 
the DBUS server. 
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(2778)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() 
D-Bus call failed:  "Not connected to D-Bus server" 

kdmgreet(2778)/kdecore (K*TimeZone*): No time zone information obtained from 
ktimezoned 

but in /var/log/auth.log all seems to works:
Aug 28 09:14:25 notetentoni kdm: :0[3930]: pam_unix(kdm:auth): authentication 
failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=  user=dominiocsa\psala
Aug 28 09:14:25 notetentoni kdm: :0[3930]: pam_winbind(kdm:auth): getting 
password (0x00004388)
Aug 28 09:14:25 notetentoni kdm: :0[3930]: pam_winbind(kdm:auth): pam_get_item 
returned a password
Aug 28 09:14:25 notetentoni kdm: :0[3930]: pam_winbind(kdm:auth): user 
'dominiocsa\psala' granted access
Aug 28 09:14:25 notetentoni kdm: :0[3930]: pam_unix(kdm:session): session 
opened for user DOMINIOCSA\psala by (uid=0)
Aug 28 09:14:25 notetentoni kdm: :0[3930]: pam_unix(kdm:session): session 
closed for user DOMINIOCSA\psala
Aug 28 09:14:25 notetentoni kdm: :0[3930]: pam_winbind(kdm:setcred): user 
'DOMINIOCSA\psala' OK


I'm not sure is a bug of kdm any way the problem arise if I use kdm as login 
manager

have a great day

Piviul

--- End Message ---
--- Begin Message ---
Version: 4:4.11.22-3+rm

kdm was last released with Debian 8 (jessie) in April 2015
and was removed from the Debian archive afterwards.
It has been superseded by sddm.
See https://bugs.debian.org/803635 for details on the removal.
I'm closing the remaining bug reports now.

Andreas

--- End Message ---

Reply via email to