Bug#351117: Hpiod crashes on startup
tag 351117 unreproducible
thanks
On Thu, 02 Feb 2006, Tommy McCabe wrote:
> Upon startup of hpiod, either by hplip or from the
> command line, it crashes with the message "can't open
> or create : No such file or directory
> io/hpiod/hpiod.cpp 195". The crash immediately shuts
[...]
> installed on a Debian Sid system, and overwrote an old
> version (Feburary 2005) downloaded from HP's website.
This won't do. You have to go and clean up:
1. **Purge** the debian hplip-*, hplip and hpijs packages.
(removing won't be enough, you need to purge the packages. Be
careful not to purge anything else).
2. Remove any and all crap left over from the old version from
HP upstream. Pay special attention to /etc/hp/*, /usr/lib/hplip/*,
/usr/share/hplip/*, /usr/lib/python2.3/site-packages/pcardext.*,
/usr/lib/python2.3/site-packages/cupsext.*.
It is possible that it has also installed PPDs all over the place,
probably directly inside the CUPS PPD dir, at /usr/share/cups/model.
Remove any PPDs in there starting with "hp-" or "HP-".
If you have any files left over in /usr/local from the old HP
hplip install, remove them too.
3. Reinstall the debian hpijs and hplip packages.
4. Make sure you have a sane /etc/hp/hplip.conf. If you don't, tell me.
> I traced the file and line mentioned in the crash
> message to an fprintf statement in the package source,
> which prints the message.
That line (195) is from the pidfile control code. Run the following command:
/usr/sbin/dpkg-statoverride --list | grep hplip
It must return this:
hplip root 755 /var/run/hplip
If it doesn't, that's what is causing your problem. Otherwise, it is
probably crap left over in /etc/hp/hplip.conf, you need a
"run=/var/run/hplip" entry there for hplip to function.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
Reply to: