As for your question: No you shouldn't have to rebuild everything. This was a 'minor' upgrade to glibc (Eg usually bugfix). if you were going from say 3.1 or 3.2 to 3.3/3.4 then yes, you should rebuild your sytem._________________2b || !2b
{ STFF } { GOOGLE } { RTFM } { NO -U } { STRIP }

Don't know about the others but the reason I haven't replied is I had nothing helpful to add I do very little printing, and don't even have a printer of my own hooked up, I always send it over the lan to the missus and have her print it lol. I'm just too lazy to set things up 'proper', and as I said, don't print enough to warrent it._________________2b || !2b
{ STFF } { GOOGLE } { RTFM } { NO -U } { STRIP }

* Figured out that my /dev/lp0 was working alright. So i knew it was a problem with cups or the client. All clients used to work so it's a cups problem.
* Figured out lp and lpr etc. where showing the scheduler error.
* Read these threads. And tried the following:

Thank you!
I was 3 seconds away from using my Canon i950 as a makeshift football until I saw this thread.
I saw this:

Quote:

The printer shows "idle, accepting jobs " and "ready to print" from cups admin but it does nothing.

Even if I try to print the test page cups gives it a job number but nothing appears in the jobs section of cups.

and that you were using turboprint as well ... bells went off. So I deleted the printer via the CUPS web admin and re-added it... PRESTO! It works, very weird. So if anyone else is using turboprint, try the web admin instead of xtpsetup. Thanks again, and my printer is grateful that you saved its life, it's still sitting in the corner with a worried look on its face.