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 519310 - crash in Image Viewer: Change to Full-Screen by...
crash in Image Viewer: Change to Full-Screen by...
Status: RESOLVED DUPLICATE of bug 320206
Product: eog
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-28 15:37 UTC by masahase
Modified: 2008-02-28 16:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description masahase 2008-02-28 15:37:42 UTC
Version: 2.18.2

What were you doing when the application crashed?
Change to Full-Screen by pressing F11 key


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 104468480 vsize: 104468480 resident: 48640000 share: 20070400 rss: 48640000 rss_rlim: 4294967295
CPU usage: start_time: 1204211834 rtime: 18024 utime: 16917 stime: 1107 cutime:38 cstime: 149 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208645920 (LWP 18915)]
[New Thread -1258484848 (LWP 18965)]
[New Thread -1212109936 (LWP 18926)]
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208645920 (LWP 18915))

  • #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_cache_add
    at eog-image-cache.c line 87
  • #5 job_image_load_finished
    at eog-full-screen.c line 707
  • #6 eog_job_call_finished
    at eog-job.c line 442
  • #7 job_finished_cb
    at eog-job-manager.c line 65
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #12 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 main
    at main.c line 651
  • #0 __kernel_vsyscall


----------- .xsession-errors (1578701 sec old) ---------------------
ウィンドウ・マネージャの警告: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e16058 (* 114.jpg )
ウィンドウ・マネージャの警告: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
ウィンドウ・マネージャの警告: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e16058 (* 115.jpg )
ウィンドウ・マネージャの警告: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
ウィンドウ・マネージャの警告: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e16058 (* 116.jpg )
ウィンドウ・マネージャの警告: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
ウィンドウ・マネージャの警告: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e16058 (* 117.jpg )
ウィンドウ・マネージャの警告: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
ウィンドウ・マネージャの警告: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e16058 (* 118.jpg )
ウィンドウ・マネージャの警告: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
ウィンドウ・マネージャの警告: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e16058 (* 119.jpg )
ウィンドウ・マネージャの警告: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
ウィンドウ・マネージャの警告: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e16058 (* 120.jpg )
ウィンドウ・マネージャの警告: meta_window_activate called by a pager with a 0 timestamp; the pager nee
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Felix Riemann 2008-02-28 16:14:33 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 320206 ***