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?
--
You received this bug
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
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
ubu...@nailor.devzero.dewrote:
thank you for your help! joseph, are you familiar with bzr and
launchpad? if
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
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
@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
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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
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
...@bugs.launchpad.net
To: tlof...@yahoo.com
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
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I should probably note that in my all-in-one case I don't have issues
with printing, just this problem with scanning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/843361
Title:
simple-scan
And like with comment #21, here's my own crash file that the last crash
generated in /var/crash.
** Attachment added: _usr_bin_simple-scan.1000.crash
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/843361/+attachment/3169409/+files/_usr_bin_simple-scan.1000.crash
--
You received
Okay, here is my simple-scan.log created by running simple-scan --debug
simple-scan.log 21 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
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
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
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.
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the
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.)
** Attachment added: contents of the crash file
Simple Scan now works using today's, 02/14/12, Precise ISO installed.
[ Xsane was not installed.]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/843361
Title:
simple-scan crashed with
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.
--
You received this bug notification because you are
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
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
vmc: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/671996
implies that simple-scan might work now, too. can you please check this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
** Changed in: simple-scan (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/843361
Title:
simple-scan crashed with SIGSEGV in g_closure_invoke()
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,
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
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.
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
Just got this problem on Precise. Simple Scan has been behaving
perfectly well for me right up until today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/843361
Title:
simple-scan crashed
For the data loss see Bug #897469
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/843361
Title:
simple-scan crashed with SIGSEGV in g_closure_invoke()
To manage notifications about this bug
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
Still crashing but now i'm getting Bug #861923
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/843361
Title:
simple-scan crashed with SIGSEGV in g_closure_invoke()
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: simple-scan (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/843361
Just happened to me on an HP Photosmart Wireless B109n-z. May be an HP
issue...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/843361
Title:
simple-scan crashed with SIGSEGV in
Still happening, unfortunately. :( Hope it's not isolated to the HP
deskjet F4500 or something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/843361
Title:
simple-scan crashed with SIGSEGV
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/843361
Title:
simple-scan crashed with SIGSEGV in g_closure_invoke()
To manage notifications about this bug go to:
** Visibility changed to: Private
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/843361
Title:
simple-scan crashed with SIGSEGV in g_closure_invoke()
To manage notifications about this bug
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/843361
Title:
simple-scan crashed with SIGSEGV in g_closure_invoke()
To manage notifications about this bug
38 matches
Mail list logo
