apt-get install -f / clean / update
does not resolve the issue. That is, I do those steps as recommended
and yet I get the same error at the next auto-install of linux-image-... .
There seems to be some chronic problem causing this at each update.
The update process generates a bug report each ti
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1477785
Title:
package linux-image-3.13.0-58-generic 3.13.0-58.97 failed to
insta
Public bug reported:
This is happening with each new auto-update of linux-image-... .
I've followed the instructions given in response to previous
bug reports I submitted when this happened; that is, I do
sudo apt-get install -f; sudo apt-get clean; sudo apt-get update
and the same problem happen
As the reporter, I'm not in a position to mark this as confirmed--no?
I did apt-get {install -f , clean , update } as suggested and the same type
of error occurred on a subsequent update today, as reported at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479158
--
You received this bug
Public bug reported:
Similar to what happened recently as reported at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477785
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-59-generic (not installed)
ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt2
Public bug reported:
Ubuntu's automated software update hit upon this bug.
I don't have further info but please email me if there are any questions I can
answer.
Tom Ace tom...@gmail.com
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-58-generic 3.
In the attached testcase (evinceligbug.pdf), the ligature comes from an
alternate font as code 0x56, ASCII 'V'. Whether or not the ligature is
blank on highlighting or shows V depends on whether V is present in the
subsetted font that the rest of the word uses. One could argue that
showing V is a
Public bug reported:
Evince renders a PDF document containing ff ligatures (taken from a different
font than the surrounding text comes from) correctly upon first opening the
file, but fails to render an ff ligature when the word containing it is
highlighted with the cursor. I am attaching a t
