Dave Mielke <[email protected]> wrote: > Maybe it had to do with whatever problem dropped your system into emergency > mode. > > Another possibility is that the volumes are usually initially mounted > read-only in emergency mode. It should work but maybe something new is > getting in the way.
That's possible. I'm not sure what it would be or how to trace it out, because I did not have any eyeballs around to read the screen. The problem volumes were storage volumes and not the main / device. > >I could not even start it manually by typing brltty at (what I assumed) was > >the command prompt. > > What error message(s) did you get? I'm not sure, because as stated above I did not have eyes to read it. I'm just curious to wonder if anything changed in brltty's execution/startup that would make it unable to start in such a circumstance. _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.app/mailman/listinfo/brltty
