body:
--16987506512.5Bfed.9970
Date: Tue, 31 Oct 2023 11:10:51 +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=3D1216740

            Bug ID: 1216740
           Summary: nfs-client: move config to /usr
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: nfbrown-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

nfs-client ships several (sample) config files in /etc. Those should be rem=
oved
nowadays. Just package the samples as %doc. The relevant ones should be shi=
pped
in /usr (e.g /usr/etc) instead. Bonus points for also supporting drop-ins.

See also tracker bug 1208319
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16987506512.5Bfed.9970
Date: Tue, 31 Oct 2023 11:10:51 +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
          1216740

          Summary
          nfs-client: move config to /usr

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          nfbrown@suse.com

          Reporter
          lnussel@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

nfs-client ships several (sample) config files in /etc. Thos=
e should be removed
nowadays. Just package the samples as %doc. The relevant ones should be shi=
pped
in /usr (e.g /usr/etc) instead. Bonus points for also supporting drop-ins.

See also tracker bug 1208319

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

You are on the CC list for the bug.

=

--16987506512.5Bfed.9970--

summary: nfs-client: move config to /usr


--16988286631.6b92d.11376
Date: Wed, 1 Nov 2023 08:51:03 +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=3D1216778

            Bug ID: 1216778
           Summary: Unable to read the text of emails in Evolution
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: x86-64
                OS: openSUSE Leap 15.5
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: alan-at-downinglewis.plus.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

>From today, 1st November, I cannot see any text when opening an email in
Evolution - the screen is completely blank.  There was a problem recently w=
ith
reading messages in Evolution due to an issue with WebKitGTK - Bug 1213858.

I checked /var/log/zypp/history to see what was installed yesterday.  I fou=
nd
the following entries:

2023-10-31
13:34:58|install|libwebkit2gtk-4_0-37|2.42.1-150400.4.57.2|x86_64||repo-sle=
-update|fec686b7d3025267b020cdec51d4dc12c65840db7572dff958d0ec93e1138618|
2023-10-31
13:34:59|install|webkit2gtk-4_0-injected-bundles|2.42.1-150400.4.57.2|x86_6=
4||repo-sle-update|c6e7c7f15f460b2799afcc8a65ec1dd055c56af19ce127972a960f37=
f3a98e09|
2023-10-31
13:35:01|install|WebKitGTK-4.0-lang|2.42.1-150400.4.57.2|noarch||repo-sle-u=
pdate|b68968a6fbeeb3ae3b472813a0c529576b7f72c8417eae46a6e22e574d28a086|

I have not had time to investigate further at the moment.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16988286631.6b92d.11376
Date: Wed, 1 Nov 2023 08:51:03 +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
          1216778

          Summary
          Unable to read the text of emails in Evolution

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          x86-64

          OS
          openSUSE Leap 15.5

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          alan@downinglewis.plus.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

From today, 1st November, I cannot see any text when opening=
 an email in
Evolution - the screen is completely blank.  There was a problem recently w=
ith
reading messages in Evolution due to an issue with WebKitGTK - Bug 1213858.

I checked /var/log/zypp/history to see what was installed yesterday.  I fou=
nd
the following entries:

2023-10-31
13:34:58|install|libwebkit2gtk-4_0-37|2.42.1-150400.4.57.2|x86_64||repo-sle=
-update|fec686b7d3025267b020cdec51d4dc12c65840db7572dff958d0ec93e1138618|
2023-10-31
13:34:59|install|webkit2gtk-4_0-injected-bundles|2.42.1-150400.4.57.2|x86_6=
4||repo-sle-update|c6e7c7f15f460b2799afcc8a65ec1dd055c56af19ce127972a960f37=
f3a98e09|
2023-10-31
13:35:01|install|WebKitGTK-4.0-lang|2.42.1-150400.4.57.2|noarch||repo-sle-u=
pdate|b68968a6fbeeb3ae3b472813a0c529576b7f72c8417eae46a6e22e574d28a086|

I have not had time to investigate further at the moment.

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

You are on the CC list for the bug.

=

--16988286631.6b92d.11376--


--16988329253.60C56d4.11469
Date: Wed, 1 Nov 2023 10:02:05 +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=3D1216783

            Bug ID: 1216783
           Summary: VUL-0: chromium: multiple security issues fixed in version 119.0.6045.105
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/383769/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: gmbr3-at-opensuse.org
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: stoyan.manolov-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

This update includes 15 security fixes. Below, we highlight fixes that were
contributed by external researchers. Please see the Chrome Security Page for
more information.

[$16000][1492698] High CVE-2023-5480: Inappropriate implementation in Payme=
nts.
Reported by Vsevolod Kokorin (Slonser) of Solidlab on 2023-10-14

[$11000][1492381] High CVE-2023-5482: Insufficient data validation in USB.
Reported by DarkNavy on 2023-10-13

[$TBD][1492384] High CVE-2023-5849: Integer overflow in USB. Reported by
DarkNavy on 2023-10-13

[$3000][1281972] Medium CVE-2023-5850: Incorrect security UI in Downloads.
Reported by Mohit Raj (shadow2639)  on 2021-12-22

[$3000][1473957] Medium CVE-2023-5851: Inappropriate implementation in
Downloads. Reported by Shaheen Fazim on 2023-08-18

[$2000][1480852] Medium CVE-2023-5852: Use after free in Printing. Reported=
 by
[pwn2car] on 2023-09-10

[$1000][1456876] Medium CVE-2023-5853: Incorrect security UI in Downloads.
Reported by Hafiizh on 2023-06-22

[$1000][1488267] Medium CVE-2023-5854: Use after free in Profiles. Reported=
 by
Dohyun Lee (@l33d0hyun) of SSD-Disclosure Labs & DNSLab, Korea Univ on
2023-10-01

[$TBD][1492396] Medium CVE-2023-5855: Use after free in Reading Mode. Repor=
ted
by ChaobinZhang on 2023-10-13

[$TBD][1493380] Medium CVE-2023-5856: Use after free in Side Panel. Reporte=
d by
Weipeng Jiang (@Krace) of VRI on 2023-10-17

[N/A][1493435] Medium CVE-2023-5857: Inappropriate implementation in Downlo=
ads.
Reported by Will Dormann on 2023-10-18

[$3000][1457704] Low CVE-2023-5858: Inappropriate implementation in WebApp
Provider. Reported by Axel Chong on 2023-06-24

[$500][1482045] Low CVE-2023-5859: Incorrect security UI in Picture In Pict=
ure.
Reported by Junsung Lee on 2023-09-13

We would also like to thank all security researchers that worked with us du=
ring
the development cycle to prevent security bugs from ever reaching the stable
channel.

References:
https://sites.google.com/a/chromium.org/dev/Home/chromium-security
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16988329253.60C56d4.11469
Date: Wed, 1 Nov 2023 10:02:05 +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
          1216783

          Summary
          VUL-0: chromium: multiple security issues fixed in version 11=
9.0.6045.105

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          gmbr3@opensuse.org

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          stoyan.manolov@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

This update includes 15 security fixes. Below, we highlight =
fixes that were
contributed by external researchers. Please see the Chrome Security Page for
more information.

[$16000][1492698] High CVE-2023-5480: Inappropriate implementation in Payme=
nts.
Reported by Vsevolod Kokorin (Slonser) of Solidlab on 2023-10-14

[$11000][1492381] High CVE-2023-5482: Insufficient data validation in USB.
Reported by DarkNavy on 2023-10-13

[$TBD][1492384] High CVE-2023-5849: Integer overflow in USB. Reported by
DarkNavy on 2023-10-13

[$3000][1281972] Medium CVE-2023-5850: Incorrect security UI in Downloads.
Reported by Mohit Raj (shadow2639)  on 2021-12-22

[$3000][1473957] Medium CVE-2023-5851: Inappropriate implementation in
Downloads. Reported by Shaheen Fazim on 2023-08-18

[$2000][1480852] Medium CVE-2023-5852: Use after free in Printing. Reported=
 by
[pwn2car] on 2023-09-10

[$1000][1456876] Medium CVE-2023-5853: Incorrect security UI in Downloads.
Reported by Hafiizh on 2023-06-22

[$1000][1488267] Medium CVE-2023-5854: Use after free in Profiles. Reported=
 by
Dohyun Lee (@l33d0hyun) of SSD-Disclosure Labs & DNSLab, Korea Univ=
 on
2023-10-01

[$TBD][1492396] Medium CVE-2023-5855: Use after free in Reading Mode. Repor=
ted
by ChaobinZhang on 2023-10-13

[$TBD][1493380] Medium CVE-2023-5856: Use after free in Side Panel. Reporte=
d by
Weipeng Jiang (@Krace) of VRI on 2023-10-17

[N/A][1493435] Medium CVE-2023-5857: Inappropriate implementation in Downlo=
ads.
Reported by Will Dormann on 2023-10-18

[$3000][1457704] Low CVE-2023-5858: Inappropriate implementation in WebApp
Provider. Reported by Axel Chong on 2023-06-24

[$500][1482045] Low CVE-2023-5859: Incorrect security UI in Picture In Pict=
ure.
Reported by Junsung Lee on 2023-09-13

We would also like to thank all security researchers that worked with us du=
ring
the development cycle to prevent security bugs from ever reaching the stable
channel.

References:
https://sites.google.com/a/chromium.org/dev/Home/chromium-security<=
/pre>

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

You are on the CC list for the bug.

=

--16988329253.60C56d4.11469--


body:
--16988475943.dB79C88Cb.11880
Date: Wed, 1 Nov 2023 14:06: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=3D1216790

            Bug ID: 1216790
           Summary: Enable zstd and parallel compression in libdar
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: psychonaut-at-nothingisreal.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Since version 2.7.0, dar has supported parallel encryption and compression =
with
its -G command-line option, as well as zstd compression using the
--compression=3Dzstd command-line option.

However, the version of (lib)dar packaged by openSUSE Tumbleweed has these =
two
features disabled:

$ dar --version

 dar version 2.7.12, Copyright (C) 2002-2023 Denis Corbin
   Long options support         : YES

 Using libdar 6.7.0 built with compilation time options:
   gzip compression (libz)      : YES
   bzip2 compression (libbzip2) : YES
   lzo compression (liblzo2)    : YES
   xz compression (liblzma)     : YES
   zstd compression (libzstd)   : NO
   lz4 compression (liblz4)     : NO
   [...]
   Multiple threads (libthreads): NO=20

Have these two features been disabled intentionally?  If not, could the pac=
kage
please be updated so that these two features are enabled?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16988475943.dB79C88Cb.11880
Date: Wed, 1 Nov 2023 14:06: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
          1216790

          Summary
          Enable zstd and parallel compression in libdar

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Enhancement

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          psychonaut@nothingisreal.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Since version 2.7.0, dar has supported parallel encryption a=
nd compression with
its -G command-line option, as well as zstd compression using the
--compression=3Dzstd command-line option.

However, the version of (lib)dar packaged by openSUSE Tumbleweed has these =
two
features disabled:

$ dar --version

 dar version 2.7.12, Copyright (C) 2002-2023 Denis Corbin
   Long options support         : YES

 Using libdar 6.7.0 built with compilation time options:
   gzip compression (libz)      : YES
   bzip2 compression (libbzip2) : YES
   lzo compression (liblzo2)    : YES
   xz compression (liblzma)     : YES
   zstd compression (libzstd)   : NO
   lz4 compression (liblz4)     : NO
   [...]
   Multiple threads (libthreads): NO=20

Have these two features been disabled intentionally?  If not, could the pac=
kage
please be updated so that these two features are enabled?

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

You are on the CC list for the bug.

=

--16988475943.dB79C88Cb.11880--

pkgs: dar libthreadar


body:
--16989131768.85B37.12599
Date: Thu, 2 Nov 2023 08:19: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=3D1216806

            Bug ID: 1216806
           Summary: [aarch64][LenovoX13s] [power supply] Battery precentage is alawys 0%
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: chester.lin-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: afaerber-at-suse.com, guillaume.gardet-at-arm.com,
                    ivan.ivanov-at-suse.com, jlee-at-suse.com, mbenes-at-suse.com,
                    mbrugger-at-suse.com, stanimir.varbanov-at-suse.com,
                    tiwai-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 870581
  --> https://bugzilla.suse.com/attachment.cgi?id=3D870581&action=3Dedit
battery_fail.png

Tested ISO: openSUSE-Tumbleweed-DVD-aarch64-Snapshot20231029-Media.iso
Link:
https://download.opensuse.org/ports/aarch64/tumbleweed/iso/openSUSE-Tumblew=
eed-DVD-aarch64-Current.iso

Install steps: https://en.opensuse.org/HCL:ThinkpadX13s#ISO_Installation

Symptom:
When booting to the installed tumbleweed, the battery percentage is not abl=
e to
be measured so it always shows 0% (See attached screenshot). In the meanwhi=
le,
the readings dumped by the 'upower' command are all zero.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16989131768.85B37.12599
Date: Thu, 2 Nov 2023 08:19: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
          1216806

          Summary
          [aarch64][LenovoX13s] [power supply] Battery precentage is al=
awys 0%

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          aarch64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          chester.lin@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          afaerber@suse.com, guillaume.gardet@arm.com, ivan.iva=
nov@suse.com, jlee@suse.com, mbenes@suse.com, mbrugger@suse=
.com, stanimir.varbanov@suse.com, tiwai@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 870581=
 [details]
battery_fail.png

Tested ISO: openSUSE-Tumbleweed-DVD-aarch64-Snapshot20231029-Media.iso
Link:
https://download.opensuse.org/ports=
/aarch64/tumbleweed/iso/openSUSE-Tumbleweed-DVD-aarch64-Current.iso

Install steps: https://en.opensuse.org/HCL:ThinkpadX13s#ISO_Installation

Symptom:
When booting to the installed tumbleweed, the battery percentage is not abl=
e to
be measured so it always shows 0% (See attached screenshot). In the meanwhi=
le,
the readings dumped by the 'upower' command are all zero.

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

You are on the CC list for the bug.

=

--16989131768.85B37.12599--

pkgs: pd-mapper qrtr


--16989327863.9fee8.13241
Date: Thu, 2 Nov 2023 13:46:26 +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=3D1216822

            Bug ID: 1216822
           Summary: Remove dhclient-script frin dhcp-client package
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: petr.vorel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

According to the comments in dhclient-script [1] we ship, the script is not
used neither by NetworkManager nor wicked:

# Note:
#   It is used by sysconfig alias netcontrol alias ifup-dhcp,
#   but not by the NetworkManager that is using an own script.
#
#   Wicked is using an another dhcp client (runtime conflict).
#   As sysconfig-network is gone on sles12 and opensuse > 13.1,
#   this script is obsolete and unsupported.

[1]
https://build.opensuse.org/package/view_file/network:dhcp/dhcp/dhclient-scr=
ipt?expand=3D1

Also, it requires usleep from deprecated sysvinit-tools, which is not
addressed.

Both of these were pointed out by #1216814. Therefore suggesting to remove =
the
script from the package instead.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16989327863.9fee8.13241
Date: Thu, 2 Nov 2023 13:46:26 +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
          1216822

          Summary
          Remove dhclient-script frin dhcp-client package

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Network

          Assignee
          screening-team-bugs@suse.de

          Reporter
          petr.vorel@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

According to the comments in dhclient-script [1] we ship, th=
e script is not
used neither by NetworkManager nor wicked:

# Note:
#   It is used by sysconfig alias netcontrol alias ifup-dhcp,
#   but not by the NetworkManager that is using an own script.
#
#   Wicked is using an another dhcp client (runtime conflict).
#   As sysconfig-network is gone on sles12 and opensuse > 13.1,
#   this script is obsolete and unsupported.

[1]
https://build.opensuse.org/package/view_file/net=
work:dhcp/dhcp/dhclient-script?expand=3D1

Also, it requires usleep from deprecated sysvinit-tools, which is not
addressed.

Both of these were pointed out by #1216814. Therefore suggesting to remove =
the
script from the package instead.

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

You are on the CC list for the bug.

=

--16989327863.9fee8.13241--


body:
--16989389591.E81F6AAcC.13513
Date: Thu, 2 Nov 2023 15:29: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=3D1216830

            Bug ID: 1216830
           Summary: rpamd: crashes on start on aarch64
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bwiedemann-at-suse.com
          Reporter: amajer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: asn-at-cryptomilk.org, wolfgang-at-rosenauer.org
  Target Milestone: ---
          Found By: ---
           Blocker: ---

this basically runs `rspamd -f` with default config.

It's using latest Tumbleweed container image and running on Leap Micro on
aarch64 with `zypper in rspamd`. Works fine on x86_64.

