Results 1 to 4 of 4

Thread: Software Update Failed

  1. #1

    Default Software Update Failed

    I recently got ADSL (after waiting for many years) and when I ran Leap for the first time it automatically downloaded software updates. Just now I got notification of 103 updates, but this time the download failed, reporting "dependency resolution failed...more information is in the detailed log."

    Where is this log? I see nothing in /var/log that indicates "update."

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,140
    Blog Entries
    2

    Default Re: Software Update Failed

    All distros that have replaced the sysVinit subsystem with systemd now store all logfiles (including the system logs) in the "journal" which is a database instead of flat files.

    You access the journal using the command "journalctl"
    You can invoke journalctl specifying entries for any boot sequence (including last), over a date and time range, keywords, etc. You can Google "journalctl" for blog articles people have written about their favorite command combinations, you can also read the MAN pages or take a look at the "help"
    Code:
    journalctl --help
    HTH,
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  3. #3
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,496
    Blog Entries
    3

    Default Re: Software Update Failed

    Use Yast online update. It will tell you where the conflict is.

    Here, I had to deselect the "chromium" update to avoid problems. It seems that "chromium-ffmpeg" in Packman is a tad behind "chromium" in the main repo. It will probably be fixed within a day or three.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  4. #4

    Default Re: Software Update Failed

    Quote Originally Posted by nrickert View Post
    Use Yast online update. It will tell you where the conflict is.

    Here, I had to deselect the "chromium" update to avoid problems. It seems that "chromium-ffmpeg" in Packman is a tad behind "chromium" in the main repo. It will probably be fixed within a day or three.
    Thanks. I did a YAST update. There are now 7 updates that relate to Chromium that will not install, so I'll wait a few days for these to be fixed.

    Although I have been using SuSE since 6.1, this is the first time I've been able to update by internet, so this is a new trick for an old dog. In my 20+ years of using Linux, I have come to value a system's administration tools. Old Linuces like Caldera Open Linux and Libranet Debian excelled in this feature, but I also got used to YAST, so I've stayed with SuSE.

Posting Permissions

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