On starting the Yast SW manager, during the initialisation sequence, I have recently started getting a conflict message that I cannot explain
nothing provides appdata(firefox.appdata.xml) needed by application:Firefox-.noarch
[x] deinstallation of application:Firefox-.noarch
] break application:Firefox-.noarch by ignoring some of its dependencies
Also within the SW manager, on selecting Package > All packages > Update if newer version available, since yesterday, I now get a whole set of conflicts (about 24!).
nothing provides libvncserver.so.0()(64bit) needed by krfb-14.12.1-8.1.x86_64
] do not install krfb-14.12.1-8.1.x86_64
] break krfb-14.12.1-8.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install samba-libs-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libfluidsynth.so.1()(64bit) needed by gstreamer-plugins-bad-1.4.5-78.1.x86_64
] do not install gstreamer-plugins-bad-1.4.5-78.1.x86_64
] break gstreamer-plugins-bad-1.4.5-78.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install samba-client-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
] do not install samba-32bit-4.1.17-5.1.x86_64
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libwbclient0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
] do not install libtevent-util0-32bit-4.1.17-5.1.x86_64
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libsmbldap0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
] do not install libsmbconf0-32bit-4.1.17-5.1.x86_64
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libsmbclient-raw0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libsamdb0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libsamba-util0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libsamba-hostconfig0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libsamba-credentials0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libpdb0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libnetapi0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libndr0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libndr-standard0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libndr-nbt0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libndr-krb5pac0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libgensec0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libdcerpc0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
nothing provides libavahi-common.so.3 needed by samba-libs-32bit-4.1.17-5.1.x86_64
] do not install libdcerpc-binding0-32bit-4.1.17-5.1.x86_64
] break samba-libs-32bit-4.1.17-5.1.x86_64 by ignoring some of its dependencies
I choose the ‘do not install’ option in every case.
Can anyone tell me what has happened? What should I do to recover normal behaviour?
That’s a known “problem”. Please search the forums, this already has been discussed a few times.
To get rid of that conflict message, disable the dependency auto-check in YaST.
Also within the SW manager, on selecting Package > All packages > Update if newer version available, since yesterday, I now get a whole set of conflicts (about 24!).
That’s not normal. openSUSE 13.2 comes with libvncserver0 (and libavahi-common3 which is also mentioned in your conflicts).
Apparently you have incompatible or missing repos.
Please post your list:
Hm? What “repository auto-check” did you switch off?
I wrote “dependency auto-check”.
In case it wasn’t clear, I meant the option “Autocheck” in the “Dependencies” menu in YaST->Software Management’s menu bar.
This does not solve the inconsistency of course, but it prevents the conflict message from being shown all the time.
The only “solution” to the problem for now is to uninstall Firefox, but other packages are affected as well.
Hm, I never saw that dialog on any of my systems, so I’d say it should not appear with the default settings (which implies of course that a fresh re-installation would help). I do see the “conflict” when I run “zypper ve” though.
Although I noticed now that I do have Dependencies->Autocheck turned ON, so this can’t really be the cause. (no idea why I thought it was off…)
Did you ever try to choose “break application:Firefox-.noarch by ignoring some of its dependencies”? It’s irrelevant anyway, appdata is just some additional information about the package/software which is only shown by “gnome-software” at the moment AFAIK. And the Firefox package does contain appdata, the package just doesn’t specify that it provides it.
You could also check whether you have libzypp-plugin-appdata installed and remove it if you have (as I suggested already in a different thread in November). Maybe this plays a part here, but I don’t know.
Breaking the dependeicies doesn’t make any difference to the Autocheck. It still comes up next time on starting Yast.
I deinstalled libzypp-plugin-appdata and it raised an inconsistency, suggesting that I also deinstall gnome-software, which I also did. No effect on the ‘firefox’ inconsistency though.
Hm. Just one question: do you actually have Firefox installed?
The dialog might be triggered because Firefox is selected for installation automatically. Try to disable “Ignore recommended packages for already installed packages” in “Options”.
Firefox was always installed. After disabling the option above the ‘firefox’ inconstency is still there.
By the way, on disabling the above option, a whole string of applications were identified for (re)installation, including libzypp-plugin-appdata and gnome-software.
Hm, no idea then.
As I don’t have the problem, I cannot tell what would (or would not) “fix” it either.
You already did try to choose “deinstallation of application:Firefox-.noarch” as well, right?
Try to explicitely remove the application Firefox-.noarch with zypper.
sudo zypper rm -t application Firefox-.noarch
Note that this will not remove the package MozillaFirefox, so you will still have it installed afterwards.
Run “sudo zypper ve” and solve the conflict there.
Maybe try to remove the zypper cache:
sudo rm -r /var/cache/zypp
By the way, on disabling the above option, a whole string of applications were identified for (re)installation, including libzypp-plugin-appdata and gnome-software.
Of course. If you disable the option, all recommended packages are installed again.
I actually wanted you to enable the option. I made a typing mistake there, sorry.
