[Touch-packages] [Bug 1547589] Re: rtkit-daemon flooding syslog

2022-05-28 Thread Olivier Duclos
An easy way to solve this problem is to use the LogLevelMax systemd
property:

1. As root, run `systemctl edit rtkit-daemon` to create a new droppin for this 
service.
2. Add this to the new file:

[Service]
LogLevelMax=warning

3. Restart the service: `systemctl restart rtkit-daemon`

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1547589

Title:
  rtkit-daemon flooding syslog

Status in Rtkit:
  New
Status in rtkit package in Ubuntu:
  Confirmed
Status in rtkit package in Debian:
  Confirmed

Bug description:
  rtkit is flooding syslog with the following:

  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.

  This may be related to but #1547585

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rtkit 0.11-4
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:42:58 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: rtkit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/rtkit/+bug/1547589/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1309535] Re: Running without pam-kwallet installed issues a warning in auth.log

2021-05-24 Thread Olivier Duclos
The correct way to fix this issue is not to comment out the lines
mentioning kwallet, but to make the modules silent by prepending a '-'
(dash) to each line. Example:

# /etc/pam.d/lightdm
-authoptionalpam_kwallet.so
-authoptionalpam_kwallet5.so
-session optionalpam_kwallet.so auto_start
-session optionalpam_kwallet5.so auto_start

Same in /etc/pam.d/lightdm-greeter.

This feature is mentioned in the pam.conf(5) manpage:

   If the type value from the list above is prepended with a - character
   the PAM library will not log to the system log if it is not possible to
   load the module because it is missing in the system. This can be useful
   especially for modules which are not always installed on the system and
   are not required for correct authentication and authorization of the
   login session.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1309535

Title:
  Running without pam-kwallet installed issues a warning in auth.log

Status in lightdm package in Ubuntu:
  Won't Fix
Status in pam package in Ubuntu:
  Won't Fix

Bug description:
  After upgrading to lightdm 1.10.0-0ubuntu2 I started to see this error
  in auth.log:

  Apr 10 14:34:54 simon-laptop lightdm: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
  Apr 10 14:34:54 simon-laptop lightdm: PAM adding faulty module: pam_kwallet.so

  This seems like a regression because with lightdm 1.10.0-0ubuntu1 or
  before I didn't have this error showing. FYI, I don't have the pam-
  kwallet package installed.

  
  $ lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  $ apt-cache policy lightdm pam-kwallet
  lightdm:
Installed: 1.10.0-0ubuntu3
Candidate: 1.10.0-0ubuntu3
Version table:
   *** 1.10.0-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 18 09:12:37 2014
  InstallationDate: Installed on 2014-01-26 (81 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309535/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1832787] Re: fontconfig 2.12 in 18.04 causes firefox to freeze when launching chrome

2019-11-25 Thread Olivier Duclos
Any chance fontconfig 2.13 could be backported to bionic? This is a
seriously annoying issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1832787

Title:
  fontconfig 2.12 in 18.04 causes firefox to freeze when launching
  chrome

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  fontconfig version: 2.12.6-0ubuntu2

  Related:

  https://askubuntu.com/questions/1076412/firefox-freezing-with-100-cpu-
  usage-for-30-seconds-when-launching-chromium

  https://bugzilla.mozilla.org/show_bug.cgi?id=1495900

  https://bugzilla.mozilla.org/show_bug.cgi?id=1411338

  
  Steps to reproduce:

  1) Launch firefox, open a few tabs

  2) Launch chrome

  3) Go back to firefox, and notice it starts being very slow, switching
  tabs do nothing (the content area remains blank).

  4) Backport fontconfig 2.13 from cosmic to bionic

  5) Try to reproduce 1-3, be happy because it is now working fine!

  
  I backported 2.13.0-5ubuntu3 from cosmic to bionic, if that helps. I don't 
have the right setup right now to do a bisect from upstream or from debian 
patches sadly.

  ~ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1832787/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp