similar to: lightdm + xorg.conf + nvidia driver

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

Hi, I made the switch from KDE4->XFCE, and because gdm takes more time than xfce to start I would like to replace it with lightdm. I installed lightdm, set it as default display manager and configured the gtk greeter. However, when I start I only get a black screen (x running) and nothing else happens. When I start it as root with the --test-mode argument, I get the following message: lightdm

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

Greetings, I've been trying to get LightDM working on FreeBSD, as there is no package for it yet. I've managed to get it compiled from source, but it fails to start. It displays the message, "Failed to get D-Bus connection". D-Bus is running, and LightDM starts the X server fine. Is there anything I need to do to get it to talk to dbus? Right now I have LightDM installed in my

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

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

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.

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

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

On 01/28/2016 11:10 AM, Jonathan Billings wrote: > On Thu, Jan 28, 2016 at 10:30:03AM -0500, ken wrote: >> When someone is sitting at their linux machine which is running >> gnome, and if that machine is running at 'init 5', and if they >> aren't yet logged in, they'll have something on their screen called >> the Greeter. If they successfully log in

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

On 02/07/2020 20:32, jmpatagonia via samba wrote: > 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

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

Hello Rowland, still not working, I try to use getent differents ways and not working, I believe we are try to update/migrate to samba 4 AD, for us this a big project because we have a lot of users (about 600) and there separated on different building, we need to keep the users password and we need to try that all PC working actually with windows xp/7 not join to domain again if not is a big work.

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

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

Hi all, I've removed two legacy features from LightDM: 1. lightdm-set-defaults This tool was created so that scripts could easily modify the LightDM configuration, in particular so packages could modify it on installation / removal. This is not required since LightDM 1.8 as you can now create a snippet of configuration in /etc/lightdm/lightdm.conf.d or /usr/share/lightdm/lightdm.conf.d.

The problem is at the end 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:

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