Summary: | net-print/hplip- 3.12.2-r2 USE=parport does not configure parallel port support | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stephen Bosch <posting> |
Component: | [OLD] Printing | Assignee: | Daniel Pielmeier <billie> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | printing |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stephen Bosch
2012-03-07 08:18:50 UTC
If you take a look at /etc/hp I bet there are ._cfgXXXX_hplip.conf files and the version you have previously installed did not have parallel port support enabled. If yes learn to use the tools described here [1] in chapter 4.a and 4.b and try again. [1] http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4 (In reply to comment #1) > If you take a look at /etc/hp I bet there are ._cfgXXXX_hplip.conf files and > the version you have previously installed did not have parallel port support > enabled. If yes learn to use the tools described here [1] in chapter 4.a and > 4.b and try again. > > [1] http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=4 There are two ._cfgXXXX_hplip.conf files there. However, *all* of the configure files in this directory contain pp-build=yes. The role of these conf files is a mystery to me, since these are configure time parameters and cannot be changed after the fact anyway. Hplip relies on this file at runtime. If you compile it with some options and change them manually in the config file afterwards you can get strange results. So it is important to run dispatch-conf or etc-update as portage already tells you after it finishes it's work. This way the settings match the installed ones. So what is the status here? (In reply to comment #4) > So what is the status here? I built it manually from current sources, at which point parallel port support was enabled (pp-build=yes) and it showed me the option of choosing the parallel port when running hp-setup, although it still doesn't seem to see the connected printer (which can at least print using a normal CUPS setup). Given that, though, I still think there is something wrong with the ebuild. In any case -- the conf files you describe are supposed to reflect build time parameters, not set them. What are the strange results you get when the conf files don't match the build-time parameters? (In reply to comment #5) > (In reply to comment #4) > > So what is the status here? > > In any case -- the conf files you describe are supposed to reflect build > time parameters, not set them. What are the strange results you get when the > conf files don't match the build-time parameters? The strange things I mentioned are the ones I thought you are experiencing at first. You built with parallel port enabled but did not update the config file. I assumed this because the version hplip reported was an old one and it gets the version number from the configuration file and all settings as well regardless of which are built or not. So the settings should reflect build time parameters but they wont if you don't update the configuration file with dispatch-conf or etc-update. Please reinstall hplip and run one of them to update the configuration file. Maybe it is also a good idea to remove any traces from the the file hplip.conf in /etc/hp including the ._cfgXXXX_ files in advance. Afterwards restart cups. Then remove all your configured printer queues and configure them again. If you still encounter problems please post the output of: emerge --info =net-print/hplip-3.12.2-r2 The complete build log of hplip Your configuration file /etc/hp/hplip.conf Please add the requested information else I can not do much and will close this bug. I don't use a parallel port printer, but there are still a lot of users who do and nobody else has reported such issues. I am not near the machine in question and need until the weekend to access it and look at it again. Can you wait until then? |