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 492355 - crash in gThumb Image Viewer: Viewing images full scre...
crash in gThumb Image Viewer: Viewing images full scre...
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-11-01 13:33 UTC by aescallon
Modified: 2007-11-01 13:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description aescallon 2007-11-01 13:33:12 UTC 
What were you doing when the application crashed?
Viewing images full screen.  Cllicked left mouse button


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: 75055104 vsize: 75055104 resident: 31191040 share: 21884928 rss: 31191040 rss_rlim: 4294967295
CPU usage: start_time: 1193923664 rtime: 179 utime: 165 stime: 14 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 -1209125152 (LWP 4050)]
[New Thread -1252467824 (LWP 4077)]
[New Thread -1250882672 (LWP 4076)]
[New Thread -1251411056 (LWP 4075)]
[New Thread -1251939440 (LWP 4074)]
[New Thread -1235383408 (LWP 4061)]
[New Thread -1234855024 (LWP 4060)]
[New Thread -1234326640 (LWP 4059)]
[New Thread -1233798256 (LWP 4058)]
[New Thread -1233269872 (LWP 4053)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 174357

Thread 1 (Thread -1209125152 (LWP 4050))

  • #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 ---------------------
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  143
  Minor opcode:  6
  Resource id:  0x14011e2
Xlib:  extension "DPMS" missing on display ":0.0".
Xlib:  extension "MIT-SCREEN-SAVER" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
Xlib:  extension "SHAPE" missing on display ":0.0".
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  143
  Minor opcode:  6
  Resource id:  0x164
Xlib:  extension "SHAPE" missing on display ":0.0".
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-11-01 13:35:22 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 2.10.7,
which is available in the F7 testing repo.

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