May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1041606] New: Privoxy needs to be restarted after every boot when using wlan
by bugzilla_noreply＠novell.com 16 Oct '21

16 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1041606 Bug ID: 1041606 Summary: Privoxy needs to be restarted after every boot when using wlan Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: siebertjonathan(a)aim.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After installing privoxy and enabling the privoxy.service in systemd, the service is automatically started at boot but when only a wlan connection is setup by NetworkManager, privoxy needs to be restarted once before it can be used (verified in Firefox only, so far). This is similar to #977944 but in this case I do not get any error messages in journalctl about privoxy entering 'failed' state. Also `systemctl status privoxy.service` shows that privoxy is up and running. When a wired connection is present at boot, everything works nicely, even if the wired connection is removed and one switches to wlan. The necessity to restart the privoxy service makes using privoxy as a daemon rather painful. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1036025] New: javapackages-tools: packaging?
by bugzilla_noreply＠novell.com 15 Oct '21

15 Oct '21

http://bugzilla.suse.com/show_bug.cgi?id=1036025 Bug ID: 1036025 Summary: javapackages-tools: packaging? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: behlert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Looking at javapackages-tools.spec I see several subpackages being created: javapackages-tools, maven-local, gradle-local, ivy-local, python-javapackages Looking at javapackages-tools there are several files that might be better added to one of the others, like the maven-* files/directories. But my main problem is the dependency of javapackages-tools to a lot of python-packages, especially python-pyxb. I wonder if we can get rid of some of the pyton dependencies, to make installation of javapackages on a minimal system possible. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1010047] New: displaced headline at fcoeadm -s (see bug 1008745)
by bugzilla_noreply＠novell.com 12 Oct '21

12 Oct '21

