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 577515 - Debug warning about disabling debug logging.
Debug warning about disabling debug logging.
Status: RESOLVED FIXED
Product: gnome-media
Classification: Deprecated
Component: gnome-volume-control
2.26.x
Other Linux
: Normal trivial
: ---
Assigned To: gnome media maintainers
gnome media maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-31 18:37 UTC by Tomislav Vujec
Modified: 2009-05-02 22:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
Proposed patch to remove the useless message. (363 bytes, patch)
2009-03-31 18:37 UTC, Tomislav Vujec
none Details | Review

Description Tomislav Vujec 2009-03-31 18:37:09 UTC
It seems that both gnome-volume-control and gnome-volume-control-applet give debug message "Disabling debugging" when started without debug. The message itself might have some sense if someone was to call gvc_log_set_debug in the middle of the running session. I can't imagine a use case where this would be useful. However, as it stands, every start of either executable gives this ugly message on stdout. It should be removed.
Comment 1 Tomislav Vujec 2009-03-31 18:37:57 UTC
Created attachment 131801 [details] [review]
Proposed patch to remove the useless message.
Comment 2 Marc-Andre Lureau 2009-05-02 22:25:12 UTC
commit c03480a8bdfbaac1b5d49ff66cc65e8deb47fe18
Author: Bastien Nocera <hadess@hadess.net>
Date:   Thu Apr 23 15:13:22 2009 +0100

    Don't show debug output when disabling debugging

    Apparently it's annoying:
    https://bugzilla.redhat.com/show_bug.cgi?id=493138

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 3 Bastien Nocera 2009-05-02 22:45:49 UTC
Oopsie. I forgot that I already fixed it...