--17246790275.B43a3b97.1115
Date: Mon, 26 Aug 2024 13:30:27 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1229757

            Bug ID: 1229757
           Summary: Package conflict in libsemanage (shadow) update
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: msvec-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: meissner-at-suse.com, mvetter-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

This is what I get with the latest MU:

+ zypper patch --with-optional

Problem: 1: the to be installed libsemanage2-3.5-150600.1.48.x86_64 requires
'libsemanage-conf >=3D 3.5', but this requirement cannot be provided
not installable providers: libsemanage-conf-3.5-150600.1.48.x86_64[repo-oss]

 Solution 1: Following actions will be done:
  do not install patch:openSUSE-SLE-15.6-2024-2808-1.noarch
  do not install patch:openSUSE-SLE-15.6-2024-2630-1.noarch
 Solution 2: deinstallation of libsemanage1-3.1-150400.1.65.x86_64
 Solution 3: deinstallation of shadow-4.8.1-150400.8.57.x86_64
 Solution 4: break libsemanage2-3.5-150600.1.48.x86_64 by ignoring some of =
its
dependencies
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17246790275.B43a3b97.1115
Date: Mon, 26 Aug 2024 13:30:27 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1229757

          Summary
          Package conflict in libsemanage (shadow) update

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          msvec@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          meissner@suse.com, mvetter@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

This is what I get with the latest MU:

+ zypper patch --with-optional

Problem: 1: the to be installed libsemanage2-3.5-150600.1.48.x86_64 requires
'libsemanage-conf >=3D 3.5', but this requirement cannot be provided
not installable providers: libsemanage-conf-3.5-150600.1.48.x86_64[repo-oss]

 Solution 1: Following actions will be done:
  do not install patch:openSUSE-SLE-15.6-2024-2808-1.noarch
  do not install patch:openSUSE-SLE-15.6-2024-2630-1.noarch
 Solution 2: deinstallation of libsemanage1-3.1-150400.1.65.x86_64
 Solution 3: deinstallation of shadow-4.8.1-150400.8.57.x86_64
 Solution 4: break libsemanage2-3.5-150600.1.48.x86_64 by ignoring some of =
its
dependencies

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17246790275.B43a3b97.1115--


--17247486410.1DdDcA.830
Date: Tue, 27 Aug 2024 08:50:41 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1229807

            Bug ID: 1229807
           Summary: [Build 12.5] Agama live boot test failed for 'Unable to connect localhost'
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 16.0
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/4436185/modules/boot
                    _agama/steps/10
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: leli-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

## Observation
Agama live boot test failed for 'Unable to connect localhost'.

Before the failure reported, we found it failed to start agama installer
service=20=20
in https://openqa.opensuse.org/tests/4436185#step/boot_agama/5.=20
And the test failed to collect the service log, I think it is because the a=
gama
installer service hasn't started so it won't recognize the live password se=
t by
live.password=3D"linux".

openQA test in scenario
opensuse-agama-9.0-agama-installer-x86_64-agama_auto_default@64bit fails in
[boot_agama](https://openqa.opensuse.org/tests/4436185/modules/boot_agama/s=
teps/10)

## Test suite description
The base test suite is used for job templates defined in YAML documents. It=
 has
no settings of its own.

## Reproducible

Fails since (at least) Build [12.4](https://openqa.opensuse.org/tests/44361=
27)

## Expected result

Last good: [12.3](https://openqa.opensuse.org/tests/4436102) (or more recen=
t)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=3Dx86_64&distri=3Dop=
ensuse&flavor=3Dagama-installer&machine=3D64bit&test=3Dagama_auto_default&v=
ersion=3Dagama-9.0)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17247486410.1DdDcA.830
Date: Tue, 27 Aug 2024 08:50:41 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1229807

          Summary
          [Build 12.5] Agama live boot test failed for 'Unable to conne=
ct localhost'

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 16.0

          Hardware
          Other

          URL
          https://openqa.opensuse.org/tests/4436185/modules/boot_agama/=
steps/10

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          leli@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

## Observation
Agama live boot test failed for 'Unable to connect localhost'.

Before the failure reported, we found it failed to start agama installer
service=20=20
in =
https://openqa.opensuse.org/tests/4436185#step/boot_agama/5.=20
And the test failed to collect the service log, I think it is because the a=
gama
installer service hasn't started so it won't recognize the live password se=
t by
live.password=3D"linux".

openQA test in scenario
opensuse-agama-9.0-agama-installer-x86_64-agama_auto_default@64bit fail=
s in
[boot_agama](https://openqa.opensuse.org/tests/4436185/modules/boot_=
agama/steps/10)

## Test suite description
The base test suite is used for job templates defined in YAML documents. It=
 has
no settings of its own.

## Reproducible

Fails since (at least) Build [12.4](https://openqa.opensuse.org/tests/4436127)

## Expected result

Last good: [12.3](htt=
ps://openqa.opensuse.org/tests/4436102) (or more recent)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.=
org/tests/latest?arch=3Dx86_64&distri=3Dopensuse&flavor=3Dagama-ins=
taller&machine=3D64bit&test=3Dagama_auto_default&version=3Dagam=
a-9.0)

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17247486410.1DdDcA.830--


body:
--17248483152.e4F27f.2326
Date: Wed, 28 Aug 2024 12:31:55 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1229868

            Bug ID: 1229868
           Summary: llvm17 fails to build on aarch64
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
                CC: aaronpuchert@alice-dsl.net
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 876997
  --> https://bugzilla.suse.com/attachment.cgi?id=3D876997&action=3Dedit
Failures from build log

llvm17 fails to build on aarch64, likely due to the switch to gcc14
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17248483152.e4F27f.2326
Date: Wed, 28 Aug 2024 12:31:55 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1229868

          Summary
          llvm17 fails to build on aarch64

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          aarch64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Development

          Assignee
          screening-team-bugs@suse.de

          Reporter
          guillaume.gardet@arm.com

          QA Contact
          qa-bugs@suse.de

          CC
          aaronpuchert@alice-dsl.net

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 876=
997 [details]
Failures from build log

llvm17 fails to build on aarch64, likely due to the switch to gcc14

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17248483152.e4F27f.2326--

summary: llvm17 fails to build on aarch64


body:
--17248757160.2C1D.224
Date: Wed, 28 Aug 2024 20:08:36 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1229887

            Bug ID: 1229887
           Summary: new pacakge: ZoneMinder
    Classification: openSUSE
           Product: openSUSE Backports
           Version: SLE-15-SP6
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Packages
          Assignee: packagehub-bugs-at-suse.com
          Reporter: erico.mendonca-at-suse.com
        QA Contact: packagehub-bugs-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I'm submitting the stable version of ZoneMinder (From security:zoneminder) =
to
the backports/PackageHub, as a customer expressed interest in having it
available for SLE, even if it's "as-is".

I'm also submitting a copy of the perl-Sys-Mmap package from
devel:languages:perl, which hasn't changed in years, but is a requirement f=
or
building ZoneMinder.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17248757160.2C1D.224
Date: Wed, 28 Aug 2024 20:08:36 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1229887

          Summary
          new pacakge: ZoneMinder

          Classification
          openSUSE

          Product
          openSUSE Backports

          Version
          SLE-15-SP6

          Hardware
          Other

          OS
          Linux

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Packages

          Assignee
          packagehub-bugs@suse.com

          Reporter
          erico.mendonca@suse.com

          QA Contact
          packagehub-bugs@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I'm submitting the stable version of ZoneMinder (From securi=
ty:zoneminder) to
the backports/PackageHub, as a customer expressed interest in having it
available for SLE, even if it's "as-is".

I'm also submitting a copy of the perl-Sys-Mmap package from
devel:languages:perl, which hasn't changed in years, but is a requirement f=
or
building ZoneMinder.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17248757160.2C1D.224--

summary: new pacakge: ZoneMinder


--17249000281.B71b9A.467
Date: Thu, 29 Aug 2024 02:53:48 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1229893

            Bug ID: 1229893
           Summary: qtwayland 6.7.2 crashes on deepin-tray-loader
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: gfx-bugs-at-suse.de
          Reporter: hillwoodroc-at-gmail.com
        QA Contact: gfx-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

