Re: Unstable scanning with Fujitsu fi-7160
"m. allan noah" <[email protected]> Wed, 14 Jan 2026 16:11:02 -0500
| Newsgroups | gmane.comp.graphics.scanning.sane.devel |
|---|---|
| Message-ID | <CAKO8m0DW9+RVFB+vzd813xPduvmMkfkkrXEtFiSA7RrysP3Csg@mail.gmail.com> |
--0000000000005f8e5d06485f8ce3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable well, are you normally killing button daemon, or did the problem start before that? On Wed, Jan 14, 2026 at 3:54=E2=80=AFPM Simon Matter <[email protected]= h> wrote: > There is nothing in dmesg, unfortunately. > I see that the button daemon does a sane_open() but when it is terminated > with SIGTERM, there is no sane_close() called from what I understand. > Could that be problem? > > Thanks, > Simon > > > Again, check for kernel-level errors using dmesg. > > > > On Wed, Jan 14, 2026 at 2:59=E2=80=AFPM Simon Matter <simon.matter@invo= ca.ch> > > wrote: > > > >> Everything changed, yes. > >> The button daemon is a quite small program so I expected it to work al= so > >> with the new system. I was wrong here and now I try to find out why it > >> leaves the system in a state where access to the device is blocked. > >> > >> Simon > >> > >> > What changed? Just the sane-backends version, or anything else > >> (hardware, > >> > OS, etc) > >> > > >> > allan > >> > > >> > On Wed, Jan 14, 2026 at 2:32=E2=80=AFPM Simon Matter <simon.matter@i= nvoca.ch> > >> > wrote: > >> > > >> >> I can confirm now that the problem is with the button daemon > >> >> scanmonitord-sanebd only and not with scanimage. > >> >> > >> >> When I run "SANE_DEFAULT_DEVICE=3Dfujitsu:fi-7160:42929 > >> >> scanmonitord-sanebd" > >> >> several times in a terminal and terminate it with Ctrl+C, it will > >> >> suddenly > >> >> say "Open of device fujitsu:fi-7160:42929 failed: Invalid argument"= . > >> >> While studying the code of scanmonitord-sanebd.c I'm failing to > >> >> understand > >> >> what could be wrong. This has worked fine with SANE backends 1.0.24 > >> but > >> >> something has changed here. > >> >> > >> >> If anyone has an idea what could be wrong, please let me know. I'm > >> quite > >> >> lost here. > >> >> > >> >> Thanks, > >> >> Simon > >> >> > >> >> > I start to believe the problem is not in SANE itself but in the > >> button > >> >> > daemon we are using (see attachement). > >> >> > > >> >> > Our software is running the button daemon and waits for events, > >> then > >> >> > terminates the button daemon and does the appropriate scanimage > >> job, > >> >> and > >> >> > then starts the button daemon again. > >> >> > > >> >> > The button daemon is a modified version of some daemon which was > >> >> floating > >> >> > around many years ago. It has worked well for the last 15 years o= r > >> so. > >> >> > Maybe there is some modification needed to make it work well with > >> >> newer > >> >> > SANE. > >> >> > > >> >> > If someone who knows SANE better than me would take a look at it, > >> that > >> >> > would be much appreciated. > >> >> > > >> >> > Thanks, > >> >> > Simon > >> >> > > >> >> >> We need to isolate the problem if possible- I expect if you > >> compile > >> >> an > >> >> >> older, known working sane-backends on your current computer, the > >> >> problem > >> >> >> will persist. That would indicate hardware or OS level issue. > >> >> >> > >> >> >> allan > >> >> >> > >> >> >> On Wed, Jan 14, 2026 at 9:35=E2=80=AFAM Simon Matter via sane-de= vel < > >> >> >> [email protected]> wrote: > >> >> >> > >> >> >>> > > >> >> >>> > Hello, > >> >> >>> > > >> >> >>> > On 2026-01-14 14:59, Simon Matter via sane-devel wrote: > >> >> >>> >> These scanners work perfectly fine with very old sane-backen= ds > >> >> >>> >> and operating system. > >> >> >>> > > >> >> >>> > Does it work on the exact same computer > >> >> >>> > where it fails or does it work on old computers? > >> >> >>> > >> >> >>> It works fine on old computers with old software. > >> >> >>> > >> >> >>> > > >> >> >>> > I ask because of possible USB 3 related issues, see > >> >> >>> > https://en.opensuse.org/SDB:Configuring_Scanners#USB > >> >> >>> > >> >> >>> Thanks, I'll check it out. > >> >> >>> > >> >> >>> Simon > >> >> >>> > >> >> >>> > >> >> >>> > >> >> >> > >> >> >> -- > >> >> >> "well, I stand up next to a mountain- and I chop it down with th= e > >> >> edge > >> >> >> of > >> >> >> my hand" > >> >> >> > >> >> > > >> >> > >> >> > >> >> > >> > > >> > -- > >> > "well, I stand up next to a mountain- and I chop it down with the ed= ge > >> of > >> > my hand" > >> > > >> > >> > >> > > > > -- > > "well, I stand up next to a mountain- and I chop it down with the edge = of > > my hand" > > > > > --=20 "well, I stand up next to a mountain- and I chop it down with the edge of my hand" --0000000000005f8e5d06485f8ce3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">well, are you normally killing button daemon, or did the p= roblem start before that?</div><br><div class=3D"gmail_quote gmail_quote_co= ntainer"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jan 14, 2026 at 3:54= =E2=80=AFPM Simon Matter <<a href=3D"mailto:[email protected]">simo= [email protected]</a>> wrote:<br></div><blockquote class=3D"gmail_quote= " style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);= padding-left:1ex">There is nothing in dmesg, unfortunately.<br> I see that the button daemon does a sane_open() but when it is terminated<b= r> with SIGTERM, there is no sane_close() called from what I understand.<br> Could that be problem?<br> <br> Thanks,<br> Simon<br> <br> > Again, check for kernel-level errors using dmesg.<br> ><br> > On Wed, Jan 14, 2026 at 2:59=E2=80=AFPM Simon Matter <<a href=3D"ma= ilto:[email protected]" target=3D"_blank">[email protected]</a>&g= t;<br> > wrote:<br> ><br> >> Everything changed, yes.<br> >> The button daemon is a quite small program so I expected it to wor= k also<br> >> with the new system. I was wrong here and now I try to find out wh= y it<br> >> leaves the system in a state where access to the device is blocked= .<br> >><br> >> Simon<br> >><br> >> > What changed? Just the sane-backends version, or anything els= e<br> >> (hardware,<br> >> > OS, etc)<br> >> ><br> >> > allan<br> >> ><br> >> > On Wed, Jan 14, 2026 at 2:32=E2=80=AFPM Simon Matter <<a h= ref=3D"mailto:[email protected]" target=3D"_blank">simon.matter@invoca= .ch</a>><br> >> > wrote:<br> >> ><br> >> >> I can confirm now that the problem is with the button dae= mon<br> >> >> scanmonitord-sanebd only and not with scanimage.<br> >> >><br> >> >> When I run "SANE_DEFAULT_DEVICE=3Dfujitsu:fi-7160:42= 929<br> >> >> scanmonitord-sanebd"<br> >> >> several times in a terminal and terminate it with Ctrl+C,= it will<br> >> >> suddenly<br> >> >> say "Open of device fujitsu:fi-7160:42929 failed: In= valid argument".<br> >> >> While studying the code of scanmonitord-sanebd.c I'm = failing to<br> >> >> understand<br> >> >> what could be wrong. This has worked fine with SANE backe= nds 1.0.24<br> >> but<br> >> >> something has changed here.<br> >> >><br> >> >> If anyone has an idea what could be wrong, please let me = know. I'm<br> >> quite<br> >> >> lost here.<br> >> >><br> >> >> Thanks,<br> >> >> Simon<br> >> >><br> >> >> > I start to believe the problem is not in SANE itself= but in the<br> >> button<br> >> >> > daemon we are using (see attachement).<br> >> >> ><br> >> >> > Our software is running the button daemon and waits = for events,<br> >> then<br> >> >> > terminates the button daemon and does the appropriat= e scanimage<br> >> job,<br> >> >> and<br> >> >> > then starts the button daemon again.<br> >> >> ><br> >> >> > The button daemon is a modified version of some daem= on which was<br> >> >> floating<br> >> >> > around many years ago. It has worked well for the la= st 15 years or<br> >> so.<br> >> >> > Maybe there is some modification needed to make it w= ork well with<br> >> >> newer<br> >> >> > SANE.<br> >> >> ><br> >> >> > If someone who knows SANE better than me would take = a look at it,<br> >> that<br> >> >> > would be much appreciated.<br> >> >> ><br> >> >> > Thanks,<br> >> >> > Simon<br> >> >> ><br> >> >> >> We need to isolate the problem if possible- I ex= pect if you<br> >> compile<br> >> >> an<br> >> >> >> older, known working sane-backends on your curre= nt computer, the<br> >> >> problem<br> >> >> >> will persist. That would indicate hardware or OS= level issue.<br> >> >> >><br> >> >> >> allan<br> >> >> >><br> >> >> >> On Wed, Jan 14, 2026 at 9:35=E2=80=AFAM Simon Ma= tter via sane-devel <<br> >> >> >> <a href=3D"mailto:[email protected]= .net" target=3D"_blank">[email protected]</a>> wrote:<b= r> >> >> >><br> >> >> >>> ><br> >> >> >>> > Hello,<br> >> >> >>> ><br> >> >> >>> > On 2026-01-14 14:59, Simon Matter via s= ane-devel wrote:<br> >> >> >>> >> These scanners work perfectly fine = with very old sane-backends<br> >> >> >>> >> and operating system.<br> >> >> >>> ><br> >> >> >>> > Does it work on the exact same computer= <br> >> >> >>> > where it fails or does it work on old c= omputers?<br> >> >> >>><br> >> >> >>> It works fine on old computers with old soft= ware.<br> >> >> >>><br> >> >> >>> ><br> >> >> >>> > I ask because of possible USB 3 related= issues, see<br> >> >> >>> > <a href=3D"https://en.opensuse.org/SDB:= Configuring_Scanners#USB" rel=3D"noreferrer" target=3D"_blank">https://en.o= pensuse.org/SDB:Configuring_Scanners#USB</a><br> >> >> >>><br> >> >> >>> Thanks, I'll check it out.<br> >> >> >>><br> >> >> >>> Simon<br> >> >> >>><br> >> >> >>><br> >> >> >>><br> >> >> >><br> >> >> >> --<br> >> >> >> "well, I stand up next to a mountain- and I= chop it down with the<br> >> >> edge<br> >> >> >> of<br> >> >> >> my hand"<br> >> >> >><br> >> >> ><br> >> >><br> >> >><br> >> >><br> >> ><br> >> > --<br> >> > "well, I stand up next to a mountain- and I chop it down= with the edge<br> >> of<br> >> > my hand"<br> >> ><br> >><br> >><br> >><br> ><br> > --<br> > "well, I stand up next to a mountain- and I chop it down with the= edge of<br> > my hand"<br> ><br> <br> <br> </blockquote></div><div><br clear=3D"all"></div><br><span class=3D"gmail_si= gnature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">&q= uot;well, I stand up next to a mountain- and I chop it down with the edge o= f my hand"</div> --0000000000005f8e5d06485f8ce3--