Oliver Kennedy

> > bash -o pipefail -c '{ /srv/rhasspy/bin/rhasspy-voltron -p de 2>&1 | cat >&2 3>&-; } 3>&1' > > Wohoo that's some bash dark magic there :D > > Thanks...

I'm getting the same thing. The problem appears to be a flatpak sandboxing issue: ``` Traceback (most recent call last): File "/app/share/siglo/siglo/window.py", line 214, in on_watches_listbox_row_activated subprocess.Popen(["systemctl", "--user", "start", "siglo"])...

Thanks for having a look @seratch I'm not sure this will help, but in case anyone comes across this issue in the future, here's a workaround: - https://github.com/VizierDB/vizier-scala/blob/master/src/main/scala/info/vizierdb/catalog/workarounds/SQLiteNoReadOnlyDriver.scala The main...

Thanks! A virtual table would be sufficient for my purposes as well. It seems like the jdbc driver can make use of vtables, but only those defined by an extension.

I'm having a comparable issue on Linux/ARM.

It looks like the default launcher link has a corrupt jar embedded in it. Fortunately install still works and `cs` comes under multiple names, so the following workaround worked for...

For what it's worth, my current workaround has been to use Zathara, which supports synctex natively rather than via dbus daemon.

It's possible it's a different issue. I can confirm that the symptom is there: The project compiles correctly under mill 0.11.1, but not under .2 I can come up with...

https://github.com/okennedy/mill_jai_repro ``` okennedy  athena  ~  Desktop  JaiTest  main  $  mill version [build.sc] [41/49] compile [info] compiling 1 Scala source to /home/okennedy/Desktop/JaiTest/out/mill-build/compile.dest/classes ... [info]...

No effect: ``` okennedy  athena  ~  Desktop  mill_jai_repro  main  $  coursier uninstall mill Uninstalled mill okennedy  athena  ~  Desktop ...