Comments on: SANE design http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/ Make scanning as easy as printing for both users and developers Mon, 22 Feb 2010 16:50:23 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Pēteris Krišjānis http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/comment-page-1/#comment-91 Pēteris Krišjānis Sun, 24 Feb 2008 18:59:00 +0000 http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/#comment-91 I fully support your idea about reworking SANE, as I have been very frequently plagued by very slow and buggy scanning. It is sad to hear that SANE 2 won't be that hero who will save us. I fully support your idea about reworking SANE, as I have been very frequently plagued by very slow and buggy scanning. It is sad to hear that SANE 2 won’t be that hero who will save us.

]]> By: Étienne Bersac http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/comment-page-1/#comment-90 Étienne Bersac Sun, 10 Feb 2008 19:30:00 +0000 http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/#comment-90 @akaladis : see http://bugzilla.gnome.org/ . @akaladis : see http://bugzilla.gnome.org/ .

]]> By: akaladis http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/comment-page-1/#comment-89 akaladis Sun, 10 Feb 2008 18:40:00 +0000 http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/#comment-89 where do i file a bug? where do i file a bug?

]]> By: Étienne Bersac http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/comment-page-1/#comment-88 Étienne Bersac Sat, 09 Feb 2008 11:11:00 +0000 http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/#comment-88 Please file a bug, posting comment won't help. Please file a bug, posting comment won’t help.

]]> By: akaladis http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/comment-page-1/#comment-87 akaladis Sat, 09 Feb 2008 09:00:00 +0000 http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/#comment-87 can we at least free memory between scans? for every 150 dpi page i scan, flegita climbs 5% on my memory. and mind you, that's 5% of 2gb! the only 'solution' is to restart gnome-scan after every page i scan. and of course i haven't been able to do a scan at 1200dpi since i run out of memory and flegita is killed. can we at least free memory between scans? for every 150 dpi page i scan, flegita climbs 5% on my memory. and mind you, that’s 5% of 2gb! the only ‘solution’ is to restart gnome-scan after every page i scan. and of course i haven’t been able to do a scan at 1200dpi since i run out of memory and flegita is killed.

]]> By: Étienne Bersac http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/comment-page-1/#comment-84 Étienne Bersac Sun, 27 Jan 2008 18:42:00 +0000 http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/#comment-84 Gegl is know to have memleaks i can't workaround from Gnome Scan.<br/><br/>Regards, Gegl is know to have memleaks i can’t workaround from Gnome Scan.

Regards,

]]> By: akaladis http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/comment-page-1/#comment-83 akaladis Sun, 27 Jan 2008 18:28:00 +0000 http://blogs.gnome.org/gnome-scan/2008/01/23/sane-design/#comment-83 speaking of future... i just noticed this:<br/><br/>after doing a good few scans in a row (using the forward button) i noticed that flegita was using about 1gb of ram. as soon as i hit the stop button, everything went back to normal.<br/><br/>this is on a gutsy desktop in sync with the gnome-scan ppa packages. speaking of future… i just noticed this:

after doing a good few scans in a row (using the forward button) i noticed that flegita was using about 1gb of ram. as soon as i hit the stop button, everything went back to normal.

this is on a gutsy desktop in sync with the gnome-scan ppa packages.

]]>