On Friday 11 July 2008 15:59:24 Rex Dieter wrote: > Anne Wilson wrote: > >> One brute force method is to reset your prefs > >> mv ~/.kde ~/.kde.BAK > >> and then (potentially) start restoring bits of it until you're back > >> where you want to be or you retrigger the bug, whichever comes first. > > > > Thanks, Rex. That's exactly what I have done (not done the restores yet, > > though). It begs the question of how this happened, though. It does > > appear to be related to the updates that I did yesterday, and apparently > > I'm not the > > only one to have experienced it. Bug #454055 reporter seems to think > > that it > > is related to xorg-x11-drv-i810-2.3.2-2.fc9.i386. I've added my bit, in > > the hope that it brings light to the devs/packagers :-) > > Yes, you're now the 3rd person I've seen report problems like that since > the xorg update. Methinks there's a smoking gun here. > I've restored most of the config files that I'm likely to need, and everything is still fine here, so at least that's good news. Anne
Attachment:
signature.asc
Description: This is a digitally signed message part.
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
