[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#894251: marked as done (mate-terminal spams systemd journal with dbus max_match_rules_per_connection)

Your message dated Wed, 4 Apr 2018 09:51:48 -0500
with message-id <CAOLfK3W9h+nNZTB74PoTKizpTddaxHLCxQjx4E-FcWnH1e7AKA@mail.gmail.com>
and subject line Re: Bug#894251: mate-terminal spams systemd journal with dbus max_match_rules_per_connection
has caused the Debian Bug report #894251,
regarding mate-terminal spams systemd journal with dbus max_match_rules_per_connection
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 owner@bugs.debian.org
immediately.)


-- 
894251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894251
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: mate-terminal
Version: 1.20.0-1
Severity: normal

Greetings,

Thank you for contributing to Debian.

When watching the systemd journal via "journalctl -f", there is a line printed
to the journal for every key press in a mate-terminal. For instance:

Mar 27 14:09:52 achilles dbus-daemon[1114]: [session uid=1000 pid=1114] Connection ":1.3831" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=50000)
Mar 27 14:09:53 achilles dbus-daemon[1114]: [session uid=1000 pid=1114] Connection ":1.3831" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=50000)
Mar 27 14:09:53 achilles dbus-daemon[1114]: [session uid=1000 pid=1114] Connection ":1.3831" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=50000)
Mar 27 14:09:54 achilles dbus-daemon[1114]: [session uid=1000 pid=1114] Connection ":1.3831" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=50000)
Mar 27 14:09:54 achilles dbus-daemon[1114]: [session uid=1000 pid=1114] Connection ":1.3831" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=50000)
Mar 27 14:09:54 achilles dbus-daemon[1114]: [session uid=1000 pid=1114] Connection ":1.3831" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=50000)
Mar 27 14:09:54 achilles dbus-daemon[1114]: [session uid=1000 pid=1114] Connection ":1.3831" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=50000)
Mar 27 14:09:54 achilles dbus-daemon[1114]: [session uid=1000 pid=1114] Connection ":1.3831" is not allowed to add more match rules (increase limits in configuration file if required; max_match_rules_per_connection=50000)

It doesn't matter which terminal has focus - pressing a key in any of the
mate-terminals yields a "Connect ... is not allowed to add more match rules".

I don't have issues on another system running the same version of
mate-terminal (1.20.0-1), so I don't know how reproducable this problem is.
Others seem to be having it, too:

https://github.com/mate-desktop/mate-terminal/issues/233
https://bugzilla.redhat.com/show_bug.cgi?id=1427721#c14

Using an xterm does not produce the log entries in the journal - it seems to
be isolated to mate-terminal.

Let me know what I can do to help solve this issue.

Thanks!

-m

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

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

Versions of packages mate-terminal depends on:
ii  gsettings-desktop-schemas  3.28.0-1
ii  libatk1.0-0                2.28.1-1
ii  libc6                      2.27-2
ii  libcairo-gobject2          1.15.10-2
ii  libcairo2                  1.15.10-2
ii  libdconf1                  0.26.1-3
ii  libgdk-pixbuf2.0-0         2.36.11-2
ii  libglib2.0-0               2.56.0-4
ii  libgnutls30                3.5.18-1
ii  libgtk-3-0                 3.22.29-2
ii  libice6                    2:1.0.9-2
ii  libpango-1.0-0             1.42.0-1
ii  libpangocairo-1.0-0        1.42.0-1
ii  libpcre2-8-0               10.31-3
ii  libsm6                     2:1.2.2-1+b3
ii  libvte-2.91-0              0.52.0-1
ii  libx11-6                   2:1.6.5-1
ii  mate-desktop-common        1.20.0-1
ii  mate-terminal-common       1.20.0-1
ii  zlib1g                     1:1.2.8.dfsg-5

mate-terminal recommends no packages.

mate-terminal suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Alex,

On Tue, Apr 3, 2018 at 7:55 AM, Alex ARNAUD <alexarnaud@hypra.fr> wrote:
Le 27/03/2018 à 23:22, Matt Zagrabelny a écrit :


On Tue, Mar 27, 2018 at 3:52 PM, Alex ARNAUD <alexarnaud@hypra.fr <mailto:alexarnaud@hypra.fr>> wrote:


    3) Add the generated file to your reply


Done.

 Thank you, unfortunately, I'm not able to reproduce this issue on my Sid VM. Are you using Mate desktop environment ? Does this issue appear with mate-terminal 1.20 ? What is different between your two machines, the one with the issue and the one without?



I just upgraded my workstation (the system that this bug report relates to) and the problem went away. Go figure.

Thanks for taking time to look into it and attempting to reproduce it.

-m

--- End Message ---
Reply to: