RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2154269 - Programs linked to libdconf emit annoying watch_* debug messages
Summary: Programs linked to libdconf emit annoying watch_* debug messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-terminal
Version: 8.6
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: David King
QA Contact: Michal Odehnal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-16 12:54 UTC by Carlos Santos
Modified: 2023-11-14 16:45 UTC (History)
3 users (show)

Fixed In Version: gnome-terminal-3.28.3-4.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-14 15:31:53 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/centos-stream/rpms gnome-terminal merge_requests 4 0 None opened Quiet dconf logging (#2154269) 2023-05-04 11:40:21 UTC
Red Hat Issue Tracker RHELPLAN-142708 0 None None None 2022-12-16 13:05:07 UTC
Red Hat Product Errata RHBA-2023:6949 0 None None None 2023-11-14 15:31:55 UTC

Description Carlos Santos 2022-12-16 12:54:23 UTC 
Description of problem:

Programs linked to libdconf emit annoying watch_* debug messages

Version-Release number of selected component (if applicable):

dconf-0.28.0-4.el8.x86_64

How reproducible:

Always

Steps to Reproduce:

1. Run "gnome-terminal" from the gnome-terminal prompt, itself.

Actual results:

  - On X11 session, these debug messages are shown:

    # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
    # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
    # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)

  - On Wayland sessions, these debug messages are shown:

    # watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0)
    # watch_fast: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 0, active: 0)
    # watch_fast: "/org/gnome/desktop/sound/" (establishing: 0, active: 0)
    # watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0)
    # watch_fast: "/org/gnome/desktop/wm/preferences/" (establishing: 0, active: 0)
    # watch_fast: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 0, active: 0)
    # watch_fast: "/org/gnome/desktop/a11y/" (establishing: 0, active: 0)
    # watch_established: "/org/gnome/desktop/interface/" (establishing: 1)
    # watch_established: "/org/gnome/settings-daemon/peripherals/mouse/" (establishing: 1)
    # watch_established: "/org/gnome/desktop/sound/" (establishing: 1)
    # watch_established: "/org/gnome/desktop/privacy/" (establishing: 1)
    # watch_established: "/org/gnome/desktop/wm/preferences/" (establishing: 1)
    # watch_established: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 1)
    # watch_established: "/org/gnome/desktop/a11y/" (establishing: 1)
    # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0)
    # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1)
    # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0)

Expected results:

No debug messages should be shown unless the G_MESSAGES_DEBUG environment
variable is set.

Additional info:

commit 5865a1324c10d82b6d5d8528bff924774146591f (origin/rhel-8.0.0)
Author: Marek Kasik <mkasik>
Date:   Fri Jan 18 18:22:37 2019 +0100

    Backport fix for emission of spurious changed signals
    
    for all keys at once crashing gnome-shell
    
    Resolves: #1666176

added 0003-Engine-add-g_debug-statements-in-state-changing-inte.patch, which
inserts several g_debug calls. Apparently they were added for debug purposes
during the implementation of the fix and was left there by mistake.
Comment 1 Marek Kašík 2022-12-21 11:09:42 UTC 
Hi, this is an issue specific to gnome-terminal. It can be fixed by backporting this commit:

https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/f84316ec180e9b9515a0914e883a0585f6877c7e
Comment 2 David King 2023-05-04 11:40:22 UTC 
Upstream patch was straightforward to backport, so the MR is ready to go.
Comment 6 errata-xmlrpc 2023-11-14 15:31:53 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (gnome-terminal bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6949
Note You need to log in before you can comment on or make changes to this bug.