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 325711 - Debug/Profiling framework for EOG
Debug/Profiling framework for EOG
Status: RESOLVED FIXED
Product: eog
Classification: Core
Component: general
2.13.x
Other All
: Normal minor
: ---
Assigned To: Lucas Rocha
EOG Maintainers
eog-ng
: 329891 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-01-04 01:26 UTC by Wouter Bolsterlee (uws)
Modified: 2007-03-18 00:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Wouter Bolsterlee (uws) 2006-01-04 01:26:20 UTC
Please describe the problem:
EOG prints a lot of debug info on the terminal. Sample output below:

Instantiate job with id 5.
eog-image_load.c
load success: 1
No profile, not correcting
Show exif data
Job 005: disposing ...
Job 005: disposing end
Instantiate job with id 6.
eog-image_load.c
load success: 1
No profile, not correcting
Show exif data
Job 006: disposing ...
Job 006: disposing end
Instantiate job with id 7.
eog-image_load.c
load success: 1
No profile, not correcting
Show exif data
Job 007: disposing ...
Job 007: disposing end


Steps to reproduce:
1. Start EOG from a terminal
2. Open a file


Actual results:
My terminal is flooded with debug messages

Expected results:
I want a clean, crisp, and empty terminal window!

Does this happen every time?
Yup.

Other information:
Of course the info is harmless and not visible to most users that don't start
EOG from a terminal. Personally, I use eog as a quick image viewer when I'm
working in  a terminal. After I'm done looking at the images, all my terminal
context was lost and replaced with lots of debug info.
Comment 1 Lucas Rocha 2006-02-06 14:04:20 UTC
Confirming. Implementation of a debug/profiling architecture for EOG is needed.
Comment 2 Lucas Rocha 2006-02-06 14:05:22 UTC
*** Bug 329891 has been marked as a duplicate of this bug. ***
Comment 3 Sebastien Bacher 2006-02-06 15:23:57 UTC
Could the debug informations be redirected to a log for now?
Comment 4 Nickolay V. Shmyrev 2006-02-14 20:40:56 UTC
Hey all, we'd like to work on this problem a bit. Unfortunately it's unclear what do you suggest to implement. 

Of course, some debug/profiling framework can be created. For example, it's possible to copy/paste the following code:

http://cvs.gnome.org/viewcvs/evince/lib/ev-debug.c?rev=1.3&view=markup

But I am not sure it's needed, I think glib provide quite enough for extensive logging. I can suggest creation of custom log_handler that will look at environment variable and modifications of all g_print to g_debug. I think that would be enough.
Comment 5 Lucas Rocha 2006-02-19 03:25:35 UTC
All debug messages are disabled by default in EOG now. I'm leaving this bug open to continue the discussion about the debug/profiling framework for EOG. Changing the title then.
Comment 6 Sebastien Bacher 2006-05-18 10:36:36 UTC
it's still flooding my command line with "No profile, not correcting" messages on GNOME 2.14.1
Comment 7 Lucas Rocha 2006-05-19 00:36:07 UTC
Fixed, thanks Sebastien!
Comment 8 Lucas Rocha 2007-01-27 00:48:27 UTC
FYI, this has been implemented in eog-ng branch already.
Comment 9 Lucas Rocha 2007-03-18 00:05:18 UTC
eog-ng branch, which has a full rewrite of eog's core, has been merged into trunk as part of 2.19/2.20 development cycle. Therefore this bug is fixed now. Thanks for the report!