--17175155301.c5d98fb21.16599
Date: Tue, 4 Jun 2024 15:38: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=3D1225951

            Bug ID: 1225951
           Summary: Package vinagre does not build with gcc14 because of new errors
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mjambor-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1220571
  Target Milestone: ---
          Found By: ---
           Blocker: ---

GCC 14 newly by default treats as errors a number of situations which
before were only warnings.  For more information see
https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571.

Because of this, package vinagre fails to compile.  This can be seen online
at:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:=
Gcc7/vinagre/standard/x86_64

It can be reproduced locally with command: osc build --clean
--alternative-project home:rguenther:nextgcc

We probably need the patch attached to
https://bugzilla.redhat.com/show_bug.cgi?id=3D2179869

The (first) error (that halts the build) is:

[   23s] vinagre/vinagre-dirs.c: In function
=E2=80=98vinagre_dirs_get_package_data_file=E2=80=99:
[   23s] vinagre/vinagre-dirs.c:121:25: error: assignment to =E2=80=98gchar=
 **=E2=80=99 {aka
=E2=80=98char **=E2=80=99} from incompatible pointer type =E2=80=98const gc=
har * const*=E2=80=99 {aka =E2=80=98const
char * const*=E2=80=99} [-Wincompatible-pointer-types]
[   23s]   121 |         _tmp1_ =3D _tmp0_ =3D g_get_system_data_dirs ();
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17175155301.c5d98fb21.16599
Date: Tue, 4 Jun 2024 15:38: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
          1225951

          Summary
          Package vinagre does not build with gcc14 because of new erro=
rs

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Network

          Assignee
          screening-team-bugs@suse.de

          Reporter
          mjambor@suse.com

          QA Contact
          qa-bugs@suse.de

          Blocks
          1220571

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

GCC 14 newly by default treats as errors a number of situati=
ons which
before were only warnings.  For more information see
https://gcc.gnu.org/=
gcc-14/porting_to.html and meta bug #1220571.

Because of this, package vinagre fails to compile.  This can be seen online
at:
https://build.opensuse.org/package=
/live_build_log/openSUSE:Factory:Staging:Gcc7/vinagre/standard/x86_64

It can be reproduced locally with command: osc build --clean
--alternative-project home:rguenther:nextgcc

We probably need the patch attached to
https://b=
ugzilla.redhat.com/show_bug.cgi?id=3D2179869

The (first) error (that halts the build) is:

[   23s] vinagre/vinagre-dirs.c: In function
=E2=80=98vinagre_dirs_get_package_data_file=E2=80=99:
[   23s] vinagre/vinagre-dirs.c:121:25: error: assignment to =E2=80=98gchar=
 **=E2=80=99 {aka
=E2=80=98char **=E2=80=99} from incompatible pointer type =E2=80=98const gc=
har * const*=E2=80=99 {aka =E2=80=98const
char * const*=E2=80=99} [-Wincompatible-pointer-types]
[   23s]   121 |         _tmp1_ =3D _tmp0_ =3D g_get_system_data_dirs ();</=
pre>

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

You are on the CC list for the bug.

=

--17175155301.c5d98fb21.16599--


--17175164710.834D9c.16638
Date: Tue, 4 Jun 2024 15:54:31 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1225953
           Summary: Package xen does not build with gcc14 because of new errors
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Xen
          Assignee: xen-bugs-at-suse.de
          Reporter: mjambor-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1220571
  Target Milestone: ---
          Found By: ---
           Blocker: ---

GCC 14 newly by default treats as errors a number of situations which
before were only warnings.  For more information see
https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571.

Because of this, package xen fails to compile.  This can be seen online
at:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:=
Gcc7/xen/standard/x86_64

It can be reproduced locally with command: osc build --clean
--alternative-project home:rguenther:nextgcc

The (first) error (that halts the build) is:

[   75s] In file included from
../../../../../newlib-1.16.0/newlib/libc/reent/signalr.c:7:
[   75s] ../../../../../newlib-1.16.0/newlib/libc/reent/signalr.c: In funct=
ion
=E2=80=98_kill_r=E2=80=99:
[   75s] ../../../../../newlib-1.16.0/newlib/libc/reent/signalr.c:61:14: er=
ror:
implicit declaration of function =E2=80=98kill=E2=80=99; did you mean =E2=
=80=98_kill=E2=80=99?
[-Wimplicit-function-declaration]
[   75s]    61 |   if ((ret =3D _kill (pid, sig)) =3D=3D -1 && errno !=3D 0)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17175164710.834D9c.16638
Date: Tue, 4 Jun 2024 15:54:31 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1225953

          Summary
          Package xen does not build with gcc14 because of new errors

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Xen

          Assignee
          xen-bugs@suse.de

          Reporter
          mjambor@suse.com

          QA Contact
          qa-bugs@suse.de

          Blocks
          1220571

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

GCC 14 newly by default treats as errors a number of situati=
ons which
before were only warnings.  For more information see
https://gcc.gnu.org/=
gcc-14/porting_to.html and meta bug #1220571.

Because of this, package xen fails to compile.  This can be seen online
at:
https://build.opensuse.org/package/liv=
e_build_log/openSUSE:Factory:Staging:Gcc7/xen/standard/x86_64

It can be reproduced locally with command: osc build --clean
--alternative-project home:rguenther:nextgcc

The (first) error (that halts the build) is:

[   75s] In file included from
../../../../../newlib-1.16.0/newlib/libc/reent/signalr.c:7:
[   75s] ../../../../../newlib-1.16.0/newlib/libc/reent/signalr.c: In funct=
ion
=E2=80=98_kill_r=E2=80=99:
[   75s] ../../../../../newlib-1.16.0/newlib/libc/reent/signalr.c:61:14: er=
ror:
implicit declaration of function =E2=80=98kill=E2=80=99; did you mean =E2=
=80=98_kill=E2=80=99?
[-Wimplicit-function-declaration]
[   75s]    61 |   if ((ret =3D _kill (pid, sig)) =3D=3D -1 && errn=
o !=3D 0)

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

You are on the CC list for the bug.

=

--17175164710.834D9c.16638--


--17175179131.1e10.16683
Date: Tue, 4 Jun 2024 16:18: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=3D1225956

            Bug ID: 1225956
           Summary: Package xf86-video-nouveau does not build with gcc14 because of new errors
    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: mjambor-at-suse.com
        QA Contact: gfx-bugs-at-suse.de
            Blocks: 1220571
  Target Milestone: ---
          Found By: ---
           Blocker: ---

GCC 14 newly by default treats as errors a number of situations which
before were only warnings.  For more information see
https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571.

Because of this, package xf86-video-nouveau fails to compile.  This can be =
seen
online
at:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:=
Gcc7/xf86-video-nouveau/standard/x86_64

It can be reproduced locally with command: osc build --clean
--alternative-project home:rguenther:nextgcc

There's a Gentoo bug which might be relevant:
https://bugs.gentoo.org/885763

The (first) error (that halts the build) is:

[   15s] nv_driver.c: In function 'NVScreenInit':
[   15s] nv_driver.c:1451:23: error: implicit declaration of function
'wfbScreenInit'; did you mean 'fbScreenInit'? [-Wimplicit-function-declarat=
ion]
[   15s]  1451 |                 ret =3D wfbScreenInit(pScreen, FBStart,
pScrn->virtualX,
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17175179131.1e10.16683
Date: Tue, 4 Jun 2024 16:18: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
          1225956

          Summary
          Package xf86-video-nouveau does not build with gcc14 because =
of new errors

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

          QA Contact
          gfx-bugs@suse.de

          Blocks
          1220571

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

GCC 14 newly by default treats as errors a number of situati=
ons which
before were only warnings.  For more information see
https://gcc.gnu.org/=
gcc-14/porting_to.html and meta bug #1220571.

Because of this, package xf86-video-nouveau fails to compile.  This can be =
seen
online
at:
https://build.opensuse.=
org/package/live_build_log/openSUSE:Factory:Staging:Gcc7/xf86-video-nouveau=
/standard/x86_64

It can be reproduced locally with command: osc build --clean
--alternative-project home:rguenther:nextgcc

There's a Gentoo bug which might be relevant:
https://bugs.gentoo.org/885763</=
a>

The (first) error (that halts the build) is:

[   15s] nv_driver.c: In function 'NVScreenInit':
[   15s] nv_driver.c:1451:23: error: implicit declaration of function
'wfbScreenInit'; did you mean 'fbScreenInit'? [-Wimplicit-function-declarat=
ion]
[   15s]  1451 |                 ret =3D wfbScreenInit(pScreen, FBStart,
pScrn->virtualX,

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

You are on the CC list for the bug.

=

--17175179131.1e10.16683--


--17175246910.9EDEbC153.16890
Date: Tue, 4 Jun 2024 18:11:31 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1225961
           Summary: plasmashell crashes with SIGTRAP starting with snapshot 20240531
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: marcec-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 875305
  --> https://bugzilla.suse.com/attachment.cgi?id=3D875305&action=3Dedit
Example core dump

Since upgrading to snapshot 20240531 plasmashell crashes consistently.  The
only way I've found to prevent it is to change the AppArmor profile from
"enforce" to "complain".  What I want to figure out is whether this is due =
to a
bug or an (accidental) misconfiguration on my end.

Manually running `plasmashell --replace` in a terminal gave the following
output:

% cat tmp/plasma_bug.log=20
KPackageStructure of KPluginMetaData(pluginId:"org.kde.plasma.worldclock",
fileName:
"/usr/share/plasma/plasmoids/org.kde.plasma.worldclock/metadata.json") does=
 not
match requested format "Plasma/Applet"
kf.coreaddons: The plugin
"/usr/lib64/qt6/plugins/plasma5support/dataengine/plasma_engine_wacomtablet=
.so"
explicitly states an Id in the embedded metadata, which is different from t=
he
one derived from the filename The Id field from the KPlugin object in the
metadata should be removed
kf.plasma.quick: Applet preload policy set to 1
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/m=
ain.qml:196:25:
QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding
loop detected for property "minimumWidth"
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:14:1:
QML WallpaperItem: grabToImage: item's window is not visible
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/m=
ain.qml:196:25:
QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding
loop detected for property "minimumWidth"
Path override failed for key base::DIR_APP_DICTIONARIES and path
'/usr/bin/qtwebengine_dictionaries'
LaunchProcess: failed to execvp:
/usr/libexec/qt6/QtWebEngineProcess
LaunchProcess: failed to execvp:
/usr/libexec/qt6/QtWebEngineProcess
[13751:13751:0603/211905.963992:FATAL:zygote_host_impl_linux.cc(208)] Check
failed: . : Datei oder Verzeichnis nicht gefunden (2)

(I couldn't figure out how to get the error message in English, exporting
LANG=3DC or LC_ALL=3DC before running didn't work. In any case it's "file or
directory not found".)

(An example core dump as produced by `coredumpctl info` is also attached.)

Googling for that final error message led me to various reports relating to
Chrome having issues with AppArmor, which led me to the above-mentioned
workaround.  Running `sudo aa-complain plasmashell` allowed me to run
plasmashell again.

For completeness: before the workaround, the audit log contained lines like=
 the
following:

type=3DAVC msg=3Daudit(1717438261.829:263): apparmor=3D"DENIED" operation=
=3D"exec"
class=3D"file" info=3D"no new privs" error=3D-1 profile=3D"plasmashell"
name=3D"/usr/libexec/qt6/QtWebEngineProcess" pid=3D6473 comm=3D"plasmashell"
requested_mask=3D"x" denied_mask=3D"x" fsuid=3D1000 ouid=3D0 target=3D"unco=
nfined"

After the workaround the audit log has two lines like this:

393:type=3DAVC msg=3Daudit(1717485012.556:257): apparmor=3D"ALLOWED" operat=
ion=3D"exec"
class=3D"file" info=3D"no new privs" error=3D-1 profile=3D"plasmashell"
name=3D"/usr/libexec/qt6/QtWebEngineProcess" pid=3D2403 comm=3D"plasmashell"
requested_mask=3D"x" denied_mask=3D"x" fsuid=3D1000 ouid=3D0 target=3D"unco=
nfined"
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17175246910.9EDEbC153.16890
Date: Tue, 4 Jun 2024 18:11:31 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1225961

          Summary
          plasmashell crashes with SIGTRAP starting with snapshot 20240=
531

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          KDE Workspace (Plasma)

          Assignee
          opensuse-kde-bugs@opensuse.org

          Reporter
          marcec@gmx.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment 875305 [details]
Example core dump

Since upgrading to snapshot 20240531 plasmashell crashes consistently.  The
only way I've found to prevent it is to change the AppArmor profile from
"enforce" to "complain".  What I want to figure out is =
whether this is due to a
bug or an (accidental) misconfiguration on my end.

Manually running `plasmashell --replace` in a terminal gave the following
output:

% cat tmp/plasma_bug.log=20
KPackageStructure of KPluginMetaData(pluginId:"org.kde.plasma.worldclo=
ck",
fileName:
"/usr/share/plasma/plasmoids/org.kde.plasma.worldclock/metadata.json&q=
uot;) does not
match requested format "Plasma/Applet"
kf.coreaddons: The plugin
"/usr/lib64/qt6/plugins/plasma5support/dataengine/plasma_engine_wacomt=
ablet.so"
explicitly states an Id in the embedded metadata, which is different from t=
he
one derived from the filename The Id field from the KPlugin object in the
metadata should be removed
kf.plasma.quick: Applet preload policy set to 1
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/m=
ain.qml:196:25:
QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding
loop detected for property "minimumWidth"
file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:14:1:
QML WallpaperItem: grabToImage: item's window is not visible
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/m=
ain.qml:196:25:
QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding
loop detected for property "minimumWidth"
Path override failed for key base::DIR_APP_DICTIONARIES and path
'/usr/bin/qtwebengine_dictionaries'
LaunchProcess: failed to execvp:
/usr/libexec/qt6/QtWebEngineProcess
LaunchProcess: failed to execvp:
/usr/libexec/qt6/QtWebEngineProcess
[13751:13751:0603/211905.963992:FATAL:zygote_host_impl_linux.cc(208)] Check
failed: . : Datei oder Verzeichnis nicht gefunden (2)

(I couldn't figure out how to get the error message in English, exporting
LANG=3DC or LC_ALL=3DC before running didn't work. In any case it's "f=
ile or
directory not found".)

(An example core dump as produced by `coredumpctl info` is also attached.)

Googling for that final error message led me to various reports relating to
Chrome having issues with AppArmor, which led me to the above-mentioned
workaround.  Running `sudo aa-complain plasmashell` allowed me to run
plasmashell again.

For completeness: before the workaround, the audit log contained lines like=
 the
following:

type=3DAVC msg=3Daudit(1717438261.829:263): apparmor=3D"DENIED" o=
peration=3D"exec"
class=3D"file" info=3D"no new privs" error=3D-1 profile=
=3D"plasmashell"
name=3D"/usr/libexec/qt6/QtWebEngineProcess" pid=3D6473 comm=3D&q=
uot;plasmashell"
requested_mask=3D"x" denied_mask=3D"x" fsuid=3D1000 oui=
d=3D0 target=3D"unconfined"

After the workaround the audit log has two lines like this:

393:type=3DAVC msg=3Daudit(1717485012.556:257): apparmor=3D"ALLOWED&qu=
ot; operation=3D"exec"
class=3D"file" info=3D"no new privs" error=3D-1 profile=
=3D"plasmashell"
name=3D"/usr/libexec/qt6/QtWebEngineProcess" pid=3D2403 comm=3D&q=
uot;plasmashell"
requested_mask=3D"x" denied_mask=3D"x" fsuid=3D1000 oui=
d=3D0 target=3D"unconfined"

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

You are on the CC list for the bug.

=

--17175246910.9EDEbC153.16890--


--17175544730.Dd4cDF7b.17274
Date: Wed, 5 Jun 2024 02:27: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=3D1225969

            Bug ID: 1225969
           Summary: kdig in knot does not support DoH(+https) query
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: smbd.jp-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

An upstream kdig supports DoH(DNS over HTTPS) query and its option is "+htt=
ps".
But, SuSE's does not.

Please enable it.

---
upstream$ kdig +https @8.8.8.8 www.google.com
;; TLS session (TLS1.3)-(ECDHE-X25519)-(RSA-PSS-RSAE-SHA256)-(AES-256-GCM)
;; HTTP session (HTTP/2-POST)-(8.8.8.8/dns-query)-(status: 200)
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 0
;; Flags: qr rd ra; QUERY: 1; ANSWER: 1; AUTHORITY: 0; ADDITIONAL: 1

;; EDNS PSEUDOSECTION:
;; Version: 0; flags: ; UDP size: 512 B; ext-rcode: NOERROR
;; PADDING: 405 B

;; QUESTION SECTION:
;; www.google.com.              IN      A

;; ANSWER SECTION:
www.google.com.         300     IN      A       142.250.207.4

;; Received 468 B
;; Time 2024-06-05 11:17:21 JST
;; From 8.8.8.8@443(HTTPS) in 56.9 ms

upstream$ kdig --help | grep https
       +[no]https[=3DURL]           Use HTTPS protocol. It's also possible =
to
specify
       +[no]https-get             Use HTTPS protocol with GET method instea=
d of
POST.

upstream$ $ ldd /usr/bin/kdig|grep http
        libnghttp2.so.14 =3D> /usr/lib64/libnghttp2.so.14 (0x00007f19121780=
00)

---
suse$ kdig +https @8.8.8.8 www.google.com
Usage: kdig [-4] [-6] [-d] [-b address] [-c class] [-p port]
            [-q name] [-t type] [-x address] [-k keyfile]
            [-y [algo:]keyname:key] [-E tapfile] [-G tapfile]
            name [type] [class] [@server]

       +[no]multiline             Wrap long records to more lines.
       +[no]short                 Show record data only.
(snip)

suse$ kdig --help | grep https
(not match)

suse$ ldd /usr/bin/kdig|grep http
(not match)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17175544730.Dd4cDF7b.17274
Date: Wed, 5 Jun 2024 02:27: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
          1225969

          Summary
          kdig in knot does not support DoH(+https) query

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Network

          Assignee
          screening-team-bugs@suse.de

          Reporter
          smbd.jp@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

An upstream kdig supports DoH(DNS over HTTPS) query and its =
option is "+https".
But, SuSE's does not.

Please enable it.

---
upstream$ kdig +https @8.8.8.8 www.google.com
;; TLS session (TLS1.3)-(ECDHE-X25519)-(RSA-PSS-RSAE-SHA256)-(AES-256-GCM)
;; HTTP session (HTTP/2-POST)-(8.8.8.8/dns-query)-(status: 200)
;; ->>HEADER<<- opcode: QUERY; status: NOERROR; id: 0
;; Flags: qr rd ra; QUERY: 1; ANSWER: 1; AUTHORITY: 0; ADDITIONAL: 1

;; EDNS PSEUDOSECTION:
;; Version: 0; flags: ; UDP size: 512 B; ext-rcode: NOERROR
;; PADDING: 405 B

;; QUESTION SECTION:
;; www.google.com.              IN      A

;; ANSWER SECTION:
www.google.com.         300     IN      A       142.250.207.4

;; Received 468 B
;; Time 2024-06-05 11:17:21 JST
;; From 8.8.8.8@443(HTTPS) in 56.9 ms

upstream$ kdig --help | grep https
       +[no]https[=3DURL]           Use HTTPS protocol. It's also possible =
to
specify
       +[no]https-get             Use HTTPS protocol with GET method instea=
d of
POST.

upstream$ $ ldd /usr/bin/kdig|grep http
        libnghttp2.so.14 =3D> /usr/lib64/libnghttp2.so.14 (0x00007f19121=
78000)

---
suse$ kdig +https @8.8.8.8 www.google.com
Usage: kdig [-4] [-6] [-d] [-b address] [-c class] [-p port]
            [-q name] [-t type] [-x address] [-k keyfile]
            [-y [algo:]keyname:key] [-E tapfile] [-G tapfile]
            name [type] [class] [@server]

       +[no]multiline             Wrap long records to more lines.
       +[no]short                 Show record data only.
(snip)

suse$ kdig --help | grep https
(not match)

suse$ ldd /usr/bin/kdig|grep http
(not match)

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

You are on the CC list for the bug.

=

--17175544730.Dd4cDF7b.17274--


body:
--17175759420.e7e471C.18114
Date: Wed, 5 Jun 2024 08:25: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=3D1225984

            Bug ID: 1225984
           Summary: [SELinux] GDM avcs for wtmp.db-journal
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: filippo.bonazzi-at-suse.com
        QA Contact: security-team-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Operating System: Tumbleweed
SELinux status, mode and policy name: permissive, targeted
SELinux policy version and repository: 20240411-231.2 from Security:SELinux
The software (incl. version) that is affected by the SELinux issue and the
error message: gdm-session-worker
SELinux Audit log:

time->Wed Jun  5 10:05:30 2024
type=3DAVC msg=3Daudit(1717574730.824:139): avc:  denied  { add_name } for=
=20
pid=3D1704 comm=3D"gdm-session-wor" name=3D"wtmp.db-journal"
scontext=3Dsystem_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:wtmp_t:s0 tclass=3Ddir permissive=3D1
----
time->Wed Jun  5 10:05:30 2024
type=3DAVC msg=3Daudit(1717574730.824:140): avc:  denied  { create } for  p=
id=3D1704
comm=3D"gdm-session-wor" name=3D"wtmp.db-journal"
scontext=3Dsystem_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:wtmp_t:s0 tclass=3Dfile permissive=3D1
----
time->Wed Jun  5 10:05:30 2024
type=3DAVC msg=3Daudit(1717574730.824:141): avc:  denied  { setattr } for  =
pid=3D1704
comm=3D"gdm-session-wor" name=3D"wtmp.db-journal" dev=3D"vda2" ino=3D158633
scontext=3Dsystem_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:wtmp_t:s0 tclass=3Dfile permissive=3D1
----
time->Wed Jun  5 10:05:30 2024
type=3DAVC msg=3Daudit(1717574730.961:142): avc:  denied  { remove_name } f=
or=20
pid=3D1704 comm=3D"gdm-session-wor" name=3D"wtmp.db-journal" dev=3D"vda2" i=
no=3D158633
scontext=3Dsystem_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:wtmp_t:s0 tclass=3Ddir permissive=3D1
----
time->Wed Jun  5 10:05:30 2024
type=3DAVC msg=3Daudit(1717574730.961:143): avc:  denied  { unlink } for  p=
id=3D1704
comm=3D"gdm-session-wor" name=3D"wtmp.db-journal" dev=3D"vda2" ino=3D158633
scontext=3Dsystem_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:wtmp_t:s0 tclass=3Dfile permissive=3D1
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17175759420.e7e471C.18114
Date: Wed, 5 Jun 2024 08:25: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
          1225984

          Summary
          [SELinux] GDM avcs for wtmp.db-journal

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Security

          Assignee
          security-team@suse.de

          Reporter
          filippo.bonazzi@suse.com

          QA Contact
          security-team@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Operating System: Tumbleweed
SELinux status, mode and policy name: permissive, targeted
SELinux policy version and repository: 20240411-231.2 from Security:SELinux
The software (incl. version) that is affected by the SELinux issue and the
error message: gdm-session-worker
SELinux Audit log:

time->Wed Jun  5 10:05:30 2024
type=3DAVC msg=3Daudit(1717574730.824:139): avc:  denied  { add_name } for=
=20
pid=3D1704 comm=3D"gdm-session-wor" name=3D"wtmp.db-journal&=
quot;
scontext=3Dsystem_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:wtmp_t:s0 tclass=3Ddir permissive=3D1
----
time->Wed Jun  5 10:05:30 2024
type=3DAVC msg=3Daudit(1717574730.824:140): avc:  denied  { create } for  p=
id=3D1704
comm=3D"gdm-session-wor" name=3D"wtmp.db-journal"
scontext=3Dsystem_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:wtmp_t:s0 tclass=3Dfile permissive=3D1
----
time->Wed Jun  5 10:05:30 2024
type=3DAVC msg=3Daudit(1717574730.824:141): avc:  denied  { setattr } for  =
pid=3D1704
comm=3D"gdm-session-wor" name=3D"wtmp.db-journal" dev=
=3D"vda2" ino=3D158633
scontext=3Dsystem_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:wtmp_t:s0 tclass=3Dfile permissive=3D1
----
time->Wed Jun  5 10:05:30 2024
type=3DAVC msg=3Daudit(1717574730.961:142): avc:  denied  { remove_name } f=
or=20
pid=3D1704 comm=3D"gdm-session-wor" name=3D"wtmp.db-journal&=
quot; dev=3D"vda2" ino=3D158633
scontext=3Dsystem_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:wtmp_t:s0 tclass=3Ddir permissive=3D1
----
time->Wed Jun  5 10:05:30 2024
type=3DAVC msg=3Daudit(1717574730.961:143): avc:  denied  { unlink } for  p=
id=3D1704
comm=3D"gdm-session-wor" name=3D"wtmp.db-journal" dev=
=3D"vda2" ino=3D158633
scontext=3Dsystem_u:system_r:xdm_t:s0-s0:c0.c1023
tcontext=3Dsystem_u:object_r:wtmp_t:s0 tclass=3Dfile permissive=3D1

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

You are on the CC list for the bug.

=

--17175759420.e7e471C.18114--

summary: [SELinux] GDM avcs for wtmp.db-journal


--17175814043.EeaABa51.18447
Date: Wed, 5 Jun 2024 09:56:44 +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=3D1225992

            Bug ID: 1225992
           Summary: Package ipmitool does not build with gcc14 because of new errors
    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: mjambor-at-suse.com
        QA Contact: qa-bugs-at-suse.de
            Blocks: 1220571
  Target Milestone: ---
          Found By: ---
           Blocker: ---

GCC 14 newly by default treats as errors a number of situations which
before were only warnings.  For more information see
https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571.

Because of this, package ipmitool fails to compile.  This can be seen online
at:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:=
Gcc7/ipmitool/standard/x86_64

It can be reproduced locally with command: osc build --clean
--alternative-project home:rguenther:nextgcc

The (first) error (that halts the build) is:

[   15s] ipmi_fru.c: In function 'fru_area_print_multirec':
[   15s] ipmi_fru.c:1556:41: error: initialization of 'struct
fru_multirec_mgmt *' from incompatible pointer type 'struct
fru_multirect_mgmt *' [-Wincompatible-pointer-types]
[   15s]  1556 |                                         (struct
fru_multirect_mgmt *)
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17175814043.EeaABa51.18447
Date: Wed, 5 Jun 2024 09:56:44 +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
          1225992

          Summary
          Package ipmitool does not build with gcc14 because of new err=
ors

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

          QA Contact
          qa-bugs@suse.de

          Blocks
          1220571

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

GCC 14 newly by default treats as errors a number of situati=
ons which
before were only warnings.  For more information see
https://gcc.gnu.org/=
gcc-14/porting_to.html and meta bug #1220571.

Because of this, package ipmitool fails to compile.  This can be seen online
at:
https://build.opensuse.org/packag=
e/live_build_log/openSUSE:Factory:Staging:Gcc7/ipmitool/standard/x86_64

It can be reproduced locally with command: osc build --clean
--alternative-project home:rguenther:nextgcc

The (first) error (that halts the build) is:

[   15s] ipmi_fru.c: In function &#39;fru_area_print_multirec&#39;:
[   15s] ipmi_fru.c:1556:41: error: initialization of &#39;struct
fru_multirec_mgmt *&#39; from incompatible pointer type &#39;struct
fru_multirect_mgmt *&#39; [-Wincompatible-pointer-types]
[   15s]  1556 |                                         (struct
fru_multirect_mgmt *)

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

You are on the CC list for the bug.

=

--17175814043.EeaABa51.18447--


body:
--17176633872.ebD0f1b.20774
Date: Thu, 6 Jun 2024 08:43:07 +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=3D1226031

            Bug ID: 1226031
           Summary: apparmor stops working due to "aa-logprof   ERROR: Can't parse mount rule mount             ""      -> "/","
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: martin.jedamzik-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Recently noticed that my dovecot server was not accessible anymore.=20

Checking the logs showed:

Jun 06 09:27:27 papa3 dovecot[6023]: auth: Error: Jun 06 09:27:27
service(auth): Fatal: execv(/usr/lib/dovecot/auth) failed: Permission denied

After some investigation I found the culprit, Apparmor was not working
properly:

papa3:/etc/apparmor.d/abstractions # aa-logprof=20

ERROR: Can't parse mount rule mount             ""      -> "/",

Root cause are these statements in /etc/apparmor.d/abstractions/[passt|past=
a]:

passt:
  mount options=3D(rw, runbindable) -> /,
  #mount    ""  -> "/",
  #mount    ""  -> "/tmp/",
  pivot_root  "/tmp/" -> "/tmp/",
  #umount "/",

pasta:

#mount    ""  -> "/proc/",

Current version of PASST : passt-20240523.765eb0b-1.1.x86_64
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17176633872.ebD0f1b.20774
Date: Thu, 6 Jun 2024 08:43:07 +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
          1226031

          Summary
          apparmor stops working due to "aa-logprof   ERROR: Can't=
 parse mount rule mount             ""      -> "/",&=
quot;

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          AppArmor

          Assignee
          suse-beta@cboltz.de

          Reporter
          martin.jedamzik@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Recently noticed that my dovecot server was not accessible a=
nymore.=20

Checking the logs showed:

Jun 06 09:27:27 papa3 dovecot[6023]: auth: Error: Jun 06 09:27:27
service(auth): Fatal: execv(/usr/lib/dovecot/auth) failed: Permission denied

After some investigation I found the culprit, Apparmor was not working
properly:

papa3:/etc/apparmor.d/abstractions # aa-logprof=20

ERROR: Can't parse mount rule mount             ""      -> &qu=
ot;/",

Root cause are these statements in /etc/apparmor.d/abstractions/[passt|past=
a]:

passt:
  mount options=3D(rw, runbindable) -> /,
  #mount    ""  -> "/",
  #mount    ""  -> "/tmp/",
  pivot_root  "/tmp/" -> "/tmp/",
  #umount "/",

pasta:

#mount    ""  -> "/proc/",

Current version of PASST : passt-20240523.765eb0b-1.1.x86_64

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

You are on the CC list for the bug.

=

--17176633872.ebD0f1b.20774--

pkgs: apparmor kernel-source


--17178600320.EFafc.32378
Date: Sat, 8 Jun 2024 15:20:32 +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=3D1226112

            Bug ID: 1226112
           Summary: Supersede kmozillahelper by xdg-desktop-portal integration
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: Firefox
          Assignee: factory-mozilla-at-lists.opensuse.org
          Reporter: fabian@ritter-vogt.de
        QA Contact: qa-bugs-at-suse.de
                CC: opensuse-kde-bugs-at-opensuse.org
  Target Milestone: ---
          Found By: ---
           Blocker: ---

For some time now, Firefox (and Thunderbird I hope) can use xdg-desktop-por=
tal
APIs for DE integration. We should try to migrate away from kmozillahelper =
in
favor of using the builtin xdg-desktop-portal integration.

For that, we need to make sure that on Plasma it uses xdg-desktop-portal
instead of GTK file dialogs out of the box. Currently this needs to be done
manually by setting

widget.use-xdg-desktop-portal.file-picker=3D1
widget.use-xdg-desktop-portal.mime-handler=3D1

I'm not sure about widget.use-xdg-desktop-portal.open-uri.

Can we get FF and TB configured such that it uses xdg-desktop-portal by def=
ault
if it detects a Plasma session?
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17178600320.EFafc.32378
Date: Sat, 8 Jun 2024 15:20:32 +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
          1226112

          Summary
          Supersede kmozillahelper by xdg-desktop-portal integration

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Enhancement

          Priority
          P5 - None

          Component
          Firefox

          Assignee
          factory-mozilla@lists.opensuse.org

          Reporter
          fabian@ritter-vogt.de

          QA Contact
          qa-bugs@suse.de

          CC
          opensuse-kde-bugs@opensuse.org

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

For some time now, Firefox (and Thunderbird I hope) can use =
xdg-desktop-portal
APIs for DE integration. We should try to migrate away from kmozillahelper =
in
favor of using the builtin xdg-desktop-portal integration.

For that, we need to make sure that on Plasma it uses xdg-desktop-portal
instead of GTK file dialogs out of the box. Currently this needs to be done
manually by setting

widget.use-xdg-desktop-portal.file-picker=3D1
widget.use-xdg-desktop-portal.mime-handler=3D1

I'm not sure about widget.use-xdg-desktop-portal.open-uri.

Can we get FF and TB configured such that it uses xdg-desktop-portal by def=
ault
if it detects a Plasma session?

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

You are on the CC list for the bug.

=

--17178600320.EFafc.32378--


--17179365942.D4c3Bb1a4.32594
Date: Sun, 9 Jun 2024 12:36: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=3D1226119

            Bug ID: 1226119
           Summary: libqt5-qtwebengine: remove dependency on older re2
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

libqt5-qtwebengine needs an older re2, this has been the case for ever a ye=
ar
now:

> # re2 >=3D 2023-07-01 breaks the build, use libre2-10-devel if needed
> BuildRequires:  pkgconfig(re2) <=3D 10.0.0

Back then that was the only package that broke like that, the maintainer
rejected building using the bundled library, and we had to introduce re2-10
transitional package. It has been a year now. Please patch libqt5-qtwebengi=
ne
to build with a current version of re2, or use the bundled version.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17179365942.D4c3Bb1a4.32594
Date: Sun, 9 Jun 2024 12:36: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
          1226119

          Summary
          libqt5-qtwebengine: remove dependency on older re2

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          KDE Applications

          Assignee
          opensuse-kde-bugs@opensuse.org

          Reporter
          Andreas.Stieger@gmx.de

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

libqt5-qtwebengine needs an older re2, this has been the cas=
e for ever a year
now:

> # re2 >=3D 2023-07-01 breaks the build, use l=
ibre2-10-devel if needed
> BuildRequires:  pkgconfig(re2) <=3D 10.0.0

Back then that was the only package that broke like that, the maintainer
rejected building using the bundled library, and we had to introduce re2-10
transitional package. It has been a year now. Please patch libqt5-qtwebengi=
ne
to build with a current version of re2, or use the bundled version.

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

You are on the CC list for the bug.

=

--17179365942.D4c3Bb1a4.32594--


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

I tried to install Aeon on a machine with 2 encrypted partitions on my driv=
e,
one with openSUSE Tumbleweed, one with just Steam Games.

The installation process failed after entering both password.
For detail, please see the attached log.
https://pastebin.com/56iR3shE

Reproducible: Didn't try

Actual Results:=20=20
Tik Installer fails

Expected Results:=20=20
Tik installer resumes

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

You are on the CC list for the bug.

=

--17179393700.9a63810A.32603--

summary: Tik Installer fails to unmount mounted encrypted drive


body:
--17179562321.ad18cAE31.32677
Date: Sun, 9 Jun 2024 18:03:52 +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=3D1226122

            Bug ID: 1226122
           Summary: TW installation leaves /boot empty
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Installation
          Assignee: yast2-maintainers-at-suse.de
          Reporter: mario_bz-at-mgtech.com
        QA Contact: jsrain-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 875388
  --> https://bugzilla.suse.com/attachment.cgi?id=3D875388&action=3Dedit
zypp log from installation

Installing TW from June 7 image. I select not to install any boot manager
because I use Refind on Mac. Note I have installed Opensuse and TW this way=
 for
15 years on multiple macs, leaving Grub out. In all cases installation alwa=
ys
worked fine and booted, the last fresh TW install 2 years ago is still good=
. I
decided to do a clean install of TW to check on other problems I am having.
However, although the kernel is placed in /usr/lib/modules, the/boot direct=
ory
is left empty except for the kernel cleanup script. I tried:

1. Copying my working kernel from a TW to /boot and /usr/lib/modules. I was
able to boot that kernel. While booted I did a force installation of the ke=
rnel
in YAST, but again, nothing was put into /boot.

2. I reinstalled using both btrf which I normally use, and xfs to see if bt=
rfs
was the issue. No change.

I searched for hours trying to find this issue and found someone had the sa=
me
thing after updating, that was a couple of years ago and they just added
symlinks. I my case, I could not do that because initrd modules were missing
which are not symlinks. Since I cant find anyone having this issue recently=
, I
am assuming it's related to the fact I selected not to install boot manager.

At this point I can't get a new install working. Some people really need to
install without a boot manager, Opensuse and TW made it easy. I assume it's=
 not
a design change since it would make no sense to leave /boot empty.

If you want any logs, please let me know where they are, I could not find an
installation log.

I attached the zypp log I found. It does not have a reference to /boot
anywhere.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17179562321.ad18cAE31.32677
Date: Sun, 9 Jun 2024 18:03:52 +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
          1226122

          Summary
          TW installation leaves /boot empty

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Major

          Priority
          P5 - None

          Component
          Installation

          Assignee
          yast2-maintainers@suse.de

          Reporter
          mario_bz@mgtech.com

          QA Contact
          jsrain@suse.com

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

Created attachment =
875388 [details]
zypp log from installation

Installing TW from June 7 image. I select not to install any boot manager
because I use Refind on Mac. Note I have installed Opensuse and TW this way=
 for
15 years on multiple macs, leaving Grub out. In all cases installation alwa=
ys
worked fine and booted, the last fresh TW install 2 years ago is still good=
. I
decided to do a clean install of TW to check on other problems I am having.
However, although the kernel is placed in /usr/lib/modules, the/boot direct=
ory
is left empty except for the kernel cleanup script. I tried:

1. Copying my working kernel from a TW to /boot and /usr/lib/modules. I was
able to boot that kernel. While booted I did a force installation of the ke=
rnel
in YAST, but again, nothing was put into /boot.

2. I reinstalled using both btrf which I normally use, and xfs to see if bt=
rfs
was the issue. No change.

I searched for hours trying to find this issue and found someone had the sa=
me
thing after updating, that was a couple of years ago and they just added
symlinks. I my case, I could not do that because initrd modules were missing
which are not symlinks. Since I cant find anyone having this issue recently=
, I
am assuming it's related to the fact I selected not to install boot manager.

At this point I can't get a new install working. Some people really need to
install without a boot manager, Opensuse and TW made it easy. I assume it's=
 not
a design change since it would make no sense to leave /boot empty.

If you want any logs, please let me know where they are, I could not find an
installation log.

I attached the zypp log I found. It does not have a reference to /boot
anywhere.

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

You are on the CC list for the bug.

=

--17179562321.ad18cAE31.32677--

summary: TW installation leaves /boot empty


--17180272510.AaC51A.3494
Date: Mon, 10 Jun 2024 13:47:31 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1226151
           Summary: Missing lxqt-qtplugin and libfm-qt qt5 versions for qt5 integration in lxqt 2.0.x
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LXQt
          Assignee: lxqt-bugs-at-suse.de
          Reporter: brbigam-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

LXQt 2.0.0 using qt6 is in Tumbleweed now, but a few libraries are recommen=
ded
by upstream to have co-installable qt5 and qt6 versions for integration. Th=
ese
include lxqt-build-tools, lxqt-qtplugin, libfm-qt, and libqtxdg.

The qt5 versions of lxqt-qtplugin and libfm-qt are missing and not installa=
ble
in Tumbleweed. These are the 1.4.x versions of these libraries. See the rel=
ease
notes here: https://lxqt-project.org/release/2024/04/15/release-lxqt-2-0-0/
section "Note for Distros."

Result: qt5 apps running within LXQt 2.0.0 on Tumbleweed are not integrated
with theming and the LXQt file dialog.

Steps to reproduce:
1. Install and run LXQt 2.0.x on Tumbleweed
2. Set Appearance settings according to your preferences, and check the res=
ults
in any qt6 app
3. Install and open any qt5 app, such as VLC

Actual results:
qt5 apps do not follow any theme settings set by the LXQt appearance settin=
gs,
regarding qt widget style, fonts, etc. qt6 apps do follow theming.
qt5 apps use the fallback qt file dialog, while qt6 apps use LXQt file dial=
og.

Expected results:
qt5 apps follow the same style and font settings as qt6 apps, as set in
Appearance settings.=20
qt5 and qt6 apps all use the LXQt file dialog.

openSUSE Tumbleweed 2024 early June release (I found the problem Monday, Ju=
ne
2, at the then-current release, when LXQt 2.0 first landed in Tumbleweed) on
Asus Vivobook M513I

First bug report here, please be gentle if I've missed something essential.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17180272510.AaC51A.3494
Date: Mon, 10 Jun 2024 13:47:31 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1226151

          Summary
          Missing lxqt-qtplugin and libfm-qt qt5 versions for qt5 integ=
ration in lxqt 2.0.x

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          LXQt

          Assignee
          lxqt-bugs@suse.de

          Reporter
          brbigam@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

LXQt 2.0.0 using qt6 is in Tumbleweed now, but a few librari=
es are recommended
by upstream to have co-installable qt5 and qt6 versions for integration. Th=
ese
include lxqt-build-tools, lxqt-qtplugin, libfm-qt, and libqtxdg.

The qt5 versions of lxqt-qtplugin and libfm-qt are missing and not installa=
ble
in Tumbleweed. These are the 1.4.x versions of these libraries. See the rel=
ease
notes here: https://lxqt-project.org/release/2024/04/15/release-lxqt-2-0-0=
/
section "Note for Distros."

Result: qt5 apps running within LXQt 2.0.0 on Tumbleweed are not integrated
with theming and the LXQt file dialog.

Steps to reproduce:
1. Install and run LXQt 2.0.x on Tumbleweed
2. Set Appearance settings according to your preferences, and check the res=
ults
in any qt6 app
3. Install and open any qt5 app, such as VLC

Actual results:
qt5 apps do not follow any theme settings set by the LXQt appearance settin=
gs,
regarding qt widget style, fonts, etc. qt6 apps do follow theming.
qt5 apps use the fallback qt file dialog, while qt6 apps use LXQt file dial=
og.

Expected results:
qt5 apps follow the same style and font settings as qt6 apps, as set in
Appearance settings.=20
qt5 and qt6 apps all use the LXQt file dialog.

openSUSE Tumbleweed 2024 early June release (I found the problem Monday, Ju=
ne
2, at the then-current release, when LXQt 2.0 first landed in Tumbleweed) on
Asus Vivobook M513I

First bug report here, please be gentle if I've missed something essential.=

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

You are on the CC list for the bug.

=

--17180272510.AaC51A.3494--


body:
--17180332262.Ce5a.3817
Date: Mon, 10 Jun 2024 15:27: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=3D1226157

            Bug ID: 1226157
           Summary: sssd: missing /etc/sssd/sssd.conf
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: gcomes.obs-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I use sssd. I normally edit /etc/sssd/sssd.conf in order to configure the
package. In Leap 15.6 such file does not exist. I found in the packages sssd
the file /usr/lib64/sssd/conf/sssd.conf and, for testing, I made my changes
there.
When I started sssd.service it didn't start. The presence of
/etc/sssd/sssd.conf is required for the service to run although I didn't fi=
nd
any reference in /usr/share/doc/packages/sssd to the fact that the user is =
now
required to create /etc/sssd/sssd.conf from scratch.
I then made a copy of /usr/lib64/sssd/conf/sssd.conf to /etc/sssd/sssd.conf=
 and
changed it. When I started sssd.service it didn't start. The file
/etc/sssd/sssd.conf can be readable only by root, but the file
/usr/lib64/sssd/conf/sssd.conf did not have such permission and when I made=
 the
copy, /etc/sssd/sssd.conf was world readable as well. After changing the
permission of /etc/sssd/sssd.conf I was finally able to start sssd.service.

Please does not make such disruptive changes without giving the user indica=
tion
about what it is required to do (that was not required before) before the
program can be used.
I suggest to put back /etc/sssd/sssd.conf with proper permission containing
only commented lines explaining what and why the changes were made and what=
 the
user is supposed to do now.
In this way may be other users will not go through the painful trial and er=
ror
process as I did, before being able to use sssd in Leap 15.6.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17180332262.Ce5a.3817
Date: Mon, 10 Jun 2024 15:27: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
          1226157

          Summary
          sssd: missing /etc/sssd/sssd.conf

          Classification
          openSUSE

          Product
          openSUSE Distribution

          Version
          Leap 15.6

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          gcomes.obs@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I use sssd. I normally edit /etc/sssd/sssd.conf in order to =
configure the
package. In Leap 15.6 such file does not exist. I found in the packages sssd
the file /usr/lib64/sssd/conf/sssd.conf and, for testing, I made my changes
there.
When I started sssd.service it didn't start. The presence of
/etc/sssd/sssd.conf is required for the service to run although I didn't fi=
nd
any reference in /usr/share/doc/packages/sssd to the fact that the user is =
now
required to create /etc/sssd/sssd.conf from scratch.
I then made a copy of /usr/lib64/sssd/conf/sssd.conf to /etc/sssd/sssd.conf=
 and
changed it. When I started sssd.service it didn't start. The file
/etc/sssd/sssd.conf can be readable only by root, but the file
/usr/lib64/sssd/conf/sssd.conf did not have such permission and when I made=
 the
copy, /etc/sssd/sssd.conf was world readable as well. After changing the
permission of /etc/sssd/sssd.conf I was finally able to start sssd.service.

Please does not make such disruptive changes without giving the user indica=
tion
about what it is required to do (that was not required before) before the
program can be used.
I suggest to put back /etc/sssd/sssd.conf with proper permission containing
only commented lines explaining what and why the changes were made and what=
 the
user is supposed to do now.
In this way may be other users will not go through the painful trial and er=
ror
process as I did, before being able to use sssd in Leap 15.6.

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

You are on the CC list for the bug.

=

--17180332262.Ce5a.3817--

summary: sssd: missing /etc/sssd/sssd.conf


--17180887490.Ee0F31.4594
Date: Tue, 11 Jun 2024 06:52: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=3D1226170

            Bug ID: 1226170
           Summary: Chromium - widevine not being loaded in arm64 Linux
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: aarch64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: gmbr3-at-opensuse.org
          Reporter: mrkcee-at-protonmail.com
        QA Contact: screening-team-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I noticed that Chromium in openSUSE Tumbleweed does not look for Widevine
despite it being installed manually in the proper places. I have verified t=
his
in Tumbleweed running on both Apple Silicon (via Asahi Linux) and in an aar=
ch64
VM (via UTM in macOS).

This bug logged in Ubuntu explains the issue:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2008433

Would it be possible to include the following patch (which is similar to the
patch included in the Ubuntu bug report) to enable widevine checking for
non-amd64 Linux systems? The first part of this patch I know is already bei=
ng
implemented.
https://build.opensuse.org/projects/home:mrkcee:branches:network:chromium/p=
ackages/chromium/files/fix_building_widevinecdm_with_chromium.patch?expand=
=3D1

I am able to build the package successfully in my branch. And is now workin=
g as
expected.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17180887490.Ee0F31.4594
Date: Tue, 11 Jun 2024 06:52: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
          1226170

          Summary
          Chromium - widevine not being loaded in arm64 Linux

          Classification
          openSUSE

          Product
          openSUSE.org

          Version
          unspecified

          Hardware
          aarch64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          3rd party software

          Assignee
          gmbr3@opensuse.org

          Reporter
          mrkcee@protonmail.com

          QA Contact
          screening-team-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I noticed that Chromium in openSUSE Tumbleweed does not look=
 for Widevine
despite it being installed manually in the proper places. I have verified t=
his
in Tumbleweed running on both Apple Silicon (via Asahi Linux) and in an aar=
ch64
VM (via UTM in macOS).

This bug logged in Ubuntu explains the issue:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/20=
08433

Would it be possible to include the following patch (which is similar to the
patch included in the Ubuntu bug report) to enable widevine checking for
non-amd64 Linux systems? The first part of this patch I know is already bei=
ng
implemented.
https://build.opensuse.org/projects/home:mrkcee:branches:ne=
twork:chromium/packages/chromium/files/fix_building_widevinecdm_with_chromi=
um.patch?expand=3D1

I am able to build the package successfully in my branch. And is now workin=
g as
expected.

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

You are on the CC list for the bug.

=

--17180887490.Ee0F31.4594--


--17180913261.6Ce5bF3e.4735
Date: Tue, 11 Jun 2024 07:35:26 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1226173
           Summary: virt-manager: Browse local does not work anymore
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: martin.jedamzik-at-suse.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

When trying to add a storage device with virt-manager via:

--> Add Hardware -->  Storage --> Select or create custom-storage --> Manage
--> Browse Local=20

nothing will happen.

After starting :

virt-manager --no-fork --debug

one see's this error message:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/storagebrowse.py", line 162, in
_browse_clicked
    return self._browse_local()
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/virt-manager/virtManager/storagebrowse.py", line 187, in
_browse_local
    filename =3D self.err.browse_local(
               ^^^^^^^^^^^^^^^^^^^^^^
TypeError: vmmErrorDialog.browse_local() got an unexpected keyword argument
'choose_label'

Commenting out "choose_label=3Ddata.choose_label" in
/usr/share/virt-manager/virtManager/storagebrowse.py does solve the issue.
However, I am unsure about possible drawbacks.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17180913261.6Ce5bF3e.4735
Date: Tue, 11 Jun 2024 07:35:26 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1226173

          Summary
          virt-manager: Browse local does not work anymore

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Virtualization:Tools

          Assignee
          virt-bugs@suse.de

          Reporter
          martin.jedamzik@suse.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

When trying to add a storage device with virt-manager via:

--> Add Hardware -->  Storage --> Select or create custom-storage =
--> Manage
--> Browse Local=20

nothing will happen.

After starting :

virt-manager --no-fork --debug

one see's this error message:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/storagebrowse.py", li=
ne 162, in
_browse_clicked
    return self._browse_local()
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/virt-manager/virtManager/storagebrowse.py", li=
ne 187, in
_browse_local
    filename =3D self.err.browse_local(
               ^^^^^^^^^^^^^^^^^^^^^^
TypeError: vmmErrorDialog.browse_local() got an unexpected keyword argument
'choose_label'

Commenting out "choose_label=3Ddata.choose_label" in
/usr/share/virt-manager/virtManager/storagebrowse.py does solve the issue.
However, I am unsure about possible drawbacks.

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

You are on the CC list for the bug.

=

--17180913261.6Ce5bF3e.4735--


--17181724711.8fAcdb90.7002
Date: Wed, 12 Jun 2024 06:07:51 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

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

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

Stable Channel Update for Desktop
Tuesday, June 11, 2024

The Chrome team is delighted to announce the promotion of Chrome 126 to the
stable channel for Windows, Mac and Linux. This will roll out over the comi=
ng
days/weeks.

Chrome 126.0.6478.54 (Linux)  126.0.6478.56/57( Windows, Mac) contains a nu=
mber
of fixes and improvements


--17181796481.a2bb7f.7263
Date: Wed, 12 Jun 2024 08:07:28 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1226207
           Summary: breeze-dark (kf6-breeze-icons) symbolic icons aren't recolored and dark though should be light
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: w01dnick-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

kf6-breeze-icons generate identical icons for both breeze & breeze-dark. Wh=
ile
this is not an issue for KF6 apps, that use run-time recoloring, in KF5 app=
s,
like Krusader, when dark color theme is used and icons are breeze-dark symb=
olic
icons are dark on dark background and almost invisible.

The reason is this build option: `-DWITH_ICON_GENERATION:BOOL=3DFALSE`

I've tried to make my custom build [1] switching it to TRUE and breeze-dark
icons are fine with Krusader now. But I don't know the reasoning behind
switching it to FALSE. There is comment:
```
saves ~30MB and installs dangling symlinks
```

Less size is true, though IMHO it's not a good solution to break KF5 apps to
save some space.
But I can't see any dangling symlinks:
```
find /usr/share/icons/breeze{,-dark} -xtype l
```
doesn't find anything.

Any other reason or should I cleanup [1] and make a submit request?

[1]
https://build.opensuse.org/package/show/home:NickLion:branches:KDE:Framewor=
ks/kf6-breeze-icons
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17181796481.a2bb7f.7263
Date: Wed, 12 Jun 2024 08:07:28 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1226207

          Summary
          breeze-dark (kf6-breeze-icons) symbolic icons aren't recolore=
d and dark though should be light

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          KDE Workspace (Plasma)

          Assignee
          opensuse-kde-bugs@opensuse.org

          Reporter
          w01dnick@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

kf6-breeze-icons generate identical icons for both breeze &a=
mp; breeze-dark. While
this is not an issue for KF6 apps, that use run-time recoloring, in KF5 app=
s,
like Krusader, when dark color theme is used and icons are breeze-dark symb=
olic
icons are dark on dark background and almost invisible.

The reason is this build option: `-DWITH_ICON_GENERATION:BOOL=3DFALSE`

I've tried to make my custom build [1] switching it to TRUE and breeze-dark
icons are fine with Krusader now. But I don't know the reasoning behind
switching it to FALSE. There is comment:
```
saves ~30MB and installs dangling symlinks
```

Less size is true, though IMHO it's not a good solution to break KF5 apps to
save some space.
But I can't see any dangling symlinks:
```
find /usr/share/icons/breeze{,-dark} -xtype l
```
doesn't find anything.

Any other reason or should I cleanup [1] and make a submit request?

[1]
https://build.opensuse.org/package/show/hom=
e:NickLion:branches:KDE:Frameworks/kf6-breeze-icons

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

You are on the CC list for the bug.

=

--17181796481.a2bb7f.7263--


--17183012552.d9999.13162
Date: Thu, 13 Jun 2024 17:54:15 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1226306
           Summary: AUDIT-0: kdeplasma-addons: review of D-Bus service
    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: fabian@ritter-vogt.de
        QA Contact: qa-bugs-at-suse.de
                CC: opensuse-kde-bugs-at-opensuse.org
  Target Milestone: ---
          Found By: ---
           Blocker: ---

KDE Plasma 6.1 ships a new kded module that allows automatic control of RGB
LEDs to match the desktop color scheme.

Package (git build) can be found at
https://build.opensuse.org/package/show/KDE:Unstable:Frameworks/kdeplasma6-=
addons.

rpmlint message:

[  185s] kdeplasma6-addons.i586: E: dbus-file-unauthorized (Badness: 10)
/usr/share/dbus-1/system.d/org.kde.kameleonhelper.conf (sha256 file digest
default filter:864c70a8676869ee553d43a9884cd6b067cbd87838f39d8a2f9fed639d5b=
1774
shell filter:6b269af23963927202767deacadcda10db531bde4136fc8a3ace0ada82ecaf=
ae
xml filter:f9c8290a4e53a251b5405f0a04676b222866c9d0463e0d5e16d020657ec335cb)
[  185s] kdeplasma6-addons.i586: E: dbus-file-unauthorized (Badness: 10)
/usr/share/dbus-1/system-services/org.kde.kameleonhelper.service (sha256 fi=
le
digest default
filter:85e17072d140148cf4cb4186389f5dd6a24c56fbae76c5392504b9062560e0f6 she=
ll
filter:85e17072d140148cf4cb4186389f5dd6a24c56fbae76c5392504b9062560e0f6 xml
filter:<failed-to-calculate>)

Code:
https://invent.kde.org/plasma/kdeplasma-addons/-/blob/master/kdeds/kameleon=
/kameleonhelper.cpp?ref_type=3Dheads

I already had a look and sent a MR with some improvements:
https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/598
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17183012552.d9999.13162
Date: Thu, 13 Jun 2024 17:54:15 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1226306

          Summary
          AUDIT-0: kdeplasma-addons: review of D-Bus service

          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
          fabian@ritter-vogt.de

          QA Contact
          qa-bugs@suse.de

          CC
          opensuse-kde-bugs@opensuse.org

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

KDE Plasma 6.1 ships a new kded module that allows automatic=
 control of RGB
LEDs to match the desktop color scheme.

Package (git build) can be found at
https://build.opensuse.org/package/show/KDE:Unstable:Fra=
meworks/kdeplasma6-addons.

rpmlint message:

[  185s] kdeplasma6-addons.i586: E: dbus-file-unauthorized (Badness: 10)
/usr/share/dbus-1/system.d/org.kde.kameleonhelper.conf (sha256 file digest
default filter:864c70a8676869ee553d43a9884cd6b067cbd87838f39d8a2f9fed639d5b=
1774
shell filter:6b269af23963927202767deacadcda10db531bde4136fc8a3ace0ada82ecaf=
ae
xml filter:f9c8290a4e53a251b5405f0a04676b222866c9d0463e0d5e16d020657ec335cb)
[  185s] kdeplasma6-addons.i586: E: dbus-file-unauthorized (Badness: 10)
/usr/share/dbus-1/system-services/org.kde.kameleonhelper.service (sha256 fi=
le
digest default
filter:85e17072d140148cf4cb4186389f5dd6a24c56fbae76c5392504b9062560e0f6 she=
ll
filter:85e17072d140148cf4cb4186389f5dd6a24c56fbae76c5392504b9062560e0f6 xml
filter:<failed-to-calculate>)

Code:
https://invent.kde.org/pla=
sma/kdeplasma-addons/-/blob/master/kdeds/kameleon/kameleonhelper.cpp?ref_ty=
pe=3Dheads

I already had a look and sent a MR with some improvements:
https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/598

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

You are on the CC list for the bug.

=

--17183012552.d9999.13162--


body:
--17183022590.fAbC.13192
Date: Thu, 13 Jun 2024 18:10:59 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1226307
           Summary: Lua includes missing for luajit
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Slowroll
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: pirateclip-at-protonmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I am attempting to update the sile package to 0.15.0 but due to some issues=
 I
temporarily need to use luajit.

The problem is that SILE expects certain header files which are not in
luajit-devel:
[    5s] checking for icu-uc icu-io... yes
[    5s] checking for a Lua interpreter with version >=3D 5.1... luajit
[    5s] checking for luajit... /usr/bin/luajit
[    5s] checking for luajit version... 5.1
[    5s] checking for luajit jit version... 2.1.1707061634
[    5s] checking for luajit platform... unknown
[    5s] checking for luajit script directory... ${prefix}/share/luajit-5_1=
-2.1
[    5s] checking for luajit module directory... ${exec_prefix}/lib64/lua/5=
.1
[    5s] checking if LUA_VERSION is defined... yes
[    5s] checking if LUAJIT_VERSION is defined... yes
[    5s] checking for lua.h... no
[    6s] checking for lualib.h... no
[    6s] checking for lauxlib.h... no
[    6s] checking for luaconf.h... no
[    6s] checking for luajit.h... no
[    6s] configure: error: cannot find Lua includes

SILE does correctly identify the headers for lua5.4 though:
[   23s] checking if LUA_VERSION is defined... yes
[   23s] checking for lua.h... no
[   24s] checking for lualib.h... no
[   24s] checking for lauxlib.h... no
[   24s] checking for luaconf.h... no
[   24s] checking for Lua headers in... /usr/include/lua5.4
[   24s] checking for lua.h... yes
[   24s] checking for lualib.h... yes
[   24s] checking for lauxlib.h... yes
[   24s] checking for luaconf.h... yes
[   24s] checking for Lua header version... 5.4
...

I think luajit-devel should include the requested headers
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17183022590.fAbC.13192
Date: Thu, 13 Jun 2024 18:10:59 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1226307

          Summary
          Lua includes missing for luajit

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Slowroll

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Other

          Assignee
          screening-team-bugs@suse.de

          Reporter
          pirateclip@protonmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I am attempting to update the sile package to 0.15.0 but due=
 to some issues I
temporarily need to use luajit.

The problem is that SILE expects certain header files which are not in
luajit-devel:
[    5s] checking for icu-uc icu-io... yes
[    5s] checking for a Lua interpreter with version >=3D 5.1... luajit
[    5s] checking for luajit... /usr/bin/luajit
[    5s] checking for luajit version... 5.1
[    5s] checking for luajit jit version... 2.1.1707061634
[    5s] checking for luajit platform... unknown
[    5s] checking for luajit script directory... ${prefix}/share/luajit-5_1=
-2.1
[    5s] checking for luajit module directory... ${exec_prefix}/lib64/lua/5=
.1
[    5s] checking if LUA_VERSION is defined... yes
[    5s] checking if LUAJIT_VERSION is defined... yes
[    5s] checking for lua.h... no
[    6s] checking for lualib.h... no
[    6s] checking for lauxlib.h... no
[    6s] checking for luaconf.h... no
[    6s] checking for luajit.h... no
[    6s] configure: error: cannot find Lua includes

SILE does correctly identify the headers for lua5.4 though:
[   23s] checking if LUA_VERSION is defined... yes
[   23s] checking for lua.h... no
[   24s] checking for lualib.h... no
[   24s] checking for lauxlib.h... no
[   24s] checking for luaconf.h... no
[   24s] checking for Lua headers in... /usr/include/lua5.4
[   24s] checking for lua.h... yes
[   24s] checking for lualib.h... yes
[   24s] checking for lauxlib.h... yes
[   24s] checking for luaconf.h... yes
[   24s] checking for Lua header version... 5.4
...

I think luajit-devel should include the requested headers

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

You are on the CC list for the bug.

=

--17183022590.fAbC.13192--

summary: Lua includes missing for luajit


--17183563801.fDFB22f10.13861
Date: Fri, 14 Jun 2024 09:13:00 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1226321
           Summary: HTTPie SSL certificate problems with python-requests 2.32.3 (fine with 2.32.2)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Python
          Assignee: python-maintainers-at-suse.com
          Reporter: w01dnick-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

After update of python311-requests to version 2.32.3 HTTPie stopped accepti=
ng
SSL certificates:

```
https google.com

https: error: SSLError: HTTPSConnectionPool(host=3D'google.com', port=3D443=
): Max
retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1,
'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get
local issuer certificate (_ssl.c:1006)'))) while doing a GET request to URL:
https://google.com/
```

Downgrading python311-requests to 2.32.2 from history [1] solves the problem
and HTTPie works fine again.

IDK if it's a python-requests API change and this should be reported upstre=
am.

[1] https://cdn.opensuse.org/history/20240610/tumbleweed/repo/oss/noarch/
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17183563801.fDFB22f10.13861
Date: Fri, 14 Jun 2024 09:13:00 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1226321

          Summary
          HTTPie SSL certificate problems with python-requests 2.32.3 (=
fine with 2.32.2)

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          Other

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Python

          Assignee
          python-maintainers@suse.com

          Reporter
          w01dnick@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

After update of python311-requests to version 2.32.3 HTTPie =
stopped accepting
SSL certificates:

```
https google.com

https: error: SSLError: HTTPSConnectionPool(host=3D'google.com', port=3D443=
): Max
retries exceeded with url: / (Caused by SSLError(SSLCertVerificationError(1,
'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get
local issuer certificate (_ssl.c:1006)'))) while doing a GET request to URL:
<a href=3D"https://google.com/">https://google.com/</a>
```

Downgrading python311-requests to 2.32.2 from history [1] solves the problem
and HTTPie works fine again.

IDK if it's a python-requests API change and this should be reported upstre=
am.

[1] https://cdn.opensuse.org/history/20240610/tumbleweed/repo/oss/no=
arch/

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

You are on the CC list for the bug.

=

--17183563801.fDFB22f10.13861--


--17184784163.9d7661.15734
Date: Sat, 15 Jun 2024 19:06:56 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1226394
           Summary: xdg-desktop-portal-lxqt not started by default
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Tumbleweed
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: LXQt
          Assignee: lxqt-bugs-at-suse.de
          Reporter: brbigam-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

xdg-desktop-portal-lxqt isn't automatically started by xdg-desktop-portal on
login, so the LXQt file dialog isn't picked up by apps that could use it, l=
ike
Firefox.

Steps to reproduce:
Log in to LXQt
check running processes, such as in qps
check file dialog in Firefox with widget.use-xdg-desktop-portal.file-picker=
 set
to 1

Actual result:
x-d-p is running, but not x-d-p-lxqt
no file dialog opens in Firefox (Unless another portal backend is also
installed)

Expected result:
x-d-p-lxqt is running
LXQt file dialog is used by Firefox

System:
Tumbleweed 20240613 and earlier, as long as LXQt 2.0.0 has been available
LXQt 2.0.0
xdg-desktop-portal-lxqt 1.0.2
xdg-desktop-portal 1.18.4
Qt 6.7.1

Workaround:
If I run /usr/libexec/xdg-desktop-portal --replace after login, x-d-p corre=
ctly
picks up x-d-p-lxqt and everything works correctly. Adding this to autostart
apps also works correctly.=20

So if it's an upstream issue, openSUSE might consider adding this to packag=
ing
temporarily as a workaround. I don't know what the underlying problem might=
 be.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17184784163.9d7661.15734
Date: Sat, 15 Jun 2024 19:06:56 +0000
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

          Bug ID
          1226394

          Summary
          xdg-desktop-portal-lxqt not started by default

          Classification
          openSUSE

          Product
          openSUSE Tumbleweed

          Version
          Current

          Hardware
          x86-64

          OS
          openSUSE Tumbleweed

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          LXQt

          Assignee
          lxqt-bugs@suse.de

          Reporter
          brbigam@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

xdg-desktop-portal-lxqt isn't automatically started by xdg-d=
esktop-portal on
login, so the LXQt file dialog isn't picked up by apps that could use it, l=
ike
Firefox.

Steps to reproduce:
Log in to LXQt
check running processes, such as in qps
check file dialog in Firefox with widget.use-xdg-desktop-portal.file-picker=
 set
to 1

Actual result:
x-d-p is running, but not x-d-p-lxqt
no file dialog opens in Firefox (Unless another portal backend is also
installed)

Expected result:
x-d-p-lxqt is running
LXQt file dialog is used by Firefox

System:
Tumbleweed 20240613 and earlier, as long as LXQt 2.0.0 has been available
LXQt 2.0.0
xdg-desktop-portal-lxqt 1.0.2
xdg-desktop-portal 1.18.4
Qt 6.7.1

Workaround:
If I run /usr/libexec/xdg-desktop-portal --replace after login, x-d-p corre=
ctly
picks up x-d-p-lxqt and everything works correctly. Adding this to autostart
apps also works correctly.=20

So if it's an upstream issue, openSUSE might consider adding this to packag=
ing
temporarily as a workaround. I don't know what the underlying problem might=
 be.

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

You are on the CC list for the bug.

=

--17184784163.9d7661.15734--


--17185677693.05Fc.16036
Date: Sun, 16 Jun 2024 19:56: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=3D1226408

            Bug ID: 1226408
           Summary: Building opensuse microOS images with kiwi-ng without OBS fails (patterns-microos-base dependencies problems)
    Classification: openSUSE
           Product: openSUSE Leap Micro
           Version: 6.0
          Hardware: All
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Patterns
          Assignee: lubos.kocman-at-suse.com
          Reporter: gmachado.tl1-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
  Target Milestone: ---
          Found By: ---
           Blocker: ---

I found 2 issues when I tried to build opensuse microOS images with kiwi-ng
without OBS. I'm adapting this OBS project to my needs :
https://build.opensuse.org/package/show/openSUSE:Factory/openSUSE-MicroOS

First issue occured because obs resolver and zypper handle busybox preferen=
ce
differently : https://groups.google.com/g/kiwi-images/c/FptmmheOT7g

Second issue occured because systemd-presets-branding-MicroOS was not insta=
lled
during the
bootstrap phase and the zypper resolver failed :
https://groups.google.com/g/kiwi-images/c/r3L_fwXp3Xc

Can you fix these issues please ? And generally test the packages/patterns
dependencies also without OBS ?

Thanks in advance and thanks again Marcus Sch=C3=A4fer for his help.
Regards,
Gabriel.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=

--17185677693.05Fc.16036
Date: Sun, 16 Jun 2024 19:56: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
          1226408

          Summary
          Building opensuse microOS images with kiwi-ng without OBS fai=
ls (patterns-microos-base dependencies problems)

          Classification
          openSUSE

          Product
          openSUSE Leap Micro

          Version
          6.0

          Hardware
          All

          OS
          Other

          Status
          NEW

          Severity
          Normal

          Priority
          P5 - None

          Component
          Patterns

          Assignee
          lubos.kocman@suse.com

          Reporter
          gmachado.tl1@gmail.com

          QA Contact
          qa-bugs@suse.de

          Target Milestone
          ---

          Found By
          ---

          Blocker
          ---

I found 2 issues when I tried to build opensuse microOS imag=
es with kiwi-ng
without OBS. I'm adapting this OBS project to my needs :
https://build.opensuse.org/package/show/openSUSE:Factory/openSUS=
E-MicroOS

First issue occured because obs resolver and zypper handle busybox preferen=
ce
differently : https://groups.google.com/g/kiwi-images/c/FptmmheOT7g

Second issue occured because systemd-presets-branding-MicroOS was not insta=
lled
during the
bootstrap phase and the zypper resolver failed :
https://g=
roups.google.com/g/kiwi-images/c/r3L_fwXp3Xc

Can you fix these issues please ? And generally test the packages/patterns
dependencies also without OBS ?

Thanks in advance and thanks again Marcus Sch=C3=A4fer for his help.
Regards,
Gabriel.

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

You are on the CC list for the bug.

=

--17185677693.05Fc.16036--


--17186015110.ce55C45bb.16225
Date: Mon, 17 Jun 2024 05:18:31 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugzilla.suse.com/
Auto-Submitted: auto-generated

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

            Bug ID: 1226415
           Summary: data loss: update 15.5 =3D> 15.6 deletes old journal entries
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.6
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Upgrade Problems
          Assignee: screening-team-bugs-at-suse.de
          Reporter: seife-at-novell.slipkontur.de
        QA Contact: jsrain-at-suse.com
  Target Milestone: ---
          Found By: ---
           Blocker: ---

Created attachment 875512
  --> https://bugzilla.suse.com/attachment.cgi?id=3D875512&action=3Dedit
/var/log/journal filesystem statistics

I updated my server from 15.5 to 15.6 yesterday and encountered a critical =
data
loss:

My journal is configured to have its own file system for /var/log/journal (=
8GB)
to keep it from eating too much disk space, the config in
/etc/systemd/journald.conf is like this:

[Journal]
SystemMaxFileSize=3D8M
SystemMaxFiles=3D1024
SystemMaxUse=3D6666M
SystemKeepFree=3D10%

After the update, the journal was pruned from 6,5GB to 850MB, removing all
files older than one months (see attached screenshot)

server:~ # ls -l /var/log/journal/63ab585aac31189cc7872956493ee6b3/ -t | ta=
il
-rw-r---