February 2018 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 1006815] New: [Build 20161024] yast2 nfs-client does not mount added export
by bugzilla_noreply＠novell.com 20 May '22

20 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1006815 Bug ID: 1006815 Summary: [Build 20161024] yast2 nfs-client does not mount added export Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jpupava(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 699166 --> http://bugzilla.suse.com/attachment.cgi?id=699166&action=edit y2logs ### observed nfs client does not mount added export, nfs client configuration is ok and the export is added in fstab, nfs client service is running but export is not mounted https://openqa.opensuse.org/tests/289982#step/yast2_nfs_client/14 ### workaround mount -a does mount nfs export ### expected added export should be also mounted linux-2cg7:~ # systemctl status nfs-client.target ● nfs-client.target - NFS client services Loaded: loaded (/usr/lib/systemd/system/nfs-client.target; disabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/nfs-client.target.d └─nfs.conf Active: active since Tue 2016-10-25 09:36:52 EDT; 36s ago Oct 25 09:36:52 linux-2cg7 systemd[1]: Reached target NFS client services. linux-2cg7:~ # linux-2cg7:~ # systemctl show nfs.service --property=Id --property=MainPID --property=Description --property=LoadState --property=ActiveState --property=SubState --property=UnitFileState --property=FragmentPath MainPID=0 Id=nfs.service Description=Alias for NFS client LoadState=loaded ActiveState=active SubState=exited FragmentPath=/usr/lib/systemd/system/nfs.service UnitFileState=enabled linux-2cg7:~ # mount|grep nfs sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) linux-2cg7:~ # linux-2cg7:~ # grep nfs /etc/fstab localhost:/tmp/nfs/server /tmp/nfs/client nfs defaults 0 0 linux-2cg7:~ # linux-2cg7:~ # mount -a linux-2cg7:~ # mount|grep nfs sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) localhost:/tmp/nfs/server on /tmp/nfs/client type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=::1,local_lock=none,addr=::1) linux-2cg7:~ # -- You are receiving this mail because: You are on the CC list for the bug.

2 41

[Bug 993885] New: Kde-Live net installer does not reboot after installation
by bugzilla_noreply＠novell.com 17 May '22

17 May '22

http://bugzilla.suse.com/show_bug.cgi?id=993885 Bug ID: 993885 Summary: Kde-Live net installer does not reboot after installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium Assignee: fvogt(a)suse.com Reporter: okurz(a)suse.com QA Contact: okurz(a)suse.com Found By: --- Blocker: --- ## observation Continuing through the whole installation process of the NET installer on the Kde-Live medium until the "reboot now" dialog shows up works fine but the reboot does not seem to happen ## steps to reproduce I am in the process of automating this but it can be as easy as * start Kde-Live * call installation from within plasma session * let installer run into "reboot now" action * observe that the system does not reboot ## expected result system should reboot into installed system ## workaround manual reboot of the system yields a properly setup Tumbleweed installation so the installation is ok. -- You are receiving this mail because: You are on the CC list for the bug.

2 31

[Bug 981004] New: Ensure template unit instances are deleted
by bugzilla_noreply＠novell.com 16 May '22

16 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=981004 Bug ID: 981004 Summary: Ensure template unit instances are deleted Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: jengelh(a)inai.de Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When a package is uninstalled, it will also be removed from the boot sequence, by means of %preun generally calling %service_del_preun foo.service, which expands to (among other things) `systemctl disable foo.service`. To disable template instances such as foo(a)bar.service and foo(a)baz.service, one can - and must, since "bar" and "baz" are not known at any time to the package management system - use `systemctl disable foo@.service`, which will disable all instances. A number of packages are lacking the corresponding %service_del_preun template@.service lines, which means template instance links like foo(a)bar.service will stick around after package uninstall. 389-ds apache2 arpwatch autossh booth chrony cups device-mapper dracut envoy freeipa govpn gpsd kmscon libteam lvm2 lvm2-clvm mariadb mdadm mgetty mysql mysql-community-server openct openvpn parkverbot rear redis rfkill syncthing system-config-printer systemd systemd-mini tomcat vpnc vsftpd wicked xf86-input-wacom -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 960478] New: krunner shows inexisting VT sessions in parallel of the existing ones
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=960478 Bug ID: 960478 Summary: krunner shows inexisting VT sessions in parallel of the existing ones Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: 64bit OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 660618 --> http://bugzilla.opensuse.org/attachment.cgi?id=660618&action=edit krunner showing non existing VT sessions in parallel to existing ones Opens a new session with the applet from desktop. You will find that krunner opens as expected but that for every VT session opened there is a "ghost session" showing the very same VT as unused. When you logout from several users these ghosts persist up to a complete reboot. VT sessions once closed should be closed without residual VTs showing up. VT sessions open should not be accompanied by a VT session ghost telling unused session. I attach a screen-shot to make the thing clearer. Repeatable always. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1074097] New: RN: "systemctl stop apparmor" intentionally broken
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1074097 Bug ID: 1074097 Summary: RN: "systemctl stop apparmor" intentionally broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: suse-beta(a)cboltz.de QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- Please add this information about AppArmor to the Leap 15 release notes (copy&paste from https://blog.cboltz.de/archives/77-AppArmor-2.12-The-Grinch-is-confined!.ht… and assuming that Leap 15 will pick up AppArmor 2.12 or newer) --- One important change in the [AppArmor 2.12] packages is that I intentionally broke "systemctl stop apparmor". The reason for this is "systemctl restart apparmor" - systemd maps this to stop, followed by start. This resulted in unloading all AppArmor profiles by the "stop" part and, even if they get loaded again a second later, running processes will stay unconfined unless you restart them. The systemd developers were unwilling to implement the proposed ExecRestart= option for unit files, therefore breaking "stop" is the best thing I can do. (See boo#996520 and boo#853019 for more details.) "systemctl reload apparmor" will continue to work and is still the recommended way to reload the AppArmor profiles, but accidently typing "restart" instead of "reload" can easily happen. Therefore I chose to break "stop" - that's annoying, but more secure than accidently removing the AppArmor confinement from running processes. If you really want to unload all AppArmor profiles, you can use the new "aa-teardown" command which does what "systemctl stop apparmor" did before - but who would do that? ;-) -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1050519] New: Description about kernel graphics update
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1050519 Bug ID: 1050519 Summary: Description about kernel graphics update Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: tiwai(a)suse.com QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- Created attachment 733812 --> http://bugzilla.opensuse.org/attachment.cgi?id=733812&action=edit Patch to release-notes.xml Some information about Leap 42.3 kernel graphics update, as Ludwig suggested in opensuse-factory ML. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1048692] New: version downgrade of libgcj_bc1
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1048692 Bug ID: 1048692 Summary: version downgrade of libgcj_bc1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: rguenther(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- 42.2 vs 42.3: libgcj48: libgcj_bc1-4.8.5-24.14.x86_64 is older than libgcj_bc1-6.2.1+r239768-5.5.2.x86_64 in 42.2 libgcj_bc1 came from libgcj-gcc6 which isn't in 42.3. What is correct here? -- You are receiving this mail because: You are on the CC list for the bug.

2 2