On Sun, Jun 7, 2009 at 11:24 AM, Arjan van de Ven<[email protected]> wrote: > bill wrote: >> >> OK, it's working. I know what I had to do but I'm not sure why. >> >> After getting the printer to work by browsing the network with the printer >> all I rebooted. Upon boot nothing seemed to be working and when I tried the >> printer app I got a cups error. So I did a "cups restart" and got the >> printer to work. Then I happened to try Nautilus and it was working. >> >> Being new at this I thought cups was for printing and not a part of the >> file system. Anyway, I used chkconfig to turn on cups though I would > > this is not supposed to be needed; we start cups on demand via xinetd...
Cups needs to be running to pick up the UDP broadcast notifications. So if it's auto-started say the first time a print dialog is opened, it could be 30 seconds after that or more until printers are detected. It may make sense to split cups into two parts, one which just picks up and saves the UDP broadcasts, and one which does the heavy lifting and scans ppds, provides the IPP server etc. _______________________________________________ Moblin dev Mailing List [email protected] To manage or unsubscribe from this mailing list visit: https://lists.moblin.org/mailman/listinfo/dev or your user account on http://moblin.org once logged in. For more information on the Moblin Developer Mailing lists visit: http://moblin.org/community/mailing-lists