# podman run -it --rm localhost/rspamd:latest
2023-11-02 15:21:52 #1(main) <957c11>; main; main: rspamd 3.7.3 is loading
configuration, build id: release
(main) lua; lua_cfg_transform.lua:173: group excessb64 has no symbols*** st=
ack
smashing detected ***: terminated
Stack trace (most recent call last):
#24   Object "[0xffffffffffffffff]", at 0xffffffffffffffff, in=20
#23   Object "/usr/bin/rspamd", at 0xaaaacffad76f, in=20
#22   Object "/lib64/libc.so.6", at 0xffffb06cb61f, in __libc_start_main
#21   Object "/lib64/libc.so.6", at 0xffffb06cb54b, in=20
#20   Object "/usr/bin/rspamd", at 0xaaaacffacb2b, in=20
#19   Object "/usr/bin/rspamd", at 0xaaaacffc103b, in=20
#18   Object "/lib64/librspamd-server.so", at 0xffffb0e3c5bf, in
rspamd_config_read
#17   Object "/lib64/librspamd-server.so", at 0xffffb0e35107, in
rspamd_rcl_maybe_apply_lua_transform
#16   Object "/lib64/liblua5.4.so.5", at 0xffffb0c9431f, in lua_pcallk
#15   Object "/lib64/liblua5.4.so.5", at 0xffffb0cb2697, in=20
#14   Object "/lib64/liblua5.4.so.5", at 0xffffb0c8e107, in=20
#13   Object "/lib64/liblua5.4.so.5", at 0xffffb0c941f3, in=20
#12   Object "/lib64/liblua5.4.so.5", at 0xffffb0ca0d1b, in=20
#11   Object "/lib64/liblua5.4.so.5", at 0xffffb0c93713, in=20
#10   Object "/lib64/librspamd-server.so", at 0xffffb0fe0863, in=20
#9    Object "/lib64/librspamd-server.so", at 0xffffb0f23553, in=20
#8    Object "/lib64/librspamd-server.so", at 0xffffb0e8c74b, in
rspamd_common_log_function
#7    Object "/lib64/librspamd-server.so", at 0xffffb0e8c553, in
rspamd_common_logv
#6    Object "/lib64/librspamd-server.so", at 0xffffb0e8f93b, in
rspamd_log_console_log
#5    Object "/lib64/libc.so.6", at 0xffffb07a77b7, in __stack_chk_fail
#4    Object "/lib64/libc.so.6", at 0xffffb07a676f, in __fortify_fail
#3    Object "/lib64/libc.so.6", at 0xffffb071e84b, in=20
#2    Object "/lib64/libc.so.6", at 0xffffb06cae07, in abort
#1    Object "/lib64/libc.so.6", at 0xffffb06dfbff, in raise
#0    Object "/lib64/libc.so.6", at 0xffffb072b430, in=20
Aborted (Signal sent by tkill() 1 498)
watf? exit

could be related to this,
https://github.com/rspamd/rspamd/issues/3849
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16989389591.E81F6AAcC.13513
Date: Thu, 2 Nov 2023 15:29: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
          1216830

          Summary
          rpamd: crashes on start on aarch64

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          bwiedemann@suse.com

          Reporter
          amajer@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          asn@cryptomilk.org, wolfgang@rosenauer.org

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

this basically runs `rspamd -f` with default config.

It's using latest Tumbleweed container image and running on Leap Micro on
aarch64 with `zypper in rspamd`. Works fine on x86_64.

# podman run -it --rm localhost/rspamd:latest
2023-11-02 15:21:52 #1(main) <957c11>; main; main: rspamd 3.7.3 is lo=
ading
configuration, build id: release
(main) lua; lua_cfg_transform.lua:173: group excessb64 has no symbols*** st=
ack
smashing detected ***: terminated
Stack trace (most recent call last):
#24   Object "[0xffffffffffffffff]", at 0xffffffffffffffff, in=20
#23   Object "/usr/bin/rspamd", at 0xaaaacffad76f, in=20
#22   Object "/lib64/libc.so.6", at 0xffffb06cb61f, in __libc_sta=
rt_main
#21   Object "/lib64/libc.so.6", at 0xffffb06cb54b, in=20
#20   Object "/usr/bin/rspamd", at 0xaaaacffacb2b, in=20
#19   Object "/usr/bin/rspamd", at 0xaaaacffc103b, in=20
#18   Object "/lib64/librspamd-server.so", at 0xffffb0e3c5bf, in
rspamd_config_read
#17   Object "/lib64/librspamd-server.so", at 0xffffb0e35107, in
rspamd_rcl_maybe_apply_lua_transform
#16   Object "/lib64/liblua5.4.so.5", at 0xffffb0c9431f, in lua_p=
callk
#15   Object "/lib64/liblua5.4.so.5", at 0xffffb0cb2697, in=20
#14   Object "/lib64/liblua5.4.so.5", at 0xffffb0c8e107, in=20
#13   Object "/lib64/liblua5.4.so.5", at 0xffffb0c941f3, in=20
#12   Object "/lib64/liblua5.4.so.5", at 0xffffb0ca0d1b, in=20
#11   Object "/lib64/liblua5.4.so.5", at 0xffffb0c93713, in=20
#10   Object "/lib64/librspamd-server.so", at 0xffffb0fe0863, in=
=20
#9    Object "/lib64/librspamd-server.so", at 0xffffb0f23553, in=
=20
#8    Object "/lib64/librspamd-server.so", at 0xffffb0e8c74b, in
rspamd_common_log_function
#7    Object "/lib64/librspamd-server.so", at 0xffffb0e8c553, in
rspamd_common_logv
#6    Object "/lib64/librspamd-server.so", at 0xffffb0e8f93b, in
rspamd_log_console_log
#5    Object "/lib64/libc.so.6", at 0xffffb07a77b7, in __stack_ch=
k_fail
#4    Object "/lib64/libc.so.6", at 0xffffb07a676f, in __fortify_=
fail
#3    Object "/lib64/libc.so.6", at 0xffffb071e84b, in=20
#2    Object "/lib64/libc.so.6", at 0xffffb06cae07, in abort
#1    Object "/lib64/libc.so.6", at 0xffffb06dfbff, in raise
#0    Object "/lib64/libc.so.6", at 0xffffb072b430, in=20
Aborted (Signal sent by tkill() 1 498)
watf? exit

could be related to this,
https://github.com=
/rspamd/rspamd/issues/3849

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

You are on the CC list for the bug.

=

--16989389591.E81F6AAcC.13513--

summary: rpamd: crashes on start on aarch64


--16990247602.Ee47b1fb.15159
Date: Fri, 3 Nov 2023 15:19: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=3D1216865

            Bug ID: 1216865
           Summary: Upgrade moves /etc/sssd/sssd.conf to /etc/sssd/sssd.conf.rpmsave
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: georg.pfuetzenreuter-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Hi,

upon upgrading `openSUSE Tumbleweed 20231031-0 -> 20231101-0` which contain=
ed
an update of `sssd`, the configuration file was moved to .rpmsave:

```
warning: /etc/sssd/sssd.conf saved as /etc/sssd/sssd.conf.rpmsave
```

I presume this is part of the /usr/etc merge effort, however my sssd.conf f=
ile
contained custom options configuring my LDAP backend - the file being (re)m=
oved
breaks LDAP login after the upgrade.

Furthermore, `sssd` refuses to start completely after the upgrade:

```
# systemctl status sssd
=E2=97=8B sssd.service - System Security Services Daemon
     Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; preset:
disabled)
     Active: inactive (dead)
  Condition: start condition unmet at Fri 2023-11-03 15:13:24 UTC; 879ms ago
             =E2=94=9C=E2=94=80 ConditionPathExists=3D|/etc/sssd/sssd.conf =
was not met
             =E2=94=94=E2=94=80 ConditionDirectoryNotEmpty=3D|/etc/sssd/con=
f.d was not met

Nov 03 15:07:29 chip systemd[1]: System Security Services Daemon was skipped
because no trigger condition checks were met.

# systemctl cat sssd|grep Condition
ConditionPathExists=3D|/etc/sssd/sssd.conf
ConditionDirectoryNotEmpty=3D|/etc/sssd/conf.d/
```

There is no /usr/etc/sssd either:

```
# ls /usr/etc/sssd
ls: cannot access '/usr/etc/sssd': No such file or directory
```

