Bug 492450 – crash in Image Viewer: abriendo Nuevo Imagen de...

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 492450 - crash in Image Viewer: abriendo Nuevo Imagen de...


Summary:	crash in Image Viewer: abriendo Nuevo Imagen de...


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-11-01 19:31 UTC by sachelaridi
Modified:	2007-11-20 11:48 UTC

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

Description sachelaridi 2007-11-01 19:31:04 UTC

Version: 2.18.2

What were you doing when the application crashed?
abriendo Nuevo Imagen de mapa de bits.bmp


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_Cairo-Curve
Icon Theme: Fedora

Memory status: size: 34996224 vsize: 34996224 resident: 7569408 share: 6295552 rss: 7569408 rss_rlim: 4294967295
CPU usage: start_time: 1193945251 rtime: 6 utime: 4 stime: 2 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208367392 (LWP 20625)]
[New Thread -1210754160 (LWP 20626)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 174423

Thread 2 (Thread -1210754160 (LWP 20626))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 eog_image_load
#5 ??
#6 eog_job_call_action
#7 ??
#8 ??
from /lib/libglib-2.0.so.0
#9 start_thread
from /lib/libpthread.so.0
#10 clone
from /lib/libc.so.6



----------- .xsession-errors (16 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: Failed to close thumbnail pixbuf loader for /root/Escritorio/Nuevo Imagen de mapa de bits.bmp: No se ha reconocido el formato de imagen del archivo
** Message: Failed to close thumbnail pixbuf loader for /root/Escritorio/Nuevo Imagen de mapa de bits.bmp: No se ha reconocido el formato de imagen del archivo
** Message: Failed to close thumbnail pixbuf loader for /root/Escritorio/Nuevo Imagen de mapa de bits.bmp: No se ha reconocido el formato de imagen del archivo
** Message: Failed to close thumbnail pixbuf loader for /root/Escritorio/Nuevo Imagen de mapa de bits.bmp: No se ha reconocido el formato de imagen del archivo
** Message: Failed to close thumbnail pixbuf loader for /root/Escritorio/Nuevo Imagen de mapa de bits.bmp: No se ha reconocido el formato de imagen del archivo
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-11-20 11:48:45 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 357405 ***