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 441466 - crash in Image Viewer: show F11 IT IS ALL TIME!...
crash in Image Viewer: show F11 IT IS ALL TIME!...
Status: RESOLVED DUPLICATE of bug 354154
Product: eog
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
: 448508 448590 454092 459993 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-05-26 18:54 UTC by litm
Modified: 2007-10-28 14:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description litm 2007-05-26 18:54:16 UTC 
Version: 2.18.0.1

What were you doing when the application crashed?
show F11
IT IS ALL TIME!
GOOD LOCK :)


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-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Free
Icon Theme: gnome

Memory status: size: 95723520 vsize: 95723520 resident: 48623616 share: 11784192 rss: 48623616 rss_rlim: 4294967295
CPU usage: start_time: 1180205517 rtime: 1439 utime: 1345 stime: 94 cutime:1 cstime: 3 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 -1226156352 (LWP 2105)]
[New Thread -1258021984 (LWP 2988)]
[New Thread -1227191392 (LWP 2375)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 136183

Thread 1 (Thread -1226156352 (LWP 2105))

  • #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 ---------------------
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
expr: błąd składni
--------------------------------------------------
Comment 1 palfrey 2007-05-27 14:30:39 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 2 Diego Escalante Urrelo (not reading bugmail) 2007-06-06 00:18:12 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!

(Since bugzilla policy for bad_stacktrace is now to mark as INCOMPLETE. Mass
changing all of these. Search for "dieguito-doing-incomplete-spam" to delete
all this from your inbox.)
Comment 3 Pedro Villavicencio 2007-06-17 21:30:52 UTC 
*** Bug 448590 has been marked as a duplicate of this bug. ***
Comment 4 Pedro Villavicencio 2007-06-17 23:56:48 UTC 
*** Bug 448508 has been marked as a duplicate of this bug. ***
Comment 5 Pedro Villavicencio 2007-07-05 23:44:40 UTC 
*** Bug 454092 has been marked as a duplicate of this bug. ***
Comment 6 Pedro Villavicencio 2007-07-05 23:45:10 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 7 Iestyn Pryce 2007-07-25 08:47:48 UTC 
*** Bug 459993 has been marked as a duplicate of this bug. ***
Comment 8 Claudio Saavedra 2007-10-28 14:38:39 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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