missing signal disconnect: simple-scan crashed with SIGSEGV in g_closure_invoke()

StacktraceTop:
 page_view_page_size_changed_cb (p=<optimized out>, self=0x117e990) at page-view.c:1899
 _page_view_page_size_changed_cb_page_size_changed (_sender=<optimized out>, self=0x117e990) at page-view.c:224
 g_closure_invoke (closure=0x7f997c18a180, return_value=0x0, n_param_values=1, param_values=0x11341a0, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.29.18/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=0xd062a0, emission_return=0x0, instance_and_params=0x11341a0) at /build/buildd/glib2.0-2.29.18/./gobject/gsignal.c:3272
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=0x7fffa480db88) at /build/buildd/glib2.0-2.29.18/./gobject/gsignal.c:3003

Still happening, unfortunately. :( Hope it's not isolated to the HP deskjet F4500 or something?

Status changed to 'Confirmed' because the bug affects multiple users.

Just happened to me on an HP Photosmart Wireless B109n-z. May be an HP issue...

Still crashing but now i'm getting Bug #861923

Might i make a suggestion (since i'm still getting this) - why does simple-scan not behave more like libreoffice does - if a document crashes, libreoffice tries to recover it.

Why not save a (temporary?) copy of everything that has been scanned so far in the session and then if the program crashes/closes unexpectedly, the user can continue with what's already been scanned with the choice to 'recover' the session?

Please. I'm tired of scanning through so many pages before it gives up and i lose everything that's been scanned before saving :(
If i need to scan 10 pages for a document and simple-scan crashes at the 7th page, i'd like to have the option to continue on from there, not start all the way back at page 1 again :(

For the data loss see Bug #897469

Just got this problem on Precise. Simple Scan has been behaving perfectly well for me right up until today.

Alright, this is getting annoying. Every single time I scan in one set of lecture notes in Simple Scan and save them, then click the button to start a new document and scan my first page, Simple Scan crashes as soon as the scan starts. Then the scanner is stuck like that until I re-open Simple Scan and start a brand-new scan.

The only workaround I have is to close and re-open Simple Scan in between documents in order to avoid this crash, which I can very easily reproduce.

Hi Christopher (and the other affected people), could you please read the following text, the wiki text linked, report make, model and ID of your scanner and try xsane? Thanks!

Hi there,

thank you for filing this bug and showing your interest in Simple Scan!

This seems to be a Hardware Issue, i.e. Simple Scan does not support
your scanner perfectly -- or possibly not at all.

Unfortunately such problems happen more often then they should, and while it might indeed be a problem with Simple Scan, in our experience, most of the time it is not.
This is why we prepared a check-list at [1] that will let you find out whether or not it really is a problem with Simple Scan and what your options are in either case.

Please read that list and tell us how you decided to proceed. I will set
this bug to "Incomplete", so a friendly robot will expire this bug in 60
days if you do not respond. However, we would really prefer to hear back
from you!

Best Regards
Michael

[1] https://help.ubuntu.com/community/SimpleScanHardwareIssues

If simple Scan doesn't support our hardware, then why does it work at all? Most of us using Simple Scan have scanned documents without issue. Its when we scan multiple documents that Simple Scan fails.

If it didn't work at all, then I could conclude its another piece of the puzzle that needs attention.

A followup on previous comment:

I installed and used xsane, and it works without fail.

Reviewing the information on the link you provided:
======
"if everything works with xsane, the problem is within Simple Scan and we will look into it"
=======

It appears the problem is with Simple Scan.

xscan info:

Vendor: Canon
Model: CanoScan N1220U
Type: flatbed scanner
Device: 004
Loaded backend: plustek:libusb:002
Sane version: 1.0.22

vmc: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/671996
implies that simple-scan might work now, too. can you please check this?

Your right. Simple Scan works. It failed using Ubuntu Precise alpha 2. Finding this bug report I was under the impression it was Simple Scan issue. Interesting is xsane work using Ubuntu Precise.

Simple works without failure under Fedora 16.

Simple Scan on Fedora 16 works, right?
xsane on Ubuntu Precise works, right?

What about Simple Scan on Ubuntu Precise BEFORE installing xsane on the machine?
What about Simple Scan on Ubuntu Precise AFTER installing xsane on the machine?

I am suspecting that the occurence of this bug depends on the absence of some configuration and or other software, that is not installed in Ubuntu (but in Fedora) that an installation of xsane pulls into Ubuntu...

Simple Scan works of Fedora 16.

Simple Scan failed on Precise before I installed xsane. Xsane work on Precise, so I didn't retest Simple Scan again on Precise.

I will test again on Precise after I install a new iso and without xsane. If it again fails I will try Simple Scan with xsane installed.

Simple Scan now works using today's, 02/14/12, Precise ISO installed.
[ Xsane was not installed.]

Still getting sporadic segmentation faults. Here's the crash file i found in /var/crash, if it's of any use. (I don't know what i should attach here specifically, but the problem clearly still exists here on 64 bit Precise.)

I just experienced this bug again in Precise. Interesting to note is that it now appears to fail like in comment #12, but between every two documents instead of one.

I am still affected by this bug as of this morning. I scanned three documents in Simple Scan: the first had 2 pages, and the second/third had 3 pages each. Simple Scan crashed while scanning the third page of the third document. The scanner head ran to the end of the tray and stayed there until I re-opened Simple Scan and told it to start the last document over.

My scanner is an HP Deskjet F4180 All-in-One printer/scanner. The device shows up in lsusb as:

Bus 002 Device 005: ID 03f0:7e04 Hewlett-Packard DeskJet F4100 Printer series

Scan image quality is not affected; the scan in progress is simply interrupted and lost.

I have so far been unable to reproduce the bug when running Simple Scan via simple-scan --debug > simple-scan.log 2>&1, but I will keep trying. I have installed xsane but have not tried using it yet; I plan to later today and I'll report back with additional info when I can. This bug is still very much real and interferes with my workflow every so often, and I'd rather help it be resolved than see it expire. I previously had no problems with scanning in 11.10, 11.04 and 10.04 with this scanner.

 switch to gscan2pdf, fare less crashes... I found when Simple Scan crashes, I will also lose my usb network card ( internal )... My gut feeling tells me there is and issue with Cups driver for All-in-One printers...

________________________________
 From: Christopher Kyle Horton <email address hidden>
To: <email address hidden>
Sent: Tuesday, May 29, 2012 9:34 AM
Subject: [Bug 843361] Re: simple-scan crashed with SIGSEGV in g_closure_invoke()

I am still affected by this bug as of this morning. I scanned three
documents in Simple Scan: the first had 2 pages, and the second/third
had 3 pages each. Simple Scan crashed while scanning the third page of
the third document. The scanner head ran to the end of the tray and
stayed there until I re-opened Simple Scan and told it to start the last
document over.

My scanner is an HP Deskjet F4180 All-in-One printer/scanner. The device
shows up in lsusb as:

Bus 002 Device 005: ID 03f0:7e04 Hewlett-Packard DeskJet F4100 Printer
series

Scan image quality is not affected; the scan in progress is simply
interrupted and lost.

I have so far been unable to reproduce the bug when running Simple Scan
via simple-scan --debug > simple-scan.log 2>&1, but I will keep trying.
I have installed xsane but have not tried using it yet; I plan to later
today and I'll report back with additional info when I can. This bug is
still very much real and interferes with my workflow every so often, and
I'd rather help it be resolved than see it expire. I previously had no
problems with scanning in 11.10, 11.04 and 10.04 with this scanner.

--
You received this bug notification because you are subscribed to a
duplicate bug report (920578).
https://bugs.launchpad.net/bugs/843361

Title:
  simple-scan crashed with SIGSEGV in g_closure_invoke()

Status in “simple-scan” package in Ubuntu:
  Incomplete

Bug description:
  Crashed after saving a scanned document. Unusual, erratic behaviour
  observed today and yesterday - When scanning, the program sometimes
  crashes before i've finished scanning all the documents i want and i
  have to start over :(

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: simple-scan 3.1.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Sep  6 23:58:22 2011
  DriverPackageVersions:
   libsane 1.0.22-2ubuntu1
   libsane-extras N/A
   hplip 3.11.7-0ubuntu5
   hpoj N/A
  ExecutablePath: /usr/bin/simple-scan
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110824)
  MachineType: ASUSTeK Computer Inc. K51AE
  ProcCmdline: simple-scan
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=1445dc4d-5ac1-46d2-a795-7560f8f987ec ro quiet pcie_aspm=force
  SegvAnalysis:
   Segfault happened at: 0x4152ea:    movl  $0x1,0x18(%rax)
   PC (0x004152ea) ok
   source "$0x1" ok
   destination "0x18(%rax)" (0xaaaaaaaaaaaaaac2) not located in a known VMA region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SimpleScanLog:

  SourcePackage: simple-scan
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/li...

y u are right theres an issue with all in one printers. printing has several issues too. if i print via adobe reader everything works perfectly, but evince is problematic. canon pixma mp610

I should probably note that in my all-in-one case I don't have issues with printing, just this problem with scanning.

Okay, here is my simple-scan.log created by running simple-scan --debug > simple-scan.log 2>&1 in a terminal and getting Simple Scan to crash on the start of my third document. (Ignore the GTK warnings about the icon theme: I'm using a third-party theme which explains those, but I get the crash even with the default icon theme.)

And like with comment #21, here's my own crash file that the last crash generated in /var/crash.

And last but not least, I tried to duplicate the crash in Xsane just now by scanning multiple multi-page documents, but I couldn't reproduce the issue. So, AFAIK the problem is still right in Simple Scan, and I believe I've followed all the steps outlined at https://help.ubuntu.com/community/SimpleScanHardwareIssues to warrant this bug being given another look.

If you need any additional information from me to this can be resolved (or at least the cause narrowed down) please let me know.

Christopher, from the log I can see you upgraded to Ubuntu 12.04 in the meantime, is this correct?

Hardware is:
HP Deskjet F4180 All-in-One printer/scanner.
Bus 002 Device 005: ID 03f0:7e04 Hewlett-Packard DeskJet F4100 Printer series

Also could you describe once more the steps to lead to the crash.
Especially important is:
- when does it crash (when receiving data from the device during scanning a page, when hitting "save", ...)
- what (high level) commands you send to the scanner (just hit "scan" - wait - hit "scan", or do you cancel scanning progress for one page and then scan another page, ...)
- do you perform any "software actions" in simple-scan (page reordering, cropping, ...)
- does it happen exactly 100% of the times, or 99% or any other guessed percentage of times?

also: other people having problems with simple-scan should create their own ticket unless there is strong indication that you encounter the exact same issue, not just "some random crash". thanks!

@Michael: Yes, that is correct for my laptop, which I'm currently using. I have also had this issue on my desktop computer running a fresh install of Ubuntu Precise during development (starting January 26th 2012, to be exact - see comment #11). I did not have any issues on Precise with it before that date, and I continue to have no issues with it on my desktop's 11.10 partition.

Here are my steps to reproduce the problem on Precise, as clearly as I can make them:
1. Open Simple Scan. For my scans, I normally use Text mode from the drop-down menu next to the Scan button, though I haven't tested the issue with Photo mode. Simple Scan remembers whether you used Text mode last time, so if you already had it set to that from a prior run, then there is no need to set it again.
2. Have a few multiple-page documents ready to scan for the rest of these steps.
3. Scan in the first document by placing each page in succession on the glass and pressing the Scan button to scan it in. After each page finishes scanning, remove it and place down the next one before pressing Scan again. This is simply normal usage of the scanner.
4. When you have finished scanning the entire document, you may choose to press the Save button to save your document first, though I don't think this is necessary to trigger the bug. Whether you do that or not, you will next want to click the leftmost button in the toolbar (its tooltip says "Start a new document") so the previous pages are cleared out of Simple Scan and you can start scanning the next document. *Up to this point, there should be no issues, regardless of how many pages are in the first document scanned.*
5. Repeat steps 3-4 above as you normally would with your other documents. Now, on any given page at random (not necessarily the first couple you scan, IMO it is most likely to occur on the second page of the second document or the ones following it), after you place the document on the scanner and click the scan button, the scanner head will start moving across the scanning bed as usual, but Simple Scan will briefly freeze with the spinner over the next page to be scanned appearing stuck as soon as the head starts moving, and then it will crash and close shortly before the scanning head can finish moving to the end of the glass. The scanning head will remain stuck at the end until you either:
- Turn the scanner off and turn it back on
- Reopen Simple Scan from the Dash
...at which point it will return to its initial position and you can resume scanning as usual until the bug is triggered again by following steps 1-5.

No other actions (i.e. page re-ordering or cropping) are followed when performing the above steps.

For me, this bug is relatively well-reproducible. It does not always show, but having longer documents, each of length 3 pages or more, increases your chances of seeing this bug. I would estimate that in practice I encounter it roughly 90% of the time. Note that the crash for me only seems to occur on or after the second page of the second document scanned before Simple Scan is closed, though the exact page when the crash will occur appears entirely random. In other words, repeating the same steps above ...

One last point I forgot to mention: if you only scan one document whenever you use Simple Scan, you will never see this bug. This bug ONLY appears when doing multiple documents without closing Simple Scan in between.

Thank you very much. From my point of view this sounds as if there is a small but crucial difference between:

A:
- close simple scan
- start simple scan

B:
- click "new document" in simple scan

these should be functionally equivalent (with some potential optimization in approach B).
in reality they are not, and that is the problem.

where could it fail:
- internal state of the scanner could be invalid after running the commands from approach B
- state of simple scan could be invalid after running the commands from approach B, this could especially affect buffers (freed them and kept dangling pointers, ...)

I will ask Robert to double check this.

I was suffering from a couple of flavors of this bug. It seems that in all cases callbacks for non-existant PageViews were getting triggered by signals related to Page updates. With the attached patch (against 3.4.2), I have not been able to reproduce any of those segfaults.

The patch does two things. In the BookView constructor, it does not try to add_cb existing pages until after the page_data hash has been initialized. Secondly, it adds a destructor for PageView that disconnects from all the Page signals that were connected to in the PageView constructor. Also, Book.clear() is changed to emit the cleared() signal before actually clearing the pages list structure.

The attachment "page_view_signal_lifetimes.diff" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

thank you for your help! joseph, are you familiar with bzr and launchpad? if so, robert (main developer) would greatly appreciate a pull request. thank you again!

I'm not familiar with launchpad, but I pushed a branch and sent a merge
request. Maybe slightly goofy because I worked off the 3.4 series.

On Sun, Jul 8, 2012 at 2:32 PM, Michael Nagel <email address hidden>wrote:

> thank you for your help! joseph, are you familiar with bzr and
> launchpad? if so, robert (main developer) would greatly appreciate a
> pull request. thank you again!
>
> ** Changed in: simple-scan (Ubuntu)
> Status: Incomplete => Confirmed
>
> ** Also affects: simple-scan
> Importance: Undecided
> Status: New
>
> ** Changed in: simple-scan
> Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/843361
>
> Title:
> simple-scan crashed with SIGSEGV in g_closure_invoke()
>
> Status in Simple Scan:
> Triaged
> Status in “simple-scan” package in Ubuntu:
> Confirmed
>
> Bug description:
> Crashed after saving a scanned document. Unusual, erratic behaviour
> observed today and yesterday - When scanning, the program sometimes
> crashes before i've finished scanning all the documents i want and i
> have to start over :(
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.10
> Package: simple-scan 3.1.5-0ubuntu1
> ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
> Uname: Linux 3.0.0-10-generic x86_64
> Architecture: amd64
> CrashCounter: 1
> Date: Tue Sep 6 23:58:22 2011
> DriverPackageVersions:
> libsane 1.0.22-2ubuntu1
> libsane-extras N/A
> hplip 3.11.7-0ubuntu5
> hpoj N/A
> ExecutablePath: /usr/bin/simple-scan
> InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110824)
> MachineType: ASUSTeK Computer Inc. K51AE
> ProcCmdline: simple-scan
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic
> root=UUID=1445dc4d-5ac1-46d2-a795-7560f8f987ec ro quiet pcie_aspm=force
> SegvAnalysis:
> Segfault happened at: 0x4152ea: movl $0x1,0x18(%rax)
> PC (0x004152ea) ok
> source "$0x1" ok
> destination "0x18(%rax)" (0xaaaaaaaaaaaaaac2) not located in a known
> VMA region (needed writable region)!
> SegvReason: writing unknown VMA
> Signal: 11
> SimpleScanLog:
>
> SourcePackage: simple-scan
> StacktraceTop:
> ?? ()
> g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> g_signal_emit_valist () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> g_signal_emit_by_name () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> Title: simple-scan crashed with SIGSEGV in g_closure_invoke()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
> dmi.bios.date: 12/09/2009
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 210
> dmi.board.asset.tag: ATN12345678901234567
> dmi.board.name: K51AE
> dmi.board.vendor: ASUSTeK Computer Inc.
> dmi.board.version: 1.0
> dmi.chassis.type: 10
> dmi.chassis.vendor: ASUSTeK Computer Inc.
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr210:bd12/09/2009:svnASUSTeKComputerInc.:pnK5...

Hi Joseph, Robert made a commit based on your changes -- albeit with some modifications:
http://bazaar.launchpad.net/~simple-scan-team/simple-scan/trunk/revision/586

can you check if it fixes the crashes as well and what you think about skipping some of your changes?

https://code.launchpad.net/~jnuzman/simple-scan/bug-843361/+merge/113867

resulted in

http://bazaar.launchpad.net/~simple-scan-team/simple-scan/trunk/revision/586
http://bazaar.launchpad.net/~simple-scan-team/simple-scan/trunk/revision/588
http://bazaar.launchpad.net/~simple-scan-team/simple-scan/trunk/revision/589

please check if this bug is still reproducible with these changes.

With main trunk (rev 589 + commit 581 backed out to ease building in my environment), I can no longer reproduce the bug.

I've got to say, judging by the code in the revisions mentioned in comment 39, this bug is very likely squashed now. I'd like to build simple-scan from source and be 100% sure, but i'm having difficulty 'make'ing the package.

Looking forward to the next .deb release of simple-scan anyway, because this was one VERY annoying issue that needed to be solved since it first cropped up for me about a year ago. I assume quantal will be getting a new version soon enough but i really hope that the revisions land back in precise etc as well.

Honestly, all i can say is great work on the program, it's really something :)

@Anthony: what is your problem with building simple scan? i'd like to enable as many people as possible to build simple scan without any major roadblocks.

Best Regards
Michael

well, i grabbed the latest code from the trunk bzr branch and i was hoping to follow this (found these instructions on an unrelated simple-scan bug here on launchpad.net)

$ sudo apt-get build-dep simple-scan
$ ./autogen.sh --prefix=`pwd`/install
$ make
$ make install
$ ./src/simple-scan

Problem is that the first 2 steps are ok, and then i do "./configure", but when i then do "make" there are 5 errors in the vala code preventing it from compiling properly. (See attached .txt file below)
Is it that i'm missing a specific package that wasn't pulled in? Are these errors preventing anyone else from compiling?

Errors when trying to 'make'.

Anthony, please see: Bug #1029492

Thanks, michael!

I successfully compiled the latest build (with the revert 581 patch from jnuzman) and tested it out on Ubuntu precise where it would usually crash. Good news: looks like this bug is indeed squashed :)

However...i can now readily reproduce Bug #1029670

Hey, this wasn't merged into 12.04 and still crashes - 12.10's package has this fixed and works properly.

Since Anthony Harrington verified the bzr branch to work, it'd be nice to get this merged or something.

Thanks for the patches.

yeah, this is a prime canidate for a bugfix to be backported. someone has to do it, though...

See bug 1158558 for backported crash fixes

Fixed in 3.4.3, 3.5.90