Find the answer to your Linux question:
Page 1 of 3 1 2 3 LastLast
Results 1 to 10 of 23
I really need help with this. While trying to uninstall a user-to-user file sharing app on Fedora 17, I accidentally uninstalled gvfs, the gnome desktop vital files. I attempted to ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Oct 2012
    Posts
    25

    Restore previous version / undo erase


    I really need help with this. While trying to uninstall a user-to-user file sharing app on Fedora 17, I accidentally uninstalled gvfs, the gnome desktop vital files. I attempted to undo this by using a command to re-install gvfs, but It didn't work properly and gnome is booting in fallback mode. I would like to restore it back to earlier today or possibly before then before I accidentally messed it up. Please help!!!

  2. #2
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    Hi,

    1. can you show the commands you ran when you uninstalled?

    2. can you show the commands you ran to install gvfs (et al)?

    3. have you tried manually changing from fall-back mode to regular mode via the control panel (accessed in the top right corner of the desktop)?

    4. what other symptoms are you experiencing, or is GNOME reverting to fall-back mode the only one?

    5. what is your video graphics adapter?

  3. #3
    Just Joined!
    Join Date
    Oct 2012
    Posts
    25
    1. sudo yum erase gvfs

    2. sudo yum install gvfs

    3. Yes, it didn't work

    4. Gnome has reverted to fallback mode, and I am getting an error notification saying it has detected a problem

    5. I don't know my video graphics adapter, sorry.

    Thanks so much for offering your help so far, if you could help me resolve this issue I would be very appreciative

  4. #4
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    Quote Originally Posted by Mark25 View Post
    5. I don't know my video graphics adapter, sorry.
    try this command:
    Code:
    lspci|grep -i vga
    I ask that b/c I am thinking of suggesting that you (re-)install the latest Xorg drivers for your video card.

    I did not think gvfs would have anything to do w/fallback mode (more of a graphics hardware thing, I though), but hey, Fedora is on the hairy edge.

    also, have you tried a full system update?

    Code:
    sudo yum update

  5. #5
    Just Joined!
    Join Date
    Oct 2012
    Posts
    25
    it said

    Code:
    01:00.0 VGA compatible controller: nVidia Corporation G84M [Quadro NVS 140M] (rev a1)
    then, when i tried to run sudo yum update, it said

    Code:
    Loaded plugins: langpacks, presto, refresh-packagekit
    Resolving Dependencies
    --> Running transaction check
    ---> Package ibus-libpinyin.x86_64 0:1.4.92-1.fc17 will be updated
    ---> Package ibus-libpinyin.x86_64 0:1.4.93-1.fc17 will be an update
    ---> Package java-1.7.0-openjdk.x86_64 1:1.7.0.6-2.3.1.fc17.2 will be updated
    ---> Package java-1.7.0-openjdk.x86_64 1:1.7.0.9-2.3.3.fc17 will be an update
    ---> Package libpinyin.x86_64 0:0.7.91-1.fc17 will be updated
    ---> Package libpinyin.x86_64 0:0.7.92-1.fc17 will be an update
    ---> Package libpinyin-data.x86_64 0:0.7.91-1.fc17 will be updated
    ---> Package libpinyin-data.x86_64 0:0.7.92-1.fc17 will be an update
    ---> Package libsss_sudo.x86_64 0:1.8.4-14.fc17 will be updated
    ---> Package libsss_sudo.x86_64 0:1.8.5-2.fc17 will be an update
    ---> Package ql2500-firmware.noarch 0:5.06.05-1.fc17 will be updated
    ---> Package ql2500-firmware.noarch 0:5.08.00-1.fc17 will be an update
    ---> Package qt-x11.i686 1:4.8.2-4.fc17 will be updated
    ---> Package qt-x11.i686 1:4.8.2-7.fc17 will be an update
    ---> Package sane-backends.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package sane-backends-drivers-scanners.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends-drivers-scanners.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package sane-backends-libs.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends-libs.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package tzdata.noarch 0:2012d-1.fc17 will be updated
    ---> Package tzdata.noarch 0:2012f-1.fc17 will be an update
    ---> Package tzdata-java.noarch 0:2012d-1.fc17 will be updated
    ---> Package tzdata-java.noarch 0:2012f-1.fc17 will be an update
    ---> Package xorg-x11-drv-synaptics.x86_64 0:1.6.2-1.fc17 will be updated
    ---> Package xorg-x11-drv-synaptics.x86_64 0:1.6.2-2.fc17 will be an update
    ---> Package xorg-x11-xinit.x86_64 0:1.3.2-5.fc17 will be updated
    ---> Package xorg-x11-xinit.x86_64 0:1.3.2-7.fc17 will be an update
    --> Finished Dependency Resolution
    Error:  Multilib version problems found. This often means that the root
           cause is something else and multilib version checking is just
           pointing it that there is a problem. Eg.:
           
             1. You have an upgrade for qt-x11 which is missing some
                dependency that another package requires. Yum is trying to
                solve this by installing an older version of qt-x11 of the
                different architecture. If you exclude the bad architecture
                yum will tell you what the root cause is (which package
                requires what).
           
             2. You have multiple architectures of qt-x11 installed, but
                yum can only see an upgrade for one of those arcitectures.
                If you don't want/need both architectures anymore then you
                can remove the one with the missing update and everything
                will work.
           
             3. You have duplicate versions of qt-x11 installed already.
                You can use "yum check" to get yum show these errors.
           
           ...you can also use --setopt=protected_multilib=false to remove
           this checking, however this is almost never the correct thing to
           do as something else is very likely to go wrong (often causing
           much more problems).
           
           Protected multilib versions: 1:qt-x11-4.8.2-7.fc17.i686 != 1:qt-x11-4.8.2-4.fc17.x86_64
    [mburghard@trogdor ~]$ sudo yum install lspci|grep -i vga
    Error: Nothing to do
    [mburghard@trogdor ~]$ sudo yum update lspci|grep -i vga
    No Match for argument: lspci
    [mburghard@trogdor ~]$ clear
    
    [mburghard@trogdor ~]$ sudo yum update
    Loaded plugins: langpacks, presto, refresh-packagekit
    Resolving Dependencies
    --> Running transaction check
    ---> Package ibus-libpinyin.x86_64 0:1.4.92-1.fc17 will be updated
    ---> Package ibus-libpinyin.x86_64 0:1.4.93-1.fc17 will be an update
    ---> Package java-1.7.0-openjdk.x86_64 1:1.7.0.6-2.3.1.fc17.2 will be updated
    ---> Package java-1.7.0-openjdk.x86_64 1:1.7.0.9-2.3.3.fc17 will be an update
    ---> Package libpinyin.x86_64 0:0.7.91-1.fc17 will be updated
    ---> Package libpinyin.x86_64 0:0.7.92-1.fc17 will be an update
    ---> Package libpinyin-data.x86_64 0:0.7.91-1.fc17 will be updated
    ---> Package libpinyin-data.x86_64 0:0.7.92-1.fc17 will be an update
    ---> Package libsss_sudo.x86_64 0:1.8.4-14.fc17 will be updated
    ---> Package libsss_sudo.x86_64 0:1.8.5-2.fc17 will be an update
    ---> Package ql2500-firmware.noarch 0:5.06.05-1.fc17 will be updated
    ---> Package ql2500-firmware.noarch 0:5.08.00-1.fc17 will be an update
    ---> Package qt-x11.i686 1:4.8.2-4.fc17 will be updated
    ---> Package qt-x11.i686 1:4.8.2-7.fc17 will be an update
    ---> Package sane-backends.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package sane-backends-drivers-scanners.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends-drivers-scanners.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package sane-backends-libs.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends-libs.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package tzdata.noarch 0:2012d-1.fc17 will be updated
    ---> Package tzdata.noarch 0:2012f-1.fc17 will be an update
    ---> Package tzdata-java.noarch 0:2012d-1.fc17 will be updated
    ---> Package tzdata-java.noarch 0:2012f-1.fc17 will be an update
    ---> Package xorg-x11-drv-synaptics.x86_64 0:1.6.2-1.fc17 will be updated
    ---> Package xorg-x11-drv-synaptics.x86_64 0:1.6.2-2.fc17 will be an update
    ---> Package xorg-x11-xinit.x86_64 0:1.3.2-5.fc17 will be updated
    ---> Package xorg-x11-xinit.x86_64 0:1.3.2-7.fc17 will be an update
    --> Finished Dependency Resolution
    Error:  Multilib version problems found. This often means that the root
           cause is something else and multilib version checking is just
           pointing it that there is a problem. Eg.:
           
             1. You have an upgrade for qt-x11 which is missing some
                dependency that another package requires. Yum is trying to
                solve this by installing an older version of qt-x11 of the
                different architecture. If you exclude the bad architecture
                yum will tell you what the root cause is (which package
                requires what).
           
             2. You have multiple architectures of qt-x11 installed, but
                yum can only see an upgrade for one of those arcitectures.
                If you don't want/need both architectures anymore then you
                can remove the one with the missing update and everything
                will work.
           
             3. You have duplicate versions of qt-x11 installed already.
                You can use "yum check" to get yum show these errors.
           
           ...you can also use --setopt=protected_multilib=false to remove
           this checking, however this is almost never the correct thing to
           do as something else is very likely to go wrong (often causing
           much more problems).
           
           Protected multilib versions: 1:qt-x11-4.8.2-7.fc17.i686 != 1:qt-x11-4.8.2-4.fc17.x86_64
    Now what do I do?
    Last edited by atreyu; 10-18-2012 at 11:54 PM. Reason: fixed code tags

  6. #6
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    That multi-lib bit is disconcerting. Have you possibly enabled another Yum repository? Or have you manually installed some xorg rpms (via the rpm command)?

    You can check which repos are enabled with this command:
    Code:
    yum repolist
    Your best bet may be to remove all xorg-related packages and then re-run the yum update command.

  7. #7
    Just Joined!
    Join Date
    Oct 2012
    Posts
    25
    It said

    Code:
    Loaded plugins: langpacks, presto, refresh-packagekit
    google-chrome/primary                                    | 1.4 kB     00:00     
    google-chrome                                                               3/3
    repo id                    repo name                                      status
    fedora                     Fedora 17 - x86_64                             27,033
    google-chrome              google-chrome                                       3
    rpmfusion-free             RPM Fusion for Fedora 17 - Free                   449
    rpmfusion-free-updates     RPM Fusion for Fedora 17 - Free - Updates         370
    updates                    Fedora 17 - x86_64 - Updates                    9,374
    repolist: 37,229
    here's what it returned. Now what do I do?

  8. #8
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    Quote Originally Posted by Mark25 View Post
    It said

    Code:
    Loaded plugins: langpacks, presto, refresh-packagekit
    google-chrome/primary                                    | 1.4 kB     00:00     
    google-chrome                                                               3/3
    repo id                    repo name                                      status
    fedora                     Fedora 17 - x86_64                             27,033
    google-chrome              google-chrome                                       3
    rpmfusion-free             RPM Fusion for Fedora 17 - Free                   449
    rpmfusion-free-updates     RPM Fusion for Fedora 17 - Free - Updates         370
    updates                    Fedora 17 - x86_64 - Updates                    9,374
    repolist: 37,229
    here's what it returned. Now what do I do?
    okay, so you do have some other repos in there. nothing that should have caused your problem, though.

    did u install any xorg packages manually?

    if it is a yum repo problem, you can try another update command while telling yum to disable all but the official repos:
    Code:
    yum --disablerepo=* --enablerepo=fedora --enablerepo=updates update
    if that doesn't work, then we can try removing all your xorg packages like I previously mentioned.

  9. #9
    Just Joined!
    Join Date
    Oct 2012
    Posts
    25
    Code:
    Loaded plugins: langpacks, presto, refresh-packagekit
    google-chrome/primary                                    | 1.4 kB     00:00     
    google-chrome                                                               3/3
    repo id                    repo name                                      status
    fedora                     Fedora 17 - x86_64                             27,033
    google-chrome              google-chrome                                       3
    rpmfusion-free             RPM Fusion for Fedora 17 - Free                   449
    rpmfusion-free-updates     RPM Fusion for Fedora 17 - Free - Updates         370
    updates                    Fedora 17 - x86_64 - Updates                    9,374
    repolist: 37,229
    [mburghard@trogdor ~]$ yum --disablerepo=* --enablerepo=fedora --enablerepo=updates update
    Loaded plugins: langpacks, presto, refresh-packagekit
    You need to be root to perform this command.
    [mburghard@trogdor ~]$ sudo yum --disablerepo=* --enablerepo=fedora --enablerepo=updates update
    [sudo] password for mburghard: 
    Loaded plugins: langpacks, presto, refresh-packagekit
    Resolving Dependencies
    --> Running transaction check
    ---> Package ibus-libpinyin.x86_64 0:1.4.92-1.fc17 will be updated
    ---> Package ibus-libpinyin.x86_64 0:1.4.93-1.fc17 will be an update
    ---> Package java-1.7.0-openjdk.x86_64 1:1.7.0.6-2.3.1.fc17.2 will be updated
    ---> Package java-1.7.0-openjdk.x86_64 1:1.7.0.9-2.3.3.fc17 will be an update
    ---> Package libpinyin.x86_64 0:0.7.91-1.fc17 will be updated
    ---> Package libpinyin.x86_64 0:0.7.92-1.fc17 will be an update
    ---> Package libpinyin-data.x86_64 0:0.7.91-1.fc17 will be updated
    ---> Package libpinyin-data.x86_64 0:0.7.92-1.fc17 will be an update
    ---> Package libsss_sudo.x86_64 0:1.8.4-14.fc17 will be updated
    ---> Package libsss_sudo.x86_64 0:1.8.5-2.fc17 will be an update
    ---> Package ql2500-firmware.noarch 0:5.06.05-1.fc17 will be updated
    ---> Package ql2500-firmware.noarch 0:5.08.00-1.fc17 will be an update
    ---> Package qt-x11.i686 1:4.8.2-4.fc17 will be updated
    ---> Package qt-x11.i686 1:4.8.2-7.fc17 will be an update
    ---> Package sane-backends.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package sane-backends-drivers-scanners.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends-drivers-scanners.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package sane-backends-libs.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends-libs.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package tzdata.noarch 0:2012d-1.fc17 will be updated
    ---> Package tzdata.noarch 0:2012f-1.fc17 will be an update
    ---> Package tzdata-java.noarch 0:2012d-1.fc17 will be updated
    ---> Package tzdata-java.noarch 0:2012f-1.fc17 will be an update
    ---> Package xorg-x11-drv-synaptics.x86_64 0:1.6.2-1.fc17 will be updated
    ---> Package xorg-x11-drv-synaptics.x86_64 0:1.6.2-2.fc17 will be an update
    ---> Package xorg-x11-xinit.x86_64 0:1.3.2-5.fc17 will be updated
    ---> Package xorg-x11-xinit.x86_64 0:1.3.2-7.fc17 will be an update
    --> Finished Dependency Resolution
    Error:  Multilib version problems found. This often means that the root
           cause is something else and multilib version checking is just
           pointing it that there is a problem. Eg.:
           
             1. You have an upgrade for qt-x11 which is missing some
                dependency that another package requires. Yum is trying to
                solve this by installing an older version of qt-x11 of the
                different architecture. If you exclude the bad architecture
                yum will tell you what the root cause is (which package
                requires what).
           
             2. You have multiple architectures of qt-x11 installed, but
                yum can only see an upgrade for one of those arcitectures.
                If you don't want/need both architectures anymore then you
                can remove the one with the missing update and everything
                will work.
           
             3. You have duplicate versions of qt-x11 installed already.
                You can use "yum check" to get yum show these errors.
           
           ...you can also use --setopt=protected_multilib=false to remove
           this checking, however this is almost never the correct thing to
           do as something else is very likely to go wrong (often causing
           much more problems).
           
           Protected multilib versions: 1:qt-x11-4.8.2-7.fc17.i686 != 1:qt-x11-4.8.2-4.fc17.x86_64
    [mburghard@trogdor ~]$ clear
    
    [mburghard@trogdor ~]$ sudo yum --disablerepo=* --enablerepo=fedora --enablerepo=updates update
    Loaded plugins: langpacks, presto, refresh-packagekit
    Resolving Dependencies
    --> Running transaction check
    ---> Package ibus-libpinyin.x86_64 0:1.4.92-1.fc17 will be updated
    ---> Package ibus-libpinyin.x86_64 0:1.4.93-1.fc17 will be an update
    ---> Package java-1.7.0-openjdk.x86_64 1:1.7.0.6-2.3.1.fc17.2 will be updated
    ---> Package java-1.7.0-openjdk.x86_64 1:1.7.0.9-2.3.3.fc17 will be an update
    ---> Package libpinyin.x86_64 0:0.7.91-1.fc17 will be updated
    ---> Package libpinyin.x86_64 0:0.7.92-1.fc17 will be an update
    ---> Package libpinyin-data.x86_64 0:0.7.91-1.fc17 will be updated
    ---> Package libpinyin-data.x86_64 0:0.7.92-1.fc17 will be an update
    ---> Package libsss_sudo.x86_64 0:1.8.4-14.fc17 will be updated
    ---> Package libsss_sudo.x86_64 0:1.8.5-2.fc17 will be an update
    ---> Package ql2500-firmware.noarch 0:5.06.05-1.fc17 will be updated
    ---> Package ql2500-firmware.noarch 0:5.08.00-1.fc17 will be an update
    ---> Package qt-x11.i686 1:4.8.2-4.fc17 will be updated
    ---> Package qt-x11.i686 1:4.8.2-7.fc17 will be an update
    ---> Package sane-backends.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package sane-backends-drivers-scanners.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends-drivers-scanners.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package sane-backends-libs.x86_64 0:1.0.22-11.fc17 will be updated
    ---> Package sane-backends-libs.x86_64 0:1.0.23-4.fc17 will be an update
    ---> Package tzdata.noarch 0:2012d-1.fc17 will be updated
    ---> Package tzdata.noarch 0:2012f-1.fc17 will be an update
    ---> Package tzdata-java.noarch 0:2012d-1.fc17 will be updated
    ---> Package tzdata-java.noarch 0:2012f-1.fc17 will be an update
    ---> Package xorg-x11-drv-synaptics.x86_64 0:1.6.2-1.fc17 will be updated
    ---> Package xorg-x11-drv-synaptics.x86_64 0:1.6.2-2.fc17 will be an update
    ---> Package xorg-x11-xinit.x86_64 0:1.3.2-5.fc17 will be updated
    ---> Package xorg-x11-xinit.x86_64 0:1.3.2-7.fc17 will be an update
    --> Finished Dependency Resolution
    Error:  Multilib version problems found. This often means that the root
           cause is something else and multilib version checking is just
           pointing it that there is a problem. Eg.:
           
             1. You have an upgrade for qt-x11 which is missing some
                dependency that another package requires. Yum is trying to
                solve this by installing an older version of qt-x11 of the
                different architecture. If you exclude the bad architecture
                yum will tell you what the root cause is (which package
                requires what).
           
             2. You have multiple architectures of qt-x11 installed, but
                yum can only see an upgrade for one of those arcitectures.
                If you don't want/need both architectures anymore then you
                can remove the one with the missing update and everything
                will work.
           
             3. You have duplicate versions of qt-x11 installed already.
                You can use "yum check" to get yum show these errors.
           
           ...you can also use --setopt=protected_multilib=false to remove
           this checking, however this is almost never the correct thing to
           do as something else is very likely to go wrong (often causing
           much more problems).
           
           Protected multilib versions: 1:qt-x11-4.8.2-7.fc17.i686 != 1:qt-x11-4.8.2-4.fc17.x86_64
    Did it work?

  10. #10
    Trusted Penguin
    Join Date
    May 2011
    Posts
    4,353
    nope, didn't work :)

    oh, now I see: you have mixed i686 and x86_64bit packages. try removing that multi-lib package (you can reinstall it later)

    Code:
    rpm -e qt-x11 --nodeps
    there may be other packages, too, though. try that for starters, then re-run the update.

Page 1 of 3 1 2 3 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
  •