Comment 13 for bug 66830

Update from Donald Welch:

Till-

Just wanted to give you an update. So far my testing is, I think, inconclusive. Here's what I know:

1. The "stock" HPLIP install of 1.6.9/10 on Edgy doesn't work properly. I used Wireshark and confirmed that HPSSD is, in fact, sending data to the hp-toolbox client, but that the Qt message loop doesn't seem to "see" it (that is, the QSocketNotifier callbacks aren't fired). This was after extensively instrumented up the code. The easiest way to reproduce this test is as follows:

    1. Install and startup HPLIP 1.6.10
    2. Setup a printer (with hp:/ backend)
    3. Run the toolbox and switch to the installed printer's status tab
    4. Run the attached "event.py" that sends an asynchronous event to the toolbox via HPSSD. To do this, copy event.py to /usr/share/hplip and then run "python ./event.py -e 600"
    5. The toolbox should immediately show the status code "600" in the status tab (it will work on Dapper, but not on Edgy).

2. I created a client/server pair to test this in more isolation (attached server.py and client.py). Unfortunately, this pair of programs does work on both Edgy and Dapper. To run these:

    1. Run the server.py and not the port number it reports
    2. Run client.py with the port number as a command line parameter
    3. The client should show the time/date periodically in the window (it works in both Edgy and Dapper)

I am left feeling that this is less likely of a PyQt/SIP bug, but rather some subtle differences in usage and/or convention that have changed in Edgy or the PyQt/SIP code in Edgy. The stripped down client/server pair have of course removed and simplified a lot of code, which is where the problem could be. So, as a test, it is far from perfect or definitive.

I am open to any suggestions as to where to go with this next.

Regards,

Don