I can confirm that this is happening. I just added a network printer and it does take a while. The Searching dialogue box window should close when the device status has changed to Ready.
Additionally, the following doesn't work when trying to close the window:
- Clicking Cancel with the mouse does nothing, no visual feedback
- Focusing on the window and pressing spacebar does nothing even though the 'Cancel' button is already focused.
- Right-clicking on the Searching window and selecting close wants the user to force quit
I can only assume at this point, that the window is stuck in a loop.
[Workaround]
- Once the device status has changed to ready, click on the Printers window and close it.
- The searching dialogue box will still be there, but you can close it with a force quit (right-click window and use close)
- Open printers to ensure previous printer was added.
- [optional] In my case I had to change the model from "Generic text-only printer" to the proper printer driver.
Scp-dbus-service.py seems to be the cause of this behaviour.
Hi Gurvinder,
I can confirm that this is happening. I just added a network printer and it does take a while. The Searching dialogue box window should close when the device status has changed to Ready.
Additionally, the following doesn't work when trying to close the window:
- Clicking Cancel with the mouse does nothing, no visual feedback
- Focusing on the window and pressing spacebar does nothing even though the 'Cancel' button is already focused.
- Right-clicking on the Searching window and selecting close wants the user to force quit
I can only assume at this point, that the window is stuck in a loop.
[Workaround]
- Once the device status has changed to ready, click on the Printers window and close it.
- The searching dialogue box will still be there, but you can close it with a force quit (right-click window and use close)
- Open printers to ensure previous printer was added.
- [optional] In my case I had to change the model from "Generic text-only printer" to the proper printer driver.
Scp-dbus-service.py seems to be the cause of this behaviour.