Results 1 to 4 of 4

Thread: Apper - "A problem that we were not expecting has occurred."

  1. #1
    Join Date
    Jan 2014
    Location
    San Jose City, PH.
    Posts
    118

    Default Apper - "A problem that we were not expecting has occurred."

    While running apper to install downloaded software I had a power failure. Before that apper worked just fine, but now it always fails to install anything.

    I get an error message that says "A problem that we were not expecting has occurred."
    In the details section it says this:
    Code:
    [PK_TMP_DIR|dir:///var/tmp/TmpDir.S40Win] Repository already exists.
    An ls listing shows no directory named TmpDir.S40Win in /var/tmp, and every time I try to run apper that directory name is different in the error details.

    How can this be fixed so I can resume using apper to install software?

    [IMG]file:///home/russ/Pictures/Apper.problem.png[/IMG]

  2. #2

    Default Re: Apper - "A problem that we were not expecting has occurred."

    Quote Originally Posted by rwbehne1 View Post
    How can this be fixed so I can resume using apper to install software?
    Please post your repo list, as that sounds like a problem there:
    Code:
    zypper lr -d

  3. #3
    Join Date
    Jan 2014
    Location
    San Jose City, PH.
    Posts
    118

    Default Re: Apper - "A problem that we were not expecting has occurred."

    Quote Originally Posted by wolfi323 View Post
    Please post your repo list, as that sounds like a problem there:
    Code:
    zypper lr -d
    You're right. I found and corrected the problem just before becoming aware of your reply. Somehow, a repository entry named "PK_TMP_DIR" was created with a location of "dir:///var/tmp/TmpDir.S40Win", a non-existent directory. I removed the entry and that has fixed the problem.

    PROBLEM SOLVED!

    ...although I can't imagine how that bogus repository entry got created in the first place.

    Thanks for the help!

  4. #4

    Default Re: Apper - "A problem that we were not expecting has occurred."

    Quote Originally Posted by rwbehne1 View Post
    ...although I can't imagine how that bogus repository entry got created in the first place.
    Hm. Looks like something that gets created (and maybe added as a repo) when you install rpm packages not coming from a standard repo. F.e. when you open a .rpm file in your file manager to install it.

Posting Permissions

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