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 341128 - eog crashes when pressing F11 some times (switching to fullscreen mode)
eog crashes when pressing F11 some times (switching to fullscreen mode)
Status: RESOLVED DUPLICATE of bug 320206
Product: eog
Classification: Core
Component: image viewer
unspecified
Other other
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-09 11:20 UTC by thomaskonrad
Modified: 2006-05-19 17:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description thomaskonrad 2006-05-09 11:20:07 UTC 
Distribution: Ubuntu 6.06 (dapper)
Package: EOG
Severity: Normal
Version: GNOME2.14.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: eog crashes when pressing F11 some times (switching to fullscreen mode)
Bugzilla-Product: EOG
Bugzilla-Component: image viewer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
eog crashes when pressing F11 some times (switching to fullscreen mode)

Steps to reproduce the crash:
1. open an image
2. press F11 some times
3. keep pressing F11

Expected Results:
that eog switches to fullscreen mode

How often does this happen?
always

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".




------- Bug created by bug-buddy at 2006-05-09 11:20 -------
Comment 1 Fabio Bonelli 2006-05-09 11:35:45 UTC 
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 thomaskonrad 2006-05-14 13:54:01 UTC 
Using gdb, i got this output:

...
(no debugging symbols found)
[New Thread -1240667216 (LWP 20870)]
[New Thread -1241039952 (LWP 20871)]
[Thread -1241039952 (LWP 20871) exited]
[New Thread -1241039952 (LWP 20876)]
[Thread -1241039952 (LWP 20876) exited]
[New Thread -1241039952 (LWP 20877)]
[Thread -1241039952 (LWP 20877) exited]
[New Thread -1241039952 (LWP 20878)]
[Thread -1241039952 (LWP 20878) exited]
(no debugging symbols found)
[New Thread -1241039952 (LWP 20880)]
No profile, not correcting
No profile, not correcting
No profile, not correcting
No profile, not correcting
No profile, not correcting
No profile, not correcting
No profile, not correcting
[New Thread -1252033616 (LWP 20881)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224665408 (LWP 20863)]
0x0806b3d6 in eog_image_cache_add ()

I hope this helps. Unfortunately, i'm not really fimilar with gdb.

Kind regards,

tom
Comment 3 Fabio Bonelli 2006-05-14 14:53:19 UTC 
Maybe this is a duplicate of bug 320206.

If you can help us with a stacktrace with debugging symbols (http://live.gnome.org/GettingTraces should say all) it would be nice.

Thanks!
Comment 4 Lucas Rocha 2006-05-19 17:36:10 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 320206 ***