How long did you let YAST sit before you killed it? It make take a long time to work after you rebuild the DB. I think it took about 15 minutes for me once. -----Original Message----- From: Dan Weisenstein [mailto:dan@tesoro.com] Sent: Friday, April 30, 2004 3:12 PM To: suse-linux-e@suse.com Subject: Re: [SLE] YaST2 Sick Jim Sabatke wrote:
Dan Weisenstein wrote:
In the course of playing around with Evolution, adding and removing things, etc. yast2 has become partially broken. If I attempt to do anything related to adding or removing packages, it just freezes up. I can do anything with services, hardware, etc. with no problems.
What could be wrong? I'm thinking something might be damaged with respect to the rpm database? If so, can it be repaired?
Thanks - Dan
You could try rebuilding the database. # rpm --rebuilddb
Well, that helped somewhat. Now, I start yast2, click on Add/Remove Software, and it starts: then a dialog starts that says "Checking Dependecies" ??? I haven't even selected anything to add or remove... The dialog box stays there... window is now frozen. It's process is now sucking up 95% of the CPU.... Any other ideas? I'll have to kill -9 it to get it to stop. Thanks- Dan -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-----Original Message----- From: Dan Weisenstein [mailto:dan@tesoro.com] Sent: Friday, April 30, 2004 3:12 PM To: suse-linux-e@suse.com Subject: Re: [SLE] YaST2 Sick
Jim Sabatke wrote:
Dan Weisenstein wrote:
In the course of playing around with Evolution, adding and removing things, etc. yast2 has become partially broken. If I attempt to do anything related to adding or removing packages, it just freezes up. I can do anything with services, hardware, etc. with no problems.
What could be wrong? I'm thinking something might be damaged with respect to the rpm database? If so, can it be repaired?
Thanks - Dan
You could try rebuilding the database. # rpm --rebuilddb
Well, that helped somewhat. Now, I start yast2, click on Add/Remove Software, and it starts: then a dialog starts that says "Checking Dependecies" ??? I haven't even selected anything to add or remove... The dialog box stays there... window is now frozen. It's process is now sucking up 95% of the CPU.... Any other ideas? I'll have to kill -9 it to get it to stop.
Thanks- Dan
Dalziel, Josh wrote:
How long did you let YAST sit before you killed it? It make take a long time to work after you rebuild the DB. I think it took about 15 minutes for me once.
Well, I let it run for about 20 minutes or so. I'll let it run over the weekend as I'm about to leave work... Let me relay the rest of the story: This all started when I did a (command line) 'rpm -Fvh' on a new download of evolution (v 1.4.5) That hung for 2 hours. I couldn't even kill it. Had to reboot. That started this whole chain of events. Something evidently got damaged... Dan
Dan Weisenstein wrote:
-----Original Message----- From: Dan Weisenstein [mailto:dan@tesoro.com] Sent: Friday, April 30, 2004 3:12 PM To: suse-linux-e@suse.com Subject: Re: [SLE] YaST2 Sick
Jim Sabatke wrote:
Dan Weisenstein wrote:
In the course of playing around with Evolution, adding and removing things, etc. yast2 has become partially broken. If I attempt to do anything related to adding or removing packages, it just freezes up. I can do anything with services, hardware, etc. with no problems.
<snip>
Let me relay the rest of the story: This all started when I did a (command line) 'rpm -Fvh' on a new download of evolution (v 1.4.5) That hung for 2 hours. I couldn't even kill it. Had to reboot. That started this whole chain of events. Something evidently got damaged...
Dan
Dan, Had the same problem once with a faulty rpm. Solved it then by using the ncurses yast (use ctrl-alt-f2 to go to a text terminal, login as root and launch yast). This one worked and i could remove the faulty package. Also hung on dependency chacking then. Otherwise get a better evolution rpm and install it manually with rpm -Uhv <package> --force. It should remove the other from the rpm database. Peter Vollebregt
participants (3)
-
Dalziel, Josh -
Dan Weisenstein -
Peter Vollebregt