However, I haven’t run a test to confirm my beliefs because I installed Intrepid Alpha 4 and had the same resolution problem after acticvating the NVIDIA driver and couldn’t get it back to work again even after some finetuning of that installation. I filed a bug report with the kernel devs of debian: Worked great for 3 years, first on Suse, Ubuntu 7. For more information and for registration, please click here. Select Reset printing system and then restart the Mac. This file does not exist on my Lion installation, and I’m pretty sure didn’t when I was running Snow Leopard either.
|Date Added:||28 May 2010|
|File Size:||11.98 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
To start the conversation again, simply ask a new question. I had the same problem since installation of Hardy – could not print to remote printer, while connecting it locally was OK. Check that the printer is functioning correctly, then try again to get the printer information I have a firewall installed but during the setup I allowed this traffic to pass it, when I was asked to do.
The bypass I reported with the bug definitely works with the latest Hardy kernel, so my Hardy systems I still have a couple run fine with my printer.
Win boxes print just fine. I am certainly prepared to help as much as possible. Also, it appears these patches are already in the Intrepid kernel. Thank You for Submitting Your Review,! Tried the workaround posted above by Eric Wick.
I was prepared to research the code differences, but I couldn’t get the tools to work and Leann didn’t reply to my questions. And I can print in Hardy too now.
And of course, opening the Printmonitor for this printer that does not exist, causes the same error message you are getting. I but only after the third time I rebooted.
Thanks again, we really appreicate your help and feedback. I went lpx your url, but wasn’t sure what to do next. So one thought to resolve this would be to reset the printing system and then add the queue again. I can print one page following a reboot. It broke a lot of stable printing systems and so we knew we would have to live with the bug for the next 18 months. Mac OS X Speciality level out of ten: Aug 9, 2: Sorry to ask for so much help and advice, but you are taking me into new territory.
So I even gave cntbmu all rights to go through the firewall, but it showed no effect. In the process of performing the git bisect, you will also need to perform some kernel builds of your own. The printer starts and stops several times up to this point. I agree with you Stefan, but don’t see any reason for you seriea have regrets! Would sure like to get this fixed!
Original new sealed Cisco product: I have also tried the patch and it has made no difference. There won’t be log entries, because the Mac does not see you having a network problem. Thank you for your recommendations, which I followed.
Not as much lost interest as buried under a pile of various other stuff. I don’t know if it’s related, but I’ve had massive problems printing across my network to an Ubuntu machine running as a print server. I conclude that the intrepid kernel with Ilpo’s fix is correct: Also, please specifically note if the issue seriea or does not appear in the 2.
I suggest to not install or upgrade to 8. Good switch, good deal!