April 2019 - 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 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

[Bug 1086757] New: Images for Raspberry Pi 1/2/3 does not boot - only Splash Screen Rainbow
by bugzilla_noreply＠novell.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1086757 Bug ID: 1086757 Summary: Images for Raspberry Pi 1/2/3 does not boot - only Splash Screen Rainbow 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: kasimir_(a)outlook.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have tried the current images [1] of the Raspberry Pi 1/2/3 and get only the Splash Screen Rainbow. No messages are output through the serial console. [1] RPi1: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2018.03.25-Build1.1.raw.xz RPi2: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi2.armv7l-2018.03.25-Build1.1.raw.xz RPi3: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2018.03.25-Build1.1.raw.xz -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1073820] New: meson fails to build projects when run under the fish shell
by bugzilla_noreply＠novell.com 11 Oct '21

11 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1073820 Bug ID: 1073820 Summary: meson fails to build projects when run under the fish shell Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: sor.alexei(a)meowr.ru Reporter: simonf.lees(a)suse.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: pth(a)suse.com, sbrabec(a)suse.com Found By: --- Blocker: --- I have my shell set to /usr/bin/fish and meson fails to detect gcc properly, if I switch to bash then the project builds fine, i've seen this on multiple projects when building under tumbleweed. simon@tek-top ~/src/build/wireless ➤ meson build The Meson build system Version: 0.43.0 Source dir: /home/simon/src/build/wireless Build dir: /home/simon/src/build/wireless/build Build type: native build Project name: wireless Meson encountered an error in file meson.build, line 1, column 0: Unable to detect GNU compiler type: cc: error trying to exec 'cc1': execvp: No such file or directory A full log can be found at /home/simon/src/build/wireless/build/meson-logs/meson-log.txt -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 930505] New: every package available in standard or optional repos is not discoverable via https://software.opensuse.org/search
by bugzilla_noreply＠novell.com 06 Oct '21

06 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=930505 Bug ID: 930505 Summary: every package available in standard or optional repos is not discoverable via https://software.opensuse.org/search Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Infrastructure Assignee: mrueckert(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: lrupp(a)suse.com Found By: --- Blocker: --- mc is the package name and binary executable for the best available file manager in openSUSE repos. Latest Midnight Commander (mc) not discoverable via https://software.opensuse.org/search . Until recently, current mc for 13.1 could be found on http://download.opensuse.org/repositories/Base:/System/openSUSE_13.2/ but this repo has been retired. Searching https://software.opensuse.org/search for search term commander produces no hits for Midnight Commander or mc. Search term mc is not acceptable to https://software.opensuse.org/search, as it rejects two character search strings, first by announcement, then when proceeding anyway, searching for mc only as a substring, listing many packages containing string mc but not mc itself. I tried searching for latest mc on https://build.opensuse.org/search but as I am not a builder I found it too difficult to use to locate latest (mc-4.8.14) even with help from irc://freenode/opensuse-factory. Something needs to be done so that every package that exists in standard or BS repos can be discovered via https://software.opensuse.org/search without the degree of difficulty searching for Midnight Commander presents. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1102840] New: trackerbug: build fails at some time
by bugzilla_noreply＠novell.com 05 Oct '21

05 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1102840 Bug ID: 1102840 Summary: trackerbug: build fails at some time Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Depends on: 1081871, 1031548, 1031549, 1068372 Found By: Development Blocker: --- Some packages make assumptions about the date+time they are built e.g. assuming that cookies or SSL-certs in their unittests are not yet expired but that breaks building in the future. This can cause trouble for maintenance-updates later and it makes my reproducible builds efforts harder. -- You are receiving this mail because: You are on the CC list for the bug.

2 3