https://bugzilla.novell.com/show_bug.cgi?id=304933#c1 --- Comment #1 from Federico Mena Quintero 2007-09-25 17:30:57 MST --- See also bug #280339 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=304933 Federico Mena Quintero changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |gnome-function-does-not-work -- 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.

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.

https://bugzilla.novell.com/show_bug.cgi?id=304933 User crivera@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=304933#c6 Chris Rivera changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|federico@novell.com | Resolution| |FIXED --- Comment #6 from Chris Rivera 2007-12-17 13:35:35 MST --- I submitted updated gvm and cups-autoconfig to 10.3 and STABLE. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=304933 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=304933#c8 --- Comment #8 from Johannes Meixner 2007-12-18 03:58:43 MST --- Morten, you are really sure that you actually got the fixed packages via online update? In comment #6 "submit" does not mean that the packages are now available via online update. It means only that the packages have been submitted to be built and at some time late they might become available for online update. Check "rpm -q --changelog .." for your packages. There should be an appropriate topmost entry regarding those bugs. I wonder that the packages got built and made available via online update in the few hours from comment #6 to comment #7. -- 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.