You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use Granite.Widgets.TimePicker in my flatpaked app and noticed it does not follow the clock-format setting (12h or 24h) chosen in the host system.
Looks like TimePicker checks the clock-format using Granite.DateTime.is_clock_format_12h () which uses GSettings key org.gnome.desktop.interface.clock-format. However, since GSettings in flatpak apps is sandboxed this returns the value from the sandbox―not from the host.
Expected Behavior
Granite.DateTime.is_clock_format_12h () should always return the host clock-format setting.
Steps to Reproduce
Choose 12h as a clock-format in Date & Time Plug
Open Terminal
Run gsettings get org.gnome.desktop.interface clock-format. You should get '12h'
Run some app in Flatpak, e.g. flatpak run --command=sh io.elementary.screenshot
Run gsettings get org.gnome.desktop.interface clock-format in the sandboxed prompt. You should get '24h' regardless of the host's clock-format setting
What Happened
I use
Granite.Widgets.TimePicker
in my flatpaked app and noticed it does not follow the clock-format setting (12h or 24h) chosen in the host system.Looks like TimePicker checks the clock-format using
Granite.DateTime.is_clock_format_12h ()
which uses GSettings keyorg.gnome.desktop.interface.clock-format
. However, since GSettings in flatpak apps is sandboxed this returns the value from the sandbox―not from the host.Expected Behavior
Granite.DateTime.is_clock_format_12h ()
should always return the host clock-format setting.Steps to Reproduce
gsettings get org.gnome.desktop.interface clock-format
. You should get'12h'
flatpak run --command=sh io.elementary.screenshot
gsettings get org.gnome.desktop.interface clock-format
in the sandboxed prompt. You should get'24h'
regardless of the host's clock-format settingLogs
N/A
Platform Information
6.1.0+r2071+pkg119~ubuntu6.1
1.10.2~ubuntu6.1
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: