about summary refs log tree commit diff
path: root/pkgs/desktops/lomiri
AgeCommit message (Collapse)AuthorFilesLines
2024-06-16Merge pull request #317000 from OPNA2608/fix/lomiri-QT_QPA_PLATFORMTHEME-issueCosima Neidahl2-0/+35
lomiri.lomiri-session: Unset QT_QPA_PLATFORMTHEME
2024-06-12lomiri.qtmir: nixfmt-rfc-styleOPNA26081-35/+34
2024-06-12lomiri.qtmir: 0.7.2-unstable-2024-01-08 -> 0.8.0-unstable-2024-03-06, switch ↵OPNA26081-8/+8
to debian-upstream branch
2024-06-09treewide: Remove indefinite article from meta.descriptionAlexis Hildebrandt2-2/+2
nix run nixpkgs#silver-searcher -- -G '\.nix$' -0l 'description.*"[Aa]n?' pkgs \ | xargs -0 nix run nixpkgs#gnused -- -i '' -Ee 's/(description.*")[Aa]n? (.)/\1\U\2/'
2024-06-09mir_2_15: init at 2.15.0OPNA26082-4/+4
2024-06-07Merge pull request #316275 from OPNA2608/fix/lomiri-xkb-layoutCosima Neidahl2-0/+30
lomiri.lomiri: Try to consider services.xserver.xkb.layout
2024-06-07Merge pull request #316255 from OPNA2608/fix/content-hub-exchangesCosima Neidahl3-23/+87
lomiri.{lomiri-app-launch,content-hub}: Fix issues with peer spawning & data transfer
2024-06-07tests/lomiri-filemanager-app: initOPNA26081-0/+2
2024-06-07lomiri.lomiri-filemanager-app: init at 1.0.4OPNA26082-0/+141
2024-06-04treewide: remove unused fetchpatch argumentsSigmanificient2-3/+0
2024-06-03lomiri.lomiri-session: Unset QT_QPA_PLATFORMTHEMEOPNA26082-0/+35
Workaround startup failure when Pantheon module sets it to "gtk3" globally.
2024-06-01lomiri.lomiri: Try to consider services.xserver.xkb.layoutOPNA26082-0/+30
Propagate the configuration setting through an envvar, check the envvar in the compositor. Needed because querying AccountsSettings for this information fails, due to Ubuntu-only "InputSources" interface. So you're stuck on US layout without this hack.
2024-05-31lomiri.content-hub: Modernise abitOPNA26081-17/+12
- Some patches have been merged, fetch merged ones if possible & update comments - with lib; in meta is frowned-upon
2024-05-31lomiri.content-hub: Fetch patch to fix data transferOPNA26081-0/+7
We don't have a functional content-hub transfer test, so this slipped through the cracks during testing. (The background setting in LSS would be an easy one, but that calls an AccountsSetting function that doesn't exist outside of Ubuntu, so it wouldn't work anyway.)
2024-05-31lomiri.lomiri-app-launch: Modernise abitOPNA26081-8/+8
- Patch has been merged, fetch merged one & update comment (hash is unchanged, checked) - We now have a CMake modern enough for pkg_get_variable DEFINE_VARIABLES, use it - substituteInPlace --replace is deprecated - with lib; in meta is frowned-upon
2024-05-31lomiri.lomiri-app-launch: Inject /run/current-system/sw/bin into PATHOPNA26082-0/+62
LAL manages desktop file parsing for various parts of the Lomiri environment. It also handles turning them into SystemD services tracked in the background. And due to how things work one, it's code is also SystemD-launched by itself. When we package applications with desktop files, we don't want the Exec values to be absolute, so we patch out absolute paths. Without absolute paths, PATH is expected to have the path to the executables. But our PATHs don't always contain i.e. /run/current-system/sw/bin. Services launched by SystemD are one such instance. If LAL code is run under SystemD's restricted reduced PATH, then it fails to find the requested executables. This is what happens to content-hub, and it causes all transfer requests to be met with an immediate "could not launch peer"-like error, and a transfer being stuck halfway. To work around this (I wouldn't call this a real solution?), patch LAL code to: - also propagate whatever PATH it currently *does* have to its launched applications - postfix the PATH it has with /run/current-system/sw/bin, to give it a decent fallback These changes allow for lomiri-filemanager-app to be launched via a content-hub request from lomiri-system-settings (i.e. the background selection).
2024-05-27lomiri.lomiri-indicator-network: Disable testsOPNA26081-1/+2
Needs a GLib change to be fixed, which needs a staging cycle, which I was told won't happen in time anymore. Seems like only the tests fail though.
2024-05-27lomiri.telephony-service: Mark broken & exclude everywhereOPNA26082-1/+3
Needs a GLib change to be fixed, which needs a staging cycle, which I was told won't happen in time anymore. Luckily it's not a crucial component for the desktop mode.
2024-04-29Merge master into staging-nextgithub-actions[bot]3-70/+29
2024-04-29Merge pull request #304798 from OPNA2608/update/lomiri/stuffCosima Neidahl3-70/+29
Update ayatana datetime & some OTA-less Lomiri things
2024-04-27treewide: wrapGAppsHook → wrapGAppsHook3Jan Tojnar5-9/+9
This was achieved using the following command: sd 'wrapGAppsHook\b' wrapGAppsHook3 (rg -l 'wrapGAppsHook\b') And then manually reverted the following changes: - alias in top-level.nix - function name in wrap-gapps-hook.sh - comment in postFixup of at-spi2-core - comment in gtk4 - comment in preFixup of 1password-gui/linux.nix - comment in postFixup of qgis/unwrapped-ltr.nix and qgis/unwrapped.nix - comment in postFixup of telegram-desktop - comment in postFixup of fwupd - buildCommand of mongodb-compass - postFixup of xflux-gui - comment in a patch in kdePackages.kde-gtk-config and plasma5Packages.kde-gtk-config - description of programs.sway.wrapperFeatures.gtk NixOS option (manual rebuild)
2024-04-17lomiri.lomiri-indicator-network: Update patching to newer CMake's possibilitiesOPNA26081-4/+3
We can just define variables for pkg-config substitution now, no need to hardcode.
2024-04-17lomiri.lomiri-system-settings-unwrapped: 1.0.2 -> 1.1.0OPNA26081-29/+7
2024-04-17lomiri.lomiri-ui-toolkit: 1.3.5012 -> 1.3.5100OPNA26082-41/+22
2024-04-14lomiri.telephony-service: Fix indicatorOPNA26081-0/+4
2024-04-14lomiri.libusermetrics: Add custom patch for launching systemd serviceOPNA26082-0/+26
The UserMetrics service expects AppArmor to be available, and its database access breaks when that's not the case. Details: https://gitlab.com/ubports/development/core/libusermetrics/-/issues/8 We need to set an envvar for it to work AppArmor-less, but that requires system config knowledge. Solve this by telling the D-Bus service to look for & launch a systemd service, which we will later create in the Lomiri module.
2024-04-14lomiri.lomiri-system-settings: Patch language plugin's locale lookup pathOPNA26081-0/+5
The only part this really affects for us is Lomiri's First-Time-Launch Wizard, which uses the found & filtered locale identifiers for a language selection & gets stuck unless at least 1 valid language has been found. This makes the wizard process completable, in case we ever re-enable it.
2024-04-14lomiri.content-hub: Move example peers to examples outputOPNA26081-0/+1
2024-04-14lomiri.morph-browser: Patch desktop icon path to be absoluteOPNA26081-3/+12
Because Lomiri App Launch parses it on Lomiri startup, and having a relative Icon entry somehow corrupts the search paths.
2024-04-14nixos/tests/lomiri: initOPNA26082-0/+4
2024-04-14lomiri.lomiri-session: init at 0.2OPNA26082-0/+197
2024-04-14lomiri.lomiri: init at 0.2.1OPNA26083-0/+318
2024-04-12lomiri.u1db-qt: Fix pkg-config fileOPNA26081-5/+20
2024-04-12lomiri.trust-store: Fix references variable in pkg-configOPNA26081-3/+5
2024-04-12lomiri.deviceinfo: Fix references variable in pkg-configOPNA26081-0/+6
2024-04-12lomiri.lomiri-download-manager: Fix lack of output fixup in pkg-config file, ↵OPNA26081-3/+9
update pkg-config call with new CMake option
2024-04-12lomiri.biometryd: Fix lack of output fixup in pkg-config file, update ↵OPNA26081-3/+8
pkg-config call with new CMake option
2024-03-19treewide: add meta.mainProgram to packages with a single binarystuebinm2-0/+2
The nixpkgs-unstable channel's programs.sqlite was used to identify packages producing exactly one binary, and these automatically added to their package definitions wherever possible.
2024-02-27lomiri.suru-icon-theme: add meta.changelogOPNA26081-0/+1
2024-02-27lomiri.suru-icon-theme: 20.05.1 -> 2024.02.1R. Ryantm1-2/+2
2024-02-26Merge pull request #278374 from OPNA2608/init/lomiri/lomiri-system-settingsPeder Bergebakken Sundt5-0/+575
lomiri.lomiri-system-settings{,-unwrapped,-security-privacy}: init at 1.0.2
2024-02-26tests/lomiri-system-settings: initOPNA26081-0/+3
2024-02-26lomiri.lomiri-system-settings: init at 1.0.2OPNA26082-0/+68
2024-02-26lomiri.lomiri-system-settings-security-privacy: init at 1.0.2OPNA26082-0/+90
2024-02-26lomiri.lomiri-system-settings-unwrapped: init at 1.0.2OPNA26083-0/+414
2024-02-23Merge branch 'master' into staging-nextWeijia Wang2-0/+140
2024-02-22lomiri-thumbnailer: Add patch to support gtest 1.13+ (forces build with C++14)Simon Hollingshead1-0/+5
From gtest 1.13, C++14 is required. Upstream hardcodes C++11 for its builds.
2024-02-22tests/morph-browser: Add standalone (non-Lomiri) testOPNA26081-1/+5
2024-02-21lomiri.morph-browser: Skip lint testsOPNA26081-4/+3
2024-02-21lomiri.morph-browser: 1.0.3 -> 1.1.0OPNA26081-2/+4