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 495842 - crash in gThumb Image Viewer: CONECTANDO LA CAMARA
crash in gThumb Image Viewer: CONECTANDO LA CAMARA
Status: RESOLVED DUPLICATE of bug 391004
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-11-11 12:01 UTC by aspidx
Modified: 2007-11-11 21:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description aspidx 2007-11-11 12:01:16 UTC 
What were you doing when the application crashed?
CONECTANDO LA CAMARA


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 176259072 vsize: 176259072 resident: 128696320 share: 19898368 rss: 128696320 rss_rlim: 4294967295
CPU usage: start_time: 1194782426 rtime: 142 utime: 93 stime: 49 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gthumb'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208903968 (LWP 11630)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 176980

Thread 1 (Thread -1208903968 (LWP 11630))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 exif_set_sshort
    from /usr/lib/libexif.so.12
  • #5 exif_set_short
    from /usr/lib/libexif.so.12
  • #6 uricmp
    from /usr/lib/libexif.so.12
  • #7 uricmp
    from /usr/lib/libexif.so.12
  • #8 exif_data_save_data
    from /usr/lib/libexif.so.12
  • #9 ??
    from /usr/lib/libgphoto2/2.3.1/directory.so
  • #10 uricmp
    from /usr/lib/libgphoto2.so.2
  • #11 gp_filesystem_get_file
    from /usr/lib/libgphoto2.so.2
  • #12 gp_camera_file_get
    from /usr/lib/libgphoto2.so.2
  • #13 ??
    from /usr/lib/gthumb/modules/libphotoimporter.so
  • #14 ??
    from /usr/lib/gthumb/modules/libphotoimporter.so
  • #15 ??
    from /lib/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (30559 sec old) ---------------------
(evolution:5173): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:5173): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:5173): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:5173): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:5173): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:5173): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:5173): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(evolution:5173): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-11-11 21:28:49 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 391004 ***