So I was upgrading my machine a few days ago after neglecting dist-upgrades for a while and realized that there was a new release out, 13.04 to be exact. I was running on Lubuntu 12.04 and enjoying it, but I was willing to take the plunge. My first mistake was I had left my system set for long term releases, so when I ranSetting up blueman (1.23-1) ... reload: Unknown instance: invoke-rc.d: initscript dbus, action "reload" failed. dpkg: error processing blueman (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: blueman
$ sudo do-release-upgrademy response was simply
Checking for a new ubuntu release
No new release found
after checking my /etc/update-manager/release-upgrades and finding that it had Prompt=lts all I had to do was change Prompt=lts to Prompt=normal and all was well.For awhile.
During my update, I may or may not have pressed "ctrl-c" to break out of what I thought was a text editor, but was really something else that sent my break command to my release upgrade in progress. I had to reboot to come back to life. When I did, I was thankfully greeted with a login prompt, but no networking. I followed the commands from the previous post to get back on my feet, and then ran into this new issue. Upgrade crashes on blueman. So I run
$ sudo apt-get remove bluemanand
$ sudo dpkg --configure -a
$ sudo apt-get install -f
until I have everything installed and configured besides blueman and lubuntu-desktop . From here I was racking my head for days, until I came upon a nice little IRC log here. I had been going through the bug logs here and found the same error earlier, but nothing new. The IRC log recommended quite a few options, but the only one that did anything for me (and the only one I even tried for that matter) was
$ sudo service dbus restartand then it worked like a charm! Whoever it was in that IRC chat, thanks!