October 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1078326] New: python-devel has dependency on /usr/bin/python3
by bugzilla_noreply＠novell.com 10 Jun '22

10 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1078326 Bug ID: 1078326 Summary: python-devel has dependency on /usr/bin/python3 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Another bug discovered by accident - sh** happens :) python-devel (python2 variant) has a dependency on /usr/bin/python3 - which sounds just weird digging a bit into the files and their headers, the offending file seems to be (in pyton-devel): /usr/lib64/python2.7/test/bisect.py:#!/usr/bin/python3 It being installed in py2.7 directories should imply it also wants to use python2.7 There is a 2nd file in python-devel that references python3, but that is likely less damaging: /usr/lib64/python2.7/config/Makefile.pre:PYTHON_FOR_REGEN=python3 -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1073748] New: Segfault in libpython2.7.so.1
by bugzilla_noreply＠novell.com 10 Jun '22

10 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1073748 Bug ID: 1073748 Summary: Segfault in libpython2.7.so.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: daniel(a)saltstack.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We are experiencing a SegFault with python2.7 when trying to run our test suite. [ 860.345322] salt-call[18552]: segfault at 3ea0 ip 00007ff59cede8bc sp 00007ffefe1e2170 error 4 in libpython2.7.so.1.0[7ff59ce0b000+1ae000] This is happening with the 42.2 ami on Amazon AWS, as well as 42.2 and 42.3 on Linode. We are running our test suite salt states here https://github.com/saltstack/salt-jenkins We are calling `salt-call --local state.apply git.salt pillar='{testing_dir: /tmp/kitchen/testing, clone_repo: false, salttesting_namespec: "salttesting==2017.6.1"}' saltenv=2017.7` It does have to be called as the exec from ssh for this to fail. I am attaching the core dump. Thanks, Daniel -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[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 1084909] New: trackerbug: packages do not build reproducibly from hostname
by bugzilla_noreply＠novell.com 20 May '22

20 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1084909 Bug ID: 1084909 Summary: trackerbug: packages do not build reproducibly from hostname Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Other Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1081754 Found By: Development Blocker: --- When packages include the name of the build host it results in binaries that differ on every build (because the OBS scheduler chooses a random host) It thus triggers rebuilds of depending packages. Those are then published to mirrors and users when actually nothing really changed. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[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 1096916] New: enlightenment_askpass causes X crash
by bugzilla_noreply＠novell.com 18 May '22

18 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1096916 Bug ID: 1096916 Summary: enlightenment_askpass causes X crash Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: nmoreychaisemartin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 773412 --> http://bugzilla.suse.com/attachment.cgi?id=773412&action=edit Full log Running on an updated Leap 15.0 $ rpm -q libecore1 libeina1 enlightenment libelementary1 libeo1 libevas1 libecore1-1.20.7-lp150.5.9.x86_64 libeina1-1.20.7-lp150.5.9.x86_64 enlightenment-0.22.3-lp150.2.1.x86_64 libelementary1-1.20.7-lp150.5.9.x86_64 libeo1-1.20.7-lp150.5.9.x86_64 libevas1-1.20.7-lp150.5.9.x86_64 Running enlightenment_askpass works fine. But when started through git imap-send this happens: git format-patch -M --to linux-rdma(a)vger.kernel.org --subject-prefix="PATCH rdma-core" --stdout origin/master | git imap-send ERR<14561>:ecore_evas modules/ecore_evas/engines/wayland/ecore_evas_wayland_common.c:2340 _ecore_evas_wl_common_new_internal() Failed to connect to Wayland Display (null) ## Copy & Paste the below (until EOF) into a terminal, then hit Enter eina_btlog << EOF /usr/lib64/libeina.so.1 0x7fd5b5af523c 0x7fd5b5acc000 /usr/lib64/libeina.so.1 0x7fd5b5af5f61 0x7fd5b5acc000 /usr/lib64/libeina.so.1 0x7fd5b5af7333 0x7fd5b5acc000 /usr/lib64/ecore_evas/engines/wayland/v-1.20/module.so 0x7fd5a814577a 0x7fd5a813d000 /usr/lib64/ecore_evas/engines/wayland/v-1.20/module.so 0x7fd5a81457f7 0x7fd5a813d000 /usr/lib64/libecore_evas.so.1 0x7fd5b6a9b397 0x7fd5b6a84000 /usr/lib64/libelementary.so.1 0x7fd5b93d7c13 0x7fd5b914c000 /usr/lib64/libelementary.so.1 0x7fd5b93d89f0 0x7fd5b914c000 /usr/lib64/libeo.so.1 0x7fd5b5f8e95e 0x7fd5b5f7e000 /usr/lib64/libeo.so.1 0x7fd5b5f86ffc 0x7fd5b5f7e000 /usr/lib64/libelementary.so.1 0x7fd5b93d26c2 0x7fd5b914c000 /usr/bin/enlightenment_askpass 0x55aa25b146cf 0x55aa25b13000 /usr/bin/enlightenment_askpass 0x55aa25b144dc 0x55aa25b13000 /lib64/libc.so.6 0x7fd5b86ddf4a 0x7fd5b86bd000 /usr/bin/enlightenment_askpass 0x55aa25b1451a 0x55aa25b13000 EOF Full error log attached. Note: This worked fined in Leap 42.3 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[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