| Summary: | net-print/hplip-3.20.6-r1: sandbox violation | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Richard H. <chain> |
| Component: | Current packages | Assignee: | Daniel Pielmeier <billie> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | herrtimson, printing, sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build log | ||
|
Description
Richard H.
2020-09-04 20:36:04 UTC
Created attachment 658414 [details]
build log
I can not reproduce this error! It looks like you have a directory /usr/lib64/x86_64-linux-gnu/sane/ which I don't have. Can you check if this is the case and if yes to which packages it belongs. (In reply to Daniel Pielmeier from comment #2) > I can not reproduce this error! > It looks like you have a directory /usr/lib64/x86_64-linux-gnu/sane/ which I > don't have. Can you check if this is the case and if yes to which packages > it belongs. Sure can do! A simple ls gives me a lot of files, all with the same timestamp. # equery b /usr/lib64/x86_64-linux-gnu/sane/ * Searching for /usr/lib64/x86_64-linux-gnu/sane/ ... media-gfx/sane-backends-1.0.30-r2 (/usr/lib64/sane) net-print/hplip-3.20.3 (/usr/lib64/sane) Which is not really surprising to me, because I have/had another scanner which I used to use. Not anymore, so I could uninstall same-backends for testings sake, but how did it work until now? (In reply to Richard H. from comment #3) > (In reply to Daniel Pielmeier from comment #2) > > I can not reproduce this error! > > It looks like you have a directory /usr/lib64/x86_64-linux-gnu/sane/ which I > > don't have. Can you check if this is the case and if yes to which packages > > it belongs. > > Sure can do! A simple ls gives me a lot of files, all with the same > timestamp. > > # equery b /usr/lib64/x86_64-linux-gnu/sane/ > * Searching for /usr/lib64/x86_64-linux-gnu/sane/ ... > media-gfx/sane-backends-1.0.30-r2 (/usr/lib64/sane) > net-print/hplip-3.20.3 (/usr/lib64/sane) > > Which is not really surprising to me, because I have/had another scanner > which I used to use. Not anymore, so I could uninstall same-backends for > testings sake, but how did it work until now? Is /usr/lib64/x86_64-linux-gnu/sane/ a link to /usr/lib64/sane or /usr/lib64/x86_64-linux-gnu/ to /usr/lib64? Wait a moment. /usr/lib64/x86_64-linux-gnu is a symlink to /usr/lib64 on my machine. Do you have that one as well? It's from 2014, so it looks fishy to me. I don't know where it comes from, equery doesn't show anything. Just saw your comment. As it stands, the symlink would overwrite itself I guess. Is that right? (In reply to Richard H. from comment #5) > Wait a moment. > > /usr/lib64/x86_64-linux-gnu is a symlink to /usr/lib64 on my machine. Do you > have that one as well? It's from 2014, so it looks fishy to me. > > I don't know where it comes from, equery doesn't show anything. > > Just saw your comment. > > > As it stands, the symlink would overwrite itself I guess. Is that right? I don't have it. Looks indeed fishy. Pretty sure it is some leftovers from some non portage operations/stuff. I am not 100% sure if it is save to remove but if you know how to recover from a potential non-booting system you can give it a try. The problem is it tries to execute the following command: ln -sf /usr/lib64/sane/libsane-hpaio.so /usr/lib64/x86_64-linux-gnu/sane/ this is essentially ln -sf /usr/lib64/sane/libsane-hpaio.so /usr/lib64/sane/ due to the symlink. As this directory exists on the live system the sandbox trigger an error. (In reply to Daniel Pielmeier from comment #6) > (In reply to Richard H. from comment #5) > > Wait a moment. > > > > /usr/lib64/x86_64-linux-gnu is a symlink to /usr/lib64 on my machine. Do you > > have that one as well? It's from 2014, so it looks fishy to me. > > > > I don't know where it comes from, equery doesn't show anything. > > > > Just saw your comment. > > > > > > As it stands, the symlink would overwrite itself I guess. Is that right? > > I don't have it. Looks indeed fishy. Pretty sure it is some leftovers from > some non portage operations/stuff. I am not 100% sure if it is save to > remove but if you know how to recover from a potential non-booting system > you can give it a try. > > The problem is it tries to execute the following command: > ln -sf /usr/lib64/sane/libsane-hpaio.so /usr/lib64/x86_64-linux-gnu/sane/ > this is essentially > ln -sf /usr/lib64/sane/libsane-hpaio.so /usr/lib64/sane/ > due to the symlink. > > As this directory exists on the live system the sandbox trigger an error. Sorry, it took so long. I wanted and needed to cross-check on my systems. Indeed it is only this one system, which has this symlink. And I am pretty sure where it might have come from. On this system I have installed the plugins/blobs myself in some dark ages where it simply wouldn't work. I needed to create this symlink myself back then. I guess now it is included as well and therefore plugins should also work out of the box. I deleted the symlink and it installed fine now. Sorry for all the noise. Exactly, I just now printed out this very bug LaserJet M1120n MFP (binary plugin needed!). Finally everything just works out of the box. Thank you all for your hard work! |