(gdb) bt
#0  0x00007ffff1b1daf4 in
QtWaylandClient::QWaylandShmBuffer::QWaylandShmBuffer(QtWaylandClient::QWay=
landDisplay*,
QSize const&, QImage::Format, double) () at /lib64/libQt5WaylandClient.so.5=
=20=20=20=20=20
#1  0x00007ffff1b1e089 in
QtWaylandClient::QWaylandShmBackingStore::getBuffer(QSize const&) ()
    at /lib64/libQt5WaylandClient.so.5
#2  0x00007ffff1b1e18e in
QtWaylandClient::QWaylandShmBackingStore::resize(QSize const&) ()
    at /lib64/libQt5WaylandClient.so.5
#3  0x00007ffff1b1e3e9 in
QtWaylandClient::QWaylandShmBackingStore::beginPaint(QRegion const&) ()
    at /lib64/libQt5WaylandClient.so.5
#4  0x00007ffff6f5a59f in QBackingStore::beginPaint (this=3D0x55555562eab0,
region=3D...) at painting/qbackingstore.cpp:138
#5  0x00007ffff75b62da in QWidgetRepaintManager::paintAndFlush
(this=3Dthis@entry=3D0x55555563baf0)
    at kernel/qwidgetrepaintmanager.cpp:989
#6  0x00007ffff75b6c7a in QWidgetRepaintManager::sync (this=3D0x55555563baf=
0,
exposedWidget=3D0x55555562e620, exposedRegion=3D...)
    at kernel/qwidgetrepaintmanager.cpp:743
#7  0x00007ffff7602f71 in QWidgetWindow::event (this=3D0x555555633f00,
event=3D0x7fffffffd4e0) at kernel/qwidgetwindow.cpp:347
#8  0x00007ffff75a513e in QApplicationPrivate::notify_helper
    (this=3D<optimized out>, receiver=3D0x555555633f00, e=3D0x7fffffffd4e0)=
 at
kernel/qapplication.cpp:3640
#9  0x00007ffff66ed8e8 in QCoreApplication::notifyInternal2
(receiver=3D0x555555633f00, event=3D0x7fffffffd4e0)
    at kernel/qcoreapplication.cpp:1064
#10 0x00007ffff66edabe in QCoreApplication::sendSpontaneousEvent
(receiver=3D<optimized out>, event=3D<optimized out>)
    at kernel/qcoreapplication.cpp:1474
#11 0x00007ffff6d7e55d in QGuiApplicationPrivate::processExposeEvent
(e=3D0x5555555abc90) at kernel/qguiapplication.cpp:3261
#12 0x00007ffff6d503dc in QWindowSystemInterface::sendWindowSystemEvents
(flags=3D...)
    at kernel/qwindowsysteminterface.cpp:1169
#13 0x00007ffff1b612e0 in ??? () at /lib64/libQt5WaylandClient.so.5
#14 0x00007ffff5a29760 in g_main_dispatch (context=3D0x7fffec000ed0) at
../glib/gmain.c:3344
#15 g_main_context_dispatch_unlocked (context=3Dcontext@entry=3D0x7fffec000=
ed0) at
../glib/gmain.c:4152
#16 0x00007ffff5a2b3a8 in g_main_context_iterate_unlocked
    (context=3Dcontext@entry=3D0x7fffec000ed0, block=3Dblock@entry=3D1,
dispatch=3Ddispatch@entry=3D1, self=3D<optimized out>)
    at ../glib/gmain.c:4217
#17 0x00007ffff5a2ba5c in g_main_context_iteration (context=3D0x7fffec000ed=
0,
may_block=3D1) at ../glib/gmain.c:4282
#18 0x00007ffff6746826 in QEventDispatcherGlib::processEvents
(this=3D0x5555555bcc00, flags=3D...)
    at kernel/qeventdispatcher_glib.cpp:423
#19 0x00007ffff66ec37b in QEventLoop::exec (this=3Dthis@entry=3D0x7fffffffd=
750,
flags=3D..., flags@entry=3D...)
    at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#20 0x00007ffff66f4810 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#21 0x000055555556267b in ??? ()
#22 0x00007ffff5c2a340 in __libc_start_call_main
    (main=3Dmain@entry=3D0x5555555618b0, argc=3Dargc@entry=3D5,
argv=3Dargv@entry=3D0x7fffffffdb08)
    at ../sysdeps/nptl/libc_start_call_main.h:58
#23 0x00007ffff5c2a409 in __libc_start_main_impl
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17249000281.B71b9A.467
Date: Thu, 29 Aug 2024 02:53:48 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1229893

          Summary
          qtwayland 6.7.2 crashes on deepin-tray-loader

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X.Org

          Assignee
          gfx-bugs@suse.de

          Reporter
          hillwoodroc@gmail.com

          QA Contact
          gfx-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

(gdb) bt
#0  0x00007ffff1b1daf4 in
QtWaylandClient::QWaylandShmBuffer::QWaylandShmBuffer(QtWaylandClient::QWay=
landDisplay*,
QSize const&, QImage::Format, double) () at /lib64/libQt5WaylandClient.=
so.5=20=20=20=20=20
#1  0x00007ffff1b1e089 in
QtWaylandClient::QWaylandShmBackingStore::getBuffer(QSize const&) ()
    at /lib64/libQt5WaylandClient.so.5
#2  0x00007ffff1b1e18e in
QtWaylandClient::QWaylandShmBackingStore::resize(QSize const&) ()
    at /lib64/libQt5WaylandClient.so.5
#3  0x00007ffff1b1e3e9 in
QtWaylandClient::QWaylandShmBackingStore::beginPaint(QRegion const&) ()
    at /lib64/libQt5WaylandClient.so.5
#4  0x00007ffff6f5a59f in QBackingStore::beginPaint (this=3D0x55555562eab0,
region=3D...) at painting/qbackingstore.cpp:138
#5  0x00007ffff75b62da in QWidgetRepaintManager::paintAndFlush
(this=3Dthis@entry=3D0x55555563baf0)
    at kernel/qwidgetrepaintmanager.cpp:989
#6  0x00007ffff75b6c7a in QWidgetRepaintManager::sync (this=3D0x55555563baf=
0,
exposedWidget=3D0x55555562e620, exposedRegion=3D...)
    at kernel/qwidgetrepaintmanager.cpp:743
#7  0x00007ffff7602f71 in QWidgetWindow::event (this=3D0x555555633f00,
event=3D0x7fffffffd4e0) at kernel/qwidgetwindow.cpp:347
#8  0x00007ffff75a513e in QApplicationPrivate::notify_helper
    (this=3D<optimized out>, receiver=3D0x555555633f00, e=3D0x7ffffff=
fd4e0) at
kernel/qapplication.cpp:3640
#9  0x00007ffff66ed8e8 in QCoreApplication::notifyInternal2
(receiver=3D0x555555633f00, event=3D0x7fffffffd4e0)
    at kernel/qcoreapplication.cpp:1064
#10 0x00007ffff66edabe in QCoreApplication::sendSpontaneousEvent
(receiver=3D<optimized out>, event=3D<optimized out>)
    at kernel/qcoreapplication.cpp:1474
#11 0x00007ffff6d7e55d in QGuiApplicationPrivate::processExposeEvent
(e=3D0x5555555abc90) at kernel/qguiapplication.cpp:3261
#12 0x00007ffff6d503dc in QWindowSystemInterface::sendWindowSystemEvents
(flags=3D...)
    at kernel/qwindowsysteminterface.cpp:1169
#13 0x00007ffff1b612e0 in ??? () at /lib64/libQt5WaylandClient.so.5
#14 0x00007ffff5a29760 in g_main_dispatch (context=3D0x7fffec000ed0) at
../glib/gmain.c:3344
#15 g_main_context_dispatch_unlocked (context=3Dcontext@entry=3D0x7fffe=
c000ed0) at
../glib/gmain.c:4152
#16 0x00007ffff5a2b3a8 in g_main_context_iterate_unlocked
    (context=3Dcontext@entry=3D0x7fffec000ed0, block=3Dblock@entry=
=3D1,
dispatch=3Ddispatch@entry=3D1, self=3D<optimized out>)
    at ../glib/gmain.c:4217
#17 0x00007ffff5a2ba5c in g_main_context_iteration (context=3D0x7fffec000ed=
0,
may_block=3D1) at ../glib/gmain.c:4282
#18 0x00007ffff6746826 in QEventDispatcherGlib::processEvents
(this=3D0x5555555bcc00, flags=3D...)
    at kernel/qeventdispatcher_glib.cpp:423
#19 0x00007ffff66ec37b in QEventLoop::exec (this=3Dthis@entry=3D0x7ffff=
fffd750,
flags=3D..., flags@entry=3D...)
    at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#20 0x00007ffff66f4810 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#21 0x000055555556267b in ??? ()
#22 0x00007ffff5c2a340 in __libc_start_call_main
    (main=3Dmain@entry=3D0x5555555618b0, argc=3Dargc@entry=3D5,
argv=3Dargv@entry=3D0x7fffffffdb08)
    at ../sysdeps/nptl/libc_start_call_main.h:58
#23 0x00007ffff5c2a409 in __libc_start_main_impl

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17249000281.B71b9A.467--


--17249157373.dD4D3.725
Date: Thu, 29 Aug 2024 07:15:37 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1229897

            Bug ID: 1229897
           Summary: VUL-0: chromium: multiple vulnerabilities fixed in 128.0.6613.113
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: Andreas.Stieger-at-gmx.de
          Reporter: gianluca.gabrielli-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

[TBD][351865302] High CVE-2024-7969: Type Confusion in V8. Reported by CFF =
of
Topsec Alpha Team on 2024-07-09
[TBD][360265320] High CVE-2024-8193: Heap buffer overflow in Skia. Reported=
 by
Renan Rios (@hyhy_100) on 2024-08-16
[TBD][360533914] High CVE-2024-8194: Type Confusion in V8. Reported by
Seunghyun Lee (@0x10n) on 2024-08-18
[TBD][360758697] High CVE-2024-8198: Heap buffer overflow in Skia. Reported=
 by
Renan Rios (@hyhy_100) on 2024-08-19
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17249157373.dD4D3.725
Date: Thu, 29 Aug 2024 07:15:37 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1229897

          Summary
          VUL-0: chromium: multiple vulnerabilities fixed in 128.0.6613=
.113

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          Andreas.Stieger@gmx.de

          Reporter
          gianluca.gabrielli@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          security-team@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

[TBD][351865302] High CVE-2024-7969: Type Confusion in V8. R=
eported by CFF of
Topsec Alpha Team on 2024-07-09
[TBD][360265320] High CVE-2024-8193: Heap buffer overflow in Skia. Reported=
 by
Renan Rios (@hyhy_100) on 2024-08-16
[TBD][360533914] High CVE-2024-8194: Type Confusion in V8. Reported by
Seunghyun Lee (@0x10n) on 2024-08-18
[TBD][360758697] High CVE-2024-8198: Heap buffer overflow in Skia. Reported=
 by
Renan Rios (@hyhy_100) on 2024-08-19

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17249157373.dD4D3.725--


body:
--17249281244.472ea.398
Date: Thu, 29 Aug 2024 10:42:04 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1229913

            Bug ID: 1229913
           Summary: AUDIT-1: kio-admin: revisit kio-admin privileged file operations via D-Bus
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: matthias.gerstner-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: popov895-at-ukr.net
  Target Milestone: ---
          Found By: ---
           Blocker: ---

+++ This bug was initially created as a clone of Bug #1205607

We've been asked to have a fresh look ad kio-admin, formerly rejected in bug
1205607. AFAIK upstream activities to come up with a robust API have been
abandoned, but we can still have another look at the current production cod=
e.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17249281244.472ea.398
Date: Thu, 29 Aug 2024 10:42:04 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1229913

          Summary
          AUDIT-1: kio-admin: revisit kio-admin privileged file operati=
ons via D-Bus

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          matthias.gerstner@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          popov895@ukr.net

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

+++ This bug was initially created as a clone of Bug #1205607

We've been asked to have a fresh look ad kio-admin, formerly rejected in bug
1205607. AFAIK upstream activities to come up with a robust API have been
abandoned, but we can still have another look at the current production cod=
e.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17249281244.472ea.398--

pkgs: polkit-default-privs rpmlint


--17250243942.2c4EdA7.1487
Date: Fri, 30 Aug 2024 13:26:34 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1229961

            Bug ID: 1229961
           Summary: erofs-utils: Enable support for zstd compression
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: daan.j.demeyer-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

erofs-utils supports zstd compression. Please enable this in the package via
passing --with-libzstd to the configure script.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17250243942.2c4EdA7.1487
Date: Fri, 30 Aug 2024 13:26:34 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1229961

          Summary
          erofs-utils: Enable support for zstd compression

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          daan.j.demeyer@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

erofs-utils supports zstd compression. Please enable this in=
 the package via
passing --with-libzstd to the configure script.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17250243942.2c4EdA7.1487--


--17251170770.C4FCf.405
Date: Sat, 31 Aug 2024 15:11:17 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1229997

            Bug ID: 1229997
           Summary: mdadm monitoring broken in Leap 15.6 (list and scan cannot be combined)
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: manfred99-at-gmx.ch
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

#> systemctl status mdmonitor
x mdmonitor.service - MD array monitor
     Loaded: loaded (/usr/lib/systemd/system/mdmonitor.service; static)
     Active: failed (Result: exit-code) since Wed 2024-08-28 22:42:31 CEST;=
 2
days ago
   Duration: 1ms
       Docs: man:mdadm(8)
    Process: 1482 ExecStartPre=3D/usr/libexec/mdadm/mdadm_env.sh (code=3Dex=
ited,
status=3D0/SUCCESS)
    Process: 1493 ExecStart=3D/usr/sbin/mdadm --monitor $MDADM_MONITOR_ARGS
(code=3Dexited, status=3D1/FAILURE)
   Main PID: 1493 (code=3Dexited, status=3D1/FAILURE)
        CPU: 6ms

Aug 28 22:42:31 mybox mdadm[1493]: mdadm: Devices list and --scan option ca=
nnot
be combined - not monitoring.
Aug 28 22:42:31 mybox systemd[1]: mdmonitor.service: Failed with result
'exit-code'.

After upgrading from 15.5 to 15.6, I encountered the above error message, it
used to work fine before.

Demangling the chain of includes, the resulting monitor command
from /usr/lib/systemd/system/mdmonitor.service seems to be:

#> /usr/sbin/mdadm --monitor /dev/md0 -d 60 -m "mail-at-example.com"  --scan  =
-c
"/etc/mdadm.conf"
mdadm: Devices list and --scan option cannot be combined - not monitoring.

The issue seems to be that both the device and "--scan" are set.
I tried the following change to only conditionally set MDADM_SCAN in
/usr/libexec/mdadm/mdadm_env.sh:=20

if [ -z "$MDADM_RAIDDEVICES" ] && [ x$MDADM_SCAN =3D x"yes" ]; then
  MDADM_SCAN=3D"--scan"
else
  MDADM_SCAN=3D""
fi

With this change it seems to work fine:

