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 569256 - crash in Image Viewer: It was a double click on...
crash in Image Viewer: It was a double click on...
Status: RESOLVED DUPLICATE of bug 523463
Product: eog
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-26 22:50 UTC by toebix
Modified: 2009-01-27 11:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description toebix 2009-01-26 22:50:26 UTC 
Version: 2.22.3

What were you doing when the application crashed?
It was a double click on a jpg photo file within nautilus


Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaAquaIsh
Icon Theme: MacUltimate_Leopard

Memory status: size: 42418176 vsize: 42418176 resident: 17854464 share: 11026432 rss: 17854464 rss_rlim: 4294967295
CPU usage: start_time: 1233010147 rtime: 52 utime: 42 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb69d7b40 (LWP 7867)]
[New Thread 0xb6802b90 (LWP 7868)]
0xb7f00424 in __kernel_vsyscall ()

+ Trace 211902

Thread 1 (Thread 0xb69d7b40 (LWP 7867))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 IA__g_main_context_check
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2491
  • #8 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2642
  • #9 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
  • #10 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.11/gtk/gtkmain.c line 1163
  • #11 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (610 sec old) ---------------------
(/usr/share/texmf-texlive/fonts/source/public/cm/romms.mf] [63 [40] [41] [42]
[43] [44] [45] [46] [47] [58] [59]
[64] [60] [61] [62] [63] [91] [92] [93] [94]
[95]) ) )
Font metrics written on cmmib10.tfm.
Output written on cmmib10.480gf (128 characters, 20644 bytes).
Transcript written on cmmib10.log.
] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78] [79]
[80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90] [91] [92] [93] [94] [95]
[96] [97] [98] [99] [100] [101] [102] [103] [104] [105] [106] [107] [108] [109]
[110] [111] [112] [113] [114] [115] [116mktexpk: /home/tobias/.texmf-var/fonts/pk/ljfour/public/cm/cmmib10.480pk: successfully generated.
] [117] [118kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 cmmib10
] [119] [120] [121] [122]
[123] [124] [125] [126] [130] [131] [132] [133
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Felix Riemann 2009-01-27 11:40:21 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 523463 ***