similar to: Problems to authenticate Ubuntu 14 on Samba4

I'm using Ubuntu 14.04-64 bits I had installed with apt-get the follows packages krb5-user krb5-config winbind samba samba-common smbclient cifs-utils libpam-krb5 libpam-winbind libnss-winbind The samba version is 4.1.16-Ubuntu Below are my files of configuration */etc/samba/smb.conf* [global] netbios name = cliente-ad192 workgroup = EMPRESA security = ads realm = EMPRESA.COM

Hi all, I'm setting up an LXC container for Ubuntu 13.10 where the X server is started in the host on vt6. The unix socket and authority file are then mounted in the LXC container. I can start X sessions and applications from the container but I can't get LightDM to use this server. I would really like to have the container's LightDM/Ubuntu greeter to automatically start on this

Ok, know from desktop logon apparently the user logon right, look user 'policia\gafranchello' granted access on the trace below, but still tel me "Invalid password please try again" Jul 2 16:15:03 samba-cliente polkitd(authority=local): Unregistered Authentication Agent for unix-session:c6 (system bus name :1.231, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale

1) Does 'getent passwd policia\gafranchello' produce output when run on a Unix client ? If try to logon on unis console --> auth.log Jul 2 14:13:59 samba-cliente sshd[11654]: Invalid user POLICIA+gafranchello from 172.33.10.1 Jul 2 14:13:59 samba-cliente sshd[11654]: input_userauth_request: invalid user POLICIA+gafranchello [preauth] Jul 2 14:14:04 samba-cliente sshd[11654]:

Hello, in the assumption that I understand them correctly I specified in /etc/lightdm/lightdm.conf autologin-user=xxxx autologin-user-timeout=10 so that after 10 seconds the user xxxx is logged-in automatically. What happens is that the user xxxx is logged-in immediately i.e. without any delay. Do I understand the second variable wrong or am I missing something? Thanks for any help. K.D.J.

Unstable release in 1.8 series. Overview of changes in lightdm 1.7.2 * Fix incorrectly distributed guest-session apparmor data Overview of changes in lightdm 1.7.1 * Fix .pc file for liblightdm-qt5-3 * Add a new option "autologin-in-background" which lets an autologin happen in a second display while still showing the greeter. * Stop if fail to create default

I'm the founder and lead developer of the lightweight Linux distro Swift Linux. I'm currently in the process of switching from the old antiX Linux base to the new Linux Mint Debian Edition base. The new Swift Linux will be using LightDM instead of SLiM. I've found that replacing LMDE's default GDM display manager with SLiM disables many functions (like audio). Restoring these

Hello, I need the possibility to login to other machines on my network. With kdm it works by choosing "Remote Login" from a menu in the greeter. I would prefer not to use kdm. ;-) I saw that the option "greeter-show-remote-login" should do that for lightdm. I work with a debian "wheezy/testing" system and installed the following packages from the

I've been using lightdm for about a year now and with all the versions I've tried, Gentoo prints a message about lightdm and xdm failing to stop if I reboot from the lightdm menu or the xfce4 menu. If I issue 'reboot' as root from an xterm within xfce4, lightdm stops fine. I couldn't find anything in the logs, but in which one of syslog-ng's logs should I look? I'm

The VNC server just listens to the appropriate TCP/IP port and then runs Xvnc which does the actual VNC communication. Ideally I'd be able to do the same thing for RDP then the daemon doesn't get any more complicated, and a bug in the RDP layer can't crash the server. I don't know enough about how NX works but I suspect we could do the same thing as for VNC and RDP. I'm

This is the first release in the stable 1.4 series. This series will be maintained on the lp:lightdm/1.4 branch and trunk (lp:lightdm) will now be used for the unstable 1.5 series. Overview of changes in lightdm 1.4.0 * Correctly implement and test autologin timeouts * Add greeter-show-remote-login hint * Correctly annotate enums in vapi file * QLightDM: Add default constructor

I came across a race condition in lightdm greeter setup phase before the login screen is displayed (at boot time or after logout). I reported this also on Launchpad with more details (https://bugs.launchpad.net/lightdm/+bug/1172752), but to work on a proper fix, ideas on how to fix this would be welcome. During greeter setup "lightdm --session-child" is spawned twice. The first call to

https://bugs.freedesktop.org/show_bug.cgi?id=89730 Bug ID: 89730 Summary: NV50: LightDM GTK+ Greeter Background - inconsistent display Product: xorg Version: git Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

I''m having a problem with the boot sequence hanging indefinitely at "stopping system V runlevel compatibility". Here are the steps I took to get to this point: 1) installed a single boot, server version of ubuntu 11.10 (intended to be dom0) 2) apt-get install xen-hypervisor-4.1-amd64 xen-utils-4.1 xenwatch xen-tools xen-utils-common xenstore-utils 3) updated grub as follows: -

Hola, ¿qué tal? ¿Qué significa "basado en R"? ¿Modificando el código fuente de R? No te refieres a "un programa escrito en R", ¿verdad? Un saludo, Carlos J. Gil Bellosta http://www.datanalytics.com El 16 de marzo de 2017, 17:43, Francisco Rodríguez <fjroar en hotmail.com> escribió: > Hola buenos días, una pregunta que quiero realizar de R sobre el tema de > la

Or how to avoid the whirlwind. Greetings everyone. I observe the coding of lighdm is well under way and I'm thinking the pressure to meet the releases of 11.11 is probably going to build without bounds. Is there time now to consider the inclusion of some of the more offbeat use cases? 1: Headless(no monitor, keyboard, or monitor) 2: True headless(no video card) but Xvfb. 3: No X but only

Hi, I'm currently testing the XDMCP functionality of LightDM which seems to work flawless, however, there is one issue which I cannot resolve: The machine I am using for my setup is a dedicated machine running some VM's, these VM's don't have any graphics card associated and run headless and the only form of command is via a web interface or SSH. LightDM seems to use the

Hi! On v4.18-rc1, the mouse cursor is missing on my right monitor. Card is G98 [GeForce 8400 GS Rev. 2]. I have two monitors: one small landscape 1280x1024 on DVI-I-1 left, and one big 1600x1200 (1200x1600 portrait) on HDMI-1 right. Curiously, the cursor is missing not only with proper xrandr setup after logging in but even in mirrored mode at the lightdm greeter[1]. How is this even possible

I've setup a portable system (ubuntu 16.04) joined to my AD domain, that in their primary network works as expected. But in this 'COVID time', the portable start to roam around, and users say me that, suddenly after some days of use, get incredibly sloooowww... after that users reboot, and cannot get back in, login refused. I've setup a VPN, but clearly if users cannot login

Hello we have Samba Version 4.3.11, we are trying to logon linux desktop clients on domain, we easy can join the client on the domain with net rpc join -S 10.11.37.3 -U xxxxx it is satisfactory. We don't have kinit server. Later we install libpam-winbind, winbind ,libnss-winbind and samba on the client side. Edit nsswitch.conf --> passwd: compat winbind