Yes, the problem did occur during removal and I was only able to enter the mysql password once. At the time, it was unclear whether dpkg was asking for the mysql bacula user password or the mysql admin password. I incorrectly assumed it was asking for the mysql bacula password, when instead it actually wanted the mysql admin password. There was no way I could see of going back and re-entering the password.
I removed all of the bacula packages and re-installed just the bacula client package. Everything is working fine now.
I guess the problem wasn't actually with bacula, but more so with dpkg not allowing me to re-enter the incorrect password and also not being specific enough about which mysql user it wanted a password for.
Thanks for your quick response time with this issue. Should I open up a new bug for dpkg and transfer this description there?
Yes, the problem did occur during removal and I was only able to enter the mysql password once. At the time, it was unclear whether dpkg was asking for the mysql bacula user password or the mysql admin password. I incorrectly assumed it was asking for the mysql bacula password, when instead it actually wanted the mysql admin password. There was no way I could see of going back and re-entering the password.
I removed all of the bacula packages and re-installed just the bacula client package. Everything is working fine now.
I guess the problem wasn't actually with bacula, but more so with dpkg not allowing me to re-enter the incorrect password and also not being specific enough about which mysql user it wanted a password for.
Thanks for your quick response time with this issue. Should I open up a new bug for dpkg and transfer this description there?