To repair the problem, I need to manually move `/etc/sssd/sssd.conf.rpmsave`
back to `/etc/sssd/sssd.conf`:

```
# mv /etc/sssd/sssd.conf.rpmsave /etc/sssd/sssd.conf
# systemctl start sssd
# systemctl status sssd
=E2=97=8F sssd.service - System Security Services Daemon
     Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; preset:
disabled)
     Active: active (running) since Fri 2023-11-03 15:15:56 UTC; 2s ago
   Main PID: 2359 (sssd)
```

This behavior following a `zypper dup` doesn't seem quite right.

The version after the update is the following:

```
 zypper se -isx sssd
i+ | sssd | package | 2.9.2-2.1 | x86_64 | repo-oss
```

Cheers,
Georg
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16990247602.Ee47b1fb.15159
Date: Fri, 3 Nov 2023 15:19: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
          1216865

          Summary
          Upgrade moves /etc/sssd/sssd.conf to /etc/sssd/sssd.conf.rpms=
ave

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Network

          Assignee
          screening-team-bugs@suse.de

          Reporter
          georg.pfuetzenreuter@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Hi,

upon upgrading `openSUSE Tumbleweed 20231031-0 -> 20231101-0` which cont=
ained
an update of `sssd`, the configuration file was moved to .rpmsave:

```
warning: /etc/sssd/sssd.conf saved as /etc/sssd/sssd.conf.rpmsave
```

I presume this is part of the /usr/etc merge effort, however my sssd.conf f=
ile
contained custom options configuring my LDAP backend - the file being (re)m=
oved
breaks LDAP login after the upgrade.

Furthermore, `sssd` refuses to start completely after the upgrade:

```
# systemctl status sssd
=E2=97=8B sssd.service - System Security Services Daemon
     Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; preset:
disabled)
     Active: inactive (dead)
  Condition: start condition unmet at Fri 2023-11-03 15:13:24 UTC; 879ms ago
             =E2=94=9C=E2=94=80 ConditionPathExists=3D|/etc/sssd/sssd.conf =
was not met
             =E2=94=94=E2=94=80 ConditionDirectoryNotEmpty=3D|/etc/sssd/con=
f.d was not met

Nov 03 15:07:29 chip systemd[1]: System Security Services Daemon was skipped
because no trigger condition checks were met.

# systemctl cat sssd|grep Condition
ConditionPathExists=3D|/etc/sssd/sssd.conf
ConditionDirectoryNotEmpty=3D|/etc/sssd/conf.d/
```

There is no /usr/etc/sssd either:

```
# ls /usr/etc/sssd
ls: cannot access '/usr/etc/sssd': No such file or directory
```

To repair the problem, I need to manually move `/etc/sssd/sssd.conf.rpmsave`
back to `/etc/sssd/sssd.conf`:

```
# mv /etc/sssd/sssd.conf.rpmsave /etc/sssd/sssd.conf
# systemctl start sssd
# systemctl status sssd
=E2=97=8F sssd.service - System Security Services Daemon
     Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; preset:
disabled)
     Active: active (running) since Fri 2023-11-03 15:15:56 UTC; 2s ago
   Main PID: 2359 (sssd)
```

This behavior following a `zypper dup` doesn't seem quite right.

The version after the update is the following:

```
 zypper se -isx sssd
i+ | sssd | package | 2.9.2-2.1 | x86_64 | repo-oss
```

Cheers,
Georg

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

You are on the CC list for the bug.

=

--16990247602.Ee47b1fb.15159--


body:
--16990444380.c288A37e.15429
Date: Fri, 3 Nov 2023 20:47: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=3D1216873

            Bug ID: 1216873
           Summary: VUL-0: tor:
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: bwiedemann-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

It was discovered that tor before 0.4.8.8 compiled with OpenSSL can crash
during handshake with a remote relay.

References:
https://gitlab.torproject.org/tpo/core/tor/-/commit/7aa496a2e057bb7c3cc284a=
04a1a4d2941c304f1
https://gitlab.torproject.org/tpo/core/tor/-/issues/40874
https://gitlab.torproject.org/tpo/core/tor/-/issues/40880
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16990444380.c288A37e.15429
Date: Fri, 3 Nov 2023 20:47:18 +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
          1216873

          Summary
          VUL-0: tor:

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          Andreas.Stieger@gmx.de

          QA Contact
          qa-bugs@suse.de

          CC
          bwiedemann@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

It was discovered that tor before 0.4.8.8 compiled with Open=
SSL can crash
during handshake with a remote relay.

References:
https://gitlab.torproject.org/tpo/core/tor/-/=
commit/7aa496a2e057bb7c3cc284a04a1a4d2941c304f1
https=
://gitlab.torproject.org/tpo/core/tor/-/issues/40874
https=
://gitlab.torproject.org/tpo/core/tor/-/issues/40880

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

You are on the CC list for the bug.

=

--16990444380.c288A37e.15429--

summary: VUL-0: tor:


--16990494980.a8509.15492
Date: Fri, 3 Nov 2023 22:11:38 +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=3D1216878

            Bug ID: 1216878
           Summary: server:monitoring/monitoring-plugins: check_users reporting negative values
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: jgonzalez-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Started happening today on my openSUSE MicroOS, I think that after the last
update.

> # who|wc -l
> 2

But calling:

> /usr/lib/nagios/plugins/check_users -w 5 -c 10

Should return OK, but instead:

> USERS CRITICAL - -13 users currently logged in |users=3D-13;5;15;0

It returns a negative number.

I see monitoring-plugins-users got updated:

> 2023-11-03 01:49:19|install|monitoring-plugins-users|2.3.3-1.1|x86_64||re=
po-oss|8c063521869d4ad1ee1c2e409fd06ffa09cbe6f86ee3cf732a6213895796eba9c396=
a06ec53efac2b315d0920490e8f5bbd508da0396327432e800b5d0624ccb|

Checking the  changelog, I think it's an update to fix
https://bugzilla.opensuse.org/show_bug.cgi?id=3D1216148 at the source packa=
ge
monitorning-plugins, but I can't figure out how that should affect check_us=
ers.

