May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1160071] New: Darktable 3.0.0-lp151.174.2 fails to open. Claims libdarktable.so "No such file"
by bugzilla_noreply＠novell.com 09 Jun '22

09 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1160071 Bug ID: 1160071 Summary: Darktable 3.0.0-lp151.174.2 fails to open. Claims libdarktable.so "No such file" 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: paul.pgp-7(a)gmx.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Darktable 3.0.0-lp151.174.2 (from https://download.opensuse.org/repositories/graphics/openSUSE_Leap_15.1 ) fails to open. Launching from a terminal gives the following message: paul@Orion-17:~> darktable darktable: error while loading shared libraries: libdarktable.so: cannot open shared object file: No such file or directory paul@Orion-17:~> libdarktable.so is present at /usr/lib64/darktable/ with size 3.0 MiB (3,180,448) and date/time Friday, 3 January 2020 07:29:13 GMT -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 899330] New: Interfaces does not automatically show up in firewall with NetworkManager
by bugzilla_noreply＠novell.com 05 Jun '22

05 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=899330 Bug ID: 899330 Summary: Interfaces does not automatically show up in firewall with NetworkManager Classification: openSUSE Product: openSUSE Factory Version: 201408* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: razirazo_90(a)live.com.my QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When using NetworkManager, network interfaces does not listed in firewall. I have to manually configure it using Wicked Service first, to make it registered in firewall. And then use networkManager back. This is troublesome, for example when setting up internet sharing you can't proceed to zone assign and Network masquerade until you do the step above. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1102737] New: Install does not work on Pentium III machine
by bugzilla_noreply＠novell.com 04 Jun '22

04 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1102737 Bug ID: 1102737 Summary: Install does not work on Pentium III machine 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: srid(a)rkmail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tried installing Tumbleweed on my Tualatin machine, but it fails to get to repository with following error: OpenSSL internal error, assertion failed: FATAL FIPS SELFTEST FAILURE Tried booting with fips=0, it does not help. I guess libssl wants something like SSE2, NX-bit or some other feature this old CPU lacks. Is there some chance of working around that issue? I know you'll likely don't want to bother with such an old hardware, but 'i586' in iso name 'openSUSE-Tumbleweed-NET-i586-Snapshot20180723-Media.iso' is a little bit confusing. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1080259] New: HPC modules show wrong summary
by bugzilla_noreply＠novell.com 03 Jun '22

03 Jun '22

http://bugzilla.suse.com/show_bug.cgi?id=1080259 Bug ID: 1080259 Summary: HPC modules show wrong summary Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: cgoll(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Most of the HPC lmod modules show the wrong summary. E.g. for the package openmpi-gnu-hpc thethe command module spider outputs openmpi: openmpi/1.10.7 Dependency package for openmpi_1_10_7-gnu-hpc-devel-static which is self refering and useless. It should be "A powerful implementation of MPI" -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1058563] New: hdf5 transient make check errors in TW ring2 for ppc64le
by bugzilla_noreply＠novell.com 03 Jun '22

03 Jun '22

http://bugzilla.suse.com/show_bug.cgi?id=1058563 Bug ID: 1058563 Summary: hdf5 transient make check errors in TW ring2 for ppc64le 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: --- Created attachment 740535 --> http://bugzilla.suse.com/attachment.cgi?id=740535&action=edit hdf5 build failures 20170910 hdf5 transient make check errors in TW ring2 for ppc64le On two successive hdf5 build output from OBS (1) the log is reporting different failing tests (2) If I try locally an osc co + osc build locally on two different KVM Host I am not able to recreate the problem. (1) https://build.opensuse.org/package/show/openSUSE:Factory:Rings:2-TestDVD/hd… (2) === Rings:2 on 20170910: [ 2046s] Testing h5watch TEST.h5/DSET_TWO *FAILED* [ 2046s] Testing h5watch --fields=field1,field2 TEST.h5/DSET_CMPD *FAILED* [ 2046s] Testing h5watch --fields=field2.b.a,field2.c TEST.h5/DSET_CMPD_TWO *FAILED* === Rings:2 on 20170912: [ 2087s] Testing h5watch TEST.h5/DSET_ONE *FAILED* [ 2087s] Testing h5watch TEST.h5/DSET_TWO *FAILED* [ 2087s] Testing h5watch --fields=field2.b.a --fields=field2.c TEST.h5/DSET_CMP*FAILED* [ 2087s] *FAILED* [ 2087s] Testing h5watch --fields=field2.b --fields=field4 TEST.h5/DSET_CMPD_TW*FAILED* [ 2087s] Testing h5watch --fields=field2.b.a,field2.c TEST.h5/DSET_CMPD_TWO *FAILED* [ 2087s] Testing h5watch --dim TEST.h5/DSET_ONE *FAILED* [ 2087s] Testing h5watch --width=30 TEST.h5/DSET_TWO *FAILED* === -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1154616] New: darktable: fix exporting of EXIF data to webp
by bugzilla_noreply＠novell.com 31 May '22