http://bugzilla.suse.com/show_bug.cgi?id=1010047 Bug ID: 1010047 Summary: displaced headline at fcoeadm -s (see bug 1008745) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: holger(a)fam-schranz.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Related to the Bug 1008745 the headline from the output of fcoeadm-s is depend to length and therefor by longer insert (devname of the ethx) displaced. See the output screen in bug 10008745. Best regards Holger -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 989713] New: built-in wlan on raspberry pi3: no drivers
by bugzilla_noreply＠novell.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=989713 Bug ID: 989713 Summary: built-in wlan on raspberry pi3: no drivers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dannvasile(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 684856 --> http://bugzilla.opensuse.org/attachment.cgi?id=684856&action=edit Dmesg output The built-in wlan on the raspberry pi 3 isn't recognized by the OS. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 989284] New: KIWI images broken due to e2fsprogs update for U-Boot based boot, uses "64bit" feature
by bugzilla_noreply＠novell.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=989284 Bug ID: 989284 Summary: KIWI images broken due to e2fsprogs update for U-Boot based boot, uses "64bit" feature 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: stefan.bruens(a)rwth-aachen.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- e2fsprogs-1.43 adds the "64bit" feature for ext4 filesystems. KIWI uses the default features from /etc/mke2fs.conf U-Boot does not support ext4 with enabled 64bit feature. Thus this affects any system using U-Boot which stores kernel and initrd on the root filesystem. (e.g. rpi3 uses a seperate ext3 /boot partition, Pine64 uses the ext4 / root filesystem) The issue can be worked around by e.g.: "tune2fs -O ^64bit /dev/sdc2; e2fsck -y /dev/sdc2; resize2fs -s /dev/sdc2" assuming sdc2 is the root filesystem partition on the SD card. Affected image: e.g. http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Pin… -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1167565] New: JeOS-olinuxinolime: empty root in dracut fails boot
by bugzilla_noreply＠novell.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1167565 Bug ID: 1167565 Summary: JeOS-olinuxinolime: empty root in dracut fails boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: guillaume.gardet(a)arm.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fvogt(a)suse.com Found By: --- Blocker: --- openSUSE-Tumbleweed-ARM-JeOS-olinuxinolime.armv7l-2020.03.10-Snapshot20200317 does not boot. Turns out dracut fails at pre-mount. Looking at /dracut-state.sh it shows root="". Adding root=UUID=<UUIDOFIMAGE> to the kernel command line makes it boot. Is dracut supposed to figure out the root device itself like that or is the kiwi config supposed to add a root= parameter? -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1164310] New: [Build 20200213] wrong order: /boot/grub2/arm64-efi specified before /boot
by bugzilla_noreply＠novell.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1164310 Bug ID: 1164310 Summary: [Build 20200213] wrong order: /boot/grub2/arm64-efi specified before /boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1174670/modules/firs trun/steps/48 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mloviska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos@aarch64-HD24G fails in [firstrun](https://openqa.opensuse.org/tests/1174670/modules/firstrun/steps/… ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. `findmnt --verbose --verify` reports issue with mounts in /boot : : /usr/local [ ] target exists [ ] FS options: autodefrag,subvol=@/usr/local [ ] UUID=f8d31393-2483-4231-9ead-1682c870873e translated to /dev/vda4 [ ] source /dev/vda4 exists [ ] FS type is btrfs /boot/grub2/arm64-efi [E] wrong order: /boot/grub2/arm64-efi specified before /boot [ ] target exists [ ] FS options: autodefrag,subvol=@/boot/grub2/arm64-efi [ ] UUID=f8d31393-2483-4231-9ead-1682c870873e translated to /dev/vda4 [ ] source /dev/vda4 exists [ ] FS type is btrfs / [ ] target exists [ ] FS options: autodefrag [ ] UUID=f8d31393-2483-4231-9ead-1682c870873e translated to /dev/vda4 [ ] source /dev/vda4 exists [ ] FS type is btrfs swap [ ] UUID=135d9c2f-691f-4f23-8f61-75672c1fa424 translated to /dev/vda3 [ ] source /dev/vda3 exists [ ] FS type is swap /boot [ ] target exists [ ] UUID=221bc50e-fee7-4fc4-8659-a6245c9ff571 translated to /dev/vda2 [ ] source /dev/vda2 exists [ ] FS type is ext4 /boot/efi [ ] target exists [ ] UUID=90F4-E245 translated to /dev/vda1 [ ] source /dev/vda1 exists [ ] FS type is vfat ## Reproducible Fails since (at least) Build [20200115](https://openqa.opensuse.org/tests/1146520) ## Expected result Last good: [20200107](https://openqa.opensuse.org/tests/1136889) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1160314] New: aarch64 JeOS efi images comes with snapper unconfigured
by bugzilla_noreply＠novell.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1160314 Bug ID: 1160314 Summary: aarch64 JeOS efi images comes with snapper unconfigured Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- aarch64 JeOS efi images have a btrfs filesystem, with snapper installed but unconfigured. Those images should provide a default snapper configuration. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1141433] New: Get no hint that network connection is made by NetworkManager when start YaST Networkmanagement
by bugzilla_noreply＠novell.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1141433 Bug ID: 1141433 Summary: Get no hint that network connection is made by NetworkManager when start YaST Networkmanagement Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bnacht(a)web.de QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)arm.com Found By: Community User Blocker: --- Start YaST module LAN. Then I miss a hint (like in openSUSE for x86_64) that the network connections are managed by NetworkManager. This leads to an improper network configuration with a IP from DHCP (via NetworkManager) and a secondary IP address which is inserted via YaST lan. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1127613] New: no wifi on raspberry 3B+
by bugzilla_noreply＠novell.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1127613 Bug ID: 1127613 Summary: no wifi on raspberry 3B+ Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have installed TW on a raspberry 3B+ using the KDE appliance. It came up without a wlan interface - I ran a zypper dup, still no wlan. I found the following in in dmesg: [ 19.191508] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 19.192794] usbcore: registered new interface driver brcmfmac [ 19.233451] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.txt failed with error -2 bcm43xx-firmware is installed, but : # l /lib/firmware/brcm/brcmfmac43455-sdio* -rw-r--r-- 1 root root 488193 Jan 18 13:04 /lib/firmware/brcm/brcmfmac43455-sdio.bin -rw-r--r-- 1 root root 1864 Jan 18 13:04 /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt I added a symlink and rebooted. Now I have wlan. I don't know if this is standard procedure? -- You are receiving this mail because: You are on the CC list for the bug.

2 11