--17117100632.8f1D7.13089
Date: Fri, 29 Mar 2024 11:01: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=3D1222158

            Bug ID: 1222158
           Summary: SDDM virtual keyboard button not working
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: suse.com-at-s.bjoern-tantau.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

This might be related to #1212880, I wasn't able to check.

After a new installation of OpenSUSE Tumbleweed with the KDE Desktop select=
ed
the button for the virtual keyboard in the login screen does not work. When=
 I
click it nothing happens.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17117100632.8f1D7.13089
Date: Fri, 29 Mar 2024 11:01: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
          1222158

          Summary
          SDDM virtual keyboard button not working

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          KDE Workspace (Plasma)

          Assignee
          opensuse-kde-bugs@opensuse.org

          Reporter
          suse.com@s.bjoern-tantau.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

This might be related to #1212880, I wasn't able to check.

After a new installation of OpenSUSE Tumbleweed with the KDE Desktop select=
ed
the button for the virtual keyboard in the login screen does not work. When=
 I
click it nothing happens.

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

You are on the CC list for the bug.

=

--17117100632.8f1D7.13089--


--17117427661.73E5CCAf.13694
Date: Fri, 29 Mar 2024 20:06:06 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1222172
           Summary: emacsclient -n -c fails to start when emacs daemon is started early
    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: gabriel.bertazi-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

TW includes emacs.service to start an emacs server through systemd. I enable
the unit file:
  systemctl enable --user emacs

after log out/log in, the server is started properly within the user sessio=
n.
But any attempt to start a client with a frame (-c) disconnected from the s=
hell
(-n) fails silently:=20

  emacsclient -n -c   // fails immediately and returns 1.

journald shows:
 29 15:54:29 cartola emacs[29953]: xauth: (argv):1:  bad display name
"wayland-0" in "extract" command
 29 15:54:29 cartola emacs[29953]: No matches found, authority file "-" not
written
 29 15:54:29 cartola emacs[29953]: xauth: (argv):1:  unable to read any ent=
ries
from file "(stdin)"

Curiously, if I omit the -n parameter, it kind of works. A tiny window gets
created.  It seems the frame is misconfigured  as it ignored the window
setting:
  emacsclient -c

Now...

If, from a shell, I restart the service:
    systemctl restart --user emacs

Then, both:
  emacsclient -n -c=20
  emacsclient -c

work fine, and respect the window sizes previously set.

I suspect the problem is some missing wayland environment variable that is =
not
configured when emacsd is first started.  After restart, when everything wo=
rks,
I see the /proc/<pid>/environ is much longer. In particular these are now  =
set
in the emacs daemon environment:

XAUTHORITY=3D/run/user/1000/emacs/xauth
XAUTHLOCALHOSTNAME=3Dmylaptop

I'm using the distro provided unit file:

 [0:krisman@cartola ~]$ systemctl status --user emacs
