Bug 489653 – crash in Image Viewer: Openning an image

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 489653 - crash in Image Viewer: Openning an image


Summary:	crash in Image Viewer: Openning an image


Status:	RESOLVED DUPLICATE of bug 357405

Product:	eog
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	EOG Maintainers
QA Contact:	EOG Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-24 02:29 UTC by dfinol
Modified:	2007-10-27 12:09 UTC

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

Description dfinol 2007-10-24 02:29:35 UTC

Version: 2.18.2

What were you doing when the application crashed?
Openning an image


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.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 272920576 vsize: 272920576 resident: 6848512 share: 5197824 rss: 6848512 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193190530 rtime: 20 utime: 17 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496350416 (LWP 3457)]
[New Thread 1084229968 (LWP 3459)]
(no debugging symbols found)
0x0000003ef4ac82e6 in poll () from /lib64/libc.so.6

+ Trace 172417

Thread 2 (Thread 1084229968 (LWP 3459))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_cclosure_marshal_VOID__VOID
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /lib64/libglib-2.0.so.0
#6 g_log
from /lib64/libglib-2.0.so.0
#7 g_assert_warning
from /lib64/libglib-2.0.so.0
#8 eog_image_load
#9 ??
#10 eog_job_call_action
#11 ??
#12 g_cclosure_marshal_VOID__VOID
from /lib64/libglib-2.0.so.0
#13 start_thread
from /lib64/libpthread.so.0
#14 clone
from /lib64/libc.so.6



----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib64/libpango-1.0.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib64/libdbus-glib-1.so.2" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib64/libssl.so.6" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib64/libcrypto.so.6" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib64/libselinux.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Felix Riemann 2007-10-27 12:09:25 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 version 2.20. You may want to check for a software upgrade.


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