#> systemctl status mdmonitor
* mdmonitor.service - MD array monitor
     Loaded: loaded (/usr/lib/systemd/system/mdmonitor.service; static)
     Active: active (running) since Sat 2024-08-31 17:02:40 CEST; 9s ago
       Docs: man:mdadm(8)
    Process: 81806 ExecStartPre=3D/usr/libexec/mdadm/mdadm_env.sh (code=3De=
xited,
status=3D0/SUCCESS)
   Main PID: 81816 (mdadm)
      Tasks: 1 (limit: 77014)
        CPU: 8ms
     CGroup: /system.slice/mdmonitor.service
             `-81816 /usr/sbin/mdadm --monitor /dev/md0 -d 60 -m
mail-at-example.com -c /etc/mdadm.conf
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17251170770.C4FCf.405
Date: Sat, 31 Aug 2024 15:11:17 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1229997

          Summary
          mdadm monitoring broken in Leap 15.6 (list and scan cannot be=
 combined)

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Basesystem

          Assignee
          screening-team-bugs@suse.de

          Reporter
          manfred99@gmx.ch

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

#> systemctl status mdmonitor
x mdmonitor.service - MD array monitor
     Loaded: loaded (/usr/lib/systemd/system/mdmonitor.service; static)
     Active: failed (Result: exit-code) since Wed 2024-08-28 22:42:31 CEST;=
 2
days ago
   Duration: 1ms
       Docs: man:mdadm(8)
    Process: 1482 ExecStartPre=3D/usr/libexec/mdadm/mdadm_env.sh (code=3Dex=
ited,
status=3D0/SUCCESS)
    Process: 1493 ExecStart=3D/usr/sbin/mdadm --monitor $MDADM_MONITOR_ARGS
(code=3Dexited, status=3D1/FAILURE)
   Main PID: 1493 (code=3Dexited, status=3D1/FAILURE)
        CPU: 6ms

Aug 28 22:42:31 mybox mdadm[1493]: mdadm: Devices list and --scan option ca=
nnot
be combined - not monitoring.
Aug 28 22:42:31 mybox systemd[1]: mdmonitor.service: Failed with result
'exit-code'.

After upgrading from 15.5 to 15.6, I encountered the above error message, it
used to work fine before.

Demangling the chain of includes, the resulting monitor command
from /usr/lib/systemd/system/mdmonitor.service seems to be:

#> /usr/sbin/mdadm --monitor /dev/md0 -d 60 -m "mail@example.com"  --scan  -c
"/etc/mdadm.conf"
mdadm: Devices list and --scan option cannot be combined - not monitoring.

The issue seems to be that both the device and "--scan" are set.
I tried the following change to only conditionally set MDADM_SCAN in
/usr/libexec/mdadm/mdadm_env.sh:=20

if [ -z "$MDADM_RAIDDEVICES" ] && [ x$MDADM_SCAN =3D x&qu=
ot;yes" ]; then
  MDADM_SCAN=3D"--scan"
else
  MDADM_SCAN=3D""
fi

With this change it seems to work fine:

#> systemctl status mdmonitor
* mdmonitor.service - MD array monitor
     Loaded: loaded (/usr/lib/systemd/system/mdmonitor.service; static)
     Active: active (running) since Sat 2024-08-31 17:02:40 CEST; 9s ago
       Docs: man:mdadm(8)
    Process: 81806 ExecStartPre=3D/usr/libexec/mdadm/mdadm_env.sh (code=3De=
xited,
status=3D0/SUCCESS)
   Main PID: 81816 (mdadm)
      Tasks: 1 (limit: 77014)
        CPU: 8ms
     CGroup: /system.slice/mdmonitor.service
             `-81816 /usr/sbin/mdadm --monitor /dev/md0 -d 60 -m
mail@example.com -c /etc/md=
adm.conf

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17251170770.C4FCf.405--


--17252412751.F14A.62
Date: Mon, 2 Sep 2024 01:41:15 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230006

            Bug ID: 1230006
           Summary: Mobile Broadband unavailable after installation
    Classification: openSUSE
           Product: openSUSE Aeon
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Base
          Assignee: rbrown-at-suse.com
          Reporter: hja37-at-aol.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

On a fresh installation of openSUSE Aeon, it is not possible to configure a
Mobile Broadband connection due to a missing dependency of ModemManager,
libmbim. Without this library ModemManager is unable to configure the modem.
Observable behaviour is Mobile Network is absent from GNOME settings.

Solution: Install missing libmbim dependency and reboot the system. Mobile
Broadband is then configurable from GNOME settings, as expected.

    # transactional-update pkg in libmbim
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17252412751.F14A.62
Date: Mon, 2 Sep 2024 01:41:15 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230006

          Summary
          Mobile Broadband unavailable after installation

          Classification
          openSUSE

          Product
          openSUSE Aeon

          Version
          Current

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Base

          Assignee
          rbrown@suse.com

          Reporter
          hja37@aol.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

On a fresh installation of openSUSE Aeon, it is not possible=
 to configure a
Mobile Broadband connection due to a missing dependency of ModemManager,
libmbim. Without this library ModemManager is unable to configure the modem.
Observable behaviour is Mobile Network is absent from GNOME settings.

Solution: Install missing libmbim dependency and reboot the system. Mobile
Broadband is then configurable from GNOME settings, as expected.

    # transactional-update pkg in libmbim

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17252412751.F14A.62--


--17252661003.4Bc3Ef4.458
Date: Mon, 2 Sep 2024 08:35:00 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230022

            Bug ID: 1230022
           Summary: VUL-0: CVE-2024-45508: HTMLDOC before 1.9.19 has an out-of-bounds write in parse_paragraph in ps-pdf.cxx because of an attempt to strip leading whitespace from a whitespace-only node.
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/419446/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: pgajdos-at-suse.com
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: abergmann-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

HTMLDOC before 1.9.19 has an out-of-bounds write in parse_paragraph in
ps-pdf.cxx because of an attempt to strip leading whitespace from a
whitespace-only node.

Backport code-streams:
openSUSE:Backports:SLE-12-SP1/htmldoc
openSUSE:Backports:SLE-15-SP5:Update/htmldoc
openSUSE:Backports:SLE-15-SP6:Update/htmldoc

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45508
https://www.cve.org/CVERecord?id=3DCVE-2024-45508
https://github.com/michaelrsweet/htmldoc/blob/2d5b2ab9ddbf2aee2209010cebc11=
efdd1cab6e2/CHANGES.md
https://github.com/michaelrsweet/htmldoc/commit/2d5b2ab9ddbf2aee2209010cebc=
11efdd1cab6e2
https://github.com/michaelrsweet/htmldoc/issues/528
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17252661003.4Bc3Ef4.458
Date: Mon, 2 Sep 2024 08:35:00 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230022

          Summary
          VUL-0: CVE-2024-45508: HTMLDOC before 1.9.19 has an out-of-bo=
unds write in parse_paragraph in ps-pdf.cxx because of an attempt to strip =
leading whitespace from a whitespace-only node.

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          URL
          https://smash.suse.de/issue/419446/

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          pgajdos@suse.com

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          abergmann@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

HTMLDOC before 1.9.19 has an out-of-bounds write in parse_pa=
ragraph in
ps-pdf.cxx because of an attempt to strip leading whitespace from a
whitespace-only node.

Backport code-streams:
openSUSE:Backports:SLE-12-SP1/htmldoc
openSUSE:Backports:SLE-15-SP5:Update/htmldoc
openSUSE:Backports:SLE-15-SP6:Update/htmldoc

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45508
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-45508
https://github.com/michaelrsweet/htmldoc=
/blob/2d5b2ab9ddbf2aee2209010cebc11efdd1cab6e2/CHANGES.md
https://github.com/michaelrsweet/htmldoc/commit/2=
d5b2ab9ddbf2aee2209010cebc11efdd1cab6e2
https://git=
hub.com/michaelrsweet/htmldoc/issues/528

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17252661003.4Bc3Ef4.458--


--17252927960.DE1AC2F.1576
Date: Mon, 2 Sep 2024 15:59:56 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230062

            Bug ID: 1230062
           Summary: RISC-V: virtio-console sometimes gets stuck in set_termios.part.0
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: RISC-V
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 877101
  --> https://bugzilla.suse.com/attachment.cgi?id=3D877101&action=3Dedit
/proc/*/task/*/stack + strace of bash

openQA types in commands to the serial console, sends a newline and then wa=
its
until the prompt appears. Running this in a loop causes it to get stuck
sometimes: https://openqa.opensuse.org/tests/4445068#step/http_srv/16

In the QEMU chardev log it appears like this:

# systemctl --no-pager is-active apache2; echo hjhkw-$?-
active
hjhkw-0-
echo Lorem ipsum dolor sit amet > /srv/www/htdocs/index.html

openQA sends 'systemctl --no-pager is-active apache2; echo hjhkw-$?-\n',
receives 'active\nhjhkw-0-\n', then sends 'echo Lorem ipsum dolor sit amet >
/srv/www/htdocs/index.html\n' and waits for '# '. That does not arrive howe=
ver
and the wait times out. In most cases that's just ignored by openQA and it
moves on to the next command. When it sends that ("curl -f ..." here), the
missing part suddenly appears:

# echo Lorem ipsum dolor sit amet > /srv/www/htdocs/index.html
# curl -f http://localhost/ | grep 'Lorem ipsum dolor sit amet'; echo _Z5Xg=
-$?-

This issue appears to happen on riscv64 only, I have not observed it anywhe=
re
else so far.

Thankfully the arbitrarily long delay of the prompt allows to debug this. I
created a testcase that exercises the serial terminal in a loop and so far =
it
always gets stuck before the 20th attempt. I logged onto the graphical cons=
ole
and collected some info. The /bin/bash process on the console is stuck in t=
he
kernel:

/proc/1624/task/1624/stack:[<0>] set_termios.part.0+0x130/0x206
/proc/1624/task/1624/stack:[<0>] tty_mode_ioctl+0x46e/0x576
/proc/1624/task/1624/stack:[<0>] n_tty_ioctl_helper+0x2a/0xe4
/proc/1624/task/1624/stack:[<0>] n_tty_ioctl+0x9a/0x148
/proc/1624/task/1624/stack:[<0>] tty_ioctl+0x170/0x64e
/proc/1624/task/1624/stack:[<0>] __riscv_sys_ioctl+0x82/0xaa
/proc/1624/task/1624/stack:[<0>] do_trap_ecall_u+0x200/0x212
/proc/1624/task/1624/stack:[<0>] handle_exception+0xde/0xde

FWICT this is inside the "retry_write_wait" loop:
https://github.com/torvalds/linux/blob/67784a74e258a467225f0e68335df77acd67=
b7ab/drivers/tty/tty_ioctl.c#L487

No other process trace has any related tty call pending. When I attached to=
 the
process with strace, it immediately continued and the missing output appear=
ed
on the serial console. /proc/*/task/*/stack and strace log are attached.

The first syscall that strace reports is rt_sigprocmask(SIG_BLOCK, ...), wh=
ich
usually follows ioctl(0, TCSETSW, ...), so it was probably stuck in that io=
ctl.

As it helps to provide more input or attach with strace, it appears like so=
me
wakeup signal is missing or got lost that would notify the wait that the wr=
ite
has completed.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17252927960.DE1AC2F.1576
Date: Mon, 2 Sep 2024 15:59:56 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230062

          Summary
          RISC-V: virtio-console sometimes gets stuck in set_termios.pa=
rt.0

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          RISC-V

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          fvogt@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created =
attachment 877101 [details]
/proc/*/task/*/stack + strace of bash

openQA types in commands to the serial console, sends a newline and then wa=
its
until the prompt appears. Running this in a loop causes it to get stuck
sometimes: https://openqa.opensuse.org/tests/4445068#step/http_srv/16

In the QEMU chardev log it appears like this:

# systemctl --no-pager is-active apache2; echo hjhkw-$?-
active
hjhkw-0-
echo Lorem ipsum dolor sit amet > /srv/www/htdocs/index.html

openQA sends 'systemctl --no-pager is-active apache2; echo hjhkw-$?-\n',
receives 'active\nhjhkw-0-\n', then sends 'echo Lorem ipsum dolor sit amet =
>
/srv/www/htdocs/index.html\n' and waits for '# '. That does not arrive howe=
ver
and the wait times out. In most cases that's just ignored by openQA and it
moves on to the next command. When it sends that ("curl -f ..." h=
ere), the
missing part suddenly appears:

# echo Lorem ipsum dolor sit amet > /srv/www/htdocs/index.html
# curl -f http://localhost/ | grep 'Lorem=
 ipsum dolor sit amet'; echo _Z5Xg-$?-

This issue appears to happen on riscv64 only, I have not observed it anywhe=
re
else so far.

Thankfully the arbitrarily long delay of the prompt allows to debug this. I
created a testcase that exercises the serial terminal in a loop and so far =
it
always gets stuck before the 20th attempt. I logged onto the graphical cons=
ole
and collected some info. The /bin/bash process on the console is stuck in t=
he
kernel:

/proc/1624/task/1624/stack:[<0>] set_termios.part.0+0x130/0x206
/proc/1624/task/1624/stack:[<0>] tty_mode_ioctl+0x46e/0x576
/proc/1624/task/1624/stack:[<0>] n_tty_ioctl_helper+0x2a/0xe4
/proc/1624/task/1624/stack:[<0>] n_tty_ioctl+0x9a/0x148
/proc/1624/task/1624/stack:[<0>] tty_ioctl+0x170/0x64e
/proc/1624/task/1624/stack:[<0>] __riscv_sys_ioctl+0x82/0xaa
/proc/1624/task/1624/stack:[<0>] do_trap_ecall_u+0x200/0x212
/proc/1624/task/1624/stack:[<0>] handle_exception+0xde/0xde

FWICT this is inside the "retry_write_wait" loop:
https://github.com/torvalds/l=
inux/blob/67784a74e258a467225f0e68335df77acd67b7ab/drivers/tty/tty_ioctl.c#=
L487

No other process trace has any related tty call pending. When I attached to=
 the
process with strace, it immediately continued and the missing output appear=
ed
on the serial console. /proc/*/task/*/stack and strace log are attached.

The first syscall that strace reports is rt_sigprocmask(SIG_BLOCK, ...), wh=
ich
usually follows ioctl(0, TCSETSW, ...), so it was probably stuck in that io=
ctl.

As it helps to provide more input or attach with strace, it appears like so=
me
wakeup signal is missing or got lost that would notify the wait that the wr=
ite
has completed.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17252927960.DE1AC2F.1576--


--17253494974.EA9cedd33.614
Date: Tue, 3 Sep 2024 07:44:57 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230083

            Bug ID: 1230083
           Summary: VUL-0: CVE-2024-45305: obs-service-cargo: gix-path: gix-path uses local config across repos when it is the highest scope
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
               URL: https://smash.suse.de/issue/419537/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: pirateclip-at-protonmail.com
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
            Blocks: 1230079
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

+++ This bug was initially created as a clone of Bug #1230079 +++

gix-path is a crate of the gitoxide project dealing with git paths and their
conversions. `gix-path` executes `git` to find the path of a configuration =
file
that belongs to the `git` installation itself, but mistakenly treats the lo=
cal
repository's configuration as system-wide if no higher scoped configuration=
 is