=E2=97=8F emacs.service - Emacs text editor
     Loaded: loaded (/usr/lib/systemd/user/emacs.service; enabled; preset:
disa>
     Active: active (running) since Fri 2024-03-29 15:56:04 EDT; 8min ago
       Docs: info:emacs
             man:emacs(1)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17117427661.73E5CCAf.13694
Date: Fri, 29 Mar 2024 20:06:06 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1222172

          Summary
          emacsclient -n -c fails to start when emacs daemon is started=
 early

          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
          gabriel.bertazi@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

TW includes emacs.service to start an emacs server through s=
ystemd. I enable
the unit file:
  systemctl enable --user emacs

after log out/log in, the server is started properly within the user sessio=
n.
But any attempt to start a client with a frame (-c) disconnected from the s=
hell
(-n) fails silently:=20

  emacsclient -n -c   // fails immediately and returns 1.

journald shows:
 29 15:54:29 cartola emacs[29953]: xauth: (argv):1:  bad display name
"wayland-0" in "extract" command
 29 15:54:29 cartola emacs[29953]: No matches found, authority file "-=
" not
written
 29 15:54:29 cartola emacs[29953]: xauth: (argv):1:  unable to read any ent=
ries
from file "(stdin)"

Curiously, if I omit the -n parameter, it kind of works. A tiny window gets
created.  It seems the frame is misconfigured  as it ignored the window
setting:
  emacsclient -c

Now...

If, from a shell, I restart the service:
    systemctl restart --user emacs

Then, both:
  emacsclient -n -c=20
  emacsclient -c

work fine, and respect the window sizes previously set.

I suspect the problem is some missing wayland environment variable that is =
not
configured when emacsd is first started.  After restart, when everything wo=
rks,
I see the /proc/<pid>/environ is much longer. In particular these are=
 now  set
in the emacs daemon environment:

XAUTHORITY=3D/run/user/1000/emacs/xauth
XAUTHLOCALHOSTNAME=3Dmylaptop

I'm using the distro provided unit file:

 [0:krisman@cartola ~]$ systemctl status --user emacs
=E2=97=8F emacs.service - Emacs text editor
     Loaded: loaded (/usr/lib/systemd/user/emacs.service; enabled; preset:
disa>
     Active: active (running) since Fri 2024-03-29 15:56:04 EDT; 8min ago
       Docs: info:emacs
             man:emacs(1)

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

You are on the CC list for the bug.

=

--17117427661.73E5CCAf.13694--


--17117754933.C668.13835
Date: Sat, 30 Mar 2024 05:11: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=3D1222179

            Bug ID: 1222179
           Summary: openSUSE Tumbleweed 20240328 breaks power-profiles-daemon
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: eazyvg-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Since the update the Power Profile stopped working, it is not being loaded
during the boot up. Previously it was working fine on KDE.

[code]
vg@VG-835G10Nix:~> sudo systemctl status power-profiles-daemon.service=20
[sudo] password for root:=20
=C3=97 power-profiles-daemon.service - Power Profiles daemon
     Loaded: loaded (/usr/lib/systemd/system/power-profiles-daemon.service;
enabled; preset: disabled)
     Active: failed (Result: exit-code) since Sat 2024-03-30 07:54:35 MSK;
15min ago
   Duration: 264us
    Process: 1633 ExecStart=3D/usr/libexec/power-profiles-daemon (code=3Dex=
ited,
status=3D1/FAILURE)
   Main PID: 1633 (code=3Dexited, status=3D1/FAILURE)
        CPU: 16ms

Mar 30 07:54:35 VG-835G10Nix systemd[1]: power-profiles-daemon.service:
Scheduled restart job, restart counter is at 5.
Mar 30 07:54:35 VG-835G10Nix systemd[1]: power-profiles-daemon.service: Sta=
rt
request repeated too quickly.
Mar 30 07:54:35 VG-835G10Nix systemd[1]: power-profiles-daemon.service: Fai=
led
with result 'exit-code'.
Mar 30 07:54:35 VG-835G10Nix systemd[1]: Failed to start Power Profiles dae=
mon.
[/code]
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17117754933.C668.13835
Date: Sat, 30 Mar 2024 05:11: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
          1222179

          Summary
          openSUSE Tumbleweed 20240328 breaks power-profiles-daemon

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          eazyvg@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Since the update the Power Profile stopped working, it is no=
t being loaded
during the boot up. Previously it was working fine on KDE.

[code]
vg@VG-835G10Nix:~> sudo systemctl status power-profiles-daemon.servi=
ce=20
[sudo] password for root:=20
=C3=97 power-profiles-daemon.service - Power Profiles daemon
     Loaded: loaded (/usr/lib/systemd/system/power-profiles-daemon.service;
enabled; preset: disabled)
     Active: failed (Result: exit-code) since Sat 2024-03-30 07:54:35 MSK;
15min ago
   Duration: 264us
    Process: 1633 ExecStart=3D/usr/libexec/power-profiles-daemon (code=3Dex=
ited,
status=3D1/FAILURE)
   Main PID: 1633 (code=3Dexited, status=3D1/FAILURE)
        CPU: 16ms

Mar 30 07:54:35 VG-835G10Nix systemd[1]: power-profiles-daemon.service:
Scheduled restart job, restart counter is at 5.
Mar 30 07:54:35 VG-835G10Nix systemd[1]: power-profiles-daemon.service: Sta=
rt
request repeated too quickly.
Mar 30 07:54:35 VG-835G10Nix systemd[1]: power-profiles-daemon.service: Fai=
led
with result 'exit-code'.
Mar 30 07:54:35 VG-835G10Nix systemd[1]: Failed to start Power Profiles dae=
mon.
[/code]

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

You are on the CC list for the bug.

=

--17117754933.C668.13835--


--17118912122.aACC1.14207
Date: Sun, 31 Mar 2024 13:20:12 +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=3D1222188

            Bug ID: 1222188
           Summary: lazarus crashes, when debugging with gdb is enabled
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: 64bit
                OS: openSUSE Leap 15.5
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: rebzdu-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Lazarus crashes, when I start a program with enabled debugging.
I've submitted a bug report for gdb:
https://sourceware.org/bugzilla/show_bug.cgi?id=3D31524
A patch for gdb is provided:
https://sourceware.org/pipermail/gdb-patches/2024-March/207606.html
It would be helpfull, if this patch could be implemented.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17118912122.aACC1.14207
Date: Sun, 31 Mar 2024 13:20:12 +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
          1222188

          Summary
          lazarus crashes, when debugging with gdb is enabled

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          64bit

          OS
          openSUSE Leap 15.5

          Status
          NEW

          Severity
          Critical

          Priority
          P5 - None

          Component
          Development

          Assignee
          screening-team-bugs@suse.de

          Reporter
          rebzdu@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Lazarus crashes, when I start a program with enabled debuggi=
ng.
I've submitted a bug report for gdb:
https:/=
/sourceware.org/bugzilla/show_bug.cgi?id=3D31524
A patch for gdb is provided:
https://sourceware.org/pipermail/gdb-patches/2024-March/207606.html
It would be helpfull, if this patch could be implemented.

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

You are on the CC list for the bug.

=

--17118912122.aACC1.14207--


--17119139151.6f88834Cf.14309
Date: Sun, 31 Mar 2024 19:38:35 +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=3D1222192

            Bug ID: 1222192
           Summary: Package description for cadvisor shows trivy
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: Other
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: holdenrf2021-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Also shows on https://software.opensuse.org/package/cadvisor

$ sudo zypper if trivy cadvisor
[sudo] password for root:=20
Loading repository data...
Reading installed packages...

Information for package trivy:
------------------------------
Repository     : Main Repository (OSS)
Name           : trivy
Version        : 0.49.1-1.2
Arch           : x86_64
Vendor         : openSUSE
Installed Size : 274.2 MiB
Installed      : No
Status         : not installed
Source package : trivy-0.49.1-1.2.src
Upstream URL   : https://github.com/aquasecurity/trivy
Summary        : A Simple and Comprehensive Vulnerability Scanner for
Containers
Description    :=20
    Trivy (`tri` pronounced like trigger, `vy` pronounced like envy) is a
simple and
    comprehensive vulnerability scanner for containers and other artifacts.=
 A
    software vulnerability is a glitch, flaw, or weakness present in the
software or
    in an Operating System. Trivy detects vulnerabilities of OS packages
(Alpine,
    RHEL, CentOS, etc.) and application dependencies (Bundler, Composer, np=
m,
yarn,
    etc.). Trivy is easy to use. Just install the binary and you're ready to
    scan. All you need to do for scanning is to specify a target such as an
image
    name of the container.

Information for package cadvisor:
---------------------------------
Repository     : Main Repository (OSS)
Name           : cadvisor
Version        : 0.46.0-1.8
Arch           : x86_64
Vendor         : openSUSE
Installed Size : 29.9 MiB
Installed      : No
Status         : not installed
Source package : cadvisor-0.46.0-1.8.src
Upstream URL   : https://github.com/google/cadvisor
Summary        : A Simple and Comprehensive Vulnerability Scanner for
Containers
Description    :=20
    Trivy (`tri` pronounced like trigger, `vy` pronounced like envy) is a
simple and
    comprehensive vulnerability scanner for containers and other artifacts.=
 A
    software vulnerability is a glitch, flaw, or weakness present in the
software or
    in an Operating System. Trivy detects vulnerabilities of OS packages
(Alpine,
    RHEL, CentOS, etc.) and application dependencies (Bundler, Composer, np=
m,
yarn,
    etc.). Trivy is easy to use. Just install the binary and you're ready to
    scan. All you need to do for scanning is to specify a target such as an
image
    name of the container.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17119139151.6f88834Cf.14309
Date: Sun, 31 Mar 2024 19:38:35 +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
          1222192

          Summary
          Package description for cadvisor shows trivy

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          All

          OS
          Other

          Status
          NEW

          Severity
          Minor

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          holdenrf2021@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Also shows on https://software.opensuse.org/package/cadvisor

$ sudo zypper if trivy cadvisor
[sudo] password for root:=20
Loading repository data...
Reading installed packages...

Information for package trivy:
------------------------------
Repository     : Main Repository (OSS)
Name           : trivy
Version        : 0.49.1-1.2
Arch           : x86_64
Vendor         : openSUSE
Installed Size : 274.2 MiB
Installed      : No
Status         : not installed
Source package : trivy-0.49.1-1.2.src
Upstream URL   : https://=
github.com/aquasecurity/trivy
Summary        : A Simple and Comprehensive Vulnerability Scanner for
Containers
Description    :=20
    Trivy (`tri` pronounced like trigger, `vy` pronounced like envy) is a
simple and
    comprehensive vulnerability scanner for containers and other artifacts.=
 A
    software vulnerability is a glitch, flaw, or weakness present in the
software or
    in an Operating System. Trivy detects vulnerabilities of OS packages
(Alpine,
    RHEL, CentOS, etc.) and application dependencies (Bundler, Composer, np=
m,
yarn,
    etc.). Trivy is easy to use. Just install the binary and you're ready to
    scan. All you need to do for scanning is to specify a target such as an
image
    name of the container.

Information for package cadvisor:
---------------------------------
Repository     : Main Repository (OSS)
Name           : cadvisor
Version        : 0.46.0-1.8
Arch           : x86_64
Vendor         : openSUSE
Installed Size : 29.9 MiB
Installed      : No
Status         : not installed
Source package : cadvisor-0.46.0-1.8.src
Upstream URL   : https://git=
hub.com/google/cadvisor
Summary        : A Simple and Comprehensive Vulnerability Scanner for
Containers
Description    :=20
    Trivy (`tri` pronounced like trigger, `vy` pronounced like envy) is a
simple and
    comprehensive vulnerability scanner for containers and other artifacts.=
 A
    software vulnerability is a glitch, flaw, or weakness present in the
software or
    in an Operating System. Trivy detects vulnerabilities of OS packages
(Alpine,
    RHEL, CentOS, etc.) and application dependencies (Bundler, Composer, np=
m,
yarn,
    etc.). Trivy is easy to use. Just install the binary and you're ready to
    scan. All you need to do for scanning is to specify a target such as an
image
    name of the container.

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

You are on the CC list for the bug.

=

--17119139151.6f88834Cf.14309--


--17119170950.c0acd.14321
Date: Sun, 31 Mar 2024 20:31:35 +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=3D1222194

            Bug ID: 1222194
           Summary: kubo ipfs tries to start before the network appears and fails with an error
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: werwolf131313-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

kubo ipfs tries to start before the network appears and fails with an error

> [werwolf@power] ~=20=20
> =E2=9D=AF sudo LANG=3Dc zypper info kubo
> Refreshing service 'openSUSE'.
> Loading repository data...
> Reading installed packages...
>=20
>=20
> Information for package kubo:
> -----------------------------
> Repository     : filesystems
> Name           : kubo
> Version        : 0.26.0-16.17
> Arch           : x86_64
> Vendor         : obs://build.opensuse.org/filesystems
> Installed Size : 79.2 MiB
> Installed      : Yes
> Status         : up-to-date
> Source package : kubo-0.26.0-16.17.src
> Upstream URL   : https://github.com/ipfs/kubo
> Summary        : IPFS implementation in Go
> Description    :=20
>     IPFS is a global, versioned, peer-to-peer filesystem. It combines goo=
d ideas from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a sing=
le bittorrent swarm, exchanging git objects. IPFS provides an interface as =
simple as the HTTP web, but with permanence
>     built in. You can also mount the world at /ipfs.

As far as I understand, the problem can be solved by simply adding one line=
 to
the systemd service file

> Wants=3Dnetwork-online.target
> After=3Dnetwork-online.target
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17119170950.c0acd.14321
Date: Sun, 31 Mar 2024 20:31:35 +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
          1222194

          Summary
          kubo ipfs tries to start before the network appears and fails=
 with an error

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          werwolf131313@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

kubo ipfs tries to start before the network appears and fail=
s with an error

> [werwolf@power] ~=20=20
> =E2=9D=AF sudo LANG=3Dc zypper info kubo
> Refreshing service 'openSUSE'.
> Loading repository data...
> Reading installed packages...
>=20
>=20
> Information for package kubo:
> -----------------------------
> Repository     : filesystems
> Name           : kubo
> Version        : 0.26.0-16.17
> Arch           : x86_64
> Vendor         : obs://build.opensuse.org/filesystems
> Installed Size : 79.2 MiB
> Installed      : Yes
> Status         : up-to-date
> Source package : kubo-0.26.0-16.17.src
> Upstream URL   : https://gith=
ub.com/ipfs/kubo
> Summary        : IPFS implementation in Go
> Description    :=20
>     IPFS is a global, versioned, peer-to-peer filesystem. It combines =
good ideas from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a s=
ingle bittorrent swarm, exchanging git objects. IPFS provides an interface =
as simple as the HTTP web, but with permanence
>     built in. You can also mount the world at /ipfs.

As far as I understand, the problem can be solved by simply adding one line=
 to
the systemd service file

> Wants=3Dnetwork-online.target
> After=3Dnetwork-online.target

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

You are on the CC list for the bug.

=

--17119170950.c0acd.14321--


body:
--17120790422.5f6925b.17103
Date: Tue, 2 Apr 2024 17:30:42 +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=3D1222249

            Bug ID: 1222249
           Summary: Systemtap fails to run on v6.8 kernel
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-bugs-at-opensuse.org
          Reporter: tonyj-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

While testing fixes for bsc#1221706 I noticed that systemtap was not
functioning correctly on v6.8 based kernels.

# stap -e 'probe oneshot { println("hello world") }'
In file included from /usr/share/systemtap/runtime/linux/access_process_vm.=
h:6,
                 from /usr/share/systemtap/runtime/linux/runtime.h:315,
                 from /usr/share/systemtap/runtime/runtime.h:26,
                 from
/tmp/stapQfrt4d/stap_12c74092879671ed4cd208bf7321d2eb_983_src.c:21:
/usr/share/systemtap/runtime/linux/access_process_vm.h: In function
=E2=80=98__access_process_vm_=E2=80=99:
/usr/share/systemtap/runtime/linux/stap_mmap_lock.h:10:43: error: =E2=80=98=
struct
mm_struct=E2=80=99 has no member named =E2=80=98mmap_sem=E2=80=99; did you =
mean =E2=80=98mmap_base=E2=80=99?
   10 | #define mmap_read_lock(mm) down_read(&mm->mmap_sem)
      |                                           ^~~~~~~~
/usr/share/systemtap/runtime/linux/access_process_vm.h:33:3: note: in expan=
sion
of macro =E2=80=98mmap_read_lock=E2=80=99
   33 |   mmap_read_lock (mm);
      |   ^~~~~~~~~~~~~~
/usr/share/systemtap/runtime/linux/access_process_vm.h:63:36: error: passing
argument 1 of =E2=80=98get_user_pages_remote=E2=80=99 from incompatible poi=
nter type
[-Werror=3Dincompatible-pointer-types]
...
...
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17120790422.5f6925b.17103
Date: Tue, 2 Apr 2024 17:30:42 +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
          1222249

          Summary
          Systemtap fails to run on v6.8 kernel

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Kernel

          Assignee
          kernel-bugs@opensuse.org

          Reporter
          tonyj@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

While testing fixes for bsc#1221706 I noticed that systemtap was not
functioning correctly on v6.8 based kernels.

# stap -e 'probe oneshot { println("hello world") }'
In file included from /usr/share/systemtap/runtime/linux/access_process_vm.=
h:6,
                 from /usr/share/systemtap/runtime/linux/runtime.h:315,
                 from /usr/share/systemtap/runtime/runtime.h:26,
                 from
/tmp/stapQfrt4d/stap_12c74092879671ed4cd208bf7321d2eb_983_src.c:21:
/usr/share/systemtap/runtime/linux/access_process_vm.h: In function
=E2=80=98__access_process_vm_=E2=80=99:
/usr/share/systemtap/runtime/linux/stap_mmap_lock.h:10:43: error: =E2=80=98=
struct
mm_struct=E2=80=99 has no member named =E2=80=98mmap_sem=E2=80=99; did you =
mean =E2=80=98mmap_base=E2=80=99?
   10 | #define mmap_read_lock(mm) down_read(&mm->mmap_sem)
      |                                           ^~~~~~~~
/usr/share/systemtap/runtime/linux/access_process_vm.h:33:3: note: in expan=
sion
of macro =E2=80=98mmap_read_lock=E2=80=99
   33 |   mmap_read_lock (mm);
      |   ^~~~~~~~~~~~~~
/usr/share/systemtap/runtime/linux/access_process_vm.h:63:36: error: passing
argument 1 of =E2=80=98get_user_pages_remote=E2=80=99 from incompatible poi=
nter type
[-Werror=3Dincompatible-pointer-types]
...
...

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

You are on the CC list for the bug.

=

--17120790422.5f6925b.17103--

summary: Systemtap fails to run on v6.8 kernel


--17121288040.cfC4bfb.17667
Date: Wed, 3 Apr 2024 07:20:04 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1222260
           Summary: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 123.0.6312.105
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: m.szczepaniak.000-at-gmail.com
          Reporter: abergmann-at-suse.com
        QA Contact: security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

https://chromereleases.googleblog.com/2024/04/stable-channel-update-for-des=
ktop.html

Stable Channel Update for Desktop
Tuesday, April 2, 2024

The Stable channel has been updated to 123.0.6312.105/.106/.107 for Windows=
 and
Mac and 123.0.6312.105 to Linux which will roll out over the coming days/we=
eks.
A full list of changes in this build is available in the Log.

Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majori=
ty
of users are updated with a fix. We will also retain restrictions if the bug
exists in a third party library that other projects similarly depend on, but
haven=E2=80=99t yet fixed.

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

High CVE-2024-3156: Inappropriate implementation in V8
High CVE-2024-3158: Use after free in Bookmarks
High CVE-2024-3159: Out of bounds memory access in V8

For detailed information, please look into the official Chrome release
announcement.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17121288040.cfC4bfb.17667
Date: Wed, 3 Apr 2024 07:20:04 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1222260

          Summary
          VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities =
fixed in 123.0.6312.105

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          m.szczepaniak.000@gmail.com

          Reporter
          abergmann@suse.com

          QA Contact
          security-team@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

https://chromereleases.googleblog.com/=
2024/04/stable-channel-update-for-desktop.html

Stable Channel Update for Desktop
Tuesday, April 2, 2024

The Stable channel has been updated to 123.0.6312.105/.106/.107 for Windows=
 and
Mac and 123.0.6312.105 to Linux which will roll out over the coming days/we=
eks.
A full list of changes in this build is available in the Log.

Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majori=
ty
of users are updated with a fix. We will also retain restrictions if the bug
exists in a third party library that other projects similarly depend on, but
haven=E2=80=99t yet fixed.

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

High CVE-2024-3156: Inappropriate implementation in V8
High CVE-2024-3158: Use after free in Bookmarks
High CVE-2024-3159: Out of bounds memory access in V8

For detailed information, please look into the official Chrome release
announcement.

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

You are on the CC list for the bug.

=

--17121288040.cfC4bfb.17667--


body:
--17121463913.49ff0.18954
Date: Wed, 3 Apr 2024 12:13:11 +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=3D1222276

            Bug ID: 1222276
           Summary: Gpaste doesn't work on Gnome 46
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: GNOME
          Assignee: gnome-bugs-at-suse.de
          Reporter: rm.canella-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Following the update to Gnome 46 (cpe:2.3:o:opensuse:tumbleweed:20240329), =
the
Gpaste extension contained in the repositories remained at version 45-3.2 of
Gnome, so it is no longer usable (it is disabled in the extensions
application).

As reported in the official application repository
https://github.com/Keruspe/GPaste Latest release for GNOME 45 or 46 is:=C2=
=A0GPaste
45.1.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17121463913.49ff0.18954
Date: Wed, 3 Apr 2024 12:13:11 +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
          1222276

          Summary
          Gpaste doesn't work on Gnome 46

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Minor

          Priority
          P5 - None

          Component
          GNOME

          Assignee
          gnome-bugs@suse.de

          Reporter
          rm.canella@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Following the update to Gnome 46 (cpe:2.3:o:opensuse:tumblew=
eed:20240329), the
Gpaste extension contained in the repositories remained at version 45-3.2 of
Gnome, so it is no longer usable (it is disabled in the extensions
application).

As reported in the official application repository
https://github.com/Keruspe/GP=
aste Latest release for GNOME 45 or 46 is:=C2=A0GPaste
45.1.

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

You are on the CC list for the bug.

=

--17121463913.49ff0.18954--

summary: Gpaste doesn't work on Gnome 46


--17122430632.a8f3dB2.21740
Date: Thu, 4 Apr 2024 15:04:23 +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=3D1222329

            Bug ID: 1222329
           Summary: AUDIT-0: util-linux: pam_lastlog2.so got moved from lastlog2
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

The lastlog2 package got merged into util-linux. As result, pam_lastlog2.so=
 is
now part of util-linux-systemd.

Packages can be found at:
https://build.opensuse.org/package/show/home:kukuk:cleanup/util-linux
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17122430632.a8f3dB2.21740
Date: Thu, 4 Apr 2024 15:04:23 +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
          1222329

          Summary
          AUDIT-0: util-linux: pam_lastlog2.so got moved from lastlog2

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          kukuk@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

The lastlog2 package got merged into util-linux. As result, =
pam_lastlog2.so is
now part of util-linux-systemd.

Packages can be found at:
https://build.opensuse.org/package/show/home:kukuk:cleanup/util-linu=
x

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

You are on the CC list for the bug.

=

--17122430632.a8f3dB2.21740--


body:
--17122995132.d5bEaaEA8.23146
Date: Fri, 5 Apr 2024 06:45:13 +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=3D1222349

            Bug ID: 1222349
           Summary: python nochecks issues
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: daniel.garcia-at-suse.com
          Reporter: bwiedemann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I extended my reproducibleopensuse tools and it found=20
python-libarchive python-praatio python-pytest-attrib
where my tools say, build results differ with=20
osc build --nochecks vs without it:
https://rb.zq1.de/compare.factory/diffs/python-libarchive-compare.out
https://rb.zq1.de/compare.factory/diffs/python-praatio-compare.out
https://rb.zq1.de/compare.factory/diffs/python-pytest-attrib-compare.out
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17122995132.d5bEaaEA8.23146
Date: Fri, 5 Apr 2024 06:45:13 +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
          1222349

          Summary
          python nochecks issues

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          daniel.garcia@suse.com

          Reporter
          bwiedemann@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I extended my reproducibleopensuse tools and it found=20
python-libarchive python-praatio python-pytest-attrib
where my tools say, build results differ with=20
osc build --nochecks vs without it:
https://rb.zq1.de/compare.factory/diffs/python-libarchive-compare.ou=
t
https://rb.zq1.de/compare.factory/diffs/python-praatio-compare.out
https://rb.zq1.de/compare.factory/diffs/python-pytest-attrib-comp=
are.out

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

You are on the CC list for the bug.

=

--17122995132.d5bEaaEA8.23146--

summary: python nochecks issues


--17125077662.fa8E.833
Date: Sun, 7 Apr 2024 16:36:06 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1222408
           Summary: VirtualBox not allowed to access USB devices although user is in vboxusers group
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.5
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Other
          Assignee: virt-bugs-at-suse.de
          Reporter: michael.nickol@t-online.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

same as bug #1222186 but now for leap 15.5 after update today (7. april 202=
4)

symptom:

Silentmax:~ # /usr/lib/virtualbox/vboxdrv.sh status
chmod: cannot access '/etc/vboxusb/': No such file or directory
chmod: cannot access '/etc/vboxusb/*': No such file or directory
chmod: cannot access '/etc/vboxusb/*/*': No such file or directory
VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp) are loaded.
Silentmax:~ # uname -a
Linux Silentmax.fritz.box 5.14.21-150500.55.52-default #1 SMP PREEMPT_DYNAM=
IC
Tue Mar 5 16:53:41 UTC 2024 (a62851f) x86_64 x86_64 x86_64 GNU/Linux

