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 491183 - crash in gThumb Image Viewer: I have a foto viewed in ...
crash in gThumb Image Viewer: I have a foto viewed in ...
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-28 21:12 UTC by Martin Wildam
Modified: 2007-10-28 22:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Martin Wildam 2007-10-28 21:12:30 UTC
What were you doing when the application crashed?
I have a foto viewed in fullscreen mode and pressed delete to move it to trash. The problem is reproducable in fullscreen mode. If not in fullscreen mode then there is no crash.


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.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 242335744 vsize: 242335744 resident: 143896576 share: 36069376 rss: 143896576 rss_rlim: 4294967295
CPU usage: start_time: 1193606034 rtime: 1980 utime: 1840 stime: 140 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208400160 (LWP 5395)]
[New Thread -1355330672 (LWP 5440)]
[New Thread -1276232816 (LWP 5437)]
[New Thread -1275704432 (LWP 5436)]
[New Thread -1275176048 (LWP 5435)]
[New Thread -1274647664 (LWP 5434)]
[New Thread -1366877296 (LWP 5425)]
[New Thread -1366348912 (LWP 5424)]
[New Thread -1365820528 (LWP 5423)]
[New Thread -1270883440 (LWP 5400)]
[New Thread -1270355056 (LWP 5399)]
(no debugging symbols found)
0x00608402 in __kernel_vsyscall ()

Thread 1 (Thread -1208400160 (LWP 5395))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/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 ??
  • #17 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #22 ??
  • #23 ??
    from /lib/i686/nosegneg/libpthread.so.0
  • #24 ??
  • #25 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #26 ??
  • #27 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (55 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
(bug-buddy:5375): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject'
(bug-buddy:5375): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:5375): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:5375): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-10-28 22:57:01 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 ***