Skip to main content


it's odilia, the odilia screenreader! finally, the long awaited by some, version 0.1.0 is out, it has been for afew hours now, but as they say, the news are only old if you heard them at least once, so for most people they should be fresh. If you want to check it out, feel free to do so, dropping bug reports as you find them, never hesitate to pop things in that issue tracker, or come talk to us in our matrix space, #odilia:stealthy.club, or irc, #odilia:libera.chat, #odilia-oftopic:libera.chat and #odilia-dev:libera.chat
the releace announcement can be found at https://odilia.app/news/release_0-1-0/
finally, we're here! A big thank you to the community who waited patiently for this release, as well as everyone who contributed, in one way or another, to the project's growth, we're here, we hear you, and we'll never forget our community! let's show the world it can indeed be done, make linux great again!
#accessibility #screenreader #screenreaders #blind #linux #odilia

reshared this

in reply to bgt lover

I installed from the AUR and got this, when I tried to launch it:

thread ‘main’ panicked at ‘Unable to copy default config file.: Os { code: 2, kind: NotFound, message: No such file or directory” }’, , odilia/src/state.rs:62:18
in reply to Billy

Lol... That moment when you think in markdown but type in bb code. Please ignore the code and /code bits.
in reply to Billy

run install_configs.sh script which comes with odilia, as root. If that script isn't there, well, open an issue, something must have been lost in transit, as they say.
in reply to bgt lover

It looks like the packager for Arch did not include install_configs.sh. I wonder if it should be ran during the install process, or maybe placed in /usr/share/odilia for the user to run after installation. I'm guessing that since it needs to be ran as root, it could be ran during the installatioin process, but I'm not sure how fakeroot would handle it, because it needs to create in pkgdir/wherever.
in reply to Billy

can you open an issue for that? I'll write on the matrix as well, but it's better to have bugs, especially UX ones, documented in issues where we can see them. I'm thinking of a system where odilia doesn't need any config file to be present when it starts, since if it's not, it'll just create one in $XDG_CONFIG_HOME/odilia/config, with default values and all that. However, I'm not sure if we need that, because you get this stuff once. Till the issue is fixed, clone the repo and run script
in reply to bgt lover

I sure can, but since this is an Arch specific packaging bug, should I comment on the package, or do you want me to comment on Odilia itself. If on Odilia, should I ask for config to be generated if it doesn't exist with default values?
in reply to Billy

you can comment on the package what pertains to the package if you want, since the maintainer of the AUR package, tate, is a member of the odilia org as well, so it's maintained by us as well. About automatic generating of config files, sure, that goes on the odilia issue tracker. Or, if you feel like doing that, you can also put both in the same issue on the repo, it'll arrive to us anyhow.
in reply to bgt lover

Ok, I'm heading over to file a bug now. One of them is fixed, before I even go there lol. The AUR package now puts the config in /etc, so don't have to worry about that one.
in reply to Billy

that's probably because I wrote on matrix and the packager saw it. Also, the packager is a developer, so yeah, that fixed itself soon enough. In any case, we're already at 0.1.4, with stuff being fixed. Still, if you want more imediate answers than this thread, I recommend you join us, maybe your bug has already been reported, or you could tell us in more detail what happened and we could do a kind of live debugging session. But sure, open an issue first, at least we know where to start
in reply to bgt lover

The issue is open. Basically, it requires both the system wide and lofcal config file to launch. If I remove the local file, it fails to start.
in reply to bgt lover

Couldn't you just impl Default for your config struct and write that out to the config path if it isn't found?