virtualbox - VirtualBox is an Emulator=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
                Version: 7.0.14-lp155.2.19.1 Installed: 7.0.14-lp155.2.19.1=
=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
                                Size: 84.7 MiB Media No.: 0=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
                                                License: GPL-2.0-or-later=
=20=20=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
                                                                Source Pack=
age:
virtualbox-7.0.14-lp155.2.19.1
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17125077662.fa8E.833
Date: Sun, 7 Apr 2024 16:36:06 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1222408

          Summary
          VirtualBox not allowed to access USB devices although user is=
 in vboxusers group

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.5

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Virtualization:Other

          Assignee
          virt-bugs@suse.de

          Reporter
          michael.nickol@t-online.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

same as bug #1222186 but now for leap 15.=
5 after update today (7. april 2024)

symptom:

Silentmax:~ # /usr/lib/virtualbox/vboxdrv.sh status
chmod: cannot access '/etc/vboxusb/': No such file or directory
chmod: cannot access '/etc/vboxusb/*': No such file or directory
chmod: cannot access '/etc/vboxusb/*/*': No such file or directory
VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp) are loaded.
Silentmax:~ # uname -a
Linux Silentmax.fritz.box 5.14.21-150500.55.52-default #1 SMP PREEMPT_DYNAM=
IC
Tue Mar 5 16:53:41 UTC 2024 (a62851f) x86_64 x86_64 x86_64 GNU/Linux

virtualbox - VirtualBox is an Emulator=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
                Version: 7.0.14-lp155.2.19.1 Installed: 7.0.14-lp155.2.19.1=
=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
                                Size: 84.7 MiB Media No.: 0=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
                                                License: GPL-2.0-or-later=
=20=20=20=20=20=20
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20
                                                                Source Pack=
age:
virtualbox-7.0.14-lp155.2.19.1

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

You are on the CC list for the bug.

=

--17125077662.fa8E.833--


--17125652932.c48DaE2f.1694
Date: Mon, 8 Apr 2024 08:34: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=3D1222442

            Bug ID: 1222442
           Summary: [20240404] Xorg crash running Android studio
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: gfx-bugs-at-suse.de
          Reporter: pujos.michael-at-gmail.com
        QA Contact: gfx-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Since snapshot 20240404 and upgrade of xorg-x11-server (21.1.11 -> 21.1.12),
starting Android Studio crashes Xorg hard everytime.
Most specifically, I am using Android Studio Koala | 2024.1.1 Canary 3 that=
 can
be downloaded here: https://developer.android.com/studio/preview. I would n=
ot
be surprised this crash happens with other Jetbrains IDE but I have not tri=
ed.

I triggered 2 crashes, both of which killed the Xorg process. There first c=
rash
had a crash stack in journalctl why the other did not:

Apr 08 10:06:11 p72 systemd-coredump[16070]: [=F0=9F=A1=95] Process 11338 (=
Xorg.bin) of
user 1000 dumped core.

                                             Stack trace of thread 11338:
                                             #0  0x00007f63b22949ec
__pthread_kill_implementation (libc.so.6 + 0x949ec)
                                             #1  0x00007f63b2241176 raise
(libc.so.6 + 0x41176)
                                             #2  0x00007f63b2228917 abort
(libc.so.6 + 0x28917)
                                             #3  0x0000555e1e464efc n/a
(/usr/bin/Xorg.bin + 0x1dbefc)
                                             #4  0x00007ffee9bf4ba0 n/a (n/=
a +
0x0)
                                             ELF object binary architecture:
AMD x86-64

Reverting to 21.1.11 fixes that issue and I have added a lock for package
xorg-x11-server for the time being.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17125652932.c48DaE2f.1694
Date: Mon, 8 Apr 2024 08:34: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
          1222442

          Summary
          [20240404] Xorg crash running Android studio

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          X.Org

          Assignee
          gfx-bugs@suse.de

          Reporter
          pujos.michael@gmail.com

          QA Contact
          gfx-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Since snapshot 20240404 and upgrade of xorg-x11-server (21.1=
.11 -> 21.1.12),
starting Android Studio crashes Xorg hard everytime.
Most specifically, I am using Android Studio Koala | 2024.1.1 Canary 3 that=
 can
be downloaded here: https://developer.android.com/studio/preview. I would not
be surprised this crash happens with other Jetbrains IDE but I have not tri=
ed.

I triggered 2 crashes, both of which killed the Xorg process. There first c=
rash
had a crash stack in journalctl why the other did not:

Apr 08 10:06:11 p72 systemd-coredump[16070]: [=F0=9F=A1=95] Process 11338 (=
Xorg.bin) of
user 1000 dumped core.

                                             Stack trace of thread 11338:
                                             #0  0x00007f63b22949ec
__pthread_kill_implementation (libc.so.6 + 0x949ec)
                                             #1  0x00007f63b2241176 raise
(libc.so.6 + 0x41176)
                                             #2  0x00007f63b2228917 abort
(libc.so.6 + 0x28917)
                                             #3  0x0000555e1e464efc n/a
(/usr/bin/Xorg.bin + 0x1dbefc)
                                             #4  0x00007ffee9bf4ba0 n/a (n/=
a +
0x0)
                                             ELF object binary architecture:
AMD x86-64

Reverting to 21.1.11 fixes that issue and I have added a lock for package
xorg-x11-server for the time being.

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

You are on the CC list for the bug.

=

--17125652932.c48DaE2f.1694--


--17125753495.84cB.2126
Date: Mon, 8 Apr 2024 11:22: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=3D1222457

            Bug ID: 1222457
           Summary: AUDIT-0: google-guest-oslogin: Please review new PAM module pam_oslogin_admin.so
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: adrian.glaubitz-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: public-cloud-maintainers-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

A recent submission for an update to the google-guest-oslogin package to
Factory was rejected due to the fact that it introduces a new PAM modules [=
1]:

[   14s] google-guest-oslogin.x86_64: E: pam-file-unauthorized (Badness: 10=
000)
/usr/lib64/security/pam_oslogin_admin.so (sha256 file digest default
filter:f9d3249da91257e53c70cf394404be3b13f6eae2a67b74192d48a2fb64941def she=
ll
filter:<failed-to-calculate> xml filter:<failed-to-calculate>)
[   14s] Packaging new PAM modules requires a review and whitelisting by the
SUSE
[   14s] security team. If the package is intended for inclusion in any SUSE
product
[   14s] please open a bug report to request review of the package by the
security
[   14s] team. Please refer to
[   14s]
https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs for
[   14s] more information.

Since google-guest-oslogin had this PAM module in the past which upstream
removed [2] and then reintroduced [3], I think it should be easy to audit t=
his
change.

