| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001_desktop-dm-lomiri-session-Drop-old-wizard-has-run-ch.patch | [PATCH] desktop/dm-lomiri-session: Drop old wizard-has-run check looking at the wrong location anyway. | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2023-02-13 | ||
| 0002_lomiri-session-Put-evaluation-of-ps-call-in-quotes.patch | [PATCH] lomiri-session: Put evaluation of ps call in quotes. Resolves this bash error (parts of the error translated from German): ``` 2023-02-13T08:57:38.592437+01:00 lomiri lomiri-session[4644]: /usr/bin/lomiri-session: Zeile 102: [: !=: Unitary operator expected. 2023-02-13T08:57:38.592886+01:00 lomiri lomiri-session[4644]: /usr/bin/lomiri-session: Zeile 106: kill: (4734) - No such process ``` |
Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2023-02-13 | ||
| 0003_lomiri-session-Properly-differentiate-between-Ubuntu.patch | [PATCH] lomiri-session: Properly differentiate between Ubuntu Touch session and Lomiri Desktop session. | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2023-02-13 | ||
| 0004_lomiri-session-Check-for-presence-of-Xwayland-use-th.patch | [PATCH] lomiri-session: Check for presence of Xwayland, use that check directly, don't use extra variable NO_X11 for it. | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2023-02-13 | ||
| 0005_systemd-lomiri.service-Drop-Before-and-Wants-for-ind.patch | [PATCH] systemd/lomiri.service: Drop Before= and Wants= for indicators.target. | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2023-02-14 | ||
| 0010-src-modules-QtMir-Application-application_manager.cp.patch | [PATCH] src/modules/QtMir/Application/application_manager.cpp: Use LOMIRI_MIR_EMITS_SIGSTOP rather than UNITY_MIR_EMITS_SIGSTOP. | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2024-02-03 | ||
| 0012-systemd-user-start-lal-application-end.target-on-sto.patch | [PATCH 2/9] systemd-user: start lal-application-end.target on stop/restart We have a problem that SIGSTOP'ed apps don't get the memo when Lomiri stops for any reason, causing the apps (and subsequently the LAL units) to linger around, confusing LAL and causing those apps to not be launch-able again. Together with [1], make sure those apps are ended when Lomiri ends through the use of lal-application-end.target. This restores the functionality in the Upstart unit file. |
Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2024-02-04 | ||
| 0013-lomiri-session-Drop-the-Xwayland-start-logic-and-lea.patch | [PATCH 3/9] lomiri-session: Drop the Xwayland start logic and leave it to lomiri/qtmir itself. | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2024-02-04 | ||
| 0014-systemd-user-set-SyslogIdentifier.patch | [PATCH 4/9] systemd-user: set SyslogIdentifier Due to our use of a wrapper, the identifier in jjournal/syslog is not pretty. So, let's set it to something that make more sense. See https://gitlab.com/ubports/development/core/lomiri/-/commit/6dae64656377647076e64dbc669159c59c240b04 |
Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2024-02-04 | ||
| 0015-lomiri-session-systemd-lomiri.service-Use-the-LOMIRI.patch | [PATCH 5/9] {lomiri-session,systemd/lomiri.service}: Use the LOMIRI_AS_SYSTEMD_UNIT way to launch the session. See: https://gitlab.com/ubports/development/core/lomiri/-/commit/b28f767a429cd3be52ff2bb07e882bf641567aa8 and: https://gitlab.com/ubports/development/core/lomiri/-/commit/1b6164636d23026173654d539a297a76128de143 |
Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2024-02-04 | ||
| 0016-systemd-lomiri.service-Allow-sd_notify-calls-to-be-a.patch | [PATCH 6/9] systemd/lomiri.service: Allow sd_notify calls to be accepted by the NOTIFY_SOCKET. As the lomiri.service launches the lomiri-session wrapper script, but the sd_notify call comes from its subproces lomiri, it will get rejected if we don't explicitly allow the complete cgroup to send service status updates via sd_notify(). |
Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2024-02-04 | ||
| 0017-lomiri-systemd-wrapper-change-env-var-for-specifying.patch | [PATCH 7/9] lomiri-systemd-wrapper: change env var for specifying 1-time binary Because Systemd doesn't have a way to specify an environment variable specific to a unit & a run, we need to use something that isn't too generic. See: https://gitlab.com/ubports/development/core/lomiri/-/commit/5f158f2ebeafe55ed5ea838d55887ba10771d97b |
Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2024-02-04 | ||
| 0018-lomiri-session-systemd-lomiri.service-Drag-the-lomir.patch | [PATCH 8/9] {lomiri-session,systemd/lomiri.service}: Drag the lomiri process under the umbrella of the wrapper script. This allows us to drop NotifyAccess=all from the lomiri.service file again. |
Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2024-02-04 | ||
| 0019-lomiri-session-Don-t-hide-Lomiri-s-exit-code-from-sy.patch | [PATCH 9/9] lomiri-session: Don't hide Lomiri's exit code from systemd. | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | 2024-02-04 | ||
| 0020_lomiri-keyboard-service.patch | Provide a Lomiri Keyboard wrapper using maliit-keyboard. | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | |||
| 0021_lomiri-requires-lomiri-keyboard.patch | Require lomiri-keyboard.service, launch it with lomiri.service even if not enabled by default. | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no | |||
| 1001_use-qt-quick-style-suru.patch | no | |||||
| 1002_no-lomiri-restart-on-failure.patch | Don't restart lomiri session on failure. | Mike Gabriel <mike.gabriel@das-netzwerkteam.de> | no |