Page 1 of 4 123 ... LastLast
Results 1 to 10 of 33

Thread: Update Failure

  1. #1

    Question Update Failure

    Hi all,

    just registered for my very first post - didn't have any issues in the past.
    Should I accidentally disregard any forum rules or best practices, please teach me.

    I have no understanding of the actual issue, so I'll give anything I have until now. I'm happy to provide additional information on request.

    Today's Plasma Update hung when trying to install Avahi (or so it said). After a restart, it will notify me:
    Failed to activate service 'org.freedesktop.PackageKit': timed out (service_start_timeout=25000ms)
    I cannot resort to zypper as it tells me:
    zypper: error while loading shared libraries: libzypp.so.1700: cannot open shared object file: No such file or directory
    There are, however, plenty of those under /.snapshots, and a symlink /usr/lib64/libzypp.so.1702 pointing to libzypp.so.1702.0.2 beside it.

    YaST will complain:
    Internal Error. Please report a bug report with logs.
    Run save_y2logs to getcomplete logs.
    Details: component cannot import namespace 'Pkg'
    Caller: /usr/lib64/ruby/vendor/ruby/2.5.0/yast/yast.rb:178 in 'import_pure'
    This is the same for the majority of components that I try to start from YaST: In the end it'll come down to the very same Details and Caller.

    I much appreciate any help to get my system straight. Thx!

  2. #2

    Default Re: Update Failure

    start yast ncurses and proceed to complete the update
    Code:
    sudo yast2 --ncurses

  3. #3

    Default Re: Update Failure

    Quote Originally Posted by Zaphod_B View Post
    I cannot resort to zypper as it tells me:
    Code:
    zypper: error while loading shared libraries: libzypp.so.1700: cannot open shared object file: No such file or directory
    There are, however, plenty of those under /.snapshots, and a symlink /usr/lib64/libzypp.so.1702 pointing to libzypp.so.1702.0.2 beside it.
    Well, /usr/lib64/libzypp.so.1702 is not the same as libzypp.so.1700... (actually the change in the number means that they are incompatible)

    Your system is in an inconsistent state because of the "aborted" update.
    Unfortunately, zypper is broken by that, so it won't be easily possible to fix it. (you'd need to download affected packages manually and install it with rpm one by one)

    I would suggest one of two things to repair your system:
    - boot from an installation medium and do an "Upgrade", this will basically reinstall all packages.
    - boot an earlier snapshot and roll back. ("snapper rollback")

    And in the future, you should only use "zypper dup" to update your Tumbleweed system.

  4. #4

    Default Re: Update Failure

    Quote Originally Posted by enziosavio View Post
    start yast ncurses and proceed to complete the update
    Code:
    sudo yast2 --ncurses
    Likely not easy to do, as YaST fails to start as well...

  5. #5

    Default Re: Update Failure

    Quote Originally Posted by enziosavio View Post
    start yast ncurses and proceed to complete the update
    Code:
    sudo yast2 --ncurses
    Quote Originally Posted by wolfi323 View Post
    Likely not easy to do, as YaST fails to start as well...
    Well, YaST itself starts, but the update component won't with the above error.

  6. #6

    Default Re: Update Failure

    Quote Originally Posted by wolfi323 View Post
    Likely not easy to do, as YaST fails to start as well...
    Usually yast ncurser also starts when Yast Gui does not work, other ideas I have not seen that the author of the post says that yast gui ne zypper work, but using the translator (also to remember what I wrote) maybe I lose something unfortunately

    Try
    # rpm --rebuilddb

  7. #7

    Default Re: Update Failure

    Quote Originally Posted by enziosavio View Post
    Usually yast ncurser also starts when Yast Gui does not work
    That depends on *why* the YaST Gui doesn't work.

    In this case:
    Code:
    Internal Error. Please report a bug report with logs.
    Run save_y2logs to getcomplete logs.
    Details: component cannot import namespace 'Pkg'
    Caller: /usr/lib64/ruby/vendor/ruby/2.5.0/yast/yast.rb:178 in 'import_pure'
    which will also affect the ncurses version.

    And "rpm --rebuilddb" won't help here either. This is definitely not a problem with the RPM database, but with the installed packages.
    Last edited by wolfi323; 17-Mar-2018 at 09:54.

  8. #8

    Default Re: Update Failure

    Quote Originally Posted by wolfi323 View Post
    Well, /usr/lib64/libzypp.so.1702 is not the same as libzypp.so.1700... (actually the change in the number means that they are incompatible)
    I'm aware of that fact. I tried to hint on the system's state.

    Quote Originally Posted by wolfi323 View Post
    I would suggest one of two things to repair your system:
    - boot from an installation medium and do an "Upgrade", this will basically reinstall all packages.
    - boot an earlier snapshot and roll back. ("snapper rollback")
    Thx, I feared there'd be no simple fix...
    Could you please be more verbose esp. on the 2nd alternative, and/or point me to howtos?

    Quote Originally Posted by wolfi323 View Post
    And in the future, you should only use "zypper dup" to update your Tumbleweed system.
    Okay... The notification itself does no harm and may remain active?

  9. #9

    Default Re: Update Failure

    Quote Originally Posted by Zaphod_B View Post
    Thx, I feared there'd be no simple fix...
    Could you please be more verbose esp. on the 2nd alternative, and/or point me to howtos?
    https://doc.opensuse.org/documentati....snapshot-boot

    Basically you choose "Start bootloader from a read-only snapshot" and the boot menu, select a snapshot to boot, and then run "snapper rollback" as mentioned.

    Okay... The notification itself does no harm and may remain active?
    Correct.

    Although I'm not completely sure that this was actually the problem here, as you say that it hang during the installation of one particular package.
    Maybe that would have happened with zypper as well...

  10. #10

    Default Re: Update Failure

    On 03/17/2018 12:46 PM, wolfi323 wrote:
    >
    > Zaphod_B;2859006 Wrote:
    >> I cannot resort to zypper as it tells me:
    >>>

    > Code:
    > --------------------
    > > > zypper: error while loading shared libraries: libzypp.so.1700: cannot open shared object file: No such file or directory

    > --------------------
    >>>

    >> There are, however, plenty of those under /.snapshots, and a symlink
    >> /usr/lib64/libzypp.so.1702 pointing to libzypp.so.1702.0.2 beside it.
    >>

    > Well, /usr/lib64/libzypp.so.1702 is not the same as libzypp.so.1700...
    > (actually the change in the number means that they are incompatible)
    >
    > Your system is in an inconsistent state because of the "aborted" update.
    > Unfortunately, zypper is broken by that, so it won't be easily possible
    > to fix it. (you'd need to download affected packages manually and
    > install it with rpm one by one)
    >
    > I would suggest one of two things to repair your system:
    > - boot from an installation medium and do an "Upgrade", this will
    > basically reinstall all packages.
    > - boot an earlier snapshot and roll back. ("snapper rollback")
    >
    > And in the future, you should only use "zypper dup" to update your
    > Tumbleweed system.
    >
    >


    I further recommend using 'zypper dup --download-only' until all
    packages are downloaded as it eliminates problems during the downloading
    portion is complete. After the downloads are complets then use 'zypper
    dup' to finish the process.

    --
    Ken
    linux since 1984
    S.u.S.E./openSUSE since 1996

Page 1 of 4 123 ... 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
  •