Results 1 to 6 of 6

Thread: Checking Conflict File Function

  1. #1

    Default Checking Conflict File Function

    Hellow Everybody

    ---------------------------------------------------------------------------

    My PC

    GIGABYTE GA-F2A88X-UP4 Rev3.0 BIOS F8a
    AMD A10-7800
    A-DATA DDR3-2133 4096MBx2
    SanDisk SDSSDA-240G-J26C SATA3 240GB SSD
    TOSHIBA DT01ACA300 SATA3 3.0TB HDD
    etc

    OS
    openSUSE Tumbleweed AMD64 Xfce JPN
    and
    Windows 10 Pro Creators Update AMD64 ENU

    ---------------------------------------------------------------------------

    I use zypper command : zypper ref -> zypper inr -> zypper up

    Checking Conflict File Function takes 100% cpu usage any 1 of 4 cpu core about 8 or 10 minutes

    Download and Install works fine

    Is it meanig "Checking Conflict File Function is a Single Thread Function"?
    Do i have any mistakes?

    Why i do not use zypper dup? -> I get a lot of message meaning "No one makes required packages for GIMP, DVDStyler,etc"

    Sorry poor my English

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,795

    Default Re: Checking Conflict File Function

    You can bring Tumbleweed up-to-date only with
    Code:
    zypper dup
    Using zypper up will not do what you need and in the end it may break things.
    Henk van Velden

  3. #3

    Default Re: Checking Conflict File Function

    Hellow hcvv

    I understand do not use "zypper ref" and "zypper inr" on Tumbleweed

    I will use "zypper dup -d" and "zypper dup"

    Thanks hcvv

  4. #4
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,795

    Default Re: Checking Conflict File Function

    Doing zypper ref is no problem. It only refreshes the information about the enabled repos.

    Doing zypper inr is not done by most, nor very often, because there will normally be nothing to install.

    It is zypper up that should NOT be done with Tumbleweed.

    ================

    I think first thing you should do is
    Code:
    zypper dup
    to get a fully updated Tumbleweed.
    Henk van Velden

  5. #5

    Default Re: Checking Conflict File Function

    Hellow hcvv

    After todays first OS boot, I did zypper ref -> zypper dup -d -> zypper dup -> OS Restart

    Checking Conflict File -> Take just a few seconds, not take CPU Core 100% Usage any 1 of 4 CPU Core, works fine

    Download and Install -> Of course works fine

    Now I have no problem
    Many Thanks

  6. #6
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,795

    Default Re: Checking Conflict File Function

    Nice it works now. You are welcome and enjoy openSUSE.
    Henk van Velden

Posting Permissions

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