Bug 373721 – crash in Image Viewer: When i fullscreen and ag...

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 373721 - crash in Image Viewer: When i fullscreen and ag...


Summary:	crash in Image Viewer: When i fullscreen and ag...


Status:	RESOLVED INCOMPLETE

Product:	eog
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	EOG Maintainers
QA Contact:	EOG Maintainers

URL:
Whiteboard:

Duplicates:	374046 (view as bug list)
Depends on:
Blocks:

Reported:	2006-11-11 07:44 UTC by Shahriar
Modified:	2007-01-28 19:37 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Shahriar 2006-11-11 07:44:25 UTC

Version: 2.16.0.1

What were you doing when the application crashed?
When i fullscreen and again back to default,


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 125661184 vsize: 0 resident: 125661184 share: 0 rss: 28909568 rss_rlim: 0
CPU usage: start_time: 1163230893 rtime: 0 utime: 1029 stime: 0 cutime:956 cstime: 0 timeout: 73 it_real_value: 0 frequency: 0

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 -1208658224 (LWP 5782)]
[New Thread -1287636080 (LWP 5784)]
[New Thread -1210758256 (LWP 5783)]
(no debugging symbols found)
0x00319402 in __kernel_vsyscall ()

+ Trace 85306

Thread 1 (Thread -1208658224 (LWP 5782))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_type_check_instance_is_a
from /lib/libgobject-2.0.so.0
#5 g_cclosure_marshal_VOID__VOID
#6 g_cclosure_marshal_VOID__VOID
#7 g_cclosure_marshal_VOID__VOID
#8 g_cclosure_marshal_VOID__VOID
#9 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#10 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#11 g_main_context_check
from /lib/libglib-2.0.so.0
#12 g_main_loop_run
from /lib/libglib-2.0.so.0
#13 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_cclosure_marshal_VOID__VOID
#15 __libc_start_main
from /lib/libc.so.6
#16 g_cclosure_marshal_VOID__VOID
#0 __kernel_vsyscall

Comment 1 Bruno Boaventura 2006-11-18 05:34:50 UTC

*** Bug 374046 has been marked as a duplicate of this bug. ***

Comment 2 Bruno Boaventura 2006-11-18 05:52:43 UTC


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

Comment 3 Pedro de Medeiros 2006-12-29 18:06:55 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 4 Pedro de Medeiros 2007-01-28 19:37:37 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!