<SOLVED> Synaptic Problems

[joechimp]

I was wondering if anyone else was having Synaptic problems today? It won't load at all for me after an upgrade yesterday when it worked fine.

[menotu]

You've tried from the Konsole ?   Restarted?

I notice that Synaptic sometimes doesn't "release" itself properly and I have to Ctrl+Esc and kill it, before a new session can start.

[joechimp]

did both those things. No go.
 Well, I just tried from Konsole again and it tells me that another Synaptic is running. So it appears I need to kill that first. It didn't say that before, It just didn't load.
Thanks.

[AndrzejL]

HTH...

Andy

[joechimp]

Thanks Andy. If what I am going to do next doesn't work, that thread has lots of options.

[longtom]

Also struggling with synaptic today.

My doctor recommended this:  http://www.pclinuxos.com/forum/index.php/topic,80839.0.html

I can only try tonight - hope you get it fixed earlier!!

[melodie]

Hi,

A few commands to find the pid of a program:

as root:

Code: [Select]

# ps ax | grep synaptic
 3368 ?        SLl    0:01 gksu -u root /usr/sbin/synaptic
 3374 pts/0    Ss+    0:00 /bin/su root -c /usr/lib/libgksu/gksu-run-helper "/usr/sbin/synaptic"
 3380 pts/0    S+     0:00 /usr/lib/libgksu/gksu-run-helper /usr/sbin/synaptic
 3385 pts/0    S+     0:12 /usr/sbin/synaptic
 3468 pts/1    S+     0:00 grep --color=auto synaptic

(then : kill -9 <pid number> where here there are 5 numbers: forget the one related to grep itself, start by killing process numbers starting from the latest children and go up to the parent's )

or with lsof:

Code: [Select]

# lsof /usr/sbin/synaptic
COMMAND   PID USER  FD   TYPE DEVICE SIZE/OFF NODE NAME
synaptic 3385 root txt    REG    8,6   895368 1420 /usr/sbin/synaptic
or "killall synaptic" and then check with the above commands that no child process is left.

[Texstar]

Well you can always put the lime in the coconut den you feel better.

Put The Lime In The Coconut - Harry Nilsson

[ebvt]

This happened to me for the first time today. I wanted to upgrade and put in the root PW, but on clicking enter the log-in screen just disappeared. After I had tried twice more, I thought I was entering the wrong PW  (my wife's computer). So I entered another PW, but on that attempt it just told me that this was the wrong PW. So I did what I always do in case of emergency: I rebooted. After that, no problem. Go figure.... But thanks for all the possible solutions.

ebvt

[joechimp]

I put da lime in da coconut and I do feel better.


However, synaptic is still broke.

Actually just getting around to fixing it now. I was just wondering how long this usually takes to complete?

                                      rpm --rebuilddb

Thank you.

[uncleV]

Actually just getting around to fixing it now. I was just wondering how long this usually takes to complete?

                                      rpm --rebuilddb

You should wait it to finish. Don't know how long.

[joechimp]

I am at lest 30 minutes or more into it. I'm Just impatient I guess.

[uncleV]

30 minutes looks too much to me...
But you just have to wait. What else to do?

[menotu]

clicking enter the log-in screen just disappeared. After I had tried twice more, I thought I was entering the wrong PW  (my wife's computer). So I entered another PW, but on that attempt it just told me that this was the wrong PW.

This has happened to me in the past; when I'm at a command prompt screen (for a login) and it asks for my password but it never accepts it, and then methought hey, mebbe its switched to a USA keyboard so with a bit of trial and error trying to remember what the keys would be I worked it out and was able to login again.

[joechimp]

30 minutes looks too much to me...
But you just have to wait. What else to do?

It seems too long to me as well. Think I will wait 60 min. then abort.