Tristan Maat

I get this consistently when using the snooze feature on alarms. ``` java.lang.RuntimeException: Unable to start receiver me.jfenn.alarmio.receivers.TimerReceiver: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at android.app.ActivityThread.handleReceiver(ActivityThread.java:3426) at android.app.ActivityThread.access$1200(ActivityThread.java:200) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1667) at...

I'm still continuously running into this. The issue occurs every second or third time a particular alarm rings. Here's my exact scenario: 1. Wipe the full app storage because I've...

Forgot to check for other PRs before firing that off, but I think that #29 basically covers 99% of the cases in which I'd need to turn off the `fill-column`...

Argh, sorry I missed that issue, I swear I searched around before raising this :| I'll keep it open for now, just in case this gets some traction at least:...

I'm also seeing this, and have been roughly since I started using lineage OS. Any way we can help debug?

How would this look? I believe most home-manager modules are implemented in home-manager itself, rather than downstream. A flakes implementation would probably need to output something like a `homeManagerModule`, but...

I think the issue opened by @berbiche answers my question then :) I agree on `$HOME/.ssh/id_rsa` (with a configuration option), since this is a home configuration after all, those should...

Hmm, upon closer inspection it appears that this happens if no system locale is set. The "workaround" is setting the system locale (`localectl` is your friend), but it would probably...

@lots0logs I don't think I agree with that assessment - it's a perfectly valid state for the system not to have a default language set - LightDM decided to signify...

A workaround for now is to manually check against the user list, which isn't too bad, I suppose (does screw with my architecture though, grr).