After upgrading from feisty last night, I'm having this problem now. Perhaps adobe has released a new version.
I think there are two bugs here that aren't being clearly addressed:
1) when the package gets installed and fails, the package management infrastructure should detect that condition and set the package state to broken.
2) when the package gets installed and fails, browser configuration should be fixed so that browsers don't hang.
After upgrading from feisty last night, I'm having this problem now. Perhaps adobe has released a new version.
I think there are two bugs here that aren't being clearly addressed:
1) when the package gets installed and fails, the package management infrastructure should detect that condition and set the package state to broken.
2) when the package gets installed and fails, browser configuration should be fixed so that browsers don't hang.