The problem was that timidity was stopping at K99timidity after
K25hwclock.sh, and holding the rtc device open so hwclock couldn’t
access it. After purging and reinstalling timidity, timidity now stops
at K01timidity, so I’m not sure how that happened. Anyway, closing
this.
** Changed in: util-linux (Ubuntu)
Status: New => Invalid
--
hwclock reports “Cannot access the Hardware Clock via any known method”
https://bugs.launchpad.net/bugs/126893
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
