I think that we should update the hald-probe-printer to add the printer
capability to the HAL device tree node when it gets back IEEE1284
DeviceID information for a printer. I just filed the bug.
6697336 hald-printer-probe should update capabilities too
I will try to fix it and integrate in the next few days so that it makes
build 90.
-Norm
Ghee Teo wrote:
> Martti Hamunen wrote:
>
>> Yes,
>> it is here:
>> ...
>> udi = '/org/freedesktop/Hal/devices/isa/lp_1_378_0'
>> info.claimed.uid = 65535 (0xffff) (int)
>> info.claimed.service = 'gnome-volume-manager' (string)
>> info.claimed = true (bool)
>> printer.device = '/dev/printers/0' (string)
>> printer.commandset = {'ESCPL2', 'BDC'} (string list)
>> printer.product = 'Stylus COLOR 600' (string)
>> printer.vendor = 'EPSON' (string)
>> info.callouts.add = {'hald-probe-printer'} (string list)
>> info.solaris.driver = 'ecpp' (string)
>> solaris.devfs_path = '/isa/lp at 1,378' (string)
>> info.product = 'Stylus COLOR 600' (string)
>> info.udi = '/org/freedesktop/Hal/devices/isa/lp_1_378_0' (string)
>> info.parent = '/org/freedesktop/Hal/devices/isa_0' (string)
>> ...
>> but this I dont understand:
>> "which means that the OSPM should offer
>> you the opportunity to create a print queue for it when you login..."
>> how?
>>
What I meant was that it should pop up and add print queue dialog when
you login, but as Ghee points out, the HAL device tree entry is missing
the 'printer' capability, so the opsm doesn't know it's a printer.
>>
>>
> ospm checks for info.capabiities = 'printer' which in this case does
> not contain.
> Should we expand the ospm checking so that we can also work this case ?
>
> -Ghee
>
>> Martt
