I'm not sure, if this is bug or feature... After few days, update applet (TW,
KDE) says there are 6843 new updates (TeX, R, ... ;-). When I click to
"Install updates" error "Too many packages to process (6843/5200)" appears.
Zypper handles it well. Is it worth of bug report? To b.o.o?
Yours,
V.
--
Vojtěch Zeisek
Komunita openSUSE GNU/Linuxu
Community of the openSUSE GNU/Linux
https://www.opensuse.org/https://trapa.cz/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
I just attempted to test Leap 15.0 in my laptop, and I don't see the XFCE
pattern. I had to abort.
Has XFCE been removed? Is there some trick?
I used openSUSE-Leap-15.0-DVD-x86_64-Build128.1-Media.iso
No internet.
- --
Cheers
Carlos E. R.
(from 42.2 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iF4EAREIAAYFAlqF2h0ACgkQja8UbcUWM1z8IwEAjoaPmiCdcp9/KThlfGp6IRYe
KYPvhgzaCbpYzLhlHNAA/0T714drgIvRZm4wERVwd0J0Rjb3SAew2e93AFII1Yob
=EJke
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello,
the SUSE security team recently decided to turn the rpmlint check
"polkit-untracked-privilege" into an error. Currently this is only an
informational message. If you get messages like these in your package:
gvfs-backends.x86_64: I: polkit-untracked-privilege org.gtk.vfs.file-operations (no:no:auth_admin_keep)
then they will become an error with 10.000 extra badness in the future,
as is the case with other polkit related errors. This affects all
packages in openSUSE:Factory.
The rationale behind that is that even though these polkit rules seem
harmless (only locally logged in users with admin privileges can acquire
the polkit privilege), they can expose security issues. This is because
the correct enforcement of the polkit policy is depending on the
individual package's polkit adaption.
Therefore such packages must go through a review process with the
security team. You can trigger this process by opening a bug against
security-team(a)suse.de and adding an AUDIT prefix to the bug summary.
For more about this please refer to this wiki page:
https://en.opensuse.org/openSUSE:Package_security_guidelines
We don't expect many packages to be affected by this. If you have any
questions please reach out to us.
Thank you
Matthias
--
Matthias Gerstner <matthias.gerstner(a)suse.de>
Dipl.-Wirtsch.-Inf. (FH), Security Engineer
https://www.suse.com/security
Telefon: +49 911 740 53 290
GPG Key ID: 0x14C405C971923553
SUSE Linux GmbH
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nuernberg)
Hi,
> There will not be an automated migration path from an old SuSEfirewall2
> configuration to a firewalld configuration. There is a package
> "susefirewall2-to-firewalld" which contains a utility for converting
> SuSEfirewall2 configurations to firewalld. It's only a supporting tool
> that tries to do the right thing. But it requires manual interaction and
> review of the resulting firewall rules.
Is there a plan or some guidance for packages that drop files in
/etc/sysconfig/SuSEfirewall2.d/services/ ?
$ ls -1 /etc/sysconfig/SuSEfirewall2.d/services/ | grep -v TEMPLATE | wc -l
33
Thanks,
Robert
--
http://robert.muntea.nu/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
since nearly 6 month now i have trouble with
my unstable ryzen systems.
randmom crashes after a couple of hours (<8), (nearly) no load, most times only hard reset
is possible to start system new.
most times nothing special in system-log
(as i know, maybe somebody who know more could see suspected things.)
after searching the net:
because i am not really familiar with kernel-boot parameter settings,
and i have read its necessary to build own kernel (on lists of other distributions)
i like to ask:
how to fix (work around) or if maybe included in
the tumbleweed-kernel the "low load freeze of ryzen"
here: ryzen (1700) 8 core processor systems with tumbleweed.
i read several links found by google:
https://bugzilla.kernel.org/show_bug.cgi?id=196683https://bugs.launchpad.net/linux/+bug/1690085/comments/69https://forums.fedoraforum.org/showthread.php?315887-Random-Crashing
they suggest to include rcu_nocbs=0-15
is /etc/defaults/grub file
correct?
GRUB_CMDLINE_LINUX_DEFAULT="video=1920x1200 splash=silent quiet showopts"
change to:
GRUB_CMDLINE_LINUX_DEFAULT="video=1920x1200 splash=silent quiet showopts rcu_nocbs=0-15 "
??
and run:
grub2-mkconfig?
is this correct will this work? or is there a better/other solution for tumbleweed?
(at the moment here not the newest version of tumbleweed):
how to check the tumbleweed version?
uname -a
Linux becherer1 4.14.2-1-default #1 SMP PREEMPT Fri Nov 24 08:20:07 UTC 2017 (b0610fc) x86_64 x86_64 x86_64 GNU/Linux
============
by the way, as suggested by this mailing-list i have replaced the amd ryzen prozessors because of the
segfault problem (i found this problem for my systemsy after the hint on this list).
tumbleweed is now running fine with HIGH load (kill-ryzen.sh) script (more than 48 hours)
and for others who read inside internet "amd ryzen production date "after week 25 (sometimes is written week30) is fine"
THIS is NOT TRUE. at least this type:
ryzen 1700 UA 1733PGS
has this bug, (2017 week 33) (i have had after a first replacement 4 of this processors all have
had this bug) see also here:
https://forum.level1techs.com/t/ryzen-pre-week-25-fabrication-rma-issue/118…
==============================
would be happy to get an info how to fix the low load problem to get stable tumbleweed-ryzen-system's.
thanks in advance,
simoN
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIbBAEBAgAGBQJacJjHAAoJEOuDxDCJWQG+9Y8P+K6tnQsCVoKSI4rrrSWqHGJf
aZEcAqmgP1R+DvR6/79iDEx3P5Gq0CWSdGWTY8y385PA5AeurT+C/0n2yE84ojjM
SzrzK3b5I+qMPCaHJNrrHpPa6WZW9DCSf1sE88XXDDKBscIVvCsbP2g//IYNMT1F
6ncZRzOmGXGPaeuTvAeQ6tfNKUL1rBA7QKjHwILpUE5hkFY8WW++fhiej9sklXxM
QJzpfV0KWJEUtu8aEkV/TShL6N/kjJhwDDPiLO5vV/LkeGIDSLJwqOBkMn0+TYBk
CJb72SCQEAvM+dL8Zjnz9Z5IwOKxIZvq0rKxay9UnwtH/KUDMnsznHo9yxcjbp6S
czSnr5Aov8BKxnOI6nKFr94oZSk/x0djZZLtsp00LgHnKLkZZTzjQTurQkWy5e6W
4ZUNtSwgpXINqPz87eIgcEvvRNV16HhdstmBf12OSPls9Z1RDDrQR6plEPWU823Q
pZUEyEBDNSqArNLNUpW7VPBh0u3BdqWdyQCbuyb2StkVKXi9xtaVZJrzEKYQMELt
JLXL5Efz6SlYsSYWsrPWGrwBXWnJ4TSUHmnJTWJQ9W8krap4E9c9X0hBG4uwUL6r
0IJXwNBodJCwS7mAZ+Ri13i7fv5RrIkODklTbyx402GFjFDgIeLF8cKu+5CEYasL
RMdkHKjfhQbSTTMGt/c=
=aB7T
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi Stefan, Dominique & all,
The recent kernel v4.14.9 release breaks NVIDIA driver. There's a
patch available on
https://devtalk.nvidia.com/default/topic/1028016/linux/patch-for-compiling-…,
do you mind applying it?
Going further, would be the openQA test that tries to install NVIDIA
proprietary driver be ever accepted to general test suite? Or is there
an OBS project with "working-with-nvidia" kernel packages? Sure, these
suggestions are off top of the head, probably there is a better way to
prevent "nvidia driver doesn't compile for 3 snapshots in a row, older
kernels were just purged by purge-kernels so X doesn't run at all"
case.
Thank you in advance.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello all,
we still happen to have may packages depending on xorg-x11-devel which
is metapackage pulling in whole x11 stack to the dependency chain.
This means your package waits for the full X stack to be available
before it even contemplates building.
There are currently 107 packages doing this (see attached file) as such
it is pretty annoying to open bugreports against everything.
As such would it be possible if interested souls fix their packages to
require only the stuff they need, preferably in the pkgconfig format,
ie:
BuildRequires: pkgconfig(libxcb)
I will also add rpmlint error to fail all packages that are adding this
dependency (as we are keeping the package for weird binary 3rd party
apps, but do not want it in OBS).
Thanks
Tom
Following up on my prior announcement [1] of Tumbleweed Snapshots, introducing
a snapshot review site [2]. By utilizing a variety of sources of feedback
pertaining to snapshots a stability score is estimated. The goal is to err on
the side of caution and to allow users to avoid troublesome releases. Obviously,
there are many enthusiasts who enjoy encountering issues and working to resolve
them, but others are looking for a relatively stable experience.
Releases with a low score will continue to impact future release scores with a
gradual trail-off. Given that issues generally are not fixed immediately in the
next release this assumes the next few releases may still be affected. If the
issue persists and is severe it will likely be mentioned again in the mailing
list and the score again reduced.
Major system components that are either release candidates or low minor releases
are also considered to be risky. For example, recent Mesa release candidates
caused white/black screens for many users which is not-trivial to recover from
for less-technical users. Such issues come around from time to time since openQA
will not catch everything.
Release stability is considered to be pending for the first week after release
to allow time for reports to surface. This of course depends on enthusiasts who
update often, encounter, and report problems.
The scoring is likely to be tweaked over time to reflect observations. It may
also make sense to add a manual override feature to aid scoring when something
critical is encountered.
Integrating the scoring data into the tumbleweed-cli would allow users to pick a
minimum stability level or score and only update to those releases. Such a
mechanism can be vital for systems run by family members, servers, or the wave
of gamers looking for the latest OSS graphics stack.
For more details see the code behind the site [3]. Currently, you can see the
very low scores for the releases laden with shader cache issues and those
therafter. This is the first iteration of the site so nothing too fancy and the
score is fairly basic.
The site also provides a machine readable (YAML) version of the data [4].
As a side-node, Tumbleweed Snapshots are limited to 50 snapshots due to a
hosting restriction [5], but that should generally be over two months worth.
Hopefully others find this useful, enjoy!
[1] https://lists.opensuse.org/opensuse-factory/2017-11/msg00591.html
[2] http://review.tumbleweed.boombatower.com/
[3] https://github.com/boombatower/tumbleweed-review
[4] http://review.tumbleweed.boombatower.com/data.html
[5] http://release-tools.opensuse.org/2018/02/09/w05-06.html
--
Jimmy
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Fresh install of Leap 42.3 on a system with / as btrfs.
Ran a 'snapper cleanup number' a couple days ago, and now I get this:
quota not working (preparing quota failed)
Looking at the quota setup, it looks like the quota groups are missing:
<hostname>:~ # btrfs qgroup show -pc /
ERROR: can't perform the search - No such file or directory
ERROR: can't list qgroups: No such file or directory
Not sure what the next steps here are - can someone assist?
Thanks,
Jim
--
Jim Henderson
Please keep on-topic replies on the list so everyone benefits
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
I ran a zypper dup on a xen guest and noticed a few messages, I thought
they might be of interest to someone:
(424/774) Installing: klogd-1.4.1-lp150.2.3.x86_64 ...............[done]
Additional rpm output:
/var/tmp/rpm-tmp.5lyOph: line 14: /var/adm/fillup-templates/syslog.del:
No such file or directory
fillup: Exception in ../SRC/services.c, line 348 concerning file
not opened
/var/tmp/rpm-tmp.5lyOph: line 36: /var/adm/fillup-templates/syslog.del:
No such file or directory
fillup: Exception in ../SRC/services.c, line 348 concerning file
not opened
Failed to try-restart klogd.service: Operation refused, unit
klogd.service may be requested by dependency only (it is configured to
refuse manual start/stop).
See system logs and 'systemctl status klogd.service' for details.
(476/774) Installing:
kbd-2.0.4-lp150.4.1.x86_64 ....................................[done]
Additional rpm output:
SysV service kbdsettings does not exist, skipping
Updating /etc/sysconfig/console ...
Updating /etc/sysconfig/keyboard ...
/var/tmp/rpm-tmp.zeOhE0: line
62: /var/adm/fillup-templates/keyboard.del: No such file or directory
/var/tmp/rpm-tmp.zeOhE0: line
62: /var/adm/fillup-templates/keyboard.del: No such file or directory
fillup: Exception in ../SRC/services.c, line 348 concerning file
not opened
Created
symlink /etc/systemd/system/multi-user.target.wants/kbdsettings.service -> /usr/lib/systemd/system/kbdsettings.service.
(478/774) Installing:
ca-certificates-2+git20170807.10b2785-lp150.4.2.noarch ..........[done]
Additional rpm output:
p11-kit: couldn't complete writing
file: /var/lib/ca-certificates/openssl/CFCA_EV_ROOT.pem: No such file
or directory
p11-kit: 'destination != NULL' not true at p11_save_symlink_in
(714/774) Installing:
syslog-service-2.0-lp150.2.3.noarch .............................[done]
Additional rpm output:
/var/tmp/rpm-tmp.RRzemz: line 11: /var/adm/fillup-templates/syslog.del:
No such file or directory
fillup: Exception in ../SRC/services.c, line 348 concerning file
not opened
/var/tmp/rpm-tmp.RRzemz: line 33: /var/adm/fillup-templates/syslog.del:
No such file or directory
fillup: Exception in ../SRC/services.c, line 348 concerning file
not opened
Updating /etc/sysconfig/boot ...
Failed to try-restart klog.service: Operation refused, unit klog.service
may be requested by dependency only (it is configured to refuse manual
start/stop).
See system logs and 'systemctl status klog.service' for details.
(718/774) Installing:
syslog-ng-3.12.1-lp150.3.5.x86_64 ..............................[done]
Additional rpm output:
warning: /etc/syslog-ng/syslog-ng.conf created
as /etc/syslog-ng/syslog-ng.conf.rpmnew
/var/tmp/rpm-tmp.eFDQDE: line 18: /var/adm/fillup-templates/syslog.del:
No such file or directory
/var/tmp/rpm-tmp.eFDQDE: line 18: /var/adm/fillup-templates/syslog.del:
No such file or directory
fillup: Exception in ../SRC/services.c, line 348 concerning file
not opened
Updating /etc/sysconfig/syslog ...
(718/774) Installing:
syslog-ng-3.12.1-lp150.3.5.x86_64 ...............................[done]
Additional rpm output:
warning: /etc/syslog-ng/syslog-ng.conf created
as /etc/syslog-ng/syslog-ng.conf.rpmnew
/var/tmp/rpm-tmp.eFDQDE: line 18: /var/adm/fillup-templates/syslog.del:
No such file or directory
/var/tmp/rpm-tmp.eFDQDE: line 18: /var/adm/fillup-templates/syslog.del:
No such file or directory
fillup: Exception in ../SRC/services.c, line 348 concerning file
not opened
Updating /etc/sysconfig/syslog ...
I also noticed the initrd being rebuilt twice, with this error:
dracut-install: ERROR:
installing '/usr/lib/udev/rules.d/54-before-scsi-sg3_id.rules/usr/lib/udev/rules.d/11-dm-parts.rules'
dracut: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.UuWGUc/initramfs -a /usr/lib/udev/rules.d/54-before-scsi-sg3_id.rules/usr/lib/udev/rules.d/11-dm-parts.rules
I'm opening a bugreport on the latter.
--
Per Jessen, Zürich (1.8°C)
http://www.hostsuisse.com/ - virtual servers, made in Switzerland.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org