I get
error: Unable to load Qt4 support. Is it installed?
Since I'm running kde 4.2.98 I'm pretty sure it is. What else could be wrong?
Anne
On Mon, Jul 27, 2009 at 4:00 PM, Anne Wilson wrote:
I get
error: Unable to load Qt4 support. Is it installed?
Since I'm running kde 4.2.98 I'm pretty sure it is. What else could be wrong?
Anne
Works fine here. Do you have PyQt removed by any chance?
Orcan
$ rpm -qa |grep hp hplip-3.9.2-4.fc11.x86_64 hpijs-3.9.2-4.fc11.x86_64 rhpl-0.221-1.x86_64 libsane-hpaio-3.9.2-4.fc11.x86_64 hplip-libs-3.9.2-4.fc11.x86_64 rhpxl-1.12-2.fc11.x86_64 hplip-gui-3.9.2-4.fc11.x86_64
$ rpm -qR hplip-gui /bin/sh /bin/sh /usr/bin/env PyQt PyQt4 desktop-file-utils >= 0.2.92 desktop-file-utils >= 0.2.92 hplip = 3.9.2-4.fc11 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
On Monday 27 July 2009 21:18:20 Orcan Ogetbil wrote:
On Mon, Jul 27, 2009 at 4:00 PM, Anne Wilson wrote:
I get
error: Unable to load Qt4 support. Is it installed?
Since I'm running kde 4.2.98 I'm pretty sure it is. What else could be wrong?
Anne
Works fine here. Do you have PyQt removed by any chance?
Orcan
$ rpm -qa |grep hp hplip-3.9.2-4.fc11.x86_64 hpijs-3.9.2-4.fc11.x86_64 rhpl-0.221-1.x86_64 libsane-hpaio-3.9.2-4.fc11.x86_64 hplip-libs-3.9.2-4.fc11.x86_64 rhpxl-1.12-2.fc11.x86_64 hplip-gui-3.9.2-4.fc11.x86_64
$ rpm -qR hplip-gui /bin/sh /bin/sh /usr/bin/env PyQt PyQt4 desktop-file-utils >= 0.2.92 desktop-file-utils >= 0.2.92 hplip = 3.9.2-4.fc11 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
I haven't removed it - I suspect it was never installed. Thanks for the list. I'll work my way through until I have them all installed.
PyQt* pulled in 36 packages.
Anne
On Monday 27 July 2009 23:37:43 Kevin Kofler wrote:
Anne Wilson wrote:
I get
error: Unable to load Qt4 support. Is it installed?
Since I'm running kde 4.2.98 I'm pretty sure it is. What else could be wrong?
yum install hplip-gui
It will also drag in the required PyQt4 stuff.
Yes, that was all it was. This isn't intuitive, though. If you can't use hplip to set up your printer without installing hplip-gui, then shouldn't that be linked as a dependency (even though it's sort of the other way around ;-) )?
Anne
On Tue, Jul 28, 2009 at 08:55:19AM +0100, Anne Wilson wrote:
yum install hplip-gui It will also drag in the required PyQt4 stuff.
Yes, that was all it was. This isn't intuitive, though. If you can't use hplip to set up your printer without installing hplip-gui, then shouldn't that be linked as a dependency (even though it's sort of the other way around ;-) )?
The reason for the missing dependency is that it would pull in all of qt and pyqt which gnome-fanboys aren't very happy about (not to offend any of them - we aren't very happy about having to depend on gtk in our default spin either).
On Tuesday 28 July 2009 09:07:29 Sven Lankes wrote:
On Tue, Jul 28, 2009 at 08:55:19AM +0100, Anne Wilson wrote:
yum install hplip-gui It will also drag in the required PyQt4 stuff.
Yes, that was all it was. This isn't intuitive, though. If you can't use hplip to set up your printer without installing hplip-gui, then shouldn't that be linked as a dependency (even though it's sort of the other way around ;-) )?
The reason for the missing dependency is that it would pull in all of qt and pyqt which gnome-fanboys aren't very happy about (not to offend any of them - we aren't very happy about having to depend on gtk in our default spin either).
But doesn't that mean that hplip is useless? If you can't set up your printer, it is. I'm not being aggressive, just practical. Happy or not, if you have an HP device that needs hplip, you have to be able to use hp-setup. It's not as though there is a -tui version.
Anne
Anne Wilson wrote:
But doesn't that mean that hplip is useless? If you can't set up your printer, it is. I'm not being aggressive, just practical. Happy or not, if you have an HP device that needs hplip, you have to be able to use hp-setup. It's not as though there is a -tui version.
You can use system-config-printer or system-config-printer-kde to set up your printer just fine, there's no need to use the vendor-specific hp-setup tool.
Another reason hplip-gui is not installed by default is that the RH folks objected to a vendor-specific tool (hp-toolbox) being in the default menus. That said, hp-toolbox is the only UI which allows you to check the cartridge state or align or clean the cartridges at the moment.
Kevin Kofler
On Tuesday 28 July 2009 15:30:10 Kevin Kofler wrote:
Anne Wilson wrote:
But doesn't that mean that hplip is useless? If you can't set up your printer, it is. I'm not being aggressive, just practical. Happy or not, if you have an HP device that needs hplip, you have to be able to use hp-setup. It's not as though there is a -tui version.
You can use system-config-printer or system-config-printer-kde to set up your printer just fine, there's no need to use the vendor-specific hp-setup tool.
I did once use s-c-p. It worked, after a fashion, but you can't use it to set up every feature of the device.
Another reason hplip-gui is not installed by default is that the RH folks objected to a vendor-specific tool (hp-toolbox) being in the default menus. That said, hp-toolbox is the only UI which allows you to check the cartridge state or align or clean the cartridges at the moment.
And a few other things too, including fax setup. It doesn't have to be in the default menu anyway. It just has to be available, just as things like nv are. I still think that the two (hplip and hplip-gui) should be linked if not packaged together. It makes no sense any other way.
Anne
Kevin Kofler wrote:
You can use system-config-printer or system-config-printer-kde to set up your printer just fine,
What is the point of these two applications? What does the kde version add? (In my case, when I run it, I am not asked for the root password, and most of the possible actions are greyed-out.)
there's no need to use the vendor-specific hp-setup tool.
I don't understand the relation - if any - of hplib to CUPS. Can one install both without problems?
Timothy Murphy wrote:
What is the point of these two applications? What does the kde version add?
KDE integration.
(In my case, when I run it, I am not asked for the root password, and most of the possible actions are greyed-out.)
That is a bug. Looks like it doesn't support the PolicyKit integration in system-config-printer properly. Are you running Rawhide or F11?
I don't understand the relation - if any - of hplib to CUPS.
hplip is a driver for CUPS (and SANE for the scanner part of multifunction printers), and a set of some additional, HP-specific tools.
Can one install both without problems?
Yes, you even need CUPS to use hplip.
Kevin Kofler
Kevin Kofler wrote:
(In my case, when I run it, I am not asked for the root password, and most of the possible actions are greyed-out.)
That is a bug. Looks like it doesn't support the PolicyKit integration in system-config-printer properly. Are you running Rawhide or F11?
Thanks for your response.
I'm running standard Fedora-11 (up to date).
I notice much the same problem with system-config-printer. I'm not asked for the root password, and if I highlight the printer (HP_LaserJet_5L), go to Printer>>Properties>>Printer Options and try to change Media Size from Letter to A4, I am told "You are not authorized to carry out the requested action".
I'm actually told the same if I carry out the same procedure as superuser. Also, in this case I cannot leave the program. When I click on Close I get the error message: ---------------------------------- [root@alfred tim]# system-config-printer Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 2785, in on_quit_activate del self.mainlist AttributeError: GUI instance has no attribute 'mainlist' ----------------------------------
(In my case, when I run it, I am not asked for the root password, and most of the possible actions are greyed-out.)
That's normal when it needs SU mode, of course. Yes, it would be useful to either ask for the password or tell you what's wrong.
Doesn't launching hp-setup from a root terminal work?
Anne
Anne Wilson wrote:
(In my case, when I run it [system-config-printer], I am not asked for the root password, and most of the possible actions are greyed-out.)
That's normal when it needs SU mode, of course. Yes, it would be useful to either ask for the password or tell you what's wrong.
But as I said, the result is actually the same if I run system-config-printer as root. I am told I am not authorized to change the Media Size (from letter to A4). In fact it is worse if I run as root, since I cannot leave the program - I have to kill it from another console.
Doesn't launching hp-setup from a root terminal work?
As far as I can see, hp-setup only allows me to install a second printer, not to modify an existing one.
I should perhaps have made clear that the CUPS web interface does allow me to change the media size; my remarks were only addressed at system-config-printer.
Incidentally, I was trying to discover where the page size (letter or A4) is stored on the computer. I couldn't find any mention of it in /etc/cups, /var/spool/cups or /var/run/cups .
On Thursday 30 July 2009 11:04:31 Timothy Murphy wrote:
Anne Wilson wrote:
(In my case, when I run it [system-config-printer], I am not asked for the root password, and most of the possible actions are greyed-out.)
That's normal when it needs SU mode, of course. Yes, it would be useful to either ask for the password or tell you what's wrong.
But as I said, the result is actually the same
My mistake - Imis-read what you said there.
if I run system-config-printer as root. I am told I am not authorized to change the Media Size (from letter to A4). In fact it is worse if I run as root, since I cannot leave the program - I have to kill it from another console.
Doesn't launching hp-setup from a root terminal work?
As far as I can see, hp-setup only allows me to install a second printer, not to modify an existing one.
hp-setup should detect the existing printer. It works in conjunction with cups.
I should perhaps have made clear that the CUPS web interface does allow me to change the media size; my remarks were only addressed at system-config-printer.
Personally I'm not happy about mixing s-c-p and hp-setup. I'd use hp-setup if I was setting up (or configuring) an hp device for which I want/need the extra features. I'd use s-c-p otherwise.
Incidentally, I was trying to discover where the page size (letter or A4) is stored on the computer. I couldn't find any mention of it in /etc/cups, /var/spool/cups or /var/run/cups .
I wouldn't expect it to be there. It would be specific to the print queue, surely? Try looking at /var/cache/cups/devicename.ipp
Anne
Anne Wilson wrote:
Doesn't launching hp-setup from a root terminal work?
It won't, PolicyKit is set up to deny access to root by default.
Hint: put this snippet of XML into /etc/PolicyKit/PolicyKit.conf: <config version="0.1"> <match user="root"> <return result="yes"/> </match> </config> and PolicyKit will blanket-approve any permissions requested by root (instead of blanket-denying them as it does by default).
(Making it actually prompt you for the password if you're root requires patching the code, blanket approval interestingly doesn't because it bypasses the anti-root check in the authentication logic entirely.)
Yes, that WILL decrease protection against malware to some extent. But if you have malware running as root, you have a bigger problem already. ;-) (And they can really do anything just bypassing the PolicyKit-based frameworks entirely, at least if you have SELinux disabled.)
Kevin Kofler
I wrote:
Anne Wilson wrote:
Doesn't launching hp-setup from a root terminal work?
It won't, PolicyKit is set up to deny access to root by default.
Well, actually hp-setup isn't using PolicyKit, system-config-printer is (so I'm replying to the wrong message).
But hplip has its own bogus checks against running as root (search for getuid in /usr/share/hplip to find them).
Kevin Kofler
On Thursday 30 July 2009 18:59:57 Kevin Kofler wrote:
I wrote:
Anne Wilson wrote:
Doesn't launching hp-setup from a root terminal work?
It won't, PolicyKit is set up to deny access to root by default.
Well, actually hp-setup isn't using PolicyKit, system-config-printer is (so I'm replying to the wrong message).
But hplip has its own bogus checks against running as root (search for getuid in /usr/share/hplip to find them).
If you try to run hp-setup as user it tells you that it *must* be run as root. This is a one-time run.
Anne
Anne Wilson wrote:
If you try to run hp-setup as user it tells you that it *must* be run as root. This is a one-time run.
Fun, run e.g. hp-toolbox as root and it will tell you you must not run it as root (well, first it tells you you should not, then it errors because of another root check somewhere else). hp-setup on the other hand won't even run as a regular user (I think years will pass until HP gets wind about things like PolicyKit). But at least HP is releasing their source code under a Free Software license unlike most other manufacturers… Still, the hp-setup tool is entirely useless as all its functionality is already provided by our own tools (system-config-printer resp. system-config-printer-kde). hp- toolbox (and hp-systray which it starts too), while providing some unique and very much necessary functionality (ink cartridge maintenance – IIRC, some time ago there was some movement to provide a unified interface for that in CUPS to avoid all the manufacturer-specific tools (there are similar tools for printers from some other manufacturers, though usually community- written unlike hp-toolbox), I hope that common interface will get completed and implemented in the UIs at some point) also duplicates some functionality of other tools already provided in Fedora and other distributions.
Kevin Kofler
On Thursday 30 July 2009 23:04:47 Kevin Kofler wrote:
Anne Wilson wrote:
If you try to run hp-setup as user it tells you that it *must* be run as root. This is a one-time run.
Fun, run e.g. hp-toolbox as root and it will tell you you must not run it as root (well, first it tells you you should not, then it errors because of another root check somewhere else). hp-setup on the other hand won't even run as a regular user (I think years will pass until HP gets wind about things like PolicyKit).
Those decisions are sensible. You want setup to be system-wide. Toolbox is user-level. Fair enough.
But at least HP is releasing their source code under a Free Software license unlike most other manufacturers… Still, the hp-setup tool is entirely useless as all its functionality is already provided by our own tools (system-config-printer resp. system-config-printer-kde). hp- toolbox (and hp-systray which it starts too), while providing some unique and very much necessary functionality (ink cartridge maintenance – IIRC, some time ago there was some movement to provide a unified interface for that in CUPS to avoid all the manufacturer-specific tools (there are similar tools for printers from some other manufacturers, though usually community- written unlike hp-toolbox), I hope that common interface will get completed and implemented in the UIs at some point) also duplicates some functionality of other tools already provided in Fedora and other distributions.
Sorry Kevin, but your are being blinkered. S-c-p has its place, but it is not as good as hplip for these devices. You use what you like and leave us to use what we like.
Anne
On Thursday 30 July 2009 18:50:32 Kevin Kofler wrote:
Anne Wilson wrote:
Doesn't launching hp-setup from a root terminal work?
It won't, PolicyKit is set up to deny access to root by default.
Interesting - because that's exactly what I did do to set up mine, only a ew days ago.
Anne
Anne Wilson wrote:
Interesting - because that's exactly what I did do to set up mine, only a ew days ago.
Well, as I said, I was thinking about the Fedora tools (which have also been mentioned in the discussion, I didn't notice we went back to hp-setup), not the HP-specific hp-setup tool. system-config-printer now uses PolicyKit for authentication and thus should NOT be run as root (it will, or at least is expected to, ask for the root password and then do that specific operation as root).
Kevin Kofler
-
Anne Wilson -
Kevin Kofler -
Orcan Ogetbil -
Sven Lankes -
Timothy Murphy