Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: Chromium update fails due to conflict in dependency

  1. #1

    Default Chromium update fails due to conflict in dependency

    A recent chromium security update fails to install because of a dependency conflict. When I attempt to do this in Yast, here is the message:

    opensSUSE-2016-1453-1.noarch conflicts with chromium.x86_64< 55.0.2883.75-99.2 provided by chromium-54.0.2840.100-91.1x86_64

    Should I install with vendor change, or don't install?

  2. #2
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,047
    Blog Entries
    14

    Default Re: Chromium update fails due to conflict in dependency

    Quote Originally Posted by rgietzen View Post
    A recent chromium security update fails to install because of a dependency conflict. When I attempt to do this in Yast, here is the message:

    opensSUSE-2016-1453-1.noarch conflicts with chromium.x86_64< 55.0.2883.75-99.2 provided by chromium-54.0.2840.100-91.1x86_64

    Should I install with vendor change, or don't install?
    Please show output of
    Code:
    zypper lr -d
    This should not happen.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  3. #3
    Join Date
    Jun 2008
    Location
    NZ
    Posts
    1,567

    Default Re: Chromium update fails due to conflict in dependency

    the conflict will be because chromium wants to update to 55.xx but chromium-ffmpeg is still on 54.xx
    Interestingly - doing the update in Yast>Software it automatically uninstalls chromium-ffmpeg - and when I later look in packman, chromium-ffmpeg has disappeared.
    BUT . . . chromium still seems to have full multimedia support.
    Has ffmpeg been incorporated directly into chromium? What's the story here?

  4. #4

    Default Re: Chromium update fails due to conflict in dependency

    Quote Originally Posted by farcusnz View Post
    Has ffmpeg been incorporated directly into chromium? What's the story here?
    No, opposite -- now it (chromium) uses the system installed version (of ffmpeg). There should be mention of this in the change log of the package update

    (the good news / benefit of this is move is that there'll be no more mis-matches between chromium updates and chromium-ffmpeg!)

  5. #5
    Join Date
    Jun 2008
    Location
    NZ
    Posts
    1,567

    Default Re: Chromium update fails due to conflict in dependency

    Quote Originally Posted by Tyler_K View Post
    No, opposite -- now it (chromium) uses the system installed version (of ffmpeg). There should be mention of this in the change log of the package update

    (the good news / benefit of this is move is that there'll be no more mis-matches between chromium updates and chromium-ffmpeg!)
    excellent - that is good news.
    Unfortunately the Plasma updater chokes on this update and it needs to be updated manually in Yast>Software.

    I also noticed that pepperflash has been removed from packman . . . . and chromium now reports no flash support.
    Not such a big problem though - can't remember the last time I visited a site that still uses flash.

  6. #6
    Join Date
    Jun 2008
    Location
    NZ
    Posts
    1,567

    Default Re: Chromium update fails due to conflict in dependency

    Quote Originally Posted by farcusnz View Post
    I also noticed that pepperflash has been removed from packman . . . . and chromium now reports no flash support.
    Not such a big problem though - can't remember the last time I visited a site that still uses flash.
    oh, I see.
    It seems the chromium-pepperflash plugin has been obsoleted and we now need to install flash-player-ppapi

  7. #7

    Default Re: Chromium update fails due to conflict in dependency

    Quote Originally Posted by farcusnz View Post
    excellent - that is good news.
    Unfortunately the Plasma updater chokes on this update and it needs to be updated manually in Yast>Software.
    Well, apparently YaST and zypper "choke" on this update too, see the OP. PackageKit (which is distribution agnostic) just doesn't support resolving conflicts manually by the user.

    The reason is likely that chromium-ffmpeg comes from a different repo/vendor than chromium, and the package management (libzypp) doesn't automatically replace a package from one repo/vendor to a package from a different one.

    Unfortunate in this case (and I don't think there can be anything done about it really), but that "vendor stickiness" is on purpose and preferable in general.

    So as answer to the OP:
    Yes, you should allow the vendor change, or uninstall chromium-ffmpeg manually before installing the update.

    Though a similar conflict may also happen if you installed chromium from some 3rd party repo which hasn't been updated (yet).
    In that case you need to decide yourself which version you want to use.

    I also noticed that pepperflash has been removed from packman . . . . and chromium now reports no flash support.
    Not such a big problem though - can't remember the last time I visited a site that still uses flash.
    It has been replaced by flash-player-ppapi apparently:
    http://packman.links2linux.de/package/flash-player

    There's a bug report that it doesn't work though:
    http://bugzilla.opensuse.org/show_bug.cgi?id=1015749

    I don't have chromium installed, so I cannot tell.
    Last edited by wolfi323; 15-Dec-2016 at 07:29.

  8. #8
    Join Date
    Jun 2008
    Location
    NZ
    Posts
    1,567

    Default Re: Chromium update fails due to conflict in dependency

    Quote Originally Posted by wolfi323;2804274
    It has been replaced by flash-player-ppapi apparently:
    [url
    http://packman.links2linux.de/package/flash-player[/url]

    There's a bug report that it doesn't work though:
    http://bugzilla.opensuse.org/show_bug.cgi?id=1015749

    I don't have chromium installed, so I cannot tell.
    seems to be working OK here . . .
    Chromium 55.0.2883...
    flash-player 24.0.0.186-2.1
    flash-player-ppapi 24.0.0.186-2.1

  9. #9

    Default Re: Chromium update fails due to conflict in dependency

    Quote Originally Posted by wolfi323 View Post
    It has been replaced by flash-player-ppapi apparently:
    http://packman.links2linux.de/package/flash-player

    There's a bug report that it doesn't work though:
    http://bugzilla.opensuse.org/show_bug.cgi?id=1015749

    I don't have chromium installed, so I cannot tell.
    It seems to work for me. Though I had to go through a bit of a dance with it:

    • Installed flash-player-ppapi yesterday. It required removing pepperflash
    • freshplayer plugin in Firefox no longer works ... (player complains "failed to load libpepflashplayer.so ....")
    • Installed adobe's flash-player (which provides plugin) ... Firefox flash video works again ... but adobe's player sucks
    • uninstalled adobe flash-player. Re-installed freshplayerplugin ... Fresh player automagically works in Firefox again (i.e. now correctly picking up the flash-player-ppapi) ... and, oh, yeah, it (flash playback) works in chromium too
    • all is good

  10. #10

    Default Re: Chromium update fails due to conflict in dependency

    Quote Originally Posted by Tyler_K View Post

    • freshplayer plugin in Firefox no longer works ... (player complains "failed to load libpepflashplayer.so ....")
    • Installed adobe's flash-player (which provides plugin) ... Firefox flash video works again ... but adobe's player sucks
    But Packman contains flash-player 24.0 now too, the exact same version as flash-player-ppapi (it's actually part of the same "source" package).

    So is there actually still a need for freshplayer-plugin?
    (never used that myself, I stick to the "official" flash-player from the standard 13.2 update repo)

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •