May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1221557] New: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221557 Bug ID: 1221557 Summary: flatpak runtime org.kde.Platform 6.6 does not reliably verify SSL certs Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Flatpak Assignee: rbrown(a)suse.com Reporter: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:123.0) Gecko/20100101 Firefox/123.0 Build Identifier: Hello there this came to my attention as OBS Studio updated their flatpak from 30.0.2 to 30.1.0 where they also changed the used runtime form KDE Platform 6.5 to 6.6. Since that update browser sources and browser docks do no longer work if they are pointing at an HTTPS protected site. While with runtime 6.5 it still works fine (more details below). Browser docks are only available in a X11 session due to bugs under Wayland but also the only one to actually show an error message while browser sources are completely silent and simply keep empty. Beside the steps to reproduce other findings made in the meantime before reporting here. This happens on openSUSE Leap 15.6, openSUSE Tumbleweed, openSUSE Aeon and openSUSE Kalpa. Running the OBS Studio flatpak on virtually any other Linux distribution (Tested Ubuntu 22.04, Fedora 39, Arch Linux) does work just fine. Nevertheless I report the bug for Aeon as Aeon and Kalpa heavily rely on flatpaks and this issue is more imminent for them than for regular Tumbleweed and Leap. Other things I tried was running the OBS Studio 30.1.0 *.dep package from inside a Ubuntu 22.04 distrobox container running on my openSUSE Aeon host. Browser sources and docks worked just fine. Also I ran a Ubuntu 22.04 VM on my openSUSE Aeon host using Gnome Boxes and the flatpak version of OBS Studio, browser sources and docks worked just fine too. Furthermore I build the OBS Studio flatpak locally using fkatpab-builder from inside a openSUSE Tumbleweed distrobox using runtime 6.5 instead of 6.6. That OBS Studio flatpak did worked just fine on my openSUSE Aeon and inside the openSUSE Tumlbeweed distrobox container. Whilst building it with 6.6 was broken again. To build OBS Studio with a different runtime do the following: 1) git clone --recursive https://github.com/obsproject/obs-studio.git 2) Change the content of obs-studio/build-aux/com.obsproject.Studio to ruse runtime 6.5 instead of 6.6 (line 4) 3) flatpak-builder --force-clean --install-deps-from=flathub --user --install --ccache --mirror-screenshots-url=https://dl.flathub.org/media/ build-dir build-aux/com.obsproject.Studio.json --user --install Reproducible: Always Steps to Reproduce: 1. Install OBS Studio flatpak 30.1.0 2. Add a browser dock or a browser source pointing to an https site 3. See nothing or in case of a dock the error: ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Actual Results: Empty browser source or a browser dock showing ERR_CERT_AUTHORITY_INVALID URL: https://obsproject.com/browser-source Expected Results: Browser sources and docks to work Thsi bug was firstly reported to OBS Studio where we found out it's actually the runtime causeing the issue: https://github.com/obsproject/obs-studio/issues/10385 And reported to KDE where they asked me to better open up the issue directly for openSUSE as other distributions are not affected over here: https://bugs.kde.org/show_bug.cgi?id=483746 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1224215] New: Krunner randomly forces you to backspace-remove text to clear out text
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224215 Bug ID: 1224215 Summary: Krunner randomly forces you to backspace-remove text to clear out text Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: jlopez777+opensuse(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Krunner randomly forces you to backspace-remove text to clear out text Submitted here too: https://bugs.kde.org/show_bug.cgi?id=485375 SUMMARY I have to manually hit backspace to remove text from krunner. expected behavior: it should just clear out text or have it highlighted to allow for "write over" so that the new text I enter wipes out old text. Hard to reproduce, not sure what triggers it because it doesn't happen all the time...but I think its when I highlight text. 1. Highlight some random text from web browser 2. Call krunner 3. Observe behavior 4. esc and call krunner again, and NOW it highlights all the text for overwrite....which should be intended behavior initially. DEMO of the problem: Hard to explain, so here is a vid: https://youtu.be/0WtkuhZGlEs -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1216083] New: cockpit-ws: theme QA
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1216083 Bug ID: 1216083 Summary: cockpit-ws: theme QA Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: Cockpit-bugs(a)suse.de Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de CC: Cockpit-bugs(a)suse.de, qa-bugs(a)suse.de Depends on: 1216082 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1216082 +++ We should add openQA test for basic theme and login -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216082] New: cockpit-ws: theme missing
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1216082 Bug ID: 1216082 Summary: cockpit-ws: theme missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: Cockpit-bugs(a)suse.de Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The theme seems to not be loaded correcly. It looks very dark, like the default theme. See MicroOS 5.1 for correct theme. TW, 5.5 need fixes. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1220476] New: GCC 14: freeipmi package fails
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1220476 Bug ID: 1220476 Summary: GCC 14: freeipmi package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kkaempf(a)suse.com, mjambor(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Building freeipmi with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: sel/ipmi-sel-string-supermicro-x10dimm-common.c: In function ‘sel_string_output_supermicro_x10dimm_event_data2_event_data3’: sel/ipmi-sel-string-supermicro-x10dimm-common.c:87:14: error: implicit declaration of function ‘sel_string_output_supermicro_dimm_event_data2_event_data3’; did you mean ‘sel_string_output_supermicro_x10dimm_event_data2_event_data3’? [-Wimplicit-function-declaration] 87 | if ((ret = sel_string_output_supermicro_dimm_event_data2_event_data3 (ctx, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | sel_string_output_supermicro_x10dimm_event_data2_event_data3 ipmi-sensors-oem-intel.c: In function ‘ipmi_sensors_oem_intel_output_oem_record’: ipmi-sensors-oem-intel.c:98:18: error: implicit declaration of function ‘ipmi_sensors_oem_intel_s2600wp_output_oem_record’; did you mean ‘ipmi_sensors_oem_intel_s2600jf_output_oem_record’? [-Wimplicit-function-declaration] 98 | if ((ret = ipmi_sensors_oem_intel_s2600wp_output_oem_record (state_data, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ipmi_sensors_oem_intel_s2600jf_output_oem_record Builds with: Index: freeipmi.spec_dir/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h =================================================================== --- freeipmi.spec_dir.orig/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h +++ freeipmi.spec_dir/freeipmi-1.6.14/libfreeipmi/sel/ipmi-sel-string-supermicro-common.h @@ -38,5 +38,14 @@ int sel_string_output_supermicro_overhea unsigned int flags, unsigned int *wlen, struct ipmi_sel_system_event_record_data *system_event_record_data); +int sel_string_output_supermicro_dimm_event_data2_event_data3 (ipmi_sel_ctx_t ctx, + struct ipmi_sel_entry *sel_entry, + uint8_t sel_record_type, + char *buf, + unsigned int buflen, + unsigned int flags, + unsigned int *wlen, + struct ipmi_sel_system_event_record_data *system_event_record_data, + int *oem_rv); #endif /* IPMI_SEL_STRING_SUPERMICRO_COMMON_H */ Index: freeipmi.spec_dir/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c =================================================================== --- freeipmi.spec_dir.orig/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c +++ freeipmi.spec_dir/freeipmi-1.6.14/ipmi-sensors/ipmi-sensors-oem-intel.c @@ -34,6 +34,7 @@ #include "ipmi-sensors-oem-intel.h" #include "ipmi-sensors-oem-intel-s5500wb.h" #include "ipmi-sensors-oem-intel-s2600jf.h" +#include "ipmi-sensors-oem-intel-s2600wp.h" #include "ipmi-sensors-oem-intel-quanta-qssc-s4r.h" #include "ipmi-sensors-oem-intel-node-manager.h" -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1221340] New: qemu: fails to build with osc
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221340 Bug ID: 1221340 Summary: qemu: fails to build with osc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: adrian.schroeter(a)suse.com, dfaggioli(a)suse.com Target Milestone: --- Found By: Development Blocker: --- Steps to reproduce: osc co openSUSE:Factory/qemu && cd $_ osc build --noservice --clean standard Actual results: using SOURCE_DATE_EPOCH with value 1709510400 as build time error: Failed build dependencies: canokey-qemu-devel is needed by qemu-8.2.1-0.x86_64 libxdp-devel is needed by qemu-8.2.1-0.x86_64 pkgconfig(spice-protocol) >= 0.12.3 is needed by qemu-8.2.1-0.x86_64 pkgconfig(spice-server) >= 0.12.5 is needed by qemu-8.2.1-0.x86_64 xen-devel >= 4.2 is needed by qemu-8.2.1-0.x86_64 Powering off. [ 94.494179][ T3445] reboot: Power down This likely has to do with these macros %if 0%{with canokey} BuildRequires: canokey-qemu-devel %endif that are not properly parsed to provide the BuildRequires # rpm -q osc build osc-1.6.1-150500.403.1.noarch build-20240221-150500.444.1.noarch (both from openSUSE:Tools / 15.5) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1225522] New: sharing a folder in nautilus gives a usershare failed error
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225522 Bug ID: 1225522 Summary: sharing a folder in nautilus gives a usershare failed error Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: hotel-brot.0z(a)icloud.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0 Build Identifier: sharing a folder in nautilus gives a usershare failed error: Called "net usershare info" but it failed: »net usershare« returned error 255: net usershare: usershares are currently disabled Reproducible: Always Steps to Reproduce: 1.create any folder for testing 2.right click on folder in nautilus -> Sharing Options -> Share this folder -> Create Share Actual Results: Called "net usershare info" but it failed: »net usershare« returned error 255: net usershare: usershares are currently disabled Expected Results: successful sharing of a folder journalctl does not show more than the same error given above -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225690] New: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 125.0.6422.141
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225690 Bug ID: 1225690 Summary: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 125.0.6422.141 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: andrea.mattiazzo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The Stable channel has been updated to 125.0.6422.141/.142 for Windows, Mac and 125.0.6422.141 for Linux which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log. Security Fixes and Rewards Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. This update includes 11 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information. - CVE-2024-5493: Heap buffer overflow in WebRTC. - CVE-2024-5494: Use after free in Dawn. - CVE-2024-5495: Use after free in Dawn. - CVE-2024-5496: Use after free in Media Session. - CVE-2024-5497: Out of bounds memory access in Keyboard Inputs. - CVE-2024-5498: Use after free in Presentation API. - CVE-2024-5499: Out of bounds write in Streams API. As usual, our ongoing internal security work was responsible for a wide range of fixes: [343518382] Various fixes from internal audits, fuzzing and other initiatives Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL. [0] https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-des… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1218513] New: wayland, scale settings not recorded
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1218513 Bug ID: 1218513 Summary: wayland, scale settings not recorded Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- If I set the scale to 105 % then it works well. When I log out then log in, the scale is at 100 %. The scale is not recorded. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225636] New: Facetimehd firmware/driver fails to load
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225636 Bug ID: 1225636 Summary: Facetimehd firmware/driver fails to load Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: crdcastro5(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hardware is a late 2015 11" Macbook Air. The facetimehd-kmp-default package was installed by default and I installed the facetimehd-firmware manually, despite this the driver fails to load and the camera is not detected as a device. [I] clayton@s-169-232-95-114 ~> dmesg -w | grep facetimehd [ 2.934906] [ T349] facetimehd 0000:02:00.0: Found FaceTime HD camera with device id: 1570 [ 2.937304] [ T349] facetimehd 0000:02:00.0: Setting 64bit DMA mask [ 2.958735] [ T349] facetimehd 0000:02:00.0: S2 PCIe link init succeeded [ 2.958770] [ T349] facetimehd 0000:02:00.0: Refclk: 25MHz (0xa) [ 2.968787] [ T349] facetimehd 0000:02:00.0: PLL reset finished [ 2.968793] [ T349] facetimehd 0000:02:00.0: Waiting for S2 PLL to lock at 450 MHz [ 2.968808] [ T349] facetimehd 0000:02:00.0: S2 PLL is locked after 10 us [ 2.978828] [ T349] facetimehd 0000:02:00.0: S2 PLL is in bypass mode [ 2.998898] [ T349] facetimehd 0000:02:00.0: DDR40 PHY PLL locked on safe settings [ 2.998916] [ T349] facetimehd 0000:02:00.0: STRAP valid [ 2.998917] [ T349] facetimehd 0000:02:00.0: Configuring DDR PLLs for 450 MHz [ 2.998925] [ T349] facetimehd 0000:02:00.0: DDR40 PLL is locked after 0 us [ 2.998935] [ T349] facetimehd 0000:02:00.0: First DDR40 VDL calibration completed after 2 us [ 2.998943] [ T349] facetimehd 0000:02:00.0: Second DDR40 VDL calibration completed after 1 us [ 2.998944] [ T349] facetimehd 0000:02:00.0: Using step size 144 [ 2.998950] [ T349] facetimehd 0000:02:00.0: VDL set to: coarse=0x10008, fine=0x10119 [ 2.998955] [ T349] facetimehd 0000:02:00.0: Virtual VTT enabled [ 3.019479] [ T349] facetimehd 0000:02:00.0: S2 DRAM memory address: 0x22159559 [ 3.019496] [ T349] facetimehd 0000:02:00.0: Rewrite DDR mode registers succeeded [ 3.019719] [ T349] facetimehd 0000:02:00.0: Full memory verification succeeded! (0) [ 3.019942] [ T349] facetimehd 0000:02:00.0: Direct firmware load for facetimehd/firmware.bin failed with error -2 [ 3.020079] [ T349] facetimehd 0000:02:00.0: probe with driver facetimehd failed with error -2 I force reinstalled both and rebooted but still saw the same behavior. additional context: uname -a Linux localhost.localdomain 6.9.1-1-default #1 SMP PREEMPT_DYNAMIC Fri May 17 11:59:46 UTC 2024 (0c0b0b5) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1221682] New: GCC 14: autofs package fails
by bugzilla_noreply＠suse.com 03 Jun '24

03 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221682 Bug ID: 1221682 Summary: GCC 14: autofs package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Filesystems Assignee: kernel-fs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ddiss(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building autofs with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to (exhaustive list of errors): cyrus-sasl.c:112:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 112 | { SASL_CB_USER, &getuser_func, NULL }, | ^ cyrus-sasl.c:112:25: note: (near initialization for ‘callbacks[0].proc’) cyrus-sasl.c:113:29: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 113 | { SASL_CB_AUTHNAME, &getuser_func, NULL }, | ^ cyrus-sasl.c:113:29: note: (near initialization for ‘callbacks[1].proc’) cyrus-sasl.c:114:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(sasl_conn_t *, void *, int, sasl_secret_t **)’ {aka ‘int (*)(struct sasl_conn *, void *, int, struct sasl_secret **)’} [-Wincompatible-pointer-types] 114 | { SASL_CB_PASS, &getpass_func, NULL }, | ^ cyrus-sasl.c:114:25: note: (near initialization for ‘callbacks[2].proc’) cyrus-sasl.c:119:24: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char *)’ [-Wincompatible-pointer-types] 119 | { SASL_CB_LOG, &sasl_log_func, NULL }, | ^ cyrus-sasl.c:119:24: note: (near initialization for ‘debug_callbacks[0].proc’) cyrus-sasl.c:120:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 120 | { SASL_CB_USER, &getuser_func, NULL }, | ^ cyrus-sasl.c:120:25: note: (near initialization for ‘debug_callbacks[1].proc’) cyrus-sasl.c:121:29: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int, const char **, unsigned int *)’ [-Wincompatible-pointer-types] 121 | { SASL_CB_AUTHNAME, &getuser_func, NULL }, | ^ cyrus-sasl.c:121:29: note: (near initialization for ‘debug_callbacks[2].proc’) cyrus-sasl.c:122:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(sasl_conn_t *, void *, int, sasl_secret_t **)’ {aka ‘int (*)(struct sasl_conn *, void *, int, struct sasl_secret **)’} [-Wincompatible-pointer-types] 122 | { SASL_CB_PASS, &getpass_func, NULL }, | ^ cyrus-sasl.c:122:25: note: (near initialization for ‘debug_callbacks[3].proc’) ./autofs-5.1.9/config.log: conftest.c: In function 'main': ./autofs-5.1.9/config.log: conftest.c:58:47: error: passing argument 4 of 'ldap_parse_page_control' from incompatible pointer type [-Wincompatible-pointer-types] ./autofs-5.1.9/config.log: 58 | ret = ldap_parse_page_control(ld,clp,ct,c); ./autofs-5.1.9/config.log: | ^ ./autofs-5.1.9/config.log: | | ./autofs-5.1.9/config.log: | struct berval * ./autofs-5.1.9/config.log: In file included from /usr/include/lber_types.h:24, ./autofs-5.1.9/config.log: from /usr/include/lber.h:29, ./autofs-5.1.9/config.log: from /usr/include/ldap.h:30, ./autofs-5.1.9/config.log: from conftest.c:49: ./autofs-5.1.9/config.log: /usr/include/ldap.h:2155:25: note: expected 'struct berval **' but argument is of type 'struct berval *' ./autofs-5.1.9/config.log: 2155 | ldap_parse_page_control LDAP_P(( ./autofs-5.1.9/config.log: | ^~~~~~ Fixing configure may not be necessary to build the package, but it might be an indication that the package will be misconfigured. See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1221507] New: sddm fails to start with DisplayServer=wayland - always attempts to use tty1
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221507 Bug ID: 1221507 Summary: sddm fails to start with DisplayServer=wayland - always attempts to use tty1 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(a)opensuse.org Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- VERSION_ID="20240314" S | Name | Summary | Type ---+-----------------------------+-----------------------------------+------ i+ | kcm_sddm | A sddm control module for KDE | пакет i+ | kcm_sddm-lang | Translations for package kcm_sddm | пакет i+ | plasma6-sddm-theme-openSUSE | SDDM theme for openSUSE | пакет i+ | sddm | QML-based display manager (Qt5) | пакет i | sddm-branding-openSUSE | openSUSE branding for SDDM (Qt5) | пакет i | sddm-greeter-qt5 | SDDM Greeter for Qt5 themes | пакет i | sddm-greeter-qt6 | SDDM Greeter for Qt6 themes | пакет i | sddm-qt6-branding-openSUSE | Plasma 6 branding for SDDM | пакет bor@uefi:~> cat /etc/sddm.conf.d/wayland.conf [General] DisplayServer=wayland bor@uefi:~> loginctl SESSION UID USER SEAT TTY STATE IDLE SINCE 10 1000 bor - pts/0 active no - 1 sessions listed. bor@uefi:~> мар 16 21:30:47 uefi sddm[1192]: Initializing... мар 16 21:30:47 uefi sddm[1192]: Starting... мар 16 21:30:47 uefi sddm[1192]: Logind interface found мар 16 21:30:47 uefi sddm[1192]: Adding new display... мар 16 21:30:47 uefi sddm[1192]: Loaded empty theme configuration мар 16 21:30:47 uefi sddm[1192]: Using VT 1 мар 16 21:30:47 uefi sddm[1192]: Display server started. мар 16 21:30:48 uefi sddm[1192]: Reading from "/usr/local/share/wayland-sessions/plasmawayland.desktop" мар 16 21:30:48 uefi sddm[1192]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop" мар 16 21:30:48 uefi sddm[1192]: Session "/usr/share/wayland-sessions/plasmawayland.desktop" selected, command: "/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" for VT 1 мар 16 21:30:49 uefi sddm-helper[1245]: [PAM] Starting... мар 16 21:30:49 uefi sddm-helper[1245]: [PAM] Authenticating... мар 16 21:30:49 uefi sddm-helper[1245]: [PAM] returning. мар 16 21:30:49 uefi sddm[1192]: Authentication for user "bor" successful мар 16 21:30:54 uefi sddm-helper[1245]: pam_unix(sddm-autologin:session): session opened for user bor(uid=1000) by bor(uid=0) мар 16 21:30:54 uefi sddm-helper[1245]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_open_session мар 16 21:30:54 uefi sddm-helper[1245]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: open_session called without kwallet5_key мар 16 21:30:55 uefi sddm-helper[1245]: [PAM] Preparing to converse... мар 16 21:30:55 uefi sddm-helper[1245]: [PAM] Conversation with 1 messages мар 16 21:30:55 uefi sddm[1192]: Authentication information: SDDM::Auth::INFO_UNKNOWN "Last login: Sat Mar 16 21:24:37 MSK 2024 on tty1" мар 16 21:30:57 uefi sddm-helper[1245]: Starting Wayland user session: "/usr/share/sddm/scripts/wayland-session" "/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland" мар 16 21:30:57 uefi sddm-helper[1318]: Failed to take control of "/dev/tty1" ("root"): Operation not permitted Well, tty1 of course belongs to agetty. In X11 mode SDDM is using setUpNewVt() which calls IOCTL VT_OPENQRY while in Wayland mode it starts with vt1 and checks whether there is logind session using it. Of course there is no logind session so it always assumes vt1 is available. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1216969] New: Recent Applications and Recent Files are no longer updated
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1216969 Bug ID: 1216969 Summary: Recent Applications and Recent Files are no longer updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent Applications and Recent Files are no longer updated in KDE's Application menu. The links are existing in .local/share/RecentDocuments, though. Didn't find any directory for Recent Apps. Operating System: openSUSE Tumbleweed 20231106 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1218455] New: kernel: NOHZ tick-stop error: local softirq work is pending
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1218455 Bug ID: 1218455 Summary: kernel: NOHZ tick-stop error: local softirq work is pending Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with kernel 6.6.6 (and continuing with 6.6.7) I get kernel: NOHZ tick-stop error: local softirq work is pending, handler #08!!! a few times within one or two minutes and during this time performance is degraded heavily. This happens about every two days, so it is not that much of a problem, but a bit annoying. system is: Operating System: openSUSE Tumbleweed 20231226 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.7-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1225540] New: openSUSE Leap 15.6 known version downgrade regressions
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225540 Bug ID: 1225540 Summary: openSUSE Leap 15.6 known version downgrade regressions Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: lubos.kocman(a)suse.com Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: maintenance(a)opensuse.org Target Milestone: --- Found By: --- Blocker: --- Similar to bug 1224165, but not security related: The packages listed blow are maintenance updates released into Leap 15.5 that are missing in Leap 15.6. We should not release openSUSE Leap 15.6 with version downgrades, and the corresponding functional regressions. Please pull the content from openSUSE:Backports:SLE-15-SP5:Update into openSUSE:Backports:SLE-15-SP6, or get a newer package from Tumbleweed. asar awf-gtk2 awf-gtk3 awf-gtk4 civetweb fwts glab htop keepassxc lyx monero perl-File-Rename rspamd seamonkey stress-ng xfce4-terminal xfce4-whiskermenu-plugin -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222185] New: Can't install gnome-builder
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222185 Bug ID: 1222185 Summary: Can't install gnome-builder Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: wardlawhunter(a)gmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I get the following error when attempting to install gnome-builder on a fresh Tumbleweed installation. Problem: 1: nothing provides 'libgit2.so.1.7()(64bit)' needed by the to be installed gnome-builder-46.0-1.1.x86_64 libgit2-1_8 is in currently in the repos, but not libgit2-1_7. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1224147] New: After installing rstudio-2024.04.0-735-x86_64.rpm [R release] , rstudio fails to start
by bugzilla_noreply＠suse.com 02 Jun '24

02 Jun '24

1 5

[Bug 1192014] provide admin option to NOT automatically REbuild initrds for previously installed kernels
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1192014 https://bugzilla.suse.com/show_bug.cgi?id=1192014#c25 --- Comment #25 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2024:1887-1: An update that has five fixes can now be installed. Category: recommended (moderate) Bug References: 1192014, 1216717, 1217979, 1223278, 1224320 Maintenance Incident: [SUSE:Maintenance:34011](https://smelt.suse.de/incident/34011/) Sources used: openSUSE Leap 15.6 (src): suse-module-tools-15.6.9-150600.3.3.3 Basesystem Module 15-SP6 (src): suse-module-tools-15.6.9-150600.3.3.3 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217979] package xfsprogs: error while installing libhandle1
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217979 https://bugzilla.suse.com/show_bug.cgi?id=1217979#c25 --- Comment #25 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-RU-2024:1887-1: An update that has five fixes can now be installed. Category: recommended (moderate) Bug References: 1192014, 1216717, 1217979, 1223278, 1224320 Maintenance Incident: [SUSE:Maintenance:34011](https://smelt.suse.de/incident/34011/) Sources used: openSUSE Leap 15.6 (src): suse-module-tools-15.6.9-150600.3.3.3 Basesystem Module 15-SP6 (src): suse-module-tools-15.6.9-150600.3.3.3 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216717] New: suse-module-tools: 60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-0/queue/scheduler}, ignoring: No such file or directory
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1216717 Bug ID: 1216717 Summary: suse-module-tools: 60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-0/queue/scheduler}, ignoring: No such file or directory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: martin.wilck(a)suse.com Reporter: antonio.feijoo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Just in case this wasn't reported yet, this error is logged in the journal of a Tumbleweed system with crypto_LUKS devices: Oct 30 15:46:46 localhost (udev-worker)[724]: dm-0: /usr/lib/udev/rules.d/60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-0/queue/scheduler}, ignoring: No such file or directory Oct 30 15:46:48 localhost (udev-worker)[723]: dm-1: /usr/lib/udev/rules.d/60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-1/queue/scheduler}, ignoring: No such file or directory # uname -r 6.5.9-1-default # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-1/queue /sys/devices/virtual/block/dm-0/queue # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue/scheduler /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler Not happening in systems with a similar setup using previous kernel versions: - ALP Dolomite Build6.8 localhost:~ # uname -r 6.4.11-1-default localhost:~ # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-0/queue localhost:~ # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler /sys/devices/virtual/block/dm-0/queue/scheduler - Leap 15.5 # uname -r 5.14.21-150500.53-default # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-0/queue # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue/scheduler /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler /sys/devices/virtual/block/dm-0/queue/scheduler I don't know if it's a kernel bug or if the udev rule needs to be adjusted. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1225778] New: Package ibus does not build with gcc14 because of uses of incompatible pointer types
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225778 Bug ID: 1225778 Summary: Package ibus does not build with gcc14 because of uses of incompatible pointer types Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)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 ibus fails to compile. This can be seen online at: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… It can be reproduced locally with command: osc build --clean --alternative-project home:rguenther:nextgcc Fedora seems to have decided to avoid the new errors, see https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/i/ibus.md?ref_… The issue seems to be related to vala, so we should probably consider using -fpermissive - at least for now - too. The error (that halts the build) is: [ 329s] emojierapp.c: In function ‘emoji_application_save_selected_string’: [ 329s] emojierapp.c:306:60: error: passing argument 3 of ‘g_settings_set_strv’ from incompatible pointer type [-Wincompatible-pointer-types] [ 329s] 306 | g_settings_set_strv (_tmp11_, "favorites", _tmp12_); [ 329s] | ^~~~~~~ [ 329s] | | [ 329s] | gchar ** {aka char **} [ 329s] In file included from /usr/include/glib-2.0/gio/gio.h:137, [ 329s] from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:28, [ 329s] from /usr/include/gtk-3.0/gdk/gdk.h:32, [ 329s] from /usr/include/gtk-3.0/gtk/gtk.h:30, [ 329s] from emojierapp.c:30: [ 329s] /usr/include/glib-2.0/gio/gsettings.h:191:94: note: expected ‘const gchar * const*’ {aka ‘const char * const*’} but argument is of type ‘gchar **’ {aka ‘char **’} [ 329s] 191 | const gchar *const *value); [ 329s] | ~~~~~~~~~~~~~~~~~~~~^~~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225777] New: Package hplip does not build with gcc14 because of new errors
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225777 Bug ID: 1225777 Summary: Package hplip 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: Printing Assignee: jsmeix(a)suse.com Reporter: mjambor(a)suse.com QA Contact: jsmeix(a)suse.com 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 hplip fails to compile. This can be seen online at: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… It can be reproduced locally with command: osc build --clean --alternative-project home:rguenther:nextgcc Fedora dealt with these issues as described at https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/h/hplip.md?ref… We seem to need at least https://bugs.launchpad.net/hplip/+bug/1997875 and https://bugs.launchpad.net/hplip/+bug/2048780 The error (that halts the build) is: [ 31s] prnt/hpps/pserror.c: In function ‘message’: [ 31s] prnt/hpps/pserror.c:27:10: error: type defaults to ‘int’ in declaration of ‘column’ [-Wimplicit-int] [ 31s] 27 | static column = 0 ; /* current screen column for message wrap */ [ 31s] | ^~~~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224773] Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c23 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(rbrown(a)suse.com) |needinfo?(iforster(a)suse.com | |) CC| |iforster(a)suse.com --- Comment #23 from Richard Brown <rbrown(a)suse.com> --- I don’t have a clue, the transactional-update maintainer might -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224773] Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c22 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown(a)suse.com Flags| |needinfo?(rbrown(a)suse.com) --- Comment #22 from Stefan Dirsch <sndirsch(a)suse.com> --- Re'adding Richard. He might be able to help here. I think he has much more background about such systems and Aeon in particular. Richard, we need to figure out why blacklisting nouveau driver doesn't work on Aeon. Do you have a clue? We have a modprobe.d snippet /usr/lib/modprobe.d/nvidia-default.conf with content blacklist nouveau This is now also in initrd. But it doesn't help. nouveau driver is still loaded during boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225776] New: Flavor addons of package graphviz does not build with gcc14
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225776 Bug ID: 1225776 Summary: Flavor addons of package graphviz does not build with gcc14 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)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, flavor addons of package graphviz fails to compile. This can be seen online at: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… It can be reproduced locally with command: osc build --clean --alternative-project home:rguenther:nextgcc The error (that halts the build) is: [ 79s] tbl.c:173:15: error: assignment to ‘char *’ from incompatible pointer type ‘char (*)[1]’ [-Wincompatible-pointer-types] [ 79s] 173 | s = &cp[i].u.s; [ 79s] | ^ -- You are receiving this mail because: You are on the CC list for the bug.

1 0