>* Mon Oct 30 2023 ro-at-suse.de
>- renamed patches
>  monitoring-plugins-wrong_return_in_check_swap.patch
>  to monitoring-plugins-2.3.3-wrong_percent_in_check_swap.patch
>  monitoring-plugins.check_snmp.arrayaddress.patch
>  to monitoring-plugins-2.3.3-check_snmp.arrayaddress.patch
>  monitoring-plugins-2.3-check_ntp_perf_absolute.patch
>  to monitoring-plugins-2.3.3-check_ntp_perf_absolute.patch
>=20
>* Mon Oct 16 2023 Thorsten Kukuk <kukuk-at-suse.com>
>- Add buildrequires for coreutils-systemd, as the configure script
>  checks for uptime [bsc#1216148]

I wonder if it's another missing dependency that is not in the list of
buildrequires. Are we maybe cleaning up the list of packages preinstalled on
buildes for Factory?

Reading
https://github.com/nagios-plugins/nagios-plugins/blob/master/plugins/check_=
users.c
I can't possible see how -13 is possible.

It seems the check uses 'who' to figure out the number of users. Who is par=
t of
 coreutils-systemd:

> # rpm -qf /usr/bin/who
> coreutils-systemd-9.4-2.1.x86_64

Which is precisely what got added by
https://bugzilla.opensuse.org/show_bug.cgi?id=3D1216148.

Not saying it's related, but at this moment I don't have more clues.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16990494980.a8509.15492
Date: Fri, 3 Nov 2023 22:11:38 +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
          1216878

          Summary
          server:monitoring/monitoring-plugins: check_users reporting n=
egative values

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          jgonzalez@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Started happening today on my openSUSE MicroOS, I think that=
 after the last
update.

> # who|wc -l
> 2

But calling:

> /usr/lib/nagios/plugins/check_users -w 5 -c 10</=
span >

Should return OK, but instead:

> USERS CRITICAL - -13 users currently logged in |=
users=3D-13;5;15;0

It returns a negative number.

I see monitoring-plugins-users got updated:

> 2023-11-03 01:49:19|install|monitoring-plugins-u=
sers|2.3.3-1.1|x86_64||repo-oss|8c063521869d4ad1ee1c2e409fd06ffa09cbe6f86ee=
3cf732a6213895796eba9c396a06ec53efac2b315d0920490e8f5bbd508da0396327432e800=
b5d0624ccb|

Checking the  changelog, I think it's an update to fix
https:/=
/bugzilla.opensuse.org/show_bug.cgi?id=3D1216148 at the source package
monitorning-plugins, but I can't figure out how that should affect check_us=
ers.

>* Mon Oct 30 2023 ro@suse.de
>- renamed patches
>  monitoring-plugins-wrong_return_in_check_swap.patch
>  to monitoring-plugins-2.3.3-wrong_percent_in_check_swap.patch
>  monitoring-plugins.check_snmp.arrayaddress.patch
>  to monitoring-plugins-2.3.3-check_snmp.arrayaddress.patch
>  monitoring-plugins-2.3-check_ntp_perf_absolute.patch
>  to monitoring-plugins-2.3.3-check_ntp_perf_absolute.patch
>=20
>* Mon Oct 16 2023 Thorsten Kukuk <kukuk@suse.com>
>- Add buildrequires for coreutils-systemd, as the configure script
>  checks for uptime [bsc#1216148]

I wonder if it's another missing dependency that is not in the list of
buildrequires. Are we maybe cleaning up the list of packages preinstalled on
buildes for Factory?

Reading
https://github.com/nagios-plugins/nagios-plugins/blob/m=
aster/plugins/check_users.c
I can't possible see how -13 is possible.

It seems the check uses 'who' to figure out the number of users. Who is par=
t of
 coreutils-systemd:

> # rpm -qf /usr/bin/who
> coreutils-systemd-9.4-2.1.x86_64

Which is precisely what got added by
https:/=
/bugzilla.opensuse.org/show_bug.cgi?id=3D1216148.

Not saying it's related, but at this moment I don't have more clues.

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

You are on the CC list for the bug.

=

--16990494980.a8509.15492--


--16992668090.DdBCEfa.16447
Date: Mon, 6 Nov 2023 10:33:29 +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=3D1216903

            Bug ID: 1216903
           Summary: SELinux: policy update broke kvm network autostart
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: jsegitz-at-suse.com
          Reporter: rfrohl-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: cathy.hu-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Hi,

since the update to selinux-policy: 20231030 KVM network autostart/interact=
ion
is broken. If one tries to start the network manually in virsh the following
error is observed:

> virsh # net-start default
> error: Failed to start network default
> error: internal error: Failed to apply firewall rules /sbin/iptables -w -=
-table filter --list-rules: libvirt:  error : cannot execute binary /sbin/i=
ptables: Permission denied

with=20

> virsh # net-info default
> Name:           default
> UUID:           31f53528-0578-4d70-b510-2f50fcf424f0
> Active:         no
> Persistent:     yes
> Autostart:      yes
> Bridge:         virbr0

As a workaround I am using:

> # setenforce 0
> # virsh net-start default
> # setenforce 1

There is only one detail to be observed: if virsh is run before 'setenforce=
 0',
then the above does not work until the system is restarted.=20

More details: it is not even 'needed' to net-start, any virsh command will
trigger the autostart if 'setenforce 0' was issued.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16992668090.DdBCEfa.16447
Date: Mon, 6 Nov 2023 10:33:29 +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
          1216903

          Summary
          SELinux: policy update broke kvm network autostart

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          jsegitz@suse.com

          Reporter
          rfrohl@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          cathy.hu@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Hi,

since the update to selinux-policy: 20231030 KVM network autostart/interact=
ion
is broken. If one tries to start the network manually in virsh the following
error is observed:

> virsh # net-start default
> error: Failed to start network default
> error: internal error: Failed to apply firewall rules /sbin/iptables -=
w --table filter --list-rules: libvirt:  error : cannot execute binary /sbi=
n/iptables: Permission denied

with=20

> virsh # net-info default
> Name:           default
> UUID:           31f53528-0578-4d70-b510-2f50fcf424f0
> Active:         no
> Persistent:     yes
> Autostart:      yes
> Bridge:         virbr0

As a workaround I am using:

> # setenforce 0
> # virsh net-start default
> # setenforce 1

There is only one detail to be observed: if virsh is run before 'setenforce=
 0',
then the above does not work until the system is restarted.=20

More details: it is not even 'needed' to net-start, any virsh command will
trigger the autostart if 'setenforce 0' was issued.

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

You are on the CC list for the bug.

=

--16992668090.DdBCEfa.16447--


--16992469980.FbCDf.16072
Date: Mon, 6 Nov 2023 05:03:18 +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=3D1216895

            Bug ID: 1216895
           Summary: VUL-0: CVE-2023-47272: Roundcube 1.5.x before 1.5.6 and 1.6.x before 1.6.5 allows XSS via a Content-Type or Content-Disposition header (used for attachment preview or download).
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/384151/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: aj-at-ajaissle.de
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: stoyan.manolov-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

Roundcube 1.5.x before 1.5.6 and 1.6.x before 1.6.5 allows XSS via a
Content-Type or Content-Disposition header (used for attachment preview or
download).

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-47272
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16992469980.FbCDf.16072
Date: Mon, 6 Nov 2023 05:03:18 +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
          1216895

          Summary
          VUL-0: CVE-2023-47272: Roundcube 1.5.x before 1.5.6 and 1.6.x=
 before 1.6.5 allows XSS via a Content-Type or Content-Disposition header (=
used for attachment preview or download).

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          aj@ajaissle.de

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          stoyan.manolov@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

Roundcube 1.5.x before 1.5.6 and 1.6.x before 1.6.5 allows X=
SS via a
Content-Type or Content-Disposition header (used for attachment preview or
download).

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-47272

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

You are on the CC list for the bug.

=

--16992469980.FbCDf.16072--


body:
--16992840810.6a5d46.16813
Date: Mon, 6 Nov 2023 15:21:21 +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=3D1216913

            Bug ID: 1216913
           Summary: Update Plasma to 5.27.9
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: fabian@ritter-vogt.de
          Reporter: fabian@ritter-vogt.de
        QA Contact: qa-bugs-at-suse.de
                CC: opensuse-kde-bugs-at-opensuse.org
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Leap 15.5 currently has Plasma 5.27.4(.1). Version 5.27.9 was released rece=
ntly
and contains various bugfixes that have accumulated over several months.

(For details, check the changelogs from the upstream release announcements =
or
the individual packages)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16992840810.6a5d46.16813
Date: Mon, 6 Nov 2023 15:21:21 +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
          1216913

          Summary
          Update Plasma to 5.27.9

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          KDE Workspace (Plasma)

          Assignee
          fabian@ritter-vogt.de

          Reporter
          fabian@ritter-vogt.de

          QA Contact
          qa-bugs@suse.de

          CC
          opensuse-kde-bugs@opensuse.org

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Leap 15.5 currently has Plasma 5.27.4(.1). Version 5.27.9 wa=
s released recently
and contains various bugfixes that have accumulated over several months.

(For details, check the changelogs from the upstream release announcements =
or
the individual packages)

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

You are on the CC list for the bug.

=

--16992840810.6a5d46.16813--

summary: Update Plasma to 5.27.9


--16992772531.6ebeA2EdB.16633
Date: Mon, 6 Nov 2023 13:27:33 +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=3D1216908

            Bug ID: 1216908
           Summary: libqt5-qtwebengine (i586): out of memory during linkage with new Binutils
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: burnus-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
                CC: christophe-at-krop.fr, matz-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

On 32bit (i586) systems, it is rather simple to run out of memory (max. 4 G=
B).

Unfortunately, this happens when linking libqt5-qtwebengine with the new
version of Binutils:

See
* (currently)
https://build.opensuse.org/project/show/openSUSE:Factory:Staging:A
* https://build.opensuse.org/request/show/1113885 (Binutils update to 2.41)

I don't know what's the best solution, but one possibility, I see, is to
disable LTO for i586, only.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16992772531.6ebeA2EdB.16633
Date: Mon, 6 Nov 2023 13:27:33 +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
          1216908

          Summary
          libqt5-qtwebengine (i586): out of memory during linkage with =
new Binutils

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          KDE Workspace (Plasma)

          Assignee
          opensuse-kde-bugs@opensuse.org

          Reporter
          burnus@gmx.de

          QA Contact
          qa-bugs@suse.de

          CC
          christophe@krop.fr, matz@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

On 32bit (i586) systems, it is rather simple to run out of m=
emory (max. 4 GB).

Unfortunately, this happens when linking libqt5-qtwebengine with the new
version of Binutils:

See
* (currently)
https://build.opensuse.org/project/show/openSUSE:Factory:Staging:A
* https://build=
.opensuse.org/request/show/1113885 (Binutils update to 2.41)

I don't know what's the best solution, but one possibility, I see, is to
disable LTO for i586, only.

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

You are on the CC list for the bug.

=

--16992772531.6ebeA2EdB.16633--


--16995047271.7a7D8a886.19412
Date: Thu, 9 Nov 2023 04:38:47 +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=3D1216978

            Bug ID: 1216978
           Summary: VUL-0: CVE-2023-5996: Use after free in WebAudio in Google Chrome prior to 119.0.6045.123 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/384404/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: gmbr3-at-opensuse.org
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: stoyan.manolov-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

Use after free in WebAudio in Google Chrome prior to 119.0.6045.123 allowed=
 a
remote attacker to potentially exploit heap corruption via a crafted HTML p=
age.
(Chromium security severity: High)

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-5996
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16995047271.7a7D8a886.19412
Date: Thu, 9 Nov 2023 04:38:47 +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
          1216978

          Summary
          VUL-0: CVE-2023-5996: Use after free in WebAudio in Google Ch=
rome prior to 119.0.6045.123 allowed a remote attacker to potentially explo=
it heap corruption via a crafted HTML page. (Chromium security severity: Hi=
gh)

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          gmbr3@opensuse.org

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          stoyan.manolov@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

Use after free in WebAudio in Google Chrome prior to 119.0.6=
045.123 allowed a
remote attacker to potentially exploit heap corruption via a crafted HTML p=
age.
(Chromium security severity: High)

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-5996

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

You are on the CC list for the bug.

=

--16995047271.7a7D8a886.19412--


body:
--16995219762.01e3f.19640
Date: Thu, 9 Nov 2023 09:26:16 +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=3D1216986

            Bug ID: 1216986
           Summary: libguestfs: embeds /etc/hosts
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: carnold-at-suse.com
          Reporter: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1081754
  Target Milestone: ---
          Found By: Development
           Blocker: ---

While working on reproducible builds for openSUSE, I found that
our libguestfs package can produce bit-identical results locally,
but when comparing with the official OBS builds,
it has this diff in=20

-

summary: libguestfs: embeds /etc/hosts


--16995872805.8AF91b2Ea.20662
Date: Fri, 10 Nov 2023 03:34: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=3D1217005

            Bug ID: 1217005
           Summary: VUL-0: CVE-2023-39913: Apache UIMA Java SDK: Deserialization of Untrusted Data, Improper Input Validation vulnerability
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
               URL: https://smash.suse.de/issue/384337/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: fstrba-at-suse.com
          Reporter: smash_bz-at-suse.de
        QA Contact: security-team-at-suse.de
                CC: stoyan.manolov-at-suse.com
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

Deserialization of Untrusted Data, Improper Input Validation vulnerability =
in
Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UI=
MA
Java SDK.This issue affects Apache UIMA Java SDK: before 3.5.0.

Users are recommended to upgrade to version 3.5.0, which fixes the issue.

There are several locations in the code where serialized Java objects are
deserialized without verifying the data. This affects in particular:
  *  the deserialization of a Java-serialized CAS, but also other binary CAS
formats that include TSI information using the CasIOUtils class;
  *  the CAS Editor Eclipse plugin which uses the=C2=A0the CasIOUtils class=
 to load
data;
  *  the deserialization of a Java-serialized CAS of the Vinci Analysis Eng=
ine
service which can receive using Java-serialized CAS objects over network
connections;
  *  the CasAnnotationViewerApplet and the CasTreeViewerApplet;
  *  the checkpointing feature of the CPE module.

Note that the UIMA framework by default does not start any remotely accessi=
ble
services (i.e. Vinci) that would be vulnerable to this issue. A user or
developer would need to make an active choice to start such a service. Howe=
ver,
users or developers may use the CasIOUtils in their own applications and
services to parse serialized CAS data. They are affected by this issue unle=
ss
they ensure that the data passed to CasIOUtils is not a serialized Java obj=
ect.

When using Vinci or using CasIOUtils in own services/applications,=C2=A0the
unrestricted deserialization of Java-serialized CAS files may allow arbitra=
ry
(remote) code execution.

As a remedy, it is possible to set up a global or context-specific
ObjectInputFilter (cf.  https://openjdk.org/jeps/290 =C2=A0and=C2=A0
https://openjdk.org/jeps/415 ) if running UIMA on a Java version that suppo=
rts
it.=20

Note that Java 1.8 does not support the ObjectInputFilter, so there is no
remedy
when running on this out-of-support platform. An upgrade to a recent Java
version is strongly recommended if you need to secure an UIMA version that =
is
affected by this issue.

To mitigate the issue on a Java 9+ platform, you can configure a filter pat=
tern
through the "jdk.serialFilter" system property using a semicolon as a
separator:

To allow deserializing Java-serialized binary CASes, add the classes:
  *  org.apache.uima.cas.impl.CASCompleteSerializer
  *  org.apache.uima.cas.impl.CASMgrSerializer
  *  org.apache.uima.cas.impl.CASSerializer
  *  java.lang.String

To allow deserializing CPE Checkpoint data, add the following classes (and =
any
custom classes your application uses to store its checkpoints):
  *  org.apache.uima.collection.impl.cpm.CheckpointData
  *  org.apache.uima.util.ProcessTrace
  *  org.apache.uima.util.impl.ProcessTrace_impl
  *  org.apache.uima.collection.base_cpm.SynchPoint

Make sure to use "!*" as the final component to the filter pattern to disal=
low
deserialization of any classes not listed in the pattern.

Apache UIMA 3.5.0 uses tightly scoped ObjectInputFilters when reading
Java-serialized data depending on the type of data being expected. Configur=
ing
a
global filter is not necessary with this version.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-39913
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16995872805.8AF91b2Ea.20662
Date: Fri, 10 Nov 2023 03:34: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
          1217005

          Summary
          VUL-0: CVE-2023-39913: Apache UIMA Java SDK: Deserialization =
of Untrusted Data, Improper Input Validation vulnerability

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          fstrba@suse.com

          Reporter
          smash_bz@suse.de

          QA Contact
          security-team@suse.de

          CC
          stoyan.manolov@suse.com

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

Deserialization of Untrusted Data, Improper Input Validation=
 vulnerability in
Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UI=
MA
Java SDK.This issue affects Apache UIMA Java SDK: before 3.5.0.

Users are recommended to upgrade to version 3.5.0, which fixes the issue.

There are several locations in the code where serialized Java objects are
deserialized without verifying the data. This affects in particular:
  *  the deserialization of a Java-serialized CAS, but also other binary CAS
formats that include TSI information using the CasIOUtils class;
  *  the CAS Editor Eclipse plugin which uses the=C2=A0the CasIOUtils class=
 to load
data;
  *  the deserialization of a Java-serialized CAS of the Vinci Analysis Eng=
ine
service which can receive using Java-serialized CAS objects over network
connections;
  *  the CasAnnotationViewerApplet and the CasTreeViewerApplet;
  *  the checkpointing feature of the CPE module.

Note that the UIMA framework by default does not start any remotely accessi=
ble
services (i.e. Vinci) that would be vulnerable to this issue. A user or
developer would need to make an active choice to start such a service. Howe=
ver,
users or developers may use the CasIOUtils in their own applications and
services to parse serialized CAS data. They are affected by this issue unle=
ss
they ensure that the data passed to CasIOUtils is not a serialized Java obj=
ect.

When using Vinci or using CasIOUtils in own services/applications,=C2=A0the
unrestricted deserialization of Java-serialized CAS files may allow arbitra=
ry
(remote) code execution.

As a remedy, it is possible to set up a global or context-specific
ObjectInputFilter (cf.  https://op=
enjdk.org/jeps/290 =C2=A0and=C2=A0
https://openjdk.org/jeps/415 )=
 if running UIMA on a Java version that supports
it.=20

Note that Java 1.8 does not support the ObjectInputFilter, so there is no
remedy
when running on this out-of-support platform. An upgrade to a recent Java
version is strongly recommended if you need to secure an UIMA version that =
is
affected by this issue.

To mitigate the issue on a Java 9+ platform, you can configure a filter pat=
tern
through the "jdk.serialFilter" system property using a semicolon =
as a
separator:

To allow deserializing Java-serialized binary CASes, add the classes:
  *  org.apache.uima.cas.impl.CASCompleteSerializer
  *  org.apache.uima.cas.impl.CASMgrSerializer
  *  org.apache.uima.cas.impl.CASSerializer
  *  java.lang.String

To allow deserializing CPE Checkpoint data, add the following classes (and =
any
custom classes your application uses to store its checkpoints):
  *  org.apache.uima.collection.impl.cpm.CheckpointData
  *  org.apache.uima.util.ProcessTrace
  *  org.apache.uima.util.impl.ProcessTrace_impl
  *  org.apache.uima.collection.base_cpm.SynchPoint

Make sure to use "!*" as the final component to the filter patter=
n to disallow
deserialization of any classes not listed in the pattern.

Apache UIMA 3.5.0 uses tightly scoped ObjectInputFilters when reading
Java-serialized data depending on the type of data being expected. Configur=
ing
a
global filter is not necessary with this version.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2023-39913

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

You are on the CC list for the bug.

=

--16995872805.8AF91b2Ea.20662--


--16996208081.ac7cCDA3.21256
Date: Fri, 10 Nov 2023 12:53:28 +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=3D1217028

            Bug ID: 1217028
           Summary: VUL-0: CVE-2023-46445: python-asyncssh: extension negotiation MitM attack
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: mimi.vx-at-gmail.com
          Reporter: carlos.lopez-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: dmueller-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

CVE-2023-46445

Summary
An issue in AsyncSSH v2.14.0 and earlier allows attackers to control the
extension info message (RFC 8308) via a man-in-the-middle attack.

Details
The rogue extension negotiation attack targets an AsyncSSH client connectin=
g to
any SSH server sending an extension info message. The attack exploits an
implementation flaw in the AsyncSSH implementation to inject an extension i=
nfo
message chosen by the attacker and delete the original extension info messa=
ge,
effectively replacing it.

A correct SSH implementation should not process an unauthenticated extension
info message. However, the injected message is accepted due to flaws in
AsyncSSH. AsyncSSH supports the server-sig-algs and global-requests-ok
extensions. Hence, the attacker can downgrade the algorithm used for client
authentication by meddling with the value of server-sig-algs (e.g. use of S=
HA-1
instead of SHA-2).

References:
https://github.com/advisories/GHSA-cfc2-wr2v-gxm5
https://github.com/ronf/asyncssh/commit/83e43f5ea3470a8617fc388c72b062c7136=
efd7e
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16996208081.ac7cCDA3.21256
Date: Fri, 10 Nov 2023 12:53:28 +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
          1217028

          Summary
          VUL-0: CVE-2023-46445: python-asyncssh: extension negotiation=
 MitM attack

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          mimi.vx@gmail.com

          Reporter
          carlos.lopez@suse.com

          QA Contact
          security-team@suse.de

          CC
          dmueller@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

CVE-2023-46445

Summary
An issue in AsyncSSH v2.14.0 and earlier allows attackers to control the
extension info message (RFC 8308) via a man-in-the-middle attack.

Details
The rogue extension negotiation attack targets an AsyncSSH client connectin=
g to
any SSH server sending an extension info message. The attack exploits an
implementation flaw in the AsyncSSH implementation to inject an extension i=
nfo
message chosen by the attacker and delete the original extension info messa=
ge,
effectively replacing it.

A correct SSH implementation should not process an unauthenticated extension
info message. However, the injected message is accepted due to flaws in
AsyncSSH. AsyncSSH supports the server-sig-algs and global-requests-ok
extensions. Hence, the attacker can downgrade the algorithm used for client
authentication by meddling with the value of server-sig-algs (e.g. use of S=
HA-1
instead of SHA-2).

References:
https://githu=
b.com/advisories/GHSA-cfc2-wr2v-gxm5
https://github.com/ronf/asyncssh/commit/83e43f5ea3470a861=
7fc388c72b062c7136efd7e

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

You are on the CC list for the bug.

=

--16996208081.ac7cCDA3.21256--


--16996308532.db3Eeb36E.21445
Date: Fri, 10 Nov 2023 15:40:53 +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=3D1217032

            Bug ID: 1217032
           Summary: VUL-0: scamper: TCP packet parsing buffer overflow via large TCP fast open cookie
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.4
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: sebix+novell.com-at-sebix.at
          Reporter: carlos.lopez-at-suse.com
        QA Contact: security-team-at-suse.de
                CC: dmueller-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

[scamper-announce] scamper-cvs-20230614d
Matthew Luckie mjl at luckie.org.nz
Mon Oct 9 10:37:01 PDT 2023
Previous message (by thread): [scamper-announce] scamper-cvs-20230614c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://www.caida.org/catalog/software/scamper/code/scamper-cvs-20230614d.t=
ar.gz

SHA256 (scamper-cvs-20230614d.tar.gz) =3D
54423b64a0b68aafa903d9260c2bff5c16f3cca44997e0e830d17296f6f03a59
SIZE (scamper-cvs-20230614d.tar.gz) =3D 2214467

scamper:
* fix buffer overflow when parsing TCP packets where the sender
  includes a TCP fast open cookie larger than 16 bytes.

References:
https://mailman.caida.org/pipermail/scamper-announce/2023-October/000037.ht=
ml
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16996308532.db3Eeb36E.21445
Date: Fri, 10 Nov 2023 15:40:53 +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
          1217032

          Summary
          VUL-0: scamper: TCP packet parsing buffer overflow via large =
TCP fast open cookie

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.4

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          sebix+novell.com@sebix.at

          Reporter
          carlos.lopez@suse.com

          QA Contact
          security-team@suse.de

          CC
          dmueller@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

[scamper-announce] scamper-cvs-20230614d
Matthew Luckie mjl at luckie.org.nz
Mon Oct 9 10:37:01 PDT 2023
Previous message (by thread): [scamper-announce] scamper-cvs-20230614c
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://www.caida.org/catalog/software/scamper/code/scamp=
er-cvs-20230614d.tar.gz

SHA256 (scamper-cvs-20230614d.tar.gz) =3D
54423b64a0b68aafa903d9260c2bff5c16f3cca44997e0e830d17296f6f03a59
SIZE (scamper-cvs-20230614d.tar.gz) =3D 2214467

scamper:
* fix buffer overflow when parsing TCP packets where the sender
  includes a TCP fast open cookie larger than 16 bytes.

References:
https://mailman.caida.org/pipermail/scamper-announce/2023-Oc=
tober/000037.html

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

You are on the CC list for the bug.

=

--16996308532.db3Eeb36E.21445--


--16997853162.E711C.21906
Date: Sun, 12 Nov 2023 10:35:16 +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=3D1217047

            Bug ID: 1217047
           Summary: Tracker: Packages incompatible with appstream 1.0
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: christophe-at-krop.fr
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Appstream 1.0 comes with BIC changes and format changes for metainfo files.

Besides, appstream now uses Qt6 or Qt5 but shares the same library and CMake
config name.

Among the factory packages requiring appstream at build time, 8 failures we=
re
found.

Build failures:
- discover (needs appstreamqt built with Qt5 for its stable build)
- flatpak
- gnome-software
- libadwaita
- pidgin-sipe

metainfo validation failures:

- deja-dup
- gnome-sudoku
- gthumb
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--16997853162.E711C.21906
Date: Sun, 12 Nov 2023 10:35:16 +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
          1217047

          Summary
          Tracker: Packages incompatible with appstream 1.0

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          christophe@krop.fr

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Appstream 1.0 comes with BIC changes and format changes for =
metainfo files.

Besides, appstream now uses Qt6 or Qt5 but shares the same library and CMake
config name.

Among the factory packages requiring appstream at build time, 8 failures we=
re
found.

Build failures:
- discover (needs appstreamqt built with Qt5 for its stable build)
- flatpak
- gnome-software
- libadwaita
- pidgin-sipe

metainfo validation failures:

- deja-dup
- gnome-sudoku
- gthumb

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

You are on the CC list for the bug.

=

--16997853162.E711C.21906--


--17001302203.d3AeA7385.3625
Date: Thu, 16 Nov 2023 10:23: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=3D1217220

            Bug ID: 1217220
           Summary: [SELinux] current MicroOS doesn't allow ssh login
    Classification: openSUSE
           Product: openSUSE Leap Micro
           Version: 5.4
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Base
          Assignee: security-team-at-suse.de
          Reporter: jsegitz-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

While investigating another SELinux issue I installed
openSUSE-MicroOS-DVD-x86_64-Snapshot20231114-Media.iso
with default settings. After installation and adding
PermitRootLogin yes
to the sshd config root still can't log in

setenforce 0
allows to log in. No visible AVCs. Disabling dontaudit yields
type=3DAVC msg=3Daudit(1700130079.518:309): avc:  denied  { read } for  pid=
=3D1178
comm=3D"sshd" name=3D"shadow" dev=3D"overlay" ino=3D20716
scontext=3Dsystem_u:system_r:sshd_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:shadow_t:s0 tclass=3Dfile permissive=3D1
type=3DAVC msg=3Daudit(1700130079.518:310): avc:  denied  { open } for  pid=
=3D1178
comm=3D"sshd" path=3D"/etc/shadow" dev=3D"overlay" ino=3D20716
scontext=3Dsystem_u:system_r:sshd_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:shadow_t:s0 tclass=3Dfile permissive=3D1
type=3DAVC msg=3Daudit(1700130079.518:311): avc:  denied  { getattr } for  =
pid=3D1178
comm=3D"sshd" path=3D"/etc/shadow" dev=3D"overlay" ino=3D20716
scontext=3Dsystem_u:system_r:sshd_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:shadow_t:s0 tclass=3Dfile permissive=3D1
type=3DAVC msg=3Daudit(1700130079.691:323): avc:  denied  { noatsecure } fo=
r=20
pid=3D1179 comm=3D"sshd" scontext=3Dsystem_u:system_r:sshd_t:s0-s0:c0.c1023
tcontext=3Dunconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=3Dp=
rocess
permissive=3D1
type=3DAVC msg=3Daudit(1700130079.691:324): avc:  denied  { siginh } for  p=
id=3D1179
comm=3D"bash" scontext=3Dsystem_u:system_r:sshd_t:s0-s0:c0.c1023
tcontext=3Dunconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=3Dp=
rocess
permissive=3D1

upon successful login.

I'll be away in a couple of minutes an likely will not be able to work on t=
his
today
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17001302203.d3AeA7385.3625
Date: Thu, 16 Nov 2023 10:23: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
          1217220

          Summary
          [SELinux] current MicroOS doesn't allow ssh login

          Classification
          openSUSE

          Product
          openSUSE Leap Micro

          Version
          5.4

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Base

          Assignee
          security-team@suse.de

          Reporter
          jsegitz@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

While investigating another SELinux issue I installed
openSUSE-MicroOS-DVD-x86_64-Snapshot20231114-Media.iso
with default settings. After installation and adding
PermitRootLogin yes
to the sshd config root still can't log in

setenforce 0
allows to log in. No visible AVCs. Disabling dontaudit yields
type=3DAVC msg=3Daudit(1700130079.518:309): avc:  denied  { read } for  pid=
=3D1178
comm=3D"sshd" name=3D"shadow" dev=3D"overlay"=
 ino=3D20716
scontext=3Dsystem_u:system_r:sshd_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:shadow_t:s0 tclass=3Dfile permissive=3D1
type=3DAVC msg=3Daudit(1700130079.518:310): avc:  denied  { open } for  pid=
=3D1178
comm=3D"sshd" path=3D"/etc/shadow" dev=3D"overlay&=
quot; ino=3D20716
scontext=3Dsystem_u:system_r:sshd_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:shadow_t:s0 tclass=3Dfile permissive=3D1
type=3DAVC msg=3Daudit(1700130079.518:311): avc:  denied  { getattr } for  =
pid=3D1178
comm=3D"sshd" path=3D"/etc/shadow" dev=3D"overlay&=
quot; ino=3D20716
scontext=3Dsystem_u:system_r:sshd_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:shadow_t:s0 tclass=3Dfile permissive=3D1
type=3DAVC msg=3Daudit(1700130079.691:323): avc:  denied  { noatsecure } fo=
r=20
pid=3D1179 comm=3D"sshd" scontext=3Dsystem_u:system_r:sshd_t:s0-s=
0:c0.c1023
tcontext=3Dunconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=3Dp=
rocess
permissive=3D1
type=3DAVC msg=3Daudit(1700130079.691:324): avc:  denied  { siginh } for  p=
id=3D1179
comm=3D"bash" scontext=3Dsystem_u:system_r:sshd_t:s0-s0:c0.c1023
tcontext=3Dunconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=3Dp=
rocess
permissive=3D1

upon successful login.

I'll be away in a couple of minutes an likely will not be able to work on t=
his
today

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

You are on the CC list for the bug.

=

--17001302203.d3AeA7385.3625--


body:
--17004660030.7cB126.7389
Date: Mon, 20 Nov 2023 07:40:03 +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=3D1217315

            Bug ID: 1217315
           Summary: [LenovoX13s] Screen remains black with live images and JeOS images
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
                CC: chester.lin-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

On the Lenovo X13s laptop, we are able to boot DVD ISO from USB just fine, =
but
Live images [0] and JeOS images [1] are not able to display anything on the
screen.

I suspect the initrd is missing some kernel drivers, but failed to find whi=
ch
ones so far.

[0]: https://build.opensuse.org/project/show/openSUSE:Factory:ARM:Live
[1]: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17004660030.7cB126.7389
Date: Mon, 20 Nov 2023 07:40:03 +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
          1217315

          Summary
          [LenovoX13s] Screen remains black with live images and JeOS i=
mages

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          aarch64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          guillaume.gardet@arm.com

          QA Contact
          qa-bugs@suse.de

          CC
          chester.lin@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

On the Lenovo X13s laptop, we are able to boot DVD ISO from =
USB just fine, but
Live images [0] and JeOS images [1] are not able to display anything on the
screen.

I suspect the initrd is missing some kernel drivers, but failed to find whi=
ch
ones so far.

[0]: https://build.opensuse.org/project/show/openSUSE:Factory:ARM:Live</=
a>
[1]: https://build.opensuse.org/package/show/openSUSE:Factory:ARM/JeOS</=
a>

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

You are on the CC list for the bug.

=

--17004660030.7cB126.7389--

pkgs: JeOS livecd-openSUSE


body:
--17005499882.d0C0Db4cf.9281
Date: Tue, 21 Nov 2023 06:59: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=3D1217352

            Bug ID: 1217352
           Summary: mediastreamer2 missing ENABLE_QT_GL
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: pstivanin-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

>From user Kimi in OBS:

Not sure if anyone else also noticed that mediastreamer2 plugin libmsqogl.so
either does not build or installs to the wrong place.

libmsqogl.so does not initiate properly when clicking on "Hamburger
icon/Preferences/Video/Static Picture or camera and then click on button Vi=
deo
Preview" in linphone-desktop GUI app causing a video crash and segmentation
fault. Seems /usr/plugins/mediastreamer/libmsqogl.so is the place where
linphone looks for it. When it is in that location, no more MSQOGL crashes
happen.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17005499882.d0C0Db4cf.9281
Date: Tue, 21 Nov 2023 06:59: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
          1217352

          Summary
          mediastreamer2 missing ENABLE_QT_GL

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          pstivanin@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

From user Kimi in OBS:

Not sure if anyone else also noticed that mediastreamer2 plugin libmsqogl.so
either does not build or installs to the wrong place.

libmsqogl.so does not initiate properly when clicking on "Hamburger
icon/Preferences/Video/Static Picture or camera and then click on button Vi=
deo
Preview" in linphone-desktop GUI app causing a video crash and segment=
ation
fault. Seems /usr/plugins/mediastreamer/libmsqogl.so is the place where
linphone looks for it. When it is in that location, no more MSQOGL crashes
happen.

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

You are on the CC list for the bug.

=

--17005499882.d0C0Db4cf.9281--

summary: mediastreamer2 missing ENABLE_QT_GL


body:
Gecko/20100101
Firefox/119.0
Build Identifier:=20

I installed python311-blue and just ran it:

[osomon@laptop ~]$ blue
Traceback (most recent call last):
  File "/usr/bin/blue", line 33, in <module>
    sys.exit(load_entry_point('blue=3D=3D0.9.1', 'console_scripts', 'blue')=
())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/blue/__init__.py", line=
 458, in main
    assert config_param.name =3D=3D 'config'
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError

Reproducible: Always

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

You are on the CC list for the bug.

=

--17005837631.d9c03.10402--

summary: Traceback when running blue (from package python311-blue)