| 1 |
Frédéric Grosshans wrote on 04/05/06 18:32: |
| 2 |
> Le jeudi 04 mai 2006 à 17:42 +0200, Petr Kocmid a écrit : |
| 3 |
|
| 4 |
>>Sometimes, due poor maintnance of low level foomatic driver in portage an |
| 5 |
>>updated foomatic driver dies silently and cups daemon thinks everything is |
| 6 |
>>finished printed fine, or if one is lucky as you, ends with dead process |
| 7 |
>>logged. |
| 8 |
|
| 9 |
> Thanks. I had the same problem, which has been solved by : |
| 10 |
> # echo "=net-print/foomatic-db-20050910" >> /etc/portage/package.mask |
| 11 |
> # emerge -vau foomatic-db |
| 12 |
> # /etc/init.d/cupsd restart |
| 13 |
|
| 14 |
The downgrade to the lower level of foomatic-db gives problems with the |
| 15 |
/etc/make.conf FEATURE=sandbox. |
| 16 |
|
| 17 |
However, this problem can be circumvented by (temporarily) replacing |
| 18 |
FEATURE="sandbox", with FEATURE="-sandbox -usersandbox" in |
| 19 |
/etc/make.conf. Do this at your own risk! |
| 20 |
|
| 21 |
However, the real solution to the problem is to re-emerge |
| 22 |
foomatic-filters, as suggested by Frédéric in a later post. |
| 23 |
|
| 24 |
The cause of the problem is (as he said) documented in bug 131533: |
| 25 |
|
| 26 |
http://bugs.gentoo.org/show_bug.cgi?id=131533 |
| 27 |
|
| 28 |
Either solution, downgrading foomatic-db or re-emerging foomatic-filters |
| 29 |
works fine. |
| 30 |
|
| 31 |
Thanks to all for their help. |
| 32 |
|
| 33 |
Cheers, Dave |
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives