May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1132214] New: AppArmor config for Dovecot package needs to be fixed
by bugzilla_noreply＠novell.com 25 Oct '20

25 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1132214 Bug ID: 1132214 Summary: AppArmor config for Dovecot package needs to be fixed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: b631093f-779b-4d67-9ffe-5f6d5b1d3f8a(a)protonmail.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Someone needs to sit down and review the bundled Dovecot profiles for AppArmor, because at the moment they are distinctly lacking. And no, I don't have the AppArmor expertise necessary. So far after many hours I have found I had to add: /var/spool/postfix/private/dovecot-auth rwk, /var/spool/postfix/private/dovecot-lmtp rwk, To: /etc/apparmor.d/local/usr.lib.dovecot.auth /etc/apparmor.d/local/usr.lib.dovecot.lmtp /etc/apparmor.d/local/usr.sbin.dovecot These should really be included in the default profiles ! And now I have a problem with dsync (e.g. 'doveadm -v -o mail_fsync=never backup -R -u foobar(a)example.com imapc:') This fails with "dns_lookup(foo.example.com) failed: read(/var/run/dovecot/dns-client) failed: read(size=512) failed: Connection reset by peer" But it works fine if I do 'aa-teardown' I have tried adding: /usr/lib/dovecot/dns-client mrPx, /var/run/dovecot/dns-client mrPx, To: /etc/apparmor.d/local/usr.sbin.dovecot But that doesn't work. So please, can someone with some expertise fix this as its completely messed up right now ! -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1125653] New: Status bar of Firefox won't display in local language
by bugzilla_noreply＠novell.com 20 Oct '20

20 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1125653 Bug ID: 1125653 Summary: Status bar of Firefox won't display in local language Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: shaodan1997(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Steps to Reproduce: 1) Install MozillaFirefox and MozillaFirefox-translations-common through zypper. 2) Ensure the language pack is in effect(for me it is zh-CN). 2) Launch Firefox. 3) View any web page. Actual Results: The status bar displays in English. Expected Results: The status bar displays in local language as the language pack set. Additional Information: 1) This issue does not affect openSUSE Leap with Firefox 60.5.0. And it happens at least from Firefox version 64.0. 2) Remove MozillaFirefox-translations-common and install the Official Language Pack through https://addons.mozilla.org/firefox/language-tools/ solved this issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1127769] New: virt-bootstrap ppc64le build failed 'Architecture is not included: powerpc64le'
by bugzilla_noreply＠novell.com 16 Oct '20

16 Oct '20

http://bugzilla.suse.com/show_bug.cgi?id=1127769 Bug ID: 1127769 Summary: virt-bootstrap ppc64le build failed 'Architecture is not included: powerpc64le' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- virt-bootstrap ppc64le build failed 'Architecture is not included: powerpc64le' as reported https://build.opensuse.org/package/show/openSUSE:Factory:PowerPC/virt-boots… at least since Feb/2018 === [ 52s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define '_build_create_debug 1' --define 'disturl obs://build.opensuse.org/openSUSE:Factory:PowerPC/standard/27f99cf41cae37ee…' /home/abuild/rpmbuild/SOURCES/virt-bootstrap.spec [ 52s] error: Architecture is not included: powerpc64le === $osc jobhist -l10 openSUSE:Factory:PowerPC/virt-bootstrap standard ppc64le time package reason code build time worker 2017-09-14 03:01:53 virt-bootstrap new build succeeded 0m 38s obs-power8-05:19 2017-10-05 11:04:56 virt-bootstrap source change succeeded 0m 44s obs-power8-02:1 2018-01-31 03:48:05 virt-bootstrap new build succeeded 1m 45s obs-power8-05:32 2018-02-16 21:27:21 virt-bootstrap source change failed 1m 35s obs-power8-01:3 2018-06-02 14:29:56 virt-bootstrap source change failed 2m 45s obs-power8-03:8 2018-08-27 22:22:41 virt-bootstrap new build failed 1m 23s obs-power8-05:19 2018-11-14 14:41:43 virt-bootstrap new build failed 1m 2s obs-power8-05:3 2019-02-01 04:13:24 virt-bootstrap meta change failed 1m 4s obs-power8-07:33 === I identified the source file creating the error message in rpm*/build/parsePreamble.c === static rpmRC checkForValidArchitectures(rpmSpec spec) { char *arch = rpmExpand("%{_target_cpu}", NULL); char *os = rpmExpand("%{_target_os}", NULL); rpmRC rc = RPMRC_FAIL; /* assume failure */ if (!strcmp(arch, "noarch")) { free(arch); arch = rpmExpand("%{_build_cpu}", NULL); } if (isMemberInEntry(spec->buildRestrictions, arch, RPMTAG_EXCLUDEARCH) == 1) { rpmlog(RPMLOG_ERR, _("Architecture is excluded: %s\n"), arch); goto exit; } === Does it mean the %{_target_cpu} is converted to 'powerpc64le' ? and where is it set ? -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1113232] New: missing http://download.opensuse.org/ports/ppc64le/distribution/leap/15.1/repo/oss/
by bugzilla_noreply＠novell.com 16 Oct '20

16 Oct '20

http://bugzilla.suse.com/show_bug.cgi?id=1113232 Bug ID: 1113232 Summary: missing http://download.opensuse.org/ports/ppc64le/distributio n/leap/15.1/repo/oss/ Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: PowerPC OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Download Infrastructure Assignee: lars.vogdt(a)suse.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: lars.vogdt(a)suse.com Found By: --- Blocker: --- missing http://download.opensuse.org/ports/ppc64le/distribution/leap/15.1/repo/oss/ While testing for the first time the Leap 15.1 ppc64le net iso (just built few days ago) I experienced linuxrc error. The problem is similar to old bug for Leap 42.3 ppc64le: https://bugzilla.suse.com/show_bug.cgi?id=1047361 So I assume the correction will need same actions, even if not detailed :) -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1098807] New: gnome-shell sigsegv while openQA user_gui_login on PowerPC
by bugzilla_noreply＠novell.com 16 Oct '20

16 Oct '20

http://bugzilla.suse.com/show_bug.cgi?id=1098807 Bug ID: 1098807 Summary: gnome-shell sigsegv while openQA user_gui_login on PowerPC Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 775028 --> http://bugzilla.suse.com/attachment.cgi?id=775028&action=edit user_gui_login-journalctl.log gnome-shell sigsegv while openQA user_gui_login on PowerPC This is a transient failure in a local IBM openQA instance, not seen yet on o3. extract of journalctl === Jun 20 11:30:41 susetest gnome-session[30356]: gnome-session-binary[30356]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Jun 20 11:30:41 susetest gnome-session-binary[30356]: Unrecoverable failure in required component org.gnome.Shell.desktop Jun 20 11:30:41 susetest gnome-session-binary[30356]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Jun 20 11:30:41 susetest org.gnome.Shell.desktop[30410]: (EE) failed to read Wayland events: Broken pipe Jun 20 11:30:41 susetest polkitd[903]: Unregistered Authentication Agent for unix-session:6 (system bus name :1.165, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Jun 20 11:30:41 susetest gnome-software[30692]: plugin shell-extensions took 1.2 seconds to do setup Jun 20 11:30:41 susetest at-spi-bus-launcher[30447]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Jun 20 11:30:41 susetest at-spi-bus-launcher[30447]: after 21 requests (21 known processed) with 0 events remaining. Jun 20 11:30:41 susetest gdm-password][30335]: pam_unix(gdm-password:session): session closed for user bernhard Jun 20 11:30:41 susetest gdm[1930]: GdmDisplay: display lasted 6.479209 seconds Jun 20 11:30:41 susetest gsd-color[30205]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output Jun 20 11:30:42 susetest systemd-coredump[30808]: Process 30410 (gnome-shell) of user 1000 dumped core. Jun 20 11:30:42 susetest systemd-logind[904]: Removed session 6. === -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1133123] New: LTO: ffmpeg-4 build fails
by bugzilla_noreply＠novell.com 14 Oct '20

14 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1133123 Bug ID: 1133123 Summary: LTO: ffmpeg-4 build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- An configure options needs to be enabled and parallel linking must be enabled. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 958524] New: filesystems/cdemu-daemon: Fails to start when user is not member of cdrom
by bugzilla_noreply＠novell.com 14 Oct '20

14 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=958524 Bug ID: 958524 Summary: filesystems/cdemu-daemon: Fails to start when user is not member of cdrom Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: jengelh(a)inai.de Reporter: c.castillo.cast(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Depends on: 958517 Found By: --- Blocker: --- Using OpenSUSE Tumbleweed 64 bit and cdemu-daemon 3.0.3 Error cdemu-daemon fails to start when user is not member of cdrom group (see attachment for error message) Solution #gpasswd -a user cdrom log-out log-in Can a message be added to request the user to add himself to the cdrom group? -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1112768] New: science/openblas: request clean up openblas update-alternatives
by bugzilla_noreply＠novell.com 09 Oct '20

09 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1112768 Bug ID: 1112768 Summary: science/openblas: request clean up openblas update-alternatives Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: dmitry(a)roshchin.org Reporter: chrisbcoutinho(a)gmail.com QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- I think the BLAS/LAPACK alternatives are inconsistent. I'm not sure if this is necessarily a bug or not - some guidance would be appreciated. I have multiple versions of the BLAS/LAPACK libraries installed on my system, and I'm having trouble selecting the right ones using `update-alternatives`. I think the alternatives to the BLAS/LAPACK libraries could be cleaned up a bit. For example, /usr/lib64/libblas.so doesn't point to /usr/lib64/libblas.so.3 (or vice-versa), which causes problems if the two are not in sync. The basic BLAS library /usr/lib64/libblas.so points to /usr/lib64/blas/libblas.so.3.8.0, whereas /usr/lib64/libblas.so.3 is an alternative that can be set to any number of BLAS implementations. Instructions can be seen on the wiki regarding libblas.so.3: https://en.opensuse.org/openSUSE:Science_Linear_algebra_libraries I'm able to set libblas.so.3 using update-alternatives, but that change is not seen by cmake because of the precedence it uses to find BLAS/LAPACK (namely defaulting to /usr/lib64/openblas.so). Further, when LAPACK is required using cmake and openblas is installed, LAPACK and BLAS both default to /usr/lib64/libopenblas.so (based on /usr/lib64/cmake/openblas/OpenBLASConfig.cmake), but that in turn points to an alternative for openblas_pthreads.so.0 (why?). Shouldn't it be the other way around, where /usr/lib64/openblas.so is the alternative with options for openblas_{pthreads,openmp}.so? That way even custom (open)blas installations could be set using update-alternatives and picked up by other software using cmake by default. What is the recommended way to cleanly switch between BLAS/LAPACK implementations? -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1099674] New: spec-cleaner version update to 1.0.9
by bugzilla_noreply＠novell.com 09 Oct '20

09 Oct '20

http://bugzilla.suse.com/show_bug.cgi?id=1099674 Bug ID: 1099674 Summary: spec-cleaner version update to 1.0.9 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: tchvatal(a)suse.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- as per $SUBJ there is new version of spec-cleaner fixing few issues reported on github. -- You are receiving this mail because: You are on the CC list for the bug.

2 53

[Bug 1127701] New: fstrim -Av runs trim on each btrfs subvolume
by bugzilla_noreply＠novell.com 08 Oct '20

08 Oct '20

http://bugzilla.suse.com/show_bug.cgi?id=1127701 Bug ID: 1127701 Summary: fstrim -Av runs trim on each btrfs subvolume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: asn(a)cryptomilk.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fstrim -Av runs trim on each btrfs subvolume $ magrathea:~ # fstrim -Av /.snapshots: 23 GiB (24640622592 bytes) trimmed on /dev/sda3 /var/tmp: 25.7 GiB (27602243584 bytes) trimmed on /dev/sda3 /var/spool: 29.9 GiB (32058798080 bytes) trimmed on /dev/sda3 /var/opt: 29 GiB (31094824960 bytes) trimmed on /dev/sda3 ... $ mount /dev/sda3 on /.snapshots type btrfs (rw,relatime,ssd,space_cache,subvolid=258,subvol=/(a)/.snapshots) /dev/sda3 on /var/tmp type btrfs (rw,relatime,ssd,space_cache,subvolid=278,subvol=/@/var/tmp) /dev/sda3 on /var/spool type btrfs (rw,relatime,ssd,space_cache,subvolid=277,subvol=/@/var/spool) /dev/sda3 on /var/opt type btrfs (rw,relatime,ssd,space_cache,subvolid=276,subvol=/@/var/opt) ... This is basically bug #1020077 again, but this time with -A instead of -a! -- You are receiving this mail because: You are on the CC list for the bug.

2 21

[Bug 1124294] New: [Snapshot 20190201] SDDM login fails using wayland - after crash, login screen is shown again
by bugzilla_noreply＠novell.com 06 Oct '20

06 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1124294 Bug ID: 1124294 Summary: [Snapshot 20190201] SDDM login fails using wayland - after crash, login screen is shown again Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/846223/modules/start _wayland_plasma5/steps/32 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: slindomansilla(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Reproducible openQA scenario opensuse-Tumbleweed-DVD-x86_64-sergio-kde-wayland@64bit - [Snapshot 20190201] https://openqa.opensuse.org/tests/846223/modules/start_wayland_plasma5/step… - [Snapshot 20190202] https://openqa.opensuse.org/tests/846224#step/start_wayland_plasma5/32 -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1094790] New: Please add "openSUSE 15.0" as a possible OS at bugzilla.openSUSE.org
by bugzilla_noreply＠novell.com 04 Oct '20

04 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1094790 Bug ID: 1094790 Summary: Please add "openSUSE 15.0" as a possible OS at bugzilla.openSUSE.org Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: antoine.mechelynck(a)gmail.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Now that openSUSE 15.0 Final has been officially released (Friday 25, at noon UTC), it should be mentioned in the "OS" rolldown at bugzilla.openSUSE.org. In the meantime, the entry best fit for it is "SUSE Other" which doesn't quite fit the bill. While we're at it, we might want to remember that openSUSE 15.1 can be expected to enter the beta phase in Q1 2019, and that it ought to be possible to flag its bugs by then rather than wait for after the final release. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1122433] New: false "gsd-color[3145]: failed to set screen _ICC_PROFILE: Failed to open file “.../.local/share/icc/...icc”: Permission denied"
by bugzilla_noreply＠novell.com 03 Oct '20

03 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1122433 Bug ID: 1122433 Summary: false "gsd-color[3145]: failed to set screen _ICC_PROFILE: Failed to open file “.../.local/share/icc/...icc”: Permission denied" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When logging in to GNOME, a message is logged in the journal that I cannot reproduce. The message says: gsd-color[3145]: failed to set screen _ICC_PROFILE: Failed to open file “/home/windl/.local/share/icc/SX2462W #1 2017-05-02 23-09 2.2 F-S XYZLUT+MTX.icc”: Permission denied gsd-color[3145]: failed to set screen _ICC_PROFILE: Failed to open file “/home/windl/.local/share/icc/SX2462W #1 2018-11-25 18-28 0.3127x 0.329y S XYZLUT.icc”: Permission denied gsd-color[3145]: failed to set screen _ICC_PROFILE: Failed to open file “/home/windl/.local/share/icc/SX2462W #1 2018-11-25 18-28 0.3127x 0.329y S XYZLUT.icc”: Permission denied However when I check the file name and permissions, I get: # ll '/home/windl/.local/share/icc/SX2462W #1 2018-11-25 18-28 0.3127x 0.329y S XYZLUT.icc' -rw-r--r-- 1 windl users 833600 25. Nov 21:29 /home/windl/.local/share/icc/SX2462W #1 2018-11-25 18-28 0.3127x 0.329y S XYZLUT.icc # ll -d '/home/windl/.local/share/icc' drwxr-xr-x 2 windl users 4096 25. Nov 21:29 /home/windl/.local/share/icc # ll -d '/home/windl/.local/share' drwxr-xr-x 35 windl users 4096 18. Jan 01:13 /home/windl/.local/share # ll -d '/home/windl/.local' drwx------ 3 windl users 19 21. Nov 2014 /home/windl/.local # ll -d '/home/windl' drwxr-xr-x 56 windl users 8192 17. Jan 22:58 /home/windl # ll -d '/home' drwxr-xr-x 6 root root 64 29. Dez 00:42 /home # ll -d '/' drwxr-xr-x 22 root root 4096 19. Dez 22:04 / -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1109534] New: trackerbug: arch-dependent noarch packages
by bugzilla_noreply＠novell.com 30 Sep '20

30 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1109534 Bug ID: 1109534 Summary: trackerbug: arch-dependent noarch packages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: adrian(a)suse.com, dleuenberger(a)suse.com, lnussel(a)suse.com Depends on: 1109470 Blocks: 1081754 Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found a new class of issues that can be very hard to trace down. You have to know that OBS builds every noarch package for every architecture, publishes only one (the first in prj metadata), but uses all of them for further builds in their respective architecture in OBS. https://github.com/openSUSE/open-build-service/issues/5784 So within OBS, noarch packages are treated pretty much like architecture-dependant packages. Things only start to break once you use osc build or use the packages on a user machine and your architecture is not the one listed first in `osc meta prj` I wrote a 'noarchcheck' script that fetches noarch rpms for 2 architectures and uses build-compare to see if they are similar. Of 10899 total Factory source packages, 1218/3802 noarch packages did not pass that test. Many of the diffs seem to be harmless, so I will review the diffs and file bugs for the uglier ones and maybe file group-bugs by class of issue for the less severe diffs. -- You are receiving this mail because: You are on the CC list for the bug.

2 33

[Bug 1109895] New: .pc files in noarch -devel pkg differ from architecture
by bugzilla_noreply＠novell.com 30 Sep '20

30 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1109895 Bug ID: 1109895 Summary: .pc files in noarch -devel pkg differ from architecture Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1109534 Found By: Development Blocker: --- see bug 1109534 for background affects 4 packages: ibus-table-extraphrase mobile-broadband-provider-info spice-protocol xtrans diffs look like /usr/share/pkgconfig/mobile-broadband-provider-info.pc @@ -1,6 +1,6 @@ prefix=/usr exec_prefix=/usr -libdir=/usr/lib64 +libdir=/usr/lib datarootdir = ${prefix}/share pkgdatadir=${datarootdir}/mobile-broadband-provider-info includedir=/usr/include And come from mobile-broadband-provider-info-20170310/mobile-broadband-provider-info.pc.in: libdir=@libdir@ Can/should the libdir just be dropped from the .pc file, because the linker will include that dir anyway? -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1114807] New: New UI for firewalld: service does not stop
by bugzilla_noreply＠novell.com 30 Sep '20

30 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1114807 Bug ID: 1114807 Summary: New UI for firewalld: service does not stop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jeriveramoya(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When using the new UI for firewalld and stop service from there, after that, checking with firewall-cmd --state the service is still running (even after waiting for a while, it seems to not take any effect apparently). Expected result: after click Accept button, firewalld service should stop to match what is indicated to the user in the UI. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1114677] New: New UI for firewalld: dialog dissapear after switching service status
by bugzilla_noreply＠novell.com 30 Sep '20

30 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1114677 Bug ID: 1114677 Summary: New UI for firewalld: dialog dissapear after switching service status Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jeriveramoya(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When in Start-up menu is switched the status of the service, for an instant firewald dialog disappears. It happens when starting and when stopping too. Expected result: no flicking of the dialog visualization. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1097611] New: [Build 20180608] packages conflicting suggesting to downgrade: kubernetes-kubeadm & kubernetes-master
by bugzilla_noreply＠novell.com 30 Sep '20

30 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1097611 Bug ID: 1097611 Summary: [Build 20180608] packages conflicting suggesting to downgrade: kubernetes-kubeadm & kubernetes-master Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jeriveramoya(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation There is a problem with packages, kubernetes-kubeadm-1.9.7-1.1.x86_64 conflicts with kubernetes-master in TW: https://openqa.opensuse.org/tests/690639?machine=64bit-4G-HD40G&test=MicroO… ## Expected result Last good: [20180606](https://openqa.opensuse.org/tests/689095#step/kubeadm/6) (or more recent) -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1083434] New: Missing accessibility to Network Configuration screen in the Installer
by bugzilla_noreply＠novell.com 30 Sep '20

30 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1083434 Bug ID: 1083434 Summary: Missing accessibility to Network Configuration screen in the Installer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jeriveramoya(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 762242 --> http://bugzilla.suse.com/attachment.cgi?id=762242&action=edit openSUSE42.1-2_Network_Settings Unless the user is not connected to the Network, Network Configuration screen is not accessible, there is not button to access it as it currently implemented for SLE products. Besides the difficulties to automate testing with this hidden screen, most important is that for the user this functionality should be available. We checked previous version in case it was dropped only for Tumbleweed but we found the same result for openSUSE 13.2 or openSUSE Leap 42.1 (screenshots attached when there is not network connection). -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1114537] New: Exec and TryExec of Gimp's /usr/share/applications/gimp.desktop should be gimp
by bugzilla_noreply＠novell.com 30 Sep '20

30 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1114537 Bug ID: 1114537 Summary: Exec and TryExec of Gimp's /usr/share/applications/gimp.desktop should be gimp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: trmdi(a)yandex.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently, their values are "gimp-2.10". It should be "gimp" instead. Otherwise, it would display wrongly: - the icon on the KDE Plasma panel - the "App name" value of the Active Window Control widget on KDE. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1132940] New: Unable to connect to the network via mobile tethering using android device
by bugzilla_noreply＠novell.com 26 Sep '20

26 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1132940 Bug ID: 1132940 Summary: Unable to connect to the network via mobile tethering using android device Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: avaish92(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since my pc comes with a broadcom WiFi device, the drivers aren't preinstalled for WiFi. Hence initially I have to tether it using my android smartphone. But that too wasn't possible in the latest beta release of openSuse 15.1, and I was getting a message to configure network using Yast2. The Ethernet controller is a Realtek Device. Attaching the output of lspci. 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 01:00.0 3D controller: NVIDIA Corporation GK208M [GeForce GT 740M] (rev a1) 07:00.0 Network controller: Broadcom Limited BCM43142 802.11b/g/n (rev 01) 08:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01) 0e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 954532] New: Elantech Touchpad on Acer Aspire R11 not detected
by bugzilla_noreply＠novell.com 26 Sep '20

26 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=954532 Bug ID: 954532 Summary: Elantech Touchpad on Acer Aspire R11 not detected Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: robin.roevens1(a)pandora.be QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Installed Tumbleweed on a brand new Acer Aspire R11 (R3-131T-C56L). Turned out the Touchpad does not work. It is even not listed in /proc/bus/input/devices. The Raydium touchscreen however works correctly. I first tried Leap 42.1 on this machine but had to convert to Tumbleweed since ACPI and the VGA adapter where not correctly supported. BUT the touchpad was detected correctly and worked without problem. On Tumbleweed ACPI and VGA work correctly but no touchpad is detected. When I boot in the Leap Recovery system /proc/bus/input/devices contains this about the touchpad: I: Bus=0011 Vendor=0002 Product=000e Version=0000 N: Name="ETPS/2 Elantech Touchpad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input4 U: Uniq= H: Handlers=mouse0 event1 B: PROP=5 B: EV=b B: KEY=e420 10000 0 0 0 0 B: ABS=661800011000003 In Tumbleweed it just is not listed. -- You are receiving this mail because: You are on the CC list for the bug.

2 28

[Bug 1137009] New: KDE's diskmonitor is reporting "file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/main.qml:22:1: module "QtQuick.Layouts" version 1.11 is not installed"
by bugzilla_noreply＠novell.com 25 Sep '20

25 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1137009 Bug ID: 1137009 Summary: KDE's diskmonitor is reporting "file:///usr/share/plasma/plasmoids/org.papylhomme.dis kmonitor/contents/ui/main.qml:22:1: module "QtQuick.Layouts" version 1.11 is not installed" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ralf(a)czekalla.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since recently KDE's diskmonitor is reporting error message Fehler beim Laden der QML-Datei: file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/main.qml:22:1: module "QtQuick.Layouts" version 1.11 is not installed If I check the mentioned file file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/main.qml:22:1 I find the important lines import QtQuick 2.3 import QtQuick.Layouts 1.11 The second one I have to change into import QtQuick.Layouts 1.3 to get rid of the error message in KDE's tray area showing diskmonitor. Seems QtQuick.Layouts did change the version... Regards Ralf -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1122855] New: fpc fails to build on obs-arm-7 worker only
by bugzilla_noreply＠novell.com 25 Sep '20

25 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1122855 Bug ID: 1122855 Summary: fpc fails to build on obs-arm-7 worker only Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fpc fails to build on obs-arm-7 (ThunderX2 machine) worker but succeeds on obs-arm-4 (ThunderX1 machine). The error is: [ 468s] Searching /home/abuild/rpmbuild/BUILD/fpcbStart compiling package a52 for target aarch64-linux. [ 468s] Compiling a52/src/a52.pas [ 468s] The installer encountered the following error: [ 468s] Invalid floating point operation [ 468s] uild/fpcsrc/packages/ide/ [ 468s] make[1]: *** [Makefile:1717: smart] Error 1 [ 468s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/fpcbuild/fpcsrc/packages' [ 468s] make: *** [Makefile:2651: packages_smart] Error 2 -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 1029129] New: rpm: drop support for DISABLE_RESTART_ON_UPDATE/DISALBLE_STOP_ON_REMOVAL from /etc/sysconfig/service
by bugzilla_noreply＠novell.com 24 Sep '20

24 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1029129 Bug ID: 1029129 Summary: rpm: drop support for DISABLE_RESTART_ON_UPDATE/DISALBLE_STOP_ON_REMOVAL from /etc/sysconfig/service Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, Those 2 global options are used in /etc/sysconfig/services. DISABLE_RESTART_ON_UPDATE=yes, disable the restart of *any* services during package updates which can lead to weak system. IMHO, we shouldn't give the possibility to the user to shoot himself in the foot by providing/suggesting a way to prevent the whole system from being updated properly. In the case where a specific package needs to turn off the "restart on update" or the "stop on removal" features, due to limitation (for instance dbus-1 doesn't support restart at all), then the package can already use some mechanism (Restart=no in the unit file, ...) in its specfile. But that should be disabled (by maintainers) for specific packages only which have good reasons to do so, no turned off globally. Hence I would propose to remove these 2 knobs. -- You are receiving this mail because: You are on the CC list for the bug.

2 20

[Bug 1126447] New: Opening KMail/Kontact causes PulseAudio output to be garbled and doubled
by bugzilla_noreply＠novell.com 24 Sep '20

24 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1126447 Bug ID: 1126447 Summary: Opening KMail/Kontact causes PulseAudio output to be garbled and doubled Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: zilti(a)lyrion.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Opening KMail/Kontact causes PulseAudio output to be garbled and doubled. I think PulseAudio gets started a second time? A "killall pulseaudio" fixes it. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 976406] New: rpmlint-mini should not use its own libmagic
by bugzilla_noreply＠novell.com 24 Sep '20

24 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=976406 Bug ID: 976406 Summary: rpmlint-mini should not use its own libmagic Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- rpm -qlp ../rpmlint-mini/binaries/rpmlint-mini-1.8-0.x86_64.rpm | grep libmagic /opt/testing/lib64/libmagic.so.1 /opt/testing/lib64/libmagic.so.1.0.0 and exactly this breaks now building Base:System with new file-5.26 as the internal format of the libmagic for its magic files has changed. Note that the API for usage of libmagic has not changed! Currently I try to bootstrap Base:System with an own rpmlint-mini which would not be necessary if rpmlint-mini would use the available libmagic and its magic.mgc. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1135854] New: Compressing kernel modules (turn on MODULE_COMPRESS_XZ)?
by bugzilla_noreply＠novell.com 24 Sep '20

24 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1135854 Bug ID: 1135854 Summary: Compressing kernel modules (turn on MODULE_COMPRESS_XZ)? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mkubecek(a)suse.com, tiwai(a)suse.com Found By: --- Blocker: --- I'm in favor of enabling module compression in master & stable branches. =============== init/Kconfig =============== config MODULE_COMPRESS bool "Compress modules on installation" depends on MODULES help Compresses kernel modules when 'make modules_install' is run; gzip or xz depending on "Compression algorithm" below. module-init-tools MAY support gzip, and kmod MAY support gzip and xz. Out-of-tree kernel modules installed using Kbuild will also be compressed upon installation. Note: for modules inside an initrd or initramfs, it's more efficient to compress the whole initrd or initramfs instead. Note: This is fully compatible with signed modules. If in doubt, say N. =============== EOF =============== In particular I would go for config MODULE_COMPRESS_XZ. It saves a lot of space: - Size : 364828674 + Size : 143548638 Surprisingly, it makes the system startup faster (systemd-analyze output of 2x3 boots): compressed ========== Startup finished in 2.059s (kernel) + 9.492s (initrd) + 7.496s (userspace) = 19.049s multi-user.target reached after 7.482s in userspace Startup finished in 2.117s (kernel) + 9.977s (initrd) + 7.483s (userspace) = 19.578s multi-user.target reached after 7.469s in userspace Startup finished in 2.113s (kernel) + 10.356s (initrd) + 7.733s (userspace) = 20.203s multi-user.target reached after 7.719s in userspace non-compressed ============== Startup finished in 3.848s (kernel) + 9.932s (initrd) + 8.446s (userspace) = 22.227s multi-user.target reached after 8.422s in userspace Startup finished in 3.910s (kernel) + 10.519s (initrd) + 8.155s (userspace) = 22.584s multi-user.target reached after 8.130s in userspace Startup finished in 3.901s (kernel) + 8.572s (initrd) + 8.801s (userspace) = 21.275s multi-user.target reached after 8.766s in userspace ============================================ Note that the modules are stored untouched (i.e. compressed individually) in initrd by dracut now. This should be perhaps changed: Size of initrd with *.ko.xz in initrd: 10758844 Size of initrd with *.ko in initrd: 10611448 *.ko in initrd and *.ko.xz on disk ================================== Startup finished in 2.056s (kernel) + 9.665s (initrd) + 7.322s (userspace) = 19.044s multi-user.target reached after 7.298s in userspace Startup finished in 2.037s (kernel) + 8.131s (initrd) + 7.307s (userspace) = 17.476s multi-user.target reached after 7.294s in userspace Startup finished in 2.051s (kernel) + 8.624s (initrd) + 7.408s (userspace) = 18.084s multi-user.target reached after 7.395s in userspace ============================================ This is what I did: --- /usr/lib/dracut/dracut-init.sh.old 2019-05-22 07:52:05.296000000 +0200 +++ /usr/lib/dracut/dracut-init.sh 2019-05-22 07:56:21.600000000 +0200 @@ -903,6 +903,10 @@ inst_simple "$1" "/lib/modules/$kernel/${1##*/lib/modules/$kernel/}" ret=$? + if [ "${1##*.ko}" = ".xz" ]; then + dinfo "unxz ${initdir}/lib/modules/$kernel/${1##*/lib/modules/$kernel/}" + unxz -f "${initdir}/lib/modules/$kernel/${1##*/lib/modules/$kernel/}" + fi [[ $DRACUT_KERNEL_LAZY_HASHDIR ]] && \ [[ -d "$DRACUT_KERNEL_LAZY_HASHDIR" ]] && \ echo $ret > "$DRACUT_KERNEL_LAZY_HASHDIR/${1##*/}" FWIW Fedora already compresses modules, but they do it in their .spec file, not by the kernel config option: =============== kernel.spec =============== %ifarch %{ix86} x86_64 %global signkernel 1 %global signmodules 1 %global zipmodules 1 %else %global signkernel 0 %global signmodules 1 %global zipmodules 1 %endif ... if [ "%{zipmodules}" -eq "1" ]; then \ find $RPM_BUILD_ROOT/lib/modules/ -type f -name '*.ko' | xargs xz; \ fi \ =============== EOF =============== I am not sure why as Makefiles seem to do the right job: =============== Makefile =============== # CONFIG_MODULE_COMPRESS, if defined, will cause module to be compressed # after they are installed in agreement with CONFIG_MODULE_COMPRESS_GZIP # or CONFIG_MODULE_COMPRESS_XZ. mod_compress_cmd = true ifdef CONFIG_MODULE_COMPRESS ifdef CONFIG_MODULE_COMPRESS_GZIP mod_compress_cmd = gzip -n -f endif # CONFIG_MODULE_COMPRESS_GZIP ifdef CONFIG_MODULE_COMPRESS_XZ mod_compress_cmd = xz -f endif # CONFIG_MODULE_COMPRESS_XZ endif # CONFIG_MODULE_COMPRESS export mod_compress_cmd =============== scripts/Makefile.modinst =============== quiet_cmd_modules_install = INSTALL $@ cmd_modules_install = \ mkdir -p $(2) ; \ cp $@ $(2) ; \ $(mod_strip_cmd) $(2)/$(notdir $@) ; \ $(mod_sign_cmd) $(2)/$(notdir $@) $(patsubst %,|| true,$(KBUILD_EXTMOD)) ; \ $(mod_compress_cmd) $(2)/$(notdir $@) -- You are receiving this mail because: You are on the CC list for the bug.

2 85

[Bug 1114588] New: Keyboard Doesn't Work after resuming from sleep.
by bugzilla_noreply＠novell.com 21 Sep '20

21 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1114588 Bug ID: 1114588 Summary: Keyboard Doesn't Work after resuming from sleep. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: avaish92(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Sony Vaio SVF15218, Keyboard doesn't work after resume from sleep. The output of lspci is below. *00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 01:00.0 3D controller: NVIDIA Corporation GK208M [GeForce GT 740M] (rev a1) 07:00.0 Network controller: Broadcom Limited BCM43142 802.11b/g/n (rev 01) 08:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01) 0e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)* The kernel that I am using is *4.12.14-lp150.12.22-default* However the issue is there since I had upgraded to leap 15.0 -- You are receiving this mail because: You are on the CC list for the bug.

2 18

[Bug 1076219] New: Pkg aspell-de is missing for x86_64 tumbleweed
by bugzilla_noreply＠novell.com 21 Sep '20

21 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1076219 Bug ID: 1076219 Summary: Pkg aspell-de is missing for x86_64 tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: dheidler(a)suse.com QA Contact: ke(a)suse.com Found By: --- Blocker: --- The package search lists aspell-de, but only the i586-version is available: https://software.opensuse.org/package/aspell-de Besides the fact that a dictionary-pkg should be noarch, it is missing for x86_64. The aspell-en pkg as well as many others are not missing for x86_64. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1087809] New: crm shell / hawk, can now create iSCSITarget, backend command not called.
by bugzilla_noreply＠novell.com 19 Sep '20

19 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1087809 Bug ID: 1087809 Summary: crm shell / hawk, can now create iSCSITarget, backend command not called. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: lszhu(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- after initialized a fresh 2 nodes cluster with ha-cluster-init / join, can not create an iSCSITarget with hawk, the backend command is not called. Hawk message: 2018-04-03 11:25: Operation start failed for resource target_test on node node1: call-id=12, rc-code=generic error (1), exit-reason=none When try to add a target manually with crm shell, I see an error message: "ERROR: configure.configure: No closing quotation". The cluster is alive in crm_mon -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1129951] New: dhclient: Don't touch files in /var during post script
by bugzilla_noreply＠novell.com 17 Sep '20

17 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1129951 Bug ID: 1129951 Summary: dhclient: Don't touch files in /var during post script Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: iforster(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The dhclient package is creating its .leases files in /var as part of its post script (https://build.opensuse.org/package/view_file/network:dhcp/dhcp/dhcp.spec?ex…, currently lines 444-447). This does not work with transactional-update, as /var is not accessible during updates. In this case this may be quite hypothetical, as dhclient will probably always be installed during the initial installation anyway, but the files are still cluttering up the root file system. Creating the files sounds like a classical case for systemd-tmpfiles (if it's still necessary to manually create the files at all, maybe the lines can simply be deleted?). -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1108009] New: resolv.conf broken after rollback
by bugzilla_noreply＠novell.com 17 Sep '20

17 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1108009 Bug ID: 1108009 Summary: resolv.conf broken after rollback Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: mt(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com, kukuk(a)suse.com Found By: --- Blocker: --- /etc/resolv.conf is managed by netconfig. netconfig stores the md5sum of the file in /var/adm/netconfig/md5 to detect user modifications. /var is on a separate subvolume however, so when performing a rollback /etc/resolv.conf gets rolled back bug /var isn't. So the checksum may no longer match if resolv.conf changed between the target snapshot and the current system. netconfig would therefore install /etc/resolv.conf.netconfig after boot, causing DNS resolving problems. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1091333] New: No 42.2 branch for /security:/OpenVAS:/STABLE:/v8/ repo
by bugzilla_noreply＠novell.com 17 Sep '20

17 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1091333 Bug ID: 1091333 Summary: No 42.2 branch for /security:/OpenVAS:/STABLE:/v8/ repo Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: qantas94heavy(a)gmail.com QA Contact: bnc-team-screening(a)forge.provo.novell.com CC: mikhail.kasimov(a)gmail.com, qantas94heavy(a)gmail.com Depends on: 1011588 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1011588 +++ As reported in bug 1011588, a Leap 15.0 branch appears to be missing. http://download.opensuse.org/repositories/security:/OpenVAS:/STABLE:/v8/ -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1131540] New: AMD Athlon 64 based system (K8 microarchitecture) hangs when AMD Cool'n'Quiet is turned on
by bugzilla_noreply＠novell.com 16 Sep '20

16 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1131540 Bug ID: 1131540 Summary: AMD Athlon 64 based system (K8 microarchitecture) hangs when AMD Cool'n'Quiet is turned on Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: kaykaykay123(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- AMD Athlon 64 based system (K8 microarchitecture) hangs when AMD Cool'n'Quiet is turned on in about two hours after booting the system. Solution: turn off AMD K8 Cool'n'Quiet in BIOS. Additional info: during installation process stops with a message "Wrong digest", especially with a huge files, such as "kernel-firmware". Testing DVD image shows errors. Updating BIOS and other measures had no effect. After disabling AMD K8 Cool'n'Quiet in BIOS dmesg shows: --------------------------------------------------------------------------- powernow_k8: [Firmware Bug]: No compatible ACPI _PSS objects found. [Firmware Bug]: First, make sure Cool'N'Quiet is enabled in the BIOS. [Firmware Bug]: If that doesn't help, try upgrading your BIOS. --------------------------------------------------------------------------- This problem is also observed with a Leap 42.3. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1125327] New: /sbin/purge-kernels is in endless loop since last maintenance update
by bugzilla_noreply＠novell.com 16 Sep '20

16 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1125327 Bug ID: 1125327 Summary: /sbin/purge-kernels is in endless loop since last maintenance update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: adrian(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- /sbin/purge-kernels is permanent trying to purge my kernel since last maintainenace update. However, it always fails since it is not taking into accoung that another package may depend on it: /sbin/purge-kernels: virtualbox-host-kmp = 5.2.22 is needed by (installed) virtualbox-5.2.22-lp150.4.23.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

2 35

[Bug 1010760] New: sysconfig-netconfig: leftover /tmp/ntp-servers-netconfig.*
by bugzilla_noreply＠novell.com 15 Sep '20

15 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1010760 Bug ID: 1010760 Summary: sysconfig-netconfig: leftover /tmp/ntp-servers-netconfig.* Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: mt(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- $ ls -1 /tmp/ntp-servers-netconfig.*|wc -l 4469 You already put the DEST file into /run. How about putting that file there as well and avoid mktemp? -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 968405] New: xdm restarts the user session on update
by bugzilla_noreply＠novell.com 15 Sep '20

15 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=968405 Bug ID: 968405 Summary: xdm restarts the user session on update Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: tchvatal(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- When system during update is updating xdm it takes down restarts the graphical user session with everything in it. It seems like the try-restart is not nice in this case enough to simply wait for user to exit the session and just kills everything. -- You are receiving this mail because: You are on the CC list for the bug.

2 56

[Bug 1121721] New: docker-compose broken on TW20190110
by bugzilla_noreply＠novell.com 15 Sep '20

15 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1121721 Bug ID: 1121721 Summary: docker-compose broken on TW20190110 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: gm.venekamp(a)quicknet.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After zypper dup for TW20190110 docker-compose is broken. Using docker-compose results in the following dump: > docker-compose --version Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 581, in _build_master ws.require(__requires__) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 898, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 789, in resolve raise VersionConflict(dist, req).with_context(dependent_req) pkg_resources.ContextualVersionConflict: (docker 3.5.1 (/usr/lib/python3.6/site-packages), Requirement.parse('docker<4.0,>=3.6.0'), {'docker-compose'}) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/docker-compose", line 6, in <module> from pkg_resources import load_entry_point File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3126, in <module> @_call_aside File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3110, in _call_aside f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3139, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 583, in _build_master return cls._build_from_requirements(__requires__) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 596, in _build_from_requirements dists = ws.resolve(reqs, Environment()) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 784, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'docker<4.0,>=3.6.0' distribution was not found and is required by docker-compose -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1116413] New: Application:Geo/qgis: Bug qgis fails to find PyQt5.sip on startup
by bugzilla_noreply＠novell.com 14 Sep '20

14 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1116413 Bug ID: 1116413 Summary: Application:Geo/qgis: Bug qgis fails to find PyQt5.sip on startup Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: dassau(a)gbd-consult.de Reporter: michael(a)actrix.gen.nz QA Contact: bnc-team-screening(a)forge.provo.novell.com CC: tzotsos(a)gmail.com Found By: --- Blocker: --- Installed qgis, at startup it complains that python will not be enabled after it fails to import PyQt5.sip. I have tumbleweeds's python3-qt5 and python-qt5-utils installed. FIRST POPUP DIALOG CONTENTS: Couldn't load PyQGIS. Python support will be disabled. Traceback (most recent call last): File "", line 1, in File "/usr/share/qgis/python/qgis/core/__init__.py", line 27, in from qgis._core import * ModuleNotFoundError: No module named 'PyQt5.sip' SECOND POPUP DIALOG CONTENTS: An error occurred during execution of following code: qgis.utils.uninstallErrorHook() Traceback (most recent call last): File "", line 1, in NameError: name 'qgis' is not defined Python version: 3.6.5 (default, Mar 31 2018, 19:45:04) [GCC] -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1113225] New: shim build failed with hash is unmatched
by bugzilla_noreply＠novell.com 14 Sep '20

14 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1113225 Bug ID: 1113225 Summary: shim build failed with hash is unmatched Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- shim in Leap 15.1 build failed recently, the error log: [ 60s] + chmod 755 /home/abuild/rpmbuild/SOURCES/timestamp.pl [ 60s] + test -n /home/abuild/rpmbuild/SOURCES/signature-opensuse.asc [ 60s] + head -1 /home/abuild/rpmbuild/SOURCES/signature-opensuse.asc [ 60s] + cp shim.efi shim.efi.bak [ 60s] + /home/abuild/rpmbuild/SOURCES/timestamp.pl --set-from-file /home/abuild/rpmbuild/SOURCES/signature-opensuse.asc shim.efi [ 60s] + pesign -h -P -i shim.efi [ 60s] + cat hash1 hash2 [ 60s] hash: 3be8e7eb348d35c1928f19c769846788991641d1f6cf09514ca10269934f7359 [ 60s] hash: 162c2814c4319dad606e51b9bb5041a5e7ba126ce183794a5ddf439798973bca [ 60s] + cmp -s hash1 hash2 [ 60s] + echo 'ERROR: opensuse binary changed, need to request new signature!' [ 60s] ERROR: opensuse binary changed, need to request new signature! [ 60s] + false This is not caught in staging project period because shim_enforce_ms_signature is not set. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1108570] New: After restarting NetworkManager service, it cannot read passwords from wallet
by bugzilla_noreply＠novell.com 12 Sep '20

12 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1108570 Bug ID: 1108570 Summary: After restarting NetworkManager service, it cannot read passwords from wallet Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: adam(a)mizerski.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Requirements: - KDE - NetworkManager that has a wifi password saved in kwallet Steps to reproduce: - connect to password protected wifi - sudo systemctl restart NetworkManager Expected result: - wifi is set up correctly Actual result: - passwords don't show in gui in wifi security section - connecting to wifi fails, logs says: <info> [1537078992.8413] device (wlp1s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') <warn> [1537078992.9063] device (wlp1s0): No agents were available for this request. <info> [1537078992.9067] device (wlp1s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Workarounds: - `nmcli connection up <connection name> --ask` - log out and log in again -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1109373] New: [HPC, slurm] slurm-node & slurm-config not setup right in %pre/%post scriptlets due to missing Requires(pre/post)
by bugzilla_noreply＠novell.com 11 Sep '20

11 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1109373 Bug ID: 1109373 Summary: [HPC, slurm] slurm-node & slurm-config not setup right in %pre/%post scriptlets due to missing Requires(pre/post) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: CONFIRMED Severity: Major Priority: P5 - None Component: Other Assignee: eich(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de CC: hpc-maintainer-bugs(a)forge.provo.novell.com, nicolas.bock(a)suse.com Found By: Development Blocker: --- Symptoms: when installed during initial system installation, the slurm user may not be set up correctly. Reason: 'slurm-config' requires 'shadow' during pre-install. This is however wrongly added as Requires(pre) to 'slurm'. Fix: Move the requires from 'slurm' to 'slurm-node'. Moreover, it should have access to systemd due to the use of 'systemd-tmpfiles' (or the correspondig macro if available). 'slurm-node' should have the access to systemd during %pre/%post. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1085606] New: [SLURM] standard epilog will kill all remaining processes
by bugzilla_noreply＠novell.com 11 Sep '20

11 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1085606 Bug ID: 1085606 Summary: [SLURM] standard epilog will kill all remaining processes Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: cgoll(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The standard epilog script will kill all remaining processes on a node. This should be mentioned in in the config and as well in the release nodes. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1112645] New: tuned-profiles-oracle partially does not work
by bugzilla_noreply＠novell.com 08 Sep '20

08 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1112645 Bug ID: 1112645 Summary: tuned-profiles-oracle partially does not work Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: achim(a)klaurie.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed tuned and tuned-profiles-oracle and the following values are not set respectively modified: kernel.shmall kernel.shmmax kernel.shmmni vm.dirty_ratio Steps to install: zypper install tuned tuned-profiles-oracle systemctl enable tuned systemctl start tuned tuned-adm profile oracle My database is 'Oracle Express Edition 11'. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1068647] New: btrfs send bails out on orphan inode
by bugzilla_noreply＠novell.com 01 Sep '20

01 Sep '20

http://bugzilla.suse.com/show_bug.cgi?id=1068647 Bug ID: 1068647 Summary: btrfs send bails out on orphan inode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I can't create backups of my currently active subvolume with btrfs send any more. It proceeeds for several minutes, than bails out with the error message ERROR: send ioctl failed with -2: No such file or directory This situation has persisted throughout several reboots, remounts, and kernel updates. This first occured while I was doing lots of experiments with btrfs-send, working on my "btrfs-clone" utility (https://github.com/mwilck/btrfs-clone) and testing the efficiency of various cloning strategies within this tool. I made several successful snapshots, until suddenly the described situation came to pass which makes it impossible to do any more snapshots of the "main" subvol. Thus it's possible that the situation was caused by btrfs-send. I admit I did this while the subvolume was mounted. Of course I'd always set the cloned subvolume and its parent to read-only mode while ran btrfs-send (it will abort otherwise). Except for the btrfs-send, no other problems have been observed so far. All other tools (btrfs image, btrfs scrub, btrfs inspect-internal dump-tree) silently ignored this situation. I've traced the error down to the following call stack: > send_subvol() > full_send_tree() > changed_cb [btrfs]() > finish_inode_if_needed [btrfs]() > get_inode_info.constprop.48 [btrfs]() > apply_children_dir_moves [btrfs]() > send_utimes [btrfs]() > get_cur_path [btrfs]() > __get_cur_name_and_parent [btrfs]() > is_inode_existent.part.15 [btrfs]() > get_first_ref [btrfs]() get_first_ref() returns with -ENOENT. I used some instrumentation to find out what was causing this problem, and found the following situation in the file system tree: root tree 28090400768(level 0) / 28058992640(1) - subvol @/.subvols/1/snapshot is item 89 at 28061384704 > root tree > node 28058992640 level 1 items 5 free 488 generation 188885 owner 1 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > key (EXTENT_TREE ROOT_ITEM 0) block 28090400768 (1714502) gen 188885 > > leaf 28090400768 items 98 free space 6117 generation 188885 owner 1 > leaf 28090400768 flags 0x1(WRITTEN) backref revision 1 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > > item 5 key (ROOT_TREE_DIR INODE_ITEM 0) itemoff 14770 itemsize 160 > generation 3 transid 0 size 0 nbytes 16384 > block group 0 mode 40755 links 1 uid 0 gid 0 rdev 0 > sequence 0 flags 0x0(none) > atime 1493728330.0 (2017-05-02 14:32:10) > ctime 1493728330.0 (2017-05-02 14:32:10) > mtime 1493728330.0 (2017-05-02 14:32:10) > otime 1493728330.0 (2017-05-02 14:32:10) > > item 12 key (257 ROOT_ITEM 0) itemoff 13191 itemsize 439 > generation 180352 root_dirid 256 bytenr 36967874560 level 0 refs 1 > lastsnap 12 byte_limit 0 bytes_used 16384 flags 0x0(none) > uuid d4ad4958-2cc1-004e-934d-f223ef4c5f2a > ctransid 180352 otransid 8 stransid 0 rtransid 0 > drop key (0 UNKNOWN.0 0) level 0 > item 13 key (257 ROOT_BACKREF 5) itemoff 13172 itemsize 19 > root backref key dirid 256 sequence 2 name @ > > item 33 key (258 ROOT_ITEM 0) itemoff 12290 itemsize 439 > generation 188511 root_dirid 256 bytenr 17933533184 level 1 refs 1 > lastsnap 0 byte_limit 0 bytes_used 163840 flags 0x0(none) > uuid e99de79b-c494-9445-812b-d08389f82947 > ctransid 188511 otransid 11 stransid 0 rtransid 0 > drop key (0 UNKNOWN.0 0) level 0 > item 34 key (258 ROOT_BACKREF 257) itemoff 12262 itemsize 28 > root backref key dirid 256 sequence 3 name .snapshots > > item 89 key (259 ROOT_ITEM 12) itemoff 10419 itemsize 439 > generation 188884 root_dirid 256 bytenr 28061384704 level 2 refs 1 > lastsnap 186971 byte_limit 0 bytes_used 259981312 flags 0x0(none) > uuid 17c54832-5028-694c-9f97-1be0a1df8757 > parent_uuid d4ad4958-2cc1-004e-934d-f223ef4c5f2a > ctransid 188884 otransid 12 stransid 0 rtransid 0 > drop key (0 UNKNOWN.0 0) level 0 > item 90 key (259 ROOT_BACKREF 258) itemoff 10393 itemsize 26 > root backref key dirid 257 sequence 2 name snapshot File system tree 28061384704 - btrfs path 28052832256(level 0) / 28045197312(1) / 28061384704(2) - item 8 (1746132 INODE_ITEM 0) has "links 0" and no ref - item 86 is an ORPHAN node linking to item 8. > file tree key (259 ROOT_ITEM 12) > node 28061384704 level 2 items 56 free 437 generation 188884 owner 259 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > > key (1732417 INODE_REF 830626) block 28045197312 (1711743) gen 188860 > > node 28045197312 level 1 items 341 free 152 generation 188860 owner 259 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > ... > key (1746122 INODE_ITEM 0) block 28052832256 (1712209) gen 188821 > > leaf 28052832256 items 66 free space 8146 generation 188821 owner 259 > leaf 28052832256 flags 0x1(WRITTEN) backref revision 1 > fs uuid ad544c37-37f9-44a4-9798-d29d3cb5db44 > chunk uuid bb2d5d7b-6b0b-4f2d-9677-097711ef8572 > ... > item 7 key (1746123 EXTENT_DATA 4096) itemoff 15701 itemsize 53 > generation 188295 type 1 (regular) > extent data disk byte 470392832 nr 4096 > extent data offset 0 nr 4096 ram 4096 > extent compression 0 (none) > item 8 key (1746132 INODE_ITEM 0) itemoff 15541 itemsize 160 > generation 188295 transid 188472 size 940 nbytes 4096 > block group 0 mode 100644 links 0 uid 465 gid 464 rdev 0 > sequence 16 flags 0x6(PREALLOC) > atime 1510830949.715375999 (2017-11-16 12:15:49) > ctime 1510838729.976180731 (2017-11-16 14:25:29) > mtime 1510830949.687375946 (2017-11-16 12:15:49) > otime 1510830949.687375946 (2017-11-16 12:15:49) > item 9 key (1746132 EXTENT_DATA 0) itemoff 15488 itemsize 53 > generation 188295 type 1 (regular) > extent data disk byte 470614016 nr 4096 > extent data offset 0 nr 4096 ram 4096 > extent compression 0 (none) > item 10 key (1746213 INODE_ITEM 0) itemoff 15328 itemsize 160 > generation 188342 transid 188819 size 6498 nbytes 8192 > block group 0 mode 100600 links 1 uid 0 gid 0 rdev 0 > sequence 0 flags 0x4(none) > atime 1510849204.24960545 (2017-11-16 17:20:04) > ctime 1510833103.94629539 (2017-11-16 12:51:43) > mtime 1510833103.86629524 (2017-11-16 12:51:43) > otime 1510833037.158509427 (2017-11-16 12:50:37) > ... > item 85 key (1746369 EXTENT_DATA 0) itemoff 7030 itemsize 53 > generation 188860 type 1 (regular) > extent data disk byte 368373760 nr 4096 > extent data offset 0 nr 4096 ram 4096 > extent compression 0 (none) > item 86 key (ORPHAN ORPHAN_ITEM 1746132) itemoff 7030 itemsize 0 > orphan item So, while trying to process inode 1746213, btrfs send runs finish_inode_if_needed() on 1746132, and fails to send the utimes for this inode because it can't figure out the path. The way I'm reading the btrfs code, it seems that btrfs-send assumes that all orphans have been cleaned up when it starts running. Indeed, btrfs should have got rid of orphan nodes by running btrfs_orphan_cleanup() via btrfs_cleanup_fs_roots() at mount time, but that doesn't seem to be the case. In fact, I've run btrfs-debug tree on this file system two times with different FS generations, and found that the orphan inode hat changed its position (inode number) in the tree. Unfortunately I didn't keep the output of the first debug run, but I'm positive that the inode number of the failing inode was in the 1743xxx range first, and is now 1746132. Therefore I'm filing this as a kernel bug. The problem was first seen with kernel 4.13.11-1.1.g0526da3 now I'm running 4.14.0-1.1.gab9e909. There are 3 aspects to this problem: 1) how did it come to pass? 2) why doesn't the kernel clean up the orphan at boot time? Why does the orphan change inode number? Or is the orphan actually cleaned, but a new one is generated instead? 3) how do I recover? I'd really love to get rid of this broken inode. I could simply switch to a different snapshot of the file system, but AFAICS as long as I don't delete the offending subvolume, the situation would persist. Anyway, as long as 1) and 2) are open, I guess I'd rather keep the subvolume around to facilitate further debugging. I'm unsure if this is easily reproducible. -- You are receiving this mail because: You are on the CC list for the bug.

2 21

[Bug 1133893] New: Incorrect colors being displayed by "display" for a 10-bit LUT (it seems)
by bugzilla_noreply＠novell.com 01 Sep '20

01 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1133893 Bug ID: 1133893 Summary: Incorrect colors being displayed by "display" for a 10-bit LUT (it seems) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 803995 --> http://bugzilla.opensuse.org/attachment.cgi?id=803995&action=edit Windows-Shot of incorrect display When I use ImageMagick-7.0.7.34-lp150.2.26.1.x86_64 to display an image, the colors look significantly wrong, and the image is partly transparent. However when I open the same image on the same display with GIMP or Firefox, the image looks correct. The only special thing seems to be my "HDR" display featuring a 10-bit lookup-table (LUT) for my ATI Radeon: "ATI Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X]" Driver: "amdgpu" The visual probably is like this: visual: visual id: 0x5af class: TrueColor depth: 32 planes available colormap entries: 1024 per subfield red, green, blue masks: 0x3ff00000, 0xffc00, 0x3ff significant bits in color specification: 10 bits -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 1051159] New: GTK3 file picker in print section of Firefox/Thunderbird
by bugzilla_noreply＠novell.com 31 Aug '20

31 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1051159 Bug ID: 1051159 Summary: GTK3 file picker in print section of Firefox/Thunderbird Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: roman(a)pletka.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Change the gtk3 file picker when printing a page as a pdf file. Steps: firefox is on any web page, print (Ctrl +P, or file->print...) select "print to file" click on file name opens a gtk3 file picker. The whole file dialog is GTK3, that needs to be implemented in mozilla-kde.patch. Thanks, Roman -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1117502] New: xemacs Unable to load any usable
by bugzilla_noreply＠novell.com 31 Aug '20

31 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1117502 Bug ID: 1117502 Summary: xemacs Unable to load any usable Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: ericj(a)mcalvin.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0 Build Identifier: With locale set to en_US.UTF-8, xemacs (and xclock and xfd) all show the warning: Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset Note that this issue did not exist in Leap 42.3. It appeared in 15.0. Reproducible: Always Steps to Reproduce: 1. ensure locale is set to: en_US.UTF-8 2. run: xemacs Actual Results: Console shows warning: Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset And xemacs (vm mail module) will not be able to display mail. Error displayed is: xintl/error Can't initialize XIM: Can't get fontset resource for Input Method Expected Results: xemacs should not display that warning, and vm module will be able to display the mail without that error message. As a workaround, you can run: export LANG=en_US xemacs Which corrects the issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 20

[Bug 1135237] New: modesetting driver and xvnc: bad performance
by bugzilla_noreply＠novell.com 29 Aug '20

29 Aug '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1135237 Bug ID: 1135237 Summary: modesetting driver and xvnc: bad performance Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: P.Suetterlin(a)royac.iac.es QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Not sure if that is a real bug, but I thought I report it here: I am running Tumbleweed (latest version, as of now 20190512) on an ASUS PN40 (Celeron N4000(a)1.1GHz, Gemini lake) for controlling a small telescope (via INDI). It is running headless, and I use x11vnc_ssh to connect to it (it runs a real X session with autologin, icewm as session). The xserver by default uses the modesetting driver. With that, when I connect using xvnc, the CPU load of the X server (X, not xvnc) goes up to some 80-90% just for displaying the empty desktop, still the display is sluggish close to being unusable, with sometimes latencies in the second range (this is on a Gbit cable network). If instead I use the intel driver (xf86-video-intel) CPU load is below 10%, screen updates are very quick, without much latency. -- You are receiving this mail because: You are on the CC list for the bug.

2 24