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 454092 - crash in Image Viewer:
crash in Image Viewer:
Status: RESOLVED DUPLICATE of bug 441466
Product: eog
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-05 21:45 UTC by diafo
Modified: 2007-07-05 23:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description diafo 2007-07-05 21:45:05 UTC
Version: 2.18.0.1

What were you doing when the application crashed?



Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-14mdv #1 SMP Wed May 9 21:11:43 MDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Blue
Icon Theme: gnome

Memory status: size: 96137216 vsize: 96137216 resident: 58662912 share: 10723328 rss: 58662912 rss_rlim: 4294967295
CPU usage: start_time: 1183671824 rtime: 3877 utime: 3709 stime: 168 cutime:0 cstime: 5 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/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226373440 (LWP 16296)]
[New Thread -1268065376 (LWP 16299)]
[New Thread -1228268640 (LWP 16297)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226373440 (LWP 16296))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 eog_image_cache_add
  • #5 ??
  • #6 eog_job_call_finished
  • #7 ??
  • #8 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #12 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (144 sec old) ---------------------
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00063 (OpenOffice)
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8
DOUBLE-CLICK: 400 --> -1 THRESHOLD: 8 --> -1 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8
Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8
Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8
Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8
Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8
DOUBLE-CLICK: 400 --> -1 THRESHOLD: 8 --> -1 
(eog:16130): Eog-CRITICAL **: eog_image_cache_add: assertion `EOG_IS_IMAGE_CACHE (cache)' failed
(eog:16130): Eog-CRITICAL **: eog_image_list_iter_valid: assertion `EOG_IS_IMAGE_LIST (list)' failed
(eog:16130): Eog-CRITICAL **: eog_image_list_iter_valid: assertion `EOG_IS_IMAGE_LIST (list)' failed
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-07-05 23:44: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 441466 ***