31 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1154616 Bug ID: 1154616 Summary: darktable: fix exporting of EXIF data to webp 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: dmitry.ashkadov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, could you apply this change https://github.com/darktable-org/darktable/commit/d18b81f2c0d42c68939632b56… to darktable please? It should fix a problem when darktable does not save EXIF information to webp format. Exported to webp format file does not contain exif information. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1165780] New: Reduce the number of PID1 reloading triggered by btrfsmaintenance units
by bugzilla_noreply＠novell.com 29 May '22

29 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1165780 Bug ID: 1165780 Summary: Reduce the number of PID1 reloading triggered by btrfsmaintenance units Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Apparently when btrfsmaintenance package is installed, the number of PID1 reloading increases from 0 to 4. Reloading PID1 is a quite expensive operation therefore it would be nice if this number could be reduced at its minimum and thus helping improving the boot process. Please note that enabling or disabling a unit implies a reload of PID1. If a batch of units needs to be enabled/disabled, it would be better to reload PID1 only at the end of the whole operation (see systemctl "--no-reload" option). For the context: this has been noticed in bnc#1137373, where the batch of PID1 reloading triggered by btrfsmaintenance makes a systemd race easier to happen. -- You are receiving this mail because: You are on the CC list for the bug.

2 112

[Bug 1156920] New: latest wpa_supplicant seems broken (2.9-1.1)
by bugzilla_noreply＠novell.com 26 May '22

26 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1156920 Bug ID: 1156920 Summary: latest wpa_supplicant seems broken (2.9-1.1) 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: roger.whittaker(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Unable to connect to wireless with wpa_supplicant-2.9-1.1.x86_64. Downgrade to wpa_supplicant-2.6-9.1.x86_64.rpm solved the problem. With 2.9-1.1, in /var/log/wpa_supplicant.log 1573837618.431976: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837618.512991: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837619.360496: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837619.431234: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837622.973427: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837623.047145: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837624.903588: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837624.987293: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837624.987338: wlp59s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="rogeroffice" auth_failures=1 duration=10 reason=CONN_FAILED 1573837634.854847: wlp59s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="rogeroffice" 1573837634.854985: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837634.935453: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837634.935488: wlp59s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="rogeroffice" auth_failures=2 duration=20 reason=CONN_FAILED 1573837636.533619: wlp59s0: Reject scan trigger since one is already pending 1573837729.947335: nl80211: deinit ifname=p2p-dev-wlp59s0 disabled_11b_rates=0 1573837730.103068: nl80211: deinit ifname=wlp59s0 disabled_11b_rates=0 After downgrade: 1573839996.915081: wlp59s0: Trying to associate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573839996.973165: wlp59s0: Associated with e4:95:6e:40:df:9d 1573839996.990751: wlp59s0: WPA: Key negotiation completed with e4:95:6e:40:df:9d [PTK=CCMP GTK=CCMP] 1573839996.990876: wlp59s0: CTRL-EVENT-CONNECTED - Connection to e4:95:6e:40:df:9d completed [id=0 id_str=] -- You are receiving this mail because: You are on the CC list for the bug.

2 23

[Bug 1161264] New: ignition, /root and installing ssh key
by bugzilla_noreply＠novell.com 24 May '22

24 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1161264 Bug ID: 1161264 Summary: ignition, /root and installing ssh key Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: iforster(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com Found By: --- Blocker: --- We have a chicken/egg problem with ignition and installing a root ssh key on a transactional-update system: /root is not mounted in initrd, you need to add an entry in the ignition config to mount /root. To do that, you need to know the device name. Which leads to two problems: 1. I don't know the device name upfront, I need to login first. But's that's not possible without working ignition config. 2. The device name varies on different machines. So you need an extra config/usb disk for every different machine. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1116084] New: Auto-mounting encrypted external disk requires root password
by bugzilla_noreply＠novell.com 22 May '22

22 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1116084 Bug ID: 1116084 Summary: Auto-mounting encrypted external disk requires root password 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: opensuserg(a)thefifthcontinent.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed 20181110 KDE Plasma Version: 5.14.3 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 Kernel Version: 4.18.15-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i7-7500U CPU @ 2.70GHz Memory: 7.7 GiB of RAM When auto-mounting an encrypted USB drive, it asks for the encryption password and if that is correct, it asks for the root password to perform the mount. When manually mounting the same drives, the root password is not required. This is the expected behaviour. -- You are receiving this mail because: You are on the CC list for the bug.

2 7