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

Thread: CONFLICTS DURING UPDATING

  1. #1

    Default CONFLICTS DURING UPDATING

    During updating I get the following message. Which option should I choose ?

    #### YaST2 conflicts list - generated 2010-07-09 12:46:43 ####

    patch:kde-4.3.5-1974.noarch conflicts with kwin.i586 < 4.3.5-0.2.1 provided by kwin-4.3.1-7.5.i586

    [ ] Following actions will be done:
    install kwin-4.4.5-466.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install kdebase4-runtime-4.4.5-216.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libkde4-4.4.5-270.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-x11-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install kdelibs4-4.4.5-270.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install oxygen-icon-theme-4.4.5-59.1.noarch (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install python-kde4-4.4.5-147.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libQtWebKit4-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install kdelibs4-core-4.4.5-270.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libstrigi0-0.7.2-35.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install soprano-2.4.4-75.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install oxygen-icon-theme-scalable-4.4.5-59.1.noarch (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install python-kdebase4-4.4.5-471.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-devel-doc-data-4.6.3-122.2.noarch (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install qt4-qtscript-0.1.0-9.6.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-sql-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-qt3support-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-devel-doc-4.6.3-120.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-devel-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqca2-2.0.2-16.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install kde4-filesystem-4.4.5-105.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libkdecore4-4.4.5-270.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install strigi-0.7.2-35.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libsoprano4-2.4.4-75.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-sql-sqlite-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-sql-postgresql-4.6.3-122.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-sql-mysql-4.6.3-122.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install soprano-backend-redland-2.4.4-75.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install python-sip-4.10.2-40.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install python-qt4-4.7.3-45.8.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    [ ] Following actions will be done:
    do not install patch:kde-4.3.5-1974.noarch
    do not install patch:kde4-kdm-2134.noarch
    [ ] replacement of compiz-kde4-0.7.8-10.18.i586 with kwin-4.3.5-0.3.1.i586




    #### YaST2 conflicts list END ###
    Thanks.

  2. #2
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,742
    Blog Entries
    20

    Default Re: CONFLICTS DURING UPDATING

    Quote Originally Posted by kkphani View Post
    During updating I get the following message. Which option should I choose ?

    #### YaST2 conflicts list - generated 2010-07-09 12:46:43 ####

    patch:kde-4.3.5-1974.noarch conflicts with kwin.i586 < 4.3.5-0.2.1 provided by kwin-4.3.1-7.5.i586

    [X ] Following actions will be done:
    install kwin-4.4.5-466.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install kdebase4-runtime-4.4.5-216.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libkde4-4.4.5-270.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-x11-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install kdelibs4-4.4.5-270.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install oxygen-icon-theme-4.4.5-59.1.noarch (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install python-kde4-4.4.5-147.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libQtWebKit4-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install kdelibs4-core-4.4.5-270.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libstrigi0-0.7.2-35.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install soprano-2.4.4-75.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install oxygen-icon-theme-scalable-4.4.5-59.1.noarch (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install python-kdebase4-4.4.5-471.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-devel-doc-data-4.6.3-122.2.noarch (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install qt4-qtscript-0.1.0-9.6.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-sql-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-qt3support-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-devel-doc-4.6.3-120.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-devel-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqca2-2.0.2-16.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install kde4-filesystem-4.4.5-105.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libkdecore4-4.4.5-270.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install strigi-0.7.2-35.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libsoprano4-2.4.4-75.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-sql-sqlite-4.6.3-120.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-sql-postgresql-4.6.3-122.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install libqt4-sql-mysql-4.6.3-122.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install soprano-backend-redland-2.4.4-75.1.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install python-sip-4.10.2-40.2.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    install python-qt4-4.7.3-45.8.i586 (with vendor change)
    openSUSE --> obs://build.opensuse.org/KDE
    [ ] Following actions will be done:
    do not install patch:kde-4.3.5-1974.noarch
    do not install patch:kde4-kdm-2134.noarch


    #### YaST2 conflicts list END ###
    Thanks.
    As indicated in BOLD
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  3. #3

    Default Re: CONFLICTS DURING UPDATING

    Quote Originally Posted by caf4926 View Post
    As indicated in BOLD
    Thanks for promt resonse

  4. #4

    Default Re: CONFLICTS DURING UPDATING

    I updated making the selection as stated. But it is a diaster.
    When I boot I have only terminal window and a bug message says

    WE ARE SORRY. PLASMA WORKSPACE CLOSED UNEXPECTEDLY.
    Excutable: kdeinit4 PID 3813 signal 11

    and then a kde message dialog comes up with the message

    No System tray detected on this system
    Unable to start, existing.

    What should I do?

  5. #5
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,742
    Blog Entries
    20

    Default Re: CONFLICTS DURING UPDATING

    Boot to Yast this way
    Picasa Web Albums - caf4926 - YaST level3

    In Software Repositories, disable all repos except:
    OSS, NON-OSS, Updates

    Then when done F9 to quit yast

    Now do this at the command line prompt

    zypper dup
    That should get you back to square one. Then if like we can look at updating kde and multi-media
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  6. #6

    Default Re: CONFLICTS DURING UPDATING

    Thanks.
    Did what you asked for. KDE is back. But there are more serious problems.
    Key board does not function. kinternet icon is shown as a small spot on desktop.
    None of the windows displayed with its usual min.max and cancel icons.
    In fact it seems it has become useless.

  7. #7
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,742
    Blog Entries
    20

    Default Re: CONFLICTS DURING UPDATING

    Try creating a new user account login, using the same yast as before
    login with that account, how is it?
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  8. #8

    Default Re: CONFLICTS DURING UPDATING

    Yes created new account using yest as before and logged in new acoount.
    The problem remains one and same as before.
    I think now I have enough of Suse experience and give it up.

  9. #9
    Join Date
    Jun 2008
    Location
    The English Lake District. UK - GMT/BST
    Posts
    36,742
    Blog Entries
    20

    Default Re: CONFLICTS DURING UPDATING

    Your experience should lead to enlightenment.
    Maybe that would include sticking with the default repositories +packman until you have sufficient experience.
    It's worth trying again. Just give some thought to how SUSE was after first installing....was it good for you then?
    Leap 15.1_KDE
    My Articles Was I any help? If yes: Click the star below

  10. #10
    Carlos E. R. NNTP User

    Default Re: CONFLICTS DURING UPDATING

    On 2010-07-09 15:56 GMT kkphani wrote:

    >
    > Yes created new account using yest as before and logged in new
    > acoount. The problem remains one and same as before.
    > I think now I have enough of Suse experience and give it up.


    Linux is not for the faint of mind.

    If you want to try Linux, you have to be serious and work at it.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 11.2 x86_64 "Emerald" GM (Elessar))


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
  •