https://bugzilla.suse.com/show_bug.cgi?id=1203808https://bugzilla.suse.com/show_bug.cgi?id=1203808#c5
--- Comment #5 from Swamp Workflow Management <swamp(a)suse.de> ---
openSUSE-SU-2022:10138-1: An update that fixes 18 vulnerabilities is now
available.
Category: security (important)
Bug References: 1203808
CVE References:
CVE-2022-3201,CVE-2022-3304,CVE-2022-3305,CVE-2022-3306,CVE-2022-3307,CVE-2022-3308,CVE-2022-3309,CVE-2022-3310,CVE-2022-3311,CVE-2022-3312,CVE-2022-3313,CVE-2022-3314,CVE-2022-3315,CVE-2022-3316,CVE-2022-3317,CVE-2022-3318,CVE-2022-3370,CVE-2022-3373
JIRA References:
Sources used:
openSUSE Backports SLE-15-SP4 (src): chromium-106.0.5249.91-bp154.2.32.1
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1203808https://bugzilla.suse.com/show_bug.cgi?id=1203808#c4
--- Comment #4 from Swamp Workflow Management <swamp(a)suse.de> ---
openSUSE-SU-2022:10139-1: An update that fixes 18 vulnerabilities is now
available.
Category: security (important)
Bug References: 1203808
CVE References:
CVE-2022-3201,CVE-2022-3304,CVE-2022-3305,CVE-2022-3306,CVE-2022-3307,CVE-2022-3308,CVE-2022-3309,CVE-2022-3310,CVE-2022-3311,CVE-2022-3312,CVE-2022-3313,CVE-2022-3314,CVE-2022-3315,CVE-2022-3316,CVE-2022-3317,CVE-2022-3318,CVE-2022-3370,CVE-2022-3373
JIRA References:
Sources used:
openSUSE Backports SLE-15-SP3 (src): chromium-106.0.5249.91-bp153.2.125.1
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203968
Bug ID: 1203968
Summary: Kernel 5.14.21.15400.24.21.2 long time to boot " a
start job..." and udev fails
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.4
Hardware: x86-64
OS: openSUSE Leap 15.4
Status: NEW
Severity: Major
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: rf(a)keynet-technology.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 861923
--> http://bugzilla.opensuse.org/attachment.cgi?id=861923&action=edit
Kernel Bootup screen
After upgrade from 15.3, kernel version 5.14.21.15400.24.21.2 repeatedly hangs
for 2-3 mins (see attached photo), then udev doesn't appear to have worked
properly as in at least 1 case, bttv pci card not recognized (in dmesg) though
working module config exists from 15.3.
modprobe -r bttv then modprobe bttv once booted, and card is recognised.
Revert to kernel 5.14.21.15400.22.1 and it doesn't halt + udev works as
expected, card is recognised using existing unchanged config.
Hardware is an HP 8300 CMT, with a Kodicom 4400R multi bttv card.
100% repeatable
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1181970
Bug ID: 1181970
Summary: Can't restart service because masked services
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Salt
Assignee: salt-maintainers(a)suse.de
Reporter: dev.dorrejo(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Hello, i am being bothered because each time i do a upgrade on opensuse
tumbleweed and need to restart some service like apache, php-fpm, postfix,
etc..., i found that they wont restart/start because the next masked
partitions.
mercurio:/etc/apache2/vhosts.d # systemctl restart apache2.service
php-fpm.service postfix.service
Failed to restart apache2.service: Unit tmp.mount is masked.
Failed to restart php-fpm.service: Unit tmp.mount is masked.
Failed to restart postfix.service: Unit var-run.mount is masked.
Each time i do update and have to restart/stop the service appear message like
the one before.
doing: systemctl unmask --now tmp.mount wont do nothing, tryed masking and
unmasking again but the issue persist and have to reboot the server to apply
those reboot of service.
Status of the .mount:
mercurio:/etc/apache2/vhosts.d # systemctl status tmp.mount
��� tmp.mount - /tmp
Loaded: masked (Reason: Unit tmp.mount is masked.)
Active: active (mounted) (Result: exit-code) since Mon 2021-02-08 22:01:05
AST; 10min ago
Where: /tmp
What: tmpfs
Tasks: 0 (limit: 4915)
CGroup: /system.slice/tmp.mount
Feb 08 22:01:05 mercurio umount[16479]: umount: /tmp: target is busy.
Feb 08 22:01:05 mercurio systemd[1]: Unmounting /tmp...
Feb 08 22:01:05 mercurio systemd[1]: tmp.mount: Mount process exited,
code=exited, status=32/n/a
Feb 08 22:01:05 mercurio systemd[1]: Failed unmounting /tmp.
mercurio:/etc/apache2/vhosts.d # systemctl status var.mount
��� var.mount - /var
Loaded: masked (Reason: Unit var.mount is masked.)
Active: active (mounted) (Result: exit-code) since Mon 2021-02-08 22:01:05
AST; 11min ago
Where: /var
What: /dev/mapper/vg0-root
Tasks: 0 (limit: 4915)
CGroup: /system.slice/var.mount
Feb 05 20:37:25 localhost systemd[1]: Mounting /var...
Feb 05 20:37:25 localhost systemd[1]: Mounted /var.
Feb 08 22:01:05 mercurio systemd[1]: Unmounting /var...
Feb 08 22:01:05 mercurio umount[16480]: umount: /var: target is busy.
Feb 08 22:01:05 mercurio systemd[1]: var.mount: Mount process exited,
code=exited, status=32/n/a
Feb 08 22:01:05 mercurio systemd[1]: Failed unmounting /var.
mercurio:/etc/apache2/vhosts.d # systemctl status var-run.mount
��� var-run.mount
Loaded: masked (Reason: Unit var-run.mount is masked.)
Active: inactive (dead)
Condition: start condition failed at Fri 2021-02-05 20:37:25 AST; 3 days ago
Feb 05 20:37:25 localhost systemd[1]: Condition check resulted in Runtime
Directory being skipped.
journalctl said nothing about this issue.
systemctl list-units: https://susepaste.org/56464129
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1203176https://bugzilla.suse.com/show_bug.cgi?id=1203176#c13
--- Comment #13 from macias - <bluedzins(a)wp.pl> ---
"When you disable nouveau packages"
I didn't say word about disabling it. I wrote about excluding them from default
setup.
Default setup should be stable, safe and secure. When the user has extra needs
or/and knows exactly the risks, no problem she/he can install nouveau or other
risky package. Default selection should mean peace of mind.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1203869https://bugzilla.suse.com/show_bug.cgi?id=1203869#c4
--- Comment #4 from Axel Schwarzer <SchwarzerA(a)messe-duesseldorf.de> ---
(In reply to Thorsten Kukuk from comment #1)
> The switch to pam_motd in Tumbleweed is a pretty old change, could it be
> that you ignored rpmsave for login.defs since a long time?
> Sounds like you have still MOTD enabled there.
>
> About PAM configuration see this wiki:
> https://en.opensuse.org/openSUSE:Packaging_UsrEtc
No, because there was no login.defs.rpmsave. Unfortunately I can not speak for
colleagues we share our duty cycles with.
In /usr/etc/ login.defs was changed by login_defs-4.12.3-1.3.noarch to
-rw-r--r-- 1 root root 10669 Aug 31 18:15 login.defs
and according to https://en.opensuse.org/openSUSE:Packaging_UsrEtc the locally
adapted login.defs still resides in /etc/. Or might that be the point?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203716
Bug ID: 1203716
Summary: Gnome 43 Backgrounds are not displayed correctly.
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
Assignee: gnome-bugs(a)suse.de
Reporter: r.alonso(a)mailbox.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
The new Gnome backgrounds are not displayed correctly.
They are monochrome.
Only when I installed "webp-pixbuf-loader" after they were displayed correctly.
This is apparently a bug in the resolution of the dependencies?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1203869https://bugzilla.suse.com/show_bug.cgi?id=1203869#c3
--- Comment #3 from Axel Schwarzer <SchwarzerA(a)messe-duesseldorf.de> ---
(In reply to Thorsten Kukuk from comment #2)
> (In reply to Axel Schwarzer from comment #0)
>
> > openSUSE Leap 15.4 still has them and we need to transfer them to Tumbleweed for the time
> > being which is not optimal.
>
> Copying random PAM config files from 15.4 to Tumbleweed is the best way to
> break your system...
Sure but at first sight this was a quick solution for that problem.
--
You are receiving this mail because:
You are on the CC list for the bug.