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

Thread: vi suddenly broken

  1. #1

    Default vi suddenly broken

    vi: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory
    i use tumbleweed
    i use vi daily
    i installed a lot of updates and then vi gives the above message

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

    Default Re: vi suddenly broken

    On my system, libperl is found by locate at the following location
    Code:
    # locate libperl.so
    /usr/lib/perl5/5.24.0/x86_64-linux-thread-multi/CORE/libperl.so
    You can try force re-installing vim by running the following command
    Code:
    zypper in --force vim
    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
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,852
    Blog Entries
    14

    Default Re: vi suddenly broken

    How do you update your TW? Should be
    Code:
    zypper dup --no-allow-vendor-change
    Otherwise, show us your repos, please
    Code:
    zypper lr -d
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  4. #4

    Default Re: vi suddenly broken

    To Knurpht
    repositories
    1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
    2 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/oss/ |
    3 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |

    for updating i have been using yast so i don't know the precise command. i have not changed anything about this since it was installed

    To tsu2
    locate doesn't find libperl.so . i also looked in location you found. not there

    Response to forciny reinstall:


    .Solution 2: downgrade of libopenssl1_0_0-1.0.2k-3.1.x86_64 to libopenssl1_0_0-1.0.2k-2.2.x86_64
    Solution 3: do not install vim-8.0.566-2.4.x86_64
    Solution 4: break vim-8.0.566-2.4.x86_64 by ignoring some of its dependencies



    Solution 1 was very extensive so i ignored it.
    not sure which of any of 2,3 or 4 i should try

  5. #5
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,853
    Blog Entries
    15

    Default Re: vi suddenly broken

    Hi
    The openssl package is at 1.0.2k-4.2, suggest you refresh and run updates for the new release today...
    Code:
    zypper ref -f
    zypper verify
    zypper dup
    Since you don't have any other repositories subscribed to, no need for the no allow vendor change.

    You could also be getting pointed at an incomplete mirror.....
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  6. #6

    Default Re: vi suddenly broken

    the suggestion by malcolmlewis worked
    apparently the update method i used (clicking on a little icon)
    isn't as complete as the suggested one.
    much thanks to all repliers

  7. #7
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,156

    Default Re: vi suddenly broken

    Quote Originally Posted by jonalanwright View Post
    apparently the update method i used (clicking on a little icon)
    isn't as complete as the suggested one.
    When you mean you are using KDE (you never explained) and use the Update applet there, that is indeed next to useless in Tumbleweed, because it tries to emulate doing zypper up.

    And for posting things like that zypper lr -d:

    Please in the future use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.
    Henk van Velden

  8. #8

    Default Re: vi suddenly broken

    Quote Originally Posted by jonalanwright View Post
    ...
    Solution 1 was very extensive so i ignored it.
    not sure which of any of 2,3 or 4 i should try
    You were wise to refuse Solution 1. I have a similar problem with Fotoxx; it complained it needed exif tool. It was suggested to force reinstallation. That also proposed extensive package installation of -586 architecture. I accepted it, and it killed KDE Plasma. I can only run ICE now.

  9. #9
    Join Date
    Oct 2014
    Location
    Rotterdam
    Posts
    147

    Default Re: vi suddenly broken

    Handy to find this thread, I had the same problem running Tumbleweed on KDE.

    The solution provided by @malcolmlewis
    Code:
    zypper ref -f
    zypper verify
    zypper dup
    did also work for me, it did a lot of updates (245 downloads).

    Quote Originally Posted by hcvv
    use the Update applet there, that is indeed next to useless in Tumbleweed, because it tries to emulate doing zypper up.
    Good to know "Software updates" in "Status & Notifications" should not be used for Tumbleweed but isn't that something that should be fixed?
    Is this not a problem for LEAP 42.2?

  10. #10

    Default Re: vi suddenly broken

    Quote Originally Posted by marel View Post
    Good to know "Software updates" in "Status & Notifications" should not be used for Tumbleweed but isn't that something that should be fixed?
    Well, I wouldn't go so far as saying it "should not be used". Actually it should work fine most of the time, but there are some situations it cannot handle properly as it (PackageKit's zypp backend) is designed to update a stable release like Leap. (as hcvv wrote it does the equivalent of "zypper up", but in Tumbleweed every snapshot is a new distribution release more or less so you should rather do a *d*istribution *up*grade, "zypper dup")

    Better support for Tumbleweed, i.e. making it able to do the equivalent of "zypper dup", is work-in-progress.

    Is this not a problem for LEAP 42.2?
    No.
    Leap is a stable release and only receives bugfix and security updates. There are no downgrades possible and no packages are added/dropped/renamed.
    "zypper up" (or even "zypper patch") is the proper way to update Leap.

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
  •