After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 625698 - wont import
wont import
Status: RESOLVED OBSOLETE
Product: gthumb
Classification: Other
Component: general
2.10.x
Other Linux
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2010-07-31 01:03 UTC by simon
Modified: 2011-07-07 18:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description simon 2010-07-31 01:03:15 UTC
when run in terminal i see this;


(gthumb:6324): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
Comment 1 Paolo Bacchilega 2010-08-01 07:39:32 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Comment 2 simon 2010-08-01 16:27:29 UTC
occurrence; when trying to import from camera

reproduces; always 

system; linux mint 9, (ubuntu, deb) x64

sequence; recent fresh OS install, install various packages, got new camera, installed gthumb, plugged in camera, see import screen with multiple thumbs, select required, press import, progress bar appears, nothing further happens.

(fired up via terminal to be able to see error message above.)

this seems to be a problem in the calculation of the progress bar size, so it might help to know that these pictures are 5-6MB (.JPG's) and are mixed in with movies (.AVI's) some many hundreds of MB.


packages (installed on top of mint 9);
acpi	install
add-apt-key	install
adium-theme-ubuntu	install
apturl	install
assogiate	install
avahi-utils	install
branding-ubuntu	install
brasero-common	install
busybox-static	install
cheese	install
chromium-browser	install
cpu-checker	install
debhelper	install
devede	install
diffutils	install
dpkg-dev	install
execstack	install
fancontrol	install
ffmpeg	install
fglrx	install
firefox-branding	install
flvstreamer	install
fortunes-husse	install
frozen-bubble	install
f-spot	install
gdm-guest-session	install
gimp-help-en	install
gnome-games	install
gnome-user-guide-en	install
gnome-user-share	install
gnupg-curl	install
gstreamer0.10-gnonlin	install
gthumb	install
gwibber	install
gwibber-service	install
hddtemp	install
hunspell-en-ca	install
icedtea6-plugin	install
imagemagick	install
indicator-applet-session	install
indicator-application	install
indicator-me	install
indicator-session	install
indicator-sound	install
initramfs-tools-bin	install
intel-gpu-tools	install
irqbalance	install
language-support-writing-en	install
libappindicator0	install
libass4	install
libbind9-60	install
libcap-ng0	install
libcdio10	install
libcelt0-0	install
libcouchdb-glib-1.0-2	install
libdb4.8	install
libdbusmenu-glib1	install
libdbusmenu-gtk1	install
libdesktopcouch-glib-1.0-2	install
libdirac-encoder0	install
libdmraid1.0.0.rc16	install
libdns64	install
libdrm-nouveau1	install
libdynamite0	install
libesd0	install
libevdocument2	install
libevview2	install
libfaad2	install
libfile-copy-recursive-perl	install
libflite1	install
libgdata6	install
libgme0	install
libgmime2.4-cil	install
libgnome-desktop-2-17	install
libgoocanvas3	install
libgoocanvas-common	install
libgraphite3	install
libgssdp-1.0-2	install
Comment 3 Michael Chudobiak 2010-08-03 12:32:09 UTC
Paolo,

I'm pretty sure this was fixed in 2.10.x branch by:

http://git.gnome.org/browse/gthumb/commit/?h=gthumb-2-10&id=3c7d20b7022a0c4a6fb76500c20c7f836f66d899

However, a 2.10.x release has not been made since then.

More details: https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/486617

I would suggest a 2.10.x release, since this is a major bug for some users.

- Mike
Comment 4 Paolo Bacchilega 2011-07-07 18:12:28 UTC
the import code is changed a lot in version 2.12, feel free to reopen the report if this bug still happens in version 2.12.