Re: Autenticazione con winbind in kde
Piviul scrisse in data 23/08/2012 16:10:
> [...]
> Ho dato un'occhiata ai log ma non ho trovato nulla di significativo; se
> aveste qualche dritta sul logon tramite winbind con kde...
>
Brancolo ancora nel buio. Per me è un mistero. In auth.log infatti
durante un tentativo di autenticazione trovo:
> Aug 24 09:44:45 notetentoni kdm: :0[1782]: pam_unix(kdm:auth):
> authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=
> user=dominiocsa\psala
> Aug 24 09:44:45 notetentoni kdm: :0[1782]: pam_winbind(kdm:auth):
> getting password (0x00004388)
> Aug 24 09:44:45 notetentoni kdm: :0[1782]: pam_winbind(kdm:auth):
> pam_get_item returned a password
> Aug 24 09:44:45 notetentoni kdm: :0[1782]: pam_winbind(kdm:auth): user
> 'dominiocsa\psala' granted access
> Aug 24 09:44:45 notetentoni kdm: :0[1782]: pam_unix(kdm:session):
> session opened for user DOMINIOCSA\psala by (uid=0)
> Aug 24 09:44:46 notetentoni kdm: :0[1782]: pam_unix(kdm:session):
> session closed for user DOMINIOCSA\psala
> Aug 24 09:44:46 notetentoni kdm: :0[1782]: pam_winbind(kdm:setcred):
> user 'DOMINIOCSA\psala' OK
Quindi l'autenticazione avviene correttamente. In kdm.log invece viene
loggato:
> 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(2888) kdemain: No DBUS session-bus found. Check if you have
> started the DBUS server.
> kdeinit4: Communication error with launcher. Exiting!
> kdmgreet(2880)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned
> initialize() D-Bus call failed: "Not connected to D-Bus server"
>
> kdmgreet(2880)/kdecore (K*TimeZone*): No time zone information
> obtained from ktimezoned
Qui sicuramente c'è qualcosa che non va ma cosa? Qualcuno ha qualche idea?
Grazie
Piviul
Reply to: