Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Lomiri: Read alarm volume/vibration enabled state settings from GSettings #103

Open
JamiKettunen opened this issue Jan 26, 2023 · 0 comments
Open

Lomiri: Read alarm volume/vibration enabled state settings from GSettings #103

JamiKettunen opened this issue Jan 26, 2023 · 0 comments

Comments

@JamiKettunen
Copy link

These preferences are already set by the Clock app but are tracked completely separately also here which it sets by a D-Bus call; this indicator should just reuse the GSettings values upon the summoning of an alarm.

Currently this has resulted in a mismatch of the state machines between this indicator and clock app due to the D-Bus communication being blocked by AppArmor: https://gitlab.com/ubports/development/apps/lomiri-clock-app/-/issues/180.
@tari01 tari01 mentioned this issue Feb 4, 2023
Closed
tari01 added a commit to tari01/ayatana-indicator-datetime that referenced this issue Feb 12, 2023
@tari01
Do not export/test alarm properties on D-Bus
84d5e75 
This commit should resolve the alarm volume/vibration issue reported in Lomiri:
https://gitlab.com/ubports/development/apps/lomiri-clock-app/-/issues/180
and upstream:
AyatanaIndicators#103
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Do not export alarm properties on D-Bus tari01/ayatana-indicator-datetime
1 participant
@JamiKettunen