We are closing this bug report because it has not been updated for some
time. Please reopen it if you have more information to submit, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the
It has not been updated because Ubuntu are just ignoring it. What is
the point of bug reports if you are going to do nothing for over a year
and then just close them?
--
_cache-open() failed, please report.
https://bugs.launchpad.net/bugs/320222
You received this bug notification because you
After today's update synaptics stopped woking with the same message.
Running sudo dpkg --configure -a doesn't help.
--
_cache-open() failed, please report.
https://bugs.launchpad.net/bugs/320222
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Nikita, your problem is bug #324252.
This issue is that a problem occurs (it is irrelevant how), and that the
packaging system knows the exact command to fix it, but instead of
fixing it just gives up and gives a gibberish dialog to the user.
--
_cache-open() failed, please report.
Roger that =)
--
_cache-open() failed, please report.
https://bugs.launchpad.net/bugs/320222
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hello!
Thank you for taking the time to report this issue and helping to make
Ubuntu better!
This problem doesn't directly belong to update-manager, but it seems to
be a more general dpkg issue. I've found a comment in bug #323894 posted
by Michael Vogt who wrote that such a kind of problems can
I can't confirm that since instead I had to talk her through running
terminal, sudo and the dpkg command over the phone which did fix it.
In any event bug #323894 is all about dpkg --configure -a not working.
It did work just fine.
My complaint is about the message appearing in the first place
Roger Binns wrote:
My complaint is about the message appearing in the first place and why
the whole package/update system doesn't just self heal instead of
spitting out a message that only the geekiest can understand.
I understand your complaint. I think that this issue doesn't belong to
