Comment 4 for bug 227342

Revision history for this message
Qluripax (qluripax) wrote :

I've tried a lot of debugging but it feels that I don't come down to the right level..
Anyway, after removing appamor and a reboot of the server I got the following in cups web-interface: "Could initialize HAL daemon: (null)"

I have also tried the network interface and the only thing I got then was "busy, retrying". Network interface is no option for me in production as we are two companies that shares this printer (and the other company don't dare to have Linux computers on their network).

I'm an Linux administrator - not a hacker - but are there any debugging tools that I can use to come down a bit deeper in this? The printer is relative expensive and I am allowed to use it for free so it's quite interesting for me to have this fixed... Thanks!