January 2018 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 1047498] New: gnuhealth not installable
by bugzilla_noreply＠novell.com 17 Jan '22

17 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1047498 Bug ID: 1047498 Summary: gnuhealth not installable Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: axel.braun(a)gmx.de, okurz(a)suse.com Found By: --- Blocker: --- Found by openQA (https://openqa.opensuse.org/tests/441262#step/gnuhealth_install/12) and confirmed by installcheck: can't install gnuhealth-3.2.0-1.1.noarch: nothing provides python3-caldav needed by gnuhealth-3.2.0-1.1.noarch nothing provides python3-cracklib needed by gnuhealth-3.2.0-1.1.noarch nothing provides python3-pyBarcode needed by gnuhealth-3.2.0-1.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 966599] New: home:j-engel/bacula: Bug
by bugzilla_noreply＠novell.com 15 Jan '22

15 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=966599 Bug ID: 966599 Summary: home:j-engel/bacula: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: jcnengel(a)gmail.com Reporter: marc(a)marcchamberlin.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Tried to download/install Bacula 7.4.0 using the 1 click installer and downloading the RPM package. I get the following error - nothing provides libbaccats-7.4.0.so()(64bit) needed by bacula-7.4.0-6.2.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 940478] New: ASL: rename conflicting-confusing package
by bugzilla_noreply＠novell.com 14 Jan '22

14 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=940478 Bug ID: 940478 Summary: ASL: rename conflicting-confusing package Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: alinm.elena(a)gmail.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE:Factory already has an "asl" package, and recently gained an "ASL" package. This very same name is, I will argue, confusing for both users and developers, as they only differ in case, and case is not something people pay sufficient attention to when e.g. reporting bugs or discussing. I suggest to rename the ASL package. Considering that "asl library" yields lots of different things on Google already, a package name like "advsimlib" might work better than "asllib". Confer with the asl.org.il team perhaps. [ The current plan is to reject, in the direct future, same-name submissions to Factory which only differ in casing. On a related notem, libzypp even falls over currently (but probably intentionally; see bug #940477). ] -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1060506] New: libkolabxml packages differ for every build
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1060506 Bug ID: 1060506 Summary: libkolabxml packages differ for every build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: lbeltrame(a)kde.org Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matthias(a)mailaender.name Found By: Development Blocker: --- When working on the reproducible builds project for openSUSE I found that libkolabxml packages differ for every build unless ASLR is disabled in the build system. This indicates either usage of unitinialized memory (compare [1]) or using (randomized) pointers in output. /usr/lib64/libkolabxml.so.1.1.6 differs because of /home/abuild/rpmbuild/BUILD/libkolabxml-1.1.6/build/kolabformat-xcal-schema.cxx 2018-10-30 08:42:53.622040000 +0000 @@ -9014,9 +9014,9 @@ 0x00, 0x01, 0x6d, 0x09, 0x00, 0x01, 0x3f, 0x07, 0x00, 0x01, 0x23, 0x07, 0x00, 0x01, 0x53, 0x0a, 0x00, 0x01, 0x68, 0x07, 0x00, 0x01, 0x7f, 0x09, 0x00, 0x01, 0x4e, 0x04, 0x00, 0x01, 0xfe, 0xff, 0xff, 0xff, 0x1d, 0x00, - 0x06, 0x0e, 0x00, 0x06, 0xe8, 0x08, 0x00, 0x01, 0xff, 0xff, 0xff, 0xff, + 0x06, 0x0e, 0x00, 0x06, 0x25, 0x07, 0x00, 0x01, 0xff, 0xff, 0xff, 0xff, 0x00, 0x03, 0x0c, 0x00, 0x06, 0x58, 0x53, 0x41, 0x6e, 0x6e, 0x6f, 0x74, - 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x03, 0x11, 0x09, 0x00, 0x05, 0x3c, + 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x03, 0xb6, 0x01, 0x00, 0x05, 0x3c, 0x00, 0xff, 0x78, 0x73, 0x3a, 0x61, 0x6e, 0x6e, 0x6f, 0x74, 0x61, 0x74, [...] which probably comes from # Compile Schemas add_custom_command(OUTPUT kolabformat-xcal-schema.cxx COMMAND ${XSDBIN} --verbose --array-name iCalendar_schema --output-dir ${CMAKE_BINARY_DIR} ${SCHEMAS} which might be from ./compiled/xsdbin.cxx and/or involving the xsd package [1] https://build.opensuse.org/package/view_file/M17N/gcin/gcin-reproducible.pa… -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1061219] New: trackerbug: packages do not build reproducibly from including uninitialized memory
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1061219 Bug ID: 1061219 Summary: trackerbug: packages do not build reproducibly from including uninitialized memory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other 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 Found By: Development Blocker: --- See also https://reproducible-builds.org/ When packages write uninitialized memory into files that are packaged it results in binaries that differ on every build. These thus trigger rebuilds of depending packages and are 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 13

[Bug 1060111] New: bash: have: command not found
by bugzilla_noreply＠novell.com 30 Dec '21

30 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1060111 Bug ID: 1060111 Summary: bash: have: command not found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: matthias(a)mailaender.name QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just encountered this in openSUSE Tumbleweed where every terminal displays > bash: have: command not found upon startup. http://www.jerous.org/2016/09/19/bash-have-not-found describes the problem and proposes a solution. I don't know if it is the correct approach. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 937067] New: efi=1 does not seem to work anymore
by bugzilla_noreply＠novell.com 17 Dec '21

17 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=937067 Bug ID: 937067 Summary: efi=1 does not seem to work anymore Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: kukuk(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In the past, you could add efi=1 as argument for the installer, and your system was setup for EFI boot, even if the detection fails. This works only partly with Tumbleweed 20150630: the bootloader still installs and configures grub2-x86_64-efi, but the storage proposal does not create a vfat /boot/EFI partition anymore. This works with SLES12, haven't tested openSUSE 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 997918] New: TW 20160901: unable to dup since docker-compose conflicts with python-requests
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=997918 Bug ID: 997918 Summary: TW 20160901: unable to dup since docker-compose conflicts with python-requests 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: robert.munteanu(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: fcastelli(a)suse.com Found By: --- Blocker: --- Another iteration of bug #984309 Problem: docker-compose-1.7.1-2.2.noarch conflicts with python-requests >= 2.11 provided by python-requests-2.11.1-1.1.noarch Solution 1: deinstallation of docker-compose-1.7.1-2.2.noarch Solution 2: keep obsolete python-requests-2.10.0-3.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

2 4