Intermittent CUPS startup at boot Lucid Lynx

[kentechy]

I have been having intermittent printing problems and am using Lucid Lynx at present. I have nailed it down to CUPS not starting properly on each boot. If it starts properly I will have my printer show up and it works. On some boots it is not there. This is in spite of it being listed in the boot-up manager. I have tried changing the priority higher and lower with no effect. If I boot up and the printer is missing I can start the CUPS service and the printer will then show up and print fine. I have been using Turbo-print for several versions of Ubuntu and am using it now as well. I also use a wireless print server. Could it be related to a delayed wireless network connection on some boots? I am pretty novice at Ubuntu but I can get around in Terminal pretty well. Any help would be appreciated. It seems like it should be a simple fix...yeah right!! Thanks in advance.

[Souris]

Hi, same problem here !!!

On bootup CUPS is often not loaded, but sometimes it is and then it works.

I don't use any print server, my CUPS server is on localhost.
I have a network printer (HP LaserJet 1320n) connected via HP Jetdirect : socket://192.168.0.126:9100
Everything is wired, no Wifi.

It is a vanilla lucid (new install)

Help apreciated!!!

[Morbius1]

I have a feeling that john newbuntu's post is going to be very useful until this problem is resolved: http://ubuntuforums.org/showpost.php...44&postcount=7

In his example he talks about automounting a remote samba share but you might try removing his "mount -t cifs" entry and replace it with:

service cups restart

[MM0AMV]

And here also.
I have no network, just computer hard wired into a router.
Sometimes CUPS works, sometimes it doesnt.
I also have Cool'n'Quiet selected in my bios to give me CPU scaling.
Sometimes it works, and sometimes it doesn't.
It all worked flawlessly under 9.10 Karmic.
Maybe, I should abandon 10.4 and go back to 9.10.

Wallace

[kentechy]

Nobody seems to know how to fix CUPS problems in lucid lynx. CUPS starts up on about every other boot, on my laptop, and sometimes Blue-tooth does the same thing. I can manually start CUPS when it fails and then printing is fine. Anybody out there have a fix? This is an old problem. Thanks.

[powerofpi]

sudo apt-get install bum

Then open the boot up manager and make sure that bluetooth and cups services are selected for startup and see if your problem persists.

[lisati]

Threads merged

[kentechy]

sudo apt-get install bum

Then open the boot up manager and make sure that bluetooth and cups services are selected for startup and see if your problem persists.

I already have bum installed and I see CUPS listed in the boot up manager. I have even messed with the priorities in the boot up manager but CUPS stills fails to load about half of the time. I can go into the boot up manager and start it successfully and then my printer works fine. I can also start it manually from Terminal. So, even though bum is trying to start it, sometimes it fails...

[MM0AMV]

Well, I uninstalled 10.4LTS and re-installed it but the problems remain.
The intermittent startups seem to be CUPS, Bluetooth, hddtemp and Cool'n'Quiet.
The mysterious thing is, that all four either startup or all four fail to start.
If you get one you get all four.
I suspect that they all live together in a folder which Lynx is intermittently missing during boot, but I am a Linux noob and wouldn't know where to start looking or what to do once I got there.
Anyone any thoughts??

Wallace

[MM0AMV]

After many hours of searching forums and reading up on CUPS failure to start problems, it seemed (to me anyway), that the problem was caused by some other service/s loading at the same time during boot and stopping CUPS starting for some reason.
So I started switching services off and re-booting to see what happened. Eventually the finger of guilt pointed at Conky, which I use to monitor my temps/fan speeds etc. Switch off Conky, boot is perfect, I get CUPS, Bluetooth, Cool'n'Quiet and hddtemp all running. Switch it on, and the problem returns.
Many reboots later and my system, without Conky, is running flawlessly.
Oh happy days!