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 393453 - crash in Image Viewer: rotating an image then s...
crash in Image Viewer: rotating an image then s...
Status: RESOLVED DUPLICATE of bug 367788
Product: eog
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-06 10:32 UTC by Ben
Modified: 2007-01-06 10:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Ben 2007-01-06 10:32:33 UTC 
Version: 2.16.0.1

What were you doing when the application crashed?
rotating an image then saving it


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:32:54 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors ---------------------
save exif data
save exif data
save exif data
save exif data
save exif data
save exif data
save exif data
save exif data
save exif data
save exif data
Gdk-ERROR **: file gdkregion-generic.c: line 1082 (miUnionNonO): assertion failed: (y1 < y2)
aborting...
** (bug-buddy:4057): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 132452352 vsize: 0 resident: 132452352 share: 0 rss: 55033856 rss_rlim: 0
CPU usage: start_time: 1168078936 rtime: 0 utime: 11019 stime: 0 cutime:10133 cstime: 0 timeout: 886 it_real_value: 0 frequency: 0

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

(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 -1209137456 (LWP 3551)]
[New Thread -1284220016 (LWP 3555)]
[New Thread -1211237488 (LWP 3553)]
(no debugging symbols found)
0x0048b402 in __kernel_vsyscall ()

+ Trace 99817

Thread 2 (Thread -1284220016 (LWP 3555))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 gdk_region_get_rectangles
    from /usr/lib/libgdk-x11-2.0.so.0
  • #11 gdk_region_get_rectangles
    from /usr/lib/libgdk-x11-2.0.so.0
  • #12 gdk_region_union
    from /usr/lib/libgdk-x11-2.0.so.0
  • #13 gdk_window_invalidate_maybe_recurse
    from /usr/lib/libgdk-x11-2.0.so.0
  • #14 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_widget_style_get
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_widget_queue_resize
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_icon_view_set_cursor
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_image_set_from_pixbuf
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_image_new_from_pixmap
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 g_object_set_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_object_set
    from /lib/libgobject-2.0.so.0
  • #22 g_cclosure_marshal_VOID__VOID
  • #23 g_cclosure_marshal_VOID__VOID
  • #24 g_cclosure_marshal_VOID__VOID
  • #25 g_cclosure_marshal_VOID__VOID
  • #26 g_cclosure_marshal_VOID__VOID
  • #27 g_thread_create_full
    from /lib/libglib-2.0.so.0
  • #28 start_thread
    from /lib/libpthread.so.0
  • #29 clone
    from /lib/libc.so.6 






Comment 1


Christian Kirbach





          2007-01-06 10:34:40 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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