Note also that I reported one other problem - that when samba asked me to confirm whether to keep my own smb.conf file, I chose the option to run a shell, and the update manager seemed to block, and no shell window that I could see was available to do my own diffs (note that a request for a side-by-side diff just resulted in a plain diff), and with the update-manager blocked, I had to find the bash that seemed relevant and kill it. When I did, update-manager came back to life and reported that the samba post install shell script had exited unexpectedly, but strangely, it also reported about 8 other packages failed, from winbind to wine to ubuntu-desktop (see the attached VarLogDistupgradeMainlog).
Oh, and while worried that the above failure meant that the upgrade was broken, I tried running a second one, but it couldn't acquire the lock. I plan to run it again when the dead-looking "Distribution Upgrade" window terminates.
Wish me luck.
Note also that I reported one other problem - that when samba asked me to confirm whether to keep my own smb.conf file, I chose the option to run a shell, and the update manager seemed to block, and no shell window that I could see was available to do my own diffs (note that a request for a side-by-side diff just resulted in a plain diff), and with the update-manager blocked, I had to find the bash that seemed relevant and kill it. When I did, update-manager came back to life and reported that the samba post install shell script had exited unexpectedly, but strangely, it also reported about 8 other packages failed, from winbind to wine to ubuntu-desktop (see the attached VarLogDistupgra deMainlog) .
Oh, and while worried that the above failure meant that the upgrade was broken, I tried running a second one, but it couldn't acquire the lock. I plan to run it again when the dead-looking "Distribution Upgrade" window terminates.
Wish me luck.