Synaptic Hangs

[bicol_willem]

28 October 2010

Hello Again,
    I'm still having the problem with Synaptic that I mentioned earlier. Actually, I've let my system sit with that last command running for over 48 hours.   Perhaps Synaptic is stuck in an infinite loop? May I have some more input on this please? Thanks.

Bonz

Hmm 48 hours ha ... That means you got to do something!    (No action, no reaction).
Got to say I also lost a few installs lately. There seems to be some growing weakness in synaptic but it could also be just "bad luck" for I never found out what was the cause. Synaptic has served me very well for a long time but ....
But back to you (you're not willing to give up your install I understand). Try a few things like a reboot, try to rebuild the db again following the instructions you found here. Maybe things clears out in the progress. Try to use a konsole and the apt-get update command followed by the apt-get dist-upgrade command.  With some "luck" in case of a error you might read there wassup. A filesystem check as well. (For that I use the lifeCD PMagic but all their own way.)
Maybe you did all that?  Then a rather quick fresh install seems the only way out here.

Edit: Oops!  OP is on job ...... where to hide?? 

[Bonzini]

28 October 2010

Hello Again,
    I'm still having the problem with Synaptic that I mentioned earlier. Actually, I've let my system sit with that last command running for over 48 hours.  Perhaps Synaptic is stuck in an infinite loop? May I have some more input on this please? Thanks.

Bonz

Your last two replies are telling us a story rather than showing us useful information. Run the commands from a newly opened terminal, then copy/paste the results to your next reply, including the prompt, command, and output to the point of the hang, so we can see what you see, rather than your description of what you see.

28 October 2010

Hello Again,
    I'm still having the problem with Synaptic that I mentioned earlier. Actually, I've let my system sit with that last command running for over 48 hours.  Perhaps Synaptic is stuck in an infinite loop? May I have some more input on this please? Thanks.

Bonz

Hmm 48 hours ha ... That means you got to do something!    (No action, no reaction).
Got to say I also lost a few installs lately. There seems to be some growing weakness in synaptic but it could also be just "bad luck" for I never found out what was the cause. Synaptic has served me very well for a long time but ....
But back to you (you're not willing to give up your install I understand). Try a few things like a reboot, try to rebuild the db again following the instructions you found here. Maybe things clears out in the progress. Try to use a konsole and the apt-get update command followed by the apt-get dist-upgrade command.  With some "luck" in case of a error you might read there wassup. A filesystem check as well. (For that I use the lifeCD PMagic but all their own way.)
Maybe you did all that?  Then a rather quick fresh install seems the only way out here.

Edit: Oops!  OP is on job ...... where to hide?? 

28 October 2010

Morning! And Ah! My humble apologies. I sometimes forget that people can't look over my shoulder.  Anyway, here is the output from the new konsole that I opened:

[chris@localhost ~]$ su
Password:
[root@localhost chris]# rm -f /var/lib/rpm/_db*
[root@localhost chris]#
[root@localhost chris]# rpm -vv --rebuilddb
warning: waiting for transaction lock on /var/lib/rpm/__db.000

Question: Should I close the first konsole? 'Nother question: What's a lifeCD PMmagic?

Bonz

[Old-Polack]

28 October 2010

Morning! And Ah! My humble apologies. I sometimes forget that people can't look over my shoulder.  Anyway, here is the output from the new konsole that I opened:

[chris@localhost ~]$ su
Password:
[root@localhost chris]# rm -f /var/lib/rpm/_db*
[root@localhost chris]#
[root@localhost chris]# rpm -vv --rebuilddb
warning: waiting for transaction lock on /var/lib/rpm/__db.000

Question: Should I close the first konsole? 'Nother question: What's a lifeCD PMmagic?

Bonz

Yes, definitely! Close both terminals, wait a bit, then open a fresh one and try again. The lock file should then be released/available so the second command can run to completion.

[Bonzini]

28 October 2010

Hi there. I did the suggestion Old-Polack wrote about. And here is the screen after thirty minutes:

[chris@localhost ~]$ su
Password:
su: incorrect password
[chris@localhost ~]$ su
Password:
[root@localhost chris]# rm -f var/lib/rpm/_db*
[root@localhost chris]# rpm -vv --rebuilddb
D: rebuilding database /var/lib/rpm into /var/lib/rpmrebuilddb.3002
D: creating directory /var/lib/rpmrebuilddb.3002
D: opening old database with dbapi 3
D: opening  db environment /var/lib/rpm/Packages mpool:joinenv

BTW: I had to reboot, I pressed too many buttons. 

[Old-Polack]

28 October 2010

Hi there. I did the suggestion Old-Polack wrote about. And here is the screen after thirty minutes:

[chris@localhost ~]$ su
Password:
su: incorrect password
[chris@localhost ~]$ su
Password:
[root@localhost chris]# rm -f var/lib/rpm/_db*
[root@localhost chris]# rpm -vv --rebuilddb
D: rebuilding database /var/lib/rpm into /var/lib/rpmrebuilddb.3002
D: creating directory /var/lib/rpmrebuilddb.3002
D: opening old database with dbapi 3
D: opening  db environment /var/lib/rpm/Packages mpool:joinenv

BTW: I had to reboot, I pressed too many buttons.  

The command given above is incorrect. The files wanting to be removed have a double underscore at the beginning of the file name, not a single underscore as you have shown. Also there is no / before var/lib/rpm, and that too needs to be there. (/var/lib/rpm/__db.*) Therefore, the first command does nothing and the damaged files are still there.

Again start fresh with a new terminal, after closing the current one. At the root prompt, enter;

[root@localhost chris]# ls -l /var/lib/rpm |grep db

I get this as a response; you should get something similar.

[root@littleboy ~]# ls -l /var/lib/rpm |grep db
-rw-r--r-- 1 root root            0 2010-09-06 15:18 __db.000
-rw-r--r-- 1 root root     24576 2010-10-28 15:48 __db.001
-rw-r--r-- 1 root root   139264 2010-10-28 15:48 __db.002
-rw-r--r-- 1 root root   663552 2010-10-28 15:48 __db.003

Now try the correct command to remove the files.

[root@localhost chris]# rm -f /var/lib/rpm/__db.*

Then try the ls -l command again.

[root@localhost chris]# ls -l /var/lib/rpm |grep db
[root@localhost chris]#

This time there should be just a return to the prompt. If this is what you get, then you are ready to issue the command to rebuild the database.

[root@localhost chris]# rpm -vv --rebuilddb

Try all that, and post your results.

[seahawk5]

I have only been skimming through this subject as I too had this problem of synaptic hanging so if this answer has been posted please forgive me. I fixed it by following Texstar's method (Thanks heaps Texstar ) in Tips and Tricks,  How to repair a corrupted RPM database   I just copied and pasted in a console
exactly how he wrote it and "bang" my synaptic started working again after hanging for days. Hope this helps anybody that has this problem. Adrian

[bicol_willem]

What's a lifeCD PMmagic?

http://partedmagic.com/

[Bonzini]

29 October 2010

Hi there!
    It worked!! I did exactly as you said:

[root@localhost chris]# ls -l /var/lib/rpm |grep db
-rw-r--r-- 1 root root        0 2010-09-06 15:18 __db.000
-rw-r--r-- 1 root root    24576 2010-10-28 15:48 __db.001
-rw-r--r-- 1 root root   139264 2010-10-28 15:48 __db.002
-rw-r--r-- 1 root root   663552 2010-10-28 15:48 __db.003

[root@localhost chris]# rm -f /var/lib/rpm/__db.*
[root@localhost chris]# ls -l /var/lib/rpm |grep db
[root@localhost chris]# rpm -vv --rebuilddb

 and got pages of output:

D:  read h#     848 Header SHA1 digest: OK (ee5d79403f646c2dd6dea8c6aaba1a0c27cfb5d3)
D:   +++ h#    1570 Header SHA1 digest: OK (ee5d79403f646c2dd6dea8c6aaba1a0c27cfb5d3)
D: adding "libredland0" to Name index.
D: adding 2 entries to Basenames index.
D: adding "System/Libraries" to Group index.
D: adding 33 entries to Requirename index.
D: adding 2 entries to Providename index.
D: adding "/usr/lib/" to Dirnames index.
D: adding 33 entries to Requireversion index.
D: adding 2 entries to Provideversion index.
D: adding 1 entries to Installtid index.
D: adding 1 entries to Sigmd5 index.
D: adding "ee5d79403f646c2dd6dea8c6aaba1a0c27cfb5d3" to Sha1header index.
D: adding 2 entries to Filedigests index.
D:  read h#     864 Header SHA1 digest: OK (65b09272c62f3861dcbbc44308ee09413e47a5cb)
D:   +++ h#    1571 Header SHA1 digest: OK (65b09272c62f3861dcbbc44308ee09413e47a5cb)
D: adding "x11-driver-video-v4l" to Name index.
D: adding 5 entries to Basenames index.
D: adding "System/X11" to Group index.
D: adding 7 entries to Requirename index.
D: adding 2 entries to Providename index.
D: adding 4 entries to Dirnames index.
D: adding 7 entries to Requireversion index.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


D: verified db index       /var/lib/rpmrebuilddb.4447/Group
D: closed   db index       /var/lib/rpmrebuilddb.4447/Basenames
D: verified db index       /var/lib/rpmrebuilddb.4447/Basenames
D: closed   db index       /var/lib/rpmrebuilddb.4447/Name
D: verified db index       /var/lib/rpmrebuilddb.4447/Name
D: closed   db index       /var/lib/rpmrebuilddb.4447/Packages
D: closed   db environment /var/lib/rpmrebuilddb.4447/Packages
D: verified db index       /var/lib/rpmrebuilddb.4447/Packages
D: removing directory /var/lib/rpmrebuilddb.4447
[root@localhost chris]#

After all that happened I am now able to get in to Synaptic! Thank you very, very much for your time and patience. I hope to learn more as I go! Ciao belle!

Bonz