November 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 942751] New: python3 test / missing __main__ module
by bugzilla_noreply＠novell.com 17 Feb '22

17 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=942751 Bug ID: 942751 Summary: python3 test / missing __main__ module Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: myemailu(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When running python 3 -m test the output is: Traceback (most recent call last): File "/usr/lib64/python3.4/runpy.py", line 170, in _run_module_as_main "__main__", mod_spec) File "/usr/lib64/python3.4/runpy.py", line 85, in _run_code exec(code, run_globals) File "/usr/lib64/python3.4/_import_failed/test.py", line 21, in <module> Please file a bug on the SUSE Bugzilla.""".format(__name__)) ImportError: Module '__main__' is not installed. It is supposed to be part of python3 distribution, but missing from failed import map. Please file a bug on the SUSE Bugzilla. I'm using python3 on Tumbleweed rpm -qi python3 Name : python3 Version : 3.4.3 Release : 4.1 Architecture: x86_64 Install Date: Mi 29 Jul 2015 22:03:48 CEST Group : Development/Languages/Python Size : 2996719 License : Python-2.0 Signature : RSA/SHA256, Di 28 Jul 2015 11:49:27 CEST, Key ID b88b2fd43dbdc284 Source RPM : python3-3.4.3-4.1.src.rpm Build Date : Di 28 Jul 2015 11:49:14 CEST Build Host : build75 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://www.python.org/ Summary : Python3 Interpreter -- You are receiving this mail because: You are on the CC list for the bug.

2 26

[Bug 1029902] New: Fatal Python error: failed to get random numbers to initialize Python3
by bugzilla_noreply＠novell.com 17 Feb '22

17 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=1029902 Bug ID: 1029902 Summary: Fatal Python error: failed to get random numbers to initialize Python3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Several packages in packman fail since a few days: [ 53s] + cd Photini-2016.12.0 [ 53s] + python3 setup.py build [ 53s] Fatal Python error: failed to get random numbers to initialize Python It happens to work in 'graphics', but not in Packman. strace shows: 1337 13:17:06.361953 getrandom(0x7f9d23bbd770, 24, 0) = -1 ENOSYS (Function not implemented) 1337 13:17:06.362176 write(2, "Fatal Python error: failed to get random numbers to initialize Python\n", 70) = 70 Leap does this, and succeeds: 1283 13:17:05.902494 open("/dev/urandom", O_RDONLY|O_CLOEXEC) = 3 -- You are receiving this mail because: You are on the CC list for the bug.

2 36

[Bug 997614] New: python's platform.linux_distribution() doesn't understand /etc/os-release
by bugzilla_noreply＠novell.com 17 Feb '22

17 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=997614 Bug ID: 997614 Summary: python's platform.linux_distribution() doesn't understand /etc/os-release Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tserong(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- > cat /etc/SuSE-release cat: /etc/SuSE-release: No such file or directory > cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20160831" ID=opensuse ID_LIKE="suse" VERSION_ID="20160831" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20160831" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" > python -c 'import platform ; print platform.linux_distribution()' ('', '', '') That's odd. Python doesn't know what distro we're running on. But, on an earlier Tumbleweed release: > cat /etc/SuSE-release openSUSE 20160701 (x86_64) VERSION = 20160701 CODENAME = Tumbleweed # /etc/SuSE-release is deprecated and will be removed in the future, use /etc/os-release instead > cat /etc/os-release NAME=openSUSE VERSION="Tumbleweed" VERSION_ID="20160701" PRETTY_NAME="openSUSE Tumbleweed (20160701) (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:20160701" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" ID_LIKE="suse" > python -c 'import platform ; print platform.linux_distribution()' ('openSUSE ', '20160701', 'x86_64') Turns out the file matching in /usr/lib64/python2.7/platform.py (line 323+) is looking for files named /(\w+)[-_](release|version)/, so it picks up "os-release", and decides _distname is "os", which *isn't* in _supported_dists (_supported_dists includes "SuSE", "debian", "fedora", etc. but no generic "os"). So, as we apparently no longer ship SuSE-release, and there's no other release-like files to parse, and we end up with platform.linux_distribution() having no idea what's going on. -- You are receiving this mail because: You are on the CC list for the bug.

2 34

[Bug 917759] New: osc fails with a python exception
by bugzilla_noreply＠novell.com 17 Feb '22

17 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=917759 Bug ID: 917759 Summary: osc fails with a python exception Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lmb(a)suse.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- This is about the latest osc client on Factory (osc-0.150.1-158.1.noarch) used on the internal build service instance: # iosc rdiff Devel:Storage:1.0 _product SUSE:SLE-12:Update:Products:Cloud5 Traceback (most recent call last): File "/usr/bin/osc", line 26, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 61, in run return prg.main(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 343, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 366, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 500, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1230, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 3593, in do_rdiff expand=not opts.unexpand) File "/usr/lib/python2.7/site-packages/osc/core.py", line 4488, in server_diff_noex unified, missingok, meta, expand) File "/usr/lib/python2.7/site-packages/osc/core.py", line 4477, in server_diff f = http_POST(u) File "/usr/lib/python2.7/site-packages/osc/core.py", line 3201, in http_POST def http_POST(*args, **kwargs): return http_request('POST', *args, **kwargs) File "/usr/lib/python2.7/site-packages/osc/core.py", line 3144, in http_request install_opener(conf._build_opener(url)) File "/usr/lib/python2.7/site-packages/osc/conf.py", line 507, in _build_opener from . import oscssl File "/usr/lib/python2.7/site-packages/osc/oscssl.py", line 8, in <module> import M2Crypto.httpslib File "/usr/lib64/python2.7/site-packages/M2Crypto/__init__.py", line 24, in <module> import ASN1 File "/usr/lib64/python2.7/site-packages/M2Crypto/ASN1.py", line 12, in <module> import BIO File "/usr/lib64/python2.7/site-packages/M2Crypto/BIO.py", line 221, in <module> class CipherStream(BIO): File "/usr/lib64/python2.7/site-packages/M2Crypto/BIO.py", line 227, in CipherStream SALT_LEN = m2.PKCS5_SALT_LEN AttributeError: 'module' object has no attribute 'PKCS5_SALT_LEN' Most invocations fail like that for me, including "osc up", submitreq, etc, making it completely unusable for me. -- You are receiving this mail because: You are on the CC list for the bug.

2 21

[Bug 1057496] New: devel:languages:python/python-six: egg-info can't be unpacked, cpio rename
by bugzilla_noreply＠novell.com 16 Feb '22

16 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1057496 Bug ID: 1057496 Summary: devel:languages:python/python-six: egg-info can't be unpacked, cpio rename Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: openSUSE Factory Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software Assignee: jmatejek(a)suse.com Reporter: i(a)marguerite.su QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- happened on latest TW, message: Installation of python2-six-1.10.0-4.2.noarch failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/lib/python2.7/site-packages/six-1.10.0-py2.7.egg-info: cpio rename error: python2-six-1.10.0-4.2.noarch: install failed This same message occurs at installing python2-six and python2-PyYAML, so it's a common issue. This issue will cause those packages not installed onto the system. As python2-six is a system essential package, please take a look and fix ASAP. A little hint: I upgraded several tumbleweed on different servers. And I remembered I saw messages complain that egg-info is a directory. Marguerite -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1067727] New: Drop libgnome and libgnomeui - deprecated upstream
by bugzilla_noreply＠novell.com 11 Feb '22

11 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1067727 Bug ID: 1067727 Summary: Drop libgnome and libgnomeui - deprecated upstream Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: zaitor(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- libgnome and libgnomeui are both deprecated upstream, openSUSE should try to removed their use in distro. Currently these packages depend on libgnome libgnome : MozillaThunderbird bareftp distcc eclipse-swt etherape gcompris girl giver gjiten gnome-color-chooser gnome-commander gnome-desktop-sharp2 gnome-do gnome-do-plugins gnome-python-desktop gnome-sharp2 gnucash gtkam gwget ignuit jack-rack jogl2 libbonoboui libgnomeui mdbtools novell-nortelplugins ocaml-lablgtk2 opa-fmgui paperclips perl-Gnome2 planner plplot presage python-gnome seamonkey swtcalendar swtchart taglib-sharp thunarx-python tuxguitar tuxpaint unison xscreensaver and on libgnomeui libgnomeui : MozillaThunderbird distcc eclipse-swt etherape gcompris girl gjiten gnome-color-chooser gnome-commander gnome-python-desktop gnome-sharp2 gnucash gtkam gwget ignuit jack-rack jogl2 mdbtools ocaml-lablgtk2 paperclips perl-Gnome2 planner plplot python-gnome seamonkey swtcalendar swtchart thunarx-python tuxguitar unison -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 936416] New: harfbuzz 32bit devel package missing symlinks
by bugzilla_noreply＠novell.com 10 Feb '22

10 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=936416 Bug ID: 936416 Summary: harfbuzz 32bit devel package missing symlinks Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: admin(a)leinir.dk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The 32bit devel package of harfbuzz (and accompanying harfbuzz-icu) is missing the .so symlinks in /usr/lib. Temporary workaround: ln -s libharfbuzz.so.0 /usr/lib/libharfbuzz.so ln -s libharfbuzz-icu.so.0 /usr/lib/libharfbuzz-icu.so -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 954329] New: Purely virtual bridge breaks networking
by bugzilla_noreply＠novell.com 08 Feb '22

08 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=954329 Bug ID: 954329 Summary: Purely virtual bridge breaks networking Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Take a purely virtual bridge (to be used for VMs) with a static network configuration: # cat /etc/sysconfig/network/ifcfg-br0 STARTMODE='auto' BOOTPROTO='static' BRIDGE='yes' BRIDGE_PORTS='' BRIDGE_FORWARDDELAY='0' BRIDGE_STP='off' IPADDR='172.16.1.1/24' enp0s25 is the local, normal ethernet interface which is working fine: 2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 Now: # ifup br0 # ip link 2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP mode DEFAULT group default qlen 1000 link/ether 28:d2:44:df:33:18 brd ff:ff:ff:ff:ff:ff 9: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 28:d2:44:df:33:18 brd ff:ff:ff:ff:ff:ff It seems that the scripts use the ethernet interface as the *default* value for BRIDGE_PORTS, which obviously then breaks networking. (If I had wanted a slaved network device, I'd have configured one.) brctl addbr br0 ; ip a add dev br0 172.16.1.1/24 ; ip link set br0 up creates the desired configuration just fine and is what I'd have expected given the configuration file. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1057592] New: Cannot connect to EAP secured wireless network with wicked
by bugzilla_noreply＠novell.com 08 Feb '22

08 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=1057592 Bug ID: 1057592 Summary: Cannot connect to EAP secured wireless network with wicked Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have trouble connecting my laptop to a PEAP secured wireless network, embarrassingly the AttachemateGroup one at SUSE HQ. The network settings seem to be right and match: BOOTPROTO='dhcp' BROADCAST='' DHCLIENT_SET_DEFAULT_ROUTE='yes' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='Wireless 7260' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='manual' WIRELESS_AP='' WIRELESS_AP_SCANMODE='1' WIRELESS_AUTH_MODE='eap' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='' WIRELESS_CHANNEL='' WIRELESS_CLIENT_CERT='' WIRELESS_CLIENT_KEY='' WIRELESS_CLIENT_KEY_PASSWORD='' WIRELESS_DEFAULT_KEY='0' WIRELESS_EAP_AUTH='MSCHAPV2' WIRELESS_EAP_MODE='PEAP' WIRELESS_ESSID='AttachmateGroup' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_PEAP_VERSION='' WIRELESS_POWER='no' WIRELESS_WPA_ANONID='' WIRELESS_WPA_IDENTITY='lmb' WIRELESS_WPA_PASSWORD='xxxxxxxx' WIRELESS_WPA_PSK='' Sep 07 13:44:40 hermes kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled Sep 07 13:44:43 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:93:f0 Sep 07 13:44:43 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:93:f0 (try 1/3) Sep 07 13:44:43 hermes kernel: wlp3s0: authenticated Sep 07 13:44:43 hermes kernel: wlp3s0: associate with f0:5c:19:1f:93:f0 (try 1/3) Sep 07 13:44:43 hermes kernel: wlp3s0: RX AssocResp from f0:5c:19:1f:93:f0 (capab=0x1411 status=0 aid=9) Sep 07 13:44:43 hermes kernel: wlp3s0: associated Sep 07 13:44:43 hermes wickedd-dhcp4[1521]: wlp3s0: Request to acquire DHCPv4 lease with UUID 4957ae59-c728-0b00-f205-000033000000 Sep 07 13:44:43 hermes kernel: wlp3s0: Limiting TX power to 23 (23 - 0) dBm as advertised by f0:5c:19:1f:93:f0 Sep 07 13:44:46 hermes kernel: wlp3s0: deauthenticating from f0:5c:19:1f:93:f0 by local choice (Reason: 3=DEAUTH_LEAVING) Sep 07 13:44:53 hermes wickedd-dhcp4[1521]: unable to confirm lease Sep 07 13:44:58 hermes wickedd-dhcp4[1521]: wlp3s0: defer timeout 15 reached (state INIT) Sep 07 13:45:00 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:97:f0 Sep 07 13:45:00 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:97:f0 (try 1/3) Sep 07 13:45:00 hermes kernel: wlp3s0: authenticated Sep 07 13:45:00 hermes kernel: wlp3s0: associate with f0:5c:19:1f:97:f0 (try 1/3) Sep 07 13:45:00 hermes kernel: wlp3s0: RX AssocResp from f0:5c:19:1f:97:f0 (capab=0x1411 status=0 aid=13) Sep 07 13:45:00 hermes kernel: wlp3s0: associated Sep 07 13:45:00 hermes wickedd-dhcp4[1521]: wlp3s0: Request to acquire DHCPv4 lease with UUID 4957ae59-c728-0b00-f205-000033000000 Sep 07 13:45:00 hermes kernel: wlp3s0: Limiting TX power to 30 (30 - 0) dBm as advertised by f0:5c:19:1f:97:f0 Sep 07 13:45:03 hermes kernel: wlp3s0: deauthenticating from f0:5c:19:1f:97:f0 by local choice (Reason: 3=DEAUTH_LEAVING) Sep 07 13:45:10 hermes wickedd-dhcp4[1521]: unable to confirm lease Sep 07 13:45:15 hermes wickedd-dhcp4[1521]: wlp3s0: defer timeout 15 reached (state INIT) Sep 07 13:45:41 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:93:e0 Sep 07 13:45:41 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:93:e0 (try 1/3) Sep 07 13:45:41 hermes kernel: wlp3s0: f0:5c:19:1f:93:e0 denied authentication (status 17) Sep 07 13:45:43 hermes wickedd-nanny[1523]: device wlp3s0: got signal linkDown Sep 07 13:45:43 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:93:e0 Sep 07 13:45:43 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:93:e0 (try 1/3) Sep 07 13:45:43 hermes kernel: wlp3s0: aborting authentication with f0:5c:19:1f:93:e0 by local choice (Reason: 3=DEAUTH_LEAVING) So there are a bunch of successful authentication attempts, but then DHCP doesn't work. Eventually the server throws me out again though. And no, the password is not incorrect. ;-) -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 996088] New: After updates today (29/08/16) efibootmgr: Could not set BootOrder: No space left on device
by bugzilla_noreply＠novell.com 28 Jan '22

28 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=996088 Bug ID: 996088 Summary: After updates today (29/08/16) efibootmgr: Could not set BootOrder: No space left on device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: stuart(a)stella-maris.org.uk QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After performing an update today, 29/08/16, I decided to run efibootmgr -v as I have had issues before. I then found it returned BootCurrent: 0003 Timeout: 1 seconds No BootOrder is set; firmware will attempt recovery Boot0000* opensuse HD(1,GPT,2eca2750-fed6-4e3f-887f-27f183020fda,0x800,0x61800)/File(\EFI\opensuse\grubx64.efi) Boot0001* Hard Drive BBS(HD,,0x0) Boot0002* CD/DVD Drive BBS(CDROM,,0x0) After which I ran efibootmgr -o 0000,0001,0002 which returned efibootmgr: Could not set BootOrder: No space left on device I then tried both update-bootloader --reinit which failed, then grub2-install which failed as well. This ended up with no efi boot options at all. I had to resort to chrooting from TW rescue disk and re-install grub2 and recover my PC. So far I have not tried to run the update-bootloader --reinit or grub2-install again since recovering my system as I fear it will mess up the system once more. As part of the update various grub2 packages were updated all not at beta3-10 level, the zypper history shows dracut running but no apparent errors were reported there. -- You are receiving this mail because: You are on the CC list for the bug.

2 9