*** Bug 2657 has been marked as a duplicate of this bug. ***

This bug is not reproduceable in Nevada. Still present in OpenSolaris 2008
build 97.

Norm had filed 6730135 in bugster for the same problem, I've closed that and
copied his eval here:
---
After running hal in debug mode, I found that the hald-addon-network-discovery
agent was unable to resolve the SNMP MIB references and as a result, it wasn't
returning a D-BUS message to the caller letting it know that it didn't start
processing.

In Nevada, the relevant MIB data is in /etc/sma/snmp/mibs/SNMPv2-MIB.txt (and
it's dependencies).  The SUNWsmmgr package appears to contain the MIB data. 
This package and it's contents don't appear to exist in OSOL.  Fixing this
requires getting the MIB data added to OSOL.
---
SUNWsmmgr is present in the package repository, though it's not on the CD. 
I've done a "pkg install SUNWsmmgr" and "svcadm clear printers:snmp", but
service returns to maintenance, so there's something more required.

I have verified that adding the SUNWsmmgr package on a fresh install of OSOL_98
resolves the problem.
The discovery service is implemented as a HAL addon module, so once you have
installed the SUNWsmmgr contents, you need to restart HAL, then clear
printers:snmp for it to work.

Dave, 
Have the package SUNWsmmgr be made part of Live CD?
We need this for 2008.11.

Thanks,

-Ghee

(In reply to comment #5)

No, it has not, we'll be taking a final look at the CD once we have build 100
in hand and decide what to do with it.

*** Bug 4072 has been marked as a duplicate of this bug. ***

Hi,

Does this bug still apply in 2009.06. Need info for documentation.

Thanks,

Nita

Yes, this bug is still in 2009.06 snv_11b x86. I need to be able to print to a
printer connected to a print server via the parallel port.

I tried a patch suggested by Ghee Teo in bug id=6366. I tried putting this into
/etc/dbus-1/system.d/hal.conf

bash-3.2$ diff -u hal.conf.orig hal.conf
--- hal.conf.orig    Tue Mar 17 07:18:50 2009
+++ hal.conf    Tue May 12 11:36:49 2009
@@ -32,6 +32,8 @@
            send_destination="org.freedesktop.Hal"/>
     <allow send_interface="org.freedesktop.Hal.Device.CPUFreq"
            send_destination="org.freedesktop.Hal"/>
+    <allow send_interface="org.freedesktop.Hal.Device.NetworkDiscovery"
+           send_destination="org.freedesktop.Hal"/>
   </policy>

   <!-- Default policy for the exported interfaces -->

and then
pfexec svcadm restart svc:/system/dbus:default
pfexec svcadm disable printers:snmp
pfexec svcadm enable printers:snmp

This did not solve the problem and prevented the gnome gui from being able to
shutdown. The first time I tried to shutdown, the window changed to asking "Do
you want to shutdown?" with a timer and cancel button. At the end of the time
it did not shutdown. After logging out and in, the option to shutdown
disappeared. I changed the hal.conf back to the original and used the terminal
command pfexec reboot. After rebooting, I did get the shutdown option back.

Checking the /var/svc/log/network-device-discovery-printers:snmp.log after
applying the above patch shows
[ Aug 13 22:21:13 Leaving maintenance because disable requested. ]
[ Aug 13 22:21:13 Disabled. ]
[ Aug 13 22:21:29 Enabled. ]
[ Aug 13 22:51:32 Enabled. ]
[ Aug 13 22:51:50 Executing start method
("/lib/svc/method/svc-network-discovery start snmp"). ]
/usr/bin/dbus-send --system --print-reply --dest=org.freedesktop.Hal
--type=method_call /org/freedesktop/Hal/devices/network_attached
org.freedesktop.Hal.Device.NetworkDiscovery.EnablePrinterScanningViaSNMP
int32:60 string:public string:0.0.0.0
Error org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched
rules; type="method_call", sender=":1.2" (uid=0 pid=502 comm=")
interface="org.freedesktop.Hal.Device.NetworkDiscovery"
member="EnablePrinterScanningViaSNMP" error name="(unset)" requested_reply=0
destination="org.freedesktop.Hal" (uid=0 pid=378 comm="))
[ Aug 13 22:51:50 Method "start" exited with status 1. ]

(In reply to comment #9)

Oops. It should read snv_111b. And I have installed SUNWsmmgr.


> Yes, this bug is still in 2009.06 snv_11b x86. I need to be able to print to a
> printer connected to a print server via the parallel port.

I'm seeing this with b122. I have the hal.conf change already (which I believe
worked before) and have SUNWsmmgr installed. Any workarounds?

It appears that in build 121 and later, there is a different issue than the one
reported here.  See http://bugs.opensolaris.org/view_bug.do?bug_id=6875964 for
details.

Hi,

Starting to get my ducks in a row for 2010.03 WRT in on this issue and the
other issue that Norm was tracking, (the one John Levon discovered). Where are
we at re: a fix for either or both of these for 2010.03?

Thanks,

Nita

In order to get the attention of the Solaris engineers, I've
opened a bug in the Sun Bugster database, and am closing this one
as TRACKEDINBUGSTER.

If the Bugster bug is now in a public category/sub-category, the
URL of the new bug at bugs.opensolaris.org will be:

http://bugs.opensolaris.org/view_bug.do?bug_id=6898632

(This will happen the next time the new Bugster bug information
is pushed to bugs.opensolaris.org).

I've added the bug submitter to the Bugster interest list. If you'd
like to be removed, just let me know (by adding a comment to this bug).

If anybody else would like to be added to the cc: of the Bugster bug,
again just let me know (by adding a comment to this bug).

Note that there is currently no easy way for external-to-Sun
people to update the Bugster bug. That's been worked on. In the
meantime, if a Bugster evaluator asks you for further information
and you are external-to-Sun, then I suggest emailing that person
directly.

Thanks.