Announcement

Collapse
No announcement yet.

[Solved, see reply #20] help! did something very wrong with nepomuk...

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

    #16
    Re: help! did something very wrong with nepomuk...

    Snowhog, thnx for your reply too

    I did try what you mentioned, following doctordruidphd's advice, and got what I mentioned in reply#6.

    I also did a little something else in the user management icon in the system settings. In my acname i unchecked admin or something and now it tells me that "I am not in the sudoers file. This incident will be reported."

    Great. Now I don't have sudo access... If you guys have any ideas I can fix this, it would be great! Otherwise I am heading to a reinstall...

    Comment


      #17
      Re: help! did something very wrong with nepomuk...

      sry for the double post, I didn't see the second page and thought I didn't post in the first place.

      Comment


        #18
        Re: help! did something very wrong with nepomuk...

        To fix the sudo problem, you will need to boot into the recovery console.

        Then you will need to issue the command

        adduser yourusername admin

        substituting your user name for "username".

        Then reboot, and you should be back in the admin group.



        We only have to look at ourselves to see how intelligent life might develop into something we wouldn't want to meet. -- Stephen Hawking

        Comment


          #19
          Re: help! did something very wrong with nepomuk...

          doctordruidphd, thnx so much for your reply, it worked

          Lesson I need to learn: If it works, don't fix it...


          EDIT: something I forgot to mention, is that the muon package manager still doesn't ask me for the password and so is unable to apply any update. I am still bypassing it using the konsole.

          EDIT2: I did some googling and found that the package polkit-kde-1 is supposed to fix this issue. Does anyone know what package this is and how safe it is to install it?

          thnx again

          Comment


            #20
            Re: help! did something very wrong with nepomuk...

            quoted from the package description:

            PolicyKit is an application-level toolkit for defining and handling the policy that allows unprivileged processes to speak to privileged processes.

            It is a framework for centralizing the decision making process with respect to granting access to privileged operations (like calling the HAL Mount() method) for unprivileged (desktop) applications.

            PolicyKit-Kde provides a D-Bus session bus service that is used to bring up authentication dialogs used for obtaining privileges.
            Yes, it is safe to install. It is a PolicyKit extension for KDE support.
            The unjust distribution of goods persists, creating a situation of social sin that cries out to Heaven and limits the possibilities of a fuller life for so many of our brothers. -- Archbishop Jorge Mario Bergoglio of Buenos Aires (now Pope Francis)

            Comment


              #21
              [solved] Re: help! did something very wrong with nepomuk...

              bsniadajewski, thnx for your reply

              I installed the package yesterday, and today I was able to install via the muon interface the updates that were just released. So, problem solved!

              To sum things up for future reference:

              a) Whenever you disable the Strigi desktop indexer and the Nepomuk Semantic Desktop, two popup errors appear a little after startup. "Mail dispatcher Agent..." and another one I can't remember. To get rid of these, click on your system tray the little arrow pointing up to Show hidden icons. Right click on Akonadi and select configure. Disable the Akonadi server, Apply, Ok. No more popups in the new reboots Do not under any circumstances uninstall nepomuk (it is mentioned on those errors but don't try to remove it) as it has valuable system dependencies.

              b) If you get stuck before the login screen at startup, Ctrl Alt F2 sends you to the command prompt login. After you login, you can sudo apt-get reinstall, or reconfigure anything that causes you problems.

              c) If you cant update using the package manager, use
              sudo apt-get update
              sudo apt-get upgrade


              (many users prefer sudo apt-get dist-upgrade, but it has other effects too. read reply #5)

              Thanks to everyone who helped me here, all issues solved

              PS: If it works, don't fix it. That actually goes to myself

              Comment

              Working...
              X