Preface
Ticking the ”Launch on System Startup” box in the desktop client’s General settings tab (correctly) adds a .desktop
file under ~/.config/autostart/
, with the following Exec
line:
Exec="/usr/bin/nextcloud" --background
Expected behaviour
The effect of --background
should be mentioned in options.rst (and the resulting online documentation).
Actual behaviour
The --background
parameter is undocumented.
Client configuration
Client version: 3.2.1
Operating system: Ubuntu 20.04
OS language: English
Client package: 3.2.1-20210429.171749.5901a0f98-1.0~focal1
Is there any way to combine the two-step method into one pipe? To output the raw bitstream to stdout, and remux from stdin?
Summary
After setting up multi-factor authentication, losing the authentication code-generating device means losing access to the Mattermost account. While having MFA is excellent, I’m afraid to set it up for my admin user account (which is the one most critically needing it), because there’s no recovery mechanism in case I lose my authenticator device.
Steps to reproduce
- Enable up multi-factor authentication in the System Console
- Configure 2FA with an authenticator app on your phone
- Break/lose/have your phone stolen
- Try to log in
Expected behavior
Have a ”use a backup code instead” link next to the MFA token prompt.
Observed behavior (that appears unintentional)
There’s no alternative way to provide the MFA. You can not log in.
Possible fixes
None available AFAICT. There’s no way to add security keys as alternatives either.
There’s an existing Jira ticket ticket about this (and it’s linked to an abandoned PR), but it’s closed as ”moved to ProductBoard for prioritization”, and I don’t know what’s happened since then, as I don’t have access to ProductBoard (that I know of).
Mattermost version
v5.34.2
My go-to way of quickly parsing arguments is as follows:
#!/bin/bash
quiet="true"
files=()
for arg in "${@}"; do
case "${arg}" in
"-v" | "--verbose")
quiet="false"
;;
*)
files+=(
"${arg}"
)
;;
esac
done
Beautysh (v6.1.0) incorrectly reports this as indent/outdent mismatch and instead indents it like so:
#!/bin/bash
quiet="true"
files=()
for arg in "${@}"; do
case "${arg}" in
"-v" | "--verbose")
quiet="false"
;;
*)
files+=(
"${arg}"
)
;;
esac
done
The deciding factor seems to be the multi-line parenthesis in assigning files
. If I assign it all on one line, like this:
files+=("${arg}")
then beautysh is satisfied with the indentation (i.e. doesn’t change it or report a mismatch).
Dressman ei siis kävele vielä tarpeeksi hitaasti?
Se oli kyllä ankea ja pimeä paikka. Minä onnekseni pääsin päiväksi kouluun, vaikka suretti sinut sinne ankeuteen jättää.
Oliko niillä televisio? Olisin väittänyt, että ainut viihdyke siellä oli joku vanha aikakauslehti. Vaikkei 80-luvulla kyllä televisiostakaan päivisin mitään katseltavaa tullut.
@kaupunkilinnut GPS-sijainti näköjään hieman epätarkka: tämä oli tuon kl-väylän toisella puolella kuin mihin iPhone otoksen sijoitti, ja sillä puolella on (kesällä) Googlen katunäkymässä tämän näköistä. Väylän toisella puolella on kyllä omakotiasutusta, mutta ei siis aivan ikkunoiden vierestä löytynyt tämä.
There seem to be a few other similar typos across different files. Should I combine them into this request, or would you prefer individual pull requests for each?
Steps to reproduce
media.autoplay.default
to1
(”Block Audio”, which is the default)media.autoplay.blocking_policy
to2
What I expect to happen
For the audio to be unmuted.
What happens instead
The audio remains muted, and the volume control/indicator remains in the muted position.
I’m unmotivated to report this to Twitch, as I’m unsure about the precise meaning of
media.autoplay.blocking_policy
, and I currently don’t use the non-working value for it myself. Feel free to downprioritize this as you see fit, unless the original reporter is still affected. Here’s my downstream report over at Launchpad though, just for reference. (I’ll update it too.)