Announcement

Collapse
No announcement yet.

Nepomuk problem after upgrade to KDE 4.4

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Nepomuk problem after upgrade to KDE 4.4

    Hi!

    After upgrading to KDE 4.4 I get the following error starting nepomukserver:

    symbol lookup error: /usr/lib/kde4/nepomukstorage.so: undefined symbol:
    _ZN7Soprano6Server10ServerCore25setMaximumConnecti onCountEi

    The installed packages seem to be inconsistent. What can I do? Is nepomuk working at your computer with KDE 4.4?

    Best regards,
    Oliver.

    #2
    Re: Nepomuk problem after upgrade to KDE 4.4

    Hi!

    libsoprano4 - 2.3.73 is installed. Don't we need 2.4.0 for KDE 4.4?

    Best regards,
    Oliver.

    Comment


      #3
      Re: Nepomuk problem after upgrade to KDE 4.4

      Hi!

      After executing "aptitude upgrade" I now have soprano 2.4.0.1 but unfortunately nepomuk is still not working. Has anybody a working nepomuk under kde 4.4?

      Best regards,
      Oliver.

      Comment


        #4
        Re: Nepomuk problem after upgrade to KDE 4.4

        Originally posted by oheidbuechel
        Hi!

        After executing "aptitude upgrade" I now have soprano 2.4.0.1 but unfortunately nepomuk is still not working. Has anybody a working nepomuk under kde 4.4?

        Best regards,
        Oliver.
        Try new update of kde4libs, only 3 hours old:
        Changelog
        kde4libs (4:4.4.0-0ubuntu1~karmic1~ppa2) karmic; urgency=low

        * Make kdelibs5 depend on shared-desktop-ontologies, otherwise
        Nepomuk search does not work properly
        -- Harald Sitter <email address hidden> Fri, 12 Feb 2010 11:42:03 +0200
        Kubuntu 12.04 64bit

        Comment


          #5
          Re: Nepomuk problem after upgrade to KDE 4.4

          I upgraded yesterday and once I'd got the right virtuoso backend (virtuoso-open I think it was called) then it seems to be working properly. Not tested the search much though.

          Comment


            #6
            Re: Nepomuk problem after upgrade to KDE 4.4

            Hi!

            After another upgrade and removing libsoprano* and a subdirectory soprano from /usr/local/lib it works.

            Best regards,
            Oliver.

            Comment


              #7
              Re: Nepomuk problem after upgrade to KDE 4.4

              fwiw - over at ArchLinux people have been reporting similar probs with virtuoso and nepomuk.

              I've disabled my indexing (vanilla kde4.4 on ArchLinux) and let it run overnight until finished.
              Once your problem is solved please mark the topic of the first post as SOLVED so others know and can benefit from your experience! / FAQ

              Comment


                #8
                Re: Nepomuk problem after upgrade to KDE 4.4

                http://socceroosd.blogspot.com/2010/...d-nepomuk.html

                via PlanetKDE

                Comment


                  #9
                  Re: Nepomuk problem after upgrade to KDE 4.4

                  Thanks!

                  Following these instructions got it going again.

                  Indexing now - seems to be going OK -fingers crossed.

                  Cheers,

                  Steve

                  Comment


                    #10
                    Re: Nepomuk problem after upgrade to KDE 4.4

                    Confirmed it solves the problem here - indexing completed and searches working great.

                    Comment


                      #11
                      Re: Nepomuk problem after upgrade to KDE 4.4

                      I also have problems with nepomuk/strigi. At first nepomuk wouldn't start, but the solution mentioned above solved that. But strigi still has issues. After I check "Enable Strigi Desktop File Indexer" it starts to index, but after a minute goes idle for a second and then starts over. After a few "restarts" it just quits and "Enable Strigi Desktop File Indexer" is unchecked. If I check it again, everything happens like before. Any ideas? Maybe I could start strigi from console to get the error?

                      B

                      Comment

                      Working...
                      X