Skip to main content

Troubleshooting

Notifications are not appearing​

  1. Confirm the background service is running:
muslimtify daemon status

If it is not registered, run muslimtify daemon install.

  1. On Linux, verify that desktop notifications work at all:
notify-send "Test" "Hello"

If nothing shows, the issue is with your desktop notification daemon, not Muslimtify.

  1. On Windows, local system settings can block toast delivery. Check your notification settings, Focus Assist / Do Not Disturb, and make sure the command is running in an interactive desktop session.

  2. Send a notification through Muslimtify itself, without waiting for the next prayer:

muslimtify notification test           # the notification for the next prayer
muslimtify notification test --adhan   # the same, with its adhan

If notify-send works but this does not, check that the prayer is enabled with muslimtify notification. If this works but real prayers never notify, the daemon is the problem, see The daemon is not running.

The adhan will not stop playing​

muslimtify notification --adhan stop

On Windows the notification also has a Stop button. To stop an adhan from playing in future, disable it for that prayer with muslimtify notification --adhan disable <prayer>, or turn sound off entirely with muslimtify notification --sound off.

A notification did not fire while the machine was busy or asleep​

Muslimtify catches up on triggers it missed. If a check cycle runs late, any trigger scheduled within the previous 15 minutes still fires. Anything older than that is dropped without firing, so resuming from a long suspend does not replay a stack of stale Adhans hours after the fact.

If notifications are missing well inside that window, the daemon is most likely not running at all. Check with muslimtify daemon status.

Location detection is not working​

  • Run the automatic detection again:
muslimtify location set --auto
  • Set your coordinates manually if auto-detection keeps failing:
muslimtify location set --lat=<latitude> --long=<longitude>
  • If the host machine is in a different region than the coordinates, override the timezone:
muslimtify location set --lat=-6.21 --long=106.84 --timezone=Asia/Jakarta
  • Auto-detection relies on network access to ipinfo.io. Check that this host is reachable if detection fails.

GPS will not turn on​

muslimtify location gps on probes the receiver before saving the setting, so it refuses rather than enabling something that cannot work. The message tells you which part is missing.

MessageFix
GPS: cannot reach gpsd.Install gpsd and start it. Muslimtify reads it over a local socket on 127.0.0.1:2947
GPS: no GPS device detected.gpsd is running but sees no hardware. Connect the receiver and confirm gpsd has picked it up
GPS: location access is turned off.On Windows, enable Settings > Privacy & security > Location, then try again
GPS not available in this build.This binary has no GPS client for the platform it is running on

If it reports that GPS is enabled but no fix is available yet, that is not an error. The setting is saved and ipinfo.io is used until the receiver locks on.

To check the current state at any time:

muslimtify location gps    # prints "GPS is enabled" or "GPS is disabled"
muslimtify location        # the gps field appears alongside your coordinates

GPS turned itself off​

If the GPS daemon or device stops being reachable after you enabled it, Muslimtify warns once and clears the setting so it does not retry on every cycle. Restore the receiver, then run muslimtify location gps on again.

A denied permission is treated differently and does not disable GPS, because granting access in Settings is enough to make the next attempt succeed on its own.

Muslimtify rejects my timezone​

Error: Unknown timezone 'Asia/Jakartaa'

The name has to resolve on this system. Check the spelling against the IANA database, for example Asia/Jakarta, Europe/London, or America/New_York. Zones that legitimately sit at UTC+0, such as Africa/Abidjan, are accepted.

Prayer times are off by an hour​

This is almost always daylight saving. Muslimtify derives the UTC offset from your IANA timezone for the date being calculated, so DST transitions are handled for you, but only when a valid zone name is saved.

Check what is stored:

muslimtify location

The gmt field shows the offset in effect today, not the one recorded when you last set your location. If timezone is empty or wrong, set it explicitly:

muslimtify location set --timezone=Europe/London

Prayer times show --:--​

A time of --:-- means there is no valid time to show. There are two causes.

The saved location is invalid. Muslimtify also prints a warning on stderr, once per run:

Warning: invalid location in config (latitude nan, longitude 106.845600), prayer times unavailable. Run: muslimtify location set --lat=<latitude> --long=<longitude>

This happens when config.json holds a latitude outside -90 to 90, a longitude outside -180 to 180, or a value that is not a number, usually after editing the file by hand. Muslimtify deliberately shows no times rather than times calculated for the wrong place. Fix the location with the command in the warning, or with muslimtify location set --auto. If auto-detection is enabled, the daemon repairs it on its own the next time it detects your location. The warning and self-repair are available from v0.4.3.

The prayer does not occur that day. At high latitudes the sun can fail to reach the position a prayer is defined by for part of the year, so some prayers, most often Fajr and Isha, have no time at all on those days. Only those prayers show --:--, with no warning, and they do not notify.

My script or status bar shows extra lines after upgrading​

Since v0.4.2 every prayer output carries its date. show --headless and show --next --headless begin with a date= line, a prayer that falls on another day adds a <prayer>_offset= line, and show --json wraps the prayers as {"date": ..., "prayers": {...}}. A script that treats every key=value line as a prayer will show date as an extra row.

Skip the keys that are not prayer names:

while IFS='=' read -r key val; do
    case "$key" in
        ""|date|remaining|*_offset) continue ;;
    esac
    echo "$key at $val"
done < <(muslimtify show --headless)

From v0.4.3, times can also read 05:52 PM if the 12-hour clock is enabled with muslimtify timeformat 12. See Output formats for every shape.

show --date rejects my dates​

Two limits apply. Years must be between 1 and 9999, and a range may span at most 366 days. A range longer than that is refused before any output is printed. Split it into smaller spans:

muslimtify show --date 2026-01-01 2026-12-31    # 365 days, accepted

I moved, but my location did not update​

An auto-detected location is re-checked in the background every 12 hours by default, so it can take up to that long to catch up after you travel. To update it right away:

muslimtify location set --auto

To make the automatic re-check more frequent, lower the interval (the minimum is 3600, one hour):

muslimtify location set --refresh-interval=3600

If your location never updates on its own, check muslimtify location: a refresh_interval of disabled turns automatic re-checks off, and coordinates set manually with --lat / --long are never re-checked at all. See Location auto-refresh.

The daemon is not running​

  • Check its status:
muslimtify daemon status
  • Re-register the service:
muslimtify daemon install
  • On Linux, the daemon runs under systemd. Confirm your session has an active user systemd instance if the service refuses to start.

Resetting your configuration​

Delete config.json to return to defaults. Muslimtify recreates it with built-in defaults the next time you change a setting.

PlatformConfig path
Linux~/.config/muslimtify/config.json
Windows%APPDATA%\muslimtify\config.json

Still stuck?​