I’m having a problem that Yast hangs when trying to install an rpm (I’m trying to install ‘meld’).
It sits there and does nothing after download (I’ve tried leaving it for a couple of hours). Checking ps -x gives me a ‘D’ in the stat column for the rpm -i command of the package yast is trying to install.
I end up having to kill -9 the pid and then aborting within yast (I can’t just abort in yast because I’m unable to click any of the buttons while it’s waiting)
I’ve tried rpm -qa which does provide a list of my installed packages and I’ve also tried rm -f /var/lib/rpm/__* ; rpm -vv --rebuilddb which does successfully rebuild my db.
However, after these, I do run into the same problems.
I’ve also tried db_verify Packages which doesn’t give any errors.
I know my first port of call should possibly have been to restart my computer, but I can’t do that until later on this evening because I’ve had it doing things. I just wanted to see if anyone had any other thoughts?
I’ll restart when my computer is free from what it’s doing and if that resolves I’ll close this
wildmanmatt adjusted his/her AFDB on Friday 14 Aug 2009 21:56 to write:
>
> I tried that when I first looked for meld…it stalls at 0% on
> “Installing meld-1.3.0-2.4.noarch.rpm”
>
>
What happens if you use the command line instead of YaST?
rpm -Ivh meld-1.3.0-2.4.noarch.rpm
Or even put --force on the end to see what output you get and force the
install but do beware there can be wyrms going that way but as it is only
one rpm I doubt it will mess anything up.
HTH
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum
Thanks for your help… The solutions posted didn’t seem to resolve the problems, but something seems to have done…
I said that I hadn’t restarted, well, I did.
However, that didn’t resolve the problem. I decided to get on with it and just leave rpms (hey, I can live with ./configure, make, make install I guess), but then after a second restart, I tried to install with YaST again and for some reason it just worked.
Maybe there was something stuck that just needed to be worked out?
wildmanmatt adjusted his/her AFDB on Saturday 22 Aug 2009 22:36 to write:
>
> However, that didn’t resolve the problem. I decided to get on with it
> and just leave rpms (hey, I can live with ./configure, make, make
> install I guess), but then after a second restart, I tried to install
> with YaST again and for some reason it just worked.
>
> Maybe there was something stuck that just needed to be worked out?
>
> Strange…
>
>
Could have been caused by a stale lock file on Yast that made the system
think that Yast was already running.
This can be caused by a crash and the file not being deleted.
HTH
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum