https://bugzilla.novell.com/show_bug.cgi?id=304933#c4
Chris Rivera changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |federico@novell.com
--- Comment #4 from Chris Rivera 2007-11-14 11:25:22 MST ---
cups-autoconfig gets run when printers are added/removed from the system. It
gets information from HAL, the current cups configuration, and the cups
backends to try and figure out what to do. When it successfully configures a
new printer it sets a property on the HAL printer device, "printer.configured".
GVM looks for this property and then pops up a libnotify bubble telling you
that it just configured your printer.
The HAL callouts are run before it sends add remove signals out on the bus so
if GVM gets an add signal and it doesn't see the property it defaults to
running gnome-cups-add. This is the fall back scenario if we can't
auto-configure the printer.
The problem was that the printer.configured property wasn't being set for
existing printers when they were plugged back in so HAL thought it was a new
printer and ran gnome-cups-add. To fix this I added another property,
printer.configured_existing. If this property exists then GVM does nothing.
I put some test packages here:
http://primates.ximian.com/~cmr/printing/
You need to install them both and then restart HAL and GVM.
I also changed the logging behavior. There should be a pretty verbose log of
what is going on in /var/log/cups-autoconfig.log. Let me know if this helps.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.