arcticaproject / arctica-greeter

Arctica Greeter: Greeter Frontend for LightDM

Arctica Greeter

Configuration

• The default configuration is stored in dconf under the schema org.ArcticaProject.arctica-greeter.
• Distributions should set their own defaults using a GLib override.

Features

• Arctica Greeter is cross-distribution and should work pretty much anywhere.
• Arctica Greeter uses Ayatana Indicators for the tray icons, so make sure they are available in your distribution, as well.
• This greeter supports HiDPI.
• Sessions are validated. If a default/chosen session isn't present on the system, the greeter scans for known sessions in /usr/share/xsessions and replaces the invalid session choice with a valid session.
• You can take a screenshot by pressing PrintScrn. The screenshot is saved in /var/lib/lightdm/Screenshot.png.

Credits

• Arctica Greeter started as a fork of Unity Greeter 16.04.2, a greeter developed for Ubuntu by Canonical. Furtheron, various improvements are take from Slick Greeter, the LinuxMint fork of Unity Greeter.

arctica-greeter's Issues

a11y: screen reader output for password change

The password change dialog that pops up when the user password has expired:

Here the screen reader reads odd things and need to be checked and reworked.

For all windows appearing, the WM_TRANSIENT_FOR X11 property should be set (pointing to the greeter's main window)

X11::Protocol::WM::set_wm_transient_for ($X, $window, $transient_for)
Set the WM_TRANSIENT_FOR property on $window (an XID).

$transient_for is another window XID, or undef if $window is not transient for anything so WM_TRANSIENT_FOR should be deleted.

"Transient for" means $window is some sort of dialog or menu related to the given $transient_for window. The window manager will generally iconify $window together with its $transient_for, etc. See set_motif_wm_hints() below for "modal" transients.

Use case: with marco keybindings disabled (see #28 and an upcoming fix for that), we need to assure that dialog windows from e.g. NM applet always stay above the greeter's main window (as they cannot be raised again via ALT-TAB).

Arctica-greeter Resolution bug

If you go in and change the resolution from Arctica-greeter on the remote desktop it will keep using the wrong resolution. It needs the "-g fullscreen" command.

ADD multimonitor support: show login screen on every display

multimonitor support: show login screen on every display

support positioning of logo to all four corners + specify offset

test mode broken since 32d28d7bf2646fc7a0008937034246fcc96dbc8a

@Ionic: test mode cannot be triggered via /usr/sbin/arctica-greeter --test-mode anymore since 32d28d7. Can you amend that? Thanks.

Arctica greeter malfunctioning under arch linux?

hello, there seems to be an issue with arctica-greeter under arch linux, i dont know why this happens but when i try to use this greeter, its resulting in a black screen and it seems to be restarting itself over and over.
i used this aur to install it but i did some changes to make it build successfully.
https://aur.archlinux.org/packages/lightdm-arctica-greeter

i tried downgrading to 0.99.3.0 and 0.99.4.0 and its the same result except it doesnt keep restarting.
could this issue be an incompatibility with newer versions of the dependencies?
whats weird is that debian seems to have a lot of dependencies for arctica-greeter compared to this aur so im not sure if this aur package was set up properly.
these are all the log files from /var/log/lightdm
lightdm.zip

this error in particular persists even if i dont have ayatana indicators installed.
** (process:917): WARNING **: 01:48:28.433: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method ?RegisterClient?

Failing to compile Arctica Greeter

Hello everyone,
I have followed the guide on how to install the Arctica Greeter. I followed the guide, did a fresh install, everything seemed to be working fine until I got to the point where I had to use the debuild command on all 5 folders. I have managed to debuild all of them except for the arctica-greeter folder. I installed the additional dependencies that weren't listed on the guide, but after doing that, I got even more errors when trying to debuild.

dpkg-buildpackage -rfakeroot -D -us -uc dpkg-buildpackage: warning: using a gain-root-command while being root dpkg-buildpackage: source package arctica-greeter dpkg-buildpackage: source version 0.99.0.1-0 dpkg-buildpackage: source distribution UNRELEASED dpkg-buildpackage: source changed by Mike Gabriel <[email protected]> dpkg-source --before-build arctica-greeter dpkg-buildpackage: host architecture amd64 fakeroot debian/rules clean dh clean --with autoreconf --fail-missing dh_testdir -O--fail-missing debian/rules override_dh_auto_clean make[1]: Entering directory '/root/greeter/arctica-greeter' dh_auto_clean make -j1 distclean make[2]: Entering directory '/root/greeter/arctica-greeter' Making distclean in src make[3]: Entering directory '/root/greeter/arctica-greeter/src' test -z "logo-generator" || rm -f logo-generator test -z "arctica-greeter" || rm -f arctica-greeter rm -f *.o rm -f *.tab.c test -z "" || rm -f test . = "." || test -z "" || rm -f test -z "Makefile.in" || rm -f Makefile.in rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags rm -rf ./.deps rm -f Makefile make[3]: Leaving directory '/root/greeter/arctica-greeter/src' Making distclean in data make[3]: Entering directory '/root/greeter/arctica-greeter/data' rm -f org.ArcticaProject.arctica-greeter.gschema.valid test -z "" || rm -f test . = "." || test -z "" || rm -f test -z "50-arctica-greeter.conf 50-arctica-guest-wrapper.conf arctica-greeter.desktop arctica-guest-session-startup.desktop Makefile.in logo.png" || rm -f 50-arctica-greeter.conf 50-arctica-guest-wrapper.conf arctica-greeter.desktop arctica-guest-session-startup.desktop Makefile.in logo.png rm -f Makefile make[3]: Leaving directory '/root/greeter/arctica-greeter/data' Making distclean in po make[3]: Entering directory '/root/greeter/arctica-greeter/po' rm -f *.pox arctica-greeter.pot *.old.po cat-id-tbl.tmp rm -f .intltool-merge-cache rm -f Makefile Makefile.in POTFILES stamp-it rm -f *.mo *.msg *.cat *.cat.m *.gmo make[3]: Leaving directory '/root/greeter/arctica-greeter/po' Making distclean in tests make[3]: Entering directory '/root/greeter/arctica-greeter/tests' test -z "arctica-greeter-test" || rm -f arctica-greeter-test test -z "test.c test-list.c test-main-window.c menubar.c arctica-greeter.c flat-button.c toggle-box.c user-list.c greeter-list.c remote-logon-service.c background.c email-autocompleter.c config.vapi fixes.vapi cairo-utils.c animate-timer.c indicator.vapi fadable.c fadable-box.c dash-box.c user-prompt-box.c fading-label.c cached-image.c dash-entry.c dash-button.c prompt-box.c session-list.c main-window.c list-stack.c settings.c shutdown-dialog.c" || rm -f test.c test-list.c test-main-window.c menubar.c arctica-greeter.c flat-button.c toggle-box.c user-list.c greeter-list.c remote-logon-service.c background.c email-autocompleter.c config.vapi fixes.vapi cairo-utils.c animate-timer.c indicator.vapi fadable.c fadable-box.c dash-box.c user-prompt-box.c fading-label.c cached-image.c dash-entry.c dash-button.c prompt-box.c session-list.c main-window.c list-stack.c settings.c shutdown-dialog.c rm -f *.o rm -f ../src/*.o rm -f *.tab.c test -z "" || rm -f test . = "." || test -z "" || rm -f rm -f ../src/.deps/.dirstamp rm -f ../src/.dirstamp test -z "Makefile.in" || rm -f Makefile.in rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags rm -rf ../src/.deps ./.deps rm -f Makefile make[3]: Leaving directory '/root/greeter/arctica-greeter/tests' make[3]: Entering directory '/root/greeter/arctica-greeter' test -z "" || rm -f test . = "." || test -z "" || rm -f test -z "Makefile.in aclocal.m4 arctica-guest-account-script compile configure config.h.in config.h depcomp gtk-doc.make install-sh missing mkinstalldirs omf.make xmldocs.make po/Makefile.in.in" || rm -f Makefile.in aclocal.m4 arctica-guest-account-script compile configure config.h.in config.h depcomp gtk-doc.make install-sh missing mkinstalldirs omf.make xmldocs.make po/Makefile.in.in rm -f config.h stamp-h1 rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags rm -f cscope.out cscope.in.out cscope.po.out cscope.files make[3]: Leaving directory '/root/greeter/arctica-greeter' rm -f config.status config.cache config.log configure.lineno config.status.lineno rm -f Makefile make[2]: Leaving directory '/root/greeter/arctica-greeter' if [ -e po/arctica-greeter.pot.bak ]; then \ mv -f po/arctica-greeter.pot.bak po/arctica-greeter.pot; \ fi rm -f src/arctica_greeter_vala.stamp rm -f src/logo_generator_vala.stamp rm -f tests/arctica_greeter_test_vala.stamp rm -f src/*.c rm -f tests/*.c rm -f debian/theme-debian-logo.png make[1]: Leaving directory '/root/greeter/arctica-greeter' dh_autoreconf_clean -O--fail-missing dh_clean -O--fail-missing dpkg-source -b arctica-greeter dpkg-source: warning: source directory 'arctica-greeter' is not <sourcepackage>-<upstreamversion> 'arctica-greeter-0.99.0.1' dpkg-source: info: using source format '1.0' dpkg-source: info: building arctica-greeter in arctica-greeter_0.99.0.1-0.tar.gz dpkg-source: info: building arctica-greeter in arctica-greeter_0.99.0.1-0.dsc debian/rules build dh build --with autoreconf --fail-missing dh_testdir -O--fail-missing dh_update_autotools_config -O--fail-missing debian/rules override_dh_autoreconf make[1]: Entering directory '/root/greeter/arctica-greeter' if [ ! -e po/arctica-greeter.pot.bak ]; then \ cp po/arctica-greeter.pot po/arctica-greeter.pot.bak; \ fi NOCONFIGURE=1 dh_autoreconf ./autogen.sh /usr/bin/mate-autogen checking for autoconf >= 2.53... testing autoconf2.50... not found. testing autoconf... found 2.69 checking for automake >= 1.7... testing automake-1.15... found 1.15 checking for intltool >= 0.25... testing intltoolize... found 0.51.0 checking for pkg-config >= 0.14.0... testing pkg-config... found 0.29.1 checking for mate-common >= 1.1.0... testing mate-doc-common... found 1.12.0 Checking for required M4 macros... Checking for forbidden M4 macros... Processing ./configure.ac Running mate-doc-common... Running intltoolize... Running autoreconf... autoreconf: Entering directory.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force --warnings=no-portability
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force --warnings=no-portability
autoreconf: running: /usr/bin/autoheader --force --warnings=no-portability
autoreconf: running: automake --add-missing --copy --force-missing --warnings=no-portability
configure.ac:8: installing './compile'
configure.ac:7: installing './install-sh'
configure.ac:7: installing './missing'
Makefile.am: installing './INSTALL'
src/Makefile.am: installing './depcomp'
autoreconf: Leaving directory .' Skipping configure process. make[1]: Leaving directory '/root/greeter/arctica-greeter' dh_auto_configure -O--fail-missing ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu --libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... none checking for valac... /usr/bin/valac checking whether /usr/bin/valac is at least version 0.24.0... yes checking whether to enable maintainer-specific portions of Makefiles... no checking whether make supports nested variables... (cached) yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.16... yes checking for ARCTICA_GREETER... yes checking for valgrind... valgrind --trace-children=yes --num-callers=256 checking whether NLS is requested... yes checking for intltool >= 0.35.0... 0.51.0 found checking for intltool-update... /usr/bin/intltool-update checking for intltool-merge... /usr/bin/intltool-merge checking for intltool-extract... /usr/bin/intltool-extract checking for xgettext... /usr/bin/xgettext checking for msgmerge... /usr/bin/msgmerge checking for msgfmt... /usr/bin/msgfmt checking for gmsgfmt... /usr/bin/msgfmt checking for perl... /usr/bin/perl checking for perl >= 5.8.1... 5.22.1 checking for XML::Parser... ok checking for GTK_3_20_0... no checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating data/Makefile config.status: creating po/Makefile.in config.status: creating src/Makefile config.status: creating tests/Makefile config.status: creating config.h config.status: executing depfiles commands config.status: executing po/stamp-it commands debian/rules override_dh_auto_build make[1]: Entering directory '/root/greeter/arctica-greeter' dh_auto_build make -j1 make[2]: Entering directory '/root/greeter/arctica-greeter' make all-recursive make[3]: Entering directory '/root/greeter/arctica-greeter' Making all in src make[4]: Entering directory '/root/greeter/arctica-greeter/src' rm -f logo_generator_vala.stamp && echo stamp > logo_generator_vala.stamp-t CDPATH="${ZSH_VERSION+.}:" && cd . && /usr/bin/valac --debug --pkg posix --pkg gtk+-3.0 --pkg gdk-x11-3.0 --pkg gio-unix-2.0 --pkg x11 --pkg liblightdm-gobject-1 --pkg libcanberra --pkg gio-2.0 --pkg pixman-1 --target-glib 2.32 -C logo-generator.vala mv -f logo_generator_vala.stamp-t logo_generator_vala.stamp gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -I/usr/include/gtk-3.0 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/lightdm-gobject-1 -I/usr/include/gio-unix-2.0/ -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/freetype2 -I/usr/include/pixman-1 -w -DGETTEXT_PACKAGE=\"arctica-greeter\" -DLOCALEDIR=\""/usr/share/locale"\" -DVERSION=\"0.99.0.1\" -DPKGDATADIR=\""/usr/share/arctica-greeter"\" -DINDICATORDIR=\""/usr/lib/ayatana-indicators3/7/"\" -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c -o logo_generator-logo-generator.o test -f 'logo-generator.c' || echo './'logo-generator.c gcc -pthread -D_REENTRANT -I/usr/include/gtk-3.0 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng12 -I/usr/include/lightdm-gobject-1 -I/usr/include/gio-unix-2.0/ -I/usr/include/libxml2 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/freetype2 -I/usr/include/pixman-1 -w -DGETTEXT_PACKAGE=\"arctica-greeter\" -DLOCALEDIR=\""/usr/share/locale"\" -DVERSION=\"0.99.0.1\" -DPKGDATADIR=\""/usr/share/arctica-greeter"\" -DINDICATORDIR=\""/usr/lib/ayatana-indicators3/7/"\" -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro -o logo-generator logo_generator-logo-generator.o -lgdk-3 -layatana-ido3-0.4 -layatana-indicator3 -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -llightdm-gobject-1 -lcairo -lfreetype -lcanberra -lpixman-1 -lX11 -lXext -lm rm -f arctica_greeter_vala.stamp && echo stamp > arctica_greeter_vala.stamp-t CDPATH="${ZSH_VERSION+.}:" && cd . && /usr/bin/valac --debug --pkg posix --pkg gtk+-3.0 --pkg gdk-x11-3.0 --pkg gio-unix-2.0 --pkg x11 --pkg liblightdm-gobject-1 --pkg libcanberra --pkg gio-2.0 --pkg pixman-1 --target-glib 2.32 -C config.vapi fixes.vapi indicator.vapi xsync.vapi animate-timer.vala background.vala cached-image.vala cairo-utils.vala email-autocompleter.vala dash-box.vala dash-button.vala dash-entry.vala fadable.vala fadable-box.vala fading-label.vala flat-button.vala greeter-list.vala idle-monitor.vala list-stack.vala main-window.vala menu.vala menubar.vala prompt-box.vala session-list.vala remote-logon-service.vala settings.vala settings-daemon.vala shutdown-dialog.vala toggle-box.vala arctica-greeter.vala user-list.vala user-prompt-box.vala main-window.vala:216.9-216.19: error: The type name Gdk.Monitor' could not be found
Gdk.Monitor primary = display.get_primary_monitor();
^^^^^^^^^^^
main-window.vala:225.13-225.23: error: The type name Gdk.Monitor' could not be found Gdk.Monitor monitor = display.get_monitor(i); ^^^^^^^^^^^ main-window.vala:249.9-249.19: error: The type name Gdk.Monitor' could not be found
Gdk.Monitor mon0;
^^^^^^^^^^^
main-window.vala:256.13-256.23: error: The type name Gdk.Monitor' could not be found Gdk.Monitor mon1; ^^^^^^^^^^^ main-window.vala:54.9-54.26: error: The type name Gdk.DrawingContext' could not be found
Gdk.DrawingContext background_context;
^^^^^^^^^^^^^^^^^^
Compilation failed: 5 error(s), 0 warning(s)
Makefile:1090: recipe for target 'arctica_greeter_vala.stamp' failed
make[4]: *** [arctica_greeter_vala.stamp] Error 1
make[4]: Leaving directory '/root/greeter/arctica-greeter/src'
Makefile:510: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/root/greeter/arctica-greeter'
Makefile:381: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/root/greeter/arctica-greeter'
dh_auto_build: make -j1 returned exit code 2
debian/rules:20: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/root/greeter/arctica-greeter'
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
debuild: fatal error at line 1376:
dpkg-buildpackage -rfakeroot -D -us -uc failed
`
Is there something I am missing? Any kind of help is greatly appreciated!

Long PAM messages are partially hidden

Some typical long PAM messages are:

Password expired. Change your password now.
Password change failed. Server message: Old password not accepted.
Password change failed. Server message: Password is in history of old passwords

In the current arctica-greeter, only "Password change failed. Server message: Pa" is displayed, the rest is hidden, so users can't understand why their password renewal fails.

Please allow long PAM messages to be fully displayed even if it's ugly, or at least show them on mouse hover.

Logon screen can be bypassed using various shortcuts

Original bug-report was reported at https://pad.lv/1948339 about Ubuntu MATE 21.10. Previous releases like 20.10 and 21.04 are affected too.

The essence of the above bug-report:

It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter):

• Mod4 + S (mate-search-tool)
• Mod4 + E (Open Caja / File Explorer)
• CTRL + Shift + Esc (mate-system-monitor)
• PRNT (Screenshot)

All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen.

Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI.

I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica-greeter, rather than within every single binary launched by shortcuts.

The bug was reproduced on a fresh installation of Ubuntu Mate 21.10.

Please find additional version details below:

$ apt-cache policy lightdm

lightdm:
Installed: 1.30.0-0ubuntu4
Candidate: 1.30.0-0ubuntu4
Version table:
*** 1.30.0-0ubuntu4 500
500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy arctica-greeter

arctica-greeter:
Installed: 0.99.1.5-2nmu1
Candidate: 0.99.1.5-2nmu1
Version table:
*** 0.99.1.5-2nmu1 500
500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages
100 /var/lib/dpkg/status

Thanks,
Basti

The magnifier application steals the focus from the password entry

As the title says, while Magnus is active one cannot type into the entry. I tried a bunch of potential fixes, but nothing productive came out.

shutdown dialog: Abort time on mouse-over.

Don't block shutdown

Test case: on arctica-greeter, press the "poweroff" computer button (=ACPI shutdown). The attached suspend/reboot/shutdown dialog will shown forever, making graceful remote shutdowns impossible.

On the other hand, all other greeters that I've tested show a countdown of e.g. 60 seconds, honoring the shutdown event at the end of the countdown.
Please do the same!

The same issue also affects VirtualBox VMs, Proxmox servers (the MATE VMs block the server reboot) etc.

arctica-greeter does not honor gsettings changes

The new arctica-greeter being used in Ubuntu MATE 20.10 does not allow any changes to its settings/theme. Both the direct edit of 90-arctica-greeter.conf file and changes via gsettings/dconf-editor do not get desired result. There is a bug on launchpad.

I would like to add that it is not specific to Ubuntu MATE. Same issue exists on LinuxMint if we install+enable arctica-greeter.

remote logons should just fail, if not available

Instead of falling back to LightDM's default session, remote logon's that don't work, should just fail and a failure message should be presented to the user.

Basically, remote logon failures due to unavailablity of the underlying LightDM remote session, probably indicate a setup flaw of the system running Arctica Greeter.

Ubuntu MATE 20.10 arctica-greeter requires seleting user on first boot

Ubuntu MATE 20.10 with arctica-greeter no longer selects username created during installation during first boot.

Per test case 1300 for Ubuntu MATE, step #20.

"The system boots properly and loads into Ubuntu MATE showing username selected at step 15"

Expected outcome:

• Username created during installation is selected and user can enter password directly to login.

Actual outcome:

• Instead user is required to selected the user they created during the installation process in order to be able to login.

---

DistroRelease: Ubuntu 20.10 (installed from 20201017 ISO)
Package: arctica-greeter 0.99.1.4-1
Downstream bug-report: https://pad.lv/1895875 .

Arctica Greeter defaults to session "ubuntu" if no other sessions are available.

This should be change, so it defaults to the default Xsession user session, which probably ends up with a message box or so on most distributions if no desktop shell is installed.

If a deskop shell is installed, the default Xsession probably launches the system's default (X) session manager.

Does not work with xmdcp under Ubuntu Mate 20.10 on Raspberry pi.

XMDCP does not work with the Arctica-greeter. It looks like it's an issue with Unity-greeter. After switching to slick-greeter, xmdcp worked with no issue. I would have liked to have stayed with Arctica-greeter, but I need xmdcp. Hopefully, this problem will be fixed in a future update.

font name/size split not working on fonts names containing blanks

I just tried to use "Noto Sans" as font for Arctica Greeter. The result is a 6pt font rendered. Not sure if it actually is a Noto font variety.

The underlying cause is this code in src/prompt-box.vala:

    public static string font = AGSettings.get_string (AGSettings.KEY_FONT_NAME);
    public static string font_family = font.split_set(" ")[0];
    public static int font_size = int.parse(font.split_set(" ")[1]);

We need to split the KEY_FONT_NAME value at the last blank, not at the first.

Testmode fixes now block construction while in GLib.Bus.watch_name()

@Ionic: With the latest fix for arctica-greeter --test-mode the greeter doesn't come up anymore when running as display manager via LightDM.

I added some extra debug messages and the code never reaches debug ("At end of ArcticaGreeter.construct().");.

@Ionic: Have you tested your change with arctica-greeter running as display manager? If not, please revisit. Thanks.

diff --git a/src/arctica-greeter.vala b/src/arctica-greeter.vala
index 322f7e3..10878f1 100644
--- a/src/arctica-greeter.vala
+++ b/src/arctica-greeter.vala
@@ -123,6 +123,9 @@ public class ArcticaGreeter : Object
                                                     debug ("xsettings is ready");
                                                     continue_init = true;
                                                 }
+                                                else {
+                                                    debug ("connected settings-daemon plugin '%s'", name);
+                                                }
                                             }
                                         );
                                     }
@@ -155,10 +158,12 @@ public class ArcticaGreeter : Object
              */
             continue_init = true;
         }
+        debug ("At end of ArcticaGreeter.construct().");
     }
 
     public override void constructed ()
     {
+        debug ("Nearly done with constructing SingleInstance class object ArcticaGreeter.");
         if (continue_init)
         {
             xsettings_ready ();
@@ -166,6 +171,7 @@ public class ArcticaGreeter : Object
 
         /* Chain up - actually necessary. */
         base.constructed ();
+        debug ("Fully done with constructing SingleInstance class object ArcticaGreeter.");
     }
 
     /*

Arctica greeter does not play well with accountsservice

Steps to reproduce:

1. Have Ubuntu MATE 20.10 installed
2. Install i3 with sudo apt-get install i3*
3. Reboot machine
4. Select i3 (or i3 with debug) on login screen

Expected results:

• i3 starts

Actual results:

• MATE starts instead of i3

---

Extra info:

After entering to "i3" it says:

$ sudo grep Session /var/lib/AccountsService/users/$USER
Session=mate
XSession=mate

After removing mate-session-manager it shows the following:

$ sudo grep Session /var/lib/AccountsService/users/$USER
Session=mate
XSession=i3

Downstream bug-report - https://bugs.launchpad.net/bugs/1910279 .

Black screen on multiseat after logout

Xorg, systemd etc support the concept of multiple seats, one seat per graphics card.
LTSP also supports a very easy way to configure it, by just putting MULTISEAT=1 in ltsp.conf.

Up to Ubuntu 20.04 with slick-greeter, everything was working fine.
Now with Ubuntu 22.04 and actica-greeter, after logout we're getting black screen in either one or both seats.

A workaround is in /usr/lib/lightdm/lightdm-greeter-session to change the following line:

--- [ -n "$DBUS_SESSION_BUS_ADDRESS" ] || eval `dbus-launch --sh-syntax`
+++ eval `dbus-launch --sh-syntax`

I.e. by forcing a new dbus, there's no black screen anymore.

It feels like something in the greeter or the indicators is incompatible with the concept that "a single user, lightdm, using a single dbus, may launch the greeter two times, and have the indicators two times".

Make GTK-3/4 builds controllable via an explicit configure flag

Today, by coincidence I built arctica-greeter against GTK-4 where the build failed (I simply had both libgtk-4-dev and libgtk-3-dev installed on my test system). Problem is, that we hard-codedly enforce gtk-3 builds, but we have HAVE_GTK_4_0 passages which get activated by the pure presence of GTK-4 header files.

As GTK-4 support is gradually moving into the arctica-greeter code, we need a proper way of controlling whether we want to build against GTK-4 or GTK-3.

Guest Session not working on Debian

I have lightdm with Arctica greeter installed and they work just fine. Then I wanted to try the guest session of arctica.

I installed guest-session like below:
apt-get install arctica-greeter-guest-session

my lightdm config became this:

$ /usr/sbin/lightdm --show-config
   [Seat:*]
I  greeter-session=arctica-greeter
I  greeter-hide-users=false
A  session-wrapper=/etc/X11/Xsession
I  user-session=xfce
C  guest-wrapper=/usr/libexec/lightdm/lightdm-guest-session
G  xserver-allow-tcp=true
G  xserver-command=X -core -listen tcp
H  allow-guest=true
H  greeter-allow-guest=true
I  greeter-show-manual-login=true
I  greeter-show-remote-login=true

   [LightDM]
H  guest-account-script=arctica-greeter-guest-account-script

Sources:
A  /usr/share/lightdm/lightdm.conf.d/01_debian.conf
B  /usr/share/lightdm/lightdm.conf.d/40-kde-plasma-kf5.conf
C  /usr/share/lightdm/lightdm.conf.d/50-arctica-greeter-guest-wrapper.conf
D  /usr/share/lightdm/lightdm.conf.d/50-slick-greeter.conf
E  /usr/share/lightdm/lightdm.conf.d/80-ukui-greeter.conf
F  /usr/share/lightdm/lightdm.conf.d/90-arctica-greeter.conf
G  /etc/lightdm/lightdm.conf.d/70-xserver-remote-connection.conf
H  /etc/lightdm/lightdm.conf.d/91-arctica-greeter-guest-session.conf
I  /etc/lightdm/lightdm.conf.d/99-my-own-configuration.conf
J  /etc/lightdm/lightdm.conf

Still when I click on Guest Session in the Arctica greeter, the screen goes black and comes back to the greeter, as if nothing happened. Logging in with regular users is fine. I noticed the following messages in the logs:

Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x40000f (arctica-gr)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

But I don't know if they have anything to do with it. Below is the full seat0.log. Can anyone help?

debianuser@debian9:/var/log/lightdm$ sudo cat seat0-greeter.log
[+0.00s] DEBUG: arctica-greeter.vala:701: HiDPI support: auto
[+0.00s] DEBUG: posix_spawn avoided (fd close requested) 
/usr/libexec/arctica-greeter/arctica-greeter-check-hidpi:33: DeprecationWarning: Gdk.Screen.get_primary_monitor is deprecated
  primary = screen.get_primary_monitor()
/usr/libexec/arctica-greeter/arctica-greeter-check-hidpi:35: DeprecationWarning: Gdk.Screen.get_monitor_geometry is deprecated
  rect = screen.get_monitor_geometry(primary)
/usr/libexec/arctica-greeter/arctica-greeter-check-hidpi:36: DeprecationWarning: Gdk.Screen.get_monitor_width_mm is deprecated
  width_mm = screen.get_monitor_width_mm(primary)
/usr/libexec/arctica-greeter/arctica-greeter-check-hidpi:37: DeprecationWarning: Gdk.Screen.get_monitor_height_mm is deprecated
  height_mm = screen.get_monitor_height_mm(primary)
/usr/libexec/arctica-greeter/arctica-greeter-check-hidpi:38: DeprecationWarning: Gdk.Screen.get_monitor_scale_factor is deprecated
  monitor_scale = screen.get_monitor_scale_factor(primary)
arctica-greeter-check-hidpi: Window scale is 1
[+0.13s] DEBUG: arctica-greeter.vala:710: Loading command line options
[+0.13s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.18s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close requested) 
[+0.18s] DEBUG: arctica-greeter.vala:769: Launched at-spi-bus-launcher. PID: 1882
[+0.18s] DEBUG: arctica-greeter.vala:780: Starting arctica-greeter 0.99.1.3 UID=115 LANG=en_US.UTF-8
[+0.18s] DEBUG: arctica-greeter.vala:783: Setting cursor
[+0.18s] DEBUG: arctica-greeter.vala:787: Setting GTK+ settings
[+0.24s] DEBUG: arctica-greeter.vala:810: Creating Arctica Greeter
[+0.24s] DEBUG: Connecting to display manager...
[+0.24s] DEBUG: Wrote 26 bytes to daemon
[+0.24s] DEBUG: Read 8 bytes from daemon
[+0.24s] DEBUG: Read 155 bytes from daemon
[+0.24s] DEBUG: Connected api=1 version=1.26.0 default-session=xfce show-manual-login=true hide-users=false has-guest-account=true show-remote-login=true
[+0.25s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.25s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close requested) 
[+0.25s] DEBUG: arctica-greeter.vala:852: Launched marco WM. PID: 1894
[+0.25s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.26s] WARNING: arctica-greeter.vala:897: Systemd failed to start Indicator Service 'ayatana-indicator-keyboard': Failed to start ayatana-indicator-keyboard.service: Unit ayatana-indicator-keyboard.service not found.

[+0.26s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.26s] DEBUG: arctica-greeter.vala:894: Successfully started Indicator Service 'ayatana-indicator-session'
[+0.26s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.27s] WARNING: arctica-greeter.vala:897: Systemd failed to start Indicator Service 'ayatana-indicator-datetime': Failed to start ayatana-indicator-datetime.service: Unit ayatana-indicator-datetime.service not found.

[+0.27s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.27s] DEBUG: arctica-greeter.vala:894: Successfully started Indicator Service 'ayatana-indicator-power'
[+0.27s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.28s] WARNING: arctica-greeter.vala:897: Systemd failed to start Indicator Service 'ayatana-indicator-sound': Failed to start ayatana-indicator-sound.service: Unit ayatana-indicator-sound.service not found.

[+0.28s] DEBUG: posix_spawn avoided (fd close requested) 
[+0.29s] DEBUG: arctica-greeter.vala:894: Successfully started Indicator Service 'ayatana-indicator-application'
[+0.29s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close requested) 
[+0.31s] DEBUG: arctica-greeter.vala:919: Launched nm-applet. PID: 1925
[+0.31s] DEBUG: arctica-greeter.vala:937: Starting main loop
[+0.31s] DEBUG: settings-daemon.vala:72: Acquired org.gnome.SessionManager
[+0.31s] DEBUG: settings-daemon.vala:98: Acquired org.gnome.ScreenSaver
[+0.31s] DEBUG: settings-daemon.vala:160: All bus names acquired, starting /usr/bin/mate-settings-daemon
[+0.31s] DEBUG: posix_spawn avoided (automatic reaping requested) (fd close requested) 
[+0.34s] DEBUG: settings-daemon.vala:173: Launched /usr/bin/mate-settings-daemon. PID: 1930

** (mate-settings-daemon:1930): WARNING **: 18:18:58.640: There was a problem when setting QT_AUTO_SCREEN_SCALE_FACTOR=0: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “Setenv”

** (mate-settings-daemon:1930): WARNING **: 18:18:58.641: There was a problem when setting QT_SCALE_FACTOR=1: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “Setenv”
[+0.50s] DEBUG: arctica-greeter.vala:125: xsettings is ready
[+0.50s] DEBUG: arctica-greeter.vala:534: Creating background surface
[+0.51s] DEBUG: menubar.vala:345: LANG=en_US.UTF-8 LANGUAGE=(null)
[+0.51s] WARNING: File '/usr/lib/ayatana-indicators3/7/liborg.ayatana.indicator.keyboard.so' does not exist.
[+0.51s] WARNING: File '/usr/lib/ayatana-indicators3/7/org.ayatana.indicator.keyboard.so' does not exist.
[+0.51s] WARNING: File '/usr/lib/ayatana-indicators3/7/org.ayatana.indicator.keyboard' does not exist.
[+0.51s] WARNING: File '/usr/lib/ayatana-indicators3/7/liborg.ayatana.indicator.datetime.so' does not exist.
[+0.51s] WARNING: File '/usr/lib/ayatana-indicators3/7/org.ayatana.indicator.datetime.so' does not exist.
[+0.51s] WARNING: File '/usr/lib/ayatana-indicators3/7/org.ayatana.indicator.datetime' does not exist.
[+0.51s] WARNING: File '/usr/lib/ayatana-indicators3/7/liborg.ayatana.indicator.sound.so' does not exist.
[+0.51s] WARNING: File '/usr/lib/ayatana-indicators3/7/org.ayatana.indicator.sound.so' does not exist.
[+0.51s] WARNING: File '/usr/lib/ayatana-indicators3/7/org.ayatana.indicator.sound' does not exist.
[+0.51s] DEBUG: menubar.vala:377: LANG=en_US.UTF-8 LANGUAGE=(null)
[+0.52s] DEBUG: arctica-greeter.vala:225: Invalid session: '(null)'. Using session 'lightdm-xsession' instead.
[+0.52s] DEBUG: user-list.vala:871: Adding user to list. User: Login, background: (null), is_active: false, has_messages: false, session: (null)
[+0.52s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.52s] DEBUG: User /org/freedesktop/Accounts/User1002 added
[+0.52s] DEBUG: User /org/freedesktop/Accounts/User1003 added
[+0.52s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.53s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.53s] DEBUG: user-list.vala:1043: Adding/updating user debian9user (debian9user)
[+0.53s] DEBUG: Loading sessions from org.freedesktop.DisplayManager
[+0.55s] DEBUG: arctica-greeter.vala:225: Invalid session: '(null)'. Using session 'lightdm-xsession' instead.
[+0.55s] DEBUG: user-list.vala:871: Adding user to list. User: debian9user, background: (null), is_active: false, has_messages: false, session: (null)
[+0.55s] DEBUG: user-list.vala:1043: Adding/updating user debianuser ()
[+0.55s] DEBUG: user-list.vala:871: Adding user to list. User: debianuser, background: (null), is_active: false, has_messages: false, session: lightdm-xsession
[+0.55s] DEBUG: user-list.vala:1043: Adding/updating user debianuser2 ()
[+0.55s] DEBUG: user-list.vala:871: Adding user to list. User: debianuser2, background: (null), is_active: false, has_messages: false, session: lightdm-xsession
[+0.55s] DEBUG: user-list.vala:1043: Adding/updating user sshuser ()
[+0.56s] DEBUG: arctica-greeter.vala:225: Invalid session: '(null)'. Using session 'lightdm-xsession' instead.
[+0.56s] DEBUG: user-list.vala:871: Adding user to list. User: sshuser, background: (null), is_active: false, has_messages: false, session: (null)
[+0.56s] DEBUG: user-list.vala:1025: Adding guest account entry
[+0.56s] DEBUG: arctica-greeter.vala:225: Invalid session: '(null)'. Using session 'lightdm-xsession' instead.
[+0.56s] DEBUG: user-list.vala:871: Adding user to list. User: Guest Session, background: (null), is_active: false, has_messages: false, session: (null)
[+0.56s] DEBUG: main-window.vala:245: Monitor 0 is 1024x768 pixels at 0,0
[+0.56s] DEBUG: main-window.vala:271: MainWindow is 1024x768 pixels
[+0.56s] DEBUG: arctica-greeter.vala:860: Showing greeter
[+0.56s] DEBUG: arctica-greeter.vala:302: Showing main window
[+0.58s] DEBUG: Ignoring configuration file /etc/lightdm/lightdm.conf.d/90-arctica-greeter.conf.old, it does not have .conf suffix
[+0.58s] DEBUG: Loaded session /usr/share/xsessions/twm.desktop (TWM, The Tab Window Manager)
[+0.58s] DEBUG: Loaded session /usr/share/xsessions/jwm.desktop (Jwm, Minimalistic pure X11 window manager with menu/tray support)
[+0.58s] DEBUG: Loaded session /usr/share/xsessions/mate.desktop (MATE, This session logs you into MATE)
[+0.58s] DEBUG: Loaded session /usr/share/xsessions/openbox.desktop (Openbox, Log in using the Openbox window manager (without a session manager))
[+0.58s] DEBUG: Loaded session /usr/share/xsessions/plasma.desktop (Plasma, Plasma by KDE)
[+0.58s] DEBUG: Loaded session /usr/share/xsessions/xfce.desktop (Xfce Session, Use this session to run Xfce as your desktop environment)
[+0.58s] DEBUG: Loaded session /usr/share/xsessions/lightdm-xsession.desktop (Default Xsession, )
[+0.58s] DEBUG: arctica-greeter.vala:225: Invalid session: '(null)'. Using session 'lightdm-xsession' instead.
[+0.58s] DEBUG: user-list.vala:871: Adding user to list. User: Login, background: (null), is_active: false, has_messages: false, session: (null)
[+0.58s] DEBUG: Starting authentication for guest account...
[+0.58s] DEBUG: Wrote 12 bytes to daemon
[+0.58s] DEBUG: Read 8 bytes from daemon
[+0.58s] DEBUG: Read 12 bytes from daemon
[+0.58s] DEBUG: Authentication complete for user  with return code 0
Window manager warning: Treating resize request of legacy application 0x40000f (arctica-gr) as a fullscreen request
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x40000f (arctica-gr)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
[+0.60s] DEBUG: Connected to Application Indicator Service.
[+0.60s] DEBUG: background.vala:70: Making background /usr/share/backgrounds/arctica-greeter.png at 1024x768
[+0.61s] DEBUG: menubar.vala:547: Adding indicator object 0x555d776ee5c0 at position 0
[+0.62s] DEBUG: Request current apps
[+0.62s] DEBUG: Building new application entry: :1.77  with icon: nm-device-wired at position 0
[+0.62s] DEBUG: menubar.vala:547: Adding indicator object 0x555d777e9c50 at position 1
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x40000f (arctica-gr)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
[+0.63s] DEBUG: background.vala:570: Regenerating backgrounds
[+0.63s] DEBUG: background.vala:70: Making background #2F70C6 at 1024x768
[+0.63s] DEBUG: background.vala:81: Render of background #2F70C6 complete
[+0.63s] DEBUG: background.vala:70: Making background /usr/share/backgrounds/arctica-greeter.png at 1024x768
[+0.63s] DEBUG: arctica-greeter.vala:285: starting system-ready sound
[+0.70s] DEBUG: background.vala:123: Render of background /usr/share/backgrounds/arctica-greeter.png complete
[+0.73s] DEBUG: background.vala:123: Render of background /usr/share/backgrounds/arctica-greeter.png complete

artica-greeter should use specified background image on the login page

My system is Ubuntu Mate 21.04. I've used dconf-editor to modify setting:

/ org / ArcticaProject / arctica-greeter / background

from the default value "/usr/share/backgrounds/ubuntu-mate-common/Green-Wall-Logo.png" to "/usr/share/backgrounds/cosmos/blue-marble-west.jpg". I ended up doing this both from my user account and from the root account, for reasons I'm about to document.

With this modification in place, if I go to the system menu and select "Lock Screen", then when I exit the lock screen, the correct background image is displayed on the page behind the password dialog box. Good so far.

However, if I log out from my user account, then the login page continues to show the default background. The same happens upon initial system startup. I thought this might be because I had originally modified the background value from my user account. That's why I did it again from the root account. Unfortunately, even after doing so with root, the login page continues to use the default image.

For those who may find this by search, one way around this is to do the following from the root account:

cd /usr/share/backgrounds/ubuntu-mate-common
mv Green-Wall-Logo.png Green-Wall-Logo.bak
ln -s /usr/share/backgrounds/cosmos/blue-marble-west.jpg Green-Wall-Logo.png

In the last statement, substitute your desired background image for /usr/share/backgrounds/cosmos/blue-marble-west.jpg.

Regression: Wrong Greeter size in VirtualBox

After cad5922 was added, the initial size of the Greeter is about 10% of the available screen size. I can nudge it to resize itself by slightly resizing the VirtualBox window.

Arctica Greeter: Current Git version
VirtualBox: 7.0.6

Bug with displaying a list of users

A bug with displaying a list of users when logging into an account and this problem is only for users without a password.

https://ibb.co/whvSKgk

OS: Linux Mint

arctica-greeter Depends on gnome-settings-daemon

The runtime dependency on gnome-settings-daemon should be reflected in debian/control.

consider dropping mate-settings-daemon hard dependency

On systems not running MATE as desktop env the hard-coded dependency on mate-settings-daemon pulls in a huge pile of MATE related packages even if no MATE desktop env gets used on the running system.

We should consider dropping that dependency or making it run-time optional...

LightDM arctica-greeter auto-rotate

When I create file /etc/lightdm/lightdm.conf

[Seat:*]
arctica-greeter-setup-scrit=/home/user/kde-auto-rotate/auto-rotate

LightDM not work!!
How could I setup right way for auto-rotate script on arctica-greeter!?

font-scaling gsettings only supports integer values

Float values get truncated to its integer representativ [like abs() function].

a11y: input fields need username and password labels

Username field and password field need to be labeled with "username" and "password" (above the input field).

after login with incorrect info to remote logon selected box bug

when loggin in with incorrect info to remote logon the remote logon box is no longer selected

Please add a language chooser

Debian Edu tries to provide a desktop environment with multiple language support. Both GNOME and KDE come with an internal language/region chooser. LDM (the LTSP login screen) has a language chooser since years. For Xfce, MATE, LXDE and LXQt a laguage choice doesn't seem to exist. The Lightdm GTK greeter can be configured to show a language chooser, see: https://salsa.debian.org/debian-edu/debian-edu-config/blob/master/share/debian-edu-config/lightdm-gtk-greeter.conf
It would be nice to have such a chooser for the Arctica greeter as well.

The menu bar should use _NET_WM_STRUT_PARTIAL

This would solve popup notifications covering the indicator area.

FTBFS on Debian 11

@tari01 since your latest PR, Arctica Greeter fails to build on Debian 11. It would be nice to have this still supported.

Thanks!

make[1]: Verzeichnis „/home/sunweaver/MyDocuments/4projects/arctica-upstream/arctica-greeter.upstream/arctica-greeter“ wird verlassen
   debian/rules override_dh_auto_build
make[1]: Verzeichnis „/home/sunweaver/MyDocuments/4projects/arctica-upstream/arctica-greeter.upstream/arctica-greeter“ wird betreten
dh_auto_build
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 in use)
	make -j1
make[2]: Verzeichnis „/home/sunweaver/MyDocuments/4projects/arctica-upstream/arctica-greeter.upstream/arctica-greeter“ wird betreten
make  all-recursive
make[3]: Verzeichnis „/home/sunweaver/MyDocuments/4projects/arctica-upstream/arctica-greeter.upstream/arctica-greeter“ wird betreten
Making all in src
make[4]: Verzeichnis „/home/sunweaver/MyDocuments/4projects/arctica-upstream/arctica-greeter.upstream/arctica-greeter/src“ wird betreten
rm -f logo_generator_vala.stamp && echo stamp > logo_generator_vala.stamp-t
/usr/bin/valac -D HAVE_GTK_3_20_0 --debug --pkg posix --pkg gtk+-3.0 --pkg gdk-x11-3.0 --pkg gio-unix-2.0 --pkg x11 --pkg liblightdm-gobject-1 --pkg libcanberra --pkg gio-2.0 --pkg pixman-1 --target-glib 2.32  -C logo-generator.vala
mv -f logo_generator_vala.stamp-t logo_generator_vala.stamp
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/uuid -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/at-spi-2.0 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/lightdm-gobject-1 -pthread -I/usr/include/libxml2 -D_REENTRANT  -w -DGETTEXT_PACKAGE=\"arctica-greeter\" -DLOCALEDIR=\"/usr/share/locale\" -DVERSION=\"0.99.3.0\" -DPKGDATADIR=\"/usr/share/arctica-greeter\" -DPKGLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu/arctica-greeter\" -DINDICATORDIR=\"/usr/lib/x86_64-linux-gnu/ayatana-indicators3/7/\" -g -O2 -ffile-prefix-map=/home/sunweaver/MyDocuments/4projects/arctica-upstream/arctica-greeter.upstream/arctica-greeter=. -fstack-protector-strong -Wformat -Werror=format-security -c -o logo_generator-logo-generator.o `test -f 'logo-generator.c' || echo './'`logo-generator.c
gcc -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/uuid -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/at-spi-2.0 -I/usr/include/libayatana-ido3-0.4 -I/usr/include/libayatana-indicator3-0.4 -I/usr/include/lightdm-gobject-1 -pthread -I/usr/include/libxml2 -D_REENTRANT  -w -DGETTEXT_PACKAGE=\"arctica-greeter\" -DLOCALEDIR=\"/usr/share/locale\" -DVERSION=\"0.99.3.0\" -DPKGDATADIR=\"/usr/share/arctica-greeter\" -DPKGLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu/arctica-greeter\" -DINDICATORDIR=\"/usr/lib/x86_64-linux-gnu/ayatana-indicators3/7/\" -g -O2 -ffile-prefix-map=/home/sunweaver/MyDocuments/4projects/arctica-upstream/arctica-greeter.upstream/arctica-greeter=. -fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro -Wl,--as-needed -o logo-generator logo_generator-logo-generator.o -L/usr/lib/x86_64-linux-gnu -layatana-indicator3 -layatana-ido3-0.4 -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -llightdm-gobject-1 -lcairo -lfreetype -lcanberra -lpixman-1 -lX11 -lXext  -lm 
rm -f arctica_greeter_vala.stamp && echo stamp > arctica_greeter_vala.stamp-t
/usr/bin/valac -D HAVE_GTK_3_20_0 --debug --pkg posix --pkg gtk+-3.0 --pkg gdk-x11-3.0 --pkg gio-unix-2.0 --pkg x11 --pkg liblightdm-gobject-1 --pkg libcanberra --pkg gio-2.0 --pkg pixman-1 --target-glib 2.32  -C config.vapi fixes.vapi indicator.vapi pam_freerdp2.vapi pam_x2go.vapi xsync.vapi animate-timer.vala background.vala cached-image.vala cairo-utils.vala email-autocompleter.vala dash-box.vala dash-button.vala dash-entry.vala fadable.vala fadable-box.vala fading-label.vala flat-button.vala greeter-list.vala idle-monitor.vala list-stack.vala main-window.vala menu.vala menubar.vala prompt-box.vala session-list.vala remote-logon-service.vala settings.vala settings-daemon.vala shutdown-dialog.vala toggle-box.vala arctica-greeter.vala user-list.vala user-prompt-box.vala util.vala ../config.h
warning: C header and source files are ignored when -C or --ccode is set
settings.vala:86.25-86.43: warning: `GLib.Settings.list_keys' has been deprecated since 2.46
idle-monitor.vala:86.23-86.36: error: The name `get_xdisplay' does not exist in the context of `Gdk.Display?' (gdk-3.0)
            display = d.get_xdisplay ();
                      ^^^^^^^^^^^^^^
shutdown-dialog.vala:610.13-610.28: warning: `Gtk.Widget.override_color' has been deprecated since 3.16
shutdown-dialog.vala:611.13-611.28: warning: `Gtk.Widget.override_color' has been deprecated since 3.16
shutdown-dialog.vala:612.13-612.28: warning: `Gtk.Widget.override_color' has been deprecated since 3.16
prompt-box.vala:256.25-256.37: warning: `Gtk.Alignment' has been deprecated since 3.14
prompt-box.vala:256.13-256.17: warning: `Gtk.Alignment' has been deprecated since 3.14
prompt-box.vala:340.9-340.39: warning: `Gtk.Widget.override_color' has been deprecated since 3.16
prompt-box.vala:351.25-351.37: warning: `Gtk.Alignment' has been deprecated since 3.14
prompt-box.vala:351.13-351.17: warning: `Gtk.Alignment' has been deprecated since 3.14
prompt-box.vala:598.13-598.43: warning: `Gtk.Widget.override_background_color' has been deprecated since 3.16
prompt-box.vala:600.9-600.28: warning: `Gtk.Widget.override_color' has been deprecated since 3.16
main-window.vala:53.9-53.33: warning: `Gtk.Widget.override_background_color' has been deprecated since 3.16
main-window.vala:67.29-67.41: warning: `Gtk.Alignment' has been deprecated since 3.14
main-window.vala:67.13-67.21: warning: `Gtk.Alignment' has been deprecated since 3.14
main-window.vala:111.25-111.37: warning: `Gtk.Alignment' has been deprecated since 3.14
main-window.vala:111.13-111.17: warning: `Gtk.Alignment' has been deprecated since 3.14
main-window.vala:146.21-146.33: warning: `Gtk.Alignment' has been deprecated since 3.14
Compilation failed: 1 error(s), 18 warning(s)
make[4]: *** [Makefile:1215: arctica_greeter_vala.stamp] Fehler 1
make[4]: Verzeichnis „/home/sunweaver/MyDocuments/4projects/arctica-upstream/arctica-greeter.upstream/arctica-greeter/src“ wird verlassen
make[3]: *** [Makefile:521: all-recursive] Fehler 1
make[3]: Verzeichnis „/home/sunweaver/MyDocuments/4projects/arctica-upstream/arctica-greeter.upstream/arctica-greeter“ wird verlassen
make[2]: *** [Makefile:392: all] Fehler 2
make[2]: Verzeichnis „/home/sunweaver/MyDocuments/4projects/arctica-upstream/arctica-greeter.upstream/arctica-greeter“ wird verlassen
dh_auto_build: error: make -j1 returned exit code 2
make[1]: *** [debian/rules:34: override_dh_auto_build] Fehler 25
make[1]: Verzeichnis „/home/sunweaver/MyDocuments/4projects/arctica-upstream/arctica-greeter.upstream/arctica-greeter“ wird verlassen
make: *** [debian/rules:13: build] Fehler 2
dpkg-buildpackage: Fehler: Unterprozess debian/rules build lieferte Exitstatus 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui failed

a11y: username field let's screen reader ask for "Enter password for <username>"

When entering username in Arctica Greeter while the screen reader is enabled, the screen reader reads:

Enter password for 'Login' - text.

It should read:

Enter username. - text

Autologin doesn't work on ubuntu 20.04

I configured /etc/lightdm/lightdm.conf.d/90-arctica-greeter.conf:

# don neither show a username / password login prompt for local login
greeter-show-manual-login=false

but I still get asked for credentials on login

GLib.Environment.set_variable() has no effect after GLib.OptionContext.parse()

From #83:

While working on font-scaling support and fixing HiDPI support, I discovered, that GLib.Environment.set_variable() does not take effect after OptionContext.parse() has been called. (For whatever unknown reason...).

To mitigate this, let's move all env variable setups to the code portion above the c.parse() call.

While the PR works around the issue for the NM applet, code in src/menubar.vala still sets a set of environment variables and is certainly created after the program arguments have been processed.

While the environment variable changes might not be that critical any longer since we stopped spawning indicators via systemd and switched to spawning them as subprocesses of the greeter, and the dbus activation environment may likewise not be needed any longer, they probably still need data such as the unique dbus name.

This is probably something that should be dbused debugged and fixed in the long run.

Unable to turn on or off the orca screenreader on arctica-greeter lightdm greeter using <alt>+<super>+<s>

Bug originally reported in Launchpad, for the "arctica-greeter package" present in Ubuntu MATE 20.10 and 21.04, by Ubuntu MATE's Team Member N0rbert, on 9th April 2021 (2021-04-09). Yesterday (15th October 2022), I ("ricmarques" = "Ricardo Dias Marques") have checked that this bug is still present / still happens in Ubuntu MATE 22.04.1 LTS ("Jammy Jellyfish") which uses "arctica-greeter" ("LightDM Arctica Greeter") version "0.99.1.5-2nmu3":

Bug #1923253 “Unable to turn on or off the orca screenreader on arctica-greeter lightdm greeter using <alt>+<super>+<s>” : Bugs : arctica-greeter package : Ubuntu
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1923253

Also yesterday (15th October 2022), I've added a comment - https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1923253/comments/5 - in that bug, with the following text:

This problem is also happening in my laptop computer running Ubuntu MATE 22.04.1 LTS ("Jammy Jellyfish"): when I'm in the login screen, if I press the "Alt + Windows key + S" key combination, the (Orca) Screen Reader does NOT start. The screen reader only starts if I go to the accessibility icon menu at the top of the screen and then click on the "Screen Reader" option. After I log in, the "Alt + Windows key + S" key combination works correctly in Ubuntu MATE to turn on and off the Orca screen reader.

This bug is being discussed, for instance, in the following Discussion in the "Ubuntu MATE Community" Discussion Forum:

CRITICAL! Still unable to startup orca at the login screen - Support & Help Requests - Ubuntu MATE Community
https://ubuntu-mate.community/t/critical-still-unable-to-startup-orca-at-the-login-screen/25938

No "Remote logon" box on startup.

When I start into Arctica-greeter, I don't get the Remote login box. I have to wait until i get an Internet connection, and then click on the Ubuntu icon to change desktop and go back.

Add gsettings option for alpha value to use for blending in the 'logo'

By default, the logo image is blended in with 0.5 alpha. This breaks things, if the logo bg color needs to exactly match the background image.

We should have a configuration paramter in the schema, to adapt this.

Are configuration files supported?

Traditionally, configuration of display managers and greeters happened by configuration files in /etc.
For example, slick-greeter supports /etc/lightdm/slick-greeter.conf.

I tried creating /etc/lightdm/arctica-greeter.conf with the following content, but it was ignored:

[Greeter]
group-filter=ltspdm

The only working alternative I found was to use gsettings, but:

• /usr/share/glib/schemas requires running glib-compile-schemas, and
• /etc/dconf/db/ requires running dconf update

Is there any way to customize arctica-greeter with plain configuration files without running external programs?
E.g. chrooting to a rootfs of different architecture to run glib-compile-schemas isn't always feasible...

Is it possible to build the greeter without support for remote session?

I would like to replace in the Slint distribution that I maintain the gtk lightdm greeter by the Arctica greeter.

However the target users barely need a remote graphical login, and not providing it would minimize the dependencies, especially those pulled by libpam-freerdp2.

Login dialog: usability bad when hinting to a soon expiring password

Whenever PAM notifies a user about a soon expiring password, the UI fails badly in being intuitive and users wonder what to do.

What happens is:

Login: ...
Password: ...

Then...

Log In

(Nothing else).

You can then use enter to proceed with login. No button offerered ("Continue login...") or the possibility to change the password.

This needs more love!

shutdown dialog's box size

@Ionic: Thanks for the shutdown dialog timeout feature. Very cool!

I have one follow up request.

The appearing and disappearing of the shutdown timeout has the side effect of resizing the shutdown dialog.

Steps to reproduce:

variant 1:

• press the computers shutdown button
• hit ESC, the shutdown dialog shrinks by one text line

variant 2:

• go to the session indicator in Arctica Greeter
• select Restart (or Reboot), "Neustarten" in German
• shutdown dialog appears, then the timeout text appears a little later
• on appearance of the timeout text, the shutdown dialog enlarges by one text line

It would be ideal, to have a shutdown dialog box size that stays the same. On box creation there should be space reserved for the time out message already. When escaping the timeout, the box should stay of the same size as with timeout message.

Please put this to your list with prio, so we can release Arctica Greeter soon. (Before the built-in a11y indicator removal).

Add badge for IceWM

If IceWM is installed, no badge is offered. Create the IceWM.png badge to solve this.

packages not found

No package 'libayatana-ido3-0.4' found
No package 'ayatana-indicator3-0.4' found

I have those installed in /usr/lib/ as indicator3 and ido3. Is it looking for a lib file with libayatana et al

Remote-Logon-Service (bug)

Category
Failed to login through Remote-logon.

Priority
Major : not functioning and is essential to be fixed, since this is the main step for using ArcticaGreeter.

Title
It is not possible to obtain a successful login on the Remote-login in the current version, which makes it impossible to reach the session login.

Steps to repair the bug
Downgrade the program one version, to get a successful access to the Remote-login, then it will be necessary to use the following version of Remote-logon-service:
ArcticaProject/remote-logon-service@71e55e0

Expected behavior
On startup the PC should show Arctica Greeter as the start window, the Greeter will ask for a username and password which will lead the user to another set of logins with the field’s x2go-session, username and password. If everything is successful the user should get access to the remote desktop.

Actual behavior
After the startup the user is only able to see the Greeter with the Remote logon including the field’s username and password. Typing the username and password will give the user a small period of waiting time, until the user will get a timeout/an answer "wrong password or email". This results that the user cannot chose his/her session from the broker.