linuxmint / slick-greeter Goto Github PK
View Code? Open in Web Editor NEWA slick-looking LightDM greeter
License: GNU General Public License v3.0
A slick-looking LightDM greeter
License: GNU General Public License v3.0
So, I'm attempting to build a distro for a school to potentially use, and while I've been doing a bit of research and discovered, that when connected to a user server domain, you'll most of the time have to put DOMAINNAME\usernamehere as your login, rather than just usernamehere to log in to the Domain.
What I'm asking for, is the ability to set it to be a more user-friendly way of logging in, by having it, like in Windows, where you can optionally log in as 'usernamehere' for the User Name output, but instead, it will log in as 'DOMAINNAME\usernamehere', I feel this will be so much more user-friendly, having the option to just have the domain name part auto-filled into the Username entry, unless the user themselves supply another Domain Name before their username.
Hi there , us ( Manjaro Linux ) and i think also @ikeydoherty ( Solus ) and @fossfreedom ( Ubuntu Budgie ) are interested at the screensaver implementation in order to drop the gnome legacy screensaver .. ( guys correct me if i wrong :p and sorry if mention you :p ) . In the source code i don't see this .. any plan to add this feature ?
Stefano Capitani
Manjaro Team
System: Mint 18.2 beta
There are some aspects in the guest account, which might to get changed or removed, because they do not make any sense or are annoying.
The main annoying thing is the welcome screen. Many of the offered feature (all with package management relation) are not usable for the guest. Further more it is annoying, that the guest has to close at first the information window about the guest account (makes sense) and with a second click the welcome screen.
Also the autostarting update manager does not make any sense in the guest account.
You might also consider to remove the complete administration section from the menu of the guest account. Also this is of no use for the guest account and removing it would make the menu (all applications) more clear.
When Logo is set to a Logotype image, or something that fits, you'll see that unlike Unity Greeter, the Logo here has no padding AT ALL and literally touches the left of the Slick Greeter area...
(Can't screenshot it as the Logo doesn't appear at all in Test Mode)
* slick-greeter version (slick-greeter --version): 1.0.7
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...): Mint 18.2 Sonya
* Graphics hardware *and* driver used: Intel GM965/GL960 Integrated Graphics. 2.1 Mesa 17.2.1
* 32 or 64 bit: 64-bit
Issue
Pressing the 'power off' button whilst the greeter is running causes an excessively slow shutdown - the shutdown takes some thirty seconds, and without any messages about what is going on, unless one presses a key and tries to interpret the system messages. The slowness seems bound up with the somewhat notorious 'a stop job is running' systemd problem. (One can see that from the aforementioned system messages.) I have a hardware 'watchdog' running and perhaps without that watchdog the shutdown would not happen at all.
Steps to reproduce
Expected behaviour
A fast shutdown or at least a slow-shutdown-with-some-sort-of-explanation. Also, a prompt - do you really want to shut down?' - might be an idea.
Other information
The affected computer - I have not tested the problem on others, yet - is a dell D830 Latitude, with 8GB RAM, a SSD, and a dual-core processor. It runs Cinnamon.
Linux Mint 18.2 Cinnamon 64 bit, upgraded from 18.1 following these instructions. Next installed LightDM and removed MDM following the same instructions.
If I go into the guest account I have unlimited access to all installed user accounts and their content.
I can access the accounts as well via Nemo (simply clicking file system in the side bar -> home -> account name) or via terminal (cd /home/account_name).
In a fresh install this problem does not exist.
For now it should be said in the blog about upgrading, that the guest account does in this case not give the same privacy protection as in a new install. The current warning ("not recommended for novice users") does not give a hint about the problem.
Reported via debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866999
"during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
From the attached log (scroll to the bottom...):
0m50.5s ERROR: FAIL: Broken symlinks:
/usr/share/slick-greeter/badges/ubuntu-2d.png -> ubuntu.png"
suggest just delete ubuntu-2d since that project died several years ago and is no longer available in any distro.
Package: slick-greeter Version: 1.0.7+sonya
System: Host: U47VC Kernel: 4.4.0-91-generic x86_64 (64 bit) Desktop: Cinnamon 3.4.6 Distro: Linux Mint 18.2 Sonya
Graphics: Card-1: Intel 3rd Gen Core processor Graphics Controller Card-2: NVIDIA GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] Display Server: X.Org 1.18.4 driver: nvidia Resolution: [email protected], [email protected] GLX Renderer: GeForce GT 620M/PCIe/SSE2 GLX Version: 4.4.0 NVIDIA 340.102
Issue
Login screen resolution is smaller than monitor resolution. External monitor is always set as primary display
Picture attached.
Steps to reproduce
Connect an external monitor and login.
Expected behaviour
Login screen resolution should have monitor resolution. MDM works fine.
Other information
/var/log/lightdm/seat0-greeter.log
seat0-greeter.log.txt
attached
Hi Folks,
It would be nice if you could display the avatar from the selected user.
You can find the avatar in the LightDM.User -> get_image() property.
https://lazka.github.io/pgi-docs/LightDM-1/classes/User.html#LightDM.User.get_image
This has to be one of the best features that Unity Greeter didn't ever have, the ability to have your user picture displayed on the left of the Username and Password box for the selected user. If this is added, it'd be much appreciated.
Also, a bit of cornering for that square the User Picture is in would also look nice, no outlines though around it, that might ruin the look of it.
* slick-greeter version: slick-greeter 1.0.8
* Distribution - Ubuntu 18.04
Feature Request
Personally I don't have an issue, but many novice users don't understand how to login after typing in their password, as there is no "arrow" at the right of the password box like unity-greeter used to have. So for usability I think it would be good to have some indication of what to click for a user (yes yes, I use "Enter" key and don't need it, but again several of our users have been confused)
* slick-greeter version (slick-greeter --version)
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
* Graphics hardware *and* driver used
* 32 or 64 bit
$ inxi -GS
System: Host: mintyfresh Kernel: 4.8.0-58-generic x86_64 (64 bit) Desktop: Cinnamon 3.4.3
Distro: Linux Mint 18.2 Sonya
Graphics: Card: Intel Sky Lake Integrated Graphics
Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
Resolution: [email protected], [email protected]
GLX Renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) GLX Version: 3.0 Mesa 12.0.6
$ slick-greeter -v
[+0.00s] DEBUG: settings.vala:145: Overriding dconf setting for background with /usr/share/backgrounds/linuxmint/edesigner_linuxmint.png
[+0.00s] DEBUG: settings.vala:145: Overriding dconf setting for enable-hidpi with auto
[+0.00s] DEBUG: settings.vala:159: Overriding dconf setting for draw-user-backgrounds
[+0.00s] DEBUG: settings.vala:159: Overriding dconf setting for draw-grid
[+0.00s] DEBUG: slick-greeter.vala:587: HiDPI support: auto
[+0.13s] DEBUG: slick-greeter.vala:613: Launched at-spi-bus-launcher. PID: 4393
[+0.18s] DEBUG: slick-greeter.vala:622: Starting slick-greeter 1.0.7 UID=1000 LANG=en_US.UTF-8
[+0.18s] DEBUG: slick-greeter.vala:625: Setting cursor
[+0.18s] DEBUG: slick-greeter.vala:639: Loading command line options
slick-greeter 1.0.7
Issue
Slick-Greeter will use the lower resolution (1440x900) for both screens. I do not know how to change this in the settings, or if I should even need to. I would expect the default behaviour to be the "Expected behaviour" listed below.
Steps to reproduce
reboot or logout. I could not find any settings that effected corrected it.
Expected behaviour
Expected the screen with 1920x1080 resolution to display using 1920x1080 resolution and the screen with 1440x900 resolution to display using 1440x900.
Other information
This is on a Mint Cinnamon system that was upgraded from 18.1 to 18.2 and I converted from MDM (default for 18.1) to Slick-greeter (default for 18.2), MDM would use the correct resolutions.
Test system: Mint 18.2 beta Cinnamon 64 bit
Environment: VirtualBox
For testing auto-login I did this:
I created in /etc/lightdm the file lightdm.conf
I entered this code:
[Seat:*] allow-guest=false autologin-user=user_name autologin-user-timeout=10
(in separate lines; the code function of GH puts all into 1 line)
The value 10 is meant to give the chance, to login in another account, if wanted.
Expected:
After timeout the login screen vanishes and the desktop of the account user_name launches.
Result:
If the timeout has expired the screen goes black for a second or so, than the login screen reappears. After some more seconds the auto login takes place as expected.
It appears, as if auto login needs 2 attempts, until it gets successful. Until now it only seems to be a visual, but ugly glitch.
I upgraded from Mint 18.1 to 18.2 and rebooted. All seemed to work, but I then logged out of account A, logged into account B, logged out of B and back into A and - at that point - there was an error message. To wit: 'Cinnamon just crashed. You are currently running in Fallback Mode.' The error box came with an option to restart Cinnamon, and upon doing so all seemed good except that there were no desktop icons, even after I launched Nemo via an icon on my dock.
I should add: a single line of text flashed up when switchings users. (It did so on every switch, I think.) The message mentioned rc.local, but I did not have time to read it properly. However, I do find the following in my log, with approximately the right time stamp: 'systemd // Started /etc/rc.local Compatibility'. I mention this because (1) it may be a clue to the problem I am reporting, (2) ideally no text should flash up when switching users. EDIT: This particular problem was with my setup, specifically a faulty script run by a udev rule; the problem was not Mint. Apologies. Still, it may be that my udev problem caused Cinnamon to crash. If so, one could interpret that in either of two ways. To wi: either there is no problem with the greeter or with Cinnamon; or a minor problem with a script of mine was enough to crash Cinnamon, and that's bad.
I will add finally that, evidently enough - and I do not mean to carp - that user switching is important. I use one account to give presentations, but before I use that account I might have logged into another account. So this stuff really does need to work. Note also that I was not using 'fast user switching' - or what one might call 'user switching properly so called' (for I've given up on that); rather I logged out of each account before logging into another one.
Quick glance through the code:
https://github.com/linuxmint/slick-greeter/search?utf8=%E2%9C%93&q=font+ubuntu&type=
Whilst the schema has a "font to use" type key - from the above search there are several instances where "ubuntu" is hard-coded.
Slick greeter doesn't respect the last used or default user session from /home/$USER/.dmrc or lightdm.conf
It thinks all sessions are invalid:
From seat0-greeter.log:
[+0.47s] DEBUG: slick-greeter.vala:194: Invalid session: 'plasma'. Using session 'xfce' instead.
[+0.54s] DEBUG: slick-greeter.vala:194: Invalid session: 'xfce'. Using session 'xfce' instead.
I'm using the AUR package on Manjaro Linux
* slick-greeter version: 1.0.7
* Distribution - Mint 18.2
* 64 bit
Issue
Consider the following series of circumstances.
Steps to reproduce
Follow the series of actions described above.
Expected behaviour
It would be better, when there are two user accounts, to offer for login the account that the user has not just left. With >2 user accounts, things get a little more complex, but, again, there's little point offering the account that just's been exited/suspended.
Other information
* slick-greeter version 1.0.7
* Distribution - Mint 18.2
* Graphics hardware NVIDIA
* 64 bit
I wonder if there is any support for choosing a session language. So far I couldn't find it and the lightdm-gtk-setting "show-language-selector=true also had no effect. I guess it is just not supported!? Any plans to add this as I think it's quite useful and needed for multi language support in mixed language environments (work/private)
* slick-greeter version (slick-greeter --version) 1.08
* Distribution - Ubuntu Budgie 17.10
* Graphics hardware *and* driver used: Virtualbox
* 32 or 64 bit : 64bit
Issue
I have two sessions - Budgie Desktop which the greeter is saying is the "default" - and Ubuntu GNOME Session
After exiting Ubuntu GNOME session, the greeter icon shows the budgie icon. Immediately logging in re-logs into the Ubuntu GNOME Session
Steps to reproduce
Install two sessions.
Via the greeter login to the non default session.
Logout - observe that the greeter icon is wrongly stated as the default session icon.
Expected behaviour
The greeter icon should be the last session used.
[Feel free to close this issue if you feel it is a bad or misplaced idea. If that is the case then receive my deepest apologies, I don't want to waste your time. Thank you for your work on linux mint]
Users of nvidia optimus laptops using "nvidia prime" are required to log-out and log-in every time they want to switch the graphics card. A common scenario is to "boot, log in, run sudo prime-select nvidia
, log out and log in again". I have to do that whenever I want to use the HDMI output in my laptop.
Having an indicator at the login screen allowing me to switch the graphics card seems logical to me as I would just need to "boot, change graphics card (if I want to) and login".
The tools /usr/bin/prime-supported
and /usr/bin/prime-select
can be used to detect if prime is supported and to select the nvidia/intel card, respectively.
Thanks again for your time
* slick-greeter 1.0.7
* Distribution - Mint 18.2
* Graphics hardware *and* driver used - Nvidia 375.82
* 64 bit
Please add out of the box numlock support option
I have one external monitor above the default laptop monitor, but slick-greeter defaults to have the external one on the right.
* slick-greeter version: 1.0.7.
* Distribution: Mint 18.2.
* Graphics hardware *and* driver used: Intel, but details irrelevant I think.
* 64 bit.
Issue
Slick-greeter hangs on boot.
Steps to reproduce
sudo apt autoremove
and accede when when asked whether you want to removed mdm config.Expected behaviour
Other information
I fixed the problem thusly: sudo dpkg-reconfigure mdm
Logitech keyboard wrong layout, defaults to US with '"' + '@' reversed.
Not sure if I am maybe missing that setting, but I can't seem to find a way to change the default login window position.
If this is actually not an included feature I would love to see it in the future.
Thank you.
Given the distro agnostic aspect of the greeter suggest that Debian folder be moved to a separate branch so that other distros can package without having to patch out that folder.
Mint 18.2 Beta Cinnamon 64 bit.
The switch user function needs to get removed from the guest account, because there is no way to to return to the opened guest session.
Alternatively: Some changes are needed, to allow a guest user to re-enter his session.
Most likely typical scenario: You have allowed a person to open a guest session. During the guest session the owner needs to get quickly int his own account (e. g. for checking his mails). Usually (in case of normal accounts) user switching is just the method to use in this case. But when the owner has finished his task and the guest will continue his session (assume, he was in the middle to search something in the web), he cannot. Trying to re-enter the guest account actually opens a new guest session, the (still opened) old guest session is no more reachable.
So the guest (and also the owner of the pc) must be aware that an interrupted session cannot get re-opened. The guest has to log out and has later to open a new guest session.
I am aware your project is for a Linux distro but I was curious as to how it'd work on freebsd. Build itself passes, but there is a defect in files/Makefile generated by ./configure that means it does not use find . to do find (on FreeBSD, a file argument to find is required; on GNU (which is what LinuxMint is based on), it's not)
So far as I can see there is not an option for this.
Mint 18.2.
PS: Well done for 18.2.
I'm not sure where the right place for this issue is, also it might be a problem limited to Arch/Manjaro. Anyway, what I see is this:
I launch the greeter with "Switch user", then log back into the existing session.
Now I see the open session just briefly, but then for a moment the lock-screen pops up and disappears again. After that everything is fine with the session.
Any ideas?
Greetings, I was looking into this particular issue, but I don't know neither I am sure if the problem lies here or on lightdm, I was able to compile and create a package of slick-greeter on Archlinux, but no matter what, I don't have an option available to enable a guest session
You can see on the screenshot that I manage to compile it and works properly (I think, correct me if I am wrong), but I don't have the option to enter into a guest session. Once again, probably there is something I may be missing but I leave some options down here related to the compiling process:
This is the packaging I took as a base for the compilation, these are the options available from unity-greeter on Arch: unity-greeter compilation options
This is the packaging of slick-greeter, you can check and maybe compare some options here. As an off-topic, that repository also has the lightdm-settings packaging and some other packages as well
After some testing I manage to remove the patching options and it compiles and works successfully, except from some warnings that I took some screenshot (I do owe you those since the computer I am using right now doesn't have those screenshots, but maybe I can try to attach them once I get home); but if you can help me checking I will appreciate it
After upgrading to v1.0.4 from v1.0.3, slick greeter no longer renders the greeter background image. The log files that correspond to each version and their differences are found below. The background that should be rendering is found at /etc/lightdm/background.png
.
v1.0.3 (seat0-greeter.log)
`[+0.00s] DEBUG: settings.vala:159: Overriding dconf setting for draw-grid
[+0.00s] DEBUG: slick-greeter.vala:520: HiDPI support: auto
[+0.07s] DEBUG: slick-greeter.vala:543: Launched at-spi-bus-launcher. PID: 8274
[+0.08s] DEBUG: slick-greeter.vala:552: Starting slick-greeter 1.0.3 UID=108 LANG=en_US.UTF-8
[+0.08s] DEBUG: slick-greeter.vala:555: Setting cursor
[+0.08s] DEBUG: slick-greeter.vala:569: Loading command line options
[+0.08s] DEBUG: slick-greeter.vala:597: Setting GTK+ settings
[+0.13s] DEBUG: slick-greeter.vala:620: Creating Slick Greeter
[+0.13s] DEBUG: slick-greeter.vala:55: Creating background surface
[+0.13s] DEBUG: Connecting to display manager...
[+0.13s] DEBUG: Wrote 22 bytes to daemon
[+0.13s] DEBUG: Read 8 bytes from daemon
[+0.13s] DEBUG: Read 149 bytes from daemon
[+0.13s] DEBUG: Connected version=1.18.3 default-session=plasma show-manual-login=true hide-users=true has-guest-account=false show-remote-login=true
[+0.21s] WARNING: slick-greeter.vala:179: Could not find a default session.
[+0.21s] DEBUG: slick-greeter.vala:197: Using default session: '(null)'
[+0.21s] WARNING: slick-greeter.vala:179: Could not find a default session.
[+0.21s] DEBUG: slick-greeter.vala:197: Using default session: '(null)'
[+0.22s] DEBUG: Loaded session /usr/share/xsessions/default.desktop (Plasma, Plasma by KDE)
[+0.22s] DEBUG: Loaded session /usr/share/xsessions/plasma.desktop (Plasma, Plasma by KDE)
[+0.22s] WARNING: slick-greeter.vala:179: Could not find a default session.
[+0.22s] DEBUG: slick-greeter.vala:197: Using default session: '(null)'
[+0.22s] DEBUG: Starting authentication for user (null)...
[+0.22s] DEBUG: Wrote 16 bytes to daemon
[+0.23s] DEBUG: main-window.vala:198: Screen is 1920x1200 pixels
[+0.23s] DEBUG: main-window.vala:206: Monitor 0 is 1920x1200 pixels at 0,0
[+0.23s] DEBUG: slick-greeter.vala:623: Showing greeter
[+0.23s] DEBUG: slick-greeter.vala:272: Showing main window
[+0.23s] DEBUG: background.vala:488: Regenerating backgrounds
[+0.23s] DEBUG: background.vala:68: Making background /etc/lightdm/background.png at 1920x1200
[+0.23s] DEBUG: slick-greeter.vala:633: Starting main loop
[+0.23s] DEBUG: Read 8 bytes from daemon
[+0.23s] DEBUG: Read 26 bytes from daemon
[+0.23s] DEBUG: Prompt user with 1 message(s)
[+0.23s] WARNING: slick-greeter.vala:179: Could not find a default session.
[+0.23s] DEBUG: slick-greeter.vala:197: Using default session: '(null)'
[+0.24s] WARNING: slick-greeter.vala:179: Could not find a default session.
[+0.24s] DEBUG: slick-greeter.vala:197: Using default session: '(null)'
[+0.25s] DEBUG: slick-greeter.vala:260: starting system-ready sound
[+0.26s] DEBUG: background.vala:121: Render of background /etc/lightdm/background.png complete
[+2.03s] DEBUG: main-window.vala:198: Screen is 1920x1200 pixels
[+2.03s] DEBUG: main-window.vala:206: Monitor 0 is 1920x1200 pixels at 0,0
`
v1.0.4 (seat0-greeter.log)
`[+0.00s] DEBUG: settings.vala:145: Overriding dconf setting for background with /etc/lightdm/background.png
[+0.00s] DEBUG: settings.vala:159: Overriding dconf setting for draw-grid
[+0.00s] DEBUG: slick-greeter.vala:576: HiDPI support: auto
[+0.07s] DEBUG: slick-greeter.vala:599: Launched at-spi-bus-launcher. PID: 11802
[+0.08s] DEBUG: slick-greeter.vala:608: Starting slick-greeter 1.0.4 UID=108 LANG=en_US.UTF-8
[+0.08s] DEBUG: slick-greeter.vala:611: Setting cursor
[+0.08s] DEBUG: slick-greeter.vala:625: Loading command line options
[+0.08s] DEBUG: slick-greeter.vala:653: Setting GTK+ settings
[+0.12s] DEBUG: slick-greeter.vala:676: Creating Slick Greeter
[+0.12s] DEBUG: slick-greeter.vala:55: Creating background surface
[+0.13s] DEBUG: Connecting to display manager...
[+0.13s] DEBUG: Wrote 22 bytes to daemon
[+0.13s] DEBUG: Read 8 bytes from daemon
[+0.13s] DEBUG: Read 149 bytes from daemon
[+0.13s] DEBUG: Connected version=1.18.3 default-session=plasma show-manual-login=true hide-users=true has-guest-account=false show-remote-login=true
[+0.20s] DEBUG: slick-greeter.vala:212: Using default session: 'gnome'
[+0.20s] DEBUG: slick-greeter.vala:212: Using default session: 'gnome'
[+0.20s] DEBUG: main-window.vala:199: Screen is 1920x1200 pixels
[+0.20s] DEBUG: main-window.vala:207: Monitor 0 is 1920x1200 pixels at 0,0
[+0.20s] DEBUG: slick-greeter.vala:679: Showing greeter
[+0.21s] DEBUG: slick-greeter.vala:287: Showing main window
[+0.22s] DEBUG: Loaded session /usr/share/xsessions/default.desktop (Plasma, Plasma by KDE)
[+0.22s] DEBUG: Ignoring session /usr/share/xsessions/gnome.desktop
[+0.22s] DEBUG: Loaded session /usr/share/xsessions/plasma.desktop (Plasma, Plasma by KDE)
[+0.22s] DEBUG: slick-greeter.vala:212: Using default session: 'gnome'
[+0.22s] DEBUG: Starting authentication for user (null)...
[+0.22s] DEBUG: Wrote 16 bytes to daemon
[+0.23s] DEBUG: slick-greeter.vala:689: Starting main loop
[+0.23s] DEBUG: slick-greeter.vala:212: Using default session: 'gnome'
[+0.23s] DEBUG: background.vala:68: Making background #000000 at 1920x1200
[+0.23s] DEBUG: background.vala:79: Render of background #000000 complete
[+0.23s] DEBUG: Read 8 bytes from daemon
[+0.23s] DEBUG: Read 26 bytes from daemon
[+0.23s] DEBUG: Prompt user with 1 message(s)
[+0.23s] DEBUG: slick-greeter.vala:212: Using default session: 'gnome'
[+0.24s] DEBUG: slick-greeter.vala:275: starting system-ready sound
[+2.03s] DEBUG: main-window.vala:199: Screen is 1920x1200 pixels
[+2.03s] DEBUG: main-window.vala:207: Monitor 0 is 1920x1200 pixels at 0,0
`
I used the sample code on the README to configure slick-greeter by creating /etc/lightdm/slick-greeter.conf
with this code:
[greeter]
background = /var/lib/lightdm/wallpapers/airplane.jpg
draw-user-backgrounds = true
draw-grid = false
show-hostname = true
theme-name = United-Opensuse-Dark
icon-theme = HighContrast
font-name = Overpass Regular 11
xft-antialias = true
xft-hintstyle = hintslight
enable-hidpi = auto
However, these settings are not applied. I still get the defaults. Then, I edited and compiled the glib scemas file with these settings and the changes were applied. This seems counter-intuitive to me. The glib file is overwritten each upgrade. The /etc/lightdm/slick-greeter.conf isn't since it is storing the configuration for you.
OS: Arch Linux x86_64
Kernel: 4.11.3-1-ARCH
The README mentions /etc/lightdm/slick-greeter.conf but no example file exists
Suggestion here is to have a an example file - structure and definition that is available and installed with the distro.
What are the possible values? - comments and a meaning for each key-value pair would be very valuable.
EDIT: example for lightdm-gtk-greeter - https://github.com/ocf/lightdm-gtk-greeter-ocf-old/blob/master/data/lightdm-gtk-greeter.conf
Hi development team,
Could you add on/off feature for guest session.
Best regards.
Hi there , i have iported this greeter on Manjaro Linux but at the moment i have one issue : The session is not saved
Here the log of seat0
[+0,00s] DEBUG: slick-greeter.vala:511: Starting slick-greeter 1.0.0 UID=620 LANG=it_IT.UTF-8
Activating service name='org.a11y.atspi.Registry'
[+0,01s] DEBUG: settings.vala:143: Overriding dconf setting for background with /usr/share/backgrounds/manjarowall17_08.jpg
[+0,01s] DEBUG: settings.vala:143: Overriding dconf setting for theme-name with Arc-Maia-Dark
[+0,01s] DEBUG: settings.vala:143: Overriding dconf setting for icon-theme-name with Arc-Maia
[+0,01s] DEBUG: settings.vala:157: Overriding dconf setting for draw-grid
[+0,02s] DEBUG: slick-greeter.vala:517: Setting cursor
[+0,14s] DEBUG: slick-greeter.vala:531: Loading command line options
[+0,14s] DEBUG: slick-greeter.vala:559: Setting GTK+ settings
Successfully activated service 'org.a11y.atspi.Registry'
[+1,72s] DEBUG: slick-greeter.vala:582: Creating Slick Greeter
[+1,72s] DEBUG: slick-greeter.vala:55: Creating background surface
[+1,77s] DEBUG: Connecting to display manager...
[+1,77s] DEBUG: Wrote 26 bytes to daemon
[+1,77s] DEBUG: Read 8 bytes from daemon
[+1,77s] DEBUG: Read 160 bytes from daemon
[+1,77s] DEBUG: Connected api=1 version=1.22.0 default-session=default show-manual-login=false hide-users=false has-guest-account=false show-remote-login=true
[+1,86s] DEBUG: background.vala:457: Failed to load background component : Apertura del file «» non riuscita: File o directory non esistente
[+1,87s] DEBUG: background.vala:457: Failed to load background component : Apertura del file «» non riuscita: File o directory non esistente
(slick-greeter:609): Gtk-WARNING **: Attempting to add a widget with type GtkBox to a GtkMenuItem, but as a GtkBin subclass a GtkMenuItem can only contain one widget at a time; it already contains a widget of type GtkLabel
[+2,99s] DEBUG: Loading users from org.freedesktop.Accounts
[+2,99s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+2,99s] DEBUG: User /org/freedesktop/Accounts/User1002 added
[+2,99s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+3,00s] DEBUG: User /org/freedesktop/Accounts/User1003 added
[+3,00s] DEBUG: user-list.vala:1030: Adding/updating user stefano (Stefano)
[+3,00s] DEBUG: Loading sessions from org.freedesktop.DisplayManager
[+3,10s] DEBUG: slick-greeter.vala:193: Invalid session: 'gnome'. Using session 'mate' instead.
[+3,10s] DEBUG: user-list.vala:1030: Adding/updating user gnomeste ()
[+3,34s] DEBUG: slick-greeter.vala:193: Invalid session: 'gnome'. Using session 'mate' instead.
[+3,34s] DEBUG: user-list.vala:1030: Adding/updating user mateste ()
[+3,34s] DEBUG: slick-greeter.vala:193: Invalid session: 'mate'. Using session 'mate' instead.
[+3,34s] DEBUG: user-list.vala:1030: Adding/updating user stebudgie ()
[+3,35s] DEBUG: slick-greeter.vala:193: Invalid session: 'budgie-desktop'. Using session 'mate' instead.
[+3,40s] DEBUG: Loaded session /usr/share/xsessions/mate.desktop (MATE, Questa sessione esegue l'accesso in MATE)
[+3,44s] DEBUG: Loaded session /usr/share/xsessions/gnome-xorg.desktop (GNOME su Xorg, Questa sessione esegue l'accesso in GNOME)
[+3,45s] DEBUG: Loaded session /usr/share/xsessions/gnome.desktop (GNOME, Questa sessione esegue l'accesso in GNOME)
[+3,46s] DEBUG: Loaded session /usr/share/xsessions/gnome-classic.desktop (GNOME classico, Questa sessione si avvia con GNOME classico)
[+3,50s] DEBUG: Loaded session /usr/share/xsessions/budgie-desktop.desktop (Desktop Budgie, Questa sessione ti fa entrare nel Desktop Budgie)
[+3,52s] DEBUG: Loaded session /usr/share/wayland-sessions/gnome.desktop (GNOME, Questa sessione esegue l'accesso in GNOME)
[+3,53s] DEBUG: Starting authentication for user stefano...
[+3,53s] DEBUG: Wrote 23 bytes to daemon
[+3,54s] DEBUG: main-window.vala:198: Screen is 1366x768 pixels
[+3,54s] DEBUG: main-window.vala:206: Monitor 0 is 1366x768 pixels at 0,0
[+3,54s] DEBUG: slick-greeter.vala:585: Showing greeter
[+3,54s] DEBUG: slick-greeter.vala:266: Showing main window
[+3,55s] DEBUG: slick-greeter.vala:595: Starting main loop
[+3,56s] DEBUG: background.vala:485: Regenerating backgrounds
[+3,56s] DEBUG: background.vala:68: Making background /usr/share/backgrounds/manjarowall17_08.jpg at 1366x768
[+3,61s] DEBUG: Read 8 bytes from daemon
[+3,61s] DEBUG: Read 37 bytes from daemon
[+3,61s] DEBUG: Prompt user with 1 message(s)
[+3,67s] DEBUG: slick-greeter.vala:254: starting system-ready sound
[+3,85s] DEBUG: background.vala:121: Render of background /usr/share/backgrounds/manjarowall17_08.jpg complete
[+30,41s] DEBUG: session-list.vala:51: Adding session budgie-desktop (Desktop Budgie)
[+30,42s] DEBUG: session-list.vala:51: Adding session gnome (GNOME)
[+30,42s] DEBUG: session-list.vala:51: Adding session gnome (GNOME)
[+30,42s] DEBUG: session-list.vala:51: Adding session gnome-classic (GNOME classico)
[+30,42s] DEBUG: session-list.vala:51: Adding session gnome-xorg (GNOME su Xorg)
[+30,42s] DEBUG: session-list.vala:51: Adding session mate (MATE)
[+30,44s] DEBUG: greeter-list.vala:210: Error registering user list dbus object: Risulta già esportato un oggetto per l'interfaccia x.dm.SlickGreeter.List su /list
[+40,14s] DEBUG: Providing response to display manager
[+40,14s] DEBUG: Wrote 25 bytes to daemon
[+40,19s] DEBUG: Read 8 bytes from daemon
[+40,19s] DEBUG: Read 19 bytes from daemon
[+40,19s] DEBUG: Authentication complete for user stefano with return code 0
[+40,19s] CRITICAL: pango_layout_get_cursor_pos: assertion 'index >= 0 && index <= layout->length' failed
[+40,19s] DEBUG: Starting session gnome-xorg
[+40,19s] DEBUG: Wrote 22 bytes to daemon
[+40,55s] DEBUG: Read 8 bytes from daemon
[+40,55s] DEBUG: Read 4 bytes from daemon
[+40,55s] DEBUG: user-list.vala:1030: Adding/updating user stefano (Stefano)
[+40,56s] DEBUG: slick-greeter.vala:193: Invalid session: 'gnome-xorg'. Using session 'mate' instead.
[+40,56s] DEBUG: slick-greeter.vala:590: Got a SIGTERM
[+40,56s] DEBUG: slick-greeter.vala:598: Cleaning up
[+40,56s] DEBUG: slick-greeter.vala:606: AT-SPI exited with return value 0
[+40,56s] DEBUG: slick-greeter.vala:612: Exiting
Issue
The shortcut for un-hiding hidden users is undocumented
Steps to reproduce
Hide some user and try to un-hide it with a shortcut
Expected behaviour
It says something like: "until Alt + xy is hit"
Current status
It says: "until a special key combination is hit"
Slick-greeter : 1.0.8
Distribution - Debian Buster AMD64
Issue
I added the slick-greeter.conf file and configured the backgroung, logo etc.
After a reboot or a logout slick-greeter is remplacing the lightdm-greeter but I can't see my background image and logo or any change. My images files are in /usr/share/wallpaper/
slick-greeter leaves at-spi process running which blocks user session at-spi
** (cinnamon-session:1614): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
** (cinnamon-settings-daemon:1797): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
** (cinnamon-launcher:1890): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
** (cinnamon:1932): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
** (polkit-gnome-authentication-agent-1:1948): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
** (canberra-gtk-play:1950): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
** (abrt:1942): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
** (nm-applet:1944): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
** (nemo:1946): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
Failed to play sound: Sound disabled
** (cinnamon-killer-daemon:1947): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
** (blueberry-tray.py:1955): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
** (blueberry-obex-agent.py:1945): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
** (redshift-gtk:1949): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OWmOPJb639: Connection refused
Cjs-Message: JS LOG: About to start Cinnamon
St-Message: cogl npot texture sizes SUPPORTED
It is a known issue with lighdm-gtk
https://bugs.launchpad.net/debian/+source/lightdm/+bug/1366534
slick-greeter needs to clean up its child processes on exit.
Hi , how set it without .conf file in the lightdm.conf file ? I have added on Manjaro linux and i want use the gsettings schemas to do our config ..
Thank you
Stefano Capitani
If I leave the computer on after it reached the login screen, without actually logging in, the screen eventually goes blank. Moving the mouse or using the keyboard won't get me the screen back, not even typing my password and pressing enter. The only solution is to restart the system and login before the screen goes blank.
I was told to provide proper info and some logging. I don't know which info or which logs so here's my best guess:
inxi -Fz: https://pastebin.com/4cpsQk8M
Auth log: https://pastebin.com/aSwpqwrT
* slick-greeter 1.0.8
* Distribution - Manjaro Linux
* 64 bit
Issue
At least the following settings are not respected:
show-a11y=false
(set as true)
show-keyboard=false
(set as true)
font-name=customfontname
(set as Ubuntu or DejaVu Sans except for top bar) (reported in #50)
Steps to reproduce
Set these settings in /etc/lightdm/slick-greeter.conf
Expected behaviour
Slick greeter respects them
* slick-greeter version (slick-greeter --version)
1.12
* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
Arch
* Graphics hardware *and* driver used
Nvidia and Intel, Nouveau
* 32 or 64 bit
64bit
Issue
I'm only able to see the first 6 desktop sessions
Steps to reproduce
Have a laptop open the session chooser and have more then 6 sessions installed
Expected behaviour
Being able to scroll up and down all the desktop sessions
:)
The session badges are 22x22px PNG...
https://github.com/linuxmint/slick-greeter/tree/master/files/usr/share/slick-greeter/badges
* Distribution - Ubuntu Budgie 17.10
* Graphics hardware: Dual Intel and Nvidia Graphics. Only intel driver in use
* 64 bit
Issue
Login prompt is not being mirrored. Default behaviour on most DMs is to mirror display when second monitor is connected
Steps to reproduce
Plug in external display, reboot and login
Expected behaviour
Login screen mirrored not extended
Other Infomation
On X11
Is it the intention that this distro agnostic greeter be pushed to Debian to allow the wider Debian and Debian derived distros to see this excellent effort?
Basically what the title says, HighContrast is happily present on the system, but for some reason, it doesn't apply HighContrast, but rather Adwaita
Steps to Reproduce:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.