I am having 2 problems with updating my laptop. I’m running KDE. My laptop is the 2015 Dell XPS 13 with Broadcom Wifi.
Firstly, it is requesting that I update NetworkManager. When I do this, Networkmanager connects to wireless and wired networks but it does not connect to the internet. When I open my web browser, it says “Server not found”. The packages it is updating are:
NetworkManager-branding-upstream (1.4.0-287.1)
NetworkManager-lang (1.4.0-287.1)
NetworkManager-vpnc-lang (1.0.8-85.1)
NetworkManager-vpnc (1.0.8-85.1)
NetworkManager (1.4.0-287.1)
The second problem is that on the GUI software updater, there are updates showing which cannot be updated because dependencies cannot be resolved. These do not show up while running zypper up from the Konsole. These packages are:
opensuse-2016-1034
opensuse-2016-724
opensuse-2016-972
opensuse-2016-997
Please could someone advise me on what causes these problems and how to fix, or to help me debug the problem further.
The NetworkManager package version is not consistent with that currently provided by the update repo for openSUSE Leap 42.1 , and I don’t have ‘NetworkManager-branding-upstream’ either.
BTW, please post any requested output within CODE tags (refer to the ‘#’ button in the forum editor). It preserves the formatting and makes output easier to read.
What are all these extra repos for? I can’t imagine that having experimental/development repos active is contributing to a stable experience. If you want the ‘latest and greatest’, there’s openSUSE Tumbleweed, which, like Leap and it’s updates, is tested in openQA. Enabling extra repos breaks that completely. My 2 cents.
Would you have had nothing but the distro repos and Packman, you’d probably have had just another update session
I’ve probably added most of them when I’ve downloaded software from the 1-click installer. It’s not trying to get the latest stuff rather, more things which aren’t in the main repositories. I guess now would be a good time to review them to make sure that I am still using the software that comes from them.
Hi, it appears that this version of NetworkManager is coming from the home:X0F:branches:network repository, which has the same version as the GNOME:Factory repository (which is even newer than the version in Tumbleweed!).
It’s most likely that NetworkManager has broken due to a recent update from 1.0.12 to 1.4.0. Try removing that repository first:
You should get some message like the following (not exactly but close enough):
Problem: NetworkManager-branding-upstream-1.4.0-287.1.noarch requires NetworkManager = 1.4.0, but this requirement cannot be provided
Solution 1: deinstallation of NetworkManager-branding-upstream-1.4.0-287.1.noarch
Solution 2: do not install NetworkManager-1.0.6-1.2.x86_64
Solution 3: break NetworkManager-branding-upstream-1.4.0-287.1.noarch by ignoring some of its dependencies
If it is shown in the same way on your computer, select Solution 1.
Please let us know if you have any issues. Thank you!
Apparently you somewhere missed the recommendation to disable a repo added by a 1 click install (and only to enable it again when you want a newer version and nothing more, from the particular package(s) you installed from it). IIRC, it is asked for during the 1 click install process.
Thank you! This has solved the NetworkManager problem.
I still have an issue with the GUI updater. The exact message that it gives is
Dependency resolution failed A package dependency could not be found.
More information is available in the detailed log
These packages aren’t showing in any repositories when I search them by those names using zypper. I don’t know where the log file is located to be able to show the log.
I’ve just tried using the 1 click install option and I could not see that recommendation. It’s possible that I dismissed a pop up and asked it not to be shown again in the past. The “remain subscribed to repositories” check box was automatically check by default for me which might explain it.
Is there a way to list the packages that have been installed from a given repository so that I can review these and unsubscribe that I might not need?
Apparently there’s a conflict somewhere.
PackageKit (being cross-platform) doesn’t support asking the user for manual conflict resolution, it just aborts with that error message.
And “zypper up” doesn’t show an update at all if there’s a conflict.
Run “zypper patch” and post the output, that should give a clue to what causes the problem.
4 Problems:
Problem: patch:openSUSE-2016-1034-1.noarch conflicts with libqt4-debuginfo.x86_64 < 4.8.6-13.1 provided by libqt4-debuginfo-4.8.6-7.1.x86_64
Problem: patch:openSUSE-2016-724-1.noarch conflicts with libqt4-x11-debuginfo.x86_64 < 4.8.6-10.2 provided by libqt4-x11-debuginfo-4.8.6-7.1.x86_64
Problem: patch:openSUSE-2016-972-1.noarch conflicts with libdbus-1-3-debuginfo.x86_64 < 1.8.16-7.1 provided by libdbus-1-3-debuginfo-1.8.16-5.2.x86_64
Problem: patch:openSUSE-2016-997-1.noarch conflicts with python3-base-debuginfo.x86_64 < 3.4.5-8.1 provided by python3-base-debuginfo-3.4.1-6.2.x86_64
Problem: patch:openSUSE-2016-1034-1.noarch conflicts with libqt4-debuginfo.x86_64 < 4.8.6-13.1 provided by libqt4-debuginfo-4.8.6-7.1.x86_64
Solution 1: deinstallation of libqt4-debuginfo-4.8.6-7.1.x86_64
Solution 2: do not install patch:openSUSE-2016-1034-1.noarch
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c):
I don’t think the recommendation is at that place, but it is in many places in the forums here.
I agree with you that the default is not the one I would love.
YaST > Software > Softtware Management.
You can e.g. choose the Repositories view from the View button and then select the repos one by one at the left. You will se at the right what you have installed from them (and what is all there that you have not installed).
You can select (click on the line, but not on the square) every installed package you see at right (either being there because of a Search or of any other selection), and then inspect the Versions tab a the bottom.
Ok, some installed debuginfo packages are the problem, as they require the exact same version of the corresponding package.
You have the following options to fix that:
uninstall the mentioned debuginfo packages, you don’t need them normally, only to debug or report crashes
enable the “debug-update” repo in YaST->Software Repositories, so that those debuginfo packages can be updated too
use “zypper patch” to update the system (this one time) and choose “Solution 1: deinstallation of libqt4-debuginfo-4.8.6-7.1.x86_64” (and similar), this is practically the same as the first point
One has to note though that YaST does display the list of repositories it is going to add when you click on a 1-click install, and allows you to deselect them.
I think this YaST window does even have such a warning, but I’m not sure at the moment.
And normally those additional repos shouldn’t cause a problem either because packages are not switched automatically to other repos (unless you run “zypper dup”).
Newly installed packages may be taken from other repos though if there’s a newer version in there than in the standard repos.
I couldn’t see the warning but there is a checkbox which allows you to choose whether or not you want to subscribe to the repositories after it is installed. By default this is checked to subscribe you to the repositories.
Yes.
There is some explanation text there, but I don’t remember what it exactly says. (I don’t use 1-click installs, I normally add the repos I want and then install things with YaST or zypper, or download the rpms and install them manually)
