Software management in Yast Control Center reports an error
internal error Please report a bug with logs
undefined method include for | “CD” “DVD” array caller /usr/share/yast/modules/packages callbacks.rb 812:in Media Change
I have fresh intallation of latest release.
Did you remove the installer from the repo list?
I didn’t change repos.
Also I don’t see anything with word “installer” in repo list.
I installed Suse from external drive.
Problem appeared after update and restart.
What gogalthorp meant was whether you have removed the installation medium, i.e. your external drive, from your repo list.
Apparently not. (Normally it shouldn’t even be necessary)
If YaST doesn’t start, use “zypper lr -d” to show your repos, and “zypper rr ##” (replace ## with the number of the repo) to remove it.
Does it “fix” the problem if you remove it?
If you’re unsure which one your installation medium is (but I think it should be obvious), please post the output of “zypper lr -d” for further advise.
I also noticed the same result of yesterday’s update on two different 13.2 computers. In my case one of them has never had a CD reader and the other one had the CD removed from the list of repositories. So it has nothing to do with the installer repository. I reverted to the previous version yast2-3.1.109-4.2.x86_64. This solved the problem. I tried the update today again and it now works, so it looks as if the problem has bin rectified.
Ulf
Well, but I do not have nor had that problem here, with that update installed. So it definitely is not a general problem either.
And nobody said that the problem might be related to a CD reader or having the CD in the list of repositories.
Maybe it gets triggered if you have an USB installation medium in the list?
No idea. Maybe it’s triggered by something else completely. The installation medium was just a guess because the error message mentions “CD” and “DVD”…
As mentioned, I don’t have that problem here, and haven’t seen it either. And I for a fact do not have any installation medium in my repo list.
I tried the update today again and it now works, so it looks as if the problem has bin rectified.
I doubt it. There has been no change to yesterday’s update (which one do you meant btw? the only official update I got yesterday was for xorg-x11-XVnc/tigervnc, I highly doubt that that one caused the problem… 
), and no update to fix the previous update either.
And neither did I have the installation medium in the repo list. Anyway I guess that you are correct about that something else triggered the behaviour, but what? The applied code was given by the delta yast2-3.1.109_3.1.109.1-4.2_8.1.x86_64.drpm, which seems to be from February 12. Since everything is back to normal via the described route I assume that it will be hard to figure out the real reason.
Ulf
You’re right, sorry. I overlooked this when I checked which updates I installed yesterday (I updated the whole KF5/Plasma 5 as well, which are over a hundred packages… ).
Since everything is back to normal via the described route I assume that it will be hard to figure out the real reason.
Well, apparently the YaST developers have found the reason, and it is fixed already:
https://build.opensuse.org/package/rdiff/YaST:openSUSE:13.2/yast2?linkrev=base&rev=5
But this is not released yet, you definitely still have the “buggy” update installed. Although I do hope that this fix will be released soon as well then of course.
But apparently the issue indeed only occurs when a media is requested, i.e. when you have an installation medium (CD, DVD, USB?) in your repo list.
As you say you didn’t have any when you encountered the problem, I can only imagine that it is also triggered when an online repo is unreachable currently (or somthing like that).
I do also have this bug which is not general because it doesn’t appear in the moderators installation, for the same reason I never had a bug in the KDE network manager. In my humble opinion, the minimizing attempt by serious bugs brings a worse reputation for our distribution. Thanks to the user who advices reverting to a previous yast2 version.
Are you trying to be cynical here?
Yes, I don’t see both bugs on my systems, but I never said there are no bugs.
Did you report your “KDE network manager” problem to KDE? 
In my humble opinion, the minimizing attempt by serious bugs brings a worse reputation for our distribution. Thanks to the user who advices reverting to a previous yast2 version.
Again, this bug has been fixed already and an update for YaST is pending and should be released soon.
I had the same problem. It seems there was a bug in some update of Yast2 that prevented from doing new updates (where the bug has been removed).
The solution is to edit the file PackageCallbacks.rb in /usr/share/YaST2/modules and change ‘include’ to ‘include?’ in lines 802 and 812 (what I did was to comment that part of the file).