Yes and no, but yes. If the button looks disabled as in your example then 'no'. Disabled buttons are disabled, and this convention is seldom violated in most applications. If a button is clearly disabled, users are unlikely to tap it, so the information they are looking for is hidden from them. So, should you be able to click the disabled button to get information, no definitely not, it's not intuitive.
The information is highly valuable, and should be readily available. Luckily there are other ways of handling it. You could:
- replace the button with text -> "Printer Malfunction" (this brings the information to the top level, no interaction required)
- leave the button in an enabled state (so users know they can tap it) and use the dialog as in your question (leave the information on a second layer, but interaction is intuitive, but the button no longer states its real action)
- when appropriate change the button text to -> "Print Error" (leaves information on a second layer, button represents what it really does)
I don't know which (if any) is appropriate for your interface, but hopefully this will help.