Repository navigation
Conversation
…t survive Omarchy's Secret-portal migration
Omarchy's migration 1788261467 ("Expose GNOME Keyring to sandboxed apps
through the Secret portal") writes ~/.config/xdg-desktop-portal/
hyprland-portals.conf with default=hyprland;gtk and the Secret line.
xdg-desktop-portal takes the user's file first, so after that migration
the phone's picks in /etc/xdg/xdg-desktop-portal/hyprland-portals.conf
(FileChooser=gnome;gtk, Access=omamobile;gtk) no longer applied: file
dialogs were GTK 3's desktop chooser again. It needs 623 px; on the
Pixel 9a's 405 px Hyprland squeezed its buffer to the screen, text drawn
tall and narrow (WhatsApp web app, Attach > Photos & videos).
omamobile-setup-user now adds, at each login, every line of the /etc file
whose interface the user's file doesn't name yet, under a comment, and
restarts xdg-desktop-portal only when it added one. No user file: nothing
is made. A line the user set (FileChooser=gtk) stays. Every login, not
once, since the migration can arrive with any later update.
test/setup-user.sh: Omarchy's file, two logins: both lines added once,
Secret kept, one portal restart; a user's own FileChooser line kept; no
file made where there was none.
On a Pixel 9a (omamobile-shell 0.2.127, omarchy-settings 4.5.0-3): with
Omarchy's file in place a portal OpenFile opened xdg-desktop-portal-gtk;
after the new step the file gained the two lines and the same call
opened Nautilus (org.gnome.Nautilus), full screen; WhatsApp's Attach >
Photos & videos picked a file through it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you for this, and for tracking it down to the migration rather than to the chooser. I checked it against Omarchy 4.5.0-3's own packages: the migration writes exactly the file you describe, and The change reads well: only the interfaces the user's file doesn't name, the user's own line kept, nothing created where there is no file, the portal restarted only when something was added, and a test that checks each of those. I ran the new step on its own against a few files in a scratch folder and it behaved as described, including a file without a final newline. A few small things, none of them blocking, if you'd like to take them in the same push:
On the version: #555 also uses 0.2.128, as you noted. I'll set the number when I merge, so please leave it as it is. Before merging I'll run it on my Pixel 7 Pro: read the user's portal file, install this build, log in again, and open a file chooser and a permission request. I'll report here. |
…ys suspend is verified (#737) * omamobile-shell 0.2.129: auto-sleep on by default where the device says suspend is verified omamobile-sleepd (s2idle 30 s after the screen goes off behind a secure lock) shipped off on every phone. On the Pixel 7 Pro it is now verified: a night asleep with about 22 h of standby, power off, and double tap waking the phone from sleep (SUSPEND-PLAN, 2026-11-13). Turn the toggle on once, at login, on a phone whose device package installs /usr/share/omamobile/auto-sleep-default; every other phone keeps it off, and a user who turns it off keeps it off. With the modem up the phone still doesn't sleep (its inhibitor stays until linux-omarchy-mobile#232). 0.2.128 is claimed by #555 and #727. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * omamobile-shell: the default-off test allows only the device-gated auto-sleep step The package test refused any code that turns the omamobile-sleep toggle on. #737 adds exactly one such step, gated on the device package's auto-sleep-default. The test now allows that one line and checks that the gate sits right above it; anything else that turns the toggle on still fails. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Omarchy's migration
1788261467.sh("Expose GNOME Keyring to sandboxed apps through the Secret portal", omarchy-settings 4.5) writes~/.config/xdg-desktop-portal/hyprland-portals.confcontainingdefault=hyprland;gtkand the Secret line. xdg-desktop-portal reads the user's file first, so after that migration the phone's picks in/etc/xdg/xdg-desktop-portal/hyprland-portals.confstop applying:FileChooser=gnome;gtk: file dialogs are GTK 3's desktop chooser again. It needs 623 px, and the Pixel 9a has 405 px, so Hyprland squeezes its buffer to fit the screen and the text is drawn tall and narrow.Access=omamobile;gtk: the permission question goes back to GTK's dialog.Here it showed up in the WhatsApp web app, under Attach › Photos & videos. On this phone the migration ran with
omamobile-updateon 2026-11-12.Change: at each login,
omamobile-setup-usercopies every line from the/etcfile whose interface the user's file doesn't name yet. The added lines go under a comment. xdg-desktop-portal is restarted only when a line was added.FileChooser=gtk) is kept.Tests:
test/setup-user.shpasses on the phone. The new case starts from Omarchy's file and runs two logins. It checks that both lines are added once, that the Secret line stays, and that the portal restarts once. It also checks that a user's ownFileChooserline is kept and that no file is created where there was none. I haven't runtest/all.On a Pixel 9a (omamobile-shell 0.2.127, omarchy-settings 4.5.0-3):
OpenFilecall openedxdg-desktop-portal-gtk.org.gnome.Nautilus) full screen.The version is 0.2.128, which #555 also uses. Renumber as needed.
Found with an AI assistant (Claude), tested on my phone.
🤖 Generated with Claude Code