*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
Glad to hear ttf-mscorefonts-installer now installs successfully.
I got the warnings too, they were there before (in addition to the
error). They don't show up every time. This is probably something to
** Description changed:
[Symptoms]
When installing or updating the package ttf-mscorefonts-installer in
Ubuntu 16.04 or 16.10, an error message appears in a GUI window,
indicating "failure to download extra data files" (the fonts themselves)
"after package installation" (the package
On Yakkety? That's weird. What error message does "sudo apt-get install
--reinstall ttf-mscorefonts-installer" return, precisely?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658707
Title:
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
Awesome, thanks for the feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658000
Title:
Package
Wahrscheinlich ein Duplikat von bug 1222654, aber ich bin überrascht,
dass dieser bug Fix Released sagt.
Ralf, kannst du dich Informationen errinern, warum die Installation
scheiterte? Vielleicht etwas, das sie anhaltete?
Bitte auf Englisch antworte, wenn du kannst, so dass andere Leuten
Solch ein Problem hatte ich noch nie gesehen. Ich habe die folgenden
potenziellen Lösungen auf Google gefunden (frag "package is in a very
inconsistent state"). Vom weichsten bis zum härtesten:
1) Sieh mal in /var/lib/update-notifier/package-data-downloads/partial/
wenn es Dateien gibt, die
Probably a duplicate of bug 1222654 but I'm surprised that this bug says
Fix Released.
Ralf, can you remember any information about why the installation failed
in the first place? Something that stopped it perhaps?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I had never seen such an issue. I found the following potential
solutions on Google (look up "package is in a very bad inconsistent
state"). From softest to hardest:
1) Check in /var/lib/update-notifier/package-data-downloads/partial/ if
there are files that look like they were partially
** Description changed:
[Symptoms]
When installing or updating the package ttf-mscorefonts-installer in
Ubuntu 16.04 or 16.10, an error message appears in a GUI window,
indicating "failure to download extra data files" (the fonts themselves)
"after package installation" (the package
This bug has been fixed in apt-transport-https 1.2.19 (xenial) and 1.3.4
(yakkety), released 2017-01-26, by Julian Klode in bug 1651923.
If you are still affected by it, update apt-transport-https to the
appropriate version and reinstall Ubuntu's version of ttf-mscorefonts-
installer. You should
Robin:
Sorry I couldn't reply sooner.
For 16.04, this bug has been fixed in apt-transport-https 1.2.19,
released Jan 26, 2017, so you shouldn't run into it again with the
Ubuntu ttf-mscorefonts-installer 3.4 package, provided you update apt-
transport-https to 1.2.19.
For 14.04, I cannot
** Changed in: msttcorefonts (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656776
Title:
should depend on apt-transport-https (was: fails to download
The fix for this bug has been released to Xenial on Jan 26. Can you try
again? Purge Debian's ttf-mscorefonts-installer 3.6, update apt-
transport-https, install Ubuntu's ttf-mscorefonts-installer 3.4. It
should work now.
** Changed in: msttcorefonts (Ubuntu)
Status: Confirmed =>
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
This is bug 1607535, fixed in package apt-transport-https 1.2.19
(released to Xenial and Yakkety on Jan 26) by Julian Klode in bug
1651923. Update apt-transport-https (and possibly the other apt
packages,
@Alain: not the same bug, you clearly have accepted the EULA already
(it's written in the output). See bug 1649203/comments/13 for your
Content-Range issue. Also make sure that apt-transport-https is 1.2.19
to avoid bug 1607535. Then you can remove Debian's version of ttf-
mscorefonts-installer
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
This is bug 1607535, fixed in package apt-transport-https 1.2.19
(released to Xenial on Jan 26) by Julian Klode in bug 1651923. Update
apt-transport-https (and possibly the other apt packages, for good
Wahrscheinlich war ttf-mscorefonts-installer nicht erfolgreich
installiert. Leider wird eine neue Installation ttf-mscorefonts-
installer wegen bug 1607535 auch scheitern, weil es sieht aus, deine
Version apt < 1.2.19 ist. Versuch mal, ttf-mscorefonts-installer zu
löschen, deine apt Pakete bis
It looks like a previous install of ttf-mscorefonts-installer failed.
But reinstalling it may fail because of bug 1607535, since your version
of apt is apparently < 1.2.19. Try removing it completely, updating apt
packages to 1.2.19, and reinstalling it:
sudo apt-get purge
Not exactly the same error message as in widely-impacting bug 1607535,
but almost, and judging by the attachments to your bug report, your
version of package apt-transport-https is < 1.2.19. Please update this
package (and other apt packages, for good measure) to 1.2.19, and retry
(reinstall
Still affects xorg-lts-trusty (for Precise users)
** Changed in: xorg (Ubuntu)
Status: Triaged => Invalid
** Changed in: xorg-lts-trusty (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
That particular error ("The HTTP server sent an invalid Content-Range
header"), contrary to the previous one ("Protocol "http" not supported
or disabled in libcurl"), has a different cause than
It could be fixed in Ubuntu MATE if they had their own fork of Déjà-Dup,
like they have their own fork of Files, Gedit, Eye of GNOME, Evince,
GNOME Terminal, File Roller.
Another Nautilus fork, Nemo, retained the name Files for its icon in the
menus. Didn't MATE did the same?
I can only suggest
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Did you upgrade apt-transport-https? The fix is in this binary package,
not in the apt binary package (both being compiled from the same source
package named apt, yes it is confusing). See bug 1651923
I have recently encountered that message during the verification step of
a backup. This was extremely disconcerting, as the data being backed up
was user data with adequate permissions.
Déjà Dup should not ask for elevated privileges without explaining why
it needs them, and it probably should
Does it work though? In Caja? Do you get the restore/revert options when
you right-click?
Cause if I understand correctly those are allowed by libdeja-dup.so in
/usr/lib/[x86_64-linux-gnu]/nautilus/extensions-3.0, so perhaps Caja
looks into a different directory (.../caja/extensions-3.0?).
Yes, this is well-known. The Debian and Ubuntu versions of ttf-
mscorefonts installer cannot be compared, with respect to this bug, and
no matter their respective version numbers, because of how differently
they download the fonts. See bug 1607535.
--
You received this bug notification because
Sigh. Your first two downloads worked though, the third one failed. You
should report this on bug 1651923, Julian Klode might be able to help.
The error message you get now, "Protocol http not supported or disabled
in libcurl", is symptomatic of the same bug 1607535/1651923 I suggested
as a
Did you update apt-transport-https to 1.2.19 too? If I understand
correctly the fix is in this binary package. apt is the source package,
compiled into several binary packages: apt, apt-utils, apt-transport-
https, libapt-*, ...
--
You received this bug notification because you are a member of
Thanks for the additional information. Even though normal installs have
the package already, I personally feel that the apt-transport-https
dependency should be added, be it only for consistency's sake. But I am
not the package maintainer and I can't help further, sorry. Perhaps ping
them directly
Thanks for the hard work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651923
Title:
apt https method decodes redirect locations and sends them to the
destination undecoded.
To manage
You're right indeed, your issue is likely different from bug 1607535,
but once you install apt-transport-https you should run into bug
1607535.
That package is normally installed as a Recommends of ubuntu-standard:
did you install your system without Recommends?
Going through the comments of bug
I'm glad we could help!
All the best
Naël
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
Undescriptive duplicity/collection-status error when the backup
directory contains two
More likely to be a manifestation of bug 1607535, fixed in the
development release by bug 1651923.
Please check those bugs, try and install manually with "sudo apt-get
install [--reinstall] ttf-mscorefonts-installer" or "sudo dpkg-
reconfigure ttf-mscorefonts-installer" depending on whether the
The file and function I examined are those mentioned in the traceback
reported by David for Ubuntu 16.04, deja-dup 34.2-0ubuntu1.1, duplicity
0.7.06-2ubuntu2:
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
line 105, in add_filename
(self.volume_name_dict, filename)
downloads.sourceforge.net is just a redirection service to an auto-
selected mirror. Using the full URL
(sourceforge.net/projects/corefonts/files/...) also auto-selects a
mirror (credited on the right of the web page: "Mirror provided by
...").
--
You received this bug notification because you
** Attachment added: "deja-dup.log2"
https://bugs.launchpad.net/deja-dup/+bug/1652410/+attachment/4804856/+files/deja-dup.log2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652410
Title:
I have also replicated the bug, on Ubuntu 14.04 deja-dup 30.0 duplicity
0.6.23 (haven't got a more recent version yet but David has), as a
newly-created user with the default Déjà-Dup settings:
1. Perform the first full backup and check that the backup, the file
signatures, and the manifest file
>> To fix this bug from happening in the future, we could perhaps
>> restrict the file list that is passed from Déjà-Dup to duplicity
>> collection-status? Perhaps to *.{diff,sig}tar.{gz,gpg} and
>> *.manifest files only, or something like that?
> This sounds good to me!
On further
** Summary changed:
- duja-dup AssertionError: ({1: 'duplicity-full.20161129T015237Z.vol1.difftar'}
+ Undescriptive duplicity/collection-status error when the backup directory
contains two volumes with different file names and same volume number in the
same backup set
** Changed in: deja-dup
>> You apparently performed a full backup on 2016-11-29 at 01:52 UTC,
>> did everything work fine during this backup? Was it successful ?
> Don't think so
Don't think so either, because your full backup on that date is only one
volume long and that volume is 120 bytes long:
ls -l
Thanks for the information. First of all, as reported by the log file
you sent and the listing of your backup directory, there is an
uncompressed backup volume in your volume directory, and an uncompressed
file of files signatures, created or last modified on Dec 22:
Also, from the content of your log-file, I've got the impression that
there isn't a single well-formed backup chain in your backup directory.
Can you check with:
ls -l /home/david/Dropbox/Backups
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You apparently performed a full backup on 2016-11-29 at 01:52 UTC, did
everything work fine during this backup? Was it successful ?
When did you run first into this problem - on the first incremental
backup ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The "status" Vej refers to is the bug status, on this web page, to
switch from "incomplete" to "new".
Thanks for the log. Can you please show the content of your cache
directory?
ls -lR ~/.cache/deja-dup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It's because you're using the fish shell instead of the more common bash
shell. If I understand correctly, the fish translation of Vej's command
is:
env DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-
dup.log
or:
set -x DEJA_DUP_DEBUG 1
deja-dup --backup | tail -n 1000 >
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
Duplicate of bug 1607535, that you couldn't find easily because it is
itself the duplicate of a bug in apt that doesn't look related at all on
first sight.
** This bug has been marked a duplicate of bug
As proposed in comments 56 57, I have temporarily removed the duplicate
status of this bug to un-hide it in the package's bug list, in the hope
that people will find it more easily and stop opening new bugs to report
this problem.
I have updated the description with all the findings made about
** Description changed:
- As noted in
-
https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1371783/comments/45,
- the current 3.4 version of ttf-mscorefonts-installer searches for the
- font files in an incorrect network location. The consequence of this is
- that the core fonts are
Robin, comment 63:
> This package comes originally from Debian, where the current
> version is 3.6. That version seems to work without problem,
> no matter how ugly it may be in doing so.
As a matter of fact, even Debian's version 3.4 works. It works because
it uses wget to download the fonts,
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Jeremy, comment 59:
> the next Ubuntu bugfix update for this package (if there is one)
> will be numbered something like 3.4+nmu1ubuntu2.1
It would be 3.4+nmu1ubuntu3 I believe. But there will be no new
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Is there a way to list this bug in the bug list of msttcorefonts without
removing duplicate status, so that people stop reporting this problem as
a new bug? The apt bug this bug is a duplicate of is not
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Duplicate of bug 1607535, whose cause was found in package apt, see bug
1651923.
** This bug has been marked a duplicate of bug 1651923
apt https method decodes redirect locations and sends them to the
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Duplicate of bug 1607535, whose cause was found in package apt, see bug
1651923.
** This bug has been marked a duplicate of bug 1651923
apt https method decodes redirect locations and sends them to the
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Duplicate of bug 1607535, whose cause was found in package apt, see bug
1651923.
** This bug has been marked a duplicate of bug 1651923
apt https method decodes redirect locations and sends them to the
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Removing the "...and should be updated to version 3.6 from Debian" part
of the bug title to reflect that the fix isn't in version 3.6 per se
(but in package apt, as explained in bug 1651923). Version 3.6
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
** Summary changed:
- ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts and
should be updated to version 3.6 from Debian
+ ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
Further investigation indicates that this bug is indeed a duplicate of
bug 1607535, although the error message is different (because the
contacted mirror server is different, see bug 1655431).
The root
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
** This bug is no longer a duplicate of bug 1649203
ttf-mscorefonts-installer always complains about cannot download data
because http is not support by libcurl?
** This bug has been marked a duplicate
*** This bug is a duplicate of bug 1651923 ***
https://bugs.launchpad.net/bugs/1651923
(In the meantime that a fix for bug 1651923 lands in xenial and yakkety,
you can still workaround this issue by installing Debian's 3.6 version
instead, which uses wget instead of apt-helper for downloading
*** This bug is a duplicate of bug 1656102 ***
https://bugs.launchpad.net/bugs/1656102
** This bug is no longer a duplicate of bug 1563840
Please merge msttcorefonts 3.6 (multiverse) from Debian testing (contrib)
** This bug has been marked a duplicate of bug 1656102
Please merge with
*** This bug is a duplicate of bug 1656102 ***
https://bugs.launchpad.net/bugs/1656102
** This bug has been marked a duplicate of bug 1656102
Please merge with Debian's msttcorefonts 3.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> This update request was originally requested in bug 1607535
It was also previously requested in bug 1563840 and bug 1542710. Adding
duplicates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656102
NOT the same error message as in bug 1607535 ("http disabled in libcurl"
vs. "404 not found") BUT a few users have seen this message too in bug
1607535 so both bugs MIGHT have the same cause (SourceForge servers are
unreliable and not adapted to headless downloads).
As with bug 1607535, you might
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
** This bug is no longer a duplicate of bug 1649203
ttf-mscorefonts-installer always complains about cannot download data
because http is not support by libcurl?
** This bug has been marked a duplicate
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
** This bug is no longer a duplicate of bug 1649203
ttf-mscorefonts-installer always complains about cannot download data
because http is not support by libcurl?
** This bug has been marked a duplicate
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
** This bug is no longer a duplicate of bug 1649203
ttf-mscorefonts-installer always complains about cannot download data
because http is not support by libcurl?
** This bug has been marked a duplicate
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
** This bug has been marked a duplicate of bug 1607535
ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts and
should be updated to version 3.6 from Debian
--
You received this bug
*** This bug is a duplicate of bug 1369043 ***
https://bugs.launchpad.net/bugs/1369043
** This bug has been marked a duplicate of bug 1369043
package ttf-mscorefonts-installer 3.4+nmu1ubuntu1 failed to install/upgrade:
subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1369043 ***
https://bugs.launchpad.net/bugs/1369043
** This bug has been marked a duplicate of bug 1369043
package ttf-mscorefonts-installer 3.4+nmu1ubuntu1 failed to install/upgrade:
subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
** This bug has been marked a duplicate of bug 1607535
ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts and
should be updated to version 3.6 from Debian
--
You received this bug
*** This bug is a duplicate of bug 1607535 ***
https://bugs.launchpad.net/bugs/1607535
** This bug has been marked a duplicate of bug 1607535
ttf-mscorefonts-installer 3.4+nmu1ubuntu2 fails to install core fonts and
should be updated to version 3.6 from Debian
--
You received this bug
You shouldn't compare the PPAPI plugin and the NPAPI plugin. They are
not exactly the same. This was obvious in the past when the NPAPI plugin
was frozen at version 11.2, but it is still true now even though both
plugins are version 24.0 (since Dec 13).
In particular, the new 24.0 NPAPI plugin is
Thanks for this log. It shows that your current backup chain started on
Oct 10, contains the offending incremental backup (Dec 19 to Dec 20),
and has later incremental backups (three more on Dec 20, one on Dec 21,
one on Dec 22, one on Dec 30). You can see for yourself under "primary
backup chain"
Flash with Chromium-based browsers is out of my knowledge, sorry.
A quick Google search shows that apparently, at least a few years ago,
Chromium/Chrome used to disable hardware acceleration for certain
graphic cards. Knowing the limited capabilities of the AMD/ATI Radeon HD
6310 (an
Could this be a message from duplicity instead?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600783
Title:
Not translated string
To manage notifications about this bug go to:
To create a new full backup, simply backup to a new location, or move
the files in the current location to some other place. Déjà Dup will
detect the absence of previous backups and start a new full backup.
The backup location is the directory that stores the duplicity files
that Déjà Dup
*** This bug is a duplicate of bug 1632870 ***
https://bugs.launchpad.net/bugs/1632870
pepperflashplugin-nonfree is well-known to be broken since Google
stopped shipping the PPAPI Flash plugin with Chrome 54: see e.g. bug
1632870. The package has not been fixed yet. Besides, if it worked, it
*** This bug is a duplicate of bug 1632870 ***
https://bugs.launchpad.net/bugs/1632870
> cannot stat
> 'unpackchrome/opt/google/chrome/PepperFlash/libpepflashplayer.so': No such
> file
>
> The .deb package no longer contains such file and as a result, the script
> cannot work.
Yes, I contacted Daniel a few weeks ago to let him know about the
Chrome/Flash unbundling and suggest he downloads from Adobe or retires
his PPA. Since there is now a variety of ways to get the NPAPI/PPAPI
Flash plugin, he decided to retire his PPA, and I updated my Flash memo
to stop mentioning
@D. Schuurman:
> Perhaps the "on-demand" installation only checks when new backups are
configured?
Yes, I believe so, it matches my experience. Also, see bugs 1606449 and
1641423. If I understand correctly, it's not duplicity and python-gi
we're supposed to install (by hand or through this
The link you provided (http://askubuntu.com/q/787244/25388) shows you
solved the dependency problem (it's indeed a matter of installing deja-
dup AND deja-dup-backend-gvfs), so I'm closing this bug. See also bugs
1606449 and 1641423 for more about this dependency issue.
The other problem you
Public bug reported:
The i386 version of ubuntu-restricted-addons Recommends adobe-
flashplugin | flashplugin-installer, whereas the amd64 version only
Recommends flashplugin-installer.
It's been years that the adobe-flashplugin package (in partner) work for
both architectures, and it is the
*** This bug is a duplicate of bug 1633678 ***
https://bugs.launchpad.net/bugs/1633678
> As regards having adobe-flashplugin and pepperflashplugin-nonfree
> conflict to each other [...] Since it can't be done easily, I
> guess we have to live with this inconvenience. I've closed the
>
Sorry, didn't see you were using Linux Mint Debian Edition. You can
theoretically use deb-multimedia with this Debian derivative; however,
note that the maintainer of that unofficial package archive doesn't have
to keep his packaging compatible with and similar to that of the
corresponding
I'm pretty sure you shouldn't use the deb-multimedia repository with
Ubuntu or Ubuntu derivatives. It is an unofficial repository of packages
made with Debian in mind and meant to be used with Debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Actually, doesn't affect Linux Mint either. Package libhal1-flash still
suggests, not depends on, flashplugin-installer.
** Changed in: linuxmint
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Doesn't affect Ubuntu. Package libhal1-flash still suggests, not depends
on, flashplugin-nonfree.
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Install in Ubuntu 16.10: error the public key is not available
+ Package is not installable in Ubuntu 16.10 since Google stopped shipping
Flash with Chrome 54 for Linux. Workaround to get Flash in Yandex Browser.
** Description changed:
+ [bug description]
+
+
Glad this solves your problem. I suspected the browser looked in certain
directories, the problem being to find out which ones.
You should report to Yandex support, if you can, that their browser
should also look for the PPAPI Flash plugin in /usr/lib/adobe-
flashplugin/ as it is now its official
I read the ubuntu-devel thread and agree with everything you said.
Thanks for trying to solve that issue at installation level.
As a side note about that thread: AFAIK, flashplugin-installer (NPAPI
11.2, src:flashplugin-nonfree) comes from Debian too, just like
pepperflashplugin-nonfree (PPAPI,
I'm trying to install Yandex Browser to have a look, but I can't find
the specific version you're using (16.10.0.2260 beta 64-bit), only the
current stable (16.10.1.545-1 64-bit). Can you point me to the source
for your version, or perhaps better, update yours to the current stable
which seems to
Gunnar:
>
> As regards dependencies in Ubuntu, I don't think it's
> possible to let a package in universe/multiverse
> recommend or depend on a package in Canonical Partner,
> since the latter is not enabled by default.
I thought so too, but now I'm not sure it's that much of a problem, as
long
Thanks for taking care of this bug Gunnar.
Unfortunately I can't test your packages since I still use Trusty for
the time being. I did at least compare the contents of your Xenial build
against the one available in multiverse and the one in Andrei Alin's
PPA. It looks good to me and should fix
The preferred source for Flash is now adobe-flashplugin from partner,
not pepperflashplugin-nonfree from multiverse. It has been so for all
supported releases of Ubuntu, including Precise, since 2015-05.
https://wiki.ubuntu.com/Chromium/Getting-Flash
** Summary changed:
- Pepper Flash needs backport to 12.04
+ Pepper Flash needs to be backported to 12.04
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1312219 ***
https://bugs.launchpad.net/bugs/1312219
** Changed in: pepperflashplugin-nonfree
Remote watch: Email to bartm@debian # => None
** Changed in: pepperflashplugin-nonfree
Status: New => Invalid
** This bug has been marked a duplicate of
** Changed in: pepperflashplugin-nonfree (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/1628247
Title:
yakkety 1.8.2+nmu1ubuntu1 does not install due
What browser are you using the Pepper Flash plugin in?
** Summary changed:
- No harware acceleration for H264 Decoding in Pepper Flush Plugin
+ No hardware acceleration for H264 Decoding in Pepper Flash Plugin
** Changed in: adobe-flashplugin (Ubuntu)
Status: New => Incomplete
--
You
If using the Pepper Flash plugin from e.g. adobe-flashplugin through the
PPAPI/NPAPI wrapper from browser-plugin-freshplayer-pepperflash in a
Mozilla-based browser: hardware accelerated decoding is disabled by
default, you can switch it on in ~/.config/freshwrapper.conf
(enable_hwdec = 1,
Ah. Too bad.
Like I said you could try adobe-flashplugin instead of
pepperflashplugin-nonfree. Unfortunately it was confirmed non-working
for Yandex.Browser in Nov. 2015, but hopefully the situation has
improved. Good luck.
If that fails, an option is to download the Flash plugin
1 - 100 of 203 matches
Mail list logo
