Bug 493428 – crash in gThumb Image Viewer: Viewing a JPEG file that...

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 493428 - crash in gThumb Image Viewer: Viewing a JPEG file that...


Summary:	crash in gThumb Image Viewer: Viewing a JPEG file that...


Status:	RESOLVED DUPLICATE of bug 485721

Product:	gthumb
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Paolo Bacchilega
QA Contact:	Paolo Bacchilega

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-04 16:53 UTC by bgee
Modified:	2007-11-04 16:56 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description bgee 2007-11-04 16:53:16 UTC

What were you doing when the application crashed?
Viewing a JPEG file that was created by kst.  I had just hit the 'V' key to go full-screen when the crash happened.


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-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 133316608 vsize: 133316608 resident: 92852224 share: 21401600 rss: 92852224 rss_rlim: 4294967295
CPU usage: start_time: 1194194909 rtime: 614 utime: 356 stime: 258 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 -1208453408 (LWP 17713)]
[New Thread -1249383536 (LWP 17817)]
[New Thread -1248855152 (LWP 17816)]
[New Thread -1243198576 (LWP 17815)]
[New Thread -1242670192 (LWP 17814)]
[New Thread -1230845040 (LWP 17729)]
[New Thread -1230316656 (LWP 17728)]
[New Thread -1229788272 (LWP 17727)]
[New Thread -1229259888 (LWP 17726)]
[New Thread -1228731504 (LWP 17721)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 175152

Thread 1 (Thread -1208453408 (LWP 17713))

#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_changed
#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 ---------------------
  Major opcode:  159
  Minor opcode:  6
  Resource id:  0x187
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1406b90
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  159
  Minor opcode:  6
  Resource id:  0x1406b90
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  159
  Minor opcode:  6
  Resource id:  0x187
--------------------------------------------------

Comment 1 Michael Chudobiak 2007-11-04 16:56:16 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. It should be solved in the next software version. You may want to check for a software upgrade.


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