/usr/bin/simple-scan:11:page_view_get_pixel:page_view_set_pixel:page_view_update_preview:page_view_update_page_view:page_view_render

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding simple-scan. This problem was most recently seen with version 3.20.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/5d14b5ef920c7cf703fc36d412ecf55b28c6621e contains more details.

[Olivier Tilloy (osomon)]

Confirming as I'm seeing this on a machine running 16.04 amd64, fully up-to-date. According to the owner of that machine, it started happening fairly recently (in the last few months, trying to get a more accurate date and I will report here).

[Olivier Tilloy (osomon)]

From comment #2 in duplicate bug #1712991, a user reported that deleting ~/.cache/simple-scan makes the problem go away.

[Bartosz Kosiorek (gang65)]

I'm an Simple-scan developer:
https://gitlab.gnome.org/GNOME/simple-scan/-/blob/master/simple-scan.doap#L27
Can I have access to these bug reports?

[Olivier Tilloy (osomon)]

Access to errors.ubuntu.com requires a Launchpad account (and I'm not sure if an extra permission).
For convenience, I'm attaching the stacktrace here.

[Olivier Tilloy (osomon)]

And I'm also copying the relevant parts of the description of bug #1712991, which is private (not sure why but it's not up to me to decide whether it should be made public):

===============================================================

1. Laptop switched of (no power) after scanning document
2. After restart can not start star simple-scan
simple-scan

(simple-scan:3519): Gtk-WARNING **: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Segmentation fault (core dumped)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: simple-scan 3.25.90-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 25 09:41:56 2017
ExecutablePath: /usr/bin/simple-scan

===============================================================

That plus the comment about deleting the cache makes me think that an abrupt shutdown (e.g. a power outage) can result in a corrupted cache, which simple-scan isn't able to gracefully handle.

[Brian Murray (brian-murray)]

On Mon, Dec 07, 2020 at 02:03:43PM -0000, Bartosz Kosiorek wrote:
> I'm an Simple-scan developer:
> https://gitlab.gnome.org/GNOME/simple-scan/-/blob/master/simple-scan.doap#L27
> Can I have access to these bug reports?

You an request access to crash reports in the Ubuntu Error Tracker via
the following link:

https://forms.canonical.com/reports/

--
Brian Murray

[Olivier Tilloy (osomon)]

I don't have physical access to the machine I was mentioning in comment #1, but I had the owner delete the cache, and the crash went away, so this confirms my suspicion that simple-scan isn't able to gracefully handle a corrupted cache.

That user also confirmed that the problem first happened after a power outage resulted in an abrupt shutdown while they were using simple-scan to scan documents.