> [1] https://build.opensuse.org/request/show/1164370
> [2] https://github.com/GoogleCloudPlatform/guest-oslogin/pull/116
> [3] https://github.com/GoogleCloudPlatform/guest-oslogin/pull/133
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17125753495.84cB.2126
Date: Mon, 8 Apr 2024 11:22: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
          1222457

          Summary
          AUDIT-0: google-guest-oslogin: Please review new PAM module p=
am_oslogin_admin.so

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          adrian.glaubitz@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          public-cloud-maintainers@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

A recent submission for an update to the google-guest-oslogi=
n package to
Factory was rejected due to the fact that it introduces a new PAM modules [=
1]:

[   14s] google-guest-oslogin.x86_64: E: pam-file-unauthorized (Badness: 10=
000)
/usr/lib64/security/pam_oslogin_admin.so (sha256 file digest default
filter:f9d3249da91257e53c70cf394404be3b13f6eae2a67b74192d48a2fb64941def she=
ll
filter:<failed-to-calculate> xml filter:<failed-to-calculate>)
[   14s] Packaging new PAM modules requires a review and whitelisting by the
SUSE
[   14s] security team. If the package is intended for inclusion in any SUSE
product
[   14s] please open a bug report to request review of the package by the
security
[   14s] team. Please refer to
[   14s]
https://en.opensuse.org/openSUSE:Package_security_guidelines#audit=
_bugs for
[   14s] more information.

Since google-guest-oslogin had this PAM module in the past which upstream
removed [2] and then reintroduced [3], I think it should be easy to audit t=
his
change.

> [1] https://build.opensuse.org/request/show/1164370
> [2] https://github.com/GoogleCloudPlatform/guest-oslogin/pull/116
> [3] https://github.com/GoogleCloudPlatform/guest-oslogin/pull/133</=
span >

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

You are on the CC list for the bug.

=

--17125753495.84cB.2126--


--17125798701.497AE4f75.2411
Date: Mon, 8 Apr 2024 12:37:50 +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=3D1222468

            Bug ID: 1222468
           Summary: VUL-0: CVE-2024-22189: caddy: quic-go: memory exhaustion attack against QUIC's connection ID mechanism
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://smash.suse.de/issue/400376/
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: alexandre.vicenzi-at-suse.com
          Reporter: camila.matos-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: camila.matos-at-suse.com, jkowalczyk-at-suse.com,
                    security-team-at-suse.de, smash_bz-at-suse.de
            Blocks: 1222461
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

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

