On Tue, 23 May 2006, Paul Menzel wrote: > So as I see it, killing just hpssd and starting it manually lets > hp-toolbox start. Then there is also something written in hpssd.port > and .pid. (1) > > Killing hpssd and hpiod and starting both fails.
Hmm, add a "sleep 1" in the /etc/init.d/hplip script, just at the beginning of do_start(). Does that fix the issue? If it does not, then please do: (as root) Stop hplip (/etc/init.d/hplip stop). strace -o /tmp/hplip-full-strace.txt -f -F -ttt /etc/init.d/hplip start Then please remove any possible sensitive information (passwords?) in /tmp/hplip-full-strace.txt, bzip2 or gzip it, and mail it to me directly. > I tried to print something in situation (1) from gedit, but it does not > print. It shows the job in lpq and in hp-toolbox: This is bad. If both hpiod and hpssd are working, you should be able to print and do everything just fine. Anything on syslog? On the CUPS log? I like to use hp-levels and hp-info as ways to detect if hpssd and hpiod are actually working. Do they output anything useful for you (when both daemons are indeed running) ? > sandclock & 23.05.2006 & 00:13:00 & paul & 500 & The printer has started > a print-job. Trying to cancel the job crashes the toolbox. Eh, I had never tried killing a job from there. Works fine here, though. No crashes. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
