Hi,

On Tue, Sep 28, 2021 at 2:49 AM Jörg Frings-Fürst <debian@jff.email> wrote:
>
> First of all, I set the severity to normal, because there is no data
> loss in the sense of grave, but only an erroneous output.

Well, I am trying to read over a month's worth of scanned personal and
business documents. I may have lost access to the data—except for LO
Draw, apparently—due to this bug. Maybe it's not a bug in simple-scan,
but something mangled the image data. The hard copies are shredded.

Other users may also have issues and not realize it, either.

>  - What was the occupancy of the mouted partitions?

Here is an overview of my mounted partitions:

Filesystem                                 Size  Used Avail Use% Mounted on
udev                                        13G     0   13G   0% /dev
tmpfs                                      2.6G  1.8M  2.6G   1% /run
/dev/mapper/optivg-stable                   41G   27G   12G  70% /
tmpfs                                       13G   92M   13G   1% /dev/shm
tmpfs                                      5.0M  4.0K  5.0M   1% /run/lock
/dev/mapper/optivg-nodeb                   4.8G  4.2G  405M  92% /nodeb
/dev/mapper/optivg-fscache                 4.9G  4.2G  480M  90%
/var/cache/fscache
/dev/mapper/optivg-home.local               25G   14G  9.8G  59% /lcl
/dev/sda127                                500M  5.2M  494M   2% /boot/efi
/dev/mapper/optivg-tmp                     197G   62M  188G   1% /tmp
/dev/mapper/optivg-schroot.unstable.amd64  4.9G  1.3G  3.4G  27%
/var/lib/schroot/union/underlay/unstable-amd64-e469dd9d-9737-4e57-96e7-fe321d53cc2f
unstable-amd64                              41G   27G   12G  70%
/run/schroot/mount/unstable-amd64-e469dd9d-9737-4e57-96e7-fe321d53cc2f
tmpfs                                       13G     0   13G   0%
/run/schroot/mount/unstable-amd64-e469dd9d-9737-4e57-96e7-fe321d53cc2f/dev/shm
wallace-server:/mirror                     1.5T  618G  828G  43% /mirror
wallace-server:/acct                       1.5T  1.3T  266G  83% /acct
tmpfs                                      2.6G   68K  2.6G   1% /run/user/0
tmpfs                                      2.6G   28M  2.6G   2% /run/user/1000

>  - How big was the logfile (~/.cache/simple-scan/simple-scan.log)?

For another scan job that was likewise garbled (my son's homework) the
size was about 2 MB.

>  - What was recorded in the logfile at the time of the error?

I believe reportbug forwarded a copy but a compressed version, which
is much smaller, is also attached to this message.

>  - Does the error still occur after a reboot?

Yes, after each of at least two reboots.

Meanwhile I also installed simple-scan and Evince from unstable on my
otherwise bullseye machine (with backports) but the symptoms are the
same. Perhaps it is worthwhile to point out that I am using Sway, and
not Gnome.

> And so that I have all system information can you please start once:
>
>   bugreport -N 995216

You probably meant reportbug. I do not use it much but it worked very
well, especially with the custom data collection.

I use your tool almost every day. Thanks for looking into this issue!

Kind regards
Felix Lechner

Attachment: simple-scan.log.xz
Description: application/xz

Reply via email to