| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
The preferred-session gsetting shall provide an ordered list of preferred
sessions for detecing the default session type.
|
| |
|
|
|
|
|
|
|
|
|
| |
spawn_async them directly.
This assures DBUS_SESSION_BUS_ADDRESS being shared between
greeter and indicators, so DBus session bus operation work
out-of-the-box (which is not the case when launching indicators
via systemd).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
3a5ca24831d1b4a74af6cfd5c5cc2a42b5787aeb backported a commit calculating
the really needed screen size more correctly as a prerequisite for
additional multi-display support (span and zoom modes) from Slick
Greeter (5d39cade1f70ffe0a9bc38ad0b405bb55d98a505), but unfortunately
missed crucial code in src/arctica-greeter.vala.
While the realize call on main_window should be harmless, calling
setup_window on it actually leads to the main window resizing to the
actual size that was queried via GDK.
While setup_window is being called as part of the main window creation,
the first call just skips resizing it (for some reason). Subsequent
calls, which are *mostly* triggered through changes in the actual
display configuration (hardware or software), then have main window
recalculate its size (and updating the background).
Honestly, we could just rip out the whole do_resize logic and always
resize, since with these changes, we're forcing a resize on startup
anyway. Not doing so leads to the nasty bug this commit fixes.
However, to keep Slick Greeter's and our code more in sync (to make
future backporting easier), let's keep it like this for now.
Fixes: https://github.com/ArcticaProject/arctica-greeter/issues/47
|
| |
|
|
|
|
| |
Relying on LightDM's signals is not enough - we do not get the guest user.
|
|
|
|
| |
keyboard indicator
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This commit removes invocation of MATE's window manager marco, that was introduced with 9b3526d12d9d6c828fbd4a29dec2295ae2f735a5
Having marco launched allows any user to use its keybindings to open applications which could bypass arctica-greeter and access the operating system as the "lightdm" user.
|
| |
|
| |
|
|
|
|
| |
'--test-bigfont' (soon to come feature).
|
|
|
|
| |
mode. Allows one to run arctica-greeter in test-mode within a Lomiri session.
|
|
|
|
| |
ArcticaGreeter behave well, when interacting with Lomiri Shell.
|
|
|
|
| |
Session. We use the com.lomiri.Shell interface to communite between session indicator and Arctica Greeter.
|
| |
|
|
|
|
| |
'session' in ArcticaGreeter's get_default_session().
|
|
|
|
| |
default_session_hint(). No direct access to LightDM's version of it.
|
|
|
|
| |
into non-static methods.
|
|
|
|
| |
LightDMs default if absolutely necessary.
|
| |
|
| |
|
|
|
|
| |
(if installed).
|
|
|
|
| |
This makes slick-greeter properly remember the last wayland session instead of defaulting to an xsession.
|
|
|
|
| |
is located below the constructor() method.
|
|
|
|
| |
ArcticaGreeter's contructor into separate ArcticaGreeter.go() method.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
32d28d7bf2646fc7a0008937034246fcc96dbc8a broke test mode by changing the
ArcticaGreeter class to a proper SingleInstance vala class. While meant
well, this created deadlocks, especially when using test mode, since
other code being called from the ArcticaGreeter constructor tries to
acquire references to ArcticaGreeter, which is still locked at that
point in time.
Fortunately, GObject has the constructed () function, that is almost
never used within vala, but still works and is called after the
constructor () (or, in vala parlance, construct), so we can move calling
functions that might require a constructed ArcticaGreeter to constructed
().
Fixes: https://github.com/ArcticaProject/arctica-greeter/issues/42
|
|
|
|
| |
arctica-greeter-enable-tap-to-click.
|
|
|
|
|
|
| |
Ported from Slick Greeter by Mike Gabriel.
https://github.com/linuxmint/slick-greeter/commit/85f83be9977faf2482d38d2cc289f0542b1c06a4
|
|
|
|
|
|
|
|
| |
The gtk and icon themes already work this way.
Ported from Slick Greeter by Mike Gabriel.
https://github.com/linuxmint/slick-greeter/commit/97f9f54b686303dec81918d3056194bff2a3163c
|
|
|
|
| |
parsed (so we know if we are in test-mode or not).
|
|
|
|
|
|
|
|
|
| |
This is a work-in-progress.
The reworked high contrast mode adds support for a configurable high
contrast GTK theme and changes a lot of widgets to change their color.
The big font mode is a stub currently.
|
|
|
|
|
| |
This allows us to drop the rather awkward self-referencing static
singleton member and use a standard vala/glib feature.
|
|
|
|
|
|
|
| |
This way, we will be able to use it everywhere, as long as we hold a
reference in the main greeter object.
We will extend this class with other properties later on.
|
|
|
|
| |
Signed-off-by: Elyes HAOUAS <ehaouas@noos.fr>
|
|
|
|
| |
than fullscreen(). With fullscreen() Arctica Greeter's main window gets only shown on the primary monitor and one cannot let the login box follow the pointing device to the active monitor anymore.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Protect memory from being paged to disk, as we deal with passwords
According to systemd-dev,
"mlockall() is generally a bad idea and certainly has no place in a graphical program.
A program like this uses lots of memory and it is crucial that this memory can be paged
out to relieve memory pressure."
With systemd version 239 the ulimit for RLIMIT_MEMLOCK was set to 16 MiB
and therefore the mlockall call would fail. This is lucky becasue the subsequent mmap would not fail.
With systemd version 240 the RLIMIT_MEMLOCK is now set to 64 MiB
and now the mlockall no longer fails. However, it not possible to mmap in all
the memory and because that would still exceed the MEMLOCK limit.
"
See https://bugzilla.redhat.com/show_bug.cgi?id=1662857 &
https://github.com/CanonicalLtd/lightdm/issues/55
RLIMIT_MEMLOCK = 64 MiB means, arctica-greeter will most likely fail with 64 bit and
will always fail on 32 bit systems.
Hence we better disable it.
Ported from Unity Greeter / Slick Greeter.
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1815493
https://github.com/linuxmint/slick-greeter/pull/127
|
|
|
|
| |
Vala API version << 0.40. (Fixes FTBFS on Debian 9).
|
| |
|
|
|
|
| |
Greeter. Makes handling windows opened via some of the indicators much more organic.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Inspired by these slick-greeter commits:
commit ffd43c4d425e70bc003b490dcddb8fbae1fffea7
Author: Clement Lefebvre <clement.lefebvre@linuxmint.com>
Date: Sat Apr 8 14:13:23 2017 +0100
HiDPI: Allow to force HiDPI support ON or OFF
commit 809f1b30a321ae12fdd3ba154791f9ead291acc7
Author: Clement Lefebvre <clement.lefebvre@linuxmint.com>
Date: Fri Apr 7 23:04:50 2017 +0100
HiDPI: Take the screen size in consideration
HiDPI shouldn't be activated on large screens where the dpi is OK.
commit 851fca4e5508471d6f388edcd0327c3fc5b2b12f
Author: Clement Lefebvre <clement.lefebvre@linuxmint.com>
Date: Fri Apr 7 18:43:42 2017 +0100
Add HiDPI support
Only support 1x and 2x scale ratios for now.
Also add a setting so the user can disable HiDPI support.
|
|
|
|
|
|
|
| |
on exit, so the user session components won't fail to connect.
Based on fix for lightdm-gtk-greeter see:
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On non Debian/Ubuntu systems, the /etc/default/keyboard path does not exist.
To prevent expensive Python startup (and hundreds/thousands of stats +
follow-up loads) we'll reduce to an initial early stat, i.e. if the
non-standard file exists only then will we exectute the helper stub.
This is most useful on systems that employ systemd for the X11 keyboard
configuration (`00-keyboard.conf` from systemd-localed) so that the X server
already has the correct layout upon starting up. This approach also avoids
unnecessary xkbcomp calls forcing recompilation of non-cached assets.
Signed-off-by: Ikey Doherty <ikey@solus-project.com>
|
| |
|