Re: [Evergreen] Can you help me with a bugzilla that was closed as invalid because it is about 13.1?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, 2016-05-02 at 16:24 +0200, Patrick Schaaf wrote: On Monday 02 May 2016 16:12:03 Carlos E. R. wrote: Hi, I reported it last november, against LibreOffice ir repo 4.3. It has been closed now becasue they say that they don't keep that repo. So I reopen it against repo 5.0, and again they close it as invalid because 13.1 is out of maintenance. Absurd! The bug is not present in any other distro, it is just a missing pacakge from the repo and should be easy to solve. Jup, experienced that too - we solved it locally by enabling both the 4.3 libreoffice repo, where these packages are still present, and the 5.0 repo. Well, now they have removed all the libreoffice repos for 13.1. :-( - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlc++UAACgkQtTMYHG2NR9WcRQCfXX1XoB537RnH/TkyEErWEXay LVMAn3qrPVVHp2xs8hVagtm3rlTk9S9N =J01C -END PGP SIGNATURE- ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] lots of systemd log messages when starting up and stopping user sessions
On 2016-05-20 08:17, Per Jessen wrote: > Carlos E. R. wrote: > >> On Wednesday, 2016-05-18 at 14:18 +0200, Per Jessen wrote: >>> Per Jessen wrote: >>> I though I would be able to reduce this by adding "Loglevel=notify" to /etc/systemd/user.conf, but: systemd[2034]: [/etc/systemd/user.conf:11] Invalid log level'notify': Operation not permitted >>> >>> Loglevel=notice does the trick. >> >> It doesn't do much here. I was getting this block, many times: >> > > It filtered out quite a few of them. All of these > are gone: > > 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Paths. > 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Paths. > 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Timers. > 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Timers. > 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Sockets. > 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Sockets. > 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Basic System. > 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Basic > System. > 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Default. > 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Default. > 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Startup finished in 36ms. > > Instead of some 40 messages, I see 8 or 9, an 80% reduction :-) > > 2016-05-19T22:17:01+02:00 sogo systemd[1]: Starting user-1000.slice. > 2016-05-19T22:17:01+02:00 sogo systemd[1]: Created slice user-1000.slice. > 2016-05-19T22:17:01+02:00 sogo systemd[1]: Starting User Manager for UID > 1000... > 2016-05-19T22:17:01+02:00 sogo systemd[1]: Started User Manager for UID 1000. > 2016-05-20T02:08:15+02:00 sogo systemd[1]: Stopping User Manager for UID > 1000... > 2016-05-20T02:08:15+02:00 sogo systemd[1]: Stopped User Manager for UID 1000. > 2016-05-20T02:08:15+02:00 sogo systemd[1]: Stopping user-1000.slice. > 2016-05-20T02:08:15+02:00 sogo systemd[1]: Removed slice user-1000.slice. I have this in rsyslog if (($programname == 'systemd') and ( \ (($msg contains 'Started Session') and ($msg contains 'of user')) \ or ($msg contains 'Starting Session') and (($msg contains 'of user news.') or ($msg contains 'of user wwwrun.') or ($msg contains 'of user cer.') or ($msg contains 'of user root.')) \ )) \ then-/var/log/pruned & stop and if ( $programname == 'systemd' and (\ ( \ ( $msg contains 'Starting' or $msg contains 'Started' or $msg contains 'Stopping' or $msg contains 'Stopped' ) \ and ($msg contains 'User Manager for UID' and ($msg contains '30' or $msg contains '0') ) \ ) \ or ( \ ( $msg contains 'Stopping' or $msg contains 'Removed slice' or $msg contains 'Starting' or $msg contains 'Created slice' ) \ and ($msg contains 'user-30.slice' or $msg contains 'user-0.slice') \ ) \ )) \ then-/var/log/pruned & stop and if ($programname startswith 'org.gtk.' and $msg contains '### debug:') or ($programname startswith 'org.gtk.vfs.Daemon') or ($programname startswith 'org.freedesktop.Tracker or ($programname startswith 'org.gnome.evince.Daemon' and ($msg contains 'egisterDocument' or $msg contains 'Watch name')) \ or ($programname startswith 'org.gnome.zeitgeist.Engine') \ or ($programname startswith 'org.xfce.FileManager' and ($msg contains 'fixme:' )) \ or ($programname == 'systemd' and ($msg contains 'Failed to open private bus connection: Failed to connect to socket' ))\ or ($programname startswith 'org.freedesktop.thumbnails.Thumbnailer') \ or ($programname startswith 'org.gnome.zeitgeist.SimpleIndexer')\ or ($programname startswith 'org.a11y.Bus') \ or ($programname startswith 'org.a11y.atspi.Registry') \ or ($programname startswith 'org.freedesktop.Telepathy.AccountManager' and ($msg contains 'WARNING' )) \ or ($programname startswith 'org.freedesktop.Notifications')\ or ($programname == 'org.gnome.evolution.dataserver.Calendar4') \ or ($programname startswith 'org.gnome.evolution.dataserver.Sources') \ or ($programname startswith 'org.freedesktop.Telepathy.AccountManager') \ or ($programname == 'org.gnome.OnlineAccounts' and ($msg contains '[DEBUG]') )\ or ($programname == 'systemd' and ($msg contains 'Failed to open private bus connection: Failed to connect to socket' ))\ or ($programname == 'xinetd' and (($msg contains 'START: nntp') or ($msg contains 'EXIT: nntp'))) \ or ($programname == 'systemd' and ( \ ($msg contains 'Starting Paths.')or ($msg contains
Re: [Evergreen] lots of systemd log messages when starting up and stopping user sessions
Carlos E. R. wrote: > On Wednesday, 2016-05-18 at 14:18 +0200, Per Jessen wrote: >> Per Jessen wrote: >> >>> I though I would be able to reduce this by adding "Loglevel=notify" >>> to /etc/systemd/user.conf, but: >>> >>> systemd[2034]: [/etc/systemd/user.conf:11] Invalid log >>> level'notify': Operation not permitted >> >> Loglevel=notice does the trick. > > It doesn't do much here. I was getting this block, many times: > It filtered out quite a few of them. All of these are gone: 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Paths. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Paths. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Timers. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Timers. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Sockets. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Sockets. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Basic System. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Basic System. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Starting Default. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Reached target Default. 2016-05-01T00:15:02+02:00 office20 systemd[16144]: Startup finished in 36ms. Instead of some 40 messages, I see 8 or 9, an 80% reduction :-) 2016-05-19T22:17:01+02:00 sogo systemd[1]: Starting user-1000.slice. 2016-05-19T22:17:01+02:00 sogo systemd[1]: Created slice user-1000.slice. 2016-05-19T22:17:01+02:00 sogo systemd[1]: Starting User Manager for UID 1000... 2016-05-19T22:17:01+02:00 sogo systemd[1]: Started User Manager for UID 1000. 2016-05-20T02:08:15+02:00 sogo systemd[1]: Stopping User Manager for UID 1000... 2016-05-20T02:08:15+02:00 sogo systemd[1]: Stopped User Manager for UID 1000. 2016-05-20T02:08:15+02:00 sogo systemd[1]: Stopping user-1000.slice. 2016-05-20T02:08:15+02:00 sogo systemd[1]: Removed slice user-1000.slice. Anyway, Andrei Borzenkov suggested just masking user@.service, he doesn't think it's actually being used. -- Per Jessen, Zürich (8.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
