[opensuse-factory] New Tumbleweed snapshot 20180301 released!
Please note that this mail was generated by a script.
The described changes are computed based on the x86_64 DVD.
The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading:
https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&version=Tumbleweed&build=20180301
When you reply to report some issues, make sure to change the subject.
It is not helpful to keep the release announcement subject in a thread
while discussing a specific problem.
Packages changed:
Mesa
Mesa-drivers
NetworkManager
augeas
bind
bluedevil5 (5.12.1 -> 5.12.2)
breeze (5.12.1 -> 5.12.2)
breeze-gtk (5.12.1 -> 5.12.2)
breeze4-style (5.12.1 -> 5.12.2)
coreutils
cracklib
diffutils
discover (5.12.1 -> 5.12.2)
drkonqi5 (5.12.1 -> 5.12.2)
elfutils
fcitx
fftw3
findutils
gawk (4.2.0 -> 4.2.1)
gcr
git
glibc (2.26 -> 2.27)
glibc (2.26 -> 2.27)
glibmm2_4
gnome-autoar (0.2.2 -> 0.2.3)
gnome-session
gnutls
gpg2 (2.2.4 -> 2.2.5)
grep
guile
icewm
kactivitymanagerd (5.12.1 -> 5.12.2)
kcm_sddm (5.12.1 -> 5.12.2)
kde-cli-tools5 (5.12.1 -> 5.12.2)
kde-gtk-config5 (5.12.1 -> 5.12.2)
kde-user-manager (5.12.1 -> 5.12.2)
kdebase4-workspace
kdump
kgamma5 (5.12.1 -> 5.12.2)
khotkeys5 (5.12.1 -> 5.12.2)
kinfocenter5 (5.12.1 -> 5.12.2)
kmenuedit5 (5.12.1 -> 5.12.2)
kscreen5 (5.12.1 -> 5.12.2)
kscreenlocker (5.12.1 -> 5.12.2)
ksysguard5 (5.12.1 -> 5.12.2)
kwayland-integration (5.12.1 -> 5.12.2)
kwin5 (5.12.1 -> 5.12.2)
lftp
libassuan
libcap
libcdio
libffi
libgcrypt
libidn
libkdecoration2 (5.12.1 -> 5.12.2)
libksba
libkscreen2 (5.12.1 -> 5.12.2)
libksysguard5 (5.12.1 -> 5.12.2)
libmpeg2
libmygpo-qt (1.0.7 -> 1.0.9)
libnettle
libnl3 (3.3.0 -> 3.4)
libnsl
liborcus (0.13.3 -> 0.13.4)
libproxy
libproxy-plugins
libqt4
libqt5-qtbase
libqt5-qtwebkit
libsmbios2
libtasn1
libtirpc
libxshmfence (1.2 -> 1.3)
mariadb
milou5 (5.12.1 -> 5.12.2)
mjpegtools
multipath-tools (0.7.3+52+suse.08a969b7fce0 -> 0.7.3+53+suse.140f4937e9e7)
mutter
nghttp2
npth
openssl
openssl-1_0_0
os-prober
oxygen5 (5.12.1 -> 5.12.2)
perl-XML-SAX (0.99 -> 1.00)
perl-libwww-perl (6.32 -> 6.33)
phonon (4.9.0 -> 4.10.0)
phonon4qt5 (4.9.1 -> 4.10.0)
pinentry
plasma-nm5 (5.12.1 -> 5.12.2)
plasma5-addons (5.12.1 -> 5.12.2)
plasma5-desktop (5.12.1 -> 5.12.2)
plasma5-integration (5.12.1 -> 5.12.2)
plasma5-openSUSE
plasma5-pa (5.12.1 -> 5.12.2)
plasma5-workspace (5.12.1 -> 5.12.2)
powerdevil5 (5.12.1 -> 5.12.2)
procps
python-kiwi (9.13.0 -> 9.13.1)
python-setuptools
sddm
shadow
solid
spec-cleaner (1.0.3 -> 1.0.4)
sssd
suitesparse
systemd
systemsettings5 (5.12.1 -> 5.12.2)
utempter
xdm
xen (4.10.0_12 -> 4.10.0_13)
yast2-nis-server (3.1.4 -> 4.0.0)
zypp-plugin
=== Details ===
==== Mesa ====
Subpackages: Mesa-dri-devel Mesa-libEGL-devel Mesa-libEGL1 Mesa-libGL-devel Mesa-libGL1 Mesa-libglapi0 libgbm1 libwayland-egl1
- removed more unneeded buildrequires: libudev, openssl, bison,
flex (boo#1082312)
- removed u_configure.ac-Link-to-libLLVMCodegen-to-fix-cyclic-li.patch
which is no longer needed due to changed LLVM build (boo#1082307)
- merge content of new rpmlintrc into existing Mesa-rpmlintrc file
==== Mesa-drivers ====
Subpackages: Mesa-dri Mesa-gallium Mesa-libva libvdpau_r300 libvdpau_r600 libvdpau_radeonsi libvulkan_radeon libxatracker2
- removed more unneeded buildrequires: libudev, openssl, bison,
flex (boo#1082312)
- removed u_configure.ac-Link-to-libLLVMCodegen-to-fix-cyclic-li.patch
which is no longer needed due to changed LLVM build (boo#1082307)
- merge content of new rpmlintrc into existing Mesa-rpmlintrc file
==== NetworkManager ====
Subpackages: NetworkManager-devel NetworkManager-lang libnm-glib-vpn1 libnm-glib4 libnm-util2 libnm0 typelib-1_0-NM-1_0 typelib-1_0-NMClient-1_0 typelib-1_0-NetworkManager-1_0
- Add nm-preserve-agent-owned-secrets-on-connection-update.patch:
Backport upstream commit to preserve agent-owned secrets on
connection update (bgo#793324, bsc#1082762).
==== augeas ====
Subpackages: augeas-lenses libaugeas0
- Use %license (boo#1082318)
==== bind ====
Subpackages: bind-chrootenv bind-doc bind-utils libbind9-160 libdns169 libirs160 libisc166 libisccc160 libisccfg160 liblwres160 python3-bind
- build with --enable-filter-aaaa to make it possible to use
config option "filter-aaaa-on-v4 yes". Useful to workaround
broken websites like netflix which block traffic from certain
IPv6 tunnel providers.
==== bluedevil5 ====
Version update (5.12.1 -> 5.12.2)
Subpackages: bluedevil5-lang
- Update to 5.12.2
* New bugfix release
* For more details please see:
* https://www.kde.org/announcements/plasma-5.12.2.php
- Changes since 5.12.1:
* None
==== breeze ====
Version update (5.12.1 -> 5.12.2)
Subpackages: breeze5-cursors breeze5-decoration breeze5-style breeze5-style-lang breeze5-wallpapers
- Update to 5.12.2
* New bugfix release
* For more details please see:
* https://www.kde.org/announcements/plasma-5.12.2.php
- Changes since 5.12.1:
* None
==== breeze-gtk ====
Version update (5.12.1 -> 5.12.2)
Subpackages: gtk2-metatheme-breeze gtk3-metatheme-breeze metatheme-breeze-common
- Update to 5.12.2
* New bugfix release
* For more details please see:
* https://www.kde.org/announcements/plasma-5.12.2.php
- Changes since 5.12.1:
* None
==== breeze4-style ====
Version update (5.12.1 -> 5.12.2)
- Update to 5.12.2
* New bugfix release
* For more details please see:
* https://www.kde.org/announcements/plasma-5.12.2.php
- Changes since 5.12.1:
* None
==== coreutils ====
Subpackages: coreutils-lang
- Use %license (boo#1082318)
==== cracklib ====
Subpackages: libcrack2 libcrack2-32bit
- Use %license (boo#1082318)
==== diffutils ====
Subpackages: diffutils-lang
- Use %license (boo#1082318)
==== discover ====
Version update (5.12.1 -> 5.12.2)
Subpackages: discover-lang
- Update to 5.12.2
* New bugfix release
* For more details please see:
* https://www.kde.org/announcements/plasma-5.12.2.php
- Changes since 5.12.1:
* Fix checking if the package is already on the ResProxyModel
* Add multimedia sub-categories
* Put all systemwide add-ons in Plasma Addons category (kde#390594)
* Sort by sortable rating
* Make it possible to debug sorting
* Make sure sortableRating is initialised
* Don't let the user write the first review for apps they haven't installed
* Fix warning
* Only instantiate the ProgressView sheet when it's to be displayed
* Fix placement of the BusyIndicator over loading screenshots (kde#390391)
* Update copyright year (kde#390358)
==== drkonqi5 ====
Version update (5.12.1 -> 5.12.2)
Subpackages: drkonqi5-lang
- Update to 5.12.2
* New bugfix release
* For more details please see:
* https://www.kde.org/announcements/plasma-5.12.2.php
- Changes since 5.12.1:
* None
==== elfutils ====
Subpackages: elfutils-lang libasm1 libdw1 libebl-plugins libelf-devel libelf1
- Use %license (boo#1082318)
==== fcitx ====
Subpackages: fcitx-branding-openSUSE fcitx-gtk2 fcitx-gtk3 fcitx-pinyin fcitx-qt4 fcitx-table fcitx-table-cn-wubi fcitx-table-cn-wubi-pinyin libfcitx-4_2_9
- Add pkgconfig(xkbfile) BuildRequires: in the past, this used to
be pulled in by libqt4, but since our own code depends on it, and
not Qt4, it is our own duty to request our build dependencies.
- Package COPYING is %license, not as %doc.
==== fftw3 ====
Subpackages: fftw3-devel libfftw3-3 libfftw3_threads3
- Add support for openmpi2 for the HPC build (FATE#325089).
==== findutils ====
Subpackages: findutils-lang
- Use %license (boo#1082318)
==== gawk ====
Version update (4.2.0 -> 4.2.1)
- GNU awk 4.2.1:
* documentation updates
* In MPFR mode, When ROUNDMODE changes, string values for
numerically type values will be redone
* various bug fixes
* drop fold-string.patch, upstream
- Use %license (boo#1082318)
==== gcr ====
Subpackages: gcr-data gcr-prompter gcr-viewer libgck-1-0 libgcr-3-1 typelib-1_0-Gck-1 typelib-1_0-Gcr-3
- Use SPDX3.0 license tags and package COPYING as %license.
- Add explicit pkgconfig(pango) and pkgconfig(cairo) BuildRequires:
closer alignment with what configure checks for.
==== git ====
Subpackages: git-core git-cvs git-daemon git-email git-gui git-svn git-web gitk
- Move %{?systemd_requires} to daemon subpackage
==== glibc ====
Version update (2.26 -> 2.27)
Subpackages: glibc-32bit glibc-locale-32bit
- Use %license (boo#1082318)
- Add systemtap-headers to BuildRequires
- Add --enable-systemtap to configure arguments (fate#324969, bsc#1073636)
- riscv-readelflib.patch: Fix parsing flags in ELF64 files on riscv
- Update to glibc 2.27
* Optimized x86-64 asin, atan2, exp, expf, log, pow, atan, sin, cosf,
sinf, sincosf and tan with FMA
* Optimized x86-64 trunc and truncf for processors with SSE4.1
* Optimized generic expf, exp2f, logf, log2f, powf, sinf, cosf and
sincosf
* In order to support faster and safer process termination the malloc API
family of functions will no longer print a failure address and stack
backtrace after detecting heap corruption
* The abort function terminates the process immediately, without flushing
stdio streams
* On platforms where long double has the IEEE binary128 format (aarch64,
alpha, mips64, riscv, s390 and sparc), the math library now implements
_Float128 interfaces for that type, as defined by ISO/IEC TS 18661-3:2015
These are the same interfaces added in version 2.26 for some platforms where
this format is supported but is not the format of long double
* On platforms with support for _Float64x (aarch64, alpha, i386, ia64,
mips64, powerpc64le, riscv, s390, sparc and x86_64), the math library now
implements interfaces for that type, as defined by ISO/IEC TS
18661-3:2015
* The math library now implements interfaces for the _Float32, _Float64 and
_Float32x types, as defined by ISO/IEC TS 18661-3:2015
* glibc now implements the memfd_create and mlock2 functions on Linux
* Support for memory protection keys was added
* The copy_file_range function was added
* The ldconfig utility now processes `include' directives using the C/POSIX
collation ordering
* Support for two grammatical forms of month names has been added
* Support for the RISC-V ISA running on Linux has been added
* Statically compiled applications attempting to load locales compiled for the
GNU C Library version 2.27 will fail and fall back to the builtin C/POSIX
locale
* Support for statically linked applications which call dlopen is deprecated
and will be removed in a future version of glibc
* Support for old programs which use internal stdio data structures and
functions is deprecated
* On GNU/Linux, the obsolete Linux constant PTRACE_SEIZE_DEVEL is no longer
defined by
On Saturday, 3 March 2018 00:00:12 GMT Dominique Leuenberger wrote:
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&version=Tumbleweed&build=20180301
When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem.
After this snapshot installed, i logged out and was then unable to login, I had to reboot to be able log back in. These messages were logged for each failed login. Mar 03 09:45:48 DamnMachine kdm[25987]: :0[25987]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libcrypt.so.1: symbol __open_nocancel, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Mar 03 09:45:48 DamnMachine kdm[25987]: :0[25987]: PAM adding faulty module: /lib64/security/pam_unix.so regards Ian -- opensuse:tumbleweed:20180301 Qt: 5.10.0 KDE Frameworks: 5.43.0 - KDE Plasma: 5.12.2 - kwin 5.12.2 kmail2 5.7.2 - akonadiserver 5.7.2 - Kernel: 4.15.6-1-default - xf86-video-nouveau: 1.0.15 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2018-03-03 at 11:50 -0000, Ianseeks wrote:
After this snapshot installed, i logged out and was then unable to login, I had to reboot to be able log back in. These messages were logged for each failed login.
Mar 03 09:45:48 DamnMachine kdm[25987]: :0[25987]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libcrypt.so.1: symbol __open_nocancel, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Mar 03 09:45:48 DamnMachine kdm[25987]: :0[25987]: PAM adding faulty module: /lib64/security/pam_unix.so
You are supposed to reboot after installing an snapshot with "zypper dup". Or, you can verify what services and apps are affected by running "zypper ps", and then manually restarting all in the list. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlqajiUACgkQtTMYHG2NR9WmbACeK27REMliGGGMpcVYzAMjUQRW 15EAoIiR9frHhSm5Bly0fngyzBe0fBb4 =B+d7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 3 March 2018 11:59:33 GMT Carlos E. R. wrote:
On Saturday, 2018-03-03 at 11:50 -0000, Ianseeks wrote:
After this snapshot installed, i logged out and was then unable to login, I had to reboot to be able log back in. These messages were logged for each failed login.
Mar 03 09:45:48 DamnMachine kdm[25987]: :0[25987]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libcrypt.so.1: symbol __open_nocancel, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Mar 03 09:45:48 DamnMachine kdm[25987]: :0[25987]: PAM adding faulty module: /lib64/security/pam_unix.so
You are supposed to reboot after installing an snapshot with "zypper dup". Or, you can verify what services and apps are affected by running "zypper ps", and then manually restarting all in the list.
thanks. This time I just needed to log back in to check something so i could go off and do something else while it rebooted
-- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar)
-- opensuse:tumbleweed:20180301 Qt: 5.10.0 KDE Frameworks: 5.43.0 - KDE Plasma: 5.12.2 - kwin 5.12.2 kmail2 5.7.2 - akonadiserver 5.7.2 - Kernel: 4.15.6-1-default - xf86-video-nouveau: 1.0.15 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Ianseeks wrote:
On Saturday, 3 March 2018 11:59:33 GMT Carlos E. R. wrote:
You are supposed to reboot after installing an snapshot with "zypper dup". Or, you can verify what services and apps are affected by running "zypper ps", and then manually restarting all in the list.
thanks. This time I just needed to log back in to check something so i could go off and do something else while it rebooted
Sure. But in that case you *have* to be prepared to meet problems like yours, and they are neither issues nor bugs.... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi *, after installing this snapshot I have lots of new warning messages in my journal logs: klauncher[2037]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerCh anged(QString,QString,QString) kdeinit5[2040]: kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/<xyz>.so" with <xyz> being about 30 .so files. kdeinit5[2040]: org.kde.kcoreaddons: Expected JSON property "X-KDE-OnlyShowOnQtPlatforms" to be a string list. Treating it as a list with a single entry: "xcb;" ksmserver[2057]: Qt: Session management error: networkIdsList argument is NULL polkit-kde-authentication-agent-1[2088]: kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing. kdeinit5[2040]: kf5.kded: found kded module "dnssdwatcher" by prepending 'kded_' to the library path, please fix your metadata. org_kde_powerdevil[2110]: QDBusArgument: read from a write-only object plasmashell[2082]: kf5.karchive: bzDecompress returned -5 org_kde_powerdevil[2110]: powerdevil: Xrandr not supported, trying ddc, helper and so on. There is a total of about 50 warning messages, I never had before. I don't have any problems so far, but I am a bit fussy on warning and error messages. I'd like to keep my logs clean, so that real errors can't be overlooked. Perhaps some debug mode was activated? Thx and bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Am Samstag, 3. M?rz 2018, 20:03:00 CET schrieb Michael Hirmke:
Hi *,
after installing this snapshot I have lots of new warning messages in my journal logs:
This is caused by this change: ==== libqt5-qtbase ==== - Enable journald support (boo#1050461) so instead of arriving in ~/.local/share/sddm/xorg-session.log, they get written into the systemd journal now. This doesn't only affect plasma and applications started by it, but all applications using the Qt logging facilities started without a connected terminal. That there's quite a lot of additional journal messages now was a concern for the change, but it's rather minor compared to the benefit of having a more complete journal.
klauncher[2037]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerCh anged(QString,QString,QString)
kdeinit5[2040]: kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/<xyz>.so"
with <xyz> being about 30 .so files.
kdeinit5[2040]: org.kde.kcoreaddons: Expected JSON property "X-KDE-OnlyShowOnQtPlatforms" to be a string list. Treating it as a list with a single entry: "xcb;"
ksmserver[2057]: Qt: Session management error: networkIdsList argument is NULL
polkit-kde-authentication-agent-1[2088]: kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing.
kdeinit5[2040]: kf5.kded: found kded module "dnssdwatcher" by prepending 'kded_' to the library path, please fix your metadata.
org_kde_powerdevil[2110]: QDBusArgument: read from a write-only object
plasmashell[2082]: kf5.karchive: bzDecompress returned -5
org_kde_powerdevil[2110]: powerdevil: Xrandr not supported, trying ddc, helper
and so on. There is a total of about 50 warning messages, I never had before.
I don't have any problems so far, but I am a bit fussy on warning and error messages. I'd like to keep my logs clean, so that real errors can't be overlooked. Perhaps some debug mode was activated?
Thx and bye. Michael.
-- Fabian Vogt - Release Engineer SUSE Linux GmbH GF: Felix Imend?rffer, Jane Smithard, Graham Norton; HRB 21284 (AG N?rnberg) Maxfeldstr. 5, 90409 N?rnberg, Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Fabian Vogt wrote:
Hi,
Am Samstag, 3. M?rz 2018, 20:03:00 CET schrieb Michael Hirmke:
Hi *,
after installing this snapshot I have lots of new warning messages in my journal logs:
This is caused by this change:
==== libqt5-qtbase ====
- Enable journald support (boo#1050461)
so instead of arriving in ~/.local/share/sddm/xorg-session.log, they get written into the systemd journal now.
This doesn't only affect plasma and applications started by it, but all applications using the Qt logging facilities started without a connected terminal.
That there's quite a lot of additional journal messages now was a concern for the change, but it's rather minor compared to the benefit of having a more complete journal.
Especially as some of the programs are really doing an *excessive* logging by default. I had to put [Rules] *.debug=false in /usr/share/qt5/qtlogging.ini to trim it down to something reasonable :( -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, [...]
Especially as some of the programs are really doing an *excessive* logging by default.
indeed, my remote syslog-ng, which receives all that crap, can't keep up with all those messages from several clients.
I had to put
[Rules] *.debug=false
in /usr/share/qt5/qtlogging.ini to trim it down to something reasonable :(
Thx for that hint, but that didn't stop those messages on my machines. I tried to put it in /usr/share/qt5/qtlogging.ini and also in ~/.config/QtProject/qtlogging.ini to no avail. According to https://doc.qt.io/qt-5/qloggingcategory.html#configuring-categories this should be correct, though 8-( Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Michael Hirmke wrote:
I had to put
[Rules] *.debug=false
in /usr/share/qt5/qtlogging.ini to trim it down to something reasonable :(
Thx for that hint, but that didn't stop those messages on my machines. I tried to put it in /usr/share/qt5/qtlogging.ini and also in ~/.config/QtProject/qtlogging.ini to no avail.
Well, if it is really error messages, switching off debug likely isn't sufficient to suppress them. But if its real errors, they should of course be fixed... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Peter,
Michael Hirmke wrote:
I had to put
[Rules] *.debug=false
in /usr/share/qt5/qtlogging.ini to trim it down to something reasonable :(
Thx for that hint, but that didn't stop those messages on my machines. I tried to put it in /usr/share/qt5/qtlogging.ini and also in ~/.config/QtProject/qtlogging.ini to no avail.
Well, if it is really error messages, switching off debug likely isn't sufficient to suppress them. But if its real errors, they should of course be fixed...
no, those are all warning messages - but thousands of them. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2018-03-03 21:50, Michael Hirmke wrote:
Hi,
[...]
Especially as some of the programs are really doing an *excessive* logging by default.
indeed, my remote syslog-ng, which receives all that crap, can't keep up with all those messages from several clients.
drop them at syslog.ng? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Hi Carlos, [...]
indeed, my remote syslog-ng, which receives all that crap, can't keep u= p with all those messages from several clients.
drop them at syslog.ng?
I could do that, but the necessary rules will kill syslog-ng, too.
--=20 Cheers / Saludos,
Carlos E. R.
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Samstag, 3. März 2018 23:31:00 CET Michael Hirmke wrote:
Hi Carlos,
[...]
indeed, my remote syslog-ng, which receives all that crap, can't keep u=
p
with all those messages from several clients.
drop them at syslog.ng?
I could do that, but the necessary rules will kill syslog-ng, too.
Syslog-ng is killed by a single rule? wow ... https://syslog-ng.com/documents/html/syslog-ng-pe-latest-guides/en/syslog-ng... Just filter for _SYSTEMD_SLICE=system.slice, if you are only interested in system messages, not messages from the user sessions. Note, messages from the user sessions where already sent to the user journals, depending on the program. All Gnome programs sent their messages to the journal, everything dbus activated (e.g. kscreen) already sent their stdout/ stderr to the journal, ... Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019
Hi, [...]
Syslog-ng is killed by a single rule? wow ...
no, not by the rule as single cause, but: Since Leap 42.3 syslog-ng already uses up 100% cpu time and doesn't keep up with lots of messages. Sometimes it lags back for over an hour. I opened a bug report last August, but didn't get any answer yet: https://bugzilla.opensuse.org/show_bug.cgi?id=1055993
https://syslog-ng.com/documents/html/syslog-ng-pe-latest-guides/en/syslog-ng... pe-guide-admin/html/configuring-sources-journal.html
Just filter for _SYSTEMD_SLICE=system.slice, if you are only interested in system messages, not messages from the user sessions.
Note, messages from the user sessions where already sent to the user journals, depending on the program. All Gnome programs sent their messages to the journal, everything dbus activated (e.g. kscreen) already sent their stdout/ stderr to the journal, ...
Thx for the information. I used rules and filters up to 42.2, but had to remove them with 42.3 to get syslog-ng to work at all 8-(
Regards,
Stefan
Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2018-03-04 10:13, Michael Hirmke wrote:
Hi,
[...]
Syslog-ng is killed by a single rule? wow ...
no, not by the rule as single cause, but: Since Leap 42.3 syslog-ng already uses up 100% cpu time and doesn't keep up with lots of messages. Sometimes it lags back for over an hour. I opened a bug report last August, but didn't get any answer yet:
The report doesn't mention what kind of load this syslog-ng has. Is it local or remote? Many messages or few? If it is local, ie, messages from only self, from the same machine, I found out that only rsyslog does adequate taking of messages from the systemd journal. If the journal is configured to produce no files, the syslog daemons get no data at all because they are reading from the files. Except rsyslog, which continue working. I did the experiment many months ago. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Samstag, 3. März 2018 20:20:58 CET Fabian Vogt wrote:
Hi,
Am Samstag, 3. M?rz 2018, 20:03:00 CET schrieb Michael Hirmke:
Hi *,
after installing this snapshot I have lots of new warning messages in my
journal logs: This is caused by this change:
==== libqt5-qtbase ====
- Enable journald support (boo#1050461)
so instead of arriving in ~/.local/share/sddm/xorg-session.log, they get written into the systemd journal now.
This doesn't only affect plasma and applications started by it, but all applications using the Qt logging facilities started without a connected terminal.
That there's quite a lot of additional journal messages now was a concern for the change, but it's rather minor compared to the benefit of having a more complete journal.
Also note, although the output is currently *too* verbose in general, this should and can be fixed on the calling site: 1) by fixing errors in the first place 2) by demoting log levels of debug messages, i.e. only keeping *real warnings* 3) by lowering the default log level to warning This helps both users and developers. Developers can request more informational messages from users, users get more helpful messages by default in the first place. There is already work happening to address all three issues, but this will take some time. Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019
Hi Stefan, [...]
That there's quite a lot of additional journal messages now was a concern for the change, but it's rather minor compared to the benefit of having a more complete journal.
Also note, although the output is currently *too* verbose in general, this should and can be fixed on the calling site:
1) by fixing errors in the first place
would be great, but there is nothing I can do. All of those warnings are addressed to the developers.
2) by demoting log levels of debug messages, i.e. only keeping *real warnings*
Yes, that would be great, because most of the warnings seem to have just informational character.
3) by lowering the default log level to warning
That didn't work. I tried to set "*.debug=false" as described in one of my messages in this thread, but obvisously I did something wrong.
This helps both users and developers. Developers can request more informational messages from users, users get more helpful messages by default in the first place.
I know 8-/ But: What would have been the problem introducing a switch to decide where warnings and error messages have to be logged. The default could have been journal log, but one would have the chance to change it back to the old behaviour.
There is already work happening to address all three issues, but this will take some time.
Ok, I'll be patient :)
Kind regards,
Stefan
Thx and bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Just doing the update (actually to 0302, but related to this): The update does remove the openssl-1_1_* stuff, installs openssl, but also (again) openssl-1_0, which is currently not installed. Is this intended? Dominique Leuenberger wrote:
openssl openssl-1_0_0
==== openssl ==== Subpackages: libopenssl-devel
- change the sonum to 1.1, as all the minor versions keep ABI compatibility (bsc#1081335) - update baselibs.conf
==== openssl-1_0_0 ====
- Remove bit obsolete syntax - Use %license macro
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2018-03-05 at 17:12 +0100, Peter Suetterlin wrote:
Just doing the update (actually to 0302, but related to this):
The update does remove the openssl-1_1_* stuff, installs openssl, but also (again) openssl-1_0, which is currently not installed.
Is this intended?
openssl-1_0_0 was never gone. There is still too much dependng on it for now. But it's not the default SSL implementation on Tumbleweed. That 'larger' change that happened was a rename of openssl-1_1_0 to openssl-1_1 Cheers Domninique
Dominique Leuenberger / DimStar wrote:
On Mon, 2018-03-05 at 17:12 +0100, Peter Suetterlin wrote:
Just doing the update (actually to 0302, but related to this):
The update does remove the openssl-1_1_* stuff, installs openssl, but also (again) openssl-1_0, which is currently not installed.
Is this intended?
openssl-1_0_0 was never gone. There is still too much dependng on it for now. But it's not the default SSL implementation on Tumbleweed.
I knew. I *thought* it was not installed on the machine and wondered why it was 'pulled in' now. Turns out I had overlooked it. It *had* been installed, and was not pulled in, but updated. Sorry for the noise :o -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Carlos E. R.
-
Dominique Leuenberger
-
Dominique Leuenberger / DimStar
-
Fabian Vogt
-
Ianseeks
-
mh@mike.franken.de
-
Peter Suetterlin
-
Stefan Brüns