quic-go is an implementation of the QUIC protocol in Go. Prior to version
0.42.0, an attacker can cause its peer to run out of memory sending a large
number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The
receiver is supposed to respond to each retirement frame with a
`RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from
sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by
collapsing the peers congestion window (by selectively acknowledging receiv=
ed
packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contai=
ns a
patch for the issue. No known workarounds are available.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-22189
https://www.cve.org/CVERecord?id=3DCVE-2024-22189
https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c=
85ed47a
https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478
https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-manageme=
nt
https://www.youtube.com/watch?v=3DJqXtYcZAtIA&t=3D3683s
https://bugzilla.redhat.com/show_bug.cgi?id=3D2273513
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17125798701.497AE4f75.2411
Date: Mon, 8 Apr 2024 12:37:50 +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
          1222468

          Summary
          VUL-0: CVE-2024-22189: caddy: quic-go: memory exhaustion atta=
ck against QUIC's connection ID mechanism

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          alexandre.vicenzi@suse.com

          Reporter
          camila.matos@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          camila.matos@suse.com, jkowalczyk@suse.com, security-=
team@suse.de, smash_bz@suse.de

          Blocks
          1222461

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

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

quic-go is an implementation of the QUIC protocol in Go. Prior to version
0.42.0, an attacker can cause its peer to run out of memory sending a large
number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The
receiver is supposed to respond to each retirement frame with a
`RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from
sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by
collapsing the peers congestion window (by selectively acknowledging receiv=
ed
packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contai=
ns a
patch for the issue. No known workarounds are available.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-22189
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-22189
https://github.com/quic-go/quic-go/commit/4a99b816ae3ab=
03ae5449d15aac45147c85ed47a
https://github.com/quic-go/quic-go/security/advisories/GHSA-c33=
x-xqrf-c478
https://seemann.io/posts/2024-03-19-exploiting-quics-connect=
ion-id-management
htt=
ps://www.youtube.com/watch?v=3DJqXtYcZAtIA&t=3D3683s
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2273513

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

You are on the CC list for the bug.

=

--17125798701.497AE4f75.2411--


--17125845301.aC61FE2e2.2735
Date: Mon, 8 Apr 2024 13:55:30 +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=3D1222473

            Bug ID: 1222473
           Summary: VUL-0: CVE-2024-22189: dnscrypt-proxy: quic-go: memory exhaustion attack against QUIC's connection ID mechanism
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://smash.suse.de/issue/400376/
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: cunix-at-mail.de
          Reporter: camila.matos-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: camila.matos-at-suse.com, security-team-at-suse.de,
                    smash_bz-at-suse.de
            Blocks: 1222461
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

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

quic-go is an implementation of the QUIC protocol in Go. Prior to version
0.42.0, an attacker can cause its peer to run out of memory sending a large
number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The
receiver is supposed to respond to each retirement frame with a
`RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from
sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by
collapsing the peers congestion window (by selectively acknowledging receiv=
ed
packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contai=
ns a
patch for the issue. No known workarounds are available.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-22189
https://www.cve.org/CVERecord?id=3DCVE-2024-22189
https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c=
85ed47a
https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478
https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-manageme=
nt
https://www.youtube.com/watch?v=3DJqXtYcZAtIA&t=3D3683s
https://bugzilla.redhat.com/show_bug.cgi?id=3D2273513
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17125845301.aC61FE2e2.2735
Date: Mon, 8 Apr 2024 13:55:30 +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
          1222473

          Summary
          VUL-0: CVE-2024-22189: dnscrypt-proxy: quic-go: memory exhaus=
tion attack against QUIC's connection ID mechanism

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          cunix@mail.de

          Reporter
          camila.matos@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          camila.matos@suse.com, security-team@suse.de, smash_b=
z@suse.de

          Blocks
          1222461

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

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

quic-go is an implementation of the QUIC protocol in Go. Prior to version
0.42.0, an attacker can cause its peer to run out of memory sending a large
number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The
receiver is supposed to respond to each retirement frame with a
`RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from
sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by
collapsing the peers congestion window (by selectively acknowledging receiv=
ed
packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contai=
ns a
patch for the issue. No known workarounds are available.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-22189
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-22189
https://github.com/quic-go/quic-go/commit/4a99b816ae3ab=
03ae5449d15aac45147c85ed47a
https://github.com/quic-go/quic-go/security/advisories/GHSA-c33=
x-xqrf-c478
https://seemann.io/posts/2024-03-19-exploiting-quics-connect=
ion-id-management
htt=
ps://www.youtube.com/watch?v=3DJqXtYcZAtIA&t=3D3683s
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2273513

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

You are on the CC list for the bug.

=

--17125845301.aC61FE2e2.2735--


--17125865970.Db3bCA.2873
Date: Mon, 8 Apr 2024 14:29:57 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1222479
           Summary: VUL-0: CVE-2024-22189: kubo: quic-go: memory exhaustion attack against QUIC's connection ID mechanism
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://smash.suse.de/issue/400376/
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: bwiedemann-at-suse.com
          Reporter: camila.matos-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: camila.matos-at-suse.com, security-team-at-suse.de,
                    smash_bz-at-suse.de
            Blocks: 1222461
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

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

quic-go is an implementation of the QUIC protocol in Go. Prior to version
0.42.0, an attacker can cause its peer to run out of memory sending a large
number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The
receiver is supposed to respond to each retirement frame with a
`RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from
sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by
collapsing the peers congestion window (by selectively acknowledging receiv=
ed
packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contai=
ns a
patch for the issue. No known workarounds are available.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-22189
https://www.cve.org/CVERecord?id=3DCVE-2024-22189
https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c=
85ed47a
https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478
https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-manageme=
nt
https://www.youtube.com/watch?v=3DJqXtYcZAtIA&t=3D3683s
https://bugzilla.redhat.com/show_bug.cgi?id=3D2273513
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17125865970.Db3bCA.2873
Date: Mon, 8 Apr 2024 14:29:57 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1222479

          Summary
          VUL-0: CVE-2024-22189: kubo: quic-go: memory exhaustion attac=
k against QUIC's connection ID mechanism

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          bwiedemann@suse.com

          Reporter
          camila.matos@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          camila.matos@suse.com, security-team@suse.de, smash_b=
z@suse.de

          Blocks
          1222461

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

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

quic-go is an implementation of the QUIC protocol in Go. Prior to version
0.42.0, an attacker can cause its peer to run out of memory sending a large
number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The
receiver is supposed to respond to each retirement frame with a
`RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from
sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by
collapsing the peers congestion window (by selectively acknowledging receiv=
ed
packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contai=
ns a
patch for the issue. No known workarounds are available.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-22189
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-22189
https://github.com/quic-go/quic-go/commit/4a99b816ae3ab=
03ae5449d15aac45147c85ed47a
https://github.com/quic-go/quic-go/security/advisories/GHSA-c33=
x-xqrf-c478
https://seemann.io/posts/2024-03-19-exploiting-quics-connect=
ion-id-management
htt=
ps://www.youtube.com/watch?v=3DJqXtYcZAtIA&t=3D3683s
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2273513

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

You are on the CC list for the bug.

=

--17125865970.Db3bCA.2873--


--17125888892.Ab3DaC7.3026
Date: Mon, 8 Apr 2024 15:08:09 +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=3D1222488

            Bug ID: 1222488
           Summary: VUL-0: CVE-2024-22189: v2ray-core: quic-go: memory exhaustion attack against QUIC's connection ID mechanism
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://smash.suse.de/issue/400376/
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: hillwoodroc-at-gmail.com
          Reporter: camila.matos-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: camila.matos-at-suse.com, security-team-at-suse.de,
                    smash_bz-at-suse.de
            Blocks: 1222461
  Target Milestone: ---
          Found By: Security Response Team
           Blocker: ---

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

quic-go is an implementation of the QUIC protocol in Go. Prior to version
0.42.0, an attacker can cause its peer to run out of memory sending a large
number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The
receiver is supposed to respond to each retirement frame with a
`RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from
sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by
collapsing the peers congestion window (by selectively acknowledging receiv=
ed
packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contai=
ns a
patch for the issue. No known workarounds are available.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-22189
https://www.cve.org/CVERecord?id=3DCVE-2024-22189
https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c=
85ed47a
https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478
https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-manageme=
nt
https://www.youtube.com/watch?v=3DJqXtYcZAtIA&t=3D3683s
https://bugzilla.redhat.com/show_bug.cgi?id=3D2273513
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17125888892.Ab3DaC7.3026
Date: Mon, 8 Apr 2024 15:08:09 +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
          1222488

          Summary
          VUL-0: CVE-2024-22189: v2ray-core: quic-go: memory exhaustion=
 attack against QUIC's connection ID mechanism

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

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

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Security

          Assignee
          hillwoodroc@gmail.com

          Reporter
          camila.matos@suse.com

          QA Contact
          qa-bugs@suse.de

          CC
          camila.matos@suse.com, security-team@suse.de, smash_b=
z@suse.de

          Blocks
          1222461

          Target Milestone
          ---

          Found By
          Security Response Team

          Blocker
          ---

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

quic-go is an implementation of the QUIC protocol in Go. Prior to version
0.42.0, an attacker can cause its peer to run out of memory sending a large
number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The
receiver is supposed to respond to each retirement frame with a
`RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from
sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by
collapsing the peers congestion window (by selectively acknowledging receiv=
ed
packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contai=
ns a
patch for the issue. No known workarounds are available.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=3DCVE-2024-22189
https://www.c=
ve.org/CVERecord?id=3DCVE-2024-22189
https://github.com/quic-go/quic-go/commit/4a99b816ae3ab=
03ae5449d15aac45147c85ed47a
https://github.com/quic-go/quic-go/security/advisories/GHSA-c33=
x-xqrf-c478
https://seemann.io/posts/2024-03-19-exploiting-quics-connect=
ion-id-management
htt=
ps://www.youtube.com/watch?v=3DJqXtYcZAtIA&t=3D3683s
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2273513

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

You are on the CC list for the bug.

=

--17125888892.Ab3DaC7.3026--


--17125908952.C5daC07.3107
Date: Mon, 8 Apr 2024 15:41:35 +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=3D1222490

            Bug ID: 1222490
           Summary: Kruner and Home Menu only show krusader in root mode
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: smartinds-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 874135
  --> https://bugzilla.suse.com/attachment.cgi?id=3D874135&action=3Dedit
Screenshot

Why Kruner and the "Home Menu" only show =E2=80=9Ckrusader=E2=80=9D in root=
 mode?
I have krusader in my path

:~> ls -l /bin/kru*
-rwxr-xr-x 1 root root   85016 mar 26 13:06 /bin/krunner
-rwxr-xr-x 1 root root   84520 abr  1 13:21 /bin/krunner-plugininstaller
-rwxr-xr-x 1 root root 2832680 mar 13 03:21 /bin/krusader

~> ls -l /usr/bin/kru*
-rwxr-xr-x 1 root root   85016 mar 26 13:06 /usr/bin/krunner
-rwxr-xr-x 1 root root   84520 abr  1 13:21 /usr/bin/krunner-plugininstaller
-rwxr-xr-x 1 root root 2832680 mar 13 03:21 /usr/bin/krusader

Krusader works if I run it with the terminal, but is weird that don show in
"Kruner" nor "Home Menu".

Note: Sometimes (random) both show me Krusader in "Normal Mode", but not the
"Root Mode".
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17125908952.C5daC07.3107
Date: Mon, 8 Apr 2024 15:41:35 +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
          1222490

          Summary
          Kruner and Home Menu only show krusader in root mode

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          KDE Applications

          Assignee
          opensuse-kde-bugs@opensuse.org

          Reporter
          smartinds@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 874135 [d=
etails]
Screenshot

Why Kruner and the "Home Menu" only show =E2=80=9Ckrusader=E2=80=
=9D in root mode?
I have krusader in my path

:~> ls -l /bin/kru*
-rwxr-xr-x 1 root root   85016 mar 26 13:06 /bin/krunner
-rwxr-xr-x 1 root root   84520 abr  1 13:21 /bin/krunner-plugininstaller
-rwxr-xr-x 1 root root 2832680 mar 13 03:21 /bin/krusader

~> ls -l /usr/bin/kru*
-rwxr-xr-x 1 root root   85016 mar 26 13:06 /usr/bin/krunner
-rwxr-xr-x 1 root root   84520 abr  1 13:21 /usr/bin/krunner-plugininstaller
-rwxr-xr-x 1 root root 2832680 mar 13 03:21 /usr/bin/krusader

Krusader works if I run it with the terminal, but is weird that don show in
"Kruner" nor "Home Menu".

Note: Sometimes (random) both show me Krusader in "Normal Mode", =
but not the
"Root Mode".

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

You are on the CC list for the bug.

=

--17125908952.C5daC07.3107--


--17126613340.b28C96BbE.5498
Date: Tue, 9 Apr 2024 11:15: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=3D1222545

            Bug ID: 1222545
           Summary: [Build 20240408] Sway needs to follow branding changes
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/4072724/modules/sway
                    /steps/26
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-sway@64bit fails in
[sway](https://openqa.opensuse.org/tests/4072724/modules/sway/steps/26)

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

## Reproducible

Fails since (at least) Build
[20240408](https://openqa.opensuse.org/tests/4072724) (current job)

## Expected result

Last good: [20240407](https://openqa.opensuse.org/tests/4068539) (or more
recent)

## Further details

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

--17126613340.b28C96BbE.5498
Date: Tue, 9 Apr 2024 11:15: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
          1222545

          Summary
          [Build 20240408] Sway needs to follow branding changes

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          URL
          https://openqa.opensuse.org/tests/4072724/modules/sway/steps/=
26

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          dimstar@opensuse.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-sway@64bit fails=
 in
[sway](https://openqa.opensuse.org/tests/4072724/modules/sway/steps/26)

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

## Reproducible

Fails since (at least) Build
[20240408](https://op=
enqa.opensuse.org/tests/4072724) (current job)

## Expected result

Last good: [20240407](https://openqa.opensuse.org/tests/4068539) (or more
recent)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=3Dx=
86_64&distri=3Dopensuse&flavor=3DDVD&machine=3D64bit&test=
=3Dsway&version=3DTumbleweed)

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

You are on the CC list for the bug.

=

--17126613340.b28C96BbE.5498--


--17127289142.6e0b1C26c.6823
Date: Wed, 10 Apr 2024 06:01:54 +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=3D1222581

            Bug ID: 1222581
           Summary: [Build 20240409] LXQt needs to follow branding changes
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/4075119/modules/open
                    suse_welcome/steps/4
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LXQt
          Assignee: lxqt-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

## Observation

openQA test in scenario opensuse-Tumbleweed-NET-x86_64-otherDE_lxqt@64bit f=
ails
in
[opensuse_welcome](https://openqa.opensuse.org/tests/4075119/modules/opensu=
se_welcome/steps/4)

## Test suite description

## Reproducible

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

## Expected result

Last good: [20240407](https://openqa.opensuse.org/tests/4068273) (or more
recent)

## Further details

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

--17127289142.6e0b1C26c.6823
Date: Wed, 10 Apr 2024 06:01:54 +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
          1222581

          Summary
          [Build 20240409] LXQt needs to follow branding changes

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          URL
          https://openqa.opensuse.org/tests/4075119/modules/opensuse_we=
lcome/steps/4

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          LXQt

          Assignee
          lxqt-bugs@suse.de

          Reporter
          dimstar@opensuse.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

## Observation

openQA test in scenario opensuse-Tumbleweed-NET-x86_64-otherDE_lxqt@64b=
it fails
in
[opensuse_welcome](https://openqa.opensuse.org/tests/4075119/mo=
dules/opensuse_welcome/steps/4)

## Test suite description

## Reproducible

Fails since (at least) Build
[20240408](https://op=
enqa.opensuse.org/tests/4072458)

## Expected result

Last good: [20240407](https://openqa.opensuse.org/tests/4068273) (or more
recent)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?=
arch=3Dx86_64&distri=3Dopensuse&flavor=3DNET&machine=3D64bit&am=
p;test=3DotherDE_lxqt&version=3DTumbleweed)

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

You are on the CC list for the bug.

=

--17127289142.6e0b1C26c.6823--


--17127290611.9639A9bDB.6832
Date: Wed, 10 Apr 2024 06:04: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=3D1222583

            Bug ID: 1222583
           Summary: [Build 20240409] MATE: clock has quit unexpectedly
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/4075118/modules/rebo
                    ot_icewm/steps/11
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: openQA
           Blocker: Yes

## Observation

openQA test in scenario opensuse-Tumbleweed-NET-x86_64-otherDE_mate@64bit f=
ails
in
[reboot_icewm](https://openqa.opensuse.org/tests/4075118/modules/reboot_ice=
wm/steps/11)

## Test suite description

## Reproducible

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

## Expected result

Last good: [20240408](https://openqa.opensuse.org/tests/4072457) (or more
recent)

## Further details

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

--17127290611.9639A9bDB.6832
Date: Wed, 10 Apr 2024 06:04: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
          1222583

          Summary
          [Build 20240409] MATE: clock has quit unexpectedly

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          URL
          https://openqa.opensuse.org/tests/4075118/modules/reboot_icew=
m/steps/11

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          dimstar@opensuse.org

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          openQA

          Blocker
          Yes

## Observation

openQA test in scenario opensuse-Tumbleweed-NET-x86_64-otherDE_mate@64b=
it fails
in
[reboot_icewm](https://openqa.opensuse.org/tests/4075118/modules/r=
eboot_icewm/steps/11)

## Test suite description

## Reproducible

Fails since (at least) Build
[20240409](https://op=
enqa.opensuse.org/tests/4074357)

## Expected result

Last good: [20240408](https://openqa.opensuse.org/tests/4072457) (or more
recent)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?=
arch=3Dx86_64&distri=3Dopensuse&flavor=3DNET&machine=3D64bit&am=
p;test=3DotherDE_mate&version=3DTumbleweed)

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

You are on the CC list for the bug.

=

--17127290611.9639A9bDB.6832--


--17127497006.FFe0e1EeA.8035
Date: Wed, 10 Apr 2024 11:48: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=3D1222621

            Bug ID: 1222621
           Summary: xpra fails to build in openSUSE:Backports:SLE-15-SP6
    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: ncutler-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

xpra fails to build in openSUSE:Backports:SLE-15-SP6 because setup.py fails=
 to
detect the SLE environment and doesn't know that it needs the same special
libexec handling as openSUSE.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17127497006.FFe0e1EeA.8035
Date: Wed, 10 Apr 2024 11:48: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
          1222621

          Summary
          xpra fails to build in openSUSE:Backports:SLE-15-SP6

          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
          ncutler@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

xpra fails to build in openSUSE:Backports:SLE-15-SP6 because=
 setup.py fails to
detect the SLE environment and doesn't know that it needs the same special
libexec handling as openSUSE.

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

You are on the CC list for the bug.

=

--17127497006.FFe0e1EeA.8035--