Restore previous version / undo erase

[Mark25]

at first It said

error: "qt-x11" specifies multiple packages:
  qt-x11-4.8.2-4.fc17.x86_64
  qt-x11-4.8.2-4.fc17.i686
  qt-x11-4.8.2-7.fc17.x86_64

So I tried

sudo rpm -e qt-x11-4.8.2-7.fc17.x86_64
[sudo] password for mburghard: 
/sbin/ldconfig: file /lib/libQtDesigner.so.4.8.2;507b0eb8 is truncated

[atreyu]

at first It said

error: "qt-x11" specifies multiple packages:
  qt-x11-4.8.2-4.fc17.x86_64
  qt-x11-4.8.2-4.fc17.i686
  qt-x11-4.8.2-7.fc17.x86_64

you are on x86_64, not i686, right? if so, then try:

rpm -e --nodeps qt-x11-4.8.2-4.fc17.i686

that truncated error is new to me. it does not sound good. anything in your /var/log/messages that looks suspicious/interesting?

for completeness, post your arch, distro, and version.

[Mark25]

the console returned

qt-x11-4.8.2-4.fc17.i686 is truncated

I can't seem to get the /var command to work. Maybe I'm typing it wrong. Could you give me the specific command to open up the /var stuff? Also, after it said the code above, I typed the same command you gave again, and it said that qt-x11-4.8.2-4fc17.i686 was erased.

[atreyu]

the console returned

qt-x11-4.8.2-4.fc17.i686 is truncated

i guess it is complaining about a corrupt file in the package, but you hopefully should still be able to remove the package with the rpm command.

I can't seem to get the /var command to work. Maybe I'm typing it wrong. Could you give me the specific command to open up the /var stuff?

Sorry, I should have been more clear. What I meant was to check your syslog, which is typically saved to this file:

/var/log/messages

you can open the file with an editor, but it is constantly being written to, so you're better off using cat or tail, e.g.:

tailf /var/log/messages

that command will send the entire contents of the file to STDOUT (your screen), and keep it open, so that any new stuff will appear at the bottom of the screen. So it is handy, when trouble-shooting, to open a terminal, su to root and run a tail of this log. Then in another terminal, do your actual trouble-shooting commands.

another handy thing to do is search the file for something particular, using grep, e.g.:

grep -i rpm /var/log/messages

so have you tried to yum update again?

[Mark25]

the grep command returned

yum[5110]: Updated: rpmfusion-free-release-17.0.3-1.noarch

The tailf command returned an insanely long list which I can't copy paste. I then updated, which surprisingly actually worked, but I rebooted and it still booted in fallback mode. So close... I just reinstalled the gnome-panel, hoping it might help. What should I do now?

[Mark25]

I also just figured out my graphics driver. It's Gallium 0.4 on NV86.

[atreyu]

is the Fedora nvidia xorg driver installed? check with:

rpm -qv xorg-x11-drv-nouveau

if not, install it with:

yum update xorg-x11-drv-nouveau

also, show your kernel boot args with this command:

cat /proc/cmdline

there is also the option of installing NVidia's closed binary driver (if you're okay w/that). I usually have no problems with it, but I have run of the mill nvidia hardware.

[Mark25]

Console returned

xorg-x11-drv-nouveau-0.0.16-37.20120306gitf5d1cd2.fc17.x86_64

after entering cat command I got

BOOT_IMAGE=/vmlinuz-3.6.1-1.fc17.x86_64 root=/dev/mapper/vg_trogdor-lv_root ro rd.lvm.lv=vg_trogdor/lv_swap rd.md=0 rd.dm=0 SYSFONT=True rd.lvm.lv=vg_trogdor/lv_root KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet

[atreyu]

Try adding modesetting and dri drivers:

yum update mesa-dri-drivers  xorg-x11-drv-modesetting

then reboot.

also, post your xorg.conf file, if you have one. it would be here:

/etc/X11/xorg.conf

also, post your xorg log. it is big, but we may need it. it should be here:

/var/log/Xorg.0.log

[Mark25]

sudo yum update mesa-dri-drivers xorg-xll-drv-modsetting
[sudo] password for mburghard: 
Loaded plugins: langpacks, presto, refresh-packagekit
No Match for argument: xorg-xll-drv-modsetting
No package xorg-xll-drv-modsetting available.
No Packages marked for Update

returned for yum update command. It kept telling me the others weren't valid commands.