found. In rare cases, this causes a less trusted repository to be treated as
more trusted, or leaks sensitive information from one repository to another,
such as sending credentials to another repository's remote. In `gix_path::e=
nv`,
the underlying implementation of the `installation_config` and
`installation_config_prefix` functions calls `git config -l --show-origin` =
and
parses the first line of the output to extract the path to the configuration
file holding the configuration variable of highest scope. It is believed to=
 be
very difficult to exploit this vulnerability deliberately, due to the need
either to anticipate a situation in which higher-scoped configuration varia=
bles
would be absent, or to arrange for this to happen. Although any operating
system may be affected, users running Apple Git on macOS are much less like=
ly
to be affected. This issue has been addressed in release version 0.10.10. A=
ll
users are advised to upgrade.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45305
https://www.cve.org/CVERecord?id=3DCVE-2024-45305
https://git-scm.com/docs/git-config#SCOPES
https://github.com/Byron/gitoxide/blob/12251eb052df30105538fa831e641eea557f=
13d8/gix-path/src/env/git/mod.rs#L112
https://github.com/Byron/gitoxide/blob/12251eb052df30105538fa831e641eea557f=
13d8/gix-path/src/env/git/mod.rs#L91
https://github.com/Byron/gitoxide/security/advisories/GHSA-v26r-4c9c-h3j6
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17253494974.EA9cedd33.614
Date: Tue, 3 Sep 2024 07:44:57 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230083

          Summary
          VUL-0: CVE-2024-45305: obs-service-cargo: gix-path: gix-path =
uses local config across repos when it is the highest scope

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          URL
          https://smash.suse.de/issue/419537/

          OS
          Other

          Status
          NEW

          Severity
          Minor

          Priority
          P5 - None

          Component
          Security

          Assignee
          pirateclip@protonmail.com

          Reporter
          thomas.leroy@suse.com

          QA Contact
          security-team@suse.de

          Blocks
          1230079

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

+++ This bug was initially created as a clone of Bug #1230079 +++

gix-path is a crate of the gitoxide project dealing with git paths and their
conversions. `gix-path` executes `git` to find the path of a configuration =
file
that belongs to the `git` installation itself, but mistakenly treats the lo=
cal
repository's configuration as system-wide if no higher scoped configuration=
 is
found. In rare cases, this causes a less trusted repository to be treated as
more trusted, or leaks sensitive information from one repository to another,
such as sending credentials to another repository's remote. In `gix_path::e=
nv`,
the underlying implementation of the `installation_config` and
`installation_config_prefix` functions calls `git config -l --show-origin` =
and
parses the first line of the output to extract the path to the configuration
file holding the configuration variable of highest scope. It is believed to=
 be
very difficult to exploit this vulnerability deliberately, due to the need
either to anticipate a situation in which higher-scoped configuration varia=
bles
would be absent, or to arrange for this to happen. Although any operating
system may be affected, users running Apple Git on macOS are much less like=
ly
to be affected. This issue has been addressed in release version 0.10.10. A=
ll
users are advised to upgrade.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45305
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-45305
https://git-scm.com/=
docs/git-config#SCOPES
https://github.com/Byron/=
gitoxide/blob/12251eb052df30105538fa831e641eea557f13d8/gix-path/src/env/git=
/mod.rs#L112
https://github.com/Byron/g=
itoxide/blob/12251eb052df30105538fa831e641eea557f13d8/gix-path/src/env/git/=
mod.rs#L91
https://github.com/Byron/gitoxide/security/advisories/GHSA-v26r-=
4c9c-h3j6

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17253494974.EA9cedd33.614--


--17253496950.FF7Da1b.626
Date: Tue, 3 Sep 2024 07:48:14 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230085

            Bug ID: 1230085
           Summary: VUL-0: CVE-2024-45305: onefetch: gix-path: gix-path uses local config across repos when it is the highest scope
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
               URL: https://smash.suse.de/issue/419537/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: jubalh-at-iodoru.org
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
            Blocks: 1230079
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

+++ This bug was initially created as a clone of Bug #1230079 +++

gix-path is a crate of the gitoxide project dealing with git paths and their
conversions. `gix-path` executes `git` to find the path of a configuration =
file
that belongs to the `git` installation itself, but mistakenly treats the lo=
cal
repository's configuration as system-wide if no higher scoped configuration=
 is
found. In rare cases, this causes a less trusted repository to be treated as
more trusted, or leaks sensitive information from one repository to another,
such as sending credentials to another repository's remote. In `gix_path::e=
nv`,
the underlying implementation of the `installation_config` and
`installation_config_prefix` functions calls `git config -l --show-origin` =
and
parses the first line of the output to extract the path to the configuration
file holding the configuration variable of highest scope. It is believed to=
 be
very difficult to exploit this vulnerability deliberately, due to the need
either to anticipate a situation in which higher-scoped configuration varia=
bles
would be absent, or to arrange for this to happen. Although any operating
system may be affected, users running Apple Git on macOS are much less like=
ly
to be affected. This issue has been addressed in release version 0.10.10. A=
ll
users are advised to upgrade.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45305
https://www.cve.org/CVERecord?id=3DCVE-2024-45305
https://git-scm.com/docs/git-config#SCOPES
https://github.com/Byron/gitoxide/blob/12251eb052df30105538fa831e641eea557f=
13d8/gix-path/src/env/git/mod.rs#L112
https://github.com/Byron/gitoxide/blob/12251eb052df30105538fa831e641eea557f=
13d8/gix-path/src/env/git/mod.rs#L91
https://github.com/Byron/gitoxide/security/advisories/GHSA-v26r-4c9c-h3j6
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17253496950.FF7Da1b.626
Date: Tue, 3 Sep 2024 07:48:15 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230085

          Summary
          VUL-0: CVE-2024-45305: onefetch: gix-path: gix-path uses loca=
l config across repos when it is the highest scope

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          URL
          https://smash.suse.de/issue/419537/

          OS
          Other

          Status
          NEW

          Severity
          Minor

          Priority
          P5 - None

          Component
          Security

          Assignee
          jubalh@iodoru.org

          Reporter
          thomas.leroy@suse.com

          QA Contact
          security-team@suse.de

          Blocks
          1230079

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

+++ This bug was initially created as a clone of Bug #1230079 +++

gix-path is a crate of the gitoxide project dealing with git paths and their
conversions. `gix-path` executes `git` to find the path of a configuration =
file
that belongs to the `git` installation itself, but mistakenly treats the lo=
cal
repository's configuration as system-wide if no higher scoped configuration=
 is
found. In rare cases, this causes a less trusted repository to be treated as
more trusted, or leaks sensitive information from one repository to another,
such as sending credentials to another repository's remote. In `gix_path::e=
nv`,
the underlying implementation of the `installation_config` and
`installation_config_prefix` functions calls `git config -l --show-origin` =
and
parses the first line of the output to extract the path to the configuration
file holding the configuration variable of highest scope. It is believed to=
 be
very difficult to exploit this vulnerability deliberately, due to the need
either to anticipate a situation in which higher-scoped configuration varia=
bles
would be absent, or to arrange for this to happen. Although any operating
system may be affected, users running Apple Git on macOS are much less like=
ly
to be affected. This issue has been addressed in release version 0.10.10. A=
ll
users are advised to upgrade.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45305
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-45305
https://git-scm.com/=
docs/git-config#SCOPES
https://github.com/Byron/=
gitoxide/blob/12251eb052df30105538fa831e641eea557f13d8/gix-path/src/env/git=
/mod.rs#L112
https://github.com/Byron/g=
itoxide/blob/12251eb052df30105538fa831e641eea557f13d8/gix-path/src/env/git/=
mod.rs#L91
https://github.com/Byron/gitoxide/security/advisories/GHSA-v26r-=
4c9c-h3j6

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17253496950.FF7Da1b.626--


--17253499880.a2Bc07d.647
Date: Tue, 3 Sep 2024 07:53:08 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230089

            Bug ID: 1230089
           Summary: VUL-0: CVE-2024-45305: tectonic: gix-path: gix-path uses local config across repos when it is the highest scope
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
               URL: https://smash.suse.de/issue/419537/
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Security
          Assignee: pirateclip-at-protonmail.com
          Reporter: thomas.leroy-at-suse.com
        QA Contact: security-team-at-suse.de
            Blocks: 1230079
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

+++ This bug was initially created as a clone of Bug #1230079 +++

gix-path is a crate of the gitoxide project dealing with git paths and their
conversions. `gix-path` executes `git` to find the path of a configuration =
file
that belongs to the `git` installation itself, but mistakenly treats the lo=
cal
repository's configuration as system-wide if no higher scoped configuration=
 is
found. In rare cases, this causes a less trusted repository to be treated as
more trusted, or leaks sensitive information from one repository to another,
such as sending credentials to another repository's remote. In `gix_path::e=
nv`,
the underlying implementation of the `installation_config` and
`installation_config_prefix` functions calls `git config -l --show-origin` =
and
parses the first line of the output to extract the path to the configuration
file holding the configuration variable of highest scope. It is believed to=
 be
very difficult to exploit this vulnerability deliberately, due to the need
either to anticipate a situation in which higher-scoped configuration varia=
bles
would be absent, or to arrange for this to happen. Although any operating
system may be affected, users running Apple Git on macOS are much less like=
ly
to be affected. This issue has been addressed in release version 0.10.10. A=
ll
users are advised to upgrade.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45305
https://www.cve.org/CVERecord?id=3DCVE-2024-45305
https://git-scm.com/docs/git-config#SCOPES
https://github.com/Byron/gitoxide/blob/12251eb052df30105538fa831e641eea557f=
13d8/gix-path/src/env/git/mod.rs#L112
https://github.com/Byron/gitoxide/blob/12251eb052df30105538fa831e641eea557f=
13d8/gix-path/src/env/git/mod.rs#L91
https://github.com/Byron/gitoxide/security/advisories/GHSA-v26r-4c9c-h3j6
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17253499880.a2Bc07d.647
Date: Tue, 3 Sep 2024 07:53:08 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230089

          Summary
          VUL-0: CVE-2024-45305: tectonic: gix-path: gix-path uses loca=
l config across repos when it is the highest scope

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          URL
          https://smash.suse.de/issue/419537/

          OS
          Other

          Status
          NEW

          Severity
          Minor

          Priority
          P5 - None

          Component
          Security

          Assignee
          pirateclip@protonmail.com

          Reporter
          thomas.leroy@suse.com

          QA Contact
          security-team@suse.de

          Blocks
          1230079

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

+++ This bug was initially created as a clone of Bug #1230079 +++

gix-path is a crate of the gitoxide project dealing with git paths and their
conversions. `gix-path` executes `git` to find the path of a configuration =
file
that belongs to the `git` installation itself, but mistakenly treats the lo=
cal
repository's configuration as system-wide if no higher scoped configuration=
 is
found. In rare cases, this causes a less trusted repository to be treated as
more trusted, or leaks sensitive information from one repository to another,
such as sending credentials to another repository's remote. In `gix_path::e=
nv`,
the underlying implementation of the `installation_config` and
`installation_config_prefix` functions calls `git config -l --show-origin` =
and
parses the first line of the output to extract the path to the configuration
file holding the configuration variable of highest scope. It is believed to=
 be
very difficult to exploit this vulnerability deliberately, due to the need
either to anticipate a situation in which higher-scoped configuration varia=
bles
would be absent, or to arrange for this to happen. Although any operating
system may be affected, users running Apple Git on macOS are much less like=
ly
to be affected. This issue has been addressed in release version 0.10.10. A=
ll
users are advised to upgrade.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-45305
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-45305
https://git-scm.com/=
docs/git-config#SCOPES
https://github.com/Byron/=
gitoxide/blob/12251eb052df30105538fa831e641eea557f13d8/gix-path/src/env/git=
/mod.rs#L112
https://github.com/Byron/g=
itoxide/blob/12251eb052df30105538fa831e641eea557f13d8/gix-path/src/env/git/=
mod.rs#L91
https://github.com/Byron/gitoxide/security/advisories/GHSA-v26r-=
4c9c-h3j6

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17253499880.a2Bc07d.647--


--17253671203.E1c64ea9.77
Date: Tue, 3 Sep 2024 12:38:40 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230101

            Bug ID: 1230101
           Summary: fail2ban no longer finds failed login attempts
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: P.Suetterlin-at-royac.iac.es
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I just noticed that since my latest update of TW to 20240829, fail2ban seems
not to detect any failed login attempts anymore.
systemctl status fail2ban shows it as active (running), but despite journal=
ctl
showing many failed logins, none are detected, no IP gets banned.  All that
happens is that long bans (I run a staged f2b-loop setup with increasing ban
times) get unbanned when their bantime ends.

My config of fail2ban is unchanged, and has been running flawlessly before,=
 the
sshd jail uses the systemd backend

The update brought systemd 256.5.  Also, for me this was the first time tha=
t I
used a 6.10 kernel (I use an NVIDIA card), so maybe this is related?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17253671203.E1c64ea9.77
Date: Tue, 3 Sep 2024 12:38:40 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230101

          Summary
          fail2ban no longer finds failed login attempts

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          P.Suetterlin@royac.iac.es

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I just noticed that since my latest update of TW to 20240829=
, fail2ban seems
not to detect any failed login attempts anymore.
systemctl status fail2ban shows it as active (running), but despite journal=
ctl
showing many failed logins, none are detected, no IP gets banned.  All that
happens is that long bans (I run a staged f2b-loop setup with increasing ban
times) get unbanned when their bantime ends.

My config of fail2ban is unchanged, and has been running flawlessly before,=
 the
sshd jail uses the systemd backend

The update brought systemd 256.5.  Also, for me this was the first time tha=
t I
used a 6.10 kernel (I use an NVIDIA card), so maybe this is related?

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17253671203.E1c64ea9.77--


--17254458205.f7Ce38A8F.1259
Date: Wed, 4 Sep 2024 10:30:20 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230132

            Bug ID: 1230132
           Summary: Intermittent sound Legion Pro 7 16IRX8H (Intel CPU)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: vjacheslav.sorokin-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 877129
  --> https://bugzilla.suse.com/attachment.cgi?id=3D877129&action=3Dedit
Information is gathered shortly after my laptops booted.

Shortly after my laptop boots, I can turn on music or video, e.g., youtube
video, and sound is there while video or audio file is playing. When I turn=
 the
playback off, sound disappears and restart is required to have it back. If =
I'm
launching a VM via VirtualBox and turn on video / audio file in VM, then so=
und
is there till the VM is turned off.=20
Attaching alsa-info.sh-s with the sound working (alsa_booted.txt,
alsa_booted_playing_sound.txt) and sound disappeared
(alsa_booted_no_sound.txt).

I'm aware of 1226449 Bug ID, but mine laptop has Intel CPU, not AMD, that's=
 why
I'm reporting this bug.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17254458205.f7Ce38A8F.1259
Date: Wed, 4 Sep 2024 10:30:20 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230132

          Summary
          Intermittent sound Legion Pro 7 16IRX8H (Intel CPU)

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Sound

          Assignee
          tiwai@suse.com

          Reporter
          vjacheslav.sorokin@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 877129 [details]
Information is gathered shortly after my laptops booted.

Shortly after my laptop boots, I can turn on music or video, e.g., youtube
video, and sound is there while video or audio file is playing. When I turn=
 the
playback off, sound disappears and restart is required to have it back. If =
I'm
launching a VM via VirtualBox and turn on video / audio file in VM, then so=
und
is there till the VM is turned off.=20
Attaching alsa-info.sh-s with the sound working (alsa_booted.txt,
alsa_booted_playing_sound.txt) and sound disappeared
(alsa_booted_no_sound.txt).

I'm aware of 1226449 Bug ID, but mine laptop has Intel CPU, not AMD, that's=
 why
I'm reporting this bug.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17254458205.f7Ce38A8F.1259--


--17254510790.23Ef05.2738
Date: Wed, 4 Sep 2024 11:57:59 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230134

            Bug ID: 1230134
           Summary: SELinux enhancements for btrfs-soft-reboot-generator needed
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

btrfs-soft-reboot-generator is a systemd-generator which generates snippets=
 for
a list of services, which should survive a soft-reboot (see
https://github.com/thkukuk/survive-soft-reboot/).=20
Since we cannot run the service from the root filesystem (will be exchanged
during soft-reboot on MicroOS/SL Micro), we start the services from a btrfs
subvolume. For this reasons the generator needs to find out the root device=
 and
the subvolid of the current root btrfs subvolume to create the correct
RootImage=3D entry.=20
SELinux prevents this:
Sep 04 11:50:23 node122 kernel: audit: type=3D1400 audit(1725450623.374:197=
):
avc:  denied  { search } for  pid=3D2110 comm=3D"btrfs-soft-rebo" name=3D"m=
ount"
dev=3D"tmpfs" ino=3D788 scontext=3Dsystem_u:system_r:systemd_generic_genera=
tor_t:s0
tcontext=3Dsystem_u:object_r:mount_var_run_t:s0 tclass=3Ddir permissive=3D1
Sep 04 11:50:23 node122 kernel: audit: type=3D1400 audit(1725450623.378:198=
):
avc:  denied  { getattr } for  pid=3D2110 comm=3D"btrfs-soft-rebo"
path=3D"/run/mount/utab" dev=3D"tmpfs" ino=3D2486
scontext=3Dsystem_u:system_r:systemd_generic_generator_t:s0
tcontext=3Dsystem_u:object_r:mount_var_run_t:s0 tclass=3Dfile permissive=3D1
Sep 04 11:50:23 node122 kernel: audit: type=3D1400 audit(1725450623.378:199=
):
avc:  denied  { read } for  pid=3D2110 comm=3D"btrfs-soft-rebo" name=3D"uta=
b"
dev=3D"tmpfs" ino=3D2486 scontext=3Dsystem_u:system_r:systemd_generic_gener=
ator_t:s0
tcontext=3Dsystem_u:object_r:mount_var_run_t:s0 tclass=3Dfile permissive=3D1
Sep 04 11:50:23 node122 kernel: audit: type=3D1400 audit(1725450623.378:200=
):
avc:  denied  { open } for  pid=3D2110 comm=3D"btrfs-soft-rebo"
path=3D"/run/mount/utab" dev=3D"tmpfs" ino=3D2486
scontext=3Dsystem_u:system_r:systemd_generic_generator_t:s0
tcontext=3Dsystem_u:object_r:mount_var_run_t:s0 tclass=3Dfile permissive=3D1
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17254510790.23Ef05.2738
Date: Wed, 4 Sep 2024 11:57:59 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230134

          Summary
          SELinux enhancements for btrfs-soft-reboot-generator needed

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          kukuk@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

btrfs-soft-reboot-generator is a systemd-generator which gen=
erates snippets for
a list of services, which should survive a soft-reboot (see
https://github.=
com/thkukuk/survive-soft-reboot/).=20
Since we cannot run the service from the root filesystem (will be exchanged
during soft-reboot on MicroOS/SL Micro), we start the services from a btrfs
subvolume. For this reasons the generator needs to find out the root device=
 and
the subvolid of the current root btrfs subvolume to create the correct
RootImage=3D entry.=20
SELinux prevents this:
Sep 04 11:50:23 node122 kernel: audit: type=3D1400 audit(1725450623.374:197=
):
avc:  denied  { search } for  pid=3D2110 comm=3D"btrfs-soft-rebo"=
 name=3D"mount"
dev=3D"tmpfs" ino=3D788 scontext=3Dsystem_u:system_r:systemd_gene=
ric_generator_t:s0
tcontext=3Dsystem_u:object_r:mount_var_run_t:s0 tclass=3Ddir permissive=3D1
Sep 04 11:50:23 node122 kernel: audit: type=3D1400 audit(1725450623.378:198=
):
avc:  denied  { getattr } for  pid=3D2110 comm=3D"btrfs-soft-rebo"
path=3D"/run/mount/utab" dev=3D"tmpfs" ino=3D2486
scontext=3Dsystem_u:system_r:systemd_generic_generator_t:s0
tcontext=3Dsystem_u:object_r:mount_var_run_t:s0 tclass=3Dfile permissive=3D1
Sep 04 11:50:23 node122 kernel: audit: type=3D1400 audit(1725450623.378:199=
):
avc:  denied  { read } for  pid=3D2110 comm=3D"btrfs-soft-rebo" n=
ame=3D"utab"
dev=3D"tmpfs" ino=3D2486 scontext=3Dsystem_u:system_r:systemd_gen=
eric_generator_t:s0
tcontext=3Dsystem_u:object_r:mount_var_run_t:s0 tclass=3Dfile permissive=3D1
Sep 04 11:50:23 node122 kernel: audit: type=3D1400 audit(1725450623.378:200=
):
avc:  denied  { open } for  pid=3D2110 comm=3D"btrfs-soft-rebo"
path=3D"/run/mount/utab" dev=3D"tmpfs" ino=3D2486
scontext=3Dsystem_u:system_r:systemd_generic_generator_t:s0
tcontext=3Dsystem_u:object_r:mount_var_run_t:s0 tclass=3Dfile permissive=3D=
1

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17254510790.23Ef05.2738--


--17256104590.1cf7.4165
Date: Fri, 6 Sep 2024 08:14:19 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230262

            Bug ID: 1230262
           Summary: GCC14 internal compiler error: Segmentation fault during LTO
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 877165
  --> https://bugzilla.suse.com/attachment.cgi?id=3D877165&action=3Dedit
openvino log

GCC14 internal compiler error: Segmentation fault during LTO.

This happen on openvino, for example.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17256104590.1cf7.4165
Date: Fri, 6 Sep 2024 08:14:19 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230262

          Summary
          GCC14 internal compiler error: Segmentation fault during LTO

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          aarch64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Development

          Assignee
          screening-team-bugs@suse.de

          Reporter
          guillaume.gardet@arm.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 877165 [details]
openvino log

GCC14 internal compiler error: Segmentation fault during LTO.

This happen on openvino, for example.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17256104590.1cf7.4165--


--17256443461.69D3Ed.7812
Date: Fri, 6 Sep 2024 17:39:06 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230287

            Bug ID: 1230287
           Summary: Package xindy needs rebuild after clisp update
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mikko-at-syrja.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

After recent clisp 2.49.93-1.1 update, xindy fails with following error
message:

/usr/lib64/clisp-2.49.93+/base/lisp.run: initialization file
`/usr/lib64/xindy/xindy.mem' was not created by this version of CLISP runti=
me

Simple rebuild is probably enough.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17256443461.69D3Ed.7812
Date: Fri, 6 Sep 2024 17:39:06 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230287

          Summary
          Package xindy needs rebuild after clisp update

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          mikko@syrja.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

After recent clisp 2.49.93-1.1 update, xindy fails with foll=
owing error
message:

/usr/lib64/clisp-2.49.93+/base/lisp.run: initialization file
`/usr/lib64/xindy/xindy.mem' was not created by this version of CLISP runti=
me

Simple rebuild is probably enough.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17256443461.69D3Ed.7812--


--17257327512.756fFDE8.316
Date: Sat, 7 Sep 2024 18:12:31 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230298

            Bug ID: 1230298
           Summary: XFig: upstream has an important (at lest for me) bug-fix, please sync
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: giacomo.boffi-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

XFig on Tumbleweed has a bug concerning dimension lines, if a user opts for
user defined text in dimension lines XFig mistakenly uses most negatives and
positive numbers as the line extremes, leading to failures when exporting to
other formats.

This bug has been fixed upstream, I'd like that you build and upload a new =
XFig
package that reflects the upstream bug fix.

Thank you =E1=8D=A8 gb
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17257327512.756fFDE8.316
Date: Sat, 7 Sep 2024 18:12:31 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230298

          Summary
          XFig: upstream has an important (at lest for me) bug-fix, ple=
ase sync

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X11 Applications

          Assignee
          screening-team-bugs@suse.de

          Reporter
          giacomo.boffi@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

XFig on Tumbleweed has a bug concerning dimension lines, if =
a user opts for
user defined text in dimension lines XFig mistakenly uses most negatives and
positive numbers as the line extremes, leading to failures when exporting to
other formats.

This bug has been fixed upstream, I'd like that you build and upload a new =
XFig
package that reflects the upstream bug fix.

Thank you =E1=8D=A8 gb

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17257327512.756fFDE8.316--


--17258924551.DEbBABdbf.65
Date: Mon, 9 Sep 2024 14:34:15 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

https://bugzilla.suse.com/show_bug.cgi?id=3D1230333

            Bug ID: 1230333
           Summary: docker-buildx: move to be a subpackage of Docker
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Containers
          Assignee: containers-bugowner-at-suse.de
          Reporter: asarai-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

docker-buildx is a component of Docker, it makes very little sense to maint=
ain
it as a separate package (especially since docker-stable will probably mean=
 we
need to maintain a docker-stable-buildx fork anyway). It's simplest to just
maintain it as a subpackage.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17258924551.DEbBABdbf.65
Date: Mon, 9 Sep 2024 14:34:15 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

      <base href=3D"https://bugzilla.suse.com/" />

          Bug ID
          1230333

          Summary
          docker-buildx: move to be a subpackage of Docker

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Containers

          Assignee
          containers-bugowner@suse.de

          Reporter
          asarai@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

docker-buildx is a component of Docker, it makes very little=
 sense to maintain
it as a separate package (especially since docker-stable will probably mean=
 we
need to maintain a docker-stable-buildx fork anyway). It's simplest to just
maintain it as a subpackage.

      You are receiving this mail because:
=20=20=20=20=20=20

You are on the CC list for the bug.

=

--17258924551.DEbBABdbf.65--