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 487439 - crash in gThumb Image Viewer: I was downloading pictur...
crash in gThumb Image Viewer: I was downloading pictur...
Status: RESOLVED DUPLICATE of bug 485721
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-10-17 09:38 UTC by copperjoy2002
Modified: 2007-10-17 11:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description copperjoy2002 2007-10-17 09:38:30 UTC
What were you doing when the application crashed?
I was downloading pictures...


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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Raleigh
Icon Theme: Fedora

Memory status: size: 72790016 vsize: 72790016 resident: 32305152 share: 22155264 rss: 32305152 rss_rlim: 4294967295
CPU usage: start_time: 1192613842 rtime: 90 utime: 80 stime: 10 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 -1208645920 (LWP 5181)]
[New Thread -1249588336 (LWP 5205)]
[New Thread -1249059952 (LWP 5204)]
[New Thread -1248531568 (LWP 5203)]
[New Thread -1248003184 (LWP 5202)]
[New Thread -1232458864 (LWP 5199)]
[New Thread -1231930480 (LWP 5198)]
[New Thread -1231402096 (LWP 5197)]
[New Thread -1230873712 (LWP 5195)]
[New Thread -1230345328 (LWP 5190)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208645920 (LWP 5181))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 add_scheme_if_absent
    from /usr/lib/gthumb/libgthumb.so
  • #5 uricmp
    from /usr/lib/gthumb/libgthumb.so
  • #6 g_list_find_custom
    from /lib/libglib-2.0.so.0
  • #7 ??
  • #8 gthumb_marshal_VOID__INT_BOXED
    from /usr/lib/gthumb/libgthumb.so
  • #9 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #13 gth_monitor_notify_update_files
  • #14 all_windows_notify_files_created
  • #15 ??
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
QMetaObject::findSignal:smoothblend::smoothblendClient: Conflict with KDecoration::keepAboveChanged(bool)
QMetaObject::findSignal:smoothblend::smoothblendClient: Conflict with KDecoration::keepBelowChanged(bool)
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x74
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
Corrupt JPEG data: premature end of data segment
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-10-17 11:41:54 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in gthumb 2.10.7.


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