Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Software management bug

  1. #1

    Default Software management bug

    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.

  2. #2
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,703

    Default Re: Software management bug

    Did you remove the installer from the repo list?

  3. #3

    Default Re: Software management bug

    Last edited by wolfi323; 12-Feb-2015 at 15:51.

  4. #4

    Default Re: Software management bug

    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.

  5. #5

    Default Re: Software management bug

    Quote Originally Posted by xmppwokki View Post
    I didn't change repos.

    Also I don't see anything with word "installer" in repo list.

    I installed Suse from external drive.
    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.
    Last edited by wolfi323; 12-Feb-2015 at 16:40.

  6. #6

    Default Re: Software management bug

    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

  7. #7

    Default Re: Software management bug

    Quote Originally Posted by UlfLennart View Post
    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.
    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.
    Last edited by wolfi323; 13-Feb-2015 at 08:43.

  8. #8

    Default Re: Software management bug

    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

  9. #9

    Default Re: Software management bug

    Quote Originally Posted by UlfLennart View Post
    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.
    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/r...rev=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).
    Last edited by wolfi323; 13-Feb-2015 at 09:45.

  10. #10

    Default Re: Software management bug

    Quote Originally Posted by wolfi323 View Post
    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... ).


    Well, apparently the YaST developers have found the reason, and it is fixed already:
    https://build.opensuse.org/package/r...rev=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.
    Laptop: MSI 60 2PC | OpenSUSE 13.1 (x86_64) | KDE Current| Compiz 8.8 | Intel(R) Core(TM) i7-4700HQ CPU 3.2GHz | GTX850M | 8GB RAM

Page 1 of 2 12 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
  •