Your message dated Mon, 13 Apr 2020 21:51:04 +0100
with message-id <20200413205104.ga192...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#917767: gnome-terminal outputs debug messages when 
started from the command line
has caused the Debian Bug report #917767,
regarding gnome-terminal outputs debug messages when started from the command 
line
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
917767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-terminal
Version: 3.30.2-2
Severity: minor
Tags: upstream
Forwarded: https://gitlab.gnome.org/GNOME/gnome-terminal/issues/42

When one starts gnome-terminal from the command line, it outputs
useless debug messages such as:

# 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)

Not sure what has changed, but 2 weeks ago, I did not get such
messages.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-terminal depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.12-1
ii  dbus-x11 [dbus-session-bus]                   1.12.12-1
ii  dconf-gsettings-backend [gsettings-backend]   0.30.1-2
ii  gnome-terminal-data                           3.30.2-2
ii  gsettings-desktop-schemas                     3.28.1-1
ii  libatk1.0-0                                   2.30.0-2
ii  libc6                                         2.28-4
ii  libdconf1                                     0.30.1-2
ii  libglib2.0-0                                  2.58.1-2
ii  libgtk-3-0                                    3.24.2-3
ii  libpango-1.0-0                                1.42.1-1
ii  libuuid1                                      2.33-0.2
ii  libvte-2.91-0                                 0.54.2-2
ii  libx11-6                                      2:1.6.7-1

Versions of packages gnome-terminal recommends:
ii  gvfs                               1.38.1-2
ii  nautilus-extension-gnome-terminal  3.30.2-2
ii  yelp                               3.30.0-2

gnome-terminal suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 3.36.1.1-2

On Sun, 30 Dec 2018 at 00:29:22 +0100, Vincent Lefevre wrote:
> When one starts gnome-terminal from the command line, it outputs
> useless debug messages such as:
> 
> # 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)
> 
> Not sure what has changed, but 2 weeks ago, I did not get such
> messages.

The issue here is that newer GNOME Terminal versions override the global
GLib log handler, replacing it with one that doesn't filter out g_debug()
like the default does. The change that made you see this is either: that
change in GNOME Terminal, or dconf starting to emit g_debug() messages
(whichever of those changes happened second).

I forgot to mention the bug number in the changelog, but I followed up on
this upstream, got the fix included, and added the patch in 3.36.1.1-2,
so it should be fixed in unstable now.

    smcv

--- End Message ---

Reply via email to