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

Thread: Update broke system

  1. #1

    Default Update broke system

    Hi, I performed a system update with `zypper update`. The update ran into a problem. I aborted it and this kinda crippled my system. To stat with, here is the terminal output leading up the the current state.

    Code:
    Retrieving: openssh-askpass-gnome-7.9p1-244.1.x86_64.rpm ......................................................................................................................................................[done]
    Checking for file conflicts: .................................................................................................................................................................................[error]
    Detected 14 file conflicts:
    
    
    File /usr/bin/par
      from install of
         par-1.1-190.2.x86_64 (repo-oss)
      conflicts with file from package
         vim-par-1.5.2-2.1.x86_64 (@System)
    
    
    File /usr/lib/modules-load.d/sg.conf
      from install of
         suse-module-tools-15.2.5-1.1.x86_64 (repo-oss)
      conflicts with file from package
         systemd-237-10.1.x86_64 (@System)
    
    
    File /usr/lib/udev/rules.d/80-hotplug-cpu-mem.rules
      from install of
         system-tuning-common-SUSE-0.1-4.1.noarch (repo-oss)
      conflicts with file from package
         udev-237-10.1.x86_64 (@System)
    
    
    File /usr/lib64/libgdbm_compat.so.4.0.0
      from install of
         libgdbm_compat4-1.18.1-1.5.x86_64 (repo-oss)
      conflicts with file from package
         libgdbm4-1.12-1.28.x86_64 (@System)
    
    
    File /usr/share/locale/de/LC_MESSAGES/gdbm.mo
      from install of
         gdbm-lang-1.18.1-1.5.noarch (repo-oss)
      conflicts with file from package
         libgdbm4-1.12-1.28.x86_64 (@System)
    
    
    File /usr/share/locale/eo/LC_MESSAGES/gdbm.mo
      from install of
         gdbm-lang-1.18.1-1.5.noarch (repo-oss)
      conflicts with file from package
         libgdbm4-1.12-1.28.x86_64 (@System)
    
    
    File /usr/share/locale/fi/LC_MESSAGES/gdbm.mo
      from install of
         gdbm-lang-1.18.1-1.5.noarch (repo-oss)
      conflicts with file from package
         libgdbm4-1.12-1.28.x86_64 (@System)
    
    
    File /usr/share/locale/fr/LC_MESSAGES/gdbm.mo
      from install of
         gdbm-lang-1.18.1-1.5.noarch (repo-oss)
      conflicts with file from package
         libgdbm4-1.12-1.28.x86_64 (@System)
    
    
    File /usr/share/locale/ja/LC_MESSAGES/gdbm.mo
      from install of
         gdbm-lang-1.18.1-1.5.noarch (repo-oss)
      conflicts with file from package
         libgdbm4-1.12-1.28.x86_64 (@System)
    
    
    File /usr/share/locale/pl/LC_MESSAGES/gdbm.mo
      from install of
         gdbm-lang-1.18.1-1.5.noarch (repo-oss)
      conflicts with file from package
         libgdbm4-1.12-1.28.x86_64 (@System)
    
    
    File /usr/share/locale/pt_BR/LC_MESSAGES/gdbm.mo
      from install of
         gdbm-lang-1.18.1-1.5.noarch (repo-oss)
      conflicts with file from package
         libgdbm4-1.12-1.28.x86_64 (@System)
    
    
    File /usr/share/locale/sr/LC_MESSAGES/gdbm.mo
      from install of
         gdbm-lang-1.18.1-1.5.noarch (repo-oss)
      conflicts with file from package
         libgdbm4-1.12-1.28.x86_64 (@System)
    
    
    File /usr/share/locale/uk/LC_MESSAGES/gdbm.mo
      from install of
         gdbm-lang-1.18.1-1.5.noarch (repo-oss)
      conflicts with file from package
         libgdbm4-1.12-1.28.x86_64 (@System)
    
    
    File /usr/share/locale/vi/LC_MESSAGES/gdbm.mo
      from install of
         gdbm-lang-1.18.1-1.5.noarch (repo-oss)
      conflicts with file from package
         libgdbm4-1.12-1.28.x86_64 (@System)
    
    
    File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
    Continue? [yes/no] (no): yes
    
    [...]
    (  92/3934) Installing: libattr1-2.4.48-3.1.x86_64 ............................................................................................................................................................[done]
    (  93/3934) Installing: libaudiofile1-0.3.6-11.5.x86_64 ......................................................................................................................................................[error]
    Installation of libaudiofile1-0.3.6-11.5.x86_64 failed:
    Error: Subprocess failed. Error: RPM failed: rpm: relocation error: /lib64/libacl.so.1: symbol getxattr version ATTR_1.0 not defined in file libattr.so.1 with link time reference
    
    
    Abort, retry, ignore? [a/r/i] (a): a
    Problem occurred during or after installation or removal of packages:
    Installation aborted by user
    Please see the above error message for a hint.
    
    
    ~                                                                                                                                                                                        
    ▶ kate                                                                                                                                                                                 
    kate: relocation error: /lib64/libacl.so.1: symbol getxattr version ATTR_1.0 not defined in file libattr.so.1 with link time reference
    
    
    ~                                                                                                                                                                                      
    ▶ libreoffice                                                                                                                                                                       
    sed: relocation error: /lib64/libacl.so.1: symbol getxattr version ATTR_1.0 not defined in file libattr.so.1 with link time reference
    /usr/bin/libreoffice: line 174: /usr/bin/oosplash: No such file or directory
    
    
    ~                                                                                                                                                                                            
    ▶ sudo zypper update                                                                                                                                                             
    [sudo] password for root: 
    zypper: relocation error: /lib64/libacl.so.1: symbol getxattr version ATTR_1.0 not defined in file libattr.so.1 with link time reference

    What logs etc. can I give you for more useful information?

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

    Default Re: Update broke system

    You should normally use "zypper dup" rather than "zypper update" for updating Tumbleweed.

    It looks as if you have some old packages that would have been removed by "zypper dup", but which are still there. And the newer replacement package has file conflicts.

    You could try "zypper dup" and see if that fixes the problems. But it might not.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  3. #3

    Default Re: Update broke system

    Quote Originally Posted by nrickert View Post
    You should normally use "zypper dup" rather than "zypper update" for updating Tumbleweed.

    It looks as if you have some old packages that would have been removed by "zypper dup", but which are still there. And the newer replacement package has file conflicts.

    You could try "zypper dup" and see if that fixes the problems. But it might not.
    No, gives me the same error as all the other program calls.

  4. #4
    Join Date
    Apr 2016
    Location
    North America
    Posts
    537

    Default Re: Update broke system

    Tumbleweed, Xfce, Firefox, uBlock Origin

  5. #5

    Default Re: Update broke system

    Are snapshots made automatically per default? I did not make any myself.

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

    Default Re: Update broke system

    Quote Originally Posted by Benutzer42 View Post
    Are snapshots made automatically per default? I did not make any myself.
    Yes,
    Snapshots are created automatically any time you boot, shutdown and packages change (update, upgrade in TW, install, remove).

    Simply roll back to any time prior to your failed update and you should be fine.

    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!

  7. #7

    Default Re: Update broke system

    Quote Originally Posted by tsu2 View Post
    Yes,
    Snapshots are created automatically any time you boot, shutdown and packages change (update, upgrade in TW, install, remove).

    Simply roll back to any time prior to your failed update and you should be fine.

    TSU
    If I reboot now, is the latest snapshot then being overwritten? As it is I can't even copy files. Likely from the recovery mode that would still work. But for that I need to reboot.

  8. #8

    Default Re: Update broke system

    I see I need to be using Btrfs for this whole rollback thing to work. But I am using ext4. So, that won't do. Any other ideas what I can do?

  9. #9
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,839

    Default Re: Update broke system

    Try going to http://download.opensuse.org/tumblew...po/oss/x86_64/, downloading:
    • zypper
    • libzypp
    • libsolv-tools
    • rpm
    • libproxy1
    • libmodman1
    and upgrading them all at once using rpm -Uvh. If another dependency is missing, download that and try again. If deps get out of hand, do an upgrade installation via NET or full installation media.
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  10. #10

    Default Re: Update broke system

    Thanks, will try. What